PineNote Development/TODOs

This page or section is under construction

Please help to review and edit this page or section. Information are subject to change.

Back to PineNote main page

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

Untested as far as I know: https://github.com/fujimo-t/gnome-shell-theme-e-ink

GTK

Todo

GNOME Configurations

See here.

Sway Configurations

See here.

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.

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