[DM-dev] current design state:

[Stephan B. <ste...@ei...>]

I've made some heavy changes to the heirarchy in DM, and I'm sure I'm=20
not done tweaking it yet. The heirarchy currently looks like this:


DMProperties -> DungeonElement -> (Room,Wall...)

DMProperties provides the basic properties storage and load/save=20
support. This can be replaced or added to later to write binary data,=20
for example.

DungeonElement is a base class for... dungeon elements. Each can=20
contain an arbitrary number of other DungeonElements, and recursively=20
saves them when it's asked to save. You can remove elements, etc., as=20
well.

Loading is broken right now because of these changes. I will make=20
several changes to saving to support this heirarchy, and hopefully will=20
be able to support arbitrarily-deeply-nested saving/loading. This=20
feature is a limitation of the data format, and not the objects, which=20
already can have any number of children going any number of levels dee.

I expect that it'll be Saturday or Sunday before I'm happy with the=20
class heirarchy, but it's getting there.

Of this heirarchy, the typical user would normally only use Room, Wall,=20
etc. The others provide all of the common functionality and to provide=20
a common framework for the data storage and internal representation.

----- Stephan Beal
Generic Universal Computer Guy
ste...@ei... - http://www.einsurance.de
Office: +49 (89) 552 92 862   Handy: +49 (179) 211 97 67
"Belief makes a hollow place. Something has to roll in to fill it."
-- Terry Pratchet