Hi all,
I have a question to all recipients regarding the user interface (screen layout) of Recent Changes and Watchlist pages (perhaps also PageHistory).
It is, that I proposed to introduce *one new link* for lines showing watched pages, which are currently marked in bold. The current screens show the links (diff) (hist) and I propose to introduce a thrid one: (diff-to-LVR) LVR = last visited revision.
Wish to receive your proposals for a changed screen layout ......
- how would *you* arrange the screens - proposal for the short text for such a link ? (diff-to-LVR) is not neat enough
Tom http://meta.wikipedia.org/Enotif http://bugzilla.wikipedia.org/show_bug.cgi?id=454 http://bugzilla.wikipedia.org/show_bug.cgi?id=536 (For pages on watchlist save last seen version number) and http://bugzilla.wikipedia.org/show_bug.cgi?id=603 (delete/undelete cycle doesn't preserce old_id)
That sounds like a great idea. "LVR" is probably fine as the link text; it isn't obvious what it means, but you just click on it to find out.
One issue: how would the watchlist store the "last visited revision"? A revision doesn't get a version number until it isn't the most recent one anymore. A hackish way to work around that limitation is to have the watchlist store the version number of the ''previous'' revision. I don't know what to do if LVR is the first version of the page.
Another idea: have the link greyed out in the case where there's only been one revision since LVR, since then it's just the same as "diff".
On Sat, 26 Feb 2005 20:58:50 +0100, Thomas Gries mail@tgries.de wrote:
It is, that I proposed to introduce *one new link* for lines showing watched pages, which are currently marked in bold. The current screens show the links (diff) (hist) and I propose to introduce a thrid one: (diff-to-LVR) LVR = last visited revision.
David Benbennick wrote:
That sounds like a great idea. "LVR" is probably fine as the link text; it isn't obvious what it means, but you just click on it to find out.
"LVR" is incomprehensible.
One issue: how would the watchlist store the "last visited revision"? A revision doesn't get a version number until it isn't the most recent one anymore.
You might want to brush up on the development branch; every revision now gets a permanent version number when it's created.
-- brion vibber (brion @ pobox.com)
On Saturday, February 26, 2005, at 01:58 PM, Thomas Gries wrote:
Wish to receive your proposals for a changed screen layout ......
- how would *you* arrange the screens - proposal for the short text for such a link ? (diff-to-LVR)is not neat enough
I like the current setup on Meta (why is it different than the setup on en?); this link could be added in before the other two: * (chng) (diff) (hist) . . m [[page name]]; ti:me . . [[User:]] ([[User talk:]]) (edit summary)
I don't think it really matters what the short text is. Other than the nipple, no interface is intuitive; "incomprehensible acronym" or not, editors will learn what it does by clicking the link, as they have done for every other feature of MediaWiki. A four character acronym would be nice just for symmetry, that's why I chose "chng".
How will this affect server performance? My watchlist is refreshed half a dozen times on a day that I'm not working on Wikipedia, ten times as often on a day that I am. Even if you only store the read state for items in the watchlist, and not all visited pages, that's still over 500 articles (for me).
Those reservations aside, I am in favor of this feature, especially if it is opt-in by the users. I read a forum that stores read states on every thread, and it makes a world of difference in usability.
Ben
Ben Brockert schrieb:
Wish to receive your proposals for a changed screen layout ......
- how would *you* arrange the screens - proposal for the short text for such a link ? (diff-to-LVR)is not neat enough
I like the current setup on Meta (why is it different than the setup on en?); this link could be added in before the other two:
- (chng) (diff) (hist) . . m [[page name]]; ti:me . . [[User:]]
([[User talk:]]) (edit summary)
How will this affect server performance? My watchlist is refreshed half a dozen times on a day that I'm not working on Wikipedia, ten times as often on a day that I am. Even if you only store the read state for items in the watchlist, and not all visited pages, that's still over 500 articles (for me).
Thank you for your comments.
Some quick answers:
a) Only 1 update takes place: if your watched page X is changed by somebody else, this notificationtimestamp (= after your last-visit time) is kept in the table watchlist and [optionally, the ENotif is mailed to you (with the link "diff-to-LVR") - this is why I gave the flag the name]. There are no further updates necessary, i.e. there are no further updates to the entry of your watched page X in the database.
b) When you actually revisit the page X, a second update of the watchlist table is necessary to reset the notificationtimestamp. The page X is still kept on your pagelist, but no longer marked with "updated since your last visit". Your visit to the page automatically re-enables the ENotif, so that you will receive an ENotif again on a further changes of somebody else but you, which very suppress - ENotif sends only one mail on the first change.
T.
Ben Brockert wrote:
I like the current setup on Meta (why is it different than the setup on en?);
It's not. You might have one account configured with "enhanced recent changes display" and the other not?
-- brion vibber (brion @ pobox.com)
On Sunday, February 27, 2005, at 03:15 AM, Brion Vibber wrote:
It's not. You might have one account configured with "enhanced recent changes display" and the other not?
On the nose, Brion. The next question is then: would it be possible to separate the style of Special:Recentchanges and Special:Watchlist? Using enhanced recent changes improves Recentchanges but doesn't help the watchlist.
Ben
wikitech-l@lists.wikimedia.org