Wiki » History » Version 14
Version 13 (S. Wrede, 10/04/2011 06:47 PM) → Version 14/25 (S. Wrede, 10/04/2011 11:33 PM)
h1. Wiki
The RST project provides "Google Protocol Buffers":http://code.google.com/p/protobuf/ based "IDL specifications":http://code.google.com/apis/protocolbuffers/docs/proto.html for common data types using in robotic systems. Moreover, the build system converts these IDL specifications into libraries for C++, Java and Python.
* [[Installation]]
* [[OganizationConventions|Conventions regarding the organization of IDL files]]
* [[ConverterRepository|Information regarding a respository of common Converters for RSB]]
* [[Using RST]]
TODO
* Structure and Naming, Visibility
** Remove data / message / ... suffixes
*** stable vs. unstable prefixes
*** from a client developer: refer to revisions
*** include revisions in build artefacts
** Hierarchische Organisation
*** + Uebersichtlichkeit, e.g., in IDEs
*** - Commitment auf eindeutiges Strukturierungsmerkmal
** Flache Organisation
*** + Eindeutigkeit von Namen als Zwang zur Kommunikation
*** ? Hierarchie in Namensraum der Zielsprachen
* Versioning
* Release process
** Review process
* Java Outer Class Name
** Extend Styleguide and explain meaning
* Re-use von Typen (innere Typen bsp. Point in BoundingBox)
* Generische Komponenten
* Dokumentation mit typischen Usecases
* Lesen und Schreiben von Arrays
The RST project provides "Google Protocol Buffers":http://code.google.com/p/protobuf/ based "IDL specifications":http://code.google.com/apis/protocolbuffers/docs/proto.html for common data types using in robotic systems. Moreover, the build system converts these IDL specifications into libraries for C++, Java and Python.
* [[Installation]]
* [[OganizationConventions|Conventions regarding the organization of IDL files]]
* [[ConverterRepository|Information regarding a respository of common Converters for RSB]]
* [[Using RST]]
TODO
* Structure and Naming, Visibility
** Remove data / message / ... suffixes
*** stable vs. unstable prefixes
*** from a client developer: refer to revisions
*** include revisions in build artefacts
** Hierarchische Organisation
*** + Uebersichtlichkeit, e.g., in IDEs
*** - Commitment auf eindeutiges Strukturierungsmerkmal
** Flache Organisation
*** + Eindeutigkeit von Namen als Zwang zur Kommunikation
*** ? Hierarchie in Namensraum der Zielsprachen
* Versioning
* Release process
** Review process
* Java Outer Class Name
** Extend Styleguide and explain meaning
* Re-use von Typen (innere Typen bsp. Point in BoundingBox)
* Generische Komponenten
* Dokumentation mit typischen Usecases
* Lesen und Schreiben von Arrays