Zzot!

I’ve been working on this, off and on, for a while now. In theory, it shouldn’t be that big of a thing to make a simple roommaker. Reality, of course, is another matter. Here’s a screen cap of my prototype, and some related details the image doesn’t really convey:

• The data is stored in a custom XML markup language.
• The tool I’m designing would be incapable of reading or writing LPC — the
  mudlib takes care of that (or, if you want to extend the loader object, you
  just inherit the XMLRoom object).
• It is designed as a web application that directly handles the XML markup.
  Because of this:
  • The read/write gateway (a server-side PHP script) will need to do some
    validation (it doesn’t yet).
  • It requires a modern-ish browser with an implementation of
    XMLHttpRequest and JavaScript enabled.
  • There’s no SOAP or XML-RPC going on — it is just a simple REST API.

If anyone wants to know more, let me know. At the moment, this more closely resembles a mock-up than a prototype, so there’s nothing anyone can interact with yet. The corresponding markup is in the extended entry.

Update: No, it isn’t. What was in the extended entry got lost somewhere, so I deleted the mess that remained.

IgorMUD | Permalink | No Comments

This entry exists only because I refuse to spend any more time figuring out how to force a category archive to be rebuilt when it has no entries in it (as I write this, the only entries are in child categories). Move along now…

Projects | Permalink | No Comments

Regular LPC objects are loaded from an LPC source file — these new objects are loaded from a source file, but not an LPC one (and not named whatever.c). This makes the object loading path more complicated, so here’s an attempt to put a few of us on the same page.

This is obviously a first draft, scribbled down quickly so we have something to discuss. Let me hear any thoughts you might have.

Continue reading…

IgorMUD | Permalink | No Comments

For the time being, this project has lame version numbers. If enough versions ever get created to make this a problem, I’ll change that. For now, they’re just sequential. I’ve only tested this on my Nokia 6600, and have little intent if any to make corrections for other handsets which I don’t own. Your mileage may vary.

Here are the things I already know are broken with this:

• One of the two tabs variations has a stray blue line
• The grayed out bar at the bottom (behind left- and right-button text) is the wrong height by a couple of pixels.
• In one of the modes, that same bar is grayed out twice, which doesn’t just look odd on its own, it’s made worse by the preceding item.
• The above not withstanding, just the tabs, status bar at the top (where the date is displayed) and the signal and battery indicators have been done — everything else is still blue, and looks slightly out of place.

Out of little more than idle curiosity, let me know if you actually use this.

Download Peppers_v3.sis

Series 60 Theme | Permalink | No Comments