And I had a momentary brain cramp since I *did* know about the Wiki! While a nice, thousand page bound doc like some of my CGI books would have a certain tangible comfort, they would be a static product and difficult to keep current with something as fluid as X-Plane. The Wiki is here: http://wiki.x-plane.com/ for those that don’t know. And Ben, I’m sorry for hijacking a bit. As it happens, I’m pretty jazzed about this particular blog entry because, if I read you right, this will remove my need to bake lighting into my 3D cockpit.

LOL that’s okay – probably others don’t realize too. Heck, it took a while to make MediaWiki look so un-wiki-ful. 🙂

And I’ve just registered. Oh gosh. Sorry for that. I was blind. °_°

Wait – we already have a wik….wiki.x-plane.com!

You’re right about a centralized point of documentation for developers. Actually I think a public Wiki could be of use. Or making parts of the Xplane.org wiki public so the burden of writing documentation would be shared with the community? The devs/XP stuff could still do corrections. But everyone who knows another piece of the puzzle could contribute.

I just didn’t get the concept early enough to try it. And I’m so glad that was the case 🙂

I didn’t mention that in the original design goals, but actually there was one more item on the feature list for regions:

7. Annoy vonhinx.

If there’s some other feature that also does that, perhaps we can phase out panel regions. 🙂

All 4 paths for v10 – if we were going to drop a path, we’d have to do it slowly and wean people off of it, which we haven’t started doing yet. But we might, for example, make it difficult to author new content with an “incorrect” path via Plane-Maker warnings.