If partial rendering was not possible, Tacos would not exist. But it does, which indicates that rendering partial pages is possible.
It's all just objects that implement methods, so partials are completely doable. The Tacos crew, including Jesse, have that working for 4.0. Jesse is working on improvements to the API for 4.1 to support partial rendering more efficiently. On 1/30/06, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > Maybe I'm just too new on the list, but why the flyweight pattern is not > applicable in this case ? > My main concern is of Tapestry not having a runtime component model. > That way you don't have to render the whole page to get a single AJAX > component. Am I wrong ? > > -- > Ing. Leonardo Quijano Vincenzi > DTQ Software > > > Geoff Longman wrote: > > I know why the LOLs came. I and many others have seen this discussion > > rise and fade many times over the last 5 years or so. So many times > > that I don't have the energy to join the debate anymore. I personally > > don't (need/want/care about) this behaviour. > > > > Things like bugs/enhancements posted on the list generally are not > > actioned until they get into Jira anyways. > > > > As it was Howard jumped in right after my post and retiterated (as he > > has many times in the past) why Tapestry does not allow this > > behaviour. > > > > Besides if *everyone* indicated on the issue thier interest, perhaps > > something might happen. or maybe not. > > > > Geoff > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
