There is another option to get around that restriction.  It is what Howard 
calls my "mutant" application.  I have one Frame.html/Frame.page/Frame.java.  
All of my other pages are popups.  There are about 5 or 6 of those.  In 
addition, I have 130 "components".  None of my components have any border 
content, it is all in the "Frame".  As part of the Frame I have Breadcrumbs and 
something we call Headcrumbs.  Headcrumbs are a higher level menu.  So, we can 
have a bunch of "breadcrumbs" within each headcrumb.  Headcrumbs are a group of 
"breadcrumbs".  Breadcrumbs are reusable across multiple Headcrumbs.  Any one 
breadcrumb knows nothing about any of its fellow breadcrumbs in a headcrumb.

Basically, we have a wizard application with 130 screens.

The border component replaces pages, we have one page that replaces components. 
 There is an age-old Tapestry question about whether you create components or 
pages?  What is your level of re-use?  We chose re-use at the level of 
components.

regards,

Mark


-----Original Message-----
From: Andreas Bulling on behalf of Andreas Bulling
Sent: Thu 6/1/2006 2:29 PM
To: Tapestry users
Subject: Re: Border question
 
On 01. Jun 2006 - 14:06:48, Mark Stang wrote:
| The other option is to create your own menuing component.  Start with 
manually coding a couple of HTML pages to get the L&F.  Then abstract it 
backwards into a component that creates the HTML on-the-fly. Then just add that 
component/components to each page.  Or put them all in a border page and change 
out the interior.

Is this the best practice for implementing for example a breadcrumb
or a multi-level menue?

The problem is caused by Tapestry's component-based approach:
You have to define the "logical order" (the tree-structure) of your pages 
manually
in a seperate file, directly in the pages or in a not portable component.
That's more difficult than in a actions/operations-based approach... :-(

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