Em Wed, 18 Feb 2009 16:25:53 -0300, Luther Baker <lutherba...@gmail.com>
escreveu:
Ok - one last convincing attempt :) and then I'll let it go.
My last one too. :)
Like many developers, my current situation is to work with a designer.
To me, one of Tapestry strengths is its template language: HTML plus some
attributes (t:type, t:id, etc). On the other hand, using a <t:parameter>
block needs Tapestry knowledge, and designers don't need nor have them. ;)
In my case, I think I incorrectly started using BeanEditForm for one of
the edit screens in this app and by default, it places the SUBMIT button
in the bottom left of the bright yellow box.
To begin with, you can use BeanEditor. Second, all Tapestry component
styles are made through CSS, so you can easily override them writing your
own CSS file(s).
out of the box, they do not render t:Parameter's consistently.
They're not consistent because they do very different things.
Ah well ... did that spiel convince you ;)
No! ;) hehehe
Up and coming frameworks like Grails auto-generate Show, List and Edit
screens for the developer -
So does Tapestry CRUD: www.arsmachina.com.br/project/tapestrycrud (current
development state is way better than the documenation shows now).
At any rate, I'm not suggesting we change anything - I think I'm making a
case to write my own first component(s)!
That's other of T5 strengths: writing components is very easy.
Good food for thought!
Different views, nice discussion. :)
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
