[
https://issues.apache.org/jira/browse/OFBIZ-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876014#action_12876014
]
Scott Gray commented on OFBIZ-3373:
-----------------------------------
We've had the ability to extend applications via new components for a long
time. This doesn't take away from that.
What it does provide is the ability to create new features for existing
applications without needing to modify those applications directly. Personally
I think this is sorely needed and clearly evidenced by some of the special
purpose components that really don't fit well as their own webapp, e.g.
googlebase (catalog), the ebays (catalog, ordermgr), oagis (ordermgr, catalog,
facility).
Say I've created a new set of reports for the order manager application, should
I have a completely separate webapp just to deliver a few reports? Should I
completely override the order manager in hot-deploy just to add a few apps?
What if I want to distribute these reports for other people to use in their own
applications, should I bundle up my customized hot-deploy order manager app and
distribute that? What if the people I'm distributing to already have their own
customized order manager app because they needed to add a couple of screens
somewhere else, should they try and merge the two?
With this approach you just drop in your plug-in component and boom, there the
reports are in the existing application. The idea here is that you pick and
choose from the available plug-ins in order to enhance the applications
distributed with OFBiz to meet your needs.
> 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.
