PlexyDesk - Display Server for GNU/Linux - Recent changes [en-gb]

News

Sirajrazick — Wed, 01 Apr 2026 08:36:56 GMT

HDR and Dolby Vision Support

← Older revision		Revision as of 08:36, 1 April 2026
Line 4:		Line 4:
	With a compatible display, PlexyDesk delivers richer colours, deeper contrast, and a more immersive visual experience than ever before.		With a compatible display, PlexyDesk delivers richer colours, deeper contrast, and a more immersive visual experience than ever before.
	<div class="pp-frontpage__hero">		<div class="pp-frontpage__hero">
	[[File:~~hrd~~.png\|alt=PlexyDesk ~~Dark theme on~~ Arch Linux\|900px\|none]]		[[File:Screenshot_2026-04-01_09-37-45.png\|alt=PlexyDesk HDR / Dolby Vision Arch Linux\|900px\|none]]
	<div class="pp-frontpage__hero-caption"></div>		<div class="pp-frontpage__hero-caption"></div>
	</div>		</div>

File:Screenshot 2026-04-01 09-37-45.png

Sirajrazick — Wed, 01 Apr 2026 08:35:49 GMT

Sirajrazick uploaded File:Screenshot 2026-04-01 09-37-45.png dolby hdr screenshot

New page

== Summary ==
dolby hdr screenshot

News

Sirajrazick — Wed, 01 Apr 2026 08:33:50 GMT

HDR and Dolby Vision Support

← Older revision		Revision as of 08:33, 1 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
			== HDR and Dolby Vision Support ==

			We are happy to announce '''HDR''' and '''Dolby Vision''' support in '''PlexyDesk'''.
			With a compatible display, PlexyDesk delivers richer colours, deeper contrast, and a more immersive visual experience than ever before.
			<div class="pp-frontpage__hero">
			[[File:hrd.png\|alt=PlexyDesk Dark theme on Arch Linux\|900px\|none]]
			<div class="pp-frontpage__hero-caption"></div>
			</div>


	=== Improved Dark theme ===		=== Improved Dark theme ===

User:Davidbog

Davidbog — Sat, 28 Mar 2026 16:10:47 GMT

User account Davidbog was created

User:Wlfieqopzg

Wlfieqopzg — Thu, 26 Mar 2026 22:57:01 GMT

User account Wlfieqopzg was created

User:Puumxlpfru

Puumxlpfru — Thu, 26 Mar 2026 22:57:00 GMT

User account Puumxlpfru was created

Main Page

Sirajrazick — Tue, 24 Mar 2026 20:18:44 GMT

← Older revision		Revision as of 20:18, 24 March 2026
(3 intermediate revisions by the same user not shown)
Line 14:		Line 14:
	</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>		<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>

			PlexyDesk is available to anyone, anywhere in the world, without restrictions. We do not block access based on location, and we do not track the people who use it. Our goal is simple: make PlexyDesk openly available to every earthling, no matter where they are.

			</div>



	<div class="pp-frontpage__story pp-frontpage__story--wide">		<div class="pp-frontpage__story pp-frontpage__story--wide">

News

Sirajrazick — Tue, 24 Mar 2026 20:00:08 GMT

