> > Get MESSUI if you want that.
>
> Yes, I get MESSUI, but in the next questions I asked why the need of two GUI's for
> that thing, why no integrate all in the same GUI?...
>
If MAMEUI is to continue that is what should happen, yes, and any bugs should be fixed.
We merged the official projects, and it's been a resounding success I feel, we've seen more interest than ever in the various components.
There have been some rather vocal people against it, and some who are taking time to fully understand it, but the general feeling I'm getting from people, and energy that's been injected into the project seems incredibly positive.
If MAMEUI were an official part of the project we would have done exactly what is suggested when the merger happened, take the MOST CAPABLE of the codebases, and use that one.
I think the issue here is, and it comes across very strongly in the comments, MAMEUI users are allergic to change, they want what they had, exactly how they had it, forever; there have been practically no compelling reasons put forward in this thread by most of the posts (one or two good posts, that's it)
I did some research of my own on the subject a while back, and ended up with similar results, in the end the conclusion was that most users wanted a 100% native windows application in a single application so that they could always update just by copying a single file.. That was actually rather worrying because even now that's the worst possible way to update.
|
Index 
Flat 
Re: A simple question
Reply
