One of the great features of wicket is the ability to allow a developer to focus on the Java behind the pages while a designer can work on the HTML/CSS. The object oriented nature of a wicket page complicates this somewhat. Our pages are broken up into many panels each with their own code and HTML. The designer in this case doesn't get an overall view of the page but rather focuses on the pieces. This is fine; however, we have gone one step further and created quite a few composite controls (i.e. text field with label, input, error indicator, hint, etc). These controls let us write a lot less HTML which makes things more maintainable and consistent. However, the downside is that the designer can't see them outside of a running wicket application. Is anyone else doing this? If so, has anyone put in place a strategy to allow for composite controls while still still allowing a designer to focus HTML/CSS? We have been thinking about perhaps creating a preprocessor that would expand our composite controls at design time to allow the designer to see the resulting markup. Any thoughts on how we might accomplish this? We are using Wicket 1.4.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Separate-Development-and-Design-tp4656132.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