← Older revision		Revision as of 20:00, 24 March 2026
(5 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	= ~~News~~ =		=== Improved Dark theme ===

	~~'''News'''~~
	~~Keep track of daily updates of plexydesk development, news and important updates~~

	~~'''~~Improved Dark theme~~'''~~

	~~we improved dark mode for plexydesk, with support for options to fine tune each compositor properties. here is a screenshot~~

			We have improved dark mode in PlexyDesk to make it feel more polished and easier to adjust. The compositor now includes more options for fine tuning individual visual properties, giving users more control over how the desktop looks and behaves. The result is a dark theme that feels cleaner, more consistent, and more flexible than before.

			<div class="pp-frontpage__hero">
			[[File:Arch linux Dark theme.png\|alt=PlexyDesk Dark theme on Arch Linux\|900px\|none]]
			<div class="pp-frontpage__hero-caption"></div>
			</div>

	== Changelog ==		== Changelog ==

File:Arch linux Dark theme.png

Sirajrazick — Tue, 24 Mar 2026 19:47:56 GMT

Sirajrazick uploaded File:Arch linux Dark theme.png

New page

Improved Dark theme for PlexyDesk

News

Sirajrazick — Tue, 24 Mar 2026 19:46:31 GMT

News

@@ Line 1: / Line 1: @@
 = News =
-'''News''' records high-level project changes that affect how PlexyDesk is understood, evaluated, or documented. It should summarize milestones, visible feature additions, and major documentation changes in concise technical terms.
+'''News'''
 == Current status summary ==
@@ Line 15: / Line 29: @@
 * [[Gallery]] for visual captures of running PlexyDesk sessions
 * [[PlexyUI API]] for source-backed toolkit reference

Community

Sirajrazick — Tue, 24 Mar 2026 17:52:51 GMT

← Older revision		Revision as of 17:52, 24 March 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	= Community =		= Community =

	~~'''Community''' describes how~~ contributors ~~can use~~ this wiki as a shared ~~technical~~ record ~~for~~ PlexyDesk.		This is where contributors help turn this wiki into a clear, shared record of how PlexyDesk works.

	== ~~Contribution paths~~ ==		The goal is simple: keep the documentation close to the real system. That includes the code, the runtime behaviour, the visible desktop, and the interfaces exposed to applications and tools. The wiki should be useful both to people actively working on PlexyDesk and to readers who are trying to understand it from the outside.
	* improve architecture, component, and API ~~reference~~ pages ~~when~~ behaviour becomes clearer
	* add diagrams, screenshots, and short demo media that ~~document actual~~ runtime ~~behaviour~~		== How people can contribute ==
	* ~~correct~~ source-oriented pages when code structure or exposed interfaces change		There are many useful ways to contribute:
	* use article talk pages to ~~discuss wording,~~ missing details, or technical ~~accuracy~~		* improve architecture, component, and API pages as behaviour becomes clearer
			* add diagrams, screenshots, and short demo media that show how PlexyDesk behaves at runtime
			* update source-oriented pages when code structure or exposed interfaces change
			* use article talk pages to point out missing details, unclear wording, or technical mistakes
			* help connect related pages so the documentation is easier to follow

			Not every contribution needs to be large. Small fixes, clearer wording, better screenshots, and accurate cross links / refs all make the wiki more useful over time.

	== Media contributions ==		== Media contributions ==
	* [[Gallery]] is the ~~public~~ index for screenshots and short demo captures		Visual material is an important part of documenting PlexyDesk. Screenshots, diagrams, and short demo captures can often explain behavior more quickly than text alone.

			Useful pages:
			* [[Gallery]] is the main index for screenshots and short demo captures
	* [[Desktop Submissions]] explains how to prepare, upload, and list desktop screenshots		* [[Desktop Submissions]] explains how to prepare, upload, and list desktop screenshots
	* [[Special:Upload]] is the upload ~~entry point~~ for image and video files		* [[Special:Upload]] is the upload page for image and video files

			When uploading media, it helps to:
			* choose filenames that describe what the media shows
			* write short captions that explain the behavior or feature being documented
			* prefer real runtime captures over promotional material
			* include version, hardware, or environment details when they are relevant

	== Useful pages ==		== Useful pages ==
			A few pages are especially helpful when navigating the wiki:
	* [[Documentation]] for the main documentation map		* [[Documentation]] for the main documentation map
	* [[Special:RecentChanges]] for a live view of current edits		* [[Special:RecentChanges]] for a live view of current edits
Line 20:		Line 36:
	* [[News]] for milestone summaries and documentation updates		* [[News]] for milestone summaries and documentation updates

	== ~~Content~~ conventions ==		== Writing style and content conventions ==
	Pages should use technical language, avoid marketing claims, ~~and~~ stay ~~close~~ to ~~what the codebase~~ and ~~runtime actually support.~~ Captions, summaries, and page text should explain ~~behaviour precisely enough~~ to be ~~useful~~ to ~~both contributors~~ and ~~readers~~.		This wiki should stay practical and technically grounded.

			Pages should:
			* use clear technical language
			* avoid marketing claims
			* describe behavior that is implemented, observable, or directly supported by the codebase
			* clearly mark planned or experimental ideas instead of presenting them as finished behavior
			* stay specific enough to be useful to both contributors and readers

			Captions, summaries, and page text should explain things as plainly and accurately as possible. A good page does not just name a feature; it helps the reader understand what it does, where it fits, and how it behaves.

			== Talk pages and discussion ==
			Talk pages are there to make pages better. They can be used to:
			* question wording that feels unclear or misleading
			* point out missing information
			* discuss technical accuracy
			* suggest better structure or linking

			As PlexyDesk evolves, the wiki should evolve with it. Keeping pages current is part of the work, and even small updates help preserve a useful technical record.

			[[Category:Communication]]
			[[Category:Documentation]]

Main Page

Sirajrazick — Mon, 23 Mar 2026 08:53:29 GMT

← Older revision		Revision as of 08:53, 23 March 2026
Line 10:		Line 10:

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

File:Screenshot 2026-03-21 20-33-27.png

Sirajrazick — Sun, 22 Mar 2026 19:54:27 GMT

Sirajrazick uploaded File:Screenshot 2026-03-21 20-33-27.png

New page

Documentation

Sirajrazick — Sun, 22 Mar 2026 16:53:44 GMT

← Older revision		Revision as of 16:53, 22 March 2026
Line 1:		Line 1:
	= Documentation =		= Documentation =

	'''Documentation''' ~~is the top-level index for~~ PlexyDesk technical material~~. It~~ links to the pages that describe runtime architecture, subsystem boundaries, source layout, public APIs, and reference media.		'''Documentation''' contains PlexyDesk technical material, links to the pages that describe runtime architecture, subsystem boundaries, source layout, public APIs, and reference media.

	== System documentation ==		== System documentation ==

Main Page

Sirajrazick — Sun, 22 Mar 2026 09:03:24 GMT

← Older revision		Revision as of 09:03, 22 March 2026
(One intermediate revision by the same user not shown)
Line 7:		Line 7:
	<div class="pp-frontpage__label">System overview</div>		<div class="pp-frontpage__label">System overview</div>

	== PlexyDesk ~~technical documentation~~ ==		== What is PlexyDesk ==

	<div class="pp-frontpage__hero">		<div class="pp-frontpage__hero">
	[[File:Screenshot 2026-03-03 10-32-43.png\|alt=shows plexydesk in use\|900px\|none]]		[[File:Screenshot 2026-03-03 10-32-43.png\|alt=shows plexydesk in use\|900px\|none]]
	<div class="pp-frontpage__hero-caption">~~PlexyDesk screenshot~~</div>		<div class="pp-frontpage__hero-caption"></div>
	</div>		</div>

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

	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.
	</div>

	<div class="pp-frontpage__story pp-frontpage__story--wide">		<div class="pp-frontpage__story pp-frontpage__story--wide">

Main Page

Plexydesk — Sun, 22 Mar 2026 06:11:21 GMT

Replace hero figcaption with full-width caption block

← Older revision		Revision as of 06:11, 22 March 2026
Line 9:		Line 9:
	== PlexyDesk technical documentation ==		== PlexyDesk technical documentation ==

	<div class="pp-frontpage__hero~~" style="align: left !important~~">		<div class="pp-frontpage__hero">
	[[File:Screenshot 2026-03-03 10-32-43.png\|alt=shows plexydesk in use\|900px\|none~~\|thumb\|~~PlexyDesk screenshot]]		[[File:Screenshot 2026-03-03 10-32-43.png\|alt=shows plexydesk in use\|900px\|none]]
			<div class="pp-frontpage__hero-caption">PlexyDesk screenshot</div>
	</div>		</div>

Main Page

Sirajrazick — Sun, 22 Mar 2026 05:58:44 GMT

← Older revision		Revision as of 05:58, 22 March 2026
Line 9:		Line 9:
	== PlexyDesk technical documentation ==		== PlexyDesk technical documentation ==

	<div class="pp-frontpage__hero">		<div class="pp-frontpage__hero" style="align: left !important">
	[[File:Screenshot 2026-03-03 10-32-43.png\|alt=shows plexydesk in use\|900px\|none\|thumb\|PlexyDesk screenshot]]		[[File:Screenshot 2026-03-03 10-32-43.png\|alt=shows plexydesk in use\|900px\|none\|thumb\|PlexyDesk screenshot]]
	</div>		</div>

Main Page

Plexydesk — Sun, 22 Mar 2026 05:15:38 GMT

Render front-page screenshot as an inline lead image

← Older revision		Revision as of 05:15, 22 March 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	__NOEDITSECTION__		__NOEDITSECTION__
	<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]]
			<div class="pp-frontpage__hero">
			[[File:Screenshot 2026-03-03 10-32-43.png\|alt=shows plexydesk in use\|900px\|none\|thumb\|PlexyDesk screenshot]]
			</div>

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

