20,741
edits
Nasal HLA standalone: Difference between revisions
Jump to navigation
Jump to search
m
→Hight Level Architecture
| Line 57: | Line 57: | ||
* [https://gitorious.org/fg/simgear/blobs/next/simgear/hla/HLAObjectClass.cxx HLAObjectClass.?xx] | * [https://gitorious.org/fg/simgear/blobs/next/simgear/hla/HLAObjectClass.cxx HLAObjectClass.?xx] | ||
* [https://gitorious.org/fg/simgear/blobs/next/simgear/hla/HLAObjectInstance.cxx HLAObjectInstance.?xx] | * [https://gitorious.org/fg/simgear/blobs/next/simgear/hla/HLAObjectInstance.cxx HLAObjectInstance.?xx] | ||
Demo code at: | |||
* https://gitorious.org/fg/flightgear/blobs/next/src/Network/HLA/hla.cxx | |||
* https://gitorious.org/fg/flightgear/blobs/next/utils/fgai/ | |||
<syntaxhighlight lang="cpp"> | <syntaxhighlight lang="cpp"> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
In the long run, one would need to implement the full interface of the HLAObjectClass, for example as part of the cppbind framework in simgear/nasal/cppbind- that way, cppbind APIs would become accessible through HLA, so that all cppbind APIs could also be used from a standalone interpreter that would not need to run inside the fgfs main loop anymore. | In the long run, one would need to implement the full interface of the HLAObjectClass, for example as part of the cppbind framework in simgear/nasal/cppbind- that way, cppbind APIs would become accessible through HLA, so that all cppbind APIs could also be used from a standalone interpreter that would not need to run inside the fgfs main loop anymore. | ||
<references/> | <references/> | ||