Joachim, Great tool but who cares here on the list? I should say you made a bad decision by choosing Tapestry. Tapestry users are fading and you could tell that yourself by looking at the traffic here on the list. If you had done it for say GWT or Wicket, you would have received tons of feedbacks because far too many users use those frameoworks. Above all, Howard have made numerous comments in the past (just google and you'd find them) saying there is no need for a tool in Tapestry development. So man, unfortunately your work done is to no avail to Tapestry users. Tapestry is just a framework for a few webframework religious fanatics writing demos and prototypes at the labs. Or writing applications that are low volume and meant for low profile organisations.
My advice? Just dump it and embrase a more serious and puposeful frameworks like Wicket. This is a framework used for serious and mission critical stuffs. Not just another over-engineerd framework just for the sake of "fun". And as the mantra for Tapestry goes, after the fun you pay a severe and painful price when there is a major release in the future. Wicket, GWT, Flex are all even more fun to work with. But the folks behind them are truly genuises and try to inflict minimal pain at any major release. I hope those reading would look farther than labeling me a Troll. The fact of the matter is I always hit on the truth head-on but unfortunatley, the truth is sometimes hard to swallow for some people. Joachim, if you drop Tapestry you won't be the first. I heard a rumor even Jesse Kuhnert, one of Tapestry's elite commiter, has also dumped Tapestry. If you don't believe me just check on this list and look for the last time he participated. So don't feel bad to drop Tapestry. Yours friendly, Rob On Mon, May 5, 2008 at 10:51 AM, Joachim Van der Auwera < [EMAIL PROTECTED]> wrote: > equanda, a open source project to generate a JEE application based on a > domain model, has released version 0.9. > > equanda generates the EJB3 access objects with possibility for powerful > declarative constraints and added programmatic constraints. > equanda also generates a tapestry5 based user interface with powerful > options for customizations. > All this (and quite a few other bots and pieces) are generated at compile > time from a XML description of the data and constraints. The customizations > remain intact in the generation process. > > This is the first useable release of equanda since the project started > (though the user interface still lacks features). > > Notable changes include : > - initial tapestry5 user interface > - type handling in field templates now also interprets subtags > - filter string per table > - improved form traversal in user interface, which also auto switches to > the next tab > - allow templates to define extra key-value pairs, possibly overwritten by > user > - fields named "Reference" or "Description" should automatically be marked > as is-reference or is-description > - generate UML and OWL from the domain model > - Improve xml reading/handling in domain model parsing code > - add selectors on proxies > - create archetype for empty equanda project > - tapestry5 accordion component > - tapestry5 tabs component > - tapestry5 FormTraversal component > - add equandaReset() method in proxies to revert the state to the database > values > - tapestry5 create "manifest" binding prefix > - Should allow a table type (in the inheritance tree) to be impossible to > create > > For more information, visit the project web site : http:// equanda.org/ > > -- > Joachim Van der Auwera > http://blog.progs.be/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
