| Main > Software Forum |
| Aaron removes xml2info as of u12 (in other words, we are screwed) |
| << < (15/16) > >> |
| krick:
--- Quote from: Pi on July 20, 2006, 05:42:25 pm ---In any case, if people really care about xml2info, then someone should take over the source and maintain the project from now on... It'll be much better and cleaner than any other solution, IMHO. --- End quote --- I've been in the xml2info source a lot in the last week or two and let me tell you, it's not a clean solution by any stretch of the imagination. The original author never anticipated having displays and controls nested the way they are now. So to get it working at all with the new XML format, I had to resort to some MAJOR hacking and it's still not 100% as I cant' see any way to get the actual control type into the output due to the way the data is parsed. The cleanest solution, and by far, the easiest to modify for future changes, is to use an XSL Transform: http://mame.3feetunder.com/xml2info/ |
| Howard_Casto:
--- Quote from: krick on July 20, 2006, 05:37:22 pm --- I think my comment was misunderstood by all. Sir Poonga originally mentioned controls.dat in response to u_rebelscum wanting suggestions on additions to the MAME XML output in the controls area. I think what is done with controls.dat is awesome, however, I know that if anything was to be added to the MAME source code, it would have to be as minimally invasive and non-bloating as possible in order to be accepted by the devs. In that respect, controls.dat *is* too heavy. It doesn't make it invalid or unimportant, just more than the MAME devs would go for if it was incorporated into the source. External XML files, however, put an entirely new spin on it. --- End quote --- No we got it, but you keep mentioning that you want to add labeling into mame for the sake of documentation. Well the only possible way you can do that is to get as detailed as controls.dat. Anything else you could think to replace the current mame labels with isn't documenting anything. As Aaron pointed out the constants in mame are just there to keep the user from getting confused and at the pcb level they are all just singular inputs. Btw, on the xml2info thing...... I've gotta agree, the proggie is dead. If it isn't going to be officially in mame then it will never be kept up and thus it isn't as useful. When it gets to the point where you can get more data from one format than the other then it's time to ditch the old format. Again I don't like it at all, but if it isn't going to be in mame, where it can constantly be updated and have the same data as the xml version then it isn't very useful, with the exception of putting a "band-aid" on older front-ends and applications that aren't going to be updated. |
| headkaze:
This may be a stupid question, but why does Mame.exe generate this data in the first place? Why isn't this data stored in a separate file rather than generated on the fly? |
| Howard_Casto:
Because this data already has to be stored for mame. rom crc's are required, the driver relationship has to be known ect.... Adding some of the stuff others are suggesting would indeed be adding data just for the sake of data. |
| headkaze:
--- Quote from: Howard_Casto on July 20, 2006, 09:01:11 pm ---Because this data already has to be stored for mame. rom crc's are required, the driver relationship has to be known ect.... Adding some of the stuff others are suggesting would indeed be adding data just for the sake of data. --- End quote --- I still don't get why it's not all stored in an external file, surely Mame could just read an external file instead of having it embedded into the source. |
| Navigation |
| Message Index |
| Next page |
| Previous page |