Main Page

Sirajrazick — Sun, 22 Mar 2026 05:10:40 GMT

← Older revision		Revision as of 05:10, 22 March 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	__NOEDITSECTION__		__NOEDITSECTION__
			<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>

File:Screenshot 2026-03-03 10-26-49.png

Sirajrazick — Sun, 22 Mar 2026 05:07:32 GMT

Sirajrazick uploaded File:Screenshot 2026-03-03 10-26-49.png PlexyDesk File Manager

New page

== Summary ==
PlexyDesk File Manager

Main Page

Plexydesk — Sun, 22 Mar 2026 04:53:49 GMT

Add gallery and submission links to main page

← Older revision		Revision as of 04:53, 22 March 2026
Line 29:		Line 29:
	<li>'''[[Components]]''' - subsystem survey and source tree structure.</li>		<li>'''[[Components]]''' - subsystem survey and source tree structure.</li>
	<li>'''[[News]]''' - project chronicle and milestone summaries.</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>		<li>'''[[Community]]''' - contribution and wiki participation guidance.</li>
	</ul>		</ul>
Line 41:		Line 42:
	<li>'''[[Development Status]]''' - current implementation notes and subsystem coverage.</li>		<li>'''[[Development Status]]''' - current implementation notes and subsystem coverage.</li>
	<li>'''[[Getting Started]]''' - local runtime and setup notes.</li>		<li>'''[[Getting Started]]''' - local runtime and setup notes.</li>
			<li>'''[[Desktop Submissions]]''' - public procedure for uploading screenshots and listing desktops.</li>
	</ul>		</ul>
	</div>		</div>
