[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Whatever happened to the KEGS updates?



On 4/6/2010 11:00 PM, geoff wrote:
   To: schmidtd
I just checked the KEGS 0.91 source code and its still GPL.  There are no
legal reasons why the source can't be extended (Kent maintains all copyrights
to what he has written--any new code is copyrighted by the respected developer
and the source must remain available).  The solution which I think might be
better is to rename the code base and spin a new version.  This way, if Kent
chooses to continue to work on KEGS, there is no user confusion of which
version is which (it is bad enough that KEGS32 is often confused to be
KEGSwin).

With a chat discussion earlier today, I found out that another Apple II
developer is willing to host a private SVN repository for KEGS advancement.
The choice comes down to using a private (running on somebody's personal
server) or to create a new name and create a new project on sourceforge.

During lunch today, I was talking about this situation to yet another Apple
enthusiast who suggested the name kiae (Kiae Is an Apple iigs Emulator).  I
had thought of the name "eggs" if it was decided to use the GTK for a GUI
(where eggs would stand for enhanced GTK GS).  The nice thing about GTK is
that it can be one GUI and run on all major modern operating systems (Windows,
Mac OS X, and UNIX).

I have some KEGS code which I would like to also contribute--and I agree that
a decent revision control system is needed for individual developers to
maintain their code.

Geoff


I'm all for a fork, a friend of mine actually suggested that when he got wind of what I was working on. Internally my build is called "KEGS 0.92", but thats easily changed. Personally I'm not a fan of GTK+, simply because it doesn't use the native OS's widgets. It looks pretty bad on Windows and really horrible on OS X. wxWidgets is one of the few cross platform GUI libraries that does use the native widgets. In the end, its usually best to program each platform's GUI code separate (see VICE), but thats a lot of work.

For the video, audio output, and joystick control, standardizing on SDL is a no brainier vs. writing separate drivers for each OS. That work is already pretty complete with the KEGS-SDL port. Lower level stuff like native serial, parallel, and MIDI I/O will require drivers for each platform.