Re: [DM-dev] Dungeon Rendering :)
Brought to you by:
acdalton,
henningsen
From: Stephan B. <ste...@ei...> - 2001-04-30 08:40:44
|
On Monday 30 April 2001 00:33, you wrote: > I would just design a file format that is easy to parse, (can be > edited by humans ???), and still can hold all the data we need. But I > get the feeling you are a perfectionist;-)=20 Only when I know others may see my code ;) > Still, with the > classloading stuff, I think you don't have to go that far.=20 Me, too. > Just > assume all the subclasses that people are going to use are all > compiled into the program. I mean, if someone writes a new subclass, > they are probably smart enough to be able to recompile the program > including their class? And anyway, we can include a nice set of > precompiled classes. That's also the conclusion I came to. > Remember to give doors the number 7;-) like in floor=3D0, wall=3D1, hig= h > wall=3D2,... door=3D7! Ah, yes, I forgot about that. I'll fix that tonight. > ???: If we have an interactive design program, the file does not even > have to be editable by humans as far as I'm concerned. And if it's > not edited by humans, you can let the file reading function fail for > any missing space or added comma or whatever (like I do anyway). Then > things shouldn't be so hard. I would, but it frustrates me to a) have a data file which I can't=20 hand-edit if I need to and b) one which may not work with the next=20 software version (and I can't hand-edit it to bring it up to spec). I'm=20 still deciding on the data format, but that part can wait a little=20 while while I clean up the rendering and such. I can currently save the=20 data, but the format isn't really one I can use to read back easily.=20 I've got to to simplify significantly before I can read it back. ----- 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 |