Well, let me put it this way: before you couldn't even get this
working *at all*. Now you can at least declare these images in the
Application manually. Sure it isn't perfect but at least now there is
a workaround.
If you want that second half (automatic exporting of
application-scoped resources) then that's a whole different
discussion. It's simple an ease of use issue as far as I'm concerned
(although it would be nice to fix it).
it is not a workaround.
Nobody and i really think nobody is going to add all the static
resources the datepicker is needing in there application including you
This needs to be fixed.
Jon suggested using an XML configuration file. I suggested adding
a method to components (I mistakenly said Page but I meant for all
components) that allows them to return a list of all resources they
wish to export. etc..
Yes but you still need to know WHAT components what to contribute.
so this must be configured/registered somehow.
i don't want xml either. just a simple property file.
johan
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
