User Interface Service Software Developerís Guide - Hitech Projects

More documents

Recommendations

Info

January 2008 Public scene, the image will disappear, that is because this scene is built using colored masks and the FillerDemo uses the masks to highlight objects. 8- another feature is the possibility to have sprites representing the objects. An object could have many states associated to different sprites. Load the office scene and type "state laptop" to see the current state and the possible state. Type "state laptop closed" to close the laptop. 3.4.2 Multimodal Fusion component development The component packages are the following: • org.amigo.ius.user_interface.multimodal_fusion.impl • org.amigo.ius.user_interface.multimodal_fusion • fr.loria.led.mmil.template.jaxb • fr.loria.led.mmil.template • fr.loria.led.mmil.objects • fr.loria.led.mmil.jaxb Packages under fr.loria.led.mmil are intented to be merged into the main MMIL trunk, but are contained in this repository for now. Important classes: • MultiModalFusionManagerStub – The stub class for use by clients. • MultiModalFusionManagerImpl – The Component’s main class. Basically serves as proxy to the fusionSynchronizer for marshalling/unmarshalling MMILComponents, and filtering the accepted templates. • FusionSynchronizer – Manages a pool of threads waiting for messages occurring in configured time windows, and releasing the messages after time goes out. Calls Fusion.doFusion when messages must be merged. • Fusion – Do the actual fusion of several MMIL components. 3.4.3 Multimodal Fusion application development In order to give a tutorial for how to use the service from another application, I describe the test client, since it plays the role of several applications sending their output to After the main bundle of the Multimodal Fusion service is started, one can either use it with the test service or directly. Here I explain how to use the MFM through the description of the test service. The test service exposes a OSGi shell command “scenario” that runs a scenario described in a xml file (either in the test service jar file or via any url) such as:
January 2008 Public tester/res/examples/home.owl"> gesture switchOn pending request speak switchOn imperative pending definite CD_Player Using the “scenario” command is done either with: • scenario sc01 (where sc01.xml is stored in the jar of the tester, under res/scenarios) • scenario The scenario element contains the initialization parameters: ontology, objects and commands files – The ontology is an OWL file, objects and commands are both xml files with MMIL data: Objects (in res/examples/example-application-objects.xml) objectDesc container Living_Room Room3 objectDesc Light Light1Room3 objectDesc TV TV1Room3 Amigo IST-2004-004182 92/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 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 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?