VenueClient restructure

[Susanne Lefvert]

cool. Eric removed the inheritance already and the code is in cvs.

On Wed, 2 Jul 2003, Robert Olson wrote:

> At 09:03 AM 6/24/2003 -0500, Susanne Lefvert wrote:
> 
> >I've been thinking about inheritance and not inheritance between
> >bin.VenueClient and AccessGrid.VenueClient and would like to argue for
> >inheritance :) If we remove inheritance, both classes will have to have an
> >instance of the other class.
> 
> That's not an argument for using inheritance..
> 
> >Events will be received by AccessGrid.VenueClient, which
> >have to call bin.VenueClient and a button event will be received in
> >bin.VenueClient that will call AccessGrid.VenueClient.  If we remove
> >inheritance, both classes must have callback methods for the other
> >class to use.
> 
> That's fine; the same communication is happening in each case; it is a big 
> win to make explicit what is actually happening.
> 
> >   If we then add a new client (non ui based or something
> >else), it will have to implement all callback methods instead of just
> >overriding necessary methods from AccessGrid.VenueClient.
> 
> Right. Again, making the communication explicit instead of implicit in the 
> inheritance is a win (I have a hard time understanding the current 
> structure because I have to keep going back thru to see what's inherited, etc).
> 
> 
> --bob 
> 
>