Professional Content LLC <cdfisher <at> vps1.procontent.org> writes:
> If Tapestry is indeed a component framework, then are we making a mistake > by creating the largest presentation layer as a dynamic object? No, it's not, as long as this object (called the Border component in Tapestry) delegates the rendering of its various parts to others. > I thought the way this should play out > would be for there to be three html files for three states of the > application. > Based on this design, if a > presentation change is called for, the html is modified, the L&F is approved, > (heads nod, smiles all around) and then the developer finds exactly where I > made that change, and copies and pastes it into his > servlet at just the right spot. The presentation cannot be > viewed in an HTML editor because the presentation might as well be in a JSP object. What's wrong whith this picture? It it my understanding of Tapestry? In Tapestry, it works similarly except that the designer can work on the html of the Border component directly in an HTML editor! The programmer doesn't need to copy and paste! To see how to make a Border component, there is an example in the component reference for RenderBody. There is also a detailed example in my book. -- Author of an e-Book for learning Tapestry (www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
