[ http://issues.apache.org/jira/browse/JS2-69?page=comments#action_59483 ]First let me say that the profiled navigation is very powerful and very useful for me. I have several sites running using role-based aggregation of navigations, and it works great. On the negative side, it wasn't easy to configure. What we need is something very intuitive that can be tooled into a UI so that site maps can be created easily. I agree with Randy: we need a better abstraction. Perhaps the site map abstraction is right.
Randy Watler commented on JS2-69:
---------------------------------
From my experience and user requirements, I had trouble getting menus to match the folder/page tree. I spent hours trying to get the algorithms to produce something that I could much more easily and more and intuitively generate with a declarative XML menu data structure. (yes im bringing this up again.)
> Generally, the goal is to provide some basic information "out of the > box", (i.e. w/o the need for document sets or other configuration > information), to support typical navigations for small to medium > sized portals.
One use case that keeps popping up is a rootless tree.
I find myself working around the root. If I have a need for for top menus as folders, and then submenus as psml, i have to move one arbitrary folder down into the root.
> "{/*,/*/,/deep0/*,/deep1/*,/deeper/*/}". Of course, a simple default > > like "{/*,/*/*}" would due in many cases. If paths are too limiting,
> a full XML menu definition might be required... but there have been
> other votes against such a thing.
not my vote
> Given that the profiler would be used to generate this "site map", it > does not seem that any capability to specify multiple menu definitions
Ive already written several applications using the profile per user approach along with navigations. I would suggest that dealing with backward compatibility is important
My opinion is that trying to build the menu on the fly off of the physical layer may not be the best approach. A better abstraction could leverage all the work Randy put into profiled-pages and navs. Perhaps this abstraction is a site map or a declarative xml menu in the folder metadata.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
