On Tue, Nov 23, 2010 at 6:06 PM, Piero Sartini <li...@pierosartini.de> wrote:
> Yeah - you could do this, but a lot of problems will arise. You don't > want to do this, I've tried it. > In the end you give up the advantages of components and gain nothing. > And its still more complex to use than in an action based framework, > especially if it comes to AJAX. I would really like to have a more direct experience but what can I say is that when you mix and match javascript with html code all become pain... As I can see from the screencast in the play framework ... that not seem a clean way. > Oh.. of course. Tapestry is a dream of productivity compared to JSF. > But we are talking about action based approaches here, more concrete > about Play! > And sure I have to worry about life cycles.. I had to in every single > tapestry app I've built. You need to worry about component IDs, about > life cycles and how your data flows through them. It's all coming > together in an elegant way - but you need to worry a lot more within > the "component" world. I really don't see this... maybe the binding mechanism is what confuse some but that's not so hard to come around... > Agreed - but sometimes you need to prototype quickly. I prefer to be > able to "upgrade" the prototype to the final app, without completely > rewriting it. I found it difficult to deliver quick changing > prototypes in tapestry. Customizing the UI costs too much time, > especially if your available web developers dont have a clue about > tapestry. And most of them dont ;) I think I should try play if it let you prototype quicker then T5 but from what I can see from the screencast (again) that seems not the case... > Agreed. On the other hand experience has shown that its not worth to > think about all possibilities the future may bring. Solve the problem, > solve it fast. > If the application needs to get more complex in 2 years, think about > how to solve this complexity then. Else you are in danger to > over-architect your application from the beginning. The result is much > more work than needed. That's right. Indeed. But has nothing to do with Tapestry nor play not the_new_framework_around > Just to say it again.. I love tapestry. I like the clean code and the > endless possibilities. But _my_ reality right now is that it is not > the best choice for some of _my_ projects. Thats sad, but I am not too > religious about the tools I use. Wise... :) Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
