Rodent.Vienna
10-31-2011, 01:00 PM
Hello,
would there be the chance to somehow implement reverse parsing for Database Files?
What do I mean by that:
- Currently:
games are defined in xml file, then artwork, /emus/roms are parsed based on that.
- My Idea:
same setup, but if a rom is missing or "not parseable", the game does not show up in wheel.
The reason I would like to see this, is, that it is much easier to delete a rom instead of deleting an entry inside an XML file (or more xml files given cases of multiple genres per system / favorites.
it may be selectable do do "reverse xml parsing" by a setting inside HyperHQ, so nobody needs to use this forcefully.
anyone here thinking this would make sense?
an even more advanced implementation could check for whats missing and define a "master" item on which the whole setup can be cleaned out.
(example: master definition for Game "XYZ" is "rom", based on if the rom is there or not, the whole trail is kept or deleted (artwork, xml-entries, etc)
rgds
Alex
would there be the chance to somehow implement reverse parsing for Database Files?
What do I mean by that:
- Currently:
games are defined in xml file, then artwork, /emus/roms are parsed based on that.
- My Idea:
same setup, but if a rom is missing or "not parseable", the game does not show up in wheel.
The reason I would like to see this, is, that it is much easier to delete a rom instead of deleting an entry inside an XML file (or more xml files given cases of multiple genres per system / favorites.
it may be selectable do do "reverse xml parsing" by a setting inside HyperHQ, so nobody needs to use this forcefully.
anyone here thinking this would make sense?
an even more advanced implementation could check for whats missing and define a "master" item on which the whole setup can be cleaned out.
(example: master definition for Game "XYZ" is "rom", based on if the rom is there or not, the whole trail is kept or deleted (artwork, xml-entries, etc)
rgds
Alex