![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current main page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 | Archive 5 |
I'd like to suggest a script I recently created, WikiMark, for evaluation to be added to the gadgets list. This is a very simple script that allows one click bookmarking of articles. Requires no configuration, and is comfirmed to work in Firefox, Opera and Chrome. My IE doesn't load it, but this could be a problem with my IE, so someone who uses it more should probably test & report. — Twinzor Say hi! 18:31, 13 January 2009 (UTC)
While we're suggesting gadgets to add, I'd like to suggest this, which makes it safe to click on most links when editing a page in Internet Exploder - normally, the links open in the same window, and any edits made are lost; the script forces them to open in a new window. Firefox, Opera, Safari and others (AFAIK) are smart enough to save the form data, so the script ignores them. The script was written by Alex Smotrov (see discussion on his talk page; the whole thing was spurred by this VPT discussion), and I've made some minor adjustments since then. 「 ダイノ ガイ 千?!」(Dinoguy1000) 22:31, 13 January 2009 (UTC)
I've created a script which I call Localize Comments. Documentation can be found at Wikipedia:Localize Comments. I've been working on it and tweaking it for nearly a year now, and I think that it's ready for primetime. What it does, in a nutshell, is it converts all timestamps generated in signatures, etc. (such as those from ~~~~) to the user's local time. The format can be changed on by the user to "2009-01-01", "January 1, 2009" or "1 January, 2009". Here's an example input:
20:22, 14 January 2009 (UTC)
And here's the output:
Yesterday, 3:22 pm (UTC-5)
As you can see, it gives me the local time, plus it gives a relative date. Other relative date possibilities include "Today, "2 days ago", "1 month 5 days ago", "1 year, 2 months, 3 days ago", etc. The actual date will be returned if it is more than one day ago, so like 2009-01-13, last Tuesday (2 days ago), 11:50 pm (UTC-5). Also, it works for timestamps in the future, like:
00:16, 22 January 2009 (UTC)
Appears as:
2009-01-21, this Wednesday (6 days from now), 7:16 pm (UTC-5)
Future timestamps are normally used in proposals such as RfAs to give the day and time that it ends. I have tested it in several browsers, and it works, but more testing from others is also appreciated. I don't think it will conflict with any other scripts, and it certainly requires no configuration—it will determine the user's timezone by their computer's setting that gets sent to the script via JavaScript. I'd like to point out that the date is returned with a font that's 90% the normal size, because the output is a bit longer so it needs more space. The bright side is that it has nowrap, so the entire timestamp is held together and completely intact no matter how squished it gets. Also, I am open to suggestions for a better and more appropriate name, although I think "Localize Comments" gets the point across even though it might not be entirely accurate, as the script actually converts any timestamp, not just in comments. In the case where the script's output is incorrect, you can mouseover the date to get the actual date that exists on the page. Questions? Comments? Gary King ( talk) 22:12, 15 January 2009 (UTC)
{{
editprotected}}
- No consensus yet that this should be a gadget.
Oren0 (
talk)
08:32, 19 January 2009 (UTC)
If there is no opposition, could someone please add it to the list of gadgets? I think it's very useful to a general audience, more so than Friendly or Twinkle, in my opinion. :) Gary King ( talk) 19:03, 18 January 2009 (UTC)
I'd like to propose User:Haza-w/Caction tool as a gadget (script: User:Haza-w/cactions.js).
It passes the general criteria:
More info on the above is available on the documentation page. haz ( talk) 22:24, 19 January 2009 (UTC)
The documentation link is still going to Haza-w's user page ( User:Haza-w/Caction_tool)) as I'm not sure where the proper location for documentation is. Thanks again to Haza-w for developing this tool. -- Ckatz chat spy 18:55, 3 February 2009 (UTC)"Add page and user options to drop-down menus on the toolbar. ( documentation; works in Monobook and Modern skins)"
It's a little-known fact that while the edit summary box is limited to 200 characters, MediaWiki can sometimes actually accept up to 250 characters. What actually happens is the database field is limited to 250 bytes, and since some characters take up more than one byte, MediaWiki allows for a 50-byte margin.
For a while now I've been using a script that gives me a lot more precision over my edit summaries. It counts the number of bytes in my edit summary, and if possible silently keeps me from entering more than 250 bytes, no matter the number of characters I've entered. If I copy and paste a bunch of characters at once totaling more than 250 bytes, JavaScript can't detect this until it's too late, so the script warns me and disables the "Save page" button until I fix the problem.
This has been useful to me because it's allowed me to better explain myself in my edit summaries. For example, when I've made a lot of small, uncontroversial changes to an article and I'd like to briefly mention as many of them as possible in the edit summary.
The script is at User:Remember the dot/Long edit summary.js. I've tested it on Internet Explorer 6, 7, and 8, Firefox 2 and 3, Opera 9.5, and Safari 3. It works excellently in most of them, however Firefox and Safari will clip the edit summary if you click Preview. I'd like to include this as a gadget, what do the rest of you think? — Remember the dot ( talk) 04:18, 21 January 2009 (UTC)
input#wpSummary {
width: 100%;
}
Ok, this gadget allows auto-refreshing page loads. User:Coconut-Freak/AJAX auto refresher.js. — HK22 \ my contributions/ ( my talk) 09:39, 21 February 2009 (UTC)
I wrote a new gadget which can display the meaning of each interwiki link in English by popping up a little yellow tooltip. -- 百楽兎 ( talk) 03:53, 22 February 2009 (UTC)
////////////////////////////////////////////////////////////////
//Authors: User:Πrate & User:Fdcn
//Date: 2008.11.25
//License: GFDL. The Version is the same as Wikipedia's license.
////////////////////////////////////////////////////////////////
var label_class="interwiki-ab","interwiki-ak","interwiki-als","interwiki-am","interwiki-an","interwiki-ang","interwiki-ar","interwiki-arc","interwiki-arz","interwiki-as","interwiki-ast","interwiki-av","interwiki-ay","interwiki-az","interwiki-ba","interwiki-bar","interwiki-bat-smg","interwiki-bcl","interwiki-be","interwiki-be-x-old","interwiki-bg","interwiki-bh","interwiki-bm","interwiki-bn","interwiki-bo","interwiki-bpy","interwiki-br","interwiki-bs","interwiki-bug","interwiki-bxr","interwiki-ca","interwiki-cbk-zam","interwiki-cdo","interwiki-ce","interwiki-ceb","interwiki-ch","interwiki-chr","interwiki-chy","interwiki-co","interwiki-cr","interwiki-crh","interwiki-cs","interwiki-csb","interwiki-cu","interwiki-cv","interwiki-cy","interwiki-da","interwiki-de","interwiki-dsb","interwiki-dv","interwiki-dz","interwiki-ee","interwiki-el","interwiki-eml","interwiki-en","interwiki-es","interwiki-et","interwiki-eu","interwiki-ext","interwiki-fa","interwiki-ff","interwiki-fi","interwiki-fj","interwiki-fo","interwiki-fr","interwiki-frp","interwiki-fur","interwiki-fy","interwiki-ga","interwiki-gan","interwiki-gd","interwiki-gl","interwiki-glk","interwiki-gn","interwiki-got","interwiki-gu","interwiki-gv","interwiki-ha","interwiki-hak","interwiki-haw","interwiki-he","interwiki-hi","interwiki-hr","interwiki-hsb","interwiki-ht","interwiki-hu","interwiki-hy","interwiki-hz","interwiki-id","interwiki-ii","interwiki-ik","interwiki-ilo","interwiki-is","interwiki-it","interwiki-iu","interwiki-ja","interwiki-jv","interwiki-ka","interwiki-kaa","interwiki-kab","interwiki-kg","interwiki-ki","interwiki-kk","interwiki-kl","interwiki-km","interwiki-kn","interwiki-ko","interwiki-ks","interwiki-ksh","interwiki-ku","interwiki-kv","interwiki-kw","interwiki-ky","interwiki-la","interwiki-lad","interwiki-lb","interwiki-lbe","interwiki-li","interwiki-lij","interwiki-lmo","interwiki-lo","interwiki-lt","interwiki-lv","interwiki-map-bms","interwiki-mdf","interwiki-mh","interwiki-mi","interwiki-mk","interwiki-ml","interwiki-mn","interwiki-mo","interwiki-mr","interwiki-ms","interwiki-mt","interwiki-mus","interwiki-my","interwiki-myv","interwiki-mzn","interwiki-na","interwiki-nah","interwiki-nap","interwiki-nds","interwiki-nds-nl","interwiki-ne","interwiki-new","interwiki-ng","interwiki-nl","interwiki-nn","interwiki-no","interwiki-nrm","interwiki-nv","interwiki-ny","interwiki-om","interwiki-or","interwiki-os","interwiki-pa","interwiki-pdc","interwiki-pi","interwiki-pih","interwiki-pl","interwiki-pms","interwiki-ps","interwiki-pt","interwiki-qu","interwiki-rm","interwiki-rmy","interwiki-rn","interwiki-ro","interwiki-roa-rup","interwiki-roa-tara","interwiki-ru","interwiki-rw","interwiki-sa","interwiki-sah","interwiki-sc","interwiki-scn","interwiki-sd","interwiki-se","interwiki-sg","interwiki-sh","interwiki-si","interwiki-sk","interwiki-sl","interwiki-sm","interwiki-sn","interwiki-so","interwiki-sq","interwiki-sr","interwiki-srn","interwiki-ss","interwiki-stq","interwiki-su","interwiki-sv","interwiki-sw","interwiki-szl","interwiki-ta","interwiki-te","interwiki-tet","interwiki-tg","interwiki-th","interwiki-ti","interwiki-tk","interwiki-tn","interwiki-to","interwiki-tr","interwiki-ts","interwiki-tt","interwiki-tum","interwiki-ty","interwiki-udm","interwiki-ug","interwiki-uk","interwiki-ur","interwiki-uz","interwiki-ve","interwiki-vec","interwiki-vi","interwiki-vls","interwiki-vo","interwiki-wa","interwiki-war","interwiki-wuu","interwiki-xal","interwiki-xh","interwiki-yi","interwiki-yo","interwiki-za","interwiki-zea","interwiki-zh","interwiki-zh-classical","interwiki-zh-min-nan","interwiki-zh-yue","interwiki-zu"];
var label_title="Abkhazian","Akan","Alemannic","Amharic","Aragonese","Anglo-Saxon","Arabic","Assyrian Neo-Aramaic","Egyptian Arabic","Assamese","Asturian","Avar","Aymara","Azeri","Bashkir","Bavarian","Samogitian","Central_Bicolano","Belarusian","Belarusian (Tarashkevitsa)","Bulgarian","Bihari","Bambara","Bengali","Tibetan","Bishnupriya Manipuri","Breton","Bosnian","Buginese","Buryat (Russia)","Catalan","Zamboanga Chavacano","Min Dong","Chechen","Cebuano","Chamorro","Cherokee","Cheyenne","Corsican","Cree","Crimean Tatar","Czech","Kashubian","Old Church Slavonic","Chuvash","Welsh","Danish","German","Lower Sorbian","Divehi","Dzongkha","Ewe","Greek","Emilian-Romagnol","English","Spanish","Estonian","Basque","Extremaduran","Persian","Fula","Finnish","Fijian","Faroese","French","Franco-Provençal/Arpitan","Friulian","West Frisian","Irish","Gan","Scottish Gaelic","Galician","Gilaki","Guarani","Gothic","Gujarati","Manx","Hausa","Hakka","Hawaiian","Hebrew","Hindi","Croatian","Upper Sorbian","Haitian","Hungarian","Armenian","Herero","Indonesian","Sichuan Yi","Inupiak","Ilokano","Icelandic","Italian","Inuktitut","Japanese","Javanese","Georgian","Karakalpak","Kabyle","Kongo","Kikuyu","Kazakh","Greenlandic","Khmer","Kannada","Korean","Kashmiri","Ripuarian","Kurdish","Komi","Cornish","Kirghiz","Latin","Ladino","Luxembourgish","Lak","Limburgian","Ligurian","Lombard","Lao","Lithuanian","Latvian","Banyumasan","Moksha","Marshallese","Maori","Macedonian","Malayalam","Mongolian","Moldovan","Marathi","Malay","Maltese","Muscogee","Burmese","Erzya","Mazandarani","Nauruan","Nahuatl","Neapolitan","Low Saxon","Dutch Low Saxon","Nepali","Newar / Nepal Bhasa","Ndonga","Dutch","Norwegian (Nynorsk)","Norwegian (Bokmål)","Norman","Navajo","Chichewa","Oromo","Oriya","Ossetian","Punjabi","Pennsylvania German","Pali","Norfolk","Polish","Piedmontese","Pashto","Portuguese","Quechua","Romansh","Romani","Kirundi","Romanian","Aromanian","Tarantino","Russian","Kinyarwanda","Sanskrit","Sakha","Sardinian","Sicilian","Sindhi","Northern Sami","Sango","Serbo-Croatian","Sinhalese","Slovak","Slovenian","Samoan","Shona","Somali","Albanian","Serbian","Sranan","Swati","Saterland Frisian","Sundanese","Swedish","Swahili","Silesian","Tamil","Telugu","Tetum","Tajik","Thai","Tigrinya","Turkmen","Tswana","Tongan","Turkish","Tsonga","Tatar","Tumbuka","Tahitian","Udmurt","Uyghur","Ukrainian","Urdu","Uzbek","Venda","Venetian","Vietnamese","West Flemish","Volapük","Walloon","Waray-Waray","Wu","Kalmyk","Xhosa","Yiddish","Yoruba","Zhuang","Zealandic","Chinese","Classical Chinese","Min Nan","Cantonese","Zulu"];
for (var i=0; i<label_class.length; i++){
var label=getElementsByClassName(document, "li", label_classi]);
if(label && label0]){
label0].title = label_titlei];
}
}
Gah, I nearly added m:User:Pathoschild/Scripts/Regex menu framework without asking ;-)
It adds regex functionality to the edit window; I dont see any similar tools already installed. I recommend it is placed in the "Editing gadgets" section.
It is installed on Wikisource, and I have copied the pages MediaWiki:Gadget-RegexMenuFramework and MediaWiki:Gadget-RegexMenuFramework.js from there. If this proposal is denied, they should be deleted. John Vandenberg ( chat) 04:10, 24 April 2009 (UTC)
I have ported the TinEye gadget at Commons to en.wikipedia.org: User:Twp/tineye.js. TinEye is an image search engine. This gadget adds a "tineye" tab to the top of File and Image pages which, when clicked, performs a TinEye search on the desired image. It's a useful tool for uncovering potential image copyright violations, so I am proposing adding it as an official Wikipedia gadget.
I have tested and found it to work on both Firefox 3.0.9 and Safari 3.2.1 on Mac OS X. I do not have a Windows platform handy on which to test it on MSIE or Chrome. Because it adds a new navigation tab to image pages, it appears to work only on the Monobook, MySkin and Chick skins.
Comments welcomed. Tim Pierce ( talk) 12:15, 27 April 2009 (UTC)
addPortletLink
to add the tab, so it should be OK compatibility-wise. It should work with Modern if the compatibility function gadget is activated.My monobook.js file has code that successfully queries Google translation services on any word that you hover your cursor over (and in ie, firefox, chrome and epiphany any selected text you hover the cursor over). The result is that nonEnglish speakers with intermediate command of English can quickly look up words or phrases in 40 languages in any article in the English Wikipedia.
Code is at User:Endo999/monobook.js if anyone wants to try it out.
The code establishes a tab at the top of the article: "translation popups on/off". You can toggle the popups on and off this way. You can change the language at this tab as well.
An earlier version of this code (98 percent of code is the same) has been successfully running on the Spanish Wikipedia for 6 months without complaint. It seems to be used in moderate amounts by the users there.
I have tested this earlier code further and made some small enhancements to it. This is the second round for this proposal. Around 7 months ago I made it. Some people thought it was a good idea but nobody implemented it.
Endo999 ( talk) 23:14, 7 May 2009 (UTC)
Thanks for the feedback about this proposal. The google translation services are free to use. Google does not charge for it. I can change the styles (the yellow) of the popup window if people wish it. On IE, Firefox, Chrome and Epiphany you can select up to 500 characters of text, hover the cursor within it, and then the translation of the text will appear in the popup. On Opera and Safari this will not happen. I can lower the popup window a bit so that it doesn't conflict with the title tags. Just tell me and I will do it. Endo999 ( talk) 20:59, 8 May 2009 (UTC)
As per your comments I have done the following:
1) the background color of the popup is now beige. It can be set by a variable in monobook.js 2) all variables and function names now have SC prefixed to them 3) when the cursor is over a link with a title the popup now appears below the title (42 pixels lower) 4) when NavPopups are on and the cursor is over a link the popup now appears above the navpopup, that is, above the cursor. Otherwise the popup appears at the cursor as before.
Endo999 ( talk) 07:00, 9 May 2009 (UTC)
Although this is true, with the unified logins it is not as bad as might be thought. A french member of fr.Wikipedia will now be able to log into en.wikipedia.org with his own account. And thus be able to turn on the gadget there.
My pitch for this code as a gadget is that there are 1 billion people who read English as a second language. Many of them are intermediate proficient. Tens of millions of these would use the en.wikipedia.org to read English language articles. These people could use this tool to help them along. I am an intermediate French/Spanish reader and I use the tool to read the French and Spanish wikipedias. I can read such articles when normally I would have trouble without the tool. I would have to manually use a dictionary which is a lot slower. Endo999 ( talk) 20:59, 8 May 2009 (UTC)
Endo999 ( talk) 08:18, 13 July 2009 (UTC)
User:M/monobook.js contains a script that rips out refs, replacing [2]<ref name=abc/><ref>cba</ref> with [2][1][3]. Puts refs back when the save/preview/changes buttons are clicked. Currently just 'hides' the refs, which is working great for heavily-cited articles. 00:06, 18 May 2009 (UTC)
Any objections to a gadget that increases the size of the diff text? I imagine it annoys a lot of people having it so small. Something like...
span.diffchange, td.diff-addedline, td.diff-deletedline { font-size:120% !important; }
Thoughts? -- MZMcBride ( talk) 23:10, 21 May 2009 (UTC)
I have no qualifications, whatsoever, to create code for gadgets. However, I have an idea for a gadget that I could see almost every editer using, so I hope that a reader of this post could code the gadget. The gadget I speak of would be a spelling checker on the edit pages, so that editers could check their spelling in the edit box as they write, or, at the very least, click on a shortcut that would check the spelling in the edit box after the editer is done writing; the gadget could point out grammar or spelling errors and skip Wikipedia formatting code. I have needed this gadget for nearly every edit I have ever made, including addition of sections on talk pages. Furthermore, thus gadget does not yet exist. I believe the widespread applicability of such a gadget is obvious; Wikipedia editers just need someone to make it!
-- Some Old Man ( talk) 04:56, 8 June 2009 (UTC)
Ah yes; all very good points. I am a bit embarassed since I use a Macintosh with Safari and have noticed the spell checker, but I usually sign in on Wikipedia using my PC with Internet Explorer (maybe out of just tradition). I have heard somewhat reliable rumors about Internet Explorer being defunct anyway; I simply use it on my PC because I am so used to it. Anyway, I very much appreciate you all responding to my idea! Feel free to delete this section.
-- Some Old Man ( talk) 22:13, 8 June 2009 (UTC)
I need opinions about a tool, I think it could be very useful Lenore ( talk) 23:54, 12 June 2009 (UTC)
importScript('User:Lenore/autolink.js')
rather than document.write('...')
. The latter has a tendency to break in unexpected ways. —Preceding
unsigned comment added by
Mr.Z-man (
talk •
contribs) 02:21, 13 June 2009
Per discussion at
Wikipedia:VPR#The_.5Bedit.5D_link_for_sections, I would like to enable
MediaWiki:Gadget-lefteditlinks.js as an option for the users who supported the change. The code has been extensively tested at the German Wikipedia, where it is included in
de:MediaWiki:Common.js, and I only added a 5px padding and made the text slightly larger. I believe that it meets all of the criteria for a gadget because: It works without configuration (in fact, it can't be configured; testing by users at VPR indicates that it functions in at least recent versions of IE, Firefox, Safari, and Google Chrome, but has a bug in Opera; it does not duplicate another gadget; it isn't a collection of scripts; it doesn't require permissions; and it works in all skins (except for "Vector", which isn't an officially usable skin yet but works via &useskin=vector
). –
Drilnoth (
T •
C •
L)
18:34, 20 June 2009 (UTC)
if (typeof oldEditsectionLinks != 'undefined' && oldEditsectionLinks) return;
can be removed? I don't quite fully understand the code since I basically just stole it from
de:MediaWiki:Monobook.js (actually, that's the only line that I don't understand). If that's what you mean, I can remove it. –
Drilnoth (
T •
C •
L)
03:59, 25 June 2009 (UTC)
I have made some improvements to the script, please see the top of my monobook.js page. I have added user customization, made the script faster (presumably), fixed the spacer size (is now set in relative units for a better look with different heading font sizes), and have added comments to the code for maintainability. It works in Opera 9.64, IE 8.0.6001, Chrome 1.0.154.65, and Safari 3.2.3 under Windows XP. Cacycle ( talk) 07:58, 27 June 2009 (UTC)
I would like to see the three CSS snippets which controls the display of coordinate as Decimal and DMS as a gadget. — Dispenser 18:26, 27 June 2009 (UTC)
This is a very useful gadget which is extensively used in de-wp. It has the simple purpose to highlight links to disambiguation pages. These should normally not exist inside articles but are hard to spot, making the gadget really valuable for editors, many links are fixed due to it. Additionally, it highlights links to “redirects from misspellings” (which are not really redirects in de-wp), and individual categories can be added in one's monobook.js. I have no idea how to port this, but I miss its functionality here, so I hope it can be included in some way. -- Momotaro ( talk) 09:01, 1 July 2009 (UTC)
'Kategorie:Wikipedia:Falschschreibung' : {
className : 'bkl-link bkl-link-inner',
titleAppend : ' (Falschschreibung)',
htmlAppend : '<sup class="bkl-link-sup">FS</sup>'}
className
gives links to misspellings the proper CSS class, titleAppend
adds the label Falschschreibung to the tooltip and htmlAppend
puts a small FS next to the link.I think I do need help … I added importScript('User:Anomie/linkclassifier.js');
to my
monobook.js, emptied my cache, went to
Special:WhatLinksHere/John_Smith, from there to
British Honduras, but nothing is highlighted (both in Firefox and Internet Explorer). The same in some random new page,
[1], where all of the ship links point do disambiguation pages. I must be doing something wrong … but what? --
Momotaro (
talk)
05:48, 7 July 2009 (UTC)
Wikipedia:WikiProject User scripts/Scripts/Six tabs replaces the standard page — edit this page — discussion trio with a page — edit — hist — talk — edit — hist set of tabs for easier navigation to article or talk page edit and history pages regardless of current view. Makes things go much faster. – Drilnoth ( T • C • L) 02:43, 2 July 2009 (UTC)
(last one!) User:Tra/sidebartranslate.js translates interwiki links in the sidebar into English, so that instead of seeing the characters for Chinese, for example, you'll just see "Chinese". I've found this very helpful since I don't know the names of each language in the language, so this helps me quickly see what interwikis there are and which ones lead to what Wikipedia. – Drilnoth ( T • C • L) 02:45, 2 July 2009 (UTC)
Having an issue with reading the diffs myself due to red-green color blindness I've edited the style a little to make reading the diffs easier on the eyes. My redgreen.css -- Max Duchess ( talk) 15:13, 19 July 2009 (UTC)
FYI, there appears to have been a discussion regarding the most recent gadget (search engine choice) at Wikipedia:Village pump (proposals)#Changing the external searchengines on the searchpage. -- Ckatz chat spy 20:44, 25 July 2009 (UTC)
Since most ids of vector are now compatible again with monobook, I think we should remove it again. In my opinion it has served it's purpose (being handy for the first deployment fase) and any scripts that are not yet compatible should be fixed. — TheDJ ( talk • contribs) 21:07, 25 July 2009 (UTC)
Could we please import commons:MediaWiki:PermissionOTRS.js? -- John Vandenberg ( chat) 13:22, 6 August 2009 (UTC)
User:Drilnoth/rounded.css contains a script which rounds many of the corners in the user interface and generally prettifies the sidebar, cactions, footer, etc. I don't believe that it works in IE (haven't tried it, but it uses -moz styles), but if that's mentioned I don't think that it would be too big a deal. I think that this makes pages look much better and would make more sense as a gadget then as a standard script (namely, because many users who just want visually changes might not yet understand how script importing, etc. works). – Drilnoth ( T • C • L) 02:38, 2 July 2009 (UTC)
webkit-border-radius
and border-radius
? I'm not sure if all of the properties you use can be converted straight through to Webkit-proprietary and CSS3 properties, but border-radius, at the very least, will work fine (and no, it won't work in IE7 or lower - no idea about IE8, though). 「
ダイノガイ
千?!」
? ·
Talk⇒Dinoguy1000
19:52, 2 July 2009 (UTC)
I'd like a gadget that would take me to my favorite map site instead of taking me to toolserver.org's GeoHack page where I have to scroll down each time to click on the same link I want. -- Gpaper ( talk) 02:28, 9 September 2009 (UTC)
I have been asked to resubmit my proposal by TheDJ that my monobook.js be made a gadget on enwiki.
The javascript implements Google toolbar translation feature functionality on any webpage you go to on enwiki. It can be easily turned on and off (and language set) by a tab at the top of the window.
Hover the cursor over a word for 1.5 seconds and a popup appears with a translation of that word. All languages that google supports are offered. (43 at the moment)
Select text (up to 500 characters) and hover the cursor within the selected text, and the selected text will be translated within a popup window. Move the cursor again and the popup window disappears.
It was proposed four months ago and TheDJ evaluated it favorably and asked for some changes:
Yug expressed strong approval of the tool, and asked for some more changes:
Yug said he could use the tool everyday, and that he was more interested in the single word popup rather than the selected text feature, because he had taught himself English this way using the Google toolbar.
There are 10s of millions of intermediate English learners who regularly use enwiki who could use the tool like Yug does. He is an administrator on enwiki with the help of such tools as this.
This tool generalizes and extends the Google toolbar translation feature, which does single word translation from English to ten other languages. As good as it is, it does not currently do the other 30 languages that Google supports. English to Bulgarian, Romanian and Farsi are not supported yet. The Google toolbar also does NOT translate from French to English, Spanish to English etc (as the javascript proposed could also be used by other language wikis to allow English readers to view their wikis).
gTranslate is a Firefox addon that does allow translation for the full Google language set. It is only available on Firefox (whereas my javascript will work on IE, Firefox, Safari, Chrome, Opera and Epiphany (doesn't work on early versions of Konqueror that I have tested on, probably will work on later versions)). gTranslate takes a
Single quotes in gTranslate are translated with the html code ''' shown instead of '.
My javascript only needs the following to translate selected text
With single word translation you don't even have to select the text. The javascript has code within it that determines the word the cursor is over.
There has been quite a bit of coding put in the gadget so that large wiki files do not upset the javascript or tie it up. If the file is too big for processing (like 70,000 characters) then parts of the text will not have the popup effect enabled, but the javascript will not go into a expensive computation loop in this case.
Finally, an earlier version of this gadget has been working as a gadget on the Spanish Wikipedia for 10 months now, without incident. It does seem to be used moderately, and the implementor of the gadget told me on my talk page:
I am willing, if the tool becomes a gadget to include work within it that allows for the translation (and replacement of text) within input fields and textareas as well. This would allow easy communication between people who do not have a common language in the messages on people's talk pages.
Thanks for the time taken to read this proposal.
Endo999 ( talk) 16:55, 2 September 2009 (UTC)
I have done the changes Cacycle wanted. It is now necessary to hold the SHIFT key down to get the popup. This is a default option. You can turn it off by going to the Translations Popups Tab and turning the option off by clicking on the link regarding it. If you do that Popups happen just by hovering the cursor over a word or selected text.
Endo999 ( talk) 06:31, 3 September 2009 (UTC)
How about 'GoogleTrans', as it is Google that does the translations. Many people do know about the Google translation services. You are welcome to change the text in the code for this.
Endo999 ( talk) 08:58, 8 September 2009 (UTC)
The tool's name has been changed to GoogleTrans to stop it conflicting with navpopups. Thanks for the support Kingoomieiii. Your suggestions:
may not run the NavPopups gadget as well. So the need to be visually consistent with navpopups may not be necessary.
Endo999 ( talk) 20:51, 11 September 2009 (UTC)
The userscript has been moved to
User:Endo999/GoogleTrans.js (tool homepage:
User:Endo999/GoogleTrans, tool discussion page:
User_talk:Endo999/GoogleTrans). Please change your monobook.js loader to importScript("User:Endo999/GoogleTrans.js");
. Cacycle ( talk) 01:15, 12 September 2009 (UTC)