Thinking
Monday, August 22nd, 2005Okay, I’ve spent this afternoon thinking about an idea for GRFMaker, or what would be a set of tools related to GRFMaker. Here it is:
Textual representation for the .lst format.
Before GRFMaker, you decoded .grf into an .nfo and a .pcx. You edited them both, and compiled them back into .grf.
When GRFMaker came allong, you worked in the GUI, using this concept of ‘blocks’ that represented chunks of .nfo code. GRFMaker made an .lst, and it could make a .pcx and .nfo out of your work. The .pcx and .nfo were then turned into a .grf. Just like normal.
What I propose, is a textual representation of the ‘block’ concept in use. To be used allongside GRFMaker, and perhaps instead of depending on the work situation (Unable to access GRFMaker, wanting to perform complex text operations on files for use with GRFMaker, and so forth).
For example. Instead of the .nfo/.pcx to .grf process, I propose:
GRFMaker Interface ——-> .lst —> .nfo/.pcx —> .grf
Text form —/So its the same, except at the very end stage, where the user interacts, he/she has two options, that work allongside each other.
GRFMaker already can save to .lst, and export to .grf (convert to .nfo then to .grf), what I would like to see is a set of command line tools similar to grfcodec for converting .lst to .nfo/.pcx, and converting .lst to a text form.
Another example. This is perhaps how a station (Because thats about all I code
) name block would look like:
Another thing is that comments within each block would be useable, but they would be lost apon conversion to .lst, or when used with GRFMaker.
[Name Block] ; This is the header for the block. Would have the exact same name as what the block does in GRFMaker.
Feature = c5xx ; Station name
Language = 3 ; American and English
ID = 0
Name = Basic PlatformSo obviously, its exactly the same as what you see and manipulate in GRFMaker, but in text form. What would be difficult is trying to represent blocks that have multiple windows to modify (Data blocks).
Here are my reasons for this rather large suggestion:
1) Another alternative way to code graphics
2) Allow drawing up plans and sketches easier on paper, or in .txt form easier when GRFMaker is not availible.
3) Perform search and replace operations on .lst’s
4) Attract people familiar with modding other games, who do not wish to use a GUI (This text form I am proposing is very similar to what is used in the Command and Conquer series of games, and also very similar to what is used in the game Freelancer. Im quite sure other games use somthing similar aswell)
5) Some people think using GUI based tools is cheap. Give them an alternative (But they’ll be attracted back to GRFMaker by the sprite block tools
)
6) Command line utilities for converting .lst’s to .nfo/.grf (Thats another suggestion) can be used allongside grfcodec and then used under other operating systems, and with advanced scripting (Such tools can be used with Cygwin bash aswell).
7) I have more points, but I’m slowly getting a headache from looking at bright white on a CRT monitor.
Now, finally, I am no programmer, so I have no idea wether this is an easy task, or somthing incredibly difficult, so obviously I’m not demanding anything, just throwing another suggestion onto the table.
I put it here, regardless of the fact I’m going to email this to Szappy, because other people might want to read it, or comment on it. And I can link this straight to Lakie instead of emailing it to him aswell.
