Looking pretty hot!
At this rate, it'll completely eclipse the frontend built into c4a-mame, so I don't mind just dropping it in there; but as you likely will build in to let it run non-mame stuff as well (indie, SNES, etc), we'll have toi play it by ear; ie: if people do not want mame, but they want your launcher, then it has to be an independant download.
This makes me think that c4a-mame should be a pnd, without a frontend; it woudl be a 'module' in concept; get your frontend, and let it run stuff; it woudl check for the required module and filter out stuff (or grey out?) the stuff that needs a module; could even check with the repo to ensure the latest copy of a module is present. If someone in turn launches a module, the module coudl in turn look for and launch the frontend.
ie:
- launch a module
--> look for frontend and fire it up, exiting the module
- launch the frontend
--> check for updates (everyone should be current ideally, to keep it fair)
----- of the frontend -> report if old
----- of the modules found -> report if old
--> check image cache, pulling down marquees as needed (on demand, in background)
--> do a dir list for games for that module (server can dsend the list), so you know what to filter out or grqay out in the games list
--> show filtered list
----- by default, show the module list with a marquee per module ("arcade" "indie" "snes" "..."), and when they tape or pick one of those, then slide into the actual selections that are available for that module
*shrug*
jeff