> > > Will do. > > > Looks like there's a lot of cruft in my dist. directories built up over the > years. > > > Will sync them to the baseline package next go around. > > > > No problem. > > > > Please note that from 0.227, I'll be including some GLSL shaders in the HLSL folder > > in my package. > > These are the ones included with ARCADE64, and will be in all my releases from now > > on. It would be > > nice if you could add them to your package too. They are files with .vsh and .fsh > > extensions. > > I mean no offense, but are you sure making MAMEUI not match MAME in the terms of the > files it distributes is the best decision? > > There's many users out there who still don't understand the project history and still > think of MAMEUI as "the Windows version of MAME", despite it being something like 15 > years where that has not been true. (They mean "a more native Windows UI", I guess, > but these are the sort of users who wouldn't understand what a UI is.) And they'll > continue to do so, unless the MAMEUI project changes its name or something. > > Therefore it would make more sense from a user point of view that MAMEUI basically > distribute everything MAME bundles and no more. > > I would counterargue that it might be better to, at least temporarily, submit a pull > request to upstream (MAME) adding the OpenGL shaders (with appropriate accreditation > and licensing for the shaders that you did not create yourself) and see if it could > pass review and be accepted. > > Or you could make OpenGL shaders an optional add-on download from the MAMEUI website. > There's plenty of solutions! > > (At any rate, it's all sort-of a moot point, as eventually this will likely all be > rewritten, perhaps years from now.) > > - Stiletto
Technically, shaders are features of the UI surely? Personally, I use ARCADE64 over MAMEUI not because of the UI options, but because the drivers included are more in line with my needs". But then, that could be just me.
|