svenmeier wrote: > > Who want's to depend on google just to load other project's javascript > files? > I can't imagine anyone wanting to load javascript from a foreign URL > just to do some jqueries: > - you must be online > - what about reliability of service? > - NoScript will bark > > Why put different javascript libraries into a single project? > This idea seems to be valuable for some javascript on an html page, but > IMHO it's not a modular solution appropriate for Wicket. > We already have wicketstuff projects for scriptaculous, dojo and gmap(2) > - they provide the required javascript files. > If someone needs it, we can setup wicketstuff-jquery or whatever similar > to wicketstuff-prototype. >
To add to that, I don't see the Google load being acceptable for most commercial projects. For legal reasons, being dependent on an external company's hosting of a core javascript library usually won't fly (privacy concerns, legitimate or not, are a big deal these days). Also, as someone mentioned above, intranet based apps might not work either. -- View this message in context: http://www.nabble.com/Wicket-JavaScript-libraries-and-Google-Ajax-libraries-API-tp17507132p17520426.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
