Project Description

I've implemented drivers for a few e-ink displays during the last hackweek and made sure that gfxprim widgets run nicely on e-ink as well. The missing piece to have a portable e-ink computer/reader/music player/... is a application that can switch between currently running applications and that can start new applications as well. Half of the solution is ready, there is a proxy gfxprim backend where applications render into a piece of a shared memory and input events (e.g. keyboard, mouse) can be multiplexed. What is missing is an interface (possibly touchscreen friendly as well) to make it user friendly.

Goal for this Hackweek

Make nekowm usable "window manager".

Resources

Looking for hackers with the skills:

gui graphics e-ink ui

This project is part of:

Hack Week 24

Activity

  • 12 months ago: michals liked this project.
  • about 1 year ago: vliaskovitis liked this project.
  • about 1 year ago: metan added keyword "ui" to this project.
  • about 1 year ago: metan added keyword "gui" to this project.
  • about 1 year ago: metan added keyword "graphics" to this project.
  • about 1 year ago: metan added keyword "e-ink" to this project.
  • about 1 year ago: metan started this project.
  • about 1 year ago: metan originated this project.

  • Comments

    • metan
      11 months ago by metan | Reply

      And while it's far from finished I managed to design most of the functionality. A short animation shows what I managed to implement.

      And as usual rpm and deb packages are in buildservice

    Similar Projects

    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles: https://linux-system-roles.github.io/