VenueClient restructure

[Eric Olson]

Susanne raised some good questions.  To the doc, I added purpose, 
pros/cons, and a sequence diagram (sequence is mostly differences -- not 
as detailed as the one in the VenueClient doc).  I included Susanne's 
pros and cons from her e-mail and added my own.  I kept changing the 
pros/cons, so I thought I would just send others will have more ideas.

I also did some search and replacing in the code and ended up with a quick 
implemenation to make sure I wasn't missing something in the design.

Eric

On Tue, 24 Jun 2003, 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.  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.  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. 
> 
> It would be nice to add a section to the document that gives motivation 
> to the suggested design changes.  And maybe more sequence diagrams to 
> make it clearer (what we have now compared to how we want to change it).  
> 
> Susanne
> 
>     
> 
> 
> 
> 
> 
> On Mon, 23 Jun 2003, Eric Olson wrote:
> 
> > Here is a short (one page) description/overview of VenueClient 
> > restructuring.
> > 
> > Comments are welcome -- if you know of specific areas that should be 
> > addressed in more detail, please let me know.
> > 
> > Thanks,
> > Eric
> > 
> > 
> > 
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: VenueClientRestructure.doc
Type: application/msword
Size: 37888 bytes
Desc: 
URL: <http://lists.mcs.anl.gov/pipermail/ag-dev/attachments/20030625/b47abbe6/attachment.doc>