This post serves as a starting point for all discussions around missing documentaton and reference pages. Questions about how these shall be written and where to start will be answered here.
Maybe you should give some exemples with your reference, just like processing, because it's an easier way to understand the language.
Scriptographer is more powerful than processing to make graphics, but we can learn very quickly with their exemples.
If you have the time...
Best regards
A.
For a wonderful model on how learning can be approached, I think luxology has done an incredible job with Modo and it's because of two things.
Active Forums and Luxology.tv
Luxology.tv is a series of "modcasts" that are released regularly. Each one is includes video tutorials which are incredibly useful at getting people to actually learn. It might take longer to watch a video but the visual aspect is compelling and with all the new podcasting software it's become pretty simple to do this.
I'm coming from a background in C# and Generative Components (Architectural Form Generation) as well as strong ArchViz. I had actually never realized that Illustrator allowed generative scripting but I must say I'm thrilled by the work you've done so far!!!! Afternow resembles a still image I created a while back in Maya. It took me a few days to get right and at the end I was only left with that one product. It's exciting to see you scripted something so beautifully done but what's also great is how beautifully illustrator can render vectors, I really see a big difference.
So what I meant to say was that if I can get my feet wet in Scriptographer and pick up the scripting quickly enough I'd be happy to start working on video tutorials to help support the community.
But, as most of us already know, the real key to any language or interface is the community using it. A strong support system goes longer than a strong language.