client/display changes

[Hakan Ardo <hakan@debian.org>]

Hi,
to remove the dependencis between the client and display oils and get
rid of the typecasting in the client I have done the following:

 - Renamed the mCreateDisplay message mCreateGtkDisplay as it will
   always create a gtkDisplay. This because a gtkClient will always
   want a gtkDisplay, and nothing else.

 - Created a virtual calss gtkDisplay contaning the methods the client 
   need from the gtkdisplay which I suppose should be replaced by a
   set of messages when I get around to it.

 - This means that the creation of the display has to be done in
   gtkBroser and not in Browser. Therefor I have renamed
   setDisp(Display *) to newDisp(int id) which is in the Browser but
   not defined untill in the gtkBrowser. It craetes the display object
   and returns it.

 - This also meens that I had to move disp and getDisp() from Browser
   to gtkBrowser.

 - I have also removed the newdisp object from the Browser class as it 
   was not used.

(I have not been able to testa any of the chnaged by it does at least
 compile...)

What do you display fokes say about this? I take back my sugestion
about only gtk dependencis in the display, after a close studie of the 
client and display code, I can see we need both, and using this
approch there should be no problem with it either.

  


-- 
---------------------------------------------------------------
 Name:        Hakan Ardo
 E-Mail:      hakan@debian.org
 WWW:         http://www.ub2.lu.se/~hakan/sig.html
 Public Key:  Try "finger hakan@master.debian.org"
 Fingerprint: E9 81 FD 90 53 5C E9 3E  3D ED 57 15 1B 7E 29 F3
 Interests:   WWW, Programming, 3D graphics

 Thought for the day: As long as one understands, the
 spelling does not matter :-)
---------------------------------------------------------------

PGP signature