[ https://issues.apache.org/jira/browse/OFBIZ-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876017#action_12876017 ]
Scott Gray commented on OFBIZ-3373: ----------------------------------- Adrian, I'm not entirely sure what you're suggesting, or more specifically, how it differs from what's in my patch. The patch does modify the menu model at run-time but that is on purpose, the idea being that these external add-ons transparently become an intrinsic part of the model being extended. In this way, even if you do have a hot-deploy order manager, the plug-in will still work so long as your custom application is extending the order manager's controller and reports menu. Unbeknownst to the hot-deploy app those order manager artifacts are actually composites of the base functionality plus any plugged in functionality. I actually think it's kinda cool. > Adding menu merging feature > --------------------------- > > Key: OFBIZ-3373 > URL: https://issues.apache.org/jira/browse/OFBIZ-3373 > Project: OFBiz > Issue Type: Wish > Components: framework > Reporter: Bruno Busco > Priority: Minor > Attachments: googlebase-inject.patch, injections.patch, links.jpg, > partymenu.JPG > > > Hi devs, > while discussing in the ML about modules and framework separation I thought > to this new feature that I would like to discuss here with you. > We have now the possibility to extend a menu from one other. This is great in > order to have an high level of code reuse and great consistency all over > OFBiz. > I was thinking to a sort of "merges-to" property for the menu widget. > This would allow a new module to specify an already exixting menu name (in > the framework core or in a lower level module) that should be somewhat > changed by the actual menu. > For instance, in the attached image partymenu.jpg there is a a tipical use of > this feature: > in the party module there are lot of links that co to order application, > account etc. Those menu link could be used defining a simple menu (say it > partylinks_menu) in the party application that contains only party or > framework related links (i.e. profile); additional components like order or > accounting could define more menus that merges-to the partylinks_manu so that > when the menu is rendered IN THE PARTY APPLICATION the new menu items added > in the order and accounting applications are also rendered. > This would allow us to dramatically reduce the component dependence and help > us to have the framework-only distribution. > To eventually implement this I think there should be an entity that defines > such mergin menus and the menu rendered should lookup the entity to check if > one or more merges to the actually rendering menu is defined. > I would appreciate to hear from you if this idea can help. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.