Line 94:		Line 96:
	<li>[[Special:RecentChanges]] shows the latest documentation edits.</li>		<li>[[Special:RecentChanges]] shows the latest documentation edits.</li>
	<li>[[Special:Upload]] accepts images and video for diagrams, screenshots, and demonstrations.</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>		<li>Talk pages remain available for technical discussion and page review.</li>
	</ul>		</ul>

Desktop Submissions

Plexydesk — Sun, 22 Mar 2026 04:53:48 GMT

Add public desktop submission guide

New page

= Desktop Submissions =

'''Desktop Submissions''' explains how public contributors can add screenshots or short demo captures of PlexyDesk to the wiki gallery.

== 1. Sign in ==
Create or sign in to a wiki account before uploading files or editing gallery pages.

== 2. Capture the desktop ==
Prepare a screenshot or short video that clearly shows PlexyDesk in use.

Preferred media:
* PNG or JPEG for still images
* WebM or MP4 for short demo captures

Before uploading, remove private data such as personal files, tokens, chat windows, or unrelated desktop content.

== 3. Upload the file ==
Open [[Special:Upload]] and provide:
* the media file
* a clear filename, preferably in a form such as <code>PlexyDesk-username-topic.png</code>
* a summary describing what the capture shows

If the file represents a specific branch, build, or experiment, include that in the upload summary.

== 4. Add the file to [[Gallery]] ==
After the upload finishes, edit [[Gallery]] and add one line inside the <code><gallery></code> block:

<pre>
File:PlexyDesk-username-topic.png|Short technical caption — branch or build; scale factor; visible shell components
</pre>

== 5. Write a useful caption ==
A good caption should include:
* branch, version, or build context when known
* what part of PlexyDesk is being shown
* whether the capture highlights shell layout, compositor behaviour, toolkit widgets, or an application
* any display-scale or multi-monitor detail that matters to interpretation

== Submission rules ==
* submit only media directly related to PlexyDesk
* use technical wording rather than promotional wording
* keep video clips short and focused on one visible behaviour
* do not upload copyrighted material you do not have the right to share
* do not upload media containing credentials, personal information, or unrelated private content

