Development Status: Difference between revisions

Add development status page
 
mNo edit summary
Line 3: Line 3:
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.
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 already visible in the tree ==
== Working areas ==
* compositor runtime and shell rendering
* compositor runtime and shell rendering
* dock and menubar
* dock and menubar

Revision as of 19:43, 21 March 2026

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 tasks/ directory contains implementation notes and change summaries including:

  • ASYNC_RENDERING_COMPLETE.md
  • DAMAGE_TRACKING_IMPLEMENTATION.md
  • IMPLEMENTATION_COMPLETE.md
  • VRAM_LEAK_ANALYSIS.md
  • VRAM_LEAK_FIXES_APPLIED.md
  • X11_FLUSH_FIX_SUMMARY.md
  • WORLD_CLASS_OPTIMIZATION_STRATEGY.md

Suggested workflow for contributors

  1. Read Getting Started
  2. Build a debug tree
  3. Run and inspect the smallest examples
  4. Read Architecture and Developer Guide
  5. Use the task documents to understand current priorities before making larger changes