Aron (ArmarX Object Notation) is the ArmarX implementation of variants which can be transferred over the network via ZeroC Ice. Further, Aron is the data representation used in the ArmarX Memory System [ArMem](ArMem/ArMem). We distinguish between:
...
...
@@ -142,7 +144,7 @@ If no type object or DTO is available, we can at least derive some information f
To differ between data and type makes it easier to work with these Variants. In most cases, the type information is not relevant. Then you only have to check for the data type.
## Aron data and type objects
# Aron data and type objects
As already mentioned, we implemented wrapper classes around the DTO. These classes offer convenience methods and conversions and make lots things easier when working directly with Aron. These classes can be found at aron/core/[data,type]/variant/Variant.h.
...
...
@@ -171,7 +173,7 @@ If you have a DTO, you dont know the exact type but you want to have a Aron obje
If you know the type, you can use the constructor the specific Aron object.
### Example to create an Aron data dict from scratch
## Example to create an Aron data dict from scratch
Goal: Have an Aron dict with a list as member "the_list" and some values in it. Then echo the members and their descriptor as a string.
...
...
@@ -202,7 +204,7 @@ Goal: Have an Aron dict with a list as member "the_list" and some values in it.
Please note that we might add more methods or make the current ones more flexible (e.g. such as nlohmann::json).
## Lessons learned
# Lessons learned
- There is a difference between Aron data and Aron type
- There is a difference between Aron objects and Aron DTOs
