🚀 go-pugleaf

	I've gotten my sprite routines to work ok, and can now lay
them down in a tiled format map, with the success of Ultima 4 or so
(ie., ugly blocky icons).
	All these icons and the map were stored in the format
const
	map : array [0..maxX,0..maxY] of byte =
	( (00,00,00,00),
	  (00,00,00,00),
	  (00,00,00,00)
	);

	Hopefully you understand the concept - they're hard coded and fixed
length. And now i'm looking for ease-of-use improvements in productivity
tools like map and icon editor.
	(ok, the icon editor is actually up in the air, because i need
to figure out hot to store icons to disk in planar format and still
read them back).
	So what is a decent idea for a map editor, and storing maps?
While I'm willing to hard code a map by hand, i don't know how to
see what it'd look like without loading it.
	And most importantly, Should I Be Defining It This Way?
	Specifically, If i have a routine DrawMap (Var Map : MapType)
then EVERY map has to be the same size!!!
	In ultima (Vampyr is better i think) you can go in castles that
are small, houses that are tiny, and the world map which is huge.
	Would I do something like 
var
	WorldMap,House1,Castle1,House2,Cave1,etc  : MapType;  

and just keep a length field to it's MaxX and MaxY? Keep several
MapTypes (diff sized arrays) and seperate procedures to display them? 
It just seems that any time someone descends into a new place i either
generate alot of waste or lot of headache.

	So any of you ever write or come close to finishing an Ultima/Tile
type game? Where did you guys have problems?
	Any help would be appreciated. Maybe I'll just go back to the 
assembler sprite routines....
						- baylor