Hi Mark, sounds as a solution even if I don't understand what you were trying to explain... Some sample code would help a lot, is there something you can show us/commit to one of the widely known Tapestry repositories?
Cheers, Andreas On 01. Jun 2006 - 14:51:00, Mark Stang wrote: | 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
