Difference between revisions of "PineNote Development/TODOs"

From PINE64
Jump to navigation Jump to search
Tags: mobile web edit mobile edit
Line 1: Line 1:
These are a list of open questions that pertain to configurations necessary for the OS to function nicely in the short-term during development and in the long term for people. If you know the answer to one of these or want something to do, please make a page with this info and link it here :)
TODOs to get the pinenote to a user ready state. If you know the answer to one of these or want something to do, please make a page with this info and link it here :)


= Configuration TODOs =
= Userspace TODOs=
== Themes ==
A lot of getting the PineNote to work nicely will be theming things appropriately. Please list themes for various components here:
=== GNOME ===
https://github.com/fujimo-t/gnome-shell-theme-e-ink


== Work that will need to be done long-term ==
== GNOME Configurations ==
=== GNOME Configurations ===
See [https://wiki.pine64.org/wiki/PineNote_Development/Apps#Gnome here].
See [https://wiki.pine64.org/wiki/PineNote_Development/Apps#Gnome here].
=== Sway Configurations ===
== Sway Configurations ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Apps#Sway here].
See [https://wiki.pine64.org/wiki/PineNote_Development/Apps#Sway here].
=== Mouse/Touch ===
=== Mouse/Touch ===

Revision as of 06:29, 1 September 2022

TODOs to get the pinenote to a user ready state. If you know the answer to one of these or want something to do, please make a page with this info and link it here :)

Userspace TODOs

Themes

A lot of getting the PineNote to work nicely will be theming things appropriately. Please list themes for various components here:

GNOME

https://github.com/fujimo-t/gnome-shell-theme-e-ink

GNOME Configurations

See here.

Sway Configurations

See here.

Mouse/Touch

  1. How should pen work? How should finger work? Are there Linux tablets that already do this decently well?

Open questions that would be helpful during development

  1. How do we pin packages so Mesa isn't updated when we update using our package manger?

Documentation TODOs

Note: These are things we know how to do, but they just haven't been documented in the wiki yet. If you know how to do one of these things, please make a page for it. If you aren't sure where to put it or just don't feel like doing it, please just message @aarondabomb on matrix and I'll be happy to document it.

Pin Mesa Packages so they don't update when we upgrade other packages

Should be super simple, I just don't know how. If you know, it would be helpful for you to add that information near step 5 here.

Control the backlight?

Building alacritty correctly

Force a screen refresh?

Maximilian mentioned how to do this, but I don't know enough to know what it means XD see conversation here: https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$tfumBpnP2UPouNpaeFrggR40ZkrD_pHAtJdQmQvzL-o?via=matrix.org&via=kde.org&via=tchncs.de