2006/7/7, Ricardo Almeida <[EMAIL PROTECTED]>:
Yes, but there are some entries that are carbon copy of others. They
should be removed, preferebly in an automated way...
Oh. In that case, you're right. Perhaps the developer was drunk and
didn't notice the carbon repetitions of some drivers... :p
It's a solution. One that gives a lot more work would be changing the
format of romrc, reorder the roms so that equals roms are in sequence,
and only state the name once and use several ROMSET .... END for each
romset of a game.
Yes. I was also thinking a solution like that (grouping romset
variants of a same ROM togother), but did not mentioned it because, as
you said it, making such change on the `romrc' format would demand
harder work to make Gngeo able to handle it.
But in the other hand, such a romset grouping, even if longer to
implement, would firstly be more logical IMHO, then would be
beneficial in a plan for spliting up the current, monolythic `romc',
into several (one per ROM) little driver files (put in a `romrc.d'
directory). The individual diver files (i.e `romrc.d/bstars') would
thus contains the ROM main driver, but also potential drivers for
other romsets.
I discussed about it with Mathieu. If the single file `romrc' were
definitively replaced by a directory containing per-ROM driver files,
Gngeo would gain some advantages:
- drivers would much easier to add/edit/remove than in a single
`romrc' which is presently more than 12.000 lines long !
- such a flexibilty could encourage new drivers creation and sharing.
For exemple, we've also talked, with Mathieu, about a project to
maintain an online repository which would concentrate all the last new
/ modified drivers that user could download (possibly through their
frontend) to add new ROM support for Gngeo.
Regards,
Choplair
--
The Choplair-network,
an indepedant libre software developement crew.
"Improve your chops!"
http://www.choplair.org/
Gngeo mailing list
To unsubscribe : mailto:[EMAIL PROTECTED]
