Navigation definition for projects - propsal

adamw Mar 29, 2006 9:36 AM

Hello,
with the restructuring of navigation, this idea came to me: now, we can support only "flat" - one level - project menus, and you define a project's menu with <page ...>, <freezone-link> and <outside-link> tags.

How about changing that, to support multi-level menus, and more customizable? Specifically, I thought about embedding fragments of <menu ...> definitions in project.xml (so a definition of a project's menu would be just like in navigation.xml, but in project.xml).

What do you think?

--
Adam

1. Re: Navigation definition for projects - propsal

dsicore Mar 29, 2006 9:39 AM (in response to adamw)

I think this will be useful someday, esp. if we go to a layout where there is only one project visible at any given time. If there are multiple projects visible, we may get into a four layer deep menu which might not work.

Sacha's proposed layout uses a "one project only" layout. So, I'd say, yes, this should be useful.
Actions
2. Re: Navigation definition for projects - propsal

adamw Mar 29, 2006 9:42 AM (in response to adamw)

That's how menus now work - in the trunk version - when a project is visible, it's menu is visible as a "top-level" one.
Actions
3. Re: Navigation definition for projects - propsal

dsicore Mar 29, 2006 9:45 AM (in response to adamw)

"adamw" wrote:
That's how menus now work - in the trunk version - when a project is visible, it's menu is visible as a "top-level" one.

And.. I'm wondering if someone is going to change their mind sometime soon. ;)
Actions

Go to original post