Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration of Colorgeneration #1100

Open
Pharmaracist opened this issue Feb 8, 2025 · 3 comments
Open

Migration of Colorgeneration #1100

Pharmaracist opened this issue Feb 8, 2025 · 3 comments
Labels
FEATURE Feature advice/request

Comments

@Pharmaracist
Copy link
Contributor

Pharmaracist commented Feb 8, 2025

since the whole dots depend on material you colors i find matugen more suitable for this espicially for the demanding feature requests of users since every one can easily use it and alot of gradience issues make the switch for matugen easier
i have implemented it for my self and used it in my dotfiles and i got pretty much the same results as the old generation mechanism
https://github.com/pharmaracist/dots-hyprland/
in addition to better transparency toggle and very faster switching in colormodes and prietty much everything

@clsty clsty added the FEATURE Feature advice/request label Feb 9, 2025
@clsty clsty changed the title [Feature] Migration of Colorgeneration Migration of Colorgeneration Feb 9, 2025
@Pharmaracist
Copy link
Contributor Author

i forked the current config and ill start making prs for this but it will need some minor changes regarding the script usage since we dont really need some custom made scripts

@Pharmaracist
Copy link
Contributor Author

so the current migration involve abandoning fuzzel for rofi which in my opinion better and inherit well with the current overall appearence i made the rofi config myself and here its shape

Image
and it supports transparent mode so ill attach this too also we will need to implement foot template for matugen (i really dont use foot so ill keep constant color scheme in the ags.scss template file)

@Pharmaracist
Copy link
Contributor Author

pushed + me and @sh1zicus made a gjs app to control the useroptions in gui way but the problem is we made the useroptions stores the default values in useroptions.default.json file and the main configin ~/.ags/config.json the app looks for the main config file and dynamically show options and writes them to the file so it will need to migrate the useroptions to json configuration which is better in my opinion and easier to configure tell me if u need sth like that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FEATURE Feature advice/request
Projects
None yet
Development

No branches or pull requests

2 participants