Fri Mar 14, 2003 9:18 am
**UTILITIES** FLIDE Sourceforge project open
I've got a sourceforge project (FLide) set up for a set of mod writing tools I'm working on. To give a quick summary of what the project is, I've got 3 things planned for it right now:
1)Shared Library - This is for utility classes, classes to read INI files, anything that could be used between multiple tools or that other projects could use.
2)Flini - A commandline INI file converter. It can read and write binary or text INI files and can batch convert whole directories, only pick up changed files, write back to the Freelancer directory in whatever format the files were already in.
3)FLIde - This is going to be the meat of the project. It's going to be a GUI that allows editing of the Freelancer game data. Here's a screenshot to give you a rough idea of what I have in mind.
Currently, the Shared Library contains a class that is fully functioning in reading and writing of binary and text mode INI files. I'd like to increase the speed a good bit by playing with the Loading code for Binary files. I have some ideas here, but the code is working.
The Flini tool is pretty solid now, I've used it to convert the standard Freelancer data files to all text in a working directory, then back into the Freelancer directory after making changes and everything seems to be working. There will probably be some bugs that need fixing, but it's functioning for now.
Flide is in a pre-alpha phase. I've got the File browser tree working for navigating the files, and you can double click on files in the tree to open up the raw INI data in the main window as seen in the screenshot. I've got an object browser planned that is an alternate way of viewing the game database. Basically, this window will understand the database and parse out individual item types, so under the Objects browse pane you'll see a Ships, Systems, Weapons, Bases, Planets folder. Then opening one of those up will show you every instance of that type. Double clicking on one of those will bring up a specialized window in the main area (where you see the INI file in the screenshot). This custom window will understand the data fields for the type of object it's dealing with, showing only the values that can be changed, keeping track of valid values and the integrity of references to other objects. For example:
If you open up a solar system, below the tabs listing open files, you might see several new tabs. Maybe one tab for each Planet and Base in that system, another for every Jump Gate, Another for encounters and hostile NPCs, and another for trade goods sold in the system. In this window you can edit / add / remove values.
Right now I'm the only one on the project, but I'd like to get some folks added to it. If you have any C#/.NET experience (or even if you have some programming experience in other languages) and want a fun project, drop me a line at [email protected] with a bit of detail as to what you want to do, experience you have, and anything else you think might be important.
Oh, and to whomever is flagging the topics as sticky, please tag this one too. Thanks.
Edited by - PumpkinEscobar on 14-03-2003 09:28:33
1)Shared Library - This is for utility classes, classes to read INI files, anything that could be used between multiple tools or that other projects could use.
2)Flini - A commandline INI file converter. It can read and write binary or text INI files and can batch convert whole directories, only pick up changed files, write back to the Freelancer directory in whatever format the files were already in.
3)FLIde - This is going to be the meat of the project. It's going to be a GUI that allows editing of the Freelancer game data. Here's a screenshot to give you a rough idea of what I have in mind.
Currently, the Shared Library contains a class that is fully functioning in reading and writing of binary and text mode INI files. I'd like to increase the speed a good bit by playing with the Loading code for Binary files. I have some ideas here, but the code is working.
The Flini tool is pretty solid now, I've used it to convert the standard Freelancer data files to all text in a working directory, then back into the Freelancer directory after making changes and everything seems to be working. There will probably be some bugs that need fixing, but it's functioning for now.
Flide is in a pre-alpha phase. I've got the File browser tree working for navigating the files, and you can double click on files in the tree to open up the raw INI data in the main window as seen in the screenshot. I've got an object browser planned that is an alternate way of viewing the game database. Basically, this window will understand the database and parse out individual item types, so under the Objects browse pane you'll see a Ships, Systems, Weapons, Bases, Planets folder. Then opening one of those up will show you every instance of that type. Double clicking on one of those will bring up a specialized window in the main area (where you see the INI file in the screenshot). This custom window will understand the data fields for the type of object it's dealing with, showing only the values that can be changed, keeping track of valid values and the integrity of references to other objects. For example:
If you open up a solar system, below the tabs listing open files, you might see several new tabs. Maybe one tab for each Planet and Base in that system, another for every Jump Gate, Another for encounters and hostile NPCs, and another for trade goods sold in the system. In this window you can edit / add / remove values.
Right now I'm the only one on the project, but I'd like to get some folks added to it. If you have any C#/.NET experience (or even if you have some programming experience in other languages) and want a fun project, drop me a line at [email protected] with a bit of detail as to what you want to do, experience you have, and anything else you think might be important.
Oh, and to whomever is flagging the topics as sticky, please tag this one too. Thanks.
Edited by - PumpkinEscobar on 14-03-2003 09:28:33
) but haven't been able to debug it properly (although it does small compressions fine but chokes on big ones lile mbases.ini. 1.5MB file with 45000+ lines of text).
