8000 GitHub - hkupty/meadhall: The gathering place for all Wayland features
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

hkupty/meadhall

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Meadhall

Wayland desktop utilities daemon

Meadhall is a gathering place for multiple desktop utilities, such as the status bars, idle notifier, etc.

It is a daemon designed to centralize the communication with wayland and can be interfaced through the meadhallctl utility

Status

Pre-alpha

TODO

  • meadhall (Daemon/Main Process)
    • Unix Socket
    • Systemd Unit
    • YAML configuration support
      • Individual configuration for each $XDG_CURRENT_DEKSTOP
        • Merge desktop-based configuration onto default one (see mergo)
    • Wayland features
      • Idle Management
      • Status Bar
      • Lock Handler
      • Output Management
        • Power Management
        • Hot-plugging & Layout Management
      • Wallpaper
  • meadhallctl (CLI interface)
    • Unix Socket communication
    • Handle arguments
    • Auto complete
  • meadbarrel (worker processes)
    • Register itself on daemon process
    • Unix Socket

Envisioned architecture

Architecture diagram

The intended architecture for meadhall consists of a main daemon process with eventual auxiliary (child) processes (aptly named meadbarrel) To interface with meadhall, the user will be provided with a CLI utility named meadhallctl which will support creating one-offs or on-the-fly configurations. Nonetheless, the main interface for configuring meadhall will still be the configuration file.

By default, the configuration will be read from $XDG_CONFIG_HOME/meadhall/config.yaml, unless there's a $XDG_CONFIG_HOME/meadhall/$XDG_CURRENT_DEKSTOP.yaml file. In which case, both files will be merged, resulting in a configuration object that is the product of the content of both files.

Open Architecture Decisions

Wayland access

There are three alternatives:

  1. meadhall is the only process actually connected to Wayland
  2. meadhall manages a significant portion, but drawing onto the screen (i.e. status bars) is delegated to individual meadbarrel processes
  3. meadhall doesn't connect to Wayland at all; instead, each Wayland feature is managed by a specialized meadbarrel process

Past Architecture Decisions

This project uses Architectural Decision Records to keep track of the architecture evolution. Refer to doc/adr/ for the list of decisions

About

The gathering place for all Wayland features

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

0