Best FE for newest Mame versions (XML changes)

[basecab]

I just built an arcade cabinet.  Every front end I have tried to use so far requires some silly workaround in order to be compatible with the XML changes made in MAME 162.  Keep in mind I'm very new to this.  But as I understand it, some XML tags were changed in 162 ("game" changes to "machine").  This has caused Mala and MGalaxy (the two I've tried so far) of being incompatible, as least natively.

I want to be using the latest MAME version for the latest features, filters, and speed.  Is there a front end that is always up to date with MAME changes?  Hyperspin?  Maximus Arcade?

It seems odd that these two FE's I've tried still don't work with what seems to be a small change.

[artyfarty]

I've been using Attract-Mode http://attractmode.org on my cab with good results.

[Slippyblade]

Love Attract-Mode.  Having games with various emulators in one list is so easy.

[NOP]

If you generate your lists for your FE using romlister, it will convert 162+ MAME xml's back to the old format, thus keeping all out of date FEs still usable with the latest versions of MAME. 

[Jayme65]

I"m a mGalaxy user! Some days ago, I read that the new mGalaxy update would fix this incompatibility with 'new' Mame version...so I simply asked on the forum to get a beta...which I was given :-) I would advice you to ask the developers for a beta if you're in a hurry!!

[BadMouth]

If you generate your lists for your FE using romlister, it will convert 162+ MAME xml's back to the old format, thus keeping all out of date FEs still usable with the latest versions of MAME.

This needs to be stickied in the Mala subforum.

I just downloaded a v.170 romset, so I'll be giving this a try.

[NOP]

If you're familiar with romlister, it's the act of creating a merged XML file that makes the backward compatible version.  You must have the latest version of RL.
What's funny is that I covert 162+ back to the old format purely out of laziness on my end.  There were too many things that RL also used in the old format and the fact that it kept all FE's working just happened to be a nice side effect.

[Howard_Casto]

I've always used a delimited text file for all of my frontends.  It's old-school, but if it ain't broke.....

That way all you really need is a list generator that can parse xml.  The parser can pull the relevant fields and ignore the rest, including any changes.  Delimited text files also import into database apps quite easily, so they can be plugged into something with filtering/sorting functionality with little or no effort.  Honestly I never have understood the popularity of xml.  Text files FTW!