development might slow down a bit since my 21" monitor recently died and have been reduced to using a single 15" monitor
also, im learning wxWidgets while developing it, so it is going sort of slow at the moment until i get comfortable with the API (not constantly referencing the docs, sample code, etc). but, so far im pretty happy with the doc/view architecture and wxAUI.
at the moment it currently supports a single project document. its setup is very similar to visual studio. i guess i could post what source i have for the hell of it so you guys could find anything wrong with it.
the basic idea behind the project document is to change the current working directory to that which contains the .ceprj file, that way everything can be done relative to that directory which should allow you to just move your project wherever you want, load the .ceprj file, and you should be good to go.
the project document currently keeps track of all things related to your project.
the application configuration is stored in a .ini file which on windows is created in Document and Settings/[username]/Application Data/CEGUI STudio/config.ini and on linux should be ~/.CEGUI Studio/config.ini (although i havent tested it on linux). the application configuration will only store application wide settings (window settings, fonts, recent files, last selected project directory, etc). im considering removing the space in CEGUI Studio and just making it CEGUIStudio to be more unix friendly.
at the moment i also create a basic directory structure from within the project directory (scheme, layout, looknfeel, fonts, etc). while this isnt very flexible, i think enforcing that layout will avoid any confusion about which directories are linked to resource locations. i sometimes feel less flexibility can be a good thing.
of course, this could be changed, but for a first release, this is how i plan on doing it. id like it to be able to export a c++ implementation which you can simpley drop into your application to use the current resource location settings of your project.
i figure it could be possible to let user keep their cegui datafiles wherever they want using absolute paths or relative paths, but its just easier to enforce this structure.
for users of the ogre rendering system, an option could even be made available to export to a zip file of the structure, which you could then drop right into your ogre app, load the zip using ogres resource manager, and youre all set (ive found using this structure in a zip file and just loading the zip in ogre is a pretty nice way of doings things)
since I do very much with wx.