== Related pages ==
* [[Gallery]]
* [[Special:Upload]]
* [[Community]]

Gallery

Plexydesk — Sun, 22 Mar 2026 04:53:47 GMT

Add screenshot gallery page

New page

= Gallery =

'''Gallery''' indexes screenshots and short demo captures of PlexyDesk sessions. Use it to document compositor behaviour, shell layout, visual changes, and application integration with the desktop.

== Scope ==
This page is intended for:
* full desktop screenshots
* focused captures of the dock, menubar, windows, or toolkit behaviour
* short demo videos that show visible runtime behaviour

== Community submissions ==
No desktop captures have been listed yet.

After uploading media through [[Special:Upload]], add it to the gallery block below by following [[Desktop Submissions]].

<gallery mode="packed" heights="220">

</gallery>

== Caption guidance ==
Each gallery entry should describe:
* the branch, build, or relevant code state if known
* the visible shell or toolkit features shown in the capture
* display scale, monitor layout, or theme details when they matter
* the specific behaviour the screenshot or video is meant to document

== Related pages ==
* [[Desktop Submissions]]
* [[Special:Upload]]
* [[Community]]

Community

Plexydesk — Sun, 22 Mar 2026 04:53:47 GMT

Rewrite community hub in technical style

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

	'''Community''' describes how ~~people~~ can use this wiki as a shared ~~editorial and~~ technical record for PlexyDesk.		'''Community''' describes how contributors can use this wiki as a shared technical record for PlexyDesk.

	== ~~Ways to contribute~~ ==		== Contribution paths ==
	* improve ~~explanatory~~ pages when ~~architecture or~~ behaviour becomes clearer		* improve architecture, component, and API reference pages when behaviour becomes clearer
	* ~~upload screenshots,~~ diagrams, ~~icons~~, and short ~~videos~~ that ~~help explain the desktop~~		* add diagrams, screenshots, and short demo media that document actual runtime behaviour
	* use article talk pages to discuss wording, ~~structure~~, ~~and missing references~~		* correct source-oriented pages when code structure or exposed interfaces change
	* keep source-backed technical ~~pages aligned with the code and the generated API reference~~		* use article talk pages to discuss wording, missing details, or technical accuracy

	== ~~Useful places around the site~~ ==		== Media contributions ==
	* [[Special:Upload]] for ~~images~~ and video		* [[Gallery]] is the public index for screenshots and short demo captures
	* [[Special:RecentChanges]] for a live view of ~~ongoing~~ edits		* [[Desktop Submissions]] explains how to prepare, upload, and list desktop screenshots
			* [[Special:Upload]] is the upload entry point for image and video files

			== Useful pages ==
			* [[Documentation]] for the main documentation map
			* [[Special:RecentChanges]] for a live view of current edits
	* [[Special:AllPages]] for the full page index		* [[Special:AllPages]] for the full page index
	* [[Documentation]] for the main reading map		* [[News]] for milestone summaries and documentation updates
	* [[News]] for ~~the current project chronicle~~

	== ~~Editorial direction~~ ==		== Content conventions ==
	~~This wiki is meant to feel like a serious technical publication.~~ Pages should ~~explain the system clearly~~, avoid ~~inflated~~ claims, and stay close to what the ~~source tree~~ and runtime actually support. ~~The goal is a record that is readable~~ to ~~newcomers and still~~ useful to ~~engineers~~.		Pages should use technical language, avoid marketing claims, and stay close to what the codebase and runtime actually support. Captions, summaries, and page text should explain behaviour precisely enough to be useful to both contributors and readers.

News

Plexydesk — Sun, 22 Mar 2026 04:53:46 GMT

