AT 2010-09-06 18:26, Roan Kattouw wrote:
2010/9/6 Maciej Jaros<egil(a)wp.pl>pl>:
At 2010-09-04 05:59, Trevor Parscal wrote:
* Allows minification of JavaScript and CSS.
Will JS/CSS developers/testers be able to disable this in preferences?
Like I said in my previous reply to Aryeh, you can use debug mode.
This is a feature we probably should've mentioned in the OP.
This is good, but an option set in preferences would be more efficient
when debugging more then one page. But if it would read _GET or _COOKIE
then it would be fine for me, too.
* Help writing new code! While wikibits.js is now also
known as the
"mediawiki.legacy.wikibits" module, the functionality that it and
basically all other existing MediaWiki JavaScript code provide is being
deprecated, in favor of new modules which take advantage of jQuery and
can be written using a lot less code while eliminating the current
dependence on a large number of globally accessible variables and
functions (see
http://www.mediawiki.org/wiki/ResourceLoader/JavaScript_Deprecations )
Will jQuery
be available for older skins too? If so won't it cause
problems for mobile browsers? AFAIK mobile jQuery will not be ready for
at least next few years.
Yes, jQuery will be served on every page load. However, the (short)
startup script that contains the module registration information and
loads the jquery and mediawiki modules checks the browser version for
compatibility before doing the latter. Currently the only browser it
considers incompatible is IE<6, but this list should probably be
extended to include other stone age browsers and mobile browsers. For
the latter, we can even do the redirect to the mobile site in that
place so we don't load a ton of JS before deciding to redirect people.
OTOH, it might be nice to put a mobile redirect script in the<head>
so the browser doesn't have to render the entire page before it hits
the redirect script.
That seems like a good idea. I've just found some data about jQuery tests:
http://jquerymobile.com/gbs/
As seems I was a little over pessimistic about jQuery for mobile
devices. None the less you can use the table on the page for
redirections. I think everything below B should be redirected to mobile
version. B might be left on monobook and A should work fine with any
skin (or least surrvive).
I'm asking
here because those that make gadgets (well me at least ;-))
still try to make them work on Vector and Monobook.
That's one of the objectives here: to provide a common base library
that everything in MW can build on, regardless of skin or whatever. To
that end, we started serving jQuery on every page on Wikimedia wikis
last week, and we already did so in trunk ($wgJQueryOnEveryPage) for a
few months IIRC.
Cool. Just announced it on pl.wiki news page.
Sorry for not
being very enthusiastic ;-). I see this as solving some
problems but creating new ones too. Not really complaining here, I think
minification is really needed now to get Wikimedia sites loading faster.
Which
problems would this introduce? The ones you mentioned in this
post have either already been solved or are trivially solvable.
I fear mainly that there will be reproduction issues and I'm probably
just a bit superstitious ;-). I'm also a bit worried how current various
loading mechanism will accompany new ones.
Regards,
Nux.