Re: Whatever happened to the KEGS updates?

["geoff" <geoff@a2central.com.remove-uj3-this>]

  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

 > On Apr 6, 3:35=A0pm, "Christopher G. Mason" <c...@my-deja.com> wrote:
 > > Regarding the forks, Kent hasn't updated KEGS in several years now and 
 > > besides the KEGS32 port with minimal GUI, none of the other forks I have 
 > > found use the latest 0.91 code base (KEGS-SDL, CasaGS, etc.) It also 
 > > doesn't help that creators of some of those forks never bothered to 
 > > release their code (CasaGS for example). There is no version management 
 > > system (SVN/CVS) setup for the code base and as it stands, the code is 
 > > kinda messy when it comes to platform specific stuff (lots of #indefs for 
 > > sound and serial support).
 > 
 > Glenn Jones added support for the Uther card in there somewhere - but 
 > without a repository to put it back in, that'll need to be merged by
 > hand.  Should we try to contact Kent to start maintaining the project
 > (and set up the code repository)?  Has anyone else tried - i.e. are
 > there any geopolitical landmines in the way?