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]
