On 7/20/05, Michael Henderson <[EMAIL PROTECTED]> wrote: > Hi > > I agree that the original Poster seems not to have 'grokked' components yet > and is looking around for an include mechanism. > > Perhaps we need some Wiki postings to explain how to achieve common tasks > with Tapestry with explicit reference to their JSP/Struts equivalent. > > On top of this can we come up with a 'lite' implementation strategy for new > Tapestry users or those developing departmental apps which won't have a large > number of users, won't be clustered and for whom the notion of tuning > persistent page or component properties is overkill, such as special > component and page subclasses or a runtime enhancement strategy that persists > all programmer declared properties (perhaps via setter/getter enhancement a > la hibernate) into the session.
Yeah defintely... I was looking at the Ruby on Rails pages... They have really nice documentation and tutorials. (also the web site itself is very slick!) This makes IMO more difference than the technology itself. Henri. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
