You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2022. It is now read-only.
Implement a per-user theme chooser within the settings, that allows users to switch the theme that's being used on Paperwork only for them.
There should be a setting within /app/config/paperwork.php that allows disabling the theme selection and setting one specific theme as default for all users.
The theme chooser should simply scan the /public/css/themes/ folder and list all available themes. For this, the current structure needs to be slightly changed: Each theme needs its own directory within /public/css/themes (e.g. /public/css/themes/themeOne/, /public/css/themes/themeTwo/, etc.) that contains the theme CSS file and a theme-description file (e.g. theme.php). This file needs to include important information like the theme-css-filename, the theme name, a short description and the theme author.
The database table settings needs to be extended, so it can save the currently selected theme for each user individually. Also the layout files need to be extended, so the dynamically load the right theme according to what the user has selected (-> settings-table entry).
Thoughts?
How about the ckEditor, which - unfortunately - is being themed separately so far. Could that be included into the main theme css and also loaded dynamically?
The text was updated successfully, but these errors were encountered:
Implement a per-user theme chooser within the settings, that allows users to switch the theme that's being used on Paperwork only for them.
There should be a setting within
/app/config/paperwork.php
that allows disabling the theme selection and setting one specific theme as default for all users.The theme chooser should simply scan the
/public/css/themes/
folder and list all available themes. For this, the current structure needs to be slightly changed: Each theme needs its own directory within/public/css/themes
(e.g./public/css/themes/themeOne/
,/public/css/themes/themeTwo/
, etc.) that contains the theme CSS file and a theme-description file (e.g. theme.php). This file needs to include important information like the theme-css-filename, the theme name, a short description and the theme author.The database table
settings
needs to be extended, so it can save the currently selected theme for each user individually. Also the layout files need to be extended, so the dynamically load the right theme according to what the user has selected (->settings
-table entry).Thoughts?
How about the ckEditor, which - unfortunately - is being themed separately so far. Could that be included into the main theme css and also loaded dynamically?
The text was updated successfully, but these errors were encountered: