Problem: Default styles are too clunky. Need to bolt a better style wrapper.
I would like to use better looking forms generated by, say, http://www.appnitro.com/ Is there some documentation, best practice or cookbook, somewhere, on MERGING styles with default Tapestry styles? The only way, right now, seems to be to reverse engineer every use-case (like form errors etc) and capture each CSS class to redefine it according to the new style. Even then, session management glue code like the hidden t:formdata can only be discovered by accident in view-source. With so much dependency on stuff showing up only after maven build in /assets/1.0-SNAPSHOT-DEV/tapestry/ ... there seems to be a lot going on to even bother creating your own look-and-feel (and also have tapestry form functionality). This would push back the project quite a bit...unless I am missing something? -- View this message in context: http://tapestry.1045711.n5.nabble.com/Better-Looking-Input-Form-tp5656603p5656603.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
