Main Page: Difference between revisions

mNo edit summary
No edit summary
Line 1: Line 1:
__NOTOC__
__NOTOC__
__NOEDITSECTION__
__NOEDITSECTION__
[[File:Screenshot 2026-03-03 10-32-43.png|alt=shows plexydesk in use|thumb|plexydesk  screenshot]]
<div class="pp-frontpage"><div class="pp-frontpage__lead">
<div class="pp-frontpage"><div class="pp-frontpage__lead">
<div class="pp-frontpage__label">System overview</div>
<div class="pp-frontpage__label">System overview</div>


== PlexyDesk technical documentation ==
== PlexyDesk technical documentation ==
[[File:Screenshot 2026-03-03 10-32-43.png|alt=shows plexydesk in use|thumb|plexydesk  screenshot]]


<p class="pp-frontpage__deck">PlexyDesk is a Linux display server, compositor, desktop shell, and application toolkit. The project combines surface composition, shell-owned desktop components, rendering infrastructure, and client-side UI libraries in one integrated system.</p>
<p class="pp-frontpage__deck">PlexyDesk is a Linux display server, compositor, desktop shell, and application toolkit. The project combines surface composition, shell-owned desktop components, rendering infrastructure, and client-side UI libraries in one integrated system.</p>

Revision as of 05:10, 22 March 2026


System overview

PlexyDesk technical documentation

shows plexydesk in use
plexydesk screenshot

PlexyDesk is a Linux display server, compositor, desktop shell, and application toolkit. The project combines surface composition, shell-owned desktop components, rendering infrastructure, and client-side UI libraries in one integrated system.

This wiki is the technical reference for PlexyDesk. It describes the compositor architecture, desktop shell behaviour, public toolkit APIs, source layout, and current implementation status. Use the section index below to navigate the main documentation areas.

Section index

Main sections

Primary sections

  • Documentation - top-level map of architecture notes, references, examples, and project pages.
  • Architecture - compositor, shell, client, and rendering model.
  • Development - engineering focus areas and implementation-oriented documentation hubs.
  • Components - subsystem survey and source tree structure.
  • News - project chronicle and milestone summaries.
  • Gallery - screenshots and short demo captures of PlexyDesk sessions.
  • Community - contribution and wiki participation guidance.

Reference pages

What PlexyDesk is

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.

Feature areas

Implemented feature areas

  • GPU-accelerated composition of windows and desktop surfaces.
  • Shell-owned dock, menubar, wallpaper, and window framing.
  • Window movement, resizing, focus handling, transitions, and presentation effects.
  • Client-side UI toolkit components exposed through PlexyUI and related libraries.
  • Theme, scale, wallpaper, and appearance configuration.
  • Multi-display layout and desktop-space positioning support.
Technical entry points

Key references

Wiki interaction

Using this wiki

  • Special:AllPages provides the complete page index.
  • Special:RecentChanges shows the latest documentation edits.
  • Special:Upload accepts images and video for diagrams, screenshots, and demonstrations.
  • Gallery collects submitted screenshots and short demo captures.
  • Desktop Submissions explains how public users can contribute desktops.
  • Talk pages remain available for technical discussion and page review.
Current scope

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.