I agree, I think this will be a constructive thread. So things that are not beautiful yet are a lack of tooling, aside from the helpful Loom plugin. I only use eclipse here, so I'm not sure if there are plugins for other IDEs.
Sometimes I wish there were more industry type examples out there, since I often find myself writing something that is overly verbose. I find myself looking at code on http://www.google.com/codesearch . Maybe a reproduction of the T4 Showcase app would make a good archetype. Maven usage used to be a problem for some, but I think most of us have gotten used to it or have worked around it. On Wed, Apr 29, 2009 at 4:19 PM, Inge Solvoll <inge.tapes...@gmail.com>wrote: > Hi! > > I have been reading the "beautiful" thread and added my opinion about > what's > great about Tapestry. It's nice to sum up why we all are so excited about > this, it obviously makes both us and the creator(s) feel good about > ourselves. But for a little while, I challenge us all to stop tapping each > others' backs and go into depth about what's not to like about our beloved > framework. > > The most obvious questions that could be asked probably have some very > obvious answers. But T5, as I see it, is all about addressing stuff that > other frameworks have given up on and create excellent implementations > rather than just looking the other way. Difficult and uncomfortable > questions should be addressed the same way. > > So: > > What are the main reasons that T5 isn't one of the "big ones", when we all > seem to agree that it is so much better than most other frameworks out > there? Why is T5 NOT beautiful? > > Hope I'm not insulting anyone, I'm a big fan too, I just think this > actually > could lead to significant insight :) > > Regards > > Inge >
