awesomewm-mirrors
/
vicious
mirror of https://github.com/vicious-widgets/vicious.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

README: more information in Power section

This commit is contained in:
Adrian C. (anrxc) 2009-10-22 14:52:47 +02:00
parent 40d7881977
commit 5c6f544787
1 changed files with 18 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
README
View File

@ -7,9 +7,9 @@ ones:
http://git.sysphere.org/vicious/about/
Vicious widget types are a framework for creating your own widgets.
Before using a widget type *you* need to ensure that a valid source of
information exists.
Vicious widget types are a framework for creating your own awesome
widgets. Before using a widget type *you* need to ensure that a valid
source of information exists.
Usage
@ -87,18 +87,23 @@ Power and Caching
-----------------
When a lot of widgets are in use they, and awesome, can generate a lot
of wake-ups and also be very expensive for system resources. This is
especially important when running on battery power. Suspending widgets
is one way to prevent them from draining your battery.
especially important when running on battery power. It was a big
problem with awesome v2 and widgets that used shell scripts to gather
data, and with widget libraries written in languages like Ruby.
Lua is an extremely fast and efficient programming language, and
Vicious takes advantage of that. But suspending Vicious widgets is one
way to prevent them from draining your battery, despite that.
Update intervals also play a big role, and you can save a lot of power
with a smart approach. Avoid intervals like: 5, 10, 30, 60... to avoid
harmonics. If you take the 60-second mark as an example, all of your
widgets would be executed at that point. Instead think about using
only prime numbers, in that case you will have only a few widgets
executed at any given time interval. When choosing intervals also
consider what a widget actually does. Some widget types read files
that reside in memory, others call external utilities and some, like
the mbox widget, read big files.
with a smart approach. Don't use intervals like: 5, 10, 30, 60... to
avoid harmonics. If you take the 60-second mark as an example, all of
your widgets would be executed at that point. Instead think about
using only prime numbers, in that case you will have only a few
widgets executed at any given time interval. When choosing intervals
also consider what a widget actually does. Some widget types read
files that reside in memory, others call external utilities and some,
like the mbox widget, read big files.
Vicious can also cache values returned by widget types. Caching
enables you to have multiple widgets using the same widget type. With