On Sun, 12 Aug 2012 10:00:53 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
I'm mainly raising this discussion because I believe tapestry could make
use of the idea of using a mature UI framework (such as Vaadin or GWT)
instead of reinventing the wheel on that part and rather focus on what
it's REALLY great at, the server side services (IoC for example as Taha
mentioned)
Wow, you've just said that Tapestry, which is a web framework, should drop
the web framework (which is multipage), replace it with Vaadin/GWT (which
are single page) and focus on the IoC part only. I'm sorry, but I think
you're at least very confused about the above opinion.
In addition, as it was already mentioned in this thread, you're focusing
too much on a single bullet point (number of ready to use client-side
components) and forgetting about the big picture. Vaadin and GWT have to
provide lots of built-in components because they're hard and
time-consuming to write (at least when compared to Tapestry). In other
words, your *not* supposed to write your own components in 95% of the
situations (numbers made up by me, of course).
In Tapestry, writing a component is a very trivial thing to do. In
addition, you're using HTML directly, which isn't the case of Vaadin/GWT,
so you can very easily and quickly get some JavaScript
component/widget/whatever from jQuery UI, Scriptaculous or other projects
and turn it into a component when that's not provided by some project like
Tapestry-jQuery or ChennileKit.
Or even may be we, tapestry users or some of us, could find this more
suitable to our projects like *lukaszkaleta* mentioned about his project
consisted on Vaadin and google guice as an IoC. (but in our case it would
be tapestry ioc of course)
Now you've said something I agree: there's no silver bullet. No solution
will be the best for all problems (nor any framework for all kinds of
webapps). There are projects in which Vaadin/GWT will be a better choice
than Tapestry and vice-versa.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
