On 03/05/06, Alphax (Wikipedia email) [email protected] wrote:
How many articles are on your watchlist? Do /you/ check every edit that appears on your watchlist?
Until there are better facilities for managing watchlists, I don't think anyone can do that. I have close to 1000 articles on mine, and others have 5 or 10 times as many. I tend to find that using "my contributions" works better, checking any article for which my edit is not the latest.
If anyone did feel like building some watchlist management tools, here are some requests: * Create a view which shows each article in your watchlist, sorted by the most recent change (unlike the current view which can show each article several times) * Add checkboxes to the previously described view, allowing you to rapidly unselect large numbers of pages from the watch list * Add an option to remove all pages which you have not edited in the last X days, or for which none of the last Y edits have been made for you. * Allow a way of bookmarking pages without actually "watching" them. That is, to record the fact that a particular page was interesting, without actually wanting to be informed of every change to that page. *On a watchlist view, provide a link to compare the current version of the page with the last version that you edited.
Even a way to bulk delete *all* items from my watchlist would be better than nothing. So frequently I want to watch an article for a couple of days, but that's it. I end up with hundreds of articles I don't really have much interest in, but there's no way to prune them except by the very tedious process of unwatching them one at a time.
Steve
Steve Bennett wrote:
- Create a view which shows each article in your watchlist, sorted by
the most recent change
That's what the watchlist does...
(unlike the current view which can show each article several times)
If so that's a bug.
- Allow a way of bookmarking pages without actually "watching" them.
That is, to record the fact that a particular page was interesting, without actually wanting to be informed of every change to that page.
*cough* your browser has this feature *cough* ;)
-- brion vibber (brion @ pobox.com)
On 03/05/06, Brion Vibber [email protected] wrote:
Steve Bennett wrote:
- Create a view which shows each article in your watchlist, sorted by
the most recent change
That's what the watchlist does...
(unlike the current view which can show each article several times)
Err, right, what was I thinking of - how about some more options for sorting then, particularly by *my* last recent change. In other words, how relevant the item on the watchlist is, rather than simply which has been touched last.
If so that's a bug.
No, it's my confusion.
- Allow a way of bookmarking pages without actually "watching" them.
That is, to record the fact that a particular page was interesting, without actually wanting to be informed of every change to that page.
*cough* your browser has this feature *cough* ;)
Well, I don't take my browser with me everywhere :) If it was integrated into mediawiki, it could do interesting things like say how many people had updated the page since you last touched it, what changes there are, let you categorise your bookmarked pages somehow..
Steve
Some of your requests are available through edition of your monobook.js. Contributors from fr wikipedia have created javascripts to manage watchlist easilly: for example, you can remove all articles from your watchlist, or only subpages from AfD... you can also hide bots in your watchlist. You can find this there : http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Monobook/Fonctions_avanc%C3%A9es
g.
On 5/3/06, Steve Bennett [email protected] wrote:
On 03/05/06, Alphax (Wikipedia email) [email protected] wrote:
How many articles are on your watchlist? Do /you/ check every edit that appears on your watchlist?
Until there are better facilities for managing watchlists, I don't think anyone can do that. I have close to 1000 articles on mine, and others have 5 or 10 times as many. I tend to find that using "my contributions" works better, checking any article for which my edit is not the latest.
If anyone did feel like building some watchlist management tools, here are some requests:
- Create a view which shows each article in your watchlist, sorted by
the most recent change (unlike the current view which can show each article several times)
- Add checkboxes to the previously described view, allowing you to
rapidly unselect large numbers of pages from the watch list
- Add an option to remove all pages which you have not edited in the
last X days, or for which none of the last Y edits have been made for you.
- Allow a way of bookmarking pages without actually "watching" them.
That is, to record the fact that a particular page was interesting, without actually wanting to be informed of every change to that page. *On a watchlist view, provide a link to compare the current version of the page with the last version that you edited.
Even a way to bulk delete *all* items from my watchlist would be better than nothing. So frequently I want to watch an article for a couple of days, but that's it. I end up with hundreds of articles I don't really have much interest in, but there's no way to prune them except by the very tedious process of unwatching them one at a time.
Steve _______________________________________________ WikiEN-l mailing list [email protected] To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Guillom "Je sers la science et c'est ma joie" - Basile le Disciple http://fr.wikipedia.org/wiki/User:Guillom
Guillaume Paumier wrote:
On 5/3/06, Steve Bennett [email protected] wrote:
On 03/05/06, Alphax (Wikipedia email) [email protected] wrote:
How many articles are on your watchlist? Do /you/ check every edit that appears on your watchlist?
Until there are better facilities for managing watchlists, I don't think anyone can do that. I have close to 1000 articles on mine, and others have 5 or 10 times as many. I tend to find that using "my contributions" works better, checking any article for which my edit is not the latest.
If anyone did feel like building some watchlist management tools, here are some requests:
- Create a view which shows each article in your watchlist, sorted by
the most recent change (unlike the current view which can show each article several times)
- Add checkboxes to the previously described view, allowing you to
rapidly unselect large numbers of pages from the watch list
- Add an option to remove all pages which you have not edited in the
last X days, or for which none of the last Y edits have been made for you.
- Allow a way of bookmarking pages without actually "watching" them.
That is, to record the fact that a particular page was interesting, without actually wanting to be informed of every change to that page. *On a watchlist view, provide a link to compare the current version of the page with the last version that you edited.
Even a way to bulk delete *all* items from my watchlist would be better than nothing. So frequently I want to watch an article for a couple of days, but that's it. I end up with hundreds of articles I don't really have much interest in, but there's no way to prune them except by the very tedious process of unwatching them one at a time.
Some of your requests are available through edition of your monobook.js. Contributors from fr wikipedia have created javascripts to manage watchlist easilly: for example, you can remove all articles from your watchlist, or only subpages from AfD... you can also hide bots in your watchlist. You can find this there : http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Monobook/Fonctions_avanc%C3%A9es
Oh yes, there's http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_scripts on en: which has a heap of these sort of things (somewhere). I've crosslinked them.
On 03/05/06, Alphax (Wikipedia email) [email protected] wrote:
Oh yes, there's http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_scripts on en: which has a heap of these sort of things (somewhere). I've crosslinked them.
It would be cool if there was a simple way where a user could click to include all these functionalities. They're quite modular, and often don't conflict with each other. So wouldn't it be nice if you could just click to include some code, rather than copy-pasting. Personally, I find after about 3-4 functions included, my monobook.js is totally out of control. Or maybe it's possible to {transclude} subpages to make it tidier?
Yes, there would be security issues to sort out - presumably you would be including a specific version of the page, not just "the latest version".
SoC project?
Steve
The JS version of transclusion appears to be:
document.write('<script type="text/javascript" src="' + 'http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js' + '&action=raw&ctype=text/javascript&dontcountme=s"></script>');
I think it would be a brilliant idea to modularise and bring together all scripts in a consistent fashion under a WikiProject umbrella, so the editor just has to include a selection of subpages.
----- Original Message ---- From: Steve Bennett [email protected] To: English Wikipedia [email protected] Sent: Wednesday, 3 May, 2006 10:28:19 AM Subject: Re: [WikiEN-l] Watchlist feature requests (was Re: Cruft)
On 03/05/06, Alphax (Wikipedia email) [email protected] wrote:
Oh yes, there's http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_scripts on en: which has a heap of these sort of things (somewhere). I've crosslinked them.
It would be cool if there was a simple way where a user could click to include all these functionalities. They're quite modular, and often don't conflict with each other. So wouldn't it be nice if you could just click to include some code, rather than copy-pasting. Personally, I find after about 3-4 functions included, my monobook.js is totally out of control. Or maybe it's possible to {transclude} subpages to make it tidier?
Yes, there would be security issues to sort out - presumably you would be including a specific version of the page, not just "the latest version".
SoC project?
Steve _______________________________________________ WikiEN-l mailing list [email protected] To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On 03/05/06, Pete Bartlett [email protected] wrote:
The JS version of transclusion appears to be:
document.write('<script type="text/javascript" src="' + 'http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js' + '&action=raw&ctype=text/javascript&dontcountme=s"></script>');
I think it would be a brilliant idea to modularise and bring together all scripts in a consistent fashion under a WikiProject umbrella, so the editor just has to include a selection of subpages.
Can such a thing be achieved through javascript? I'm imagining something like this:
1. User makes a single modification to their monobook.js to include the module tool. 2. The module tool provides an interface such that they can select the modules that interest them 3. Modules currently selected are saved somewhere like user:Stevage/modules 4. When the user confirms, the tool retrieves the originals and writes them to something like user:Stevage/modulecode 5. Either the user, or the tool automatically adds a line which includes everything in user:Stevage/modulecode as you described above.
Feasible? Comments?
Steve
Steve Bennett wrote:
On 03/05/06, Pete Bartlett [email protected] wrote:
The JS version of transclusion appears to be:
document.write('<script type="text/javascript" src="' + 'http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js' + '&action=raw&ctype=text/javascript&dontcountme=s"></script>');
I think it would be a brilliant idea to modularise and bring together all scripts in a consistent fashion under a WikiProject umbrella, so the editor just has to include a selection of subpages.
Can such a thing be achieved through javascript? I'm imagining something like this:
- User makes a single modification to their monobook.js to include
the module tool. 2. The module tool provides an interface such that they can select the modules that interest them 3. Modules currently selected are saved somewhere like user:Stevage/modules 4. When the user confirms, the tool retrieves the originals and writes them to something like user:Stevage/modulecode 5. Either the user, or the tool automatically adds a line which includes everything in user:Stevage/modulecode as you described above.
Theoretically, yes. I thought about having a similar system, only the entire code would be written back to the monobook.js, because it's protected from other users. However, I'm not sure that it would be /practical/ to implement it without something like XUL to get the UI setup - ie. it would be a Mozilla extension.
- User makes a single modification to their monobook.js to include
the module tool. 2. The module tool provides an interface such that they can select the modules that interest them 3. Modules currently selected are saved somewhere like user:Stevage/modules 4. When the user confirms, the tool retrieves the originals and writes them to something like user:Stevage/modulecode 5. Either the user, or the tool automatically adds a line which includes everything in user:Stevage/modulecode as you described above.
Theoretically, yes. I thought about having a similar system, only the entire code would be written back to the monobook.js, because it's protected from other users. However, I'm not sure that it would be /practical/ to implement it without something like XUL to get the UI setup - ie. it would be a Mozilla extension.
This is all very sexy. But wouldn't an easy first step just to be gather the code in one set of pages first? Then users can do "manual" transclusion to begin with, and the neat interface could come later?
On 04/05/06, Pete Bartlett [email protected] wrote:
Theoretically, yes. I thought about having a similar system, only the entire code would be written back to the monobook.js, because it's protected from other users. However, I'm not sure that it would be /practical/ to implement it without something like XUL to get the UI setup - ie. it would be a Mozilla extension.
This is all very sexy. But wouldn't an easy first step just to be gather the code in one set of pages first? Then users can do "manual" transclusion to begin with, and the neat interface could come later?
Well, the French page given before does just that. But copying and pasting becomes very quickly unmanageable. What do you do when you have 30 extensions and your monobook.js doesn't compile? How do you remove one extension without breaking others? I do it by embedding big ///////////////// comments around them, but it's still a bit dicey.
Steve
Steve Bennett wrote:
On 03/05/06, Alphax (Wikipedia email) [email protected] wrote:
Oh yes, there's http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_scripts on en: which has a heap of these sort of things (somewhere). I've crosslinked them.
It would be cool if there was a simple way where a user could click to include all these functionalities. They're quite modular, and often don't conflict with each other. So wouldn't it be nice if you could just click to include some code, rather than copy-pasting. Personally, I find after about 3-4 functions included, my monobook.js is totally out of control. Or maybe it's possible to {transclude} subpages to make it tidier?
There's [[Template:Js]], which unfortunately is rather underpublicized. You use it by adding {{subst:js|Script to include}} to your monobook.js; it expands to the code posted by Pete Bartlett. You may also want to look at my own monobook.js for a slightly more compact solution:
http://en.wikipedia.org/wiki/User:Ilmari_Karonen/monobook.js
Of course, you probably shouldn't include the unprotected versions at [[Wikipedia:WikiProject User scripts]] directly. I've been thinking for a while that the project ought to provide "stable" protected versions of each script for ease of inclusion.
One possibility might be to register a dummy user account, such as User:Scripts, for this purpose, and maintain the stable versions as js subpages of that user. Besides providing shorter page names, that would guarantee that the stable versions are always protected.
I think I'll propose something like this at [[Wikipedia talk:WikiProject User scripts]]. Of course, any such stable version system requires admins to promptly merge in any valid changes, but it seems to me that there are enough active admins on that project to make this feasible. There probably also ought to be an easy way for users to list their personal forks of each script.
I think I'll sleep on it, and write up a proposal tomorrow.
On 03/05/06, Guillaume Paumier [email protected] wrote:
Some of your requests are available through edition of your monobook.js. Contributors from fr wikipedia have created javascripts to manage watchlist easilly: for example, you can remove all articles from your watchlist, or only subpages from AfD... you can also hide bots in your watchlist. You can find this there : http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Monobook/Fonctions_avanc%C3%A9es
g.
Thanks, works well (just had to modify it a bit to work on en)! So it seems my request of checkboxes to rapidly remove large numbers of watched articles already existed, but I never noticed it.
For the curious: http://en.wikipedia.org/wiki/Special:Watchlist/edit
The monobook changes above improve the functionality somewhat though.
Out of curiosity, what's the process for getting a change incorporated into the standard monobook.js?
Steve
I think you just need a sysop to change http://en.wikipedia.org/wiki/MediaWiki:Monobook.js... after getting approval from the community :)
On 5/3/06, Steve Bennett [email protected] wrote:
On 03/05/06, Guillaume Paumier [email protected] wrote:
Some of your requests are available through edition of your monobook.js. Contributors from fr wikipedia have created javascripts to manage
watchlist
easilly: for example, you can remove all articles from your watchlist,
or
only subpages from AfD... you can also hide bots in your watchlist. You
can
find this there :
g.
Thanks, works well (just had to modify it a bit to work on en)! So it seems my request of checkboxes to rapidly remove large numbers of watched articles already existed, but I never noticed it.
For the curious: http://en.wikipedia.org/wiki/Special:Watchlist/edit
The monobook changes above improve the functionality somewhat though.
Out of curiosity, what's the process for getting a change incorporated into the standard monobook.js?
Steve _______________________________________________ WikiEN-l mailing list [email protected] To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Guillom "Je sers la science et c'est ma joie" - Basile le Disciple http://fr.wikipedia.org/wiki/User:Guillom
the correct link is http://en.wikipedia.org/wiki/MediaWiki:Monobook.jshttp://en.wikipedia.org/wiki/MediaWiki:Monobook.js.(without that *%&$ dot)
On 5/3/06, Guillaume Paumier [email protected] wrote:
I think you just need a sysop to change http://en.wikipedia.org/wiki/MediaWiki:Monobook.js... after getting approval from the community :)
On 5/3/06, Steve Bennett [email protected] wrote:
On 03/05/06, Guillaume Paumier [email protected] wrote:
Some of your requests are available through edition of your
monobook.js.
Contributors from fr wikipedia have created javascripts to manage
watchlist
easilly: for example, you can remove all articles from your watchlist,
or
only subpages from AfD... you can also hide bots in your watchlist.
You can
find this there :
g.
Thanks, works well (just had to modify it a bit to work on en)! So it seems my request of checkboxes to rapidly remove large numbers of watched articles already existed, but I never noticed it.
For the curious: http://en.wikipedia.org/wiki/Special:Watchlist/edit
The monobook changes above improve the functionality somewhat though.
Out of curiosity, what's the process for getting a change incorporated into the standard monobook.js?
Steve _______________________________________________ WikiEN-l mailing list [email protected] To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Guillom "Je sers la science et c'est ma joie" - Basile le Disciple http://fr.wikipedia.org/wiki/User:Guillom
-- Guillom "Je sers la science et c'est ma joie" - Basile le Disciple http://fr.wikipedia.org/wiki/User:Guillom