An idea that the team is considering and discussing is turning Mupen64Plus into an API based core, which interacts with a GUI.
The core would be a back-end, and the GUI would be the front-end. You can see this in an emulator such as MAME (which has been very successful).
Such calls that would be needed in an API would be.
Emulator driven calls:
START_ROM(path);
PAUSE_ROM();
STOP_ROM();
SELECT_CORE(type);
SET_WINDOW(window);
Plugin based calls:
LOAD_PLUGIN(type,path);
UNLOAD_PLUGIN(type);
CONFIGURE_PLUGIN(type);
TEST_PLUGIN(type);
CALL_PLUGIN(call,type);
the way this would work is that: the GUI would interact with the core, allowing for a clean core with little dependency. this would make portability a lot easier. a lot of things might have to be rewritten, and this is only an idea... but it might be the course this project needs.
discuss
The core would be a back-end, and the GUI would be the front-end. You can see this in an emulator such as MAME (which has been very successful).
Such calls that would be needed in an API would be.
Emulator driven calls:
START_ROM(path);
PAUSE_ROM();
STOP_ROM();
SELECT_CORE(type);
SET_WINDOW(window);
Plugin based calls:
LOAD_PLUGIN(type,path);
UNLOAD_PLUGIN(type);
CONFIGURE_PLUGIN(type);
TEST_PLUGIN(type);
CALL_PLUGIN(call,type);
the way this would work is that: the GUI would interact with the core, allowing for a clean core with little dependency. this would make portability a lot easier. a lot of things might have to be rewritten, and this is only an idea... but it might be the course this project needs.
discuss