A front-end for *stupid* front-ends?

[LegsXd]

Does there exist a program (which when give very simple command-line arguments) can call "other" emulators using more complicated commands?, .i.e., similar to a BAT file but more powerful.
For example, such a program could:
- uncompress *.zip & *.7z roms for emulators that do not have support.
- automatically mount CD images for emulators which are not capable.
- have a script language for complex command-line arguements and modification of emulator *.ini files
- force the emulator into fullscreen and possibly make ESC key work as expected.
- support for multiple emulators for a single system.

As many of you know, some front-ends support this sort of stuff, for example:
- Gamebase contains a script language (Gemus) which can modify emulator *.ini files and can form complex (game dependent) command-line arguments.
- LusSpace FE has support for the Goodtools "Goodmerged" 7-zip sets.
- Mamewah has pre- & post- commands for executing other programs like WinIPAC.
- A few front-ends give you the option to uncompress a rom before sending it to the emulator.

I think this is an idea that would "level the playing field" in the battle between the FE authors.  What do you guys/gals think?

[youki]

You can do that using VBScript or JavaScript instead of bat.  It works really well. You create your script .VBS or .JS  , then you call it from the Front End you want.  For instance from a .BAT  like taht

CScript  RunMyGame.vbs %1

Of course, in your VBS file you have to code what you want. But you can do all what you want. Even download a ROM from internet for instance.

[Howard_Casto]

Does there exist a program (which when give very simple command-line arguments) can call "other" emulators using more complicated commands?, .i.e., similar to a BAT file but more powerful.
For example, such a program could:
- uncompress *.zip & *.7z roms for emulators that do not have support.
- automatically mount CD images for emulators which are not capable.
- have a script language for complex command-line arguements and modification of emulator *.ini files
- force the emulator into fullscreen and possibly make ESC key work as expected.
- support for multiple emulators for a single system.

As many of you know, some front-ends support this sort of stuff, for example:
- Gamebase contains a script language (Gemus) which can modify emulator *.ini files and can form complex (game dependent) command-line arguments.
- LusSpace FE has support for the Goodtools "Goodmerged" 7-zip sets.
- Mamewah has pre- & post- commands for executing other programs like WinIPAC.
- A few front-ends give you the option to uncompress a rom before sending it to the emulator.

I think this is an idea that would "level the playing field" in the battle between the FE authors.

[LegsXd]

I understand all of the points you 2 make.  They are valid. 

But it's like this, for some of the features I mentioned, I'd have to write 20-30 scripts for all of the emus I use.  I'd much rather have a program that could organize this effort (and would have a much lower learning curve).

For people who only use MAME and 2-3 other console systems, then fine, this wouldn't be that useful.  There are other and perhaps better ways to do this (as youki mentioned).

As for the multiple emus, I was just suggesting that such a program could easily have a set of "preferences" where the current default emu could be picked.

I think people do choose a FE based on these sort of features.  Many FE's as they evolve seem to slowly add these "types" of  features--proving that they are useful. (the emulators I mentioned are examples of this)

I'm simply trying to point out how a simple program could potentially make things less complicated for many people out there.  Isn't that usually the point of good software?

[Howard_Casto]

I understand all of the points you 2 make.

[youki]

And the more things said app does, the more complicated the cfg has to be. 

good point!.  Totally agree.

While there is no real standard for Emulator development. At least for their interface, it is impossible to do something really generic and easy to configure.  If you concentrate on only one emulator you can. But in the case of dozen of emulators... it is very hard to keep simple.

Somebody should create an Emulator Framework , with interface normalizations. It would be very usefull for FE coders.

[Howard_Casto]

For once we agree on something.  The standard is already there really, namely mame, it's switches and it's naming conventions.  Raine and mess already conform to this standard, but other emulator developers are reluctant to adopt it for fear that they might not seem original. 

[iwillfearnoevil]

For once we agree on something.

[Howard_Casto]

version numbering isn't a standard...... In the case of mame, it is annoying, but this is a moot point considering all over emulators would be on different versions and version numbering has little or nothing to do with how to launch/configure an emulator. 

[Minwah]

For once we agree on something.  The standard is already there really, namely mame, it's switches and it's naming conventions.  Raine and mess already conform to this standard, but other emulator developers are reluctant to adopt it for fear that they might not seem original. 

I agree but I doubt emulators will ever be created to the same 'standard'.  Playing games on arcade cabinets is most emulator developers last concern (if a concern at all), and really why should it be any different.

[jcrouse]

Playing games on arcade cabinets is most emulator developers last concern (if a concern at all), and really why should it be any different.

I think this is the root of most non-cabinet friendliness. The authours don't care about cabinet users. Take Nebula for instance. Why in the world does ESC toggle fullscreen/windowed and Alt-ESC exit the application.

John