-
1. Re: They all should be Trees:Panel Menu, Context Menu, Drop
luxspes Aug 9, 2008 3:08 PM (in response to luxspes)8 days and no answer, I tried to do this, but I do not know enough about RichFaces internals... So, I asked for it as a feature request: RF-4128.
I only hope someone with the required knowledge finds a time to implements this. -
2. Re: They all should be Trees:Panel Menu, Context Menu, Drop
luxspes Dec 16, 2008 4:07 PM (in response to luxspes)Today RF-4128 was rejected with the comment:
"Solution exist using c:forEach or bindingd. "
But I didnt ask for an alternative way of solving this problem, I asked for integration Panel Menu, Context Menu, Drop Down Menu... why was that rejected?
In ASP.NET all the controls that can deal with hierarchical information can bind to a HierarchicalDataSourceControl ( http://msdn.microsoft.com/en-us/library/system.web.ui.hierarchicaldatasourcecontrol.aspx ), and therefore a consitent programming model can be used to deal with all of them... if " c:forEach or bindingd" were alredy good enought... then...
why did you recursiveTreeNodesAdaptor in the first place? Is it really such a bad idea to ask for an unified way to deal with Hierarchical data controls? -
3. Re: They all should be Trees:Panel Menu, Context Menu, Drop
nbelaevski Dec 17, 2008 9:10 AM (in response to luxspes)Hello,
I've reopened the issue. -
4. Re: They all should be Trees:Panel Menu, Context Menu, Drop
luxspes Dec 17, 2008 11:33 AM (in response to luxspes)Thanks a lot! :-D.
So... do you think we could have some kind of hierarchicalDataAdaptor that works for Tree, Panel Menu, Context Menu, Drop Down Menu in the not so distant future?
Regards,