really? because we have quiet the opposite experience. we take a wireframe prototype, build it, and have the designer go in afterwards and pretty it up. with only a couple of hours of wicket-related training the designers know what to touch and what not to touch.
-igor On Tue, Oct 27, 2009 at 9:15 PM, John Armstrong <siber...@siberian.org> wrote: > Its amazing what designers can screw up :) > > Design can have a huge impact on code. This peaceful co-existence can > really only occur if you let the designers go first. If you start with > wicket you will either A) tell your designers to go to h*ll daily or > B) spend hours and hours re-factoring to meet their 'whims'. > > The separation of html/code is wonderful in wicket and a key reason I > use it and advocate for it but its no substitute for good planning and > a 'design first' mentality. > > John- > > On Tue, Oct 27, 2009 at 8:18 PM, Dave B <d...@davebolton.net> wrote: > >> While my Wicket usage is very basic at the stage, one of the >> attractive parts is the code and logic is completely separate to the >> layout. So your designers can do all the fine tuning and magic >> without screwing up your work. >> >> Cheers, >> Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
