Hmm, OK, I guess there is no good solution to this. I have menu and locale selection in my border and some other stuff and I don't want to put this in all pages. But keeping the static version in all pages seems almost as tedious. Or maybe I'll just add the css in all pages and then the design guy will have to imagine all the menu stuff around each page body. But I'm not happy with this. ....
Malin On 8/21/06, hv @ Fashion Content <[EMAIL PROTECTED]> wrote:
This is why I don't use the Border component pattern, but add the basic structure to all pages. With a decent css design and some NavigationPane/Header/Footer components you can keep the additional tags quite low, and allow the designer maximum freedom. Something like: <html jwcid="shell"> <head jwcid="$remove$"> ... </head> <body jwcid="body"> <div id="navbar" jwcid="navbar"><ul><li>Link</li></ul></div> <div id="content"> .. </div> <div id="footer" jwcid="footer">copyright etc.</div> Henrik "Malin Ljungh" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] >I thought one of the main advantages of Tapestry was that you can open your > html files directly from > the filesystem and see how they actually will look when rendered by the > Tapestry servlet. > > But now when my design guy is about to do the css this is not the case, > and > I guess it is because I have not entered static bodies to the components > that renders its own body in a proper way. And the biggest "problem" is > maybe the border component. > Am I supposed to insert a static version of my border component in each > and > every page to get this to work properly? What if I change the border > component - I will have to change all my files... > > I realise this is not a critical runtime issue, but I thought maybe I have > missed something here. How do you guys handle this? > > Malin > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
