State |
Draft |
Date |
2008-03-06 |
Proposed by |
Ichthyostega |
-
the Application has three Layers: Backend, Proc and GUI
-
the Application shall be completely functional without GUI (script-driven)
-
all IO, media data fetching, processing and bookkeeping falls within the realm of the Backend
-
all media object manipulation, deciding and configuration is the Proc Layer’s job
-
extendible by plugins on all levels, highly configurable, but not totally componentized (micro kernel) architecture
-
strong separation between high-level and low-level areas of the Application -the user/GUI manipulates a high-level model wheras rendering is based on a corresponding low-level model -stored Session (state) is comprised of hig-level model, a collection of Assets and accompaning configuration
-
(possibly) several storage backends, abstracted out by a common interface
Tasks:
-
fill in the parts regarding the GUI
-
more details on the Backend? (cehteh?)
Discussion
This proposal intends to capture our current architectural view. Feel free to comment, augment and propose…
ask Ichthyo if interested in the SVG source of the drawing
Historical note
This early draft of the Architecture RfC was published on Cehteh’s Wiki in 2008;
it has been preserved as a HTML capture from pipapo.org at 2008-03-06.
I’m re-publishing this text as historic document, only transcribed into Asciidoc markup.
→ See the reworked and accepted version.
- Ichthyo
-
2025-09-13
|
The HTML capture shows a drawing, which was generated from Lumi.Architecture-1.svg |
This graphic was first added to Git in May 2008, and looks similar, yet notably different than the later iterations of this graphic
