__NOTOC__
__NOEDITSECTION__

<div class="pp-frontpage">

<div class="pp-frontpage__lead">
<div class="pp-frontpage__label">System overview</div>

== What is PlexyDesk ==

<div class="pp-frontpage__hero">
[[File:Screenshot_2026-03-21_20-33-27.png|alt=shows plexydesk in use|900px|none]]
<div class="pp-frontpage__hero-caption"></div>
</div>

<p class="pp-frontpage__deck">PlexyDesk is a Linux display server, compositor, desktop shell, and application toolkit for GNU/Linux and BSD. The project provides you with a full rendering infrastructure to create your own desktop environment, and client-side UI libraries to create native applications required for your DE. We are excited to see what you will create, so just ping us on Discord or update this wiki to share your project</p></div>

<div class="pp-frontpage__story pp-frontpage__story--wide">
<div class="pp-frontpage__label">Section index</div>

== Main sections ==

<div class="pp-frontpage__section-grid">

<div>
=== Primary sections ===
<ul class="pp-frontpage__brief-list">
<li>'''[[Documentation]]''' - top-level map of architecture notes, references, examples, and project pages.</li>
<li>'''[[Architecture]]''' - compositor, shell, client, and rendering model.</li>
<li>'''[[Development]]''' - engineering focus areas and implementation-oriented documentation hubs.</li>
<li>'''[[Components]]''' - subsystem survey and source tree structure.</li>
<li>'''[[News]]''' - project chronicle and milestone summaries.</li>
<li>'''[[Gallery]]''' - screenshots and short demo captures of PlexyDesk sessions.</li>
<li>'''[[Community]]''' - contribution and wiki participation guidance.</li>
</ul>
</div>

<div>
=== Reference pages ===
<ul class="pp-frontpage__brief-list">
<li>'''[[Developer Guide]]''' - source orientation and implementation landmarks.</li>
<li>'''[[PlexyUI API]]''' - generated reference for the current UI toolkit headers.</li>
<li>'''[[Examples]]''' - sample programs and UI usage patterns.</li>
<li>'''[[Development Status]]''' - current implementation notes and subsystem coverage.</li>
<li>'''[[Getting Started]]''' - local runtime and setup notes.</li>
<li>'''[[Desktop Submissions]]''' - public procedure for uploading screenshots and listing desktops.</li>
</ul>
</div>

</div>
</div>

<div class="pp-frontpage__story">
<div class="pp-frontpage__label">What PlexyDesk is</div>

== System model ==

PlexyDesk combines several layers that are often documented separately: a compositor responsible for final output composition, a desktop shell responsible for system UI such as the dock and menubar, and client libraries that let applications render native interface surfaces.

Applications can render their own content and submit finished surfaces to the compositor. The shell composes those surfaces with desktop-owned elements, manages input routing, and applies the presentation rules that define the environment.
</div>

<div class="pp-frontpage__story">
<div class="pp-frontpage__label">Feature areas</div>

== Implemented feature areas ==

<ul class="pp-frontpage__brief-list">
<li>GPU-accelerated composition of windows and desktop surfaces.</li>
<li>Shell-owned dock, menubar, wallpaper, and window framing.</li>
<li>Window movement, resizing, focus handling, transitions, and presentation effects.</li>
<li>Client-side UI toolkit components exposed through PlexyUI and related libraries.</li>
<li>Theme, scale, wallpaper, and appearance configuration.</li>
<li>Multi-display layout and desktop-space positioning support.</li>
</ul>
</div>

<div class="pp-frontpage__story">
<div class="pp-frontpage__label">Technical entry points</div>

== Key references ==

<ul class="pp-frontpage__brief-list">
<li>Start with [[Architecture]] for the runtime model.</li>
<li>Use [[Components]] and [[Developer Guide]] for source orientation.</li>
<li>Use [[PlexyUI API]] for the current public UI interface surface.</li>
<li>Use [[Examples]] to inspect small application patterns.</li>
</ul>
</div>

<div class="pp-frontpage__story">
<div class="pp-frontpage__label">Wiki interaction</div>

== Using this wiki ==

<ul class="pp-frontpage__brief-list">
<li>[[Special:AllPages]] provides the complete page index.</li>
<li>[[Special:RecentChanges]] shows the latest documentation edits.</li>
<li>[[Special:Upload]] accepts images and video for diagrams, screenshots, and demonstrations.</li>
<li>[[Gallery]] collects submitted screenshots and short demo captures.</li>
<li>[[Desktop Submissions]] explains how public users can contribute desktops.</li>
<li>Talk pages remain available for technical discussion and page review.</li>
</ul>
</div>

<div class="pp-frontpage__story">
<div class="pp-frontpage__label">Current scope</div>

== Current documentation scope ==

The current wiki covers architecture, source structure, generated API reference, example programs, implementation status, and project record pages. It will continue to expand as more subsystem documentation is extracted directly from the codebase.
</div>

</div>

2026-03-21T19:43:46Z

Sirajrazick:

= Development Status =

PlexyDesk is an active engineering project. It already contains a working compositor shell, rendering pipeline, widget toolkit, and supporting examples, but it should still be treated as a development platform rather than a finished consumer desktop.

== Working areas ==
* compositor runtime and shell rendering
* dock and menubar
* widget toolkit and retained layout API
* example applications and experiments
* packaging and systemd helpers
* bridge and compatibility work around Wayland and X11

== Areas that still read as active work ==
* broader application compatibility
* input and clipboard edge cases
* bridge robustness and performance tuning
* memory, damage tracking, and async rendering refinement

== Useful engineering notes in the repository ==
The <code>tasks/</code> directory contains implementation notes and change summaries including:
* <code>ASYNC_RENDERING_COMPLETE.md</code>
* <code>DAMAGE_TRACKING_IMPLEMENTATION.md</code>
* <code>IMPLEMENTATION_COMPLETE.md</code>
* <code>VRAM_LEAK_ANALYSIS.md</code>
* <code>VRAM_LEAK_FIXES_APPLIED.md</code>
* <code>X11_FLUSH_FIX_SUMMARY.md</code>
* <code>WORLD_CLASS_OPTIMIZATION_STRATEGY.md</code>

== Suggested workflow for contributors ==
# Read [[Getting Started]]
# Build a debug tree
# Run and inspect the smallest examples
# Read [[Architecture]] and [[Developer Guide]]
# Use the task documents to understand current priorities before making larger changes

== Related pages ==
* [[Main Page]]
* [[Getting Started]]
* [[Architecture]]
* [[Developer Guide]]
* [[Examples]]