Just as an observation, when you fork a closely related project like
the Win32 port of GGI, you spend a lot of time syncing changes between
the distributions. The net effect (likely) will be that WinGGI would
always lag behind GGI(linux) in support/features.
I don't know a great answer, but forking code usually causes a lot of
hassles.
jeff
(BTW, I'm excited to hear that you got XGGI working... does this mean
that soon there will be a decent, functional X server for the windows
platform?)
On Thu, Feb 17, 2000 at 01:38:34PM -0500, John Fortin wrote:
> As alot of you probably know, I've been working on a Win32 port of GGI.
> A good portion is done, and I have been successful in getting XGGI to
> run on Win95/98/NT.
>
> The current GGI sources are very Linux oriented, as they should be.
> However, quite a bit of the source code is worthless for Win32
> platforms. There are also places where there are just plain
> incompatibilities. select() for unix and win32 are very different,
> win32 has no fork, as well as other Posix defeinciences.
>
> I'd like to propose the following.... A seperate project, WinGGI, and
> source tree based on the current GGI tree, devoted towards Win32
> platforms. The basic libggi/ libgii api would stay the same. I would
> like to see some additions such as Joystick and sound support.
>
> Please, this is not an attempt to start a linux vs. win32 flame war, but
> a way of increasing the visibility on GGI in the windows community.
>
> Any thoughts, ideas are welcome...
>
> John Fortin
