Also Tapestry is very lenient in the approaches to problems you can take. You never feel artificially confined. Another great point is the component orientation which makes for a much more natural flow of coding compared to pure MVC. Though on the surface it is also page oriented, you automatically start to think differently about webapplications, since the pages are more or less only functional units or "meta-components". I usually start now by thinking about what functional behaviour I need, create my components and mixins and assemble the functionality into pages which get shorter with every iteration. Everything about tapestry feels clean. When you start to do ugly hacks, you probably got it wrong in design. If you think and read up a bit more you usually end up with half the code or even less and simple one at that.
The only drawback of Tapestry 5 is, that you might get spoiled for other frameworks, since they tend to feel clumsy compared to the elegant approach Tapestry takes. 2009/4/26 Luther Baker <lutherba...@gmail.com> > I'll chime in and say the template engine (html template and Java class > integration), the page pooling strategy and OO perspective that comes along > with it, native hibernate integration and the clever state management > between requests are all unique, out of the box and really help define the > Tapestry experience. > > -Luther > > > On Sun, Apr 26, 2009 at 9:23 AM, Hugo Palma <hugo.m.pa...@gmail.com> > wrote: > > > I would like to add to what everyone else has pointed the excelent > > error reporting. I'm still to find another framework that has such > > self explanatory error reporting. It's a real time saver when trying > > to figure out why things aren't working. > > > > On Thu, Apr 23, 2009 at 7:12 PM, Sebastian Hennebrueder > > <use...@laliluna.de> wrote: > > > Hello, > > > > > > I am working on an article evaluating Tapestry 5 in details. The > article > > is > > > part of an article series on my website http://www.laliluna.de on web > > > technologies and frameworks. Apart from a large article on > technologies, > > > there is a detailed test of the Stripes Framework. > > > > > > One chapter in the evaluation is going to show features or concepts > which > > > are very beautiful, unique or somehow special for this framework. In > this > > > chapter, I would like to integrate > > > feedback from the community using the framework. I did this as well > with > > > Stripes > > > ( > > > http://www.mail-archive.com/stripes-us...@lists.sourceforge.net/msg02294.html > > ) > > > > > > This is why, I would like to ask you for your opinion. > > > > > > What is your favourite feature or concept of Stripes, what is unique as > > > compared to other things, what is an eye catcher? > > > > > > -- > > > Best Regards / Viele Grüße > > > > > > Sebastian Hennebrueder > > > ----- > > > Software Developer and Trainer for Hibernate / Java Persistence > > > http://www.laliluna.de > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
