On Apr 16, 2012, at 6:50 PM, Usman Bhatti wrote:
Hello,
I am building a MoosePanel with customized entities, customized model and, hence
customized menus. So, for example, in models pane I would like to display only my own
models.
For menu items, I am looking to replace existing menus (on models and entities) with my
own menus: since the entities in my custom models are particular, current menus cannot be
used (some parts can be used e.g. delete a model). I would like to keep the current
display/navigation model of the moose panel/moose finder.
For my solution, I have started subclassing MooseModel and MooseEntity to be able to
describe my customized menus on my models and entities.
Customized model integration in Moose Panel was smooth: subclass MooseModel and launch
this class from a MoosePanel subclass (needed to do a resetMeta, though).
Customized menus cannot be constructed by simply subclassing MooseModel and MooseEntities
because menus are constructed from particular pragmas inside methods of these classes.
My solution: I override mooseFinderActions method in my custom model class to populate
menus of my model. I works. However, I cannot reuse parts of MooseModel menus that are
applicable on my customized model. Similarly, for actions (moosePresentationOrder:) I
override methods for customized menu building through pragma reading.
My question: Is it the right way to achieve my objectives or should I look somewhere else
for the task?
may be we should introduce a policy object?
tx,
usman
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev