README: more information in Power section
This commit is contained in:
parent
40d7881977
commit
5c6f544787
31
README
31
README
|
@ -7,9 +7,9 @@ ones:
|
||||||
|
|
||||||
http://git.sysphere.org/vicious/about/
|
http://git.sysphere.org/vicious/about/
|
||||||
|
|
||||||
Vicious widget types are a framework for creating your own widgets.
|
Vicious widget types are a framework for creating your own awesome
|
||||||
Before using a widget type *you* need to ensure that a valid source of
|
widgets. Before using a widget type *you* need to ensure that a valid
|
||||||
information exists.
|
source of information exists.
|
||||||
|
|
||||||
|
|
||||||
Usage
|
Usage
|
||||||
|
@ -87,18 +87,23 @@ Power and Caching
|
||||||
-----------------
|
-----------------
|
||||||
When a lot of widgets are in use they, and awesome, can generate a lot
|
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
|
of wake-ups and also be very expensive for system resources. This is
|
||||||
especially important when running on battery power. Suspending widgets
|
especially important when running on battery power. It was a big
|
||||||
is one way to prevent them from draining your battery.
|
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
|
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
|
with a smart approach. Don't use intervals like: 5, 10, 30, 60... to
|
||||||
harmonics. If you take the 60-second mark as an example, all of your
|
avoid harmonics. If you take the 60-second mark as an example, all of
|
||||||
widgets would be executed at that point. Instead think about using
|
your widgets would be executed at that point. Instead think about
|
||||||
only prime numbers, in that case you will have only a few widgets
|
using only prime numbers, in that case you will have only a few
|
||||||
executed at any given time interval. When choosing intervals also
|
widgets executed at any given time interval. When choosing intervals
|
||||||
consider what a widget actually does. Some widget types read files
|
also consider what a widget actually does. Some widget types read
|
||||||
that reside in memory, others call external utilities and some, like
|
files that reside in memory, others call external utilities and some,
|
||||||
the mbox widget, read big files.
|
like the mbox widget, read big files.
|
||||||
|
|
||||||
Vicious can also cache values returned by widget types. Caching
|
Vicious can also cache values returned by widget types. Caching
|
||||||
enables you to have multiple widgets using the same widget type. With
|
enables you to have multiple widgets using the same widget type. With
|
||||||
|
|
Loading…
Reference in New Issue