Commons:Village pump/Proposals/Archive/2012/06

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Search link in sidebar allows everybody to easily find more search options

I see request after request for more search options. Many of those options are already available at Special:Search. So why not put a link to search in the sidebar? That is something we can do on the Commons right now without having to modify the overall MediaWiki software.

Then people could click the search link in the sidebar to go to Special:Search. Then they could do all kinds of searches.

And most importantly, they can right-click the link to open search in a new tab. So one does not cover up the page that one is reading. --Timeshifter (talk) 12:56, 29 May 2012 (UTC)

MediaWiki:Search-results-new-tab.js helps the people who use it to get directly to Special:Search in a new tab. But few people know of it. So that is why a search link in the sidebar would allow everybody to take advantage of many search options available at Special:Search. All without closing the current page they are viewing. They can right-click the link to open Special:Search in a new tab. --Timeshifter (talk) 17:41, 3 June 2012 (UTC)

Import photos from Assamese Wikipedia

We had arranged a photography completion on behalf of Assamese Wikipedia Community. The competition is almost successes with a result of 629 Photos and a lot of photos in Mail also which are yet to upload. We have lake of Manpower in our community. So, for importing we need help of Some bot to import those photos to commons as soon as possible. We have also lots of privious uploaded photos in our wiki. Please think about it also. This will be within the scope of WikiProject Assam and WikiProject India.

Please guide us. Can it made by a bot or something else?

Bishnu Saikia (talk) 12:11, 3 June 2012 (UTC)

Just looking at the first few photos on that page, I see several problems with automatically transferring these files to Commons:
All of these files would be deleted if uploaded to Commons in that state. I also noticed that the Assamese Wikipedia is hosting a lot of files under fair use claims despite not being listed as one of the projects that accept non-free content and despite not having an Exemption Doctrine Policy as required by the Wikimedia Foundation to do so. Several of these non-free files were even tagged for transfer to Commons! Personally, I'd strongly recommend disabling local uploads on the Assamese Wikipedia, as the project is clearly lacking the ability to manage the responsibility. LX (talk, contribs) 12:48, 3 June 2012 (UTC)
Let us give some time, we are talking about it at our Village pump. Hope to fix this problems as soon as possible.

Bishnu Saikia (talk) 17:33, 3 June 2012 (UTC)

One more request here, Please check these photos uploaded by User Nitul Borah for the photo competition are with full descriptions and can be imported to commons. But the descriptions are in Assamese language. Will it work ? Have a look please. Waiting for your reply. Bishnu_Saikia (Talk) 18:41, 4 June 2012 (UTC)


"Other versions", and other sets of similar images

Currently the Category:Other versions templates contain many templates which provide navigation through numerous versions of essentially the same image. It is convenient, but it does not simplify maintenance of {{Information}} descriptions, nor does not it help with categorization. Should descriptions be transcluded too? Differences from image to image may be encoded via named parameters (which, for example, can reassign homonymous fields in {{Information}}). Should categories be transcluded? Should such navigational templates appear in content categories? Should, at last, all similar images be necessarily included in a content category directly? Incnis Mrsi (talk) 10:29, 4 June 2012 (UTC)

Names and links for gadgets

I suppose this isn't so much a proposal as a request, but could we please have the names of the gadgets and links to the documentation (or .js/.css page if no documentation is available) for each gadget in Special:Preferences? Two reasons for this: 1) The descriptions don't always say exactly how a gadget works and 2) if we want to customize the functionality of a gadget, it's nice to have a link to the page with the code on it. --Philosopher Let us reason together. 05:06, 19 June 2012 (UTC)

This will help coders mainly. See next section for laypeople. They need a simple description page. --Timeshifter (talk) 16:39, 19 June 2012 (UTC)

New dropdown menu next to the edit tab

Screenshot of MediaWiki:Gadget-editDropdown.js

Dear community, MediaWiki is made to build an encyclopedia, not for hosting files. This is one reason why we, on Commons have to change a lot of our user interface using JavaScript.

A time ago, Rd232 found a draft by Guillaume Paumier. Unfortunately this was never implemented.

Therefore I decided to use my spare time to "hack" something together. Not nice, not necessarily stable but works with major browsers and current MediaWiki.

I suggest to place the default Gadget Rotatelink, a link to Cropbot's Toolserver interface and the upload a new version of this file-link into this menu, thus activating MediaWiki:Gadget-editDropdown.js by default.

Anyone will be able to add own custom links to this menu, and the dropdown gracefully falls back in e.g. Monobook theme (adding the links to the predefined place, default is the toolbox).

The script is small: After whitespace is removed by RL about 1.4KB.

Please tell my your thoughts. Regards -- RE rillke questions? 14:02, 18 June 2012 (UTC)

  • Comment. RE rillke. Most of what you wrote is incomprehensible to me. Could you explain what this gadget does in a few sentences. See related talk section farther down. --Timeshifter (talk) 16:45, 19 June 2012 (UTC)
    • It won't appear on your gadget-interface. Just a utility gadget. Look at the screenshot. That's all the "gadget" does: Providing a new dropdown next to the edit-tab. Why? Because operations like file upload or requesting rotation do not belong on the file-description, IMHO. -- RE rillke questions? 19:02, 19 June 2012 (UTC)
OK. Another dropdown menu. I have one dropdown menu already added by a gadget in preferences. I forget which one. Where can one get the code to test your dropdown menu? --Timeshifter (talk) 19:08, 20 June 2012 (UTC)

Just an example (a static link to toolserver). Actually the rotate link should go into this menu.

