aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorAdrian C. (anrxc) <anrxc@sysphere.org>2009-10-22 14:52:47 +0200
committerAdrian C. (anrxc) <anrxc@sysphere.org>2009-10-22 14:52:47 +0200
commit5c6f544787c1a9e019e24c2d336c69349ad5eca5 (patch)
treeaf84c39e0854b4b28fa5f7b553b818c352226ee0 /README
parent40d78819774dd8b3963c642c2eb6b21948a64943 (diff)
downloadvicious-legacy-5c6f544787c1a9e019e24c2d336c69349ad5eca5.tar.xz
README: more information in Power section
Diffstat (limited to 'README')
-rw-r--r--README31
1 files changed, 18 insertions, 13 deletions
diff --git a/README b/README
index 1321019..cf704d7 100644
--- a/README
+++ b/README
@@ -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