Rewrite news hub in technical style

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

	'''News''' is ~~the public chronicle for the PlexyDesk project~~. It ~~is less about marketing announcements and more about keeping a readable record of what the system already is~~, ~~what areas are actively being refined~~, and ~~where readers should look next~~.		'''News''' records high-level project changes that affect how PlexyDesk is understood, evaluated, or documented. It should summarize milestones, visible feature additions, and major documentation changes in concise technical terms.

	== Current ~~headlines~~ ==		== Current status summary ==
	* PlexyDesk ~~already presents~~ a functioning compositor shell with ~~its own~~ dock and menubar.		* PlexyDesk includes a functioning compositor shell with integrated dock and menubar components.
	* The ~~rendering path~~ supports ~~a visually rich desktop with~~ shell-owned presentation and ~~effects~~.		* The runtime supports shell-owned composition, visual presentation, and client-submitted surfaces.
	* ~~The project includes a native application~~ toolkit ~~so programs can look and behave like part of~~ the ~~same environment~~.		* Public toolkit headers are documented through the generated [[PlexyUI API]] reference.
	* ~~Documentation is being expanded into a permanent project publication~~, ~~with architecture notes~~, ~~component surveys~~, and ~~generated API reference~~ pages.		* The wiki now includes architectural, subsystem, example, gallery, and contribution pages intended to track the codebase.

	== ~~Where to follow the project~~ ==		== Tracking pages ==
	* [[Development Status]] for implementation notes and ~~current~~ subsystem coverage		* [[Development Status]] for implementation notes and subsystem coverage
	* [[Development]] for ~~the~~ engineering ~~hub~~		* [[Development]] for engineering-facing references
	* [[Special:RecentChanges]] for the latest edits ~~on this wiki~~		* [[Special:RecentChanges]] for the latest wiki edits
			* [[Gallery]] for visual captures of running PlexyDesk sessions
	* [[PlexyUI API]] for source-backed toolkit reference		* [[PlexyUI API]] for source-backed toolkit reference

	== ~~Why this page exists~~ ==		== Intended use ==
	~~The purpose of this~~ page ~~is to give PlexyDesk a chronicle that reads clearly to new visitors while staying grounded in the work already represented elsewhere in the wiki. As the publication grows, this page can carry~~ milestone summaries, ~~notable additions~~, and high-level ~~editorial notes~~.		This page should be used for milestone summaries, major visible changes, documentation expansions, and other high-level updates that are useful to readers who need a compact view of project progress.

Components

Plexydesk — Sun, 22 Mar 2026 04:53:45 GMT

Rewrite components hub in technical style

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

	'''Components''' ~~surveys~~ the major building blocks of PlexyDesk and the role each one plays in the ~~overall desktop~~.		'''Components''' maps the major building blocks of PlexyDesk and the role each one plays in the runtime.

	== System layers ==		== System layers ==
Line 19:		Line 19:
	\|}		\|}

	== Source tree ~~components~~ ==		== Source tree map ==
	=~~== Compositor and shell runtime ===~~		{\| class="wikitable"
	~~The runtime lives primarily under~~ <code>src/</code>~~. This is where~~ window presentation~~, rendering, shell behaviour~~, backend integration, and ~~input flow are managed.~~		\|-
			! Path
	~~=== Client libraries ===~~		! Component area
	~~The supporting libraries under~~ <code>lib/</code> ~~provide application~~-facing helpers ~~so client programs can participate in the~~ PlexyDesk ~~environment without duplicating shell responsibilities.~~		! Responsibility
			\|-
	~~=== Public interface headers ===~~		\| <code>src/</code>
	~~The public headers under~~ <code>include/plexy/</code> ~~define~~ the ~~interface~~ surface ~~exposed to clients. The most visible reference is [[PlexyUI API]].~~		\| Compositor and shell runtime
			\| Output composition, window presentation, backend integration, input routing, and shell-owned desktop behaviour
	~~=== Examples and applications ===~~		\|-
	~~The~~ <code>examples/</code> and <code>apps/</code> ~~directories show how~~ the ~~runtime~~ and ~~toolkit are exercised in practice~~, ~~from small UI samples to larger application experiments.~~		\| <code>lib/</code>
			\| Client support libraries
			\| Application-facing runtime helpers, event loop code, and support functionality used by PlexyDesk clients
			\|-
			\| <code>include/plexy/</code>
			\| Public headers
			\| Exposed interface definitions for client code, including the current PlexyUI surface
			\|-
			\| <code>examples/</code>
			\| Reference examples
			\| Small programs that demonstrate application patterns and toolkit usage
			\|-
			\| <code>apps/</code>
			\| Application experiments
			\| Larger programs used to exercise the desktop, shell integration, and UI stack
			\|-
			\| <code>tasks/</code>
			\| Engineering notes
			\| Design notes, implementation summaries, and optimisation work
			\|}

	== ~~Further reading~~ ==		== Related pages ==
	* [[Architecture]]		* [[Architecture]]
	* [[Developer Guide]]		* [[Developer Guide]]
	* [[~~Examples~~]]		* [[PlexyUI API]]
	* [[Development]]		* [[Development]]

