On 4/11/07, Philip Weaver <[EMAIL PROTECTED]> wrote:
I understand. Thanks. One of Rail's mantra is convention over
configuration. Being able to render default HTML for common types of
controls seems conventional - it seems less cumbersome. I am not
disrespecting Wicket - I appreciate Wicket but I wish that it were less
cumbersome to use for UI programmers.
tbh, i actually tried to do this in an application i was building using
wicket2.0. it worked great for prototyping things, but it did produce forms
that werent very usable because the layout was too pragmatic. sometimes you
want two text components to share a label, sometimes not. sometimes you want
two components to be in the same row, sometimes not. in the end i always
ended up going through and redoing my bean panel with regular markup and
form components because the users complained. it wouldve actually saved me
time doing it the way its usually done the first time, but i wanted to
experiment with bean panels for myself :)
just my experience.
-igor
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-user
