27
edits
Difference between revisions of "User:Toneman"
Jump to navigation
Jump to search
added "extra concerns" to Plugin Design Change Plans
(Modified Plugin Design Change Plans) |
(added "extra concerns" to Plugin Design Change Plans) |
||
| Line 41: | Line 41: | ||
====Implement support for loadable modules on the DS with the aid of the ARM-based GP2x code. (To be completed by: August 13th)==== | ====Implement support for loadable modules on the DS with the aid of the ARM-based GP2x code. (To be completed by: August 13th)==== | ||
July 19th-23rd: Get Debugging Facilities Set up for the DS and make final design decisions with mentors (see "Plugin Design Change Plans" below). | July 19th-23rd: Get Debugging Facilities Set up for the DS and make final design decisions concerning plugin loading with mentors (see "Plugin Design Change Plans" below). | ||
July 26th-30th: Begin making necessary changes to GP2x loader/linker to adapt it for DS and altered design. | July 26th-30th: Begin making necessary changes to GP2x loader/linker to adapt it for DS and altered design. | ||
| Line 65: | Line 65: | ||
For a next step, every game target in the config file can be given an "engine=MYENGINE" key-value pair. This way, the right engine plugin can be decided upon right away. If the "engine=" field is missing for a given game, we can just revert to the behavior of the "First Refinement" and automatically update the target in the config file with an "engine" key based on which engine the old behavior detects as correct for the game. | For a next step, every game target in the config file can be given an "engine=MYENGINE" key-value pair. This way, the right engine plugin can be decided upon right away. If the "engine=" field is missing for a given game, we can just revert to the behavior of the "First Refinement" and automatically update the target in the config file with an "engine" key based on which engine the old behavior detects as correct for the game. | ||
3) Extra Concerns | |||
------------------------------- | |||
*Currently, starting a game without a config entry is supported. For example, if you type "scummvm monkey2" and have no monkey2 target configured, it will try to locate monkey2 in the current directory. We can't know the engine this way, but we could again fall back to the "First Refinement" behavior. | |||
*To support "--list-games", we can just load every engine individually and add the output to a list. | |||
*For desktop ports and certain other ports (e.g. Dreamcast) where it makes more sense to stick with the old, unmodified model of loading all plugins from the start, we can certainly just retain that old behavior :-). | |||