Introduction to EON SDK - Construction IT research at VTT

More documents

Recommendations

Info

User Guide Techniques EON SDK Basics EON EON is a VR development tool that is built on an architecture that is highly modular, extensible and versatile. Using the EON Studio application you can create fully interactive 3D worlds that are executed and rendered in real-time by the run-time viewer EON/X. The viewer can be embedded in various host applications such as Web browsers, RAD and multimedia authoring tools. 3rd Party EON Modules EON Studio View Modules (Scengraph, Butterfly, etc) EON Studio Application Object Model (IAutApp, IAutDoc, IAutSettings, etc) EON Studio (windowing, inter-module messaging, license management, etc) NodeBag API (INodeBag) Design Mode EON Simulation Simulation Node Scen Node Run-time Mode Frame Node Custom Node 1 Mesh Node Custom Node 2 ... NodeBag API (INodeBag) EON/X (ActiveX control) EON Studio (Simulation Window) Custom Viewer (Currently not supported by the SDK) Legend: = SDK creatable component = EON pre-defined component Embedded in... EON Viewer Other ActiveX control Container (Internet Explorer, MS Word, VisualBasic, etc) Figure 3. The EON architecture As you can see the EON system is split into two distinct modes, and using the SDK you can extend both parts of the system. By creating EON Modules, you can extend the design mode functionality, inside EON Studio. You can also create custom nodes to supply or 6 EON SDK 2.53.0
User Guide Wizards enhance functionality in run-time mode. To let the user configure these nodes in design mode, you have essentially three choices: provide custom properties dialog for each node (most common), create a custom module or let EON Studio takes care of it (you will get a standard properties list similar to Visual Basic). EON uses Microsoft COM extensively to interface against both internal and SDK-created components. Therefore, most components in EON are COM objects, including nodes, modules, the run-time viewer (EON/X), etc. Inside EON As a plug-in developer, you must understand the EON architecture in a deeper way and need to have working knowledge of C++. On the other hand, you will be able to utilize the power of EON in full strength since you will have access to the same interface and functionality that are used by internal components as well. The kernel of an EON simulation is the Scenegraph. This is the place where all nodes are located. EON Studio can be seen as a tool to configure and insert nodes into this graph (and to make connections between nodes so that events can be transferred from node to node). To access this collection of nodes, the Nodebag component is used. This COM object exposes an interface named INodebag, to encapsulate the inner structure of the collection and to let the rest of the system access it in a controlled way. In most cases, the plug-in developer would not need to deal with the Nodebag component directly, unless you would like to develop your own viewer or similar. The real-time 3D graphics is handled by the simulation node, which is the root node of the scenegraph. This is where the main execution loop lies, to traverse and activate the rest of the nodes in the scenegraph to form a complete simulation. This node also handles mouse and keyboard input, in addition to route management. A route is a connection between two nodes, which will permit a node to send an event to another one. Other additional input channels (trackers, etc) and visual elements (shapes, lights, sounds, videos, etc) are handled by specialized nodes, which are added when needed. This means the run-time system can be very lightweight and flexible but also powerful and versatile at the same time. Using this SDK you can further enhance this system by creating and adding your own nodes to the system. These nodes can provide totally new functionality or just enhance or replace the standard ones. These nodes are deployed and used in the same way as the standard nodes that are shipped with EON. Hence, these plug-in components are truly integrated with the system. 2.5 7
Page 1 and 2: Introduction to EON SDK Jan 2002 ©
Page 3 and 4: User’s Guide Introduction Introdu
Page 5: User Guide Installation modules. By
Page 9 and 10: User Guide Wizards or multiple-valu
Page 11 and 12: User Guide Wizards EON SDK can also
Page 13 and 14: User Guide Wizards Although not fea
Page 15 and 16: User Guide Wizards • The name of
Page 17 and 18: User Guide Wizards lists based on t
Page 19 and 20: User Guide Wizards Studio are actua
Page 21 and 22: User Guide Wizards 9. Select which
Page 23 and 24: User Guide Wizards Node class defin
Page 25 and 26: User Guide Wizards If you use Direc
Page 27 and 28: User Guide Wizards disable licensin
Page 29 and 30: User Guide Wizards Writing modules
Page 31 and 32: User Guide Techniques when it goes
Page 33 and 34: User Guide Techniques the * and ->
Page 35 and 36: User Guide Techniques ); if (FAILED
Page 37 and 38: Reference Guide Introduction Introd
Page 39 and 40: Reference Guide Classes in EON SDK
Page 41 and 42: Reference Guide Modules Modules Int
Page 43 and 44: Reference Guide Interfaces IAgent U
Page 45 and 46: Reference Guide Interfaces SetDefau
Page 47 and 48: Reference Guide Interfaces GetIdOfN
Page 49 and 50: Reference Guide Interfaces SetStrin
Page 51 and 52: Reference Guide Interfaces GetInsta
Page 53 and 54: Reference Guide Interfaces GetJoyst
Page 55 and 56: Reference Guide Interfaces GetRefer
Page 57 and 58:
Reference Guide Interfaces UseLogTy
Page 59 and 60:
Reference Guide Interfaces ISimulat
Page 61 and 62:
Reference Guide Interfaces Index Ac
Page 63:
Reference Guide Interfaces LockRend
show all

Introduction to EON SDK - Construction IT research at VTT

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?