I'm thinking of disabling normal wiki account creation and instead offloading it to OpenID integration via an extension. Are there any here with any particular objections to OpenID as the wiki account mechanism?

How does that work, exactly? On some sites I've seen that you have to pass some sort of OpenID URL, in some other cases it was something with logging in...

The extension handles all the URL passing and such, I gather. MediaWiki's spam prevention doc recommends it, so there's probably something to it.

Given that there have been a few dozen spam registrations over the past couple of days, I'm temporarily disabling wiki registration until I can get this sorted out.

Ok, installed OpenID on the wiki. Apparently, it's been a while since I've seen OpenID in action, as I've completely forgotten until now that it also lets you choose to tie a Google account to it!

So this interface allows either manually passing an OpenID URL or choosing to tie another OpenID-enabled account (like a Google account) instead. Once you tie the account, THEN you can choose what you want your wiki username to be. For now I've disabled choosing an existing wiki username to tie with the OID acct, so @DaVince & @Flying Jester if you currently have trouble logging into the wiki let me know and I'll figure something out (will probably re-enable tying to an existing username for a small period of time in that case).

It looks like I can no longer use the wiki name 'Flying Jester', because I already registered that before. And I can't seem to log in with just my username and account I made for the wiki before.

@Jester - sent PM re accts.

New wiki topic - the following is a list of articles (and subsequently the links they contain) I'd consider higher priority than some other non-API articles:

Template:functemp (critical as of 2013/03-27; created 3-28 but lacking category template)
Template:objecttemp (critical as of 2013/03-27)

Sphere:Latest (archived at http://web.archive.org/web/20121031101209/http://spheredev.org/wiki/Sphere:Latest)
Script:Persist.js (archived at http://web.archive.org/web/20100621061805/http://www.spheredev.org/wiki/Persist.js) DONE!
Script:json.js (archived at http://web.archive.org/web/20100621060813/http://www.spheredev.org/wiki/Json.js) DONE!
Main Page (archived at http://web.archive.org/web/20121011104106/http://spheredev.org/wiki/Main_Page; the content isn't necessarily essential, but for me the layout kinda is; eh, maybe the content too)
Higher-order programming in JS (archived at http://web.archive.org/web/20120828191718/http://www.spheredev.org/wiki/Higher-order_programming_in_JavaScript)
Battle System Tutorial by Flik (archived at http://web.archive.org/web/20120811000937/http://spheredev.org/wiki/Battle_System_Tutorial_by_Flik)
Battle System Tutorial by Radnen (archived at http://web.archive.org/web/20120414032626/http://www.spheredev.org/wiki/Battle_System_Tutorial_by_Radnen)

list of tutorials archived at http://web.archive.org/web/20120901210809/http://www.spheredev.org/wiki/Category:Tutorials

Also, I've created a template called "section" for marking out a colored box with what amounts to aside or warning text.

Alsoalso, for future reference and convenience for me, a possible todo list:

https://meta.wikimedia.org/wiki/Music_markup
http://www.mediawiki.org/wiki/Manual:Math
http://www.mediawiki.org/wiki/Extension:Math (specifically, http://www.mediawiki.org/wiki/Extension:Math#MathJax)
possibly http://www.mediawiki.org/wiki/Manual:Enable_TeX

2013/03-27 - waiting on response from original author re adding http://www.extentofthejam.com/pseudo/ to the wiki...
2013/03-28 - added MgOpen Modata & League Gothic webfont styling to wiki headings
2013/04-06 - added gist extension to wiki; can now embed a gist by <gist>GIST_ID</gist>
2013/04-20 - added CodeEditor extension to wiki; JS & CSS editors (eg, your personal CSS and JS) are now syntax highlighted
2013/05-31 - finished restoring kamatsu's Understanding musical theory article, but need missing linked files
2013/06-03 - restored persist.js and json.js articles, persist demo now hosted on Spherical's GDrive.

Request: can someone with more consistent internet and a bit more time get all the SVGs from https://commons.wikimedia.org/wiki/Category:Musical_score_components_(2) (885 in total it seems) and upload them to the wiki under their same name? I want the music score template I copied to actually work if we can't get some sort of musictex happening, thanks.

NOTICE: I'd like to institute a new wiki article convention. For articles regarding Sphere API, if the function or variable in question belongs to a Sphere object (eg, Sound.play() ) the article's title should be API:Object/member (with member being in its proper case, eg API:Sound/play). Anyone who knows wikitext will realize this makes the article a sub-page of the Object article, eg Sound/play is a sub-page of the Sound article.

Sound

Sound.play


Also! I added a new template, Usage, that should be used for marking up a Sphere function's example usage. Visit Sound.play for an example, and if you need multiple usages in an article let me know and I'll show you how to mark it up.

LoadWindowStyle, edited to use the Usage template

I made a sound.isPlaying page: http://wiki.spheredev.org/API:Sound/isPlaying

The usage displays a bit weird, since it has no parameters.

Also, the new API: convention means we have to switch over sll others to use it right? The Functions page doesn't use this convention so someone would have to go through and edit all of the links. 

I'll fix the template, that's mainly me forgetting to fix the default for the params argument. (edit - fixed)

Re the API: convention, yes that does mean someone or someones plural would have to go through the Functions page and edit links. Block by block is probably the best way to handle it and I'll make a small dent in it right now in a few of the Objects to reduce some of that work.

edit: finished editing the links for the Objects in the Functions page. Also fixed/redirected existing functions that weren't taken care of previously.

Added a navbox template; see http://wiki.spheredev.org/Template:Mario_franchise for a sample navbox and http://wiki.spheredev.org/MediaWiki:Sandbox for transclusion.

The navbox template is mainly for an alternate organization of Functions that subdivides them to be handled more independently of each other. When you write a function page, you'd put the navbox of that function's section at the footer, eg Image.blit would have the Image navbox at the bottom. I feel it's going to become very useful in the future.

edit - also split out the Objects on the Functions page into separate pages transcluded into it; I highly recommend following suit with the other sections on that page as well.

Restored tung's Git for the lazy article since apparently it has importance beyond Sphere usage and Wayback Machine failed when attempting to archive it on May 12th.

New documentation conventions!

I finished converting all the links on the Functions page to now point to the API namespace properly. I've also started filling in a few pages myself. A particular change to note is how I've set up the system scripts to be linked.

Visit the system scripts article and you'll notice that not only does it now redirect to "Script:System" but also all the system scripts are linked as subpages; "menu.js" becomes "Script:System/menu.js" and so on. Visit the Wayback Machine version of the article to get links to the original script articles for restoration and cleanup.

I've also updated the wiki's syntax highlighter to once again highlight Sphere functions and link them to wiki articles. I'm updating the list as I go but for now I don't give special treatment to methods of Sphere objects, so only unattached functions like "GetVersion" get linked. If I figure out a way without basically writing my own JS parser to differentiate methods so that a "clone" method links appropriately to Image.clone or Font.clone then I'll add those, but until then they're left being highlighted as non-linked object members according to the existing highlight rules.

There are almost 400 API articles that need to be restored/written. Can someone besides myself start tackling that please?

I'll try to pitch in a few every once in a while, but I'm super busy. Spherical is tertiary on my priority list.

But also the wiki is kinda slow loading, so it takes a while to edit a new page.