> > I feel the pain as well - my front-end also depends on a quick and simple game list > > to drive it rather than waiting 30+ second of capture and parsing of XML - not to > > mention XML breaking from time to time. Anyway, I suspect only way to really work > > with it at the moment and produce the only the game list is to monitor the first > > letter of the setname at each line and stop reading/capture of names as soon as the > > next entry is in not in sequential order since all the games fed first and are > sorted > > with the devices thrown in afterwords. > > So do what qmc2 does and import the XML to a database that you can query quickly. > That's going to be more efficient and flexible than trying to parse a list on each > launch.
That would depend how much you want your front-end to do, I reckon. If you want a simple launcher allowing yourself to manually configure things as needed via command-line (my desired setup), then -listfull is by far easiest/quickest method to deal with parsing under 40k lines of a text file as opposed to 4.7 million lines of XML text. I guess each user has their own use cases.
|