Yesterday, Tim Johansson (I'll call him Joti from now on, we have too many Tims already) asked me to mentor him for this year's Google Summer of Code. I accepted. The project he proposed was fixing bug 167 [1] (separating category and interlanguage links from the article text in the interface). I've read through the comments, and the issue looks controversial. Several approaches have been suggested in the past and there has been debate as to which one is best. Of course, I'd like to hear from Joti what his plans are so we can discuss them here, but I'd also like to hear opinions as to whether we should actually implement bug 167 in the first place.
Roan Kattouw (Catrope)
of Code. I accepted. The project he proposed was fixing bug 167 [1] (separating category and interlanguage links from the article text in the interface). I've read through the comments, and the issue looks
For categories there already is Hotcat [1], and a similar gadget for interlanguage links would be trivial.
[1] http://commons.wikimedia.org/wiki/MediaWiki_talk:Gadget-HotCat.js
Roan Kattouw writes:
Yesterday, Tim Johansson (I'll call him Joti from now on, we have too many Tims already) asked me to mentor him for this year's Google Summer of Code. I accepted. The project he proposed was fixing bug 167 [1] (separating category and interlanguage links from the article text in the interface). I've read through the comments, and the issue looks controversial. Several approaches have been suggested in the past and there has been debate as to which one is best. Of course, I'd like to hear from Joti what his plans are so we can discuss them here, but I'd also like to hear opinions as to whether we should actually implement bug 167 in the first place.
Roan Kattouw (Catrope)
Why I think this should be WONTFIXed? I still can't see any way how this would be implemented, considering problem that interwikis and categories can be included from templates. --VasilievVV
On Wed, Mar 19, 2008 at 07:47:33PM +0100, VasilievVV wrote:
Why I think this should be WONTFIXed? I still can't see any way how this would be implemented, considering problem that interwikis and categories can be included from templates. --VasilievVV
Even more interesting: [[Category:{{SomePage}} works - if there is a ]] in the transcluded page, the preprocesser can uncover it and use it to close the category link.
- Carl
VasilievVV a écrit :
Why I think this should be WONTFIXed? I still can't see any way how this would be implemented, considering problem that interwikis and categories can be included from templates. --VasilievVV
There are two types of interwikis:
* Internals
They are used to link to an article in a different language and appear in the interwiki toolbox. The way it is done now (including the link in the article text) can be migrated to articles metadata. It is simply a matter of adding a new table and another one to keep history. The tricky part is migrating the metadata from inline text to a database table.
* externals Those are just shortcuts for externals links (ex: [[youtube:QSZE3M]]). This is a w3c draft named 'curie' : http://www.w3.org/TR/curie/ We could also drop support for the 'ISBN' and 'RFC' keywords while we are it.
Categories could also be added as metadata, it will solve a ton of issues and get ride of revisions spam. When used in templates, one should be able to mark the category as includable or not includable.
On Wed, Mar 19, 2008 at 2:47 PM, VasilievVV vasilvv@gmail.com wrote:
Why I think this should be WONTFIXed? I still can't see any way how this would be implemented, considering problem that interwikis and categories can be included from templates.
You would just provide no interface to alter the categories that are added by templates, or generally speaking uncovered by template expansion. Of course it's somewhat tricky to do anyway, but it should be feasible to allow the tool to handle manually-added categories.
Additionally, it would be conceivably possible to "remove" categories added by templates by instituting some kind of per-page exception mechanism. When calculating added and removed categories, you would calculate them as normal and then subtract out all exceptions. The value of this addition is questionable, however, and it could safely be omitted.
Why I think this should be WONTFIXed? I still can't see any way how this would be implemented, considering problem that interwikis and categories can be included from templates.
You would just provide no interface to alter the categories that are added by templates, or generally speaking uncovered by template
??!! Why the subjunctive? Am I already blacklisted? Is no one reading my postings?
It already exists (HotCat-Gadget on commons)! The SoC proposal is moot. It has been done.[*] And for the day to day real-life applications (on commons for example) all the constructed pathological cases that were posted here are simply irrelevant.
[*] Oh, right, it has been done as a Javascript add-on, that may not count to some people. But please keep in mind that the category suggestion uses AJAX anyways, so there is no way (and no point for that matter) to built it into the interface (unless you also plan to abandon [[Category:..]] tags and change ta DB structure accordingly)
On Wed, Mar 19, 2008 at 7:42 PM, Daniel Schwen lists@schwen.de wrote:
??!! Why the subjunctive? Am I already blacklisted? Is no one reading my postings?
Must have missed it.
It already exists (HotCat-Gadget on commons)! The SoC proposal is moot. It has been done.[*] And for the day to day real-life applications (on commons for example) all the constructed pathological cases that were posted here are simply irrelevant.
[*] Oh, right, it has been done as a Javascript add-on, that may not count to some people. But please keep in mind that the category suggestion uses AJAX anyways, so there is no way (and no point for that matter) to built it into the interface (unless you also plan to abandon [[Category:..]] tags and change ta DB structure accordingly)
Interesting. It's GPL/GPL-compatible? Maybe I'll have a look at that sometime and merge it into core if it seems suitable. It seems like at least some parts should be server-side: surely it currently needs to retrieve the text of the page, parse it in the client, and resubmit it?
Interesting. It's GPL/GPL-compatible? Maybe I'll have a look at that
Yes, sure, it was originally created by Magnus on commons and is now maintained by some other people there (mainly Lupo and occasionaly myself)
sometime and merge it into core if it seems suitable. It seems like at least some parts should be server-side: surely it currently needs to retrieve the text of the page, parse it in the client, and resubmit it ?
No. The categories are parsed from the rendered page in "catlinks" (there is a blacklist for license categories). The API is used to suggest categories while typing (very useful).
http://commons.wikimedia.org/wiki/MediaWiki:Gadget-HotCat.js
On 20/03/2008, Daniel Schwen lists@schwen.de wrote:
sometime and merge it into core if it seems suitable. It seems like at least some parts should be server-side: surely it currently needs to retrieve the text of the page, parse it in the client, and resubmit it ?
No. The categories are parsed from the rendered page in "catlinks" (there is a blacklist for license categories). The API is used to suggest categories while typing (very useful).
HotCat is indeed great. I have heard that hu.wikipedia has a gadget similar to HotCat, but that has a hierarchical display. I am trying to find out more about it.
cheers Brianna
On Wed, Mar 19, 2008 at 12:44 PM, Roan Kattouw roan.kattouw@home.nl wrote:
Yesterday, Tim Johansson (I'll call him Joti from now on, we have too many Tims already) asked me to mentor him for this year's Google Summer of Code. I accepted. The project he proposed was fixing bug 167 [1] (separating category and interlanguage links from the article text in the interface). I've read through the comments, and the issue looks controversial. Several approaches have been suggested in the past and there has been debate as to which one is best. Of course, I'd like to hear from Joti what his plans are so we can discuss them here, but I'd also like to hear opinions as to whether we should actually implement bug 167 in the first place.
I see my HotCat was alreadz mentioned. Note that there are copies of it on commons, en and de wikipedia, and probably others. I am uncertain if these are kept "in sync". Probably not...
See also my latest endeavour in this direction at [[User:Magnus Manske/less edit clutter.js]] on en.wikipedia. BTW, is there no "&withJS" parameter on en?
Cheers, Magnus
See also my latest endeavour in this direction at [[User:Magnus Manske/less edit clutter.js]] on en.wikipedia. BTW, is there no "&withJS" parameter on en?
The "&withJS" parameter is implemented entirely in Javascript itself, and as far as I know exists only on commons.
wikitech-l@lists.wikimedia.org