Development: Difference between revisions
Add development hub page |
Rewrite development hub in technical style |
||
| Line 1: | Line 1: | ||
= Development = | = Development = | ||
'''Development''' | '''Development''' indexes the engineering-facing material for PlexyDesk. Use this page to identify active work areas, the source directories that implement them, and the reference pages that should be consulted during development. | ||
== Current engineering themes == | == Current engineering themes == | ||
Current work is centred on making the compositor, shell, and client toolkit operate as one coherent runtime. The main areas are: | |||
* compositor and surface management behaviour | * compositor and surface management behaviour | ||
* shell-owned UI such as the dock, menubar, and | * shell-owned desktop UI such as the dock, menubar, wallpaper, and chrome | ||
* renderer and | * renderer behaviour, materials, and presentation consistency | ||
* growth and | * client toolkit growth and public API clarity | ||
* source-backed documentation that | * source-backed documentation and examples that track the codebase closely | ||
== Source map == | == Source map == | ||
| Line 37: | Line 37: | ||
|} | |} | ||
== | == Working references == | ||
* [[ | * [[Architecture]] for the runtime model and subsystem responsibilities | ||
* [[Developer Guide]] for a guided source-tree tour | * [[Developer Guide]] for a guided source-tree tour | ||
* [[PlexyUI API]] for the toolkit | * [[PlexyUI API]] for the current toolkit interface surface | ||
* [[ | * [[Examples]] for small application patterns | ||
* [[ | * [[Development Status]] for implementation notes and current project state | ||
Latest revision as of 04:53, 22 March 2026
Development
[edit | edit source]Development indexes the engineering-facing material for PlexyDesk. Use this page to identify active work areas, the source directories that implement them, and the reference pages that should be consulted during development.
Current engineering themes
[edit | edit source]Current work is centred on making the compositor, shell, and client toolkit operate as one coherent runtime. The main areas are:
- compositor and surface management behaviour
- shell-owned desktop UI such as the dock, menubar, wallpaper, and chrome
- renderer behaviour, materials, and presentation consistency
- client toolkit growth and public API clarity
- source-backed documentation and examples that track the codebase closely
Source map
[edit | edit source]| Area | Why it matters |
|---|---|
src/
|
Core compositor, backend, renderer, protocol, input, and shell implementation |
lib/
|
Client-side support libraries and event loop code used by applications |
include/plexy/
|
Public API headers, including the current PlexyUI interface surface |
examples/
|
Small reference programs that demonstrate application patterns |
apps/
|
Application experiments that exercise the runtime and UI toolkit |
tasks/
|
Engineering notes, implementation summaries, and optimisation work |
Working references
[edit | edit source]- Architecture for the runtime model and subsystem responsibilities
- Developer Guide for a guided source-tree tour
- PlexyUI API for the current toolkit interface surface
- Examples for small application patterns
- Development Status for implementation notes and current project state
This page has not yet been filed in a published category.