Thread:Pecoes/@comment-4674838-20121105085352/@comment-4674838-20121106032605

Nope, haven't tested Preferences yet. Mainly because I haven't been working on Railgun lately. In terms of integrating it with Preferences, I think I still need to do some other work first. I still need to integrate the Railgun modules, and add back in the show/hide siderail feature. Once that's done, I'll feel ready to integrate with Preferences.

The help page you've built for it is dauntingly long and scary though. The main problem I have with it is it's *API oriented*, whereas I'm trying to translate all that mumbo jumbo into *procedurally oriented* in my mind.
 * 1) Form Scripts are only active on Special:Scripts. The purpose of Form Scripts are to allow the end-users of your script to save their configuration options. (Interested in the specific technical details of how that "saving" happens behind the scenes? Read this other page, otherwise continue with the tutorial)
 * 2) How do you write a form script? Well you do X, Y and Z. If you want to do fancier stuff, read the API.
 * 3) Okay, so the user has saved some configuration options. So how does your script get access to the user's configuration options on non-Special:Script pages? Well you have to write a main script. The purpose of a main script is to allow your script to get access to the user's configuration options as raw data that you can do stuff with (for example, display their birthday on their profile page).
 * 4) How do you write a main script? Well you do A, B and C. If you want to do fancier stuff, read the API.
 * 5) Here's the full API (preferably isolated on a separate page, like Preferences/API)