Changes between Version 7 and Version 8 of MoonlightDesignOverview

Author:

gregor (IP: 132.180.237.113)

Timestamp:

11/27/06 17:23:28 (4 years ago)

Comment:

fixed some mistakes in the earlier edit

MoonlightDesignOverview

@@ -55 +55 @@
-which allows the operator graph manager to generate them without knowing
-any details of their implementation.
-
+
-Each operator graph node has a set of named and typed properties,
-through which its parameters are exposed. This mechanism is needed for
-animation component, which can then change these parameters based on some
-animation data, which is managed seperately.
-
+
-Currently, each operator graph node gets scene graphs into its 
-(named) input slots, which are then processed by the node. The result is
-connected with the input of a link, and vice versa. This terminology can
-be confusing sometimes, so be careful.
-
+
-Plugins may register own operator graph node factories with the operator
-graph manager, which allows for easy node creation by name. Operator
-the scene.
-
-=== The user interface ===
-
-The user interface core contains the implementation of the main window
-of Moonlight|3D together with its layout and view management mechanisms.
-    
-The so-called "views" are screen areas defined by sashes, which
-are oocupied by plugin-provided classes. They can be arranged into any
-given user-specified layout, which is usually loaded from an XML file.
-    
-=== The core ===
-
-If you want one of them, you have to go through ml.core.State to reach them, 
-unless you are provided with a reference to the target anyway.
-
+
-The plugin loader in ml.core.plugins takes care of loading the plugins in
-the right order. Every plugin must have a class which implements 
-dependencies. Currently, circular dependencies are not checked for and
-cannot be handled. Any other dependency structure should be fine, though.
-
+
-Please note that plugin loading is a process which takes several steps.
-First the plugin class is instanced, which does not mean that the associated
-actually start to register it's payload (mostly factories) with the core 
-components.
-
+
-The scripting support in ml.core.scripting defines basic services through which
-arbitrary script languages can be integrated by plygins. Script language plugins 
-The user interface core contains the implementation of the main window
-of Moonlight|3D together with its layout and view management mechanisms.
-
+
-The so-called "views" are screen areas defined by sashes, which
-are oocupied by plugin-provided classes. They can be arranged into any
-given user-specified layout, which is usually loaded from an XML file.
-
+
-User interface plugins provide all views in Moonlight|3D. For that they 
-have to register a factory with 
-of such an algorithm is a node which moves mesh vertices or adds faces to
-a mesh.
-
+
-Operator graph nodes expose their parameters through properties, which are
-named and typed. The plane creator OG node for example has two properties,