|
||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||
See:
Description
| Class Summary | |
| Ana | applet delivering content for VR visitors (ana) |
| CityProxy | dataspace proxy with an inner class handlers for each visitor type |
| Content | servlet displaying initial content page for EQUATOR city demos |
| ContentData | |
| ContentDataImpl | |
| Dub | applet delivering content for WWW visitors (dub) |
| Entry | servlet-based entry point for EQUATOR city demos |
| Explanation | |
| ExplanationImpl | |
| ExplanationPublisher | utility class for adding, updating or deleting explanations in dataspace |
| LinkyListener | utility class for querying Linky and inserting content into dataspace |
| LocationListener | service class for generating location- and device-aware content |
| Map | servlet displaying applet frame for EQUATOR City demos |
| TOC | servlet displaying list placeholder for EQUATOR city demos |
| Transition | |
| TransitionData | |
| TransitionDataImpl | |
| TransitionImpl | |
| TransitionPublisher | utility class for adding, updating or deleting transitions in dataspace |
| TriggerTest2 | service class to transform positions into named locations |
| UserHolding | |
| UserHoldingImpl | |
| UserLocation | |
| UserLocationImpl | |
EQUATOR city applets, proxy and service classes supporting mixed visiting experiences for physical, World Wide Web (WWW) and virtual reality (VR) visitors.
Physical visitors use a handheld (Compaq iPAQ or HP Jornada 568) or wearable running custom software that polls positioning sensors, presents awareness information (map or radar) and calls a WWW browser to refresh its display. WWW visitors use a browser that runs an applet (Dub) that displays a map for awareness information and mouse input of position, and refreshes a frame. VR visitors use a VR renderer (immersive or non-immersive) and also use a browser that runs a faceless applet (Ana) that refreshes a frame. The VR renderer runs on top of an EQUIP dataspace. Visitors communicate via an EQUIP audio service.
Applet clients are downloaded from a servlet-based entry page (Entry) that permits entry of visitor type and name. The browser for a physical visitor has its home page set to a previously known location.
The handheld/wearable client and both applets use an ASCII protocol to communicate with a proxy (CityProxy) for an EQUIP application dataspace. The dataspace contains a spatial model corresponding to the physical space being visited, with a number of other application-specific data items. The proxy inserts user and device data from the clients (other than the VR renderer) into the dataspace, and responds to content events by retrieving and munging content, and by notifying clients of content availability. For physical and WWW clients the proxy also updates position data, resulting in rendering of VR avatars for physical and WWW visitors, and advises of positions of all visitors for awareness displays.
The pipeline of EQUIP processes that transforms position data into location- and device-aware content consists of a location service and a linking service. The location service (TriggerTest2) inserts named, axis-aligned bounding boxes into the spatial model in the dataspace and responds to events posted by an EQUIP collision-detector by inserting items mapping users to locations. The linking service (LocationListener) responds to user-location events by querying the Linky contextual link server, and inserting content data items.
|
||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||