Create new section for architecture design docs
Signed-off-by: Ichthyostega <prg@ichthyostega.de>
This commit is contained in:
parent
5e4d3a3ca0
commit
90caeaee6c
3 changed files with 56 additions and 0 deletions
34
doc/design/architecture/ArchitectureSummary.txt
Normal file
34
doc/design/architecture/ArchitectureSummary.txt
Normal file
|
|
@ -0,0 +1,34 @@
|
|||
Lumiera Architecture: Executive Summary
|
||||
=======================================
|
||||
:Author: Hermann Voßeler
|
||||
:Email: <Ichthyostega@web.de>
|
||||
:Date: Sept 2010
|
||||
|
||||
.Three Layers
|
||||
Besides the (obvious) separation in GUI frontend and render engine, editing core and application logic
|
||||
are treated separately. Besides enforcing clearly defined interfaces, the ability for script driven
|
||||
``headless'' operation and extensibility by plug-ins are deeply rooted in the overall design.
|
||||
|
||||
.Strong Separation
|
||||
High-level and low-level realm remain cleanly separated, relying on a compiler-like translation mechanism.
|
||||
This way, each part can be optimised for its purpose. The GUI exposes a feature-rich session model close
|
||||
to the problem domain, while the engine operates on a performance optimised render nodes graph.
|
||||
|
||||
.Scheduling Micro Operations
|
||||
High performance calculations in the engine are organised as micro tasks to be scheduled,
|
||||
allowing for adaptation to current and future hardware, expected to operate increasingly parallelised.
|
||||
|
||||
.Intelligent IO
|
||||
The engine is backed by an sophisticated frame cache and self adjusting I/O manager for maximising throughput
|
||||
and bandwidth use.
|
||||
|
||||
.Stream Type System
|
||||
Instead of relying on a single media framework, data streams are abstracted and classified, allowing to
|
||||
handle most wiring, detection of possible connections and conversion automatically.
|
||||
|
||||
.Rules Based Configuration
|
||||
Rather than driven by hard wired default behaviour or tedious manual operation, control flow is guided by
|
||||
a set of rules shaped configuration, which scales better to large and complicated projects. Queries are
|
||||
issued at decision points, allowing to build up a work environment customised and tailored for the needs
|
||||
of specific projects.
|
||||
|
||||
13
doc/design/architecture/index.txt
Normal file
13
doc/design/architecture/index.txt
Normal file
|
|
@ -0,0 +1,13 @@
|
|||
Design Documents: Lumiera Architecture
|
||||
======================================
|
||||
|
||||
This section will feature some rather high-level considerations regarding
|
||||
the architecture of the application.
|
||||
|
||||
.Executive Summary
|
||||
See link:ArchitectureSummary.html[here] for a short summary of the core architecture
|
||||
ideas of the envisioned Lumiera Application.
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -1,6 +1,15 @@
|
|||
Lumiera Design Documents
|
||||
========================
|
||||
|
||||
// Menu : prepend child design/backend
|
||||
// Menu : prepend child engine
|
||||
// Menu : prepend child model
|
||||
// Menu : prepend child design/gui
|
||||
// Menu : prepend child architecture
|
||||
|
||||
// Menu : append child plugins
|
||||
// Menu : append child workflow
|
||||
|
||||
The goal of Lumiera is to provide a professional tool for video editing on
|
||||
GNU/Linux systems. The vision of the development team defines a modern design
|
||||
for the core of a Non-Linear Editing software. One of the key aspect of Lumiera
|
||||
|
|
|
|||
Loading…
Reference in a new issue