What if you have two different emulators for the same console on your Pandora? One might be better for certain games, and the other might be better for other games. You'd much rather have one directory in which you put your ROMs than have them in two separate directories. I'm with you on keeping ROMs in their emu's directory, but it's just as easy and clean to make a ROMs directory which has subdirectories that are categorized by system. For something like the Pandora, that's probably the better system.Sturatt said:I suppose it just comes down to preference then. I would rather have my roms in the same folder as the emulator to keep everything together. I don't really see a problem with an app being distributed as a directory rather than a file. If you do, nothing is stopping you from packaging it into a pnd file, all you have to do is execute a script or run the gui program and select 3-4 options.j6cubic said:Why? Emulators for OS X are distributed as application bundles, just like everything else (save command-line only tools and daemons). Just because the application needs to reference something in a certain path, that path doesn't need to be in the application's $PREFIX or hardcoded somewhere.Sturatt said:To be fair, it doesnt really make sense for some apps to be distributed as pnd files (emulators are a perfect example, with you having to put your own files in with the application's), which is why libpnd also considers a directory with a pxml file in it executable. It will still be the exact same amount of work to install, only you will be copying a directory over instead of a file.
What I think about is the following: The emulator is in a .PND archive. When I start it I need to configure where it looks for ROMs, etc. (if it doesn't just use a file chooser of some sort) and from there everything works just as if the emulator uses a plain directory structure. If the emulator explicitly needs me to install files to my home directory before I can use it, PXML either supports automatically installing a skeleton file or its use as an installation helper is fairly limited anyway.
My assumption here is that no sane application ever needs to modify itself. And an application modifying itself is the only reason why its files need to be in a writable location as opposed to a mounted ISO.
I mean, this isn't Windows 9x where application settings are stored in that application's directory. .PND or no, an application should be able to read from the rest of the directory tree as far as permissions go and it should be able to write to ~/.appname. And emulators really don't need much beyond that.
Last edited by a moderator: