Software Support > PowerMAME
PowerMAME - New Derivative Build
MikeQ:
Well, I've been trying to hold off on these discussions until I had something to announce but the discussion seems to be begging me to say something. I can't give out the URL right now because I'm waiting for Aaron Giles to approve the use of the MAME name on the site. We have some minor issues to iron out.
I started this hobby late last year with the sole purpose of building an arcade machine. As I've learned more and become more involved, I've seen a number of places where if the BYOAC community would pull together, we could make some nice enhancements to MAME. I did some software work for RandyT and created a custom MAME to make use of the LED-WIZ. Suddenly, I find my hobby is now software development to enhance MAME. I'm not saying I dislike the new tangent my hobby has taken, but it isn't something that one person will be able to manage easily (although I will try if necessary).
I've setup up a website to distribute Power**** (replace **** with your favorite emulator starting with M). The impetus for Power**** was to support LED-WIZ on my own personal cabinet. With some urging from others, I decided to make Power**** available to the public. This has now grown into a much large project which I would like all who are capable to take part in.
For this reason, I'm setting up a web bases source control system that all the BYOACers can work out of. We will have a central repository for OUR version of MAME. Every attempt will be made to pull all the nice features of the various MAME's into a single version. I'm going to be running a software configuration management tool that will handle the integration of Power**** changes into the current version of the official release. I've setup a bug reporting system and long term would like to setup regression servers to run automated testing on changes to the baseline.
Ideally, with positive dialog, we may be able to develop well integrated and well designed solutions that MAMEDevs may see as more legitimate. I'm sure one reason they are reluctant to accept outside modifications is because it requires the devs to learn code that they didn't write and accept ownership for it in the future. One goal that we should strive for is well documented designs for what we do. Handing a bunch of C files to the devs is not very helpful. A well documented design with the C code makes life for them much easier.
I have 20+ years experience in professional software development and currently work for ATI developing OpenGL drivers for the Radeon graphics products.
Now to address concerns:
I've been told that this has been tried before and failed. I don't think someone elses failure should be a reason for me not to try. I believe (correct me if I'm wrong) that the person who tried this before was a student at the time and this played a major role in the demise of his project. I also believe he tried to support this himself.
I've been criticized for not starting with one of the already derivative versions floating around. Most of these are not based on the current release. I started with 0.102 and have made the move to 0.103. I plan to make a release in conjunction with every major MAME release.
I've been told that people will lose interest, drop off the project and the whole thing will collapse eventually. Yet another stupid reason not to try. I plan to handle the brunt of what makes derivative versions difficult. This is the source management and merges to release new versions. Their will be times when architectural changes to MAME hose us and we will need to re-architect our own code. This is inevitable. If we can develop a positive relationship with the MAMEdevs, we may be better prepaired to handle these changes.
I'm sure, that people will lose interest but there will always be people who are and we should be able to handle attrition. We should all make an attempt to embrace the MAME code and become intimate with its workings. This will allow seasoned developers to teach the new ones. This will also make it possible for a leaving developer to pass his work to someone else.
Regardless of what kind of support I get with this project, I intend to go forward. If I end up doing it myself, I will just get features in slower than if we work as a team.
Thanks,
Mike
mahuti:
Swell.
MikeQ:
Is this a sarcastic "Swell" or a genuine "Swell"?
thebrownshow:
I think this is a fantastic idea. Kudos for getting the ball rolling on it.
mahuti:
Sorry. Genuine swell. I'm just understated. And by swell, I mean, kick @$$!.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version