I think we need to be more flexible here. The idea of
having a standard set of navigation links is good, but
what if there are more than one sets of menus, that
may or may not appear on some pages?
Also, I think it would be a really smart move to
change the format to XML now. If we do it right, it
should be just as easy to read, and a lot easier to
extend.
Here's an example of what I have in mind.
<wireframe>
<head>
<application-name>Demo Application</application-name>
<author>Patrick McElhaney ([EMAIL PROTECTED])</author>
</head>
<alias name="standardMenu">
<link fuseaction="red">Red Page</link>
<link fuseaction="green">Green Page</link>
<link fuseaction="blue">Blue Page</link>
</alias>
<alias name="admin">
<description>
This page will only be available to
administrators.
</description>
<link fuseaction="addUser">Add User</link>
<link fuseaction="editUser">Edit User</link>
</alias>
<fuseaction name="home" title="Home">
<description>
This is the home page.
</description>
</fuseaction>
<fuseaction name="red" title="Red Page">
<description>
This page is about the color red.
</description>
<link fuseaction="pink">Read about pink</link>
<alias name="standardMenu"/>
</fuseaction>
<fuseaction name="green" title="Green Page">
<description>
This page is about the color green.
</description>
<alias name="standardMenu"/>
</fuseaction>
<fuseaction name="blue" title="Blue Page">
<description>
This page is about the color blue.
</description>
<alias name="standardMenu"/>
</fuseaction>
<fuseaction name="pink" title="Pink Page">
<description>
Pink is a light shade of red.
</description>
<link fuseaction="red">Back to red</link>
<alias name="standardMenu"/>
</fuseaction>
<fuseaction name="editUser" title="Edit User">
<description>
Here you can edit a user.
</description>
<alias name="admin">
</fuseaction>
<fuseaction name="addUser" title="Edit User">
<description>
Here you can add a user.
</description>
<alias name="admin">
</fuseaction>
</wireframe>
Does that make sense? Basically, each fuseaction
can have a description (which is basically
responsibilties, but I used a term that's more
flexible), as well as links to other fuseactions.
In addition, aliases can be defined to
automatically include a description and/or
links in specified fuseactions -- a minor
enhancement to Hal's idea.
What do you think?
Patrick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
