User Interface Service Software Developerís Guide - Hitech Projects

More documents

Recommendations

Info

January 2008 Public 3.6 Appendix 3.6.1 Multimodal Fusion sample files and messages 3.6.1.1 Properties file for time windows: amigo.mmf.timeout.long.selection=2000 amigo.mmf.timeout.long.sentence=2000 amigo.mmf.timeout.long.gesture=2000 amigo.mmf.timeout.short.selection=1000 amigo.mmf.timeout.short.sentence=1000 amigo.mmf.timeout.short.gesture=1000 3.6.1.2 MMIL message example for gesture gesture switchOn pending 3.6.1.3 MMIL message example for selection selection pending Light1Room3 light CeilingRoom3 ceiling 3.6.1.4 MMIL message example for sentence Amigo IST-2004-004182 97/114
January 2008 Public request speak ellipsis pending definite CD_Player 3.7 GUI-Service Component Overview Nearly every applications needs a way to get in to contact with the user. Typically this is done by a graphical user interface designed for a special application. So the user is presented a graphical interface for his text application, for his painting application, to control the TV or to control the washing machine. Usually, this means that the developer of an application has to write program code for the core service and program code for the GUI. These GUIs are specialised to the problem field their belong to. Unfortunately, the user interfaces of applications that belong to the same field, but produced by different manufactures, will typically differ enormously. As a consequent a user is unfamiliar when changing devices, even if they belong to the same area. Today and in the future it will be quite usual that users are getting in contact with many different environments equipped with variants services/devices of numerous manufactures. As a result, it will be impossible to bring an Amigo middleware to success if a user has to learn the inner logic of each service each time he is exposed to a new environment. For this reason, Amigo will use a different way. In Amigo not every service has to implement an own GUI-Application, instead it tries to build one single integrated GUI-Service, which combines every given service to build a homogenous control interface of the environment. The actual GUI is automatically generated by the GUI-Service exploring information provided by the services. Therefore each service has to explain it’s capabilities (functionalities) and the internal dependences. The GUI-Service will build an integrated control model out of the numerous descriptions and allows different GUI-Interfaces of different manufactures to enter this model and to make use of it. This approach makes use of the classic MVC (model view control) approach. The descriptions and the related services represent the model. The control is done by the GUI-Service, while the views are represented by the realised GUI-Interfaces connected to the GUI-Service. Provider IMS Introduction Development status Amigo IST-2004-004182 98/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 100 and 101: January 2008 Public Intended audien
Page 102 and 103: January 2008 Public 3.9 Component A
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?