Plexydesk: Rewrite development hub in technical style

2026-03-22T04:53:45Z

Rewrite development hub in technical style

← Older revision		Revision as of 04:53, 22 March 2026
Line 1:		Line 1:
	= Development =		= Development =

	'''Development''' ~~collects~~ the engineering ~~view of~~ PlexyDesk~~: what~~ areas ~~are active~~, ~~where~~ the ~~important subsystems live~~, and ~~which~~ reference pages should be consulted ~~while the project evolves~~.		'''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 ==
	~~PlexyDesk development~~ is ~~focused~~ on making the compositor, shell, and toolkit ~~behave like~~ one ~~deliberate desktop environment~~. ~~That means work tends to concentrate on~~:		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 ~~window framing~~		* shell-owned desktop UI such as the dock, menubar, wallpaper, and chrome
	* renderer and ~~visual effect~~ consistency		* renderer behaviour, materials, and presentation consistency
	* growth and ~~clarification of the PlexyUI toolkit~~		* client toolkit growth and public API clarity
	* source-backed documentation that ~~stays close to~~ the ~~code~~		* source-backed documentation and examples that track the codebase closely

	== Source map ==		== Source map ==
Line 37:		Line 37:
	\|}		\|}

	== ~~Development~~ references ==		== Working references ==
	* [[~~Development Status~~]] for the ~~current implementation record~~		* [[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 ~~API reference~~		* [[PlexyUI API]] for the current toolkit interface surface
	* [[~~Architecture~~]] for ~~the system-level design picture~~		* [[Examples]] for small application patterns
	* [[~~News~~]] for ~~the public-facing chronicle of progress~~		* [[Development Status]] for implementation notes and current project state

Plexydesk: Add development hub page

2026-03-21T21:36:31Z

Add development hub page

New page

= Development =

'''Development''' collects the engineering view of PlexyDesk: what areas are active, where the important subsystems live, and which reference pages should be consulted while the project evolves.

== Current engineering themes ==
PlexyDesk development is focused on making the compositor, shell, and toolkit behave like one deliberate desktop environment. That means work tends to concentrate on:

* compositor and surface management behaviour
* shell-owned UI such as the dock, menubar, and window framing
* renderer and visual effect consistency
* growth and clarification of the PlexyUI toolkit
* source-backed documentation that stays close to the code

== 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
|}

== Development references ==
* [[Development Status]] for the current implementation record
* [[Developer Guide]] for a guided source-tree tour
* [[PlexyUI API]] for the toolkit API reference
* [[Architecture]] for the system-level design picture
* [[News]] for the public-facing chronicle of progress

Development - Revision history

Plexydesk: Rewrite development hub in technical style

Plexydesk: Add development hub page