-
Notifications
You must be signed in to change notification settings - Fork 2
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
GUI #3
Comments
Flutter & Tauri are new shiny option these days, along with good old Qt/GTK. Some projects in Flutter to check out: Some tauri apps to check out: https://tauri.studio/en/showcase |
It actually sounds like the perfect excuse to learn Flutter haha. I guess I'll have to look into those later. Still, I think the priorities would be the following:
|
This would literally take me at least a year or two. lol |
@KarkanAlzwayed Hey, no pressure ^^ I just created the issue because I think it's something that'll probably be requested sooner or later. I thought pointers as to where to start would be good to have here, for anyone wanting to give it a go. |
I don't know what you did in your latest commit, but after my last |
I have a question, does this conflict with TLP and cpu-autofreq? I am running Manjaro, and it has both installed out of the box. Should I remove them, or with powerplan play well with them? |
Nice, I use Manjaro as well! I actually started developing this because neither did it completely for my needs (among other tools there), but currently I use TLP (without it's Processor options) alongside powerplan without issues. As for auto-cpufreq, I think having it installed would be a bit redundant, and I would advice uninstalling it (since it supports less of a similar set of features). Before writing this program I actually submitted some code there, but for design reasons I grew disenchanted with the project. Auto-cpufreq's objective is a noble one, but as it is, it's not easy to develop on top and it's very prone to stuff breaking in my experience, and frankly speaking, it's delivery of "optimization" is very questionable. All that said, If you ever get in a situation where X tool overrides powerplan's config at times (and you can't or rather not change X's configuration), you can just use powerplan with it's --persistent flag. |
I don't know what persistent flags are. lol |
You can run it like this: powerplan --persistent
Hey thanks! That's very nice of you 😁 |
This is kind of badass/"Like a boss" behavior. Haha.
You're welcome! EDIT: I have a couple of questions. I just noticed that even though I have |
Can you please a separate issue for this? Let's not flood this issue (GUI) with unrelated stuff. I also think it's ok if you open separate issues for questions/discussion. There's another participant here and they might be getting emails for each message 😅. In the meantime, can you please test if this happens if you run powerplan (the instance not in monitor mode) with the mentioned --persistent argument? |
I've been real busy lately but I started work on a Qt GUI (among other things). I'll probably release it early 2022. |
Oh hell yeah. Let me know whenever you need me to test it. |
Continuing off from the discussion started in #1 by @KarkanAlzwayed.
I actually planned for powerplan to get a profile edition (and perhaps some status plotting/monitoring) GUI at some point, but truth be told, at this point in time I'm not really experienced in writing pretty desktop GUI's and there's still other powerplan features I'd like to implement first. I actually had a look at QtDesigner a while ago and it seemed like a good starting point. If anyone has some framework/library recommendations or would like to give it a go that'd be great!
@KarkanAlzwayed By all means feel free to try! I think Open-Source projects like this are a great way to learn new things, and I'd be happy to do some code review and offer help if needed. If you end up deciding to give it a go, I think good places to start are the classes PowerProfile and CPUSpec. The main project structure is outlined simply here.
The text was updated successfully, but these errors were encountered: