UW is probably one of the worst "offenders" of this. Granted, some are needed to work with the older versions, but any that are in at least 1.17 should be cleaned up
Like the datepicker files, among many others :)
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Krinkle | T28306 Cleanup extensions that include jquery (and common plugins) themselves | |||
| Resolved | None | T31099 Remove all jquery/js files that already exist in core |
Tipsy is in core, and has been for a while. I guess that's another candidate to strip from UW :). Not sure what the difference between version 1.0.0a and version 1.0.0a+ is. Maybe someone could tidy that up and remove from UW? Even if the UW version replaces the core one
Spinner can also go away with 1.19 (it's in phase3)
jquery.autocomplete could probably be pulled straight into core
ibaker wrote:
While we're at it, the JS wikitext parser is another good candidate for something to roll into core. It's in the jQueryMsg extension (though that version is a little out-of-date), but should really not be an extension at all.
(In reply to comment #3)
While we're at it, the JS wikitext parser is another good candidate for
something to roll into core. It's in the jQueryMsg extension (though that
version is a little out-of-date), but should really not be an extension at all.
{{BeBold}} && {{JFDI}} :D
Seems relatively simple and standalone
As long as files are svn copied in, all should be well
neilk wrote:
Yeah, also I want to use some libraries from UW in the VisualEditor thing so I'm moving quite a few of them out right now.
Reedy: svn copy and not svn move?
(In reply to comment #5)
Yeah, also I want to use some libraries from UW in the VisualEditor thing so
I'm moving quite a few of them out right now.Reedy: svn copy and not svn move?
As per IRC, svn move is fine (as it's svn copy && svn delete)
(In reply to comment #3)
While we're at it, the JS wikitext parser is another good candidate for
something to roll into core. It's in the jQueryMsg extension (though that
version is a little out-of-date), but should really not be an extension at all.
See bug 32979, seems we have a core module dependent on extensions :(