User Tools

Site Tools


manual:tuio_protocol

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
manual:tuio_protocol [2009/06/03 23:28]
camille created
manual:tuio_protocol [2009/06/09 12:26] (current)
camille
Line 4: Line 4:
  
  
-//(from [[http://tuio.lfsaw.de]])//+//(from [[http://www.tuio.org/]])//
  
 <​blockquote>​TUIO is a simple yet versatile protocol designed specifically to meet the requirements of table-top tangible user interfaces. ​ Inspired by the idea of interconnecting various existing table interfaces such as the [[http://​www.iua.upf.edu/​mtg/​reacTable/​|reacTable]],​ being developed in Barcelona and the tDesk from [[http://​www.techfak.uni-bielefeld.de/​ags/​ni|Bielefeld University]],​ this protocol defines common properties of controller objects on the table surface as well as of finger and hand gestures performed by the user. <​blockquote>​TUIO is a simple yet versatile protocol designed specifically to meet the requirements of table-top tangible user interfaces. ​ Inspired by the idea of interconnecting various existing table interfaces such as the [[http://​www.iua.upf.edu/​mtg/​reacTable/​|reacTable]],​ being developed in Barcelona and the tDesk from [[http://​www.techfak.uni-bielefeld.de/​ags/​ni|Bielefeld University]],​ this protocol defines common properties of controller objects on the table surface as well as of finger and hand gestures performed by the user.
Line 49: Line 49:
  
 There is not much to do than launch the reacTIVision program. ​ This application send OSC message to port ''​3333''​ on the local host by default, this means that you will need to change the OSC Input Port in OSCulator to ''​3333''​. There is not much to do than launch the reacTIVision program. ​ This application send OSC message to port ''​3333''​ on the local host by default, this means that you will need to change the OSC Input Port in OSCulator to ''​3333''​.
- 
- 
 ==== Messages definition ==== ==== Messages definition ====
  
-As soon as OSCulator receives TUIO messages, it will display them in the main window((remember, ​these are actually ​interpreted ​messages, not raw TUIO messages)).  Those message ​always come in pair:+As soon as OSCulator receives TUIO messages, it will display them in the main window((remember, ​the messages ​are interpreted,​ not displayed in the raw TUIO format)).  Those messages ​always come in pair:
  
   * the message carrying position, orientation and speed informations,​ for example ''/​tuio/​2D/​obj/​1''​ ;   * the message carrying position, orientation and speed informations,​ for example ''/​tuio/​2D/​obj/​1''​ ;
-  * and the message carrying activity information,​ for example ''/​tuio/​2D/​obj/​1/​activity''​. ​ This messages tells is the object is visible.  ​If it is not visible, ​an activity message is sent with a value of ''​0'', ​or ''​1'' ​if the object becomes visible.+  * and the message carrying activity information,​ for example ''/​tuio/​2D/​obj/​1/​activity''​. ​ This messages tells if the object is visible ​or not.  ​When visible, a float value of ''​1.0'' ​is senton the contrary, the value is ''​0.0''​.
  
 The positional messages have the following format: The positional messages have the following format:
Line 94: Line 92:
  
 These are basically the same arguments as given by the TUIO protocol for ''​set''​ messages. These are basically the same arguments as given by the TUIO protocol for ''​set''​ messages.
- 
manual/tuio_protocol.1244064528.txt.gz ยท Last modified: 2009/06/03 23:28 by camille