benn/lumiera_documentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
lumiera_documentation/doc/technical/index.txt

43 lines
1.6 KiB
Text
Raw Normal View History

Add a note about Python pretty printers in GDB
2011-01-07 18:03:26 +01:00
Technical Documentation
=======================
added the documentation overview pages from the new website-draft
2010-11-14 03:38:43 +01:00
add a section for library technical documentation
2012-01-08 00:12:54 +01:00
// Menu : prepend child library
Global-Layer-Renaming: rearrange directories backend -> vault proc -> steam gui -> stage
2018-11-15 23:28:03 +01:00
// Menu : prepend child vault
// Menu : prepend child steam
// Menu : prepend child stage
reordering overview pages in User and Technical documentation
2011-03-04 02:48:31 +01:00
// Menu : prepend child howto
// Menu : prepend child overview
added the documentation overview pages from the new website-draft
2010-11-14 03:38:43 +01:00
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
This documentation section contains technical documentation about Lumiera. +
To get an *overview* of all the internals and components, you might want to read
reordering overview pages in User and Technical documentation
2011-03-04 02:48:31 +01:00
link:overview.html[Lumiera the Inner Core]
Minor changes on doc index and technical doc index Intended to make pages more user friendly. Formatted pages structures and added text
2010-11-18 22:21:48 +01:00
Add a note about Python pretty printers in GDB
2011-01-07 18:03:26 +01:00
== Three Layers
doc: Several minor fixes and structural improvements.
2011-02-20 20:40:13 +01:00
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
The technical documentation is divided into three main parts and some supplements,
corresponding to the code organisation in three layers. The information here can be
very detailed and technical at times, and the topics are organised by individual components.
Minor changes on doc index and technical doc index Intended to make pages more user friendly. Formatted pages structures and added text
2010-11-18 22:21:48 +01:00
Global-Layer-Renaming: rearrange directories backend -> vault proc -> steam gui -> stage
2018-11-15 23:28:03 +01:00
* link:stage/index.html[*Stage Layer*] : Documents related to the GTK based Lumiera GUI
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
* link:steam/index.html[*Steam Layer*] : Documents regarding Session, the models and the engine
Global-Layer-Renaming: rearrange directories backend -> vault proc -> steam gui -> stage
2018-11-15 23:28:03 +01:00
* link:vault/index.html[*Vault Layer*] : Documents about the data and processing backend
Add a note about Python pretty printers in GDB
2011-01-07 18:03:26 +01:00
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
To better understand the underlying concepts, it might be helpful to also consult the
link:{ldoc}/design/index.html[Design Documents].
Add a note about Python pretty printers in GDB
2011-01-07 18:03:26 +01:00
== Tools
Minor changes on doc index and technical doc index Intended to make pages more user friendly. Formatted pages structures and added text
2010-11-18 22:21:48 +01:00
.Development
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
* link:/doxy/[*Doxygen*] : API documentation of the Lumiera code.
Add Debian packaging informations to the documentation
2011-10-14 03:36:36 +02:00
* organisation of the link:code/index.html[Code Base] in general
clean-up: link maintenance - use HTTPS - avoid redirects - supply Archive.org snapshots for old resources
2025-09-02 19:42:49 +02:00
* link:/x/CodingGuidelines.html[Coding Style] and further guidelines
Minor changes on doc index and technical doc index Intended to make pages more user friendly. Formatted pages structures and added text
2010-11-18 22:21:48 +01:00
.Building
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
* link:build/index.html[Buildsystem] : Installation and compilation tools, dependencies and packaging.
the_inner_core is considered rather a piece of technical documentation
2010-11-18 22:49:25 +01:00
Add a note about Python pretty printers in GDB
2011-01-07 18:03:26 +01:00
.HOWTO
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
* link:/x/DevHowto.html[Developer *HOWTOs*] : Collection of instructions, recipes, hints, misdeeds
and confessions and similar helpful resources for developers
Reference in a new issue Copy permalink