This is the
talk page for discussing improvements to the
WikiProject JavaScript page. |
|
Archives: 1 |
JavaScript NA‑class | |||||||
|
|
|
Feel free to share the details of your user script projects, your problems, your ideas, and your JavaScript-related technological fantasies on this page. :) The Transhumanist 01:10, 14 April 2017 (UTC)
You are invited to join the discussion at Wikipedia:Village pump (technical)#Creating and saving a preloaded page with one click. {{u| Sdkb}} talk 19:42, 14 June 2020 (UTC)
I'm looking to build a userscript the interacts with a template call, and I was hoping that there's another one out there that I can see how this functionality works. Specifically, I want the userscript to do the following:
Does anyone know of a userscript that does something like this, or a set of userscripts that together do all of these functions? Am I completely crazy thinking this is even possible? It's been about 20 years since I last programmed anything in javascript, so I'm very much looking for a place to start connecting the dots again. Thanks for any help you have. Van Isaac WS cont 18:28, 24 June 2020 (UTC)
A little late, but is it supposed to scroll down to where the template is and open up a screen, then load the parameters?
00:37, 15 January 2023 (UTC)
Hello all. I have made a proposal over at the village pump which you may be interested in regarding user scripts. See Wikipedia:Village_pump_(proposals)#Proposal_regarding_a_user_script_approval_process Ed6767 talk! 02:29, 26 June 2020 (UTC)
Anyone know how I can authenticate a request from a user script to a Toolforge tool? I'm not sure OAuth would work, since I figure that uses cookies (but I would be happy to be wrong about that). I could always have the user script make an edit or a log entry and pass the diff/log entry ID with the request, but that seems spammy. Enterprisey ( talk!) 07:12, 3 July 2020 (UTC)
The RedWarn team is currently in the process of renaming to Ultraviolet. Some documentation pages are still in the process of being written/transferred. Read the announcement here. |
Part of Wikipedia user scripts |
|
Ultraviolet is a new, fast-growing JavaScript counter-vandalism tool, specifically designed for user friendliness. Ultraviolet has gained over 200 new users and is rapidly growing every day. So far, 40,000+ edits have been made with the tool. Thanks to your help, Ultraviolet is now backed by a team of hard-working and trusted volunteers. If you'd like to join us, you don't need to be a genius, or have any major experience to volunteer — and, to be cliche, it may even be a great thing to put on your resume. Engaging in Ultraviolet's development is a good way to get your work in use by hundreds of editors across the globe. If you've had any JavaScript, PHP, HTML, CSS, design, translation, counter-vandalism, or other experience that would aid in Ultraviolet's development, your contributions would be highly valued!
- Ed6767 talk! 15:09, 15 July 2020 (UTC)
It's not uncommon to need to restore a discussion from a talk venue archive, but it's not easy to do it correctly and exceeds the ability of many editors. I wonder if anyone would be interested in creating a restore-from-archive script modeled after OneClickArchiver. Instead of clicking an "Archive" link on a talk page, one would click a "Restore" link on an archive page. The coding would be a little simpler than OneClickArchiver, which has to worry about whether it's time to create a new archive page. Any taker? ― Mandruss ☎ 22:08, 27 November 2020 (UTC)
I would love to contribute code to wikipedia, but I'm once again failing at the same obstacle I did 6 months ago. Wikimedia is geared to a now over 10 years old version of JavaScript. Let's put that in perspective: Wikimedia is geared to a version of JavaScript that's that was released the same year as Windows 7! Back then I was barely a teenager. JQuery is now not much more than a relic, and all it does now is encouraging sloppy code-style and making debugging a lot harder. Combine this with the relatively large API of Wikimedia and the complete lack of modern comforts like Intellisense and TypeScript it becomes nearly unsurmountable to produce a functional script while keeping your sanity for someone who has become accustomed to the modern ways.
There is sadly no easy way to remedy this... The changes necessary would be large enough to warrant an essentially total rewrite of the MediaWiki software. And while this would open up some awesome opportunities, I won't blame anyone breaking out in cold sweat when they just imagine it.
Any opinions on this? SkSlick ( talk) 01:08, 13 December 2020 (UTC)
mw
, we've had to place whatever we need in a
declaration file that has been expanding even more and more as progress goes on. I've tried to automatically grab the types based on the provided JSDoc inside of the source, but to no avail, as it it extremely complicated to do so. Since a rewrite of MediaWiki's JavaScript parts is (unfortunately) out of the question (unless WMF wants to spend some funds to make that happen), we've had to deal with this old and clunky method. My best advice would be to have the
MW JS documentation at hand whenever making scripts, and just rely on your best senses to see which goes with which. Sure, it's a strong timesink, but once you're used to the extremely old and aging JavaScript codebase, it shouldn't really be a problem. Babel/TS transpilers don't sound that bad, but that might raise some security or performance issues. I guess the only way to find out if that's the case would be to actually bring that suggestion to the Phab. But if there's anything that Wikipedia has taught me about its developers, it's that there's a lot of people who are overly attached to old processes and tech, and that introducing changes as big as these (especially when it uses newer technologies) is commonly met with a lot of criticism.
Chlod (
say hi!) 17:31, 13 December 2020 (UTC)
The Mediawiki:Clearyourcache message should link "scripts" to WP:US. I made a proposal at Template talk:Script doc auto#Proposal: link to WP:US. Enterprisey ( talk!) 21:50, 13 December 2020 (UTC)
A requested move discussion has been initiated for React (web framework) to be moved to React (JavaScript library). This page is of interest to this WikiProject and interested members may want to participate in the discussion here. — RMCD bot 11:36, 31 January 2021 (UTC)
A requested move discussion has been initiated for CSS framework to be moved to CSS Framework. This page is of interest to this WikiProject and interested members may want to participate in the discussion here. — RMCD bot 10:18, 11 June 2021 (UTC)
You are invited to join the discussion at WP:VPIL § Bold idea: the Generic Queue Toolkit. Enterprisey ( talk!) 07:12, 11 August 2021 (UTC) Enterprisey ( talk!) 07:12, 11 August 2021 (UTC)
Hi there! I am going to suggest moving these user script "snippets" formerly managed by WikiProject User scripts to be migrated to user space. This brings multiple advantages, but mainly improves security (they would be interface-admin protected essentially), and readability / ease-of-use (the pages that are not currently marked as JS in terms of content model would be able to be installed using scripts like scriptinstaller). 🐶 EpicPupper (he/him | talk) 19:13, 13 March 2022 (UTC)
A requested move discussion has been initiated for Npm (software) to be moved to npm. This page is of interest to this WikiProject and interested members may want to participate in the discussion here. — RMCD bot 10:03, 27 June 2023 (UTC)
Just found this wikiproject so here's the link to the Technical post explaining my issue. Vghfr ( talk) 04:22, 22 January 2024 (UTC)
You are invited to join the discussion at Wikipedia talk:User scripts § Preview edits by a userscript. — andrybak ( talk) 19:34, 10 February 2024 (UTC)
This is the
talk page for discussing improvements to the
WikiProject JavaScript page. |
|
Archives: 1 |
JavaScript NA‑class | |||||||
|
|
|
Feel free to share the details of your user script projects, your problems, your ideas, and your JavaScript-related technological fantasies on this page. :) The Transhumanist 01:10, 14 April 2017 (UTC)
You are invited to join the discussion at Wikipedia:Village pump (technical)#Creating and saving a preloaded page with one click. {{u| Sdkb}} talk 19:42, 14 June 2020 (UTC)
I'm looking to build a userscript the interacts with a template call, and I was hoping that there's another one out there that I can see how this functionality works. Specifically, I want the userscript to do the following:
Does anyone know of a userscript that does something like this, or a set of userscripts that together do all of these functions? Am I completely crazy thinking this is even possible? It's been about 20 years since I last programmed anything in javascript, so I'm very much looking for a place to start connecting the dots again. Thanks for any help you have. Van Isaac WS cont 18:28, 24 June 2020 (UTC)
A little late, but is it supposed to scroll down to where the template is and open up a screen, then load the parameters?
00:37, 15 January 2023 (UTC)
Hello all. I have made a proposal over at the village pump which you may be interested in regarding user scripts. See Wikipedia:Village_pump_(proposals)#Proposal_regarding_a_user_script_approval_process Ed6767 talk! 02:29, 26 June 2020 (UTC)
Anyone know how I can authenticate a request from a user script to a Toolforge tool? I'm not sure OAuth would work, since I figure that uses cookies (but I would be happy to be wrong about that). I could always have the user script make an edit or a log entry and pass the diff/log entry ID with the request, but that seems spammy. Enterprisey ( talk!) 07:12, 3 July 2020 (UTC)
The RedWarn team is currently in the process of renaming to Ultraviolet. Some documentation pages are still in the process of being written/transferred. Read the announcement here. |
Part of Wikipedia user scripts |
|
Ultraviolet is a new, fast-growing JavaScript counter-vandalism tool, specifically designed for user friendliness. Ultraviolet has gained over 200 new users and is rapidly growing every day. So far, 40,000+ edits have been made with the tool. Thanks to your help, Ultraviolet is now backed by a team of hard-working and trusted volunteers. If you'd like to join us, you don't need to be a genius, or have any major experience to volunteer — and, to be cliche, it may even be a great thing to put on your resume. Engaging in Ultraviolet's development is a good way to get your work in use by hundreds of editors across the globe. If you've had any JavaScript, PHP, HTML, CSS, design, translation, counter-vandalism, or other experience that would aid in Ultraviolet's development, your contributions would be highly valued!
- Ed6767 talk! 15:09, 15 July 2020 (UTC)
It's not uncommon to need to restore a discussion from a talk venue archive, but it's not easy to do it correctly and exceeds the ability of many editors. I wonder if anyone would be interested in creating a restore-from-archive script modeled after OneClickArchiver. Instead of clicking an "Archive" link on a talk page, one would click a "Restore" link on an archive page. The coding would be a little simpler than OneClickArchiver, which has to worry about whether it's time to create a new archive page. Any taker? ― Mandruss ☎ 22:08, 27 November 2020 (UTC)
I would love to contribute code to wikipedia, but I'm once again failing at the same obstacle I did 6 months ago. Wikimedia is geared to a now over 10 years old version of JavaScript. Let's put that in perspective: Wikimedia is geared to a version of JavaScript that's that was released the same year as Windows 7! Back then I was barely a teenager. JQuery is now not much more than a relic, and all it does now is encouraging sloppy code-style and making debugging a lot harder. Combine this with the relatively large API of Wikimedia and the complete lack of modern comforts like Intellisense and TypeScript it becomes nearly unsurmountable to produce a functional script while keeping your sanity for someone who has become accustomed to the modern ways.
There is sadly no easy way to remedy this... The changes necessary would be large enough to warrant an essentially total rewrite of the MediaWiki software. And while this would open up some awesome opportunities, I won't blame anyone breaking out in cold sweat when they just imagine it.
Any opinions on this? SkSlick ( talk) 01:08, 13 December 2020 (UTC)
mw
, we've had to place whatever we need in a
declaration file that has been expanding even more and more as progress goes on. I've tried to automatically grab the types based on the provided JSDoc inside of the source, but to no avail, as it it extremely complicated to do so. Since a rewrite of MediaWiki's JavaScript parts is (unfortunately) out of the question (unless WMF wants to spend some funds to make that happen), we've had to deal with this old and clunky method. My best advice would be to have the
MW JS documentation at hand whenever making scripts, and just rely on your best senses to see which goes with which. Sure, it's a strong timesink, but once you're used to the extremely old and aging JavaScript codebase, it shouldn't really be a problem. Babel/TS transpilers don't sound that bad, but that might raise some security or performance issues. I guess the only way to find out if that's the case would be to actually bring that suggestion to the Phab. But if there's anything that Wikipedia has taught me about its developers, it's that there's a lot of people who are overly attached to old processes and tech, and that introducing changes as big as these (especially when it uses newer technologies) is commonly met with a lot of criticism.
Chlod (
say hi!) 17:31, 13 December 2020 (UTC)
The Mediawiki:Clearyourcache message should link "scripts" to WP:US. I made a proposal at Template talk:Script doc auto#Proposal: link to WP:US. Enterprisey ( talk!) 21:50, 13 December 2020 (UTC)
A requested move discussion has been initiated for React (web framework) to be moved to React (JavaScript library). This page is of interest to this WikiProject and interested members may want to participate in the discussion here. — RMCD bot 11:36, 31 January 2021 (UTC)
A requested move discussion has been initiated for CSS framework to be moved to CSS Framework. This page is of interest to this WikiProject and interested members may want to participate in the discussion here. — RMCD bot 10:18, 11 June 2021 (UTC)
You are invited to join the discussion at WP:VPIL § Bold idea: the Generic Queue Toolkit. Enterprisey ( talk!) 07:12, 11 August 2021 (UTC) Enterprisey ( talk!) 07:12, 11 August 2021 (UTC)
Hi there! I am going to suggest moving these user script "snippets" formerly managed by WikiProject User scripts to be migrated to user space. This brings multiple advantages, but mainly improves security (they would be interface-admin protected essentially), and readability / ease-of-use (the pages that are not currently marked as JS in terms of content model would be able to be installed using scripts like scriptinstaller). 🐶 EpicPupper (he/him | talk) 19:13, 13 March 2022 (UTC)
A requested move discussion has been initiated for Npm (software) to be moved to npm. This page is of interest to this WikiProject and interested members may want to participate in the discussion here. — RMCD bot 10:03, 27 June 2023 (UTC)
Just found this wikiproject so here's the link to the Technical post explaining my issue. Vghfr ( talk) 04:22, 22 January 2024 (UTC)
You are invited to join the discussion at Wikipedia talk:User scripts § Preview edits by a userscript. — andrybak ( talk) 19:34, 10 February 2024 (UTC)