You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Michael Xu (JIRA)" <ji...@apache.org> on 2009/12/22 07:29:18 UTC

[jira] Commented: (OFBIZ-3373) Adding menu merging feature

    [ https://issues.apache.org/jira/browse/OFBIZ-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793531#action_12793531 ] 

Michael Xu commented on OFBIZ-3373:
-----------------------------------

hi Bruno,

This is really a great idea, which is similar with extension points in OSGI. Basically, each module can define its own extension (simple menu in this case) and then system can automatically load and aggregate them from different extension points in different components.

Just my thoughts here:
* access control on menu item level
(If one user have no appropriate permission(s), then he should not even see the menu item.)
* make the UI more flexible
In the attached screen, I would like to suggest to put a "actions" dropdown list to contain all menu items. Otherwise, the layout might be likely get messed up. Of course, different people could have different taste. So maybe it is better to have flexibility here.
* Is it possible to link an icon for each menu item? still for UI purpose.

+1

Regards,
Michael

> 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: 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.