On Sat, 11 Aug 2012 15:30:31 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
I've never used Vaadin but what I can say about it after I visited it's
website is that it's much more UI component rich when compared to
tapestry but it has no IoC support. Of course the lack of UI components
in t5 can be mitigated by using external libraries\frameworks but I'm
comparing based on the OTB features
From Tapestry side:
* Using HTML, CSS and JavaScript directly.
* Live class reloading
* You can change almost anything in the framework without needing to touch
its source: service override, advice, decoration.
* It's very easy and quick and painless to write new components. In GWT
and Vaadin, creating your own component which uses JavaScript is actually
discouraged: see the bottom of
https://developers.google.com/web-toolkit/doc/latest/DevGuideUiCustomWidgets.
My argument here is that there's no framework that will provide you 100%
of your component needs, so you'll eventually need to write your own and
you'll hope you have chosen a framework that makes it easy.
* Very high source code quality and test code coverage.
* You can use client-side-focused frameworks like GWT on the top of
Tapestry if you want or need. Someone has already done GWT on Tapestry.
Google it.
And don't forget that Vaadin is basically GWT plus some server-side stuff.
that requires no efforts to import.
How much effort is needed to get some third-party package like
tapestry-jquery to work in Tapestry? Just add it to the classpath. If use
use some dependency management tool like Maven, Ivy or Gradle, just add
the dependency to the configuration and the tool will do it for you. If
not, download the JAR and configure your project to include it in your
classpath. It couldn't be easier or faster.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
