Juergen Donnerstag wrote:
[ ... ] I wonder if downloading (and locally caching) the same js script (because of different urls) twice or may 3 or 4 times, realy is such a big problem.
It may not be an issue at all, and I'll probably try it first to see. Maybe I'll just get a few JS warnings about redeclared vars and that's it. There's something inelegant about it, but I suppose if it works, that trumps any aesthetics...
Hmm, did you mention references (or alias) already? What about an approach where the re-usable components referes to a js reference and the application throws an exception if the reference has not yet been defined. This way each re-usable component may define its own references with there own names and while plumbing the components to an application, your application must provide a mapping from alias to js filename.
I hadn't thought about that. For my own internal component, that should be fine. I think it would break the encapsulation for a component meant for distribution. But I really am starting to believe that there really can be no ideal solution to this.
In any case, folks, thanks for all the discussion. If the project schedule allows me the time to do this, I will try several techniqes, and report back my results.
-- Scott ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
