i apply the same practice as igor. it works great for both sides, dev and des. once des already has the html model, dev creates the first integration to the object-tree, providing feedback to des, so dom-tree follows the same coherence (in case needed to correct some parts), and following are just test-error-correct cycles done by des at local environments running the app. .
On Tue, Feb 19, 2013 at 11:18 PM, Igor Vaynberg <igor.vaynb...@gmail.com> wrote: > they do not need to restart their local server to see changes. wicket > automatically reloads html/css/js/etc. only changes to java files that > cannot be hot-swapped require a server restart. but your designers > wont be changing java files will they? > > -igor > > On Tue, Feb 19, 2013 at 12:44 PM, eugenebalt <eugeneb...@yahoo.com> wrote: >> Our designers say they don't want to run on the server. >> >> It's a lot of effort to restart the server to test every tweak; also, >> they're not familiar with the intricacies of our IDE and server. It's a lot >> more productive for them to have a direct set of files they can test in IE, >> which is how they've been working all along. >> >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/The-best-way-for-designers-and-Wicket-developers-to-collaborate-tp4656560p4656570.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 >> > > --------------------------------------------------------------------- > 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
