[
https://issues.apache.org/jira/browse/CLK-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694082#action_12694082
]
Joseph Schmidt commented on CLK-407:
------------------------------------
> How you render it is up to you. This is why rendering is done via a Velocity
> macro.
Exactly this is my biggest problem with the behavior of the Menu control :(
I don't have to do this with most Click controls, and that's why I like Click.
I just use $form and $table - nothing more. Only Java code.
(well the Panels are an exception - they look complicated too, so I don't use
them either :( - despite the fact that I would like to :( )
> Its not possible to anticipate all the ways people may wish to provide the
> page navigation.
Of course not, but what about good/intelligent defaults?
What about a good set of "decorators"(styles, or how would one call it) like I
described in the links in the following issues ?:
https://issues.apache.org/jira/browse/CLK-511
https://issues.apache.org/jira/browse/CLK-512
They would cover what most people want - just like the Table control does.
thanks,
Joseph.
> 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.