Development

Plexydesk — Sun, 22 Mar 2026 04:53:45 GMT

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

Documentation

Plexydesk — Sun, 22 Mar 2026 04:53:44 GMT

Rewrite documentation hub in technical style

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

	'''Documentation''' is the ~~central~~ index for ~~the~~ PlexyDesk ~~publication~~. It ~~points~~ to the pages that ~~explain how the desktop is structured~~, ~~how the~~ source ~~tree is arranged~~, and ~~where the current API~~ reference ~~lives~~.		'''Documentation''' is the top-level index for PlexyDesk technical material. It links to the pages that describe runtime architecture, subsystem boundaries, source layout, public APIs, and reference media.

	== ~~Core reading~~ ==		== System documentation ==
	* [[Architecture]] - ~~a technical explanation of how the~~ compositor, shell, and ~~client stack fit together~~		* [[Architecture]] - compositor, shell, client-surface, and rendering model
	* [[Components]] - a survey ~~of the major subsystems~~ and ~~directories that make up the project~~		* [[Components]] - subsystem survey and source tree map
	* [[Developer Guide]] - ~~a guide to the main~~ source areas and implementation ~~landmarks~~		* [[Developer Guide]] - implementation landmarks and source orientation
			* [[Development]] - current engineering areas and working references
			* [[Development Status]] - implementation coverage and subsystem notes

	== ~~Practical references~~ ==		== API and reference material ==
	* [[PlexyUI API]] - generated reference ~~for~~ the current ~~PlexyUI surface~~		* [[PlexyUI API]] - generated reference derived from the current UI toolkit headers
	* [[Examples]] - ~~small~~ programs and UI ~~samples that show how PlexyDesk applications are assembled~~		* [[Examples]] - sample programs and UI usage patterns
	* [[Getting Started]] - ~~current environment~~ and setup notes ~~for running or exploring the project locally~~		* [[Getting Started]] - local runtime and setup notes

	== ~~Project record~~ ==		== Media and community resources ==
	* [[~~Development~~]] - ~~the working hub for engineering direction~~ and ~~subsystem notes~~		* [[Gallery]] - screenshots and short demo captures of PlexyDesk sessions
	* [[~~Development Status~~]] - ~~implementation coverage~~ and ~~current project shape~~		* [[Desktop Submissions]] - public procedure for uploading and listing desktop captures
	* [[~~News~~]] - ~~the project chronicle~~ and ~~headline summary~~		* [[Community]] - contribution workflow and content conventions
	* [[~~Community~~]] - ~~editorial, contribution,~~ and ~~wiki participation pointers~~		* [[News]] - milestone and documentation record

MediaWiki:Sidebar

Plexydesk — Sun, 22 Mar 2026 04:53:42 GMT

Add gallery and submission links to sidebar

← Older revision		Revision as of 04:53, 22 March 2026
Line 6:		Line 6:
	** Components\|Components		** Components\|Components
	** News\|News		** News\|News
			** Gallery\|Gallery
	** Community\|Community		** Community\|Community
	* plexydesk-nav		* plexydesk-nav
Line 13:		Line 14:
	** Development Status\|Development Status		** Development Status\|Development Status
	** Getting Started\|Getting Started		** Getting Started\|Getting Started
			** Desktop Submissions\|Desktop Submissions
	* wiki-tools		* wiki-tools
	** Special:RecentChanges\|Recent Changes		** Special:RecentChanges\|Recent Changes

Main Page

Plexydesk — Sun, 22 Mar 2026 04:46:12 GMT

Rework main page into technical section index

Show changes

Community

Plexydesk — Sat, 21 Mar 2026 21:36:33 GMT

Add community and editorial guidance page

New page

= Community =

'''Community''' describes how people can use this wiki as a shared editorial and technical record for PlexyDesk.

