I'm used to writing programs that consist of a fair number of object "classes", with multiple objects, messages between them, and the like. I've written programs in procedural languages, using lots of small functions. Most RL programming languages provide some way of managing the program in pieces. In LSL, I found myself writing programs that... Continue Reading →
Lesson Learned: Code Repository
As we worked to get the Alpine Executive Center up and running, we made new versions of a lot of scripts. It wasn't just a matter of dragging and dropping existing scripts in, although in retrospect it could have been more like that than it was. But even if we had done the very best... Continue Reading →
Lesson Learned: Single Builder
On our installation of our vehicle technology at the Alpine Executive Center, Dizzi and I both worked on things. Dizzi made the routes, which are represented in notecards. She put scripts into the cog rail and tested it and built a rezzer for it at one point. (Now that I think of it, she did... Continue Reading →
Intention and Code Improvement
The Piano of Damocles is one piece of my long-delayed Engines of Destruction series. It is an upright piano that hangs in the air over someone's head, following them around if necessary. At my command, it can drop from the sky, hit them on the head, and explode into bits. True art, I'm sure of... Continue Reading →
Packaging a Product
I'm thinking about how to package up our wonderful new vehicles. Here are my thoughts so that I won't lose them. I'm happy to share them with you and hope they'll give you good ideas. If you have ideas better than mine, please comment. Dizzi and I have been working on a number of vehicles... Continue Reading →