On Thu, 31 Oct 2013 04:10:26 -0200, Jens Breitenstein
<mailingl...@j-b-s.de> wrote:
I believe it strongly depends what you want and use from Tapestry.
For example: The BeanEditor is a great component to display something
quickly but at the very end I never used it, because you can not (or at
least I am to stupid to) control exactly the look and feel / positioning
of all fields to make a real responsive form because it lacks css
modification accross fields.
T5.3-: BeanEditor adds CSS classes based on the name of the property.
T5.4: BeanEditor adds data-* attributes based on the name of the property.
As the world and Tapestry moves more and more towards JavaScript it's
natural you loose your preview capabilities but Tapestry still allows a
detailed preview of the static positioning and responsive setup without
a running server, in contrast to JSF / GWT or others.
In short: I like the concept, still.
Thanks, Jens! That's exactly what I was trying to say, but with better
words. :)
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
