suggestions for renaming bin/VenueClient, etc.

[Eric Olson]

Are there any suggestions for the new name of bin/VenueClient ?  I agree 
with Bob that it could be changed (and Ivan mentioned it with the 
restructuring too) to reflect that it should only contain UI code.

* Is "GuiClient" descriptive enough or would we rather have wxClient or 
wxGuiClient? (what sort of other clients are we expecting? web? 
scheduler?)

* As long as we're on the subject, is CommandLineVenueClient also a good 
name for the command-line version?

Please e-mail your ideas.  It's not extremely critical, but the fewer 
times we move filenames in cvs the better (cvs doesn't handle it all too 
well).  I'm assuming we would change the class name And the filename, but 
let me know if you disagree.

* One more thing, Bob suggested a file to launch the client so people 
wouldn't be typing "something.py".  Do we all agree that would be a good 
idea -- if so, what's the best name for that?

Eric


---------- Forwarded message ----------
Date: Wed, 2 Jul 2003 15:44:17 -0500 (CDT)
From: Susanne Lefvert <lefvert at mcs.anl.gov>
To: Eric Olson <eolson at mcs.anl.gov>
Subject: reminder

>From mud because I will forget to tell you this and am going on vacation 
next week:

------------------------------------------------------------------------
Bob hrms, the split between the code in bin/VenueClient and the code in
ag/venueclientuiclasses is nonobvious
Bob says, "and nonintuitive"
>nd bob
You nod to Bob.
Bob again argues for a module say "GuiClient"  that contains *all* of the 
gui
client code
>bob, and then remove bin/VenueClient completely
You [to Bob]: and then remove bin/VenueClient completely
Bob says, "and to call the thing that people run say "ag2" whcih is just a
(batch file/shell script) that invokes python with the right .py file"
Bob doesn't like peopel typing "something.py" to start somethign
------------------------------------------------------------------------