20,741
edits
Nasal HLA standalone: Difference between revisions
Jump to navigation
Jump to search
m
→High Level Architecture
| Line 76: | Line 76: | ||
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. | ||
To add HLA support to cppbind, we'd need to provide corresponding [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/cppbind/detail/from_nasal_helper.cxx from_nasal_helper()] and [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/cppbind/detail/from_nasal_helper.cxx to_nasal_helper()] templates to convert various HLA types to their corresponding Nasal equivalents and vice versa. | |||
<references/> | <references/> | ||
[[Category:Developer Plans]] | [[Category:Developer Plans]] | ||