click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian A. (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLK-407) Menu improvements - more properties: enable/disable, show/hide
Date Wed, 01 Apr 2009 16:52:12 GMT

    [ https://issues.apache.org/jira/browse/CLK-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694615#action_12694615
] 

Adrian A. commented on CLK-407:
-------------------------------

I also need enable/disable, show/hide  methods in most applications for the menus.
(I think the simplest would be to add the according properties to the xml file and the Menu
class)

In most applications, it's a requirement:
- to be able to hide items not just based on roles but also based on application logic, and
not just at the beginning but at various moments in time.
- to disable (i.e. to show but make non-click-able some items) e.g.
   - user needs to upgrade his account to a better scheme or it is in demo/trial mode.
   - another user performs that action at the same time (e.g. backup or some other batch process),
so the menu item needs to be disabled too.

For this to work properly however, I think https://issues.apache.org/jira/browse/CLK-405 should
also work correctly - only so it makes (if different users can see different menu item states)

Thank you,
A.

> Menu improvements - more properties: enable/disable, show/hide 
> ---------------------------------------------------------------
>
>                 Key: CLK-407
>                 URL: https://issues.apache.org/jira/browse/CLK-407
>             Project: Click
>          Issue Type: Improvement
>          Components: extras
>            Reporter: Demetrios Kyriakis
>
> Please improve the Menu Control, by allowing the user to show/hide menu items, and also
to enable/disable them.
> Right now, this is not possible at all with the Menu Control :(.
> This is very limiting, making the existing Menu Control useless for most user applications,
thus forcing the users
> to make their own menu controls (or the hack the original one). 
> There's no need for these properties to be present in menu.xml, since their role is mostly
at runtime:
> - enable/disable would allow to enable or disable a menu item (so to show it but make
it unclickable).
> - show/hide would allow to to show and hide menu items (of course if the user doesn't
have a specific role, the menu will be hidden).
> Regarding the API, it would be important to have practical methods for hiding and disabling
menu items:
> something like Menu#hide(Menu item) would not be very practical since in most cases the
"item" reference is not present
> so it should be Menu#hide(String path), and when applied, to seach this in the children
items too.
> Another improvement would be if the Menu Click control would use Link Controls for the
items (since that's what they are).
> Thank you,
> Demetrios.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message