> Thanks. Is that common practice? It seems like it tightly > couples the java code with the design of the web page. > I thought the Image class was for creating dynamic images - > as that's all I've needed to use it for.
To be honest, I don't know. If you don't want to put wicket:id attributes in your images, maybe you could instead put some Javascript in a HeaderContributor that rewrites the src attributes of all your images (or all the ones of a particular css class) when the page loads. This could fix their paths while still letting their paths remain original in the raw HTML. (They wouldn't get changed because the script wouldn't get loaded.) -- View this message in context: http://www.nabble.com/Setting-up-project---images-and-stylesheets-tf4094209.html#a11680081 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
