STOP! LOOK! LISTEN!

[Adrian Ratnapala <s369625@student.uq.edu.au>]

I don't like being the one telling everyone else to make a major
architectural
change to their project, but I feel it needs to be said before any more
is done:

THE GGI DOES SOUND AND INPUT TOO!

That is to say it is not enough for PenguinGraphics to live on top of
GGI,  other
parts of the project need to a well, otherwise we are hacking into
places we are
not allowed to be.

Sound might be OK, since GGI sound support is minimal, but input is an
integral
part of the GGI.    They define a display as an output device + a
keyboard.   GGI
programs grab events from GGI.

I am not sure how well developed the GGI input stuff is, or wether it
even supports
joysticks yet.  PPlay input should focus on two things:
    * Layer O wrappers for GGI input stuff.
    * Layer P == Codeveloping GGI.
Events should be translated from raw hardware or X events to GGI events,
not to PPlay
events.

The alternative would be to drop the GGI.  That would not be fun.  So I
suggest the input
people _at_least_  should grab the GGI, have a look at the sources and
even join the GGI
mailing list (although that means wading through incredible amounts of
irrelevant mail).

Sorry for having to write this message.   But I feel it is important.