mw.loader.using('ext.gadget.editDropdown', function () {
	mw.libs.commons.ui.addEditLink(
		'//toolserver.org', 
		"Toolserver", 
		'p-Toolserverlink', 
		"Toolserver. Driven by Wikimedia Germany"
	);
});

-- RE rillke questions? 19:24, 20 June 2012 (UTC)

Where do I put this? Here?: User:Timeshifter/common.js --Timeshifter (talk) 12:25, 21 June 2012 (UTC)
Yes. -- RE rillke questions? 13:45, 21 June 2012 (UTC)
  • Support. I support this as long as it does not remove links (file upload, requesting rotation, etc.) from the file-description. So the links would be in both the dropdown menu and the file description. It looks like that is how you have it now, and so there is no problem now. --Timeshifter (talk) 14:28, 22 June 2012 (UTC)

Link to description page for each gadget in preferences

At Special:Preferences#mw-prefsection-gadgets many of the gadgets are incomprehensible to many people, myself included. Could a description page be linked for each gadget listed. Just put a "description" link for each gadget. I am not talking about a detailed documentation page. Those are also oftentimes incomprehensible. I am talking about a short description in a paragraph or two. This way people can decide whether to turn the gadget on in order to try it. --Timeshifter (talk) 16:41, 19 June 2012 (UTC)

And a name for the gadget, so people know how to refer to it, I hope.  ;-) I actually like this idea better, provided the description page links to the full documentation and to the gadget's code page, perhaps as a "See also" section at the end. --Philosopher Let us reason together. 02:09, 20 June 2012 (UTC)
And who wants to update these links for each language? This should be done by {{Gadget-desc}}, if someone has the time (since we provide the self=-param it should be possible). I am just not sure how the interface will look like after Roan, Trevor and Krinkle revamped the whole gadget stuff. IMHO, a screenshot or demo should be loaded when hovering a gadget description but our site-js is disabled on Special:Preferences. -- RE rillke questions? 19:08, 19 June 2012 (UTC)
Having the language links in any language is better than none - there is Google Translate after all. As for the other, why is js disabled on Special:Preferences? --Philosopher Let us reason together. 16:24, 20 June 2012 (UTC)
Because the devs think we are so dumb that we lockout ourselves. bugzilla:33220, bugzilla:29028. This is at least what I think they mean with "security" because if I am an evil script and want to change the user prefs, I could use the API, doing this silently or bind a handler to the prefs-link loading the prefs-page with Ajax and simply insert the page into the DOM (with me, the evil script still alive).
BTW, did you know there is Special:Gadgets? -- RE rillke questions? 17:44, 20 June 2012 (UTC)
No, I hadn't known about that - I guess now I know where to put any {{Editprotected}} requests, thanks! --Philosopher Let us reason together. 20:19, 20 June 2012 (UTC)
I and others can help update the short description info. Just put a link for "description" next to each gadget listed in preferences. I do not understand the templates being discussed. And I do not want to edit templates, nor any of their parameters. I just want to enter short description info in English. --Timeshifter (talk) 19:12, 20 June 2012 (UTC)
Yes, but I makes no sense to edit each description for each language (only admins can). Instead {{Gadget-desc}} could be used to look-up whether a description-info exists in a namespace that could be edited by all users and if so, display a link. The same approach could be used to mark default gadgets, instead of having to change each single language when changing the state of a gadget (e.g. from normal to default). -- RE rillke questions? 21:14, 20 June 2012 (UTC)
That sounds good. Rd232 (talk) 22:25, 20 June 2012 (UTC)
The intro at Special:Preferences#mw-prefsection-gadgets needs to be changed to indicate that some description pages, or sections of pages, can be edited by users. --Timeshifter (talk) 12:34, 21 June 2012 (UTC)

Improved category browsing

Example of galleryZoomHover.js

Improve category browsing by enabling as default gadgets

  1. User:Rillke/galleryZoomHover.js - gives a popup preview of the image when you hover over it (try it with mw.loader.using(['mediawiki.util', 'mediawiki.api'], function() { importScript('User:Rillke/galleryZoomHover.js'); }); in your Special:Mypage/common.js)
  2. Long Image Names in Categories - on category pages, gives the full filename of images instead of chopping off the name after 20 letters (Special:Preferences#mw-prefsection-gadgets, "interface: files and categories") ✓ Done -- RE rillke questions? 11:35, 30 June 2012 (UTC)

Rd232 (talk) 13:09, 22 April 2012 (UTC)

How about adding a gadget that loads the next files on-demand when scrolling down, if the category consists of more than 200 files? (Like done in VisualFileChange) (Personally, I think MediaWiki should not send out 200 files initially but use some LOD-technique, proposed this on bugzilla:35618) -- RE rillke questions? 17:50, 22 April 2012 (UTC)
 Support Looks good. Will certainly annoy many an experimented contributor (who will deactivate it) and be loved by everyone else. Jean-Fred (talk) 22:03, 4 June 2012 (UTC)
 Comment I would move it first to MediaWiki namespace, and activate as an optional gadget. --Jarekt (talk) 14:29, 18 June 2012 (UTC)
OK, I can live with that for 1. What about 2.? Rd232 (talk) 21:36, 18 June 2012 (UTC)
  • Support both as default. The zoomed image needs to be moved up a line. I can't see the text at the bottom due to the URL covering part of it. I use Firefox. It popups up the image URL at the bottom left of the screen. Also, I don't need the progressive increase in size if it slows down the presentation of the final image. --Timeshifter (talk) 21:53, 18 June 2012 (UTC)