Exactly because this is the kind of requests we're going to get, I think it
makes sense not to have any library bundled by default, but have a
centralized handling for libraries, e.g. one extension asks for latest
jQuery and latest YUI and MW loads them, another extension asks for jQuery
only and so on.
It can be similar or simply using Google lib loader:
http://code.google.com/apis/ajaxlibs/documentation/
Thank you,
Sergey
--
Sergey Chernyshev
http://www.sergeychernyshev.com/
On Wed, Apr 22, 2009 at 12:28 PM, Brian <Brian.Mingus(a)colorado.edu> wrote:
Many extensions are now using the Yahoo User Interface
library. It would be
nice if mediawiki included it by default.
On Wed, Apr 15, 2009 at 3:05 PM, Brion Vibber <brion(a)wikimedia.org> wrote:
Just a heads-up --
Michael Dale is working on some cleanup of how the various JavaScript
bits are loaded by the skins to centralize some of the currently
horridly spread-out code and make it easier to integrate in a
centralized loader so we can serve more JS together in a single
compressed request.
Unless there's a strong objection I'd be very happy for this to also
include loading up the jQuery core library as a standard component.
The minified jQuery core is 19k gzipped, and can simplify other JS code
significantly so we can likely chop down wikibits.js, mwsuggest.js, and
the site-customized Monobook.js files by a large margin for a net
savings.
If you've done browser-side JavaScript development without jQuery and
wanted to kill yourself, I highly recommend you try jQuery -- it's
sooooo nice. :)
-- brion
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l