On Tue, 14 Aug 2012 10:20:57 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
I agree this is an issue. Have you filled a JIRA for that? If not,
please> do it.
It's already done but I think I'm not labeling it correctly because it
hasn't had any activity since then.
https://issues.apache.org/jira/browse/TAP5-1948
Thanks! But don't forget that there's no company behind Tapestry, so the
committers pick what they want when they want. ;)
I think what you're really saying is not that Tapestry UI framework is
immature, but that it doesn't have the same number of components
out-of-the-box (not including the easily-added third-party modules) as
Vaadin.
This is it :)
This is very different from what you said originally. That's why I'm
always very concerned on using the right words and terminology, because
otherwise people will probably not understand what you're saying. ;)
Maturity is very different from number of components. Believe me, number
of components by itself is a good advantage for a framework, but it's
quite far from being a good point to choose one framework over another.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
