VR-Link includes examples of how to create FOM Mappers, and of how to extend the top-level API to work with new FOM concepts.
These examples are in several subdirectories of ./examples.
-
The myFomMap example shows how to create a FOM Mapper for a new FOM, but assumes that the new FOM contains concepts already covered by VR-Link's API (so no extensions are necessary.) It also demonstrates how to put the new FOM Mapper into a shared library that can be loaded by DtExerciseConn, and by MAK applications like MAK Data Logger and VR-Forces. The shared library works with the FED file called MyFomMap.fed, which is in the VR-Link root directory.
-
The addAttr example demonstrates how to extend the RPR FOM by adding new attributes or parameters to existing classes, particularly when this requires extending VR-Link's API to work with them.
-
The testInter and testObj examples demonstrate how to add a new interaction or object class to your FOM, including extending VR-Link's API to work with them.
-
The testSimpInter example demonstrates a method of working with new interaction classes that does not use VR-Link's encoder and decoder classes. This implementation is simpler in some cases, but less extensible and less efficient. We do not provide a walk-through of this example. Please see comments in the source files for details.
All the examples except myFomMap create executables that work with the VrlExtend.fed FED file that is in the VR-Link root directory.
[<< Choosing a DtFomMapper] [Home]
