Talk:Gadget kitchen

Previous page history was archived for backup purposes at Talk:Gadget kitchen/LQT Archive 1 on 2015-07-10.

At section Gadget_kitchen#Debugging_user_scripts_and_gadgets Internet explorer is no longer supported. Needed actual realignment for Edge. Thanks.

Christian 🇫🇷 FR (talk) 09:23, 26 July 2022 (UTC)

Hi everybody! Google Code-in (GCI) will soon take place again - a seven week long contest for 13-17 year old students to contribute to free software projects. Tasks should take an experienced contributed about two-three hours and can be of the categories Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface/Design. Do you have an idea for a task and could you imagine mentoring that task? For example, do you have something on mind that needs documentation, research, some gadget or template issues on your "To do" list but you never had the time, and can imagine enjoying mentoring such a task to help a new contributor? If yes, please check out mw:Google Code-in/2018 and become a mentor! Thanks in advance!

This works:

mw.loader.load('//www.mediawiki.org/w/index.php?title=MediaWiki:Tutorial-QuickRC.js&action=raw&ctype=text/javascript');

do i need to do something besides enable userjs?

Gadget kitchen#I want to try!

i know my common.js works, because i use it for other things. Def working.

Maybe a problem with `importScript`?

importScript() won't work if you try to use a script from another wiki. See en:Wikipedia:User_scripts#Full_manual_instructions.

Still not seeing the expected new side-bar item. Tried all the following:

mw.loader.load('https://www.mediawiki.org/wiki/MediaWiki:Tutorial-QuickRC.js');
mw.loader.load('//www.mediawiki.org/wiki/MediaWiki:Tutorial-QuickRC.js');

This should work: mw.loader.load('//www.mediawiki.org/w/index.php?title=MediaWiki:Tutorial-QuickRC.js&action=raw&ctype=text/javascript');

i updated the doc. Feel free to revise my text.

Hi everybody! Google Code-in (GCI) will soon take place again - a seven week long contest for 13-17 year old students to contribute to free software projects. Tasks should take an experienced contributed about two-three hours and can be of the categories Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface/Design. Do you have an idea for a task and could you imagine mentoring that task? For example, do you have something on mind that needs documentation, research, some gadget or template issues on your "To do" list but you never had the time, and can imagine enjoying mentoring such a task to help a new contributor? If yes, please check out mw:Google Code-in/2017 and become a mentor! Thanks in advance!

The directions around importScript seem outdated?

I poked around a bit, and while I noticed a category for JS snippets, there appears to be no significant category for general-purpose gadgets and user scripts. Where should I put JS code for gadgets that aren't exclusively for use on Wikimedia wikis? I know Wikipedia:User scripts/list exists, as I have contributed there, but it's a bit of a toss-up as to whether or not all those user scripts will function on a non-Wikimedia wiki.

This page says to enable the "Code Editor" item in preferences, but this is missing. ~~~~

It's probably on by default now. You can turn it on and off with the first button on top of the editor when editing a .js page.

• Are you a developer and have small, self-contained, "easy" bugs in your Wikimedia code that you would love to get fixed?
• Does your gadget use some deprecated API calls?
• Does the documentation of your gadget code need some improvements?
• Do you enjoy mentoring to a new contributor fixing small tasks?

Google Code-In (GCI) will take place again in December and January: a contest for 13-17 year old students to provide small contributions to free software projects. Wikimedia will apply again to take part and would like to offer a wide range of tasks.

Just one example: Multimedia saw some impressive achievements in last year's contest!

Tasks should take an experienced contributed about two-three hours ("beginner tasks" also welcome which are smaller) and can be of the categories Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface/Design. For more information, check the wiki page and if something is unclear, please ask on the talk page!

Thank you!

Hi everybody! Google Code-In (GCI) will soon take place again - a six week long contest for 13-17 year old students to contribute to free software projects. Wikimedia took part in 2013 already with great results. Tasks should take an experienced contributor about two-three hours (but "beginner tasks" are also welcome which are smaller) and can be of the categories Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface/Design.

Do you have an idea for a task and could you imagine mentoring that task? For example, do you have some gadget in mind that needs documentation or has some code issues but you never had the time to fix that yourself?

If yes, please go to mw:Google Code-in 2014, check out the "Mentor's corner", and add your task there (please add tasks until Sunday even if it's only a stub - we can still polish them until December 1st when the contest begins)! And if something is unclear, please ask on the talk page. Happy to help!