Yep, I know. Have been working with Wicket for a few months now, so I
pretty much walked into the same issues your stating here. That's why we
plan to do something about it in 1.1.
Eelco
Gili wrote:
BTW: The reason this is a big deal is previewability. Currently I
have to maintain two copies of my CSS directory (and associated
images): one in webapp and one in the classpath. It makes development
rather difficult and error-prone.
When editing my Page, I need a CSS directory in the classpath.
When testing the application I need a CSS directory in webapp.
Gili
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