== Ways to contribute ==
* improve explanatory pages when architecture or behaviour becomes clearer
* upload screenshots, diagrams, icons, and short videos that help explain the desktop
* use article talk pages to discuss wording, structure, and missing references
* keep source-backed technical pages aligned with the code and the generated API reference

== Useful places around the site ==
* [[Special:Upload]] for images and video
* [[Special:RecentChanges]] for a live view of ongoing edits
* [[Special:AllPages]] for the full page index
* [[Documentation]] for the main reading map
* [[News]] for the current project chronicle

== Editorial direction ==
This wiki is meant to feel like a serious technical publication. Pages should explain the system clearly, avoid inflated claims, and stay close to what the source tree and runtime actually support. The goal is a record that is readable to newcomers and still useful to engineers.

News

Plexydesk — Sat, 21 Mar 2026 21:36:33 GMT

Add project chronicle page

New page

= News =

'''News''' is the public chronicle for the PlexyDesk project. It is less about marketing announcements and more about keeping a readable record of what the system already is, what areas are actively being refined, and where readers should look next.

== Current headlines ==
* PlexyDesk already presents a functioning compositor shell with its own dock and menubar.
* The rendering path supports a visually rich desktop with shell-owned presentation and effects.
* The project includes a native application toolkit so programs can look and behave like part of the same environment.
* Documentation is being expanded into a permanent project publication, with architecture notes, component surveys, and generated API reference pages.

== Where to follow the project ==
* [[Development Status]] for implementation notes and current subsystem coverage
* [[Development]] for the engineering hub
* [[Special:RecentChanges]] for the latest edits on this wiki
* [[PlexyUI API]] for source-backed toolkit reference

== Why this page exists ==
The purpose of this page is to give PlexyDesk a chronicle that reads clearly to new visitors while staying grounded in the work already represented elsewhere in the wiki. As the publication grows, this page can carry milestone summaries, notable additions, and high-level editorial notes.

Components

Plexydesk — Sat, 21 Mar 2026 21:36:32 GMT

Add component survey page

New page

= Components =

'''Components''' surveys the major building blocks of PlexyDesk and the role each one plays in the overall desktop.

== System layers ==
{| class="wikitable"
|-
! Layer
! Role in the desktop
|-
| Applications
| Create windows, controls, text, panels, lists, and other interface content
|-
| PlexyDesk client libraries
| Help applications describe UI, render it locally, and submit finished surfaces
|-
| PlexyDesk compositor and shell
| Combine application surfaces with shell elements such as the dock, menubar, wallpaper, chrome, and transitions
|}

== Source tree components ==
=== Compositor and shell runtime ===
The runtime lives primarily under <code>src/</code>. This is where window presentation, rendering, shell behaviour, backend integration, and input flow are managed.

=== Client libraries ===
The supporting libraries under <code>lib/</code> provide application-facing helpers so client programs can participate in the PlexyDesk environment without duplicating shell responsibilities.

=== Public interface headers ===
The public headers under <code>include/plexy/</code> define the interface surface exposed to clients. The most visible reference is [[PlexyUI API]].

=== Examples and applications ===
The <code>examples/</code> and <code>apps/</code> directories show how the runtime and toolkit are exercised in practice, from small UI samples to larger application experiments.

== Further reading ==
* [[Architecture]]
* [[Developer Guide]]
* [[Examples]]
* [[Development]]

MediaWiki:Wiki-tools

Plexydesk — Sat, 21 Mar 2026 21:36:32 GMT

Rename editorial site tools section

← Older revision		Revision as of 21:36, 21 March 2026
Line 1:		Line 1:
	~~Wiki~~ Tools		Site Tools

← Older revision		Revision as of 04:53, 22 March 2026
Line 6:		Line 6:
	** Components\|Components		** Components\|Components
	** News\|News		** News\|News
			** Gallery\|Gallery
	** Community\|Community		** Community\|Community
	* plexydesk-nav		* plexydesk-nav
Line 13:		Line 14:
	** Development Status\|Development Status		** Development Status\|Development Status
	** Getting Started\|Getting Started		** Getting Started\|Getting Started
			** Desktop Submissions\|Desktop Submissions
	* wiki-tools		* wiki-tools
	** Special:RecentChanges\|Recent Changes		** Special:RecentChanges\|Recent Changes