> > > When you talk about something like QMC2, I know the problem with it: it takes
> > to
> > > set up properly, there's always something wrong, the wiki is huge and full of
> > > technical jargon, basically it defeats its own purpose: making MAME easily and
> > > immediately usable, directly from a UI.
> > >
> > > I predict the new integrated MEWUI in comparison will become tremendously more
> > > popular and acclaimed, because it looks a lot like a Windows UI and is
> > > useable.
> > Hopefully, had the Windows 8 'Metro' stuff caught on maybe moreso because that was
> > pushing very much for a direction of simplified fullscreen UIs like the internal
> > although maybe that rejection is just a sign that it's really still not the best
> > idea.
> > but yeah, that's what I'm talking about, in *reality* QMC2 isn't that difficult to
> > use, but the way it's all presented overwhelms people, they don't see simple things
> > they can connect with, they see pages and pages of technical jargon on a wiki, it's
> > worse for projects which have huge wiki pages where half the content is out of date
> > too because when people do try they end up getting even more confused when things
> > don't work.
> > maybe I am overstating the date thing, but it is a field I've used before, it gives
> > sense of time - something I also find bitterly missing with the github interface
> > which insists for the most part on telling you xx days ago rather than an actual
> > submission date. I consider it awful design that I can go to a page like
> > https://github.com/mamedev/mame/commit/19bbdaac3543c8c17893dc396f08c8ab4ea28fd2 and
> > not see an actual date anywhere; 22 days ago isn't as useful to me as knowing when
> > something happened.
> > I don't calculate my life in 'days since I was born' I have a birthday...
> Hovering the mouse over the "22 days ago" text shows the exact time and date of the
> commit. (Why? That info should be displayed by default instead of hiding it like
Ah, so it does, but yeah, it's still not good design, there's no visual feedback when your mouse is over the '22 days' to indicate you'll get any kind of mouseover info there if you stop moving, plus it can't be copy+pasted from a mouseover.
> is there a reason why we can't add a line of code that translates that specific bit
> of information into something that can be displayed in MAME? "This build was created
> based on the source as available at X date."
> I dunno, that sounds like a workable compromise to me?
I don't know, I don't really expect a change at this point.
To me both the release date, and the build date, and the difference between them are useful metrics to have, and we've gone to having neither. Don't know if anybody would be willing to compromise.
I think what bugs me about this thread is that I've made mistakes in the past, 6-7 years ago I was probably pushing a bit too hard for 'idealistic' solutions myself, which didn't always go down well because I made the same mistake of assuming that people all had technical minds. I was criticized for that then, but I've taken it onboard, built a wider picture of things, and I'm more or less being shot down for the opposite now :S