we did almost exactly the same thing at thoof. although occasionally you'll get a designer stuck on a build problem or something, it works really well. definitely the best approach in my mind.
igor.vaynberg wrote: > > so you are giving designers markup from a wicket app? why not just let > them run the app, that way they can go in and do things themselves? > > in my company out developers checkout the code and run mvn jetty to > get the app up and running with markup reloading, then they go in with > textmate or coda and tweak the markup. > > -igor > > On Fri, Jan 15, 2010 at 8:00 AM, Marek Šabo <ms...@buk.cvut.cz> wrote: >> Hi everyone, >> >> I would like to know if someone can share their experience with graphical >> templates under wicket. It's easy to provide markup code for designers, >> they >> just need to preserve hierarchy of wicket elements, right? But how do you >> cope with things like attribute modifier inside application and dynamic >> loading of other css files? Or what is the most common approach to this >> kind >> of thing? >> >> Regards, >> >> Marek >> >> --------------------------------------------------------------------- >> 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 > > > -- View this message in context: http://old.nabble.com/Templates-in-Wicket-tp27179274p27179469.html Sent from the Wicket - User 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
