![]() I haven't changed the way XMAME works - the user could in theory change where everything is. So how much user control do you offer? Well be default, XMAME actually does offer full control - if you want. Some of these directories could be shared amonst versions of MAME: roms, snap Whilst the remaining must be specific to the version of XMAME using it. Some of these contain content supplied by the user: roms, snap, samples, artwork Some of these contain files which will be generated by XMAME: snap, cfg nvram, memcard, inp, hi, sta, frontend Some may be a bit of both. For XMAME the following directories are used in each of the three versions of XMAME I've offered: roms snap cfg nvram samples memcard inp hi sta artwork frontend history.dat hiscore.dat cheat.dat That's a lot to take care of and choose where everything goes, as that is multiplied by three. As for offering the user the exact ROMs directory location, this approach isn't really sufficient in this case - if you want to offer the user flexibility then it should be able to define exactly where everything goes. For this reason I tried solving the issue of the relatively complex file structure and various paths in easiest way possible from my point of view - which does deviate with the standard way other people have packaged their OPKs. However I do want to make it all work The installation part of the project doesn't motivate me very highly. I like solving problems when particular games don't work. I have a confession to make - I'm not *that* interested in the installation/OPK side of the software my interest is in porting and then optimizing the actual emulator and getting the games running as smoothly and as excellently as possible. XMAME69 |-MAME.SDL.69 |-history.dat <-shared |-hiscore.dat <-shared |-cheat.dat <-shared |-roms/ <-could be shared |-snap/ <-could be shared |-cfg/ |-frontend/ |-memcard/ I nice conceptual model for the XMAME setup is that the directory containing the main executable has all it's relevant resources underneath. Having everything in the one spot means this was easily done through the XMAMEROOT environment variable. * Configuration of file paths to XMAME directories. And I reasoned that it there would be not much difference to the end user between using an OPK or running the executables. Whilst this isn't much benefit for most users, as a developer having the application ready to go without launching the OPK is very useful. * No need to "launch" an OPK to have the application available. roms/ and snap/ directories are prime candidates as well as the history, hiscore and optional cheat dat database files. * Easily share resources between versions of MAME. Personally I find it annoying having files distributed around the filesystem for applications. My reasons were: * Have the entire application and it's data files in the one spot. ![]() ![]() Well I thought it would be better to be installed.
0 Comments
Leave a Reply. |