planning

[Terry Disz]

AG wish list

Venues API, protocols, examples
This means an API reference document and a Programmers guide to:
		Creating services, adding them to the venue, discovering and using them,
with exemplars.
		Creating shared applications

Shared pointer tool
	An API to use that creates and uses a shared pointer.

Automatic  bridging setup and switch over

Capability of indexing all venues on a server, direct access to venues, an
API to list all venues, filled-in venue bookmarks  of all venues in a
server.

Start up capture vic's iconified.

Don't start vic's over the client window

Data storage
	Allow folders with normal permissions, etc - see Justin's suggestions for
this.

PPT
	GUI
	Reliable
	Synch up on slide changes
	Auto loading from venue
	Integrated into client

Fix heartbeat client drop during busy sessions

Interface - separate participants, data, services, etc

Clarify difference between services, applications, etc

Provide the ability to invite participant/groups into things and autolaunch
apps at clients

Tear off sections of the interface







> -----Original Message-----
> From: owner-ag-dev at mcs.anl.gov [mailto:owner-ag-dev at mcs.anl.gov]On
> Behalf Of Ivan R. Judson
> Sent: Thursday, June 05, 2003 9:09 AM
> To: 'AG Dev'
> Subject: planning
>
>
>
> Hey,
>
> Next week we're going to be dealing with our planning for 2.1, I'd like
> folks to provide lists of what they think is missing or needs to be fixed
> (or started) to make AG2.X better, faster, cheaper, more widely used, etc.
>
> Please send lists by Friday afternoon.
>
> --Ivan
>