This page is currently inactive and is retained for
historical reference. Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the
village pump.
Piles of code
Places that we might mine for interesting and/or useful bits of code. Please anotate the following as you review them. This is from the June 23 2005 database dump, listing all the page names with .js in them, excluding the other skins versions of monobook.js.
User:Poccil/Schooltables.js - valuable - doesn't look like code I've seen before. Should be investigated further.
JesseW 23:48, 29 August 2005 (UTC)
Is for personal use; it reads a file on his computer. The FSO code is nice to have, though.
raylu 05:42, August 31, 2005 (UTC)
I wouldn't think we really want ActiveX security risks here. As much as possible, we're looking for cross-browser scripting.
jnothmantalk 01:26, 7 November 2005 (UTC)reply
User:Tom-/mediawiki.js - contains only the line: document.getElementById("ca-delete").getElementsByTagName("a")[0].accessKey = ""; - which should probably be added to
Techniques
User:Lupin/fixnew.js - change ip addresses into contribs links (eg used to be useful on
Special:Newpages, but now mediawiki does that anyway so it's obselete on that page)
Quarl's pages, with more current(?) versions
here. Valuable An astonishingly productive writer of code, which we should examine and include in the script library.
User:Alphax/monobook.js - Popups, godmode-lite, add purge tab, add section 0 tab, add generic tab, add generic tab for use as a menu, close AFD, 1-click talk page messages, funky date manipulation stuff (start thread, week old AFD page, live clock (client based)), toolbox link adding, show/hide AFDs, force edit summary, text replacement, make clicking on non-existent talk pages from the content page auto-start a new section, add a history link to the new messages box
I have added a lot of extra JS code since this was posted. If you want the status bar/title bar script, just copy and paste the first four or five lines of the file (to the document.title line), and ignore the rest of the code. Andrew(
My talk) 20:05, 20 July 2006 (UTC)reply
User:Lupin/monobook.js - removeAccessKeys (somewhat redundant), subject nag (ignore own userspace, but don't allow blank summaries or summaries just consisting of automatically generated section titles otherwise), the evaluator, an extremely useful javascript debugging tool
User:Omegatron/monobook.js - I have a thing to fix dashes (en,em,minus), fix units ("43KHZ" → "43 kHz"), and add an unwatch link after every article on your watchlist
User:Zocky/PicturePopups.js - "Picture Popups for Wikipedia" - I've been using this for a few weeks now, and now I don't think I could live without it. This is definitely worth a try. ~Mr Inky · (
T@C) 22:17, 8 June 2006 (UTC)reply
Create a tutorial/walkthrough of how to set up scripts and how to get started writing your own.
can we please get on this task asap!
ALKIVAR™ 19:17, 8 November 2005 (UTC)reply
Unless you know javascript, I think that this will just consist of "Find a nice script somewhere and copy it/follow the instructions for installing it". We don't have any sort of generic framework that a non-programmer can use to install or create scripts as far as I know.
Lupin|
talk|
popups 01:07, 9 November 2005 (UTC)reply
Colorizer:
http://blogs.applibase.net/prasad/downloads/jscolorizer/jscolorizer.html (needs a few tweaks to be perfectly set up for the wiki, though: remove the >pre> tags, put a single space at the beginning of every line. Somebody want to make these minor changes and host it on their webspace?).
CHANGES: Thanks for putting up the requirements,
I have made the required changes, so now you can get colorized code with/without <pre> tags, you can select each line indentation.
Thanks so much for making the changes I requested! It is much better! If I may, I'd like to request one other addition - a way to replace the br/ tags with real newlines; that way the output won't all end up on one line. Just replacing them won' work, as closing font tags are put after them. But if you replace all of them, then replace font newline combinations with newline font - it works. Thanks again for responding! - Let me know if I should put this somewhere else. (Copied to the linked blog).
JesseW, the juggling janitor 23:16, 28 October 2005 (UTC)
Goals
Provide a central store of user scripts
Make it easy for people to use user scripts
Create a plugin system for user scripts
If you would like to help, please inquire on the
talk page and also see the to-do list there.
This page is currently inactive and is retained for
historical reference. Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the
village pump.
Piles of code
Places that we might mine for interesting and/or useful bits of code. Please anotate the following as you review them. This is from the June 23 2005 database dump, listing all the page names with .js in them, excluding the other skins versions of monobook.js.
User:Poccil/Schooltables.js - valuable - doesn't look like code I've seen before. Should be investigated further.
JesseW 23:48, 29 August 2005 (UTC)
Is for personal use; it reads a file on his computer. The FSO code is nice to have, though.
raylu 05:42, August 31, 2005 (UTC)
I wouldn't think we really want ActiveX security risks here. As much as possible, we're looking for cross-browser scripting.
jnothmantalk 01:26, 7 November 2005 (UTC)reply
User:Tom-/mediawiki.js - contains only the line: document.getElementById("ca-delete").getElementsByTagName("a")[0].accessKey = ""; - which should probably be added to
Techniques
User:Lupin/fixnew.js - change ip addresses into contribs links (eg used to be useful on
Special:Newpages, but now mediawiki does that anyway so it's obselete on that page)
Quarl's pages, with more current(?) versions
here. Valuable An astonishingly productive writer of code, which we should examine and include in the script library.
User:Alphax/monobook.js - Popups, godmode-lite, add purge tab, add section 0 tab, add generic tab, add generic tab for use as a menu, close AFD, 1-click talk page messages, funky date manipulation stuff (start thread, week old AFD page, live clock (client based)), toolbox link adding, show/hide AFDs, force edit summary, text replacement, make clicking on non-existent talk pages from the content page auto-start a new section, add a history link to the new messages box
I have added a lot of extra JS code since this was posted. If you want the status bar/title bar script, just copy and paste the first four or five lines of the file (to the document.title line), and ignore the rest of the code. Andrew(
My talk) 20:05, 20 July 2006 (UTC)reply
User:Lupin/monobook.js - removeAccessKeys (somewhat redundant), subject nag (ignore own userspace, but don't allow blank summaries or summaries just consisting of automatically generated section titles otherwise), the evaluator, an extremely useful javascript debugging tool
User:Omegatron/monobook.js - I have a thing to fix dashes (en,em,minus), fix units ("43KHZ" → "43 kHz"), and add an unwatch link after every article on your watchlist
User:Zocky/PicturePopups.js - "Picture Popups for Wikipedia" - I've been using this for a few weeks now, and now I don't think I could live without it. This is definitely worth a try. ~Mr Inky · (
T@C) 22:17, 8 June 2006 (UTC)reply
Create a tutorial/walkthrough of how to set up scripts and how to get started writing your own.
can we please get on this task asap!
ALKIVAR™ 19:17, 8 November 2005 (UTC)reply
Unless you know javascript, I think that this will just consist of "Find a nice script somewhere and copy it/follow the instructions for installing it". We don't have any sort of generic framework that a non-programmer can use to install or create scripts as far as I know.
Lupin|
talk|
popups 01:07, 9 November 2005 (UTC)reply
Colorizer:
http://blogs.applibase.net/prasad/downloads/jscolorizer/jscolorizer.html (needs a few tweaks to be perfectly set up for the wiki, though: remove the >pre> tags, put a single space at the beginning of every line. Somebody want to make these minor changes and host it on their webspace?).
CHANGES: Thanks for putting up the requirements,
I have made the required changes, so now you can get colorized code with/without <pre> tags, you can select each line indentation.
Thanks so much for making the changes I requested! It is much better! If I may, I'd like to request one other addition - a way to replace the br/ tags with real newlines; that way the output won't all end up on one line. Just replacing them won' work, as closing font tags are put after them. But if you replace all of them, then replace font newline combinations with newline font - it works. Thanks again for responding! - Let me know if I should put this somewhere else. (Copied to the linked blog).
JesseW, the juggling janitor 23:16, 28 October 2005 (UTC)
Goals
Provide a central store of user scripts
Make it easy for people to use user scripts
Create a plugin system for user scripts
If you would like to help, please inquire on the
talk page and also see the to-do list there.