"Parsing the ROMs list for each game is what takes time..."
I don't extract the roms data, too long and unnneeded in FFE... I didn't want FFE to be a rom management programm, don't even know if i can call it a "front end"... it's more a user interface just to launch games in a nice way....
What i extract for each games can be read in the debug window, mainly name and shortname, manufacturer, driver, clone of, width and height of the driver, emulation status, and what type of game (raster, vector, fruits or mech)
And that's it..
Thanks for your interest, in no way i want to be something as complete as Emuloader, even if i will surely copy the way we choose in EL with the icons i did for you the way you choose how to sort the list between parents, clones, working/not working, vector/raster, etc...
BTW, if setup is that long to create the files, it's because ALL files are already extracted for next betas (check the fscommand/datas dir), all lists are already there, even if actually beta 1 only uses 2 of them (raster + vector, only working and no clones, sorted by description or zipname)
|