Developer Example: Alternate Venue Clients

The standard Access Grid Venue Client offers a typical user interface to all the functionality of a Venue, including people, data, services, and applications in the Venue, doorways to other Venues, chat, control of media tools, etc. As the standard client, it is appropriate for it to be as full featured as possible. It is, however, only one user interface built on top of the underlying components that connect the user with the Venue. These components can (and should) be used to build other interesting applications.

Consider the range of possible clients to the Access Grid, built using the foundation code in the current toolkit, such as the current Venue Client. Low-end clients could be more usable, appropriate for public Access Grid "kiosks", and driven by a touch screen. High-end clients could provide a more natural interface to Venues, giving the user more of a sense of being "in" a Venue and interacting with the contents. One could also imagine immersive 3D or VR clients. Two starting points for developing alternate Venue Clients are given in the following examples.

Venue Kiosk


A simplified Venue Client that compromises functionality for ease of use. The Venue Kiosk presents Venues in the same manner that a building directory might present the building's occupants.




Immersive Venue Clients

An introduction to possible immersive clients for the Access Grid, and a simple example of an immersive client to demonstrate what could be done.

login or register to post comments