NOTE: This is information for a program-in-planning. That means it is in the planning stages. That I will write pseudo-code, then real code. I can only say it will manifest. I can not give any kind of a time frame. I am learning C#, again, and once I have refreshed my memory sufficiently and gone through enough material to be comfortable I can start to code this thing, after of course the pseudo-code is written. This plan is step 1, step 2 is the pseudo-code, step 3 is coding the program itself. This program will only be initially available for Windows. but the code will be made available to anyone who wants to get it to run on another OS. This program will also most likely be written in C# and WPF.
I am at a strange place in my life. I have created a reality for myself I am currently manifesting and coding is a part of that but not central to it. In other words I am a computer artist first and foremost, and a computer programmer secondarily. This does not mean I am better at computer art than programming. It means that my preferred medium for expressing myself creatively is in computer art while my programming knowledge allows me to create the tools I want or need for my art. I have an idea for a GCS I want to make and it is a long-standing dream. I learn best by doing, so creating simple (hopefully) programs of some value and interest to me are the fist steps to manifesting this GCS.
So hopefully you understand a little more about what is going on here. Please read the following and post your thoughts/feedback/suggestions. Keep it constructive! Tell me what you want, why you want it, and why I should include this. Or what you don't want, why you don't want it, and why I shouldn't include it. Make a case for any thought, suggestion or advice you give. I am creating a blueprint here, planning stuff, so this is the best time to work things out. Once code is written in any form things become much harder.
Code: Select all
Program Purpose
To allow the user to install custom content or prepare their own content for installation. Key features are the automatic creation of the .cfg file needed for any package or combination of packages and the automatic creation of an autoexec.cfg file with all information needed to automatically load any custom content.
Program Features
1. Load an archive file of .7z, .zip or .rar.
2. Save to an archive file by calling user's installed archiver.
3. Instantly load .ogz, .obj, .mtl, .jpg, .png, and .cfg from archives. Also allow Browse/Load of these files.
4. Link all related files together (the proper .mtl file is linked to its .obj, for example.)
5. Paths configuration for Cube 2 engine based games (Sandbox, Cube 2. Red Eclipse.)
6. Paths configuration for user's archiver. Possible configuration to user's modeler and image editor as well.
7. Required name for folder (can be user's name) where files will be installed to or loaded from.
8. Map files (.ogz) to this directory in Packages/Base/
9. Model files (.obj, .jpg, .png) to this directory in Packages/Models/
10. Create or Open an autoexec.cfg file off the base of the game directory.
11. Paths written in autoexec.cfg for automatically loading.
12. Automatically create needed .cfg file(s) for all texture, model or map packages or any combination of these. Use customizable default settings.
13. Tabbed interface, one tab for autoexec.cfg editing, one for packages creation/load, one for options/configuration, one for modeling extension.
14. Possible modeling extension
1. Allows the user to export any imported .obj with its material to .3ds so it will import fully textured.
2. Displays a measurement or model showing player height.
3. Allows the user to perform a unified scale of their model based on player height.
4. The ability to “bake” textures/materials to a mesh.
- DreamBliss