-
Notifications
You must be signed in to change notification settings - Fork 0
Runtime Engine Library
The Magic Lantern Software Development Kit provides a runtime engine to facilitate title execution. In fact, if a title is not using the Magic Lantern Runtime Engine, then it is not a Magic Lantern title. The Runtime Engine controls the lifecycle of the title.
The execution model that contols the sequencing of Magic Lantern titles is a cyclic process repeated once per frame. Each actor, role, set, and stage receives control of the processor, in that order. By default, on each frame, all of the actors execute before any of the roles; all of the roles execute before any of the sets, etc. This scheduling order is not strict, however, since an actor may explicitly pass control to its role and that role may explicitly pass control to its set. Programmers can also reorder or augment the scheduling.
The idea behind tha actors-then-roles-then-sets-then-stage ordering is that first the interactivity is computed (actors), then the presentation is computed (roles), then the various resource controllers gain control (sets), then the entire frame presentation is created (stage).
The Runtime Engine Library povides support for:
- Interface and base classes for Actor, Role, Media Reference, Set, Stage and Prop title components,
- Event dispatching,
- Scheduling of title execution,
- Reading and processing the Digital Playprint.
The Runtime Engine Library API documentation can be found in the form of Javadoc and Doxygen HTML pages. The Javadoc pages correlate to the Java version of the API while the C++ version of the documentation is generated using Doxygen.
API documentation for the Java packages are not currently available online. To generate the Javadoc using the Eclipse project for the Runtime Engine Library, simply follow these instructions:
- In the com.wizzer.mle.runtime project, select javadoc.xml in the Package Explorer view.
- Right-click the resource and select Open Javadoc Wizard... from the context menu. This action will bring up the Javadoc Generation dialog.
- Make sure the Javadoc command: field points to the javadoc.exe executable in your environment.
- Select the Next>, button, accepting the the default configuration.
- Again, select the Next>, button, accepting the the default configuration.
- Finally select the Finish button.
- The Javadoc HTML will be generated in the project's doc directory.
API documentation for the C++ libraries is not yet available.
Copyright (c) 2019-2024 Wizzer Works All rights reserved.
Contents
- User Home Page
-
Developer Home Page
- SDK Build Environment using Microsoft Visual Studio
- SDK Build Environment using Microsoft MSBuild
- SDK Build Environment for Linux Platform
- SDK Build Environment for Qt Linux Platform
- SDK Build Environment for J2SE Platform
- SDK Build Environment for Android Platform
- Rehearsal Player Build Environment using Microsoft Visual Studio
- Rehearsal Player Build Environment for Linux Platform