Jump to content

User talk:The Transhumanist/ScriptCreator.js

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by The Transhumanist (talk | contribs) at 04:24, 2 December 2017 (Bodyguard function: transclude template). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
I'm using this page as a workspace. The talk page portion of it starts at #Discussions, below.

(Script under development - not yet functional)

When completed, this script will prompt for a title, then it will create a script page and accompanying workshop page using that title, using standard templates via substitution.

Script's workshop

This is the work area for developing the script and its documentation. The talk page portion of this page starts at #Discussions, below.

Description / instruction manual

(Script under development - not yet functional)

CreateScript.js = Create new script page, and corresponding workshop page.

When completed, this script will prompt for a title, then it will create a script page and accompanying workshop page using that title, using standard templates via substitution.

Explanatory notes

This section explains the source code, in detail.

You can only use so many comments in the source code before you start to choke or bury the programming itself. So, I've put short summaries in the source code, and have provided in-depth explanations here. My intention is twofold:

  1. to thoroughly document the script so that even relatively new JavaScript beginners can understand what it does.
  2. to refresh my memory of exactly how the script works, such as if I don't look at the source code for weeks or months.

The explanatory notes include examples, and links to relevant documentation pages, tutorials, etc.

In addition to some standard JavaScript code, this script also relies heavily on the jQuery library.

If you have any questions, feel free to ask me at the bottom of this page under Discussions. Trying to answer them will help me learn JavaScript better.

Quick walk-through

Aliases

An alias is one string defined to mean another. Another term for "alias" is "shortcut". In the script, the following aliases are used:

$ is the alias for jQuery (the jQuery library)

mw is the alias for mediawiki (the mediawiki library)

These two aliases are set up like this:

( function ( mw, $ ) {}( mediaWiki, jQuery ) );

That also happens to be a "bodyguard function", which is explained in the section below...

Bodyguard function

The bodyguard function assigns an alias for a name within the function, and reserves that alias for that purpose only. For example, if you want "t" to be interpreted only as "transhumanist".

Since the script uses jQuery, we want to defend jQuery's alias, the "$". The bodyguard function makes it so that "$" means only "jQuery" inside the function, even if it means something else outside the function. That is, it prevents other javascript libraries from overwriting the $() shortcut for jQuery within the function. It does this via scoping.

The bodyguard function is used like a wrapper, with the alias-containing source code inside it, typically, wrapping the whole rest of the script. Here's what a jQuery bodyguard function looks like:

1 ( function($) {
2     // you put the body of the script here
3 } ) ( jQuery );

See also: bodyguard function solution.

To extend that to lock in "mw" to mean "mediawiki", use the following (this is what the script uses):

1 ( function(mw, $) {
2     // you put the body of the script here
3 } ) (mediawiki, jQuery);

For the best explanation of the bodyguard function I've found so far, see: Solving "$(document).ready is not a function" and other problems   (Long live Spartacus!)

The ready() event listener/handler

The ready() event listener/handler makes the rest of the script wait until the page (and its DOM) is loaded and ready to be worked on. If the script tries to do its thing before the page is loaded, there won't be anywhere for it to place the menu item (mw.util.addPortletLink), and the script will fail.

It looks like this: $( document ).ready() {});

The part of the script that is being made to wait goes inside the curly brackets (starting on the next line, with the ending curly bracket, closing parenthesis, and semicolon following that on a line of their own).

See also: http://docs.jquery.com/Tutorials:Introducing_$(document).ready()

The jQuery shorthand version of the same thing looks like this:

1 $(function() {<br>
2     // Handler for .ready() called.<br>
3 });

This is explained further on the jQuery page for .ready()

Change log

Task list

Bugs

Desired features

Completed features

Development notes

Trycatch needed

The Transhumanist, where you use local storage.getItem() or setItem() you should always wrap that in try catch, as it can fail at any moment (even if you checked previously). This can be due to the browser running out of storage space for the domain, or because the browser is running in privacy mode or with an ad blocker extensions or something. Also, your new RegExp() calls should be lifted outside of the for loops, so that they aren't continuously recreated. For wpTextbox1.value, realise that sometimes the content might be managed by an editor (The syntaxhighlighting beta does this for instance). We use the jquery.textSelection plugin to abstract way from these differences. Don't check document.title, check mw.config.get( 'wgTitle' ) or mw.config.get( 'wgPageName' ). And when you use mw.util.addPortlink, you have to ensure that the mediawiki.util plugin is loaded already, which you can do by using mw.loader.using. —TheDJ (talkcontribs) 14:47, 27 October 2017 (UTC)[reply]

Steps

  • should not work if on an edit page - done
  • should only work after a menu item is clicked - done
  • Declare a variable for script's mode
  • Declare a variable for script page title
  • Declare a variable for script's talk page title
  • Prompt for script title
    • Specify script title, then press enter.
  • Set script title variable
  • Set script talk page title variable
  • If script page exists, skip this section
  • Create script page in edit mode
  • Add script template
  • Manual save?
  • If script talk page exists, clear local storage and terminate script
  • Create script talk page in edit mode
  • Add talk page template
  • Manual save?

Rough rough talk-through

The script runs on every page you open. It checks its localstorage for mode, to see what it should do.

The mode will tell it whether to create script page, create workshop page, or be in neutral mode.

In neutral mode, the menu item is available if you are not on an edit page. When you click the button, the script asks you for the name of the script you wish to create.

Once you've specified a title, the script then puts itself it into create script mode, and opens an edit page.

It detects it is in create script mode, and uses template substitution to insert the script.

When done, it changes to script inserted mode, and prompts user to check and save the page.

Once saved, it detects it is in script inserted mode, changes the mode to create workshop mode, and opens an edit page.

It detects it is in create workshop mode, and uses template substitution to insert the workshop.

When done, it changes to workshop inserted mode, and prompts user to check and save the page.

Once saved, it detects it is in workshop inserted mode, and changes to neutral mode.

Script dependencies

Discussions