User Interface Service Software Developerís Guide - Hitech Projects

More documents

Recommendations

Info

January 2008 Public 3.9 Component Architecture GUI Service The architecture of the GUI service is shown in Figure 4. Figure 4Components of the complete GUI service The core components of the GUI service are • Services and devices: The actual services and devices embedded in the environment implement the various functions. They combine sensor input with user requests. The services and devices form the actual application intelligence within the environment. They register with the UI service in order to be able to interact with the user. Hence, they do not directly interact with the user but just describe their requirements and possible options the user may choose. To this end, during registration, ontology based descriptions of the services are transferred to the UI service. • A user interface service: The user interface service (UI-service) provides the actual control mechanisms for the presentation and interaction components of the system. Further, it controls the interaction of user and system and also handles the different user profiles. The UI-service determines the actual content and navigation options of the user interface. Both elements are generated based on the navigation model associated with the corresponding user. Content and navigation model are transmitted to the presentation and interaction components. Further, the UI-service receives and forwards events that are received from services. The input that is generated by the user is processed by the UI-service and is either forwarded to the specific services or devices or is used to control navigation within the user interface. • A knowledge base manager: The knowledge base manager holds the entire knowledge about the environment. This includes information about available services and devices. As a result, each device transmits its knowledge base that covers the device’s functionality to the manager. The manger takes the various knowledge bases and builds a large information database from it. The UI-service uses this integrated knowledge based in order to determine which information and what navigation structures shall be displayed. • A user manager: The user manager takes care of the various navigation strategies of the different users. Note that this information is stored and retrieved using UMPS. • Presentation and interaction components (PI-component): These components are responsible for displaying the actual information and receiving the user input. They register with the UI-service and receive the information that are to be shown. For Amigo, a Java based PI-component has been implemented. In order to display a Amigo IST-2004-004182 101/114
January 2008 Public specific piece of information, a presentation repository is used. This repository stores for a defined set of information types how they shall be shown on the screen. The association of information type and the actual presentation on the screen is done via a presentation map. Searching the map is based on the environmental model. 3.9.1 Interfaces Figure 4 and Figure 5 show the interfaces that are used within the UI-service. Figure 5 Interface definitions of components within the UI-service The interface between the UI-service and devices or services is IServiceConnector. By using this interface, services can register with the UI-services. This interface is implemented by class ServiceManager. It is also used by services and devices to inform the system about changes. Further, services and devices may use this interface to deregister themselves from the system. In order to receive input generated by the user, the IService interface must be implemented. Moreover, this interface can be used to retrieve values and valid value ranges. The interface IUIRegistrar is implemented by class UIClientManager. PI-components use this interface to register or deregister themselves from the UI-service. For each PIO-component a separate instance for the class VirtualUIClient is created during registration. The instances provide interfaces of type IUIConnector, which is responsible to establish communication between PI-components and the UI-service. PI-components use this interface to transmit user Amigo IST-2004-004182 102/114
Page 1 and 2:
IST Amigo Project Deliverable D4.7
Page 3 and 4:
January 2008 Public Table of Conten
Page 5 and 6:
January 2008 Public 3.2.3.4 Configu
Page 7 and 8:
January 2008 Public 1 Speech based
Page 9 and 10:
January 2008 Public Bugs - Patches
Page 11 and 12:
January 2008 Public 1.2 Deployment
Page 13 and 14:
January 2008 Public SWIsvcMonPort=
Page 15 and 16:
January 2008 Public # RealSpeak por
Page 17 and 18:
January 2008 Public 6666 20 10
Page 19 and 20:
January 2008 Public true C:/Temp/
Page 21 and 22:
January 2008 Public [Recording_TCP]
Page 23 and 24:
January 2008 Public Example string
Page 25 and 26:
January 2008 Public 1.3.2 Explicit
Page 27 and 28:
January 2008 Public • the user sp
Page 29 and 30:
January 2008 Public parameters. The
Page 31 and 32:
January 2008 Public In this example
Page 33 and 34:
January 2008 Public Assuming that y
Page 35 and 36:
January 2008 Public Step 3 Rebuild
Page 37 and 38:
January 2008 Public 1.4.1.3 Run Tra
Page 39 and 40:
January 2008 Public On a successful
Page 41:
January 2008 Public At the end the
Page 44 and 45:
January 2008 Public At the end the
Page 46 and 47:
January 2008 Public Step 5 In the S
Page 48 and 49:
January 2008 Public Step 8 In Serve
Page 50 and 51:
January 2008 Public 1.4.2.5 Run Voi
Page 52 and 53: January 2008 Public 1.4.2.6 Run Voi
Page 54 and 55: January 2008 Public As soon as the
Page 56 and 57: January 2008 Public • SoapBox bas
Page 58 and 59: January 2008 Public 2.2.1.1.4 Confi
Page 60 and 61: January 2008 Public The gesture ser
Page 62 and 63: January 2008 Public • Folder Volu
Page 64 and 65: January 2008 Public After installat
Page 66 and 67: January 2008 Public Up 65 In
Page 68 and 69: January 2008 Public Figure below pr
Page 70 and 71: January 2008 Public Development sta
Page 72 and 73: January 2008 Public Tools Oscar Fil
Page 74 and 75: January 2008 Public Bugs None Patch
Page 76 and 77: January 2008 Public 3.2 Deployment
Page 78 and 79: January 2008 Public Scene descripti
Page 80 and 81: January 2008 Public 3.2.2.5 Comp
Page 82 and 83: January 2008 Public 3.3 Component A
Page 84 and 85: January 2008 Public 3.3.3 Multimoda
Page 86 and 87: January 2008 Public Fallback soluti
Page 88 and 89: January 2008 Public 3.3.3.4 Compone
Page 90 and 91: January 2008 Public 3.4 Tutorial 3.
Page 92 and 93: January 2008 Public scene, the imag
Page 94 and 95: January 2008 Public objectDesc VCR
Page 96 and 97: January 2008 Public 3.5 Assessment
Page 98 and 99: January 2008 Public 3.6 Appendix 3.
Page 100 and 101: January 2008 Public Intended audien
Page 104 and 105: January 2008 Public interface input
Page 106 and 107: January 2008 Public Figure 7 Classe
Page 108 and 109: January 2008 Public different sub-m
Page 110 and 111: January 2008 Public Figure 3: Menu
Page 112 and 113: January 2008 Public 30% 10% 7% 0% 5
Page 114 and 115: January 2008 Public Figure 10: Conc
show all

User Interface Service Software Developerís Guide - Hitech Projects

Create successful ePaper yourself

Delete template?

Save as template?