On Monday 18 December 2006 11:24, David Leangen wrote:
> Essentially, a menu item is a link (can't think of anything else it
> could be) that does one of the following:
>
> - Directs to some outside page
> - Directs to another page in the same app
> - Invokes some process
- Modify the content of the current page.
and other typical "onClick()" actions in Wicket lingo.
> In that sense, each wicket osgi component should have the possibility
> (not the obligation) to contribute its menu item to the app, and we
> should look at this from the perspective of the component that
> contributes the menu item, not from the perspective of the menu item
> itself.
Yes, the "best practice" I have in mind is that the bundle that contains the
PAGE that you want to LINK TO, registers the MenuItem for that Page. And that
the bundle that own the Page where the Link will show up, instantiates and
manages the Menu. ("Manage" in this context is primarily identification and
rendering.)
So, I don't think we are on different pages (pun intended) on this one. I
perhaps need better explaination in the docs and the example will show what I
mean in better detail.
Cheers
Niclas
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
