HSC2011/Communication: Unterschied zwischen den Versionen
Chrysn (Diskussion | Beiträge) documented information flow |
Chrysn (Diskussion | Beiträge) serial format |
||
| Zeile 35: | Zeile 35: | ||
|rowspan=2| <tt>software/ …/ base.js</tt> || JavaScript application || || library for developing games | |rowspan=2| <tt>software/ …/ base.js</tt> || JavaScript application || || library for developing games | ||
|- | |- | ||
| || <tt>Edubuzzer.event_occurred</tt>, … || game development API | | || <tt>Edubuzzer.event_occurred</tt>, <tt>Edubuzzer.send_set()</tt>… || game development API | ||
|- | |- | ||
| '''your application''' ||colspan=2| whatever you like || | | '''your application''' ||colspan=2| whatever you like || | ||
|} | |} | ||
== Serial format == | |||
The serial serialization format is important as it is passed through the whole software stack (from C to JavaScript, although both also use processed forms of it). Even if it not directly used in the "wire" format strucs and the JavaScript object representation, it can be used to understand the other representations. | |||
The serial format documentation also explains lots of details of how the devices can be controlled, so it is recommended reading for game developers env everyone else. | |||
Read it in full length at [[HSC2011/Communication/Serial protocol]]. | |||