Research how settings for users can be saved

a24timsv commented

2026-04-08 07:23:51 +00:00

Collaborator

The user should be able to save, load and edit its dashboard, as mentioned in #87. In order for this to work something needs to be saved as a settings or config file (or something else).

Parent issue: #65

The user should be able to save, load and edit its dashboard, as mentioned in #87. In order for this to work something needs to be saved as a settings or config file (or something else). Parent issue: #65

a24timsv added the

project documentation

backEnd

research

labels

2026-04-08 07:24:17 +00:00

b24johka commented

2026-04-08 09:53:01 +00:00

Collaborator

This has been assigned to Alexander L, but he hasnt got permissions yet.

e24aleli self-assigned this

2026-04-08 10:40:23 +00:00

e24aleli commented

2026-04-08 11:20:51 +00:00

Collaborator

idea of possible solution

Directory "config":

Collection of all possible settings the user can enable.

Palettes/ (dir with different styles such as purple,blue,green etc)
- green.css
- purple.css
Fonts? (Fonts for specific text "normal, mono, fancy, other languages etc..." )
Style (such as light/dark mode)
Globals? (General css, standard variables/properties.)

Settings (User conf obj.)

When the user changes the settings a "master" settings file should be generated (gets overwritten once created). This file should hold ONLY current settings to ensure the code knows that settings is in use.
ex:

userid: admin1
settings
- theme: dark
- palette: blue
- fontSize: "large"
- language: en

rough sketch:

## idea of possible solution - - - - ### Directory "config": Collection of all possible settings the user can enable. - Palettes/ (dir with different styles such as purple,blue,green etc) - green.css - purple.css - Fonts? (Fonts for specific text "normal, mono, fancy, other languages etc..." ) - Style (such as light/dark mode) - Globals? (General css, standard variables/properties.) ### Settings (User conf obj.) When the user changes the settings a "master" settings file should be generated (gets overwritten once created). This file should hold **ONLY** current settings to ensure the code knows that settings is in use. ex: - userid: admin1 - settings - theme: dark - palette: blue - fontSize: "large" - language: en rough sketch:

Screenshot 2026-04-08 131652.png

16 KiB

e24aleli added the

needs review

label

2026-04-08 11:50:15 +00:00

a24timsv commented

2026-04-08 11:58:29 +00:00

Author

Collaborator

I'm guessing then that the config file would be saved on a server (our server) so that the settings are saved regardless of device?

e24aleli commented

2026-04-08 12:01:41 +00:00

Collaborator

Yes, perhaps it could be saved on our server in a file like "user_123.json" and on login it fetches that specific users settings file..

a24vinla referenced this issue

2026-04-09 09:21:36 +00:00

Research if and how we can export react grid layout matrix #200

b24johka commented

2026-04-09 09:47:11 +00:00

Collaborator

The model is quite hard to interpret, could we perhaps make it a little less rough?

b24johka removed the

needs review

label

2026-04-09 09:47:28 +00:00

e24aleli added reference #173-Save-User-Settings

2026-04-09 12:52:06 +00:00

e24aleli commented

2026-04-09 14:12:21 +00:00

Collaborator

Visualization of my thought process how user settings can be saved with postgresql to ensure that the settings persists regardless of device.

When the user changes the appearance they have to name their custom layout preset which gets saved in the database. There should always be a default layout incase the user is new or they dont want to change anything. When fetching the layout the program should look for "preset" that the user has selected in their settings. The config directory should contain every option and also store the UUID to make it possible to fetch that users specific preset. The JSON or the "master config" should only contain the selected options. This file is the preset that gets applied to the interface.

This is how i believe the user settings can be saved.

Furthermore, to make the settings apply on startup perhaps we can implement some cache that stores what preset a user last had enabled.

Draw.io link:
https://drive.google.com/file/d/1xln_3-kEF8bilJRZD2FJS6nRwMfbmPyT/view?usp=sharing

Another way of showing the flow is my quickshell i worked on a while ago which has an identical structure (except that its locally saved)
https://github.com/Liligirthlord/numbshell/tree/main/quickshell/Config

Visualization of my thought process how user settings can be saved with postgresql to ensure that the settings persists regardless of device. When the user changes the appearance they have to name their custom layout preset which gets saved in the database. There should always be a default layout incase the user is new or they dont want to change anything. When fetching the layout the program should look for "preset" that the user has selected in their settings. The config directory should contain every option and also store the UUID to make it possible to fetch that users specific preset. The JSON or the "master config" should only contain the selected options. This file is the preset that gets applied to the interface. This is how i believe the user settings can be saved. - - - Furthermore, to make the settings apply on startup perhaps we can implement some cache that stores what preset a user last had enabled. **Draw.io link:** https://drive.google.com/file/d/1xln_3-kEF8bilJRZD2FJS6nRwMfbmPyT/view?usp=sharing - - - Another way of showing the flow is my quickshell i worked on a while ago which has an identical structure (except that its locally saved) https://github.com/Liligirthlord/numbshell/tree/main/quickshell/Config

Screenshot 2026-04-09 160248.png

50 KiB

e24aleli added the

needs review

label

2026-04-09 14:12:35 +00:00

a24vinla referenced this issue

2026-04-10 07:24:57 +00:00

Card layout config #217

b24johka commented

2026-04-10 07:58:10 +00:00

Collaborator

a24vinla has been assigned as reviewer.

a24vinla commented

2026-04-10 08:17:29 +00:00

Collaborator

Model looks really good!

I have some questions regarding the config directory. Is it a separate database or a directory on a local server? Since the saved data will be minimal, is there a major upside to storing the actual layout data separately? My idea was to store it all in the same DB, with layouts being their own tables.

Model looks really good! I have some questions regarding the config directory. Is it a separate database or a directory on a local server? Since the saved data will be minimal, is there a major upside to storing the actual layout data separately? My idea was to store it all in the same DB, with layouts being their own tables.

a24vinla commented

2026-04-10 08:20:16 +00:00

Collaborator

Obviously user information would be stored separately, with some type of UID being used to reference users once logged in.

e24aleli commented

2026-04-10 08:31:30 +00:00

Collaborator

This was the one thing I was unsure about. When I made the model I was thinking of a directory on a local server I just didn't know how to draw it clearly. But I dont know how it work out in practice.

As for the question regarding the layout storing, yes that was my idea too to store the config directory with its sub directories on the same db my apologies for confusion in the model.

This was the one thing I was unsure about. When I made the model I was thinking of a directory on a local server I just didn't know how to draw it clearly. But I dont know how it work out in practice. As for the question regarding the layout storing, yes that was my idea too to store the config directory with its sub directories on the same db my apologies for confusion in the model.