Andreas,
That is a good question.  When we first started doing Tapestry I created a menu 
component.  It was based on our "states".  Each breadcrumb is a state and each 
headcrumb is a finite state machine.  With Tapestry and it's many pages the 
question is how do you link everything together?  Pages can be tightly coupled 
to other pages.  I like to think of it as a "wire diagram".  A "wire diagram" 
has a list of all pages and the links between each page.  I presume that a menu 
would drop you into different points in the "diagram".  The question is are you 
trying to define a generic menu component that can be "populated" with the 
links between the pages or are you trying to create a project specific menu 
component that only has to work with your existing pages?

Then the next question is what does it look like visually?  Is it down the left 
side or across the top?  If it is nested then each one would have it's list of 
pages.  Which I think would support menus within menus.  As part of the "menu" 
component you would pass in a list of Menu Options and for each option a 
"Destionation Page".  If you take a step back, this is a tree structure.  So, 
it could be stored in a database or an XML file.  Or it could be hard-coded in 
the supporting classes.  The component itself could genereate different 
HTML/JavaScript as needed.  I would start by creating one manually to see how 
it works and how the L&F works.  Then I would generalize it from there.

hth,

regards,

Mark


-----Original Message-----
From: Andreas Bulling on behalf of Andreas Bulling
Sent: Fri 6/2/2006 2:25 AM
To: Tapestry users
Subject: Re: Border question
 
Hi Mark,

thanks for your explanations which made it a little bit clearer for me ;)
But just another short question: How would you implement a multi-level
page menue? Especially would you use a external file to describe the
page hierarchy/structure?

Thanks!
  Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to