I would especially appreciate
comments on the following points, but welcome all comments (positive or
otherwise).
Please
have a look at the status page. There is a style
question there, to which I would appreciate feedback.
First release:I
have aimed for something that works, even if it's a little kludgey, and
can generate code, then will round of the rough edges in subsequent releases.
Major point of philosophy - internally,
I previously represented all 'objects' as either a room, item or actor.
Of course, TADS allows us to create mixtures of these (a spaceship, or intelligent
car, which can speak to you is a vehicle (hence a room) and an actor; a kangaroo
is an actor, but it's pouch might be a room, etc.). I have removed this internal
representation; should I also remove the separate room/item/actor tabs? I
have kept these - for instance, the kangaroo would accessible over both the
room and the actor tabs. Since this greatly affects the visual appearance
and the operation of the program, I would like your opinion of this.
Language: I
have chosen to make the first version generate TADS code. I am sure that
that will annoy a lot of Inform aficionados (are they called Informers?).
I may allow myself to be influenced by feedback. The goal is to have a
future version which supports both, but this will most likely take years
to materialize.
Acronym: my tools generally have
cryptic acronyms. I can never aspire to the heights of GNU (GNU's not Unix)
or the scanner software TWAIN (Tool Without An Interesting Name). Nevertheless,
I would like something impressive here. I'd prefer something that fits with
PLUGH, but will accept another if it is superior. The best (but not very impressive
that I can come up with so far is Programming Labyrinths, Using Graphical
Help). Please feel free to suggest something (or maybe even a new name).
Operation: how should the whole
thing actually work in operation? Is there anything implemented which bothers
you? Does there seem to be something missing? I realize that this is subjective,
so will try to implement an amalgam of feedback or offer configuration options.
Graphics & sounds. Anyone
care to contribute any, or a logo? I'm a coder, not an artist. I can foresee
a splash screen in the program & maybe a few good graphics on the site,
without going overboard & bloating the code or web site.
Aids to the development process.
The to-do page foresees a to-do list & a means of representing the plot
development (order of puzzles). How should these look & operate?