Editing 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 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 ==
{| class="wikitable"
|-
! Area
! Why it matters
|-
| <code>src/</code>
| Core compositor, backend, renderer, protocol, input, and shell implementation
|-
| <code>lib/</code>
| Client-side support libraries and event loop code used by applications
|-
| <code>include/plexy/</code>
| Public API headers, including the current PlexyUI interface surface
|-
| <code>examples/</code>
| Small reference programs that demonstrate application patterns
|-
| <code>apps/</code>
| Application experiments that exercise the runtime and UI toolkit
|-
| <code>tasks/</code>
| Engineering notes, implementation summaries, and optimisation work
|}

== Working references ==
* [[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