Mirrors/gBar
1
0
Fork 0
mirror of https://github.com/scorpion-26/gBar.git synced 2024-10-06 04:26:49 +00:00
Code Issues Projects Releases Packages Wiki Activity

Fix formatting and improve README

Browse source
This commit is contained in:
scorpion-26 2023-01-14 23:28:39 +01:00 committed by GitHub
parent 7eb364aa6a
commit ddc8af62a5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -1,6 +1,8 @@
# gBar # gBar
My personal blazingly fast and efficient status bar + widgets, in case anyone finds a use for it. My personal blazingly fast and efficient status bar + widgets, in case anyone finds a use for it.
*gBar: **G**TK **Bar***
## Prerequisites ## Prerequisites
*If you don't have the optional dependencies, some features are not available and you must manually disable them.* *If you don't have the optional dependencies, some features are not available and you must manually disable them.*
- wayland - wayland
@ -85,7 +87,7 @@ Audio Flyin:
- Waybar: - Waybar:
Great performance, though limited styling(Almost no dynamic sliders, revealers, ...) and (at least for me) buggy css. Great performance, though limited styling(Almost no dynamic sliders, revealers, ...) and (at least for me) buggy css.
- eww: - eww:
Really solid project with many great customization options. There is one problem though: Performance Really solid project with many great customization options. There is one problem though: Performance.\
Due to the way eww configuration is set up, for each dynamic variable (the number of them quickly grows) you need a shell command which opens a process. Due to the way eww configuration is set up, for each dynamic variable (the number of them quickly grows) you need a shell command which opens a process.
This became quickly a bottleneck, where the bar took up 10% of the CPU-time due to the creation of many processes all the time (without even considering the workspace widget). This became quickly a bottleneck, where the bar took up 10% of the CPU-time due to the creation of many processes all the time (without even considering the workspace widget).
gBar implements all of the information gathering(CPU, RAM, GPU, Disk, ...) in native C++ code, which is WAY faster. In fact, gBar was meant to be a fast replacement/alternative for eww for me. gBar implements all of the information gathering(CPU, RAM, GPU, Disk, ...) in native C++ code, which is WAY faster. In fact, gBar was meant to be a fast replacement/alternative for eww for me.