Hi,
Maybe I did not understand the change set, so let me tell you what I see: each class specifies the superclass from which to start building the menu. For example, in your implementation, MooseEntity says that the menu is built starting from the MooseEntity downwards.
This might be Ok for your context, but it breaks the original requirement for this menu: to provide a quick way to get to the default menu (including Inspect which is quite important during prototyping) for any object from a script like Mondrian or Glamour. This is why I do not see it working right now.
I believe that what you want is more of an object-specific menu, or even better a browser specific one. Am I wrong?
Cheers, Doru
On 8 May 2012, at 20:30, Stéphane Ducasse wrote:
Doru
I do not understand why having some hooks methods are the wrong way. To me having a method without hooks in the top of the hierarchy is not so good. And this is cheap to get a couple of hooks when they can already solve part of the problem.
So now I got it we will build our own solution and nuke the default one of Moose. Stef
Hi,
I took a quick look, and I think this is the wrong way to approach the problem. The default Moose menu relies on a lightweight implementation that is useful for just that: being a default menu. If you are adding multiple layers to this mechanism it will become too complex.
If you want to go into customization, than the way to go is to reify each action as an object and then assembly the menu by putting those objects together in the menu logic. Basically, you would need to implement a command hierarchy (like the hierarchy of MoosePanelCommand).
Cheers, Doru
On Tue, May 8, 2012 at 2:25 PM, Usman Bhatti usman.bhatti@gmail.com wrote:
Hi,
As discussed, I am working on the idea how to customize menus for entities in Moose Finder. As the menu construction depends on the pragmas defined on moose entity hierarchy, the idea is to read pragmas in some specific way. We tried something with Stéphane yesterday and here I am sending you the change set. Can you please have a look?
The change set does not complete resolve the problem :-). The problem is that menus are duplicated and changes are still invasive (that is the code overrides the default moose finder behavior). But this can be a possible approach to resolve it.
tx
Usman
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."