> Now, I have every intention of releasing the source to my frontend once it is ready
> (if that ever happens), but if someone had the same idea as I did and *didn't* want
> to release their source, then I wanted to know whether that would be allowed. And
> since my patches to MAME are what enable this kind of functionality, I want to be
> able to provide guidance on this licensing issue to anyone else who uses libmame.
All right.
First up, I need to mention that the QMC2 frontend does more or less what you're describing on Linux with totally stock MAME/MESS binaries (they fork/exec MAME as a separate process and then find and hijack the X window handle, I think). We're investigating adding an IPC protocol to allow QMC2 (and anything else) to have live control of MAME settings (and to swap media in and out in MESS) as MAMEUI does, because "integrated" frontends are the worst idea in computer science since MS-DOS.
Secondly, the viewer itself probably is not subject to the MAME license (although as such it also can't use the registered trademark "MAME" anywhere either). The backend MAME/libmame process obviously still is.
Edited by R. Belmont (10/14/11 11:05 PM)
|
Previous 
Index 
Next 
Flat 
Re: What is the policy on distributing patches?
Reply
