Perun
Public Area Guest
Issa (Vis) [1:76:24]
Posts: 2,506
|
Post by Perun on Mar 17, 2004 22:59:11 GMT
|
|
|
Post by Old Shendemiar on Mar 18, 2004 2:57:36 GMT
UUUUUUHHH!!!!
The SQL map exporter wizard is giving me a hardon! ;D
I can output my database as a image with gdlib and open it with this, and have the changes as sql commands! UUUH!
|
|
|
Post by sparrowhawk on Mar 18, 2004 9:11:10 GMT
You finns get turned on by the oddest things...
;D
|
|
|
Post by sparrowhawk on Mar 18, 2004 9:22:19 GMT
WOW! Just been playing with the new version, and it really is quite superb. Robert is right about the SQL export (though I must say that it does not quite have the same effects on me ). Could I be very cheeky and ask for an addition for a future release? I have been planning to change the way that MU holds it's map data, so that I can accomodate maps of any height/width. To this purpose I plan to have a similar structure to the one that you have (x,y,terrain). But I would also need an additional 2 fields: scenarioID (integer,10) and description (varchar 50), so my table would look like this scenarioID, terrain, row, column, description eg: 3, "T", 14,34,"The Tower of the Squirrels" Would this be possible to implement? MU uses single letter abbreviations for terrain type, but I guess that you already hold those in a table since you generate MU maps. Maybe as an option in the wizard, eg Standard or MU.
|
|
|
Post by Old Shendemiar on Mar 18, 2004 11:28:32 GMT
WOW! Just been playing with the new version, and it really is quite superb. Robert is right about the SQL export (though I must say that it does not quite have the same effects on me ). Could I be very cheeky and ask for an addition for a future release? I have been planning to change the way that MU holds it's map data, so that I can accomodate maps of any height/width. To this purpose I plan to have a similar structure to the one that you have (x,y,terrain). But I would also need an additional 2 fields: scenarioID (integer,10) and description (varchar 50), so my table would look like this scenarioID, terrain, row, column, description eg: 3, "T", 14,34,"The Tower of the Squirrels" Would this be possible to implement? MU uses single letter abbreviations for terrain type, but I guess that you already hold those in a table since you generate MU maps. Maybe as an option in the wizard, eg Standard or MU. But you allready have that function. Do the map, and then use the update to add addtional data to your table. Like that you can have as many columns you want. And Remember you can also use notepad and global replace to edit the sql file, so you can do allmost anything with this combination.
|
|
|
Post by sparrowhawk on Mar 18, 2004 12:26:03 GMT
Yes I know that, but if it's all automated then when people submit maps I don't have to do all the manual updates. Especially true if the map gets revised and resent multiple times. Just being lazy of course
|
|
|
Post by Old Shendemiar on Mar 18, 2004 14:07:31 GMT
"jeah jeah more demans..."
Sorry old friend, i'm ashamed.
Bitmap importer could evolve also now that it's UniMapGen.
A "Select Transformation method" optionpage before the "Transformation parameters" page would be very usefull.
There would be option for "Regular", giving "Transformation parameters" it as it's now, and "Customisable terraintypes" option, that would give a page including:
Table with desired amount of following pairs: "rgb-value" - "terraintype name" - "Editor representation: Dropdownmenu with lom terraintypes (this would not be output anywhere with any of the exporters)"
Just say no if dont want to...
|
|
|
Post by sparrowhawk on Mar 18, 2004 14:14:48 GMT
Regarding the MU SQL bit above, actually since you cannot set the description of locations in UniMapGen (you can't can you, or have I missed yet another fab feature?), then I would not need the description column. The scenario ID would be useful though, but as Roope pointed out, not essential. What it does already saves a stack of work
|
|
|
Post by Old Shendemiar on Mar 18, 2004 14:29:28 GMT
And who was it that made pointy notes abot the retro looks anyway! Shame on you! I get kicks by just looking at it!
|
|
|
Post by sparrowhawk on Mar 18, 2004 14:50:00 GMT
And who was it that made pointy notes abot the retro looks anyway! Shame on you! I get kicks by just looking at it! Well it wasn't me - I only spotted the retro look this time around. And hey! I'm mentioned in the About box. Fame
|
|
|
Post by Old Shendemiar on Mar 18, 2004 14:56:11 GMT
Well it wasn't me - I only spotted the retro look this time around. And hey! I'm mentioned in the About box. Fame Sorry me english, i didnt meant that it was you, but somebody.
|
|
|
Post by sparrowhawk on Mar 18, 2004 14:57:34 GMT
No need to apologise - I wish my finnish were as good as your english. Seeing as my finnish consists of exactly 0 words!
|
|
Perun
Public Area Guest
Issa (Vis) [1:76:24]
Posts: 2,506
|
Post by Perun on Mar 18, 2004 20:42:53 GMT
"jeah jeah more demans..." Sorry old friend, i'm ashamed. Bitmap importer could evolve also now that it's UniMapGen. A "Select Transformation method" optionpage before the "Transformation parameters" page would be very usefull. There would be option for "Regular", giving "Transformation parameters" it as it's now, and "Customisable terraintypes" option, that would give a page including: Table with desired amount of following pairs: "rgb-value" - "terraintype name" - "Editor representation: Dropdownmenu with lom terraintypes (this would not be output anywhere with any of the exporters)" Just say no if dont want to... I think I'm gonna regret sending you preview of Mesced ;D! Is this what you mean (excluding color and description)? Notice replacement gfx for henge!
|
|
Perun
Public Area Guest
Issa (Vis) [1:76:24]
Posts: 2,506
|
Post by Perun on Mar 18, 2004 20:46:04 GMT
WOW! Just been playing with the new version, and it really is quite superb. Robert is right about the SQL export (though I must say that it does not quite have the same effects on me ). Could I be very cheeky and ask for an addition for a future release? I have been planning to change the way that MU holds it's map data, so that I can accomodate maps of any height/width. To this purpose I plan to have a similar structure to the one that you have (x,y,terrain). But I would also need an additional 2 fields: scenarioID (integer,10) and description (varchar 50), so my table would look like this scenarioID, terrain, row, column, description eg: 3, "T", 14,34,"The Tower of the Squirrels" Would this be possible to implement? MU uses single letter abbreviations for terrain type, but I guess that you already hold those in a table since you generate MU maps. Maybe as an option in the wizard, eg Standard or MU. IDs and abbrevs are underway, will think about descriptions.
|
|
|
Post by Old Shendemiar on Mar 18, 2004 21:13:24 GMT
I meant the bitmap importer, to have a customisable color-terraintype combinations, so users wont have to stick with only plain-down-forest-mountain.
Each pre-defined color-terraintype pair would need to show in editor only as a empty tile of the defined color.
(Associating them also with any existing editor graphics-tile wouldnt do any harm i think, but dont think that so important that i would make official request about it)
|
|