# SchDE — the SchOS Desktop Environment

> **Superseded as a directory, not as an idea.** A panel, a launcher and a
> settings app are ordinary Wayland clients using `wlr-layer-shell`. This
> directory is to be deleted; they need no home of their own until one of them
> is written.
>
> See [`docs/plan/wayland.md`](../../docs/plan/wayland.md).

The parts you actually look at: a panel, a launcher, settings, a file
manager, a terminal.

SchDE is a set of ordinary Schcom clients plus whatever shared widget code
they end up needing. Nothing in it is privileged and nothing in it is
special — if SchDE can do something that a third-party program could not, the
line has been drawn in the wrong place.

## Status

Not started. Last of the three, and deliberately so: there is no point
designing a panel before there is a compositor to put it on.

## What it will need that does not exist yet

- **Text rendering.** Everything here is text, and the console's fixed 8×16
  CP437 grid is not usable for it. See `docs/plan/wayland.md` — a real
  glyph cache and rasteriser, and layout as a library in `lib/` so the
  terminal and the file manager are not each solving it.
- **A widget toolkit**, however small. Even a panel needs buttons, labels and
  hit testing.
- **A terminal emulator.** Note the direction: the *kernel* console parses
  ANSI today because it draws directly to the framebuffer. A GUI terminal is
  a client that parses ANSI itself and renders it with proportional-capable
  text. The two do not share code.