GUI - Comments

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

OK some thoughts  about the GUI.  I like it.

Here is the basis for a signal/slot mechanism similar to
Qt. 
 
The equivilent of the Qt signal would be some object which
maintained a list of Slots.  When this object is activated,
it gets some datum from the sender and forwards it to the
recipients by some kind of function call (i.e a Qt Slot).

Senders would contain such objects a data memebers.

Connecting a signal to a slot would be a matter of adding
the Slot list.  

I suppose this is basically what goes on "under the hood" of
Qt.


h4>What kind(s) of target surface(s) for mouse
 pointers should exist?</h4>

Are you talking about the actual pixmap representing
the mouse cursor? This can be handled nicely.
The 2d API can supply the outside with a surface
which represents mouse pointers, as well as GC's
for drawing into them.  These surfaces would bee
representations for something defined in the GGI.



<li>For Drag'n'Drop and similar mechanisms it 
is very useful if the
 mouse pointer can temporarily take the look of 
 the dragged
item or be merged with it.</li>
Maybe not.  As far as the user is concerned, 
the mouse pointer is an object dragging the
object conerned, they are distinct.  From a
programmers point of view, it allows the
object being dragged to be an arbitrary image,
while the mouse pointer would probably have to
be a pixmap.