Age | Commit message (Collapse) | Author | Files |
|
|
|
With the Lua 5.2 port we change the way vicious is loaded as a module,
so that it remains backwards compatible with Lua 5.1 users. Also added
the author of the Lua 5.2 port to the contributors list.
|
|
Thermal now accepts an optional third argument when warg is a table.
|
|
|
|
Many users miss the fact they can register their functions as widget
types. Documentation for wtype being incomplete wasn't helping.
|
|
|
|
|
|
There's no more need to edit init files and manually disable widgets.
Signed-off-by: Joerg T. (Mic92) <jthalheim@gmail.com>
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
|
|
Old dio.lua was moved to contrib. New one is used like CPU widget is,
request the device or parition in the format argument, {sda read_mb}
as an example. New widget doesn't provide scheduler information, but I
don't know anyone who used that. If you think this is wrong let me
know.
|
|
|
|
|
|
|
|
The os.time() call should not be passed as an argument it self,
because of a chance it will be stored internally and so we would
always get the same time. Instead we can pass time offsets in seconds,
i.e. to go 6 hours forward we can use the widget argument 21600, to go
6 hours back we use -21600 instead.
|
|
Format custom time for example to calculate time zone differences, New
York time relative to me would be widget argument: os.time()-21600
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This widget type returns 1st value as the number of assigned, and 2nd
as active, devices in the array provided as the widget argument.
|
|
Operating System widget type now returns two additional values, 5th as
available system entropy and 6th as available entropy in percent.
|
|
|
|
|
|
|
|
|
|
If you would like to be removed from the list let me know.
|
|
Contrib should be better known because of the extra widgets it
contains. While the vicious-fbsd branch by Richard Kolkovich was
already added to the vicious home page and needs more exposure.
|
|
|
|
Widget type uses curl now, like all other types accessing network
resources (until, if ever, we switch to luasocket). Where previously
only the currently playing song was returned now you can access these
keys: {volume}, {state}, {Artist}, {Title}, {Album}, {Genre}. You can
provide an optional table argument to change password, host or port.
|
|
I/O scheduler information is stored in the key: {sched}
|
|
This widget type returns 1st value as the operating system in use, 2nd
as the release version, 3rd as your username and 4th the hostname.
|
|
Login information is now kept in the ~/.netrc file, which should be
readable only by the owner. This should solve futher problems with
unquoted characters addressed in the last commit. The format of the
~/.netrc file is as follows (also documented in the README):
machine mail.google.com login user password pass
|
|
Format string and key example: "${/home avail_p}"
|
|
|
|
New function introduced vicious.force({ widget, }) - widget argument
is a table with one or more widgets that will be updated.
|
|
|
|
|
|
|
|
Widge type returns 1st value as the volume level and 2nd as the mute
state of the requested channel represented as a symbol.
|
|
|
|
|
|
|
|
Widget type takes the mixer control as an argument, i.e. "PCM" but can
take optional amixer options, i.e. "PCM -c 1".
|
|
Widget type now takes the thermal zone as an argument, or a table with
1st field as thermal zone and 2nd field as data source. Available data
sources are: "proc" (procfs ACPI), "sys" (sysfs like before) and
"core" (sysfs coretemp). When only the thermal zone is provided widget
defaults to "sys".
|
|
|
|
This widget type now takes the distribution name as an argument; Arch,
Arch S, Debian and Fedora examples are now in the package manager
table. Feedback from yum users is needed.
|
|
This changes keys that are returned, previously only total I/O was
available in: {raw}, {kb} and {mb}. Keys returned now are (s=raw):
{total_s}, {total_kb}, {total_mb}, {read_s}, {read_kb}, {read_mb},
{write_s},{write_kb} and {write_mb}.
|
|
|
|
Previous version could return 1 on one update and 900 on the next (1st
being GB, 2nd MB) a user appending "GB" to the value suddenly has a
900GB disk available. Returned keys are now: size_mb, size_gb,
used_mb, used_gb, avail_mb, avail_gb, and percentage is now: used_p.
|