wierd idea: i wonder how hard it would be to create a tiny stripped-down eclipse or netbeans that's easy for designers to do nothing but wicket page viewing and simple html/css editing in...
Mathias P.W Nilsson wrote: > > Thanks. > > I used this a while but after multiple markup inheritance I just didn't > see the point because the markup don't look like in runtime anyways. > > After reading Wicket In Action I realized that for this to work properly > you'd have to create a lot of <wicket:remove> tags. > > Very often you will keep the images outside the container in a shared file > server or something like that and have tomcat, apache or a servlet to > serve the static files. This will not work if the designer just opens the > html file in a browser. > > I would very much value your opinion in how to avoid this. A css designer > may not even have eclipse, netbeans or any other programming IDE rather > some other tool for css:ing. So stopping and starting tomcat, jboss would > be out of the question. > > How do you solve this? > > > -- View this message in context: http://www.nabble.com/Question-on-markup-and-wicket-page-tp19542131p19543954.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
