The goal of this project is to add Cell Shading capabilities to the Quake III
engine with real-time performance.
In order to provide such feature we have decided to use Kuwahara filter, a
noise-reduction filter that preserves edges.
It uses four subquadrants to calculate the mean and variance and chooses the
mean value for the region with the smallest variance.
To increase the hand-painted effect we have decided to apply a simple blur
filter to reduce hard-edges on textures and increase the flatness effect.
To produce the cell shading effect we use no graphics card shaders, so our
implementation could run with almost any graphics card. The edge effect is
produced by painting backface polygons with a thick wireframe without
textures and repaint all the scene, but this time, with textures.
We have also implemented a different algorithm (we call it White Texture),
which uses white textures. You can set the console variable r_celshadalgo
to 2, and load another map, or run using the appropriate link that came
with the release.
Pidgin is a multi-protocol instant messaging client. It is compatible with AIM
(Oscar and TOC protocols), ICQ, MSN Messenger, Yahoo, IRC, Jabber, Gadu-Gadu,
and Zephyr networks.
Pidgin users can log in to multiple accounts on multiple IM networks
simultaneously. This means that you can be chatting with friends on AOL
Instant Messenger, talking to a friend on Yahoo Messenger, and sitting in an
IRC channel all at the same time.
Pidgin supports many features of the various networks, such as file transfer
(coming soon), away messages, typing notification, and MSN window closing
notification. It also goes beyond that and provides many unique features. A
few popular features are Buddy Pounces, which give the ability to notify you,
send a message, play a sound, or run a program when a specific buddy goes away,
signs online, or returns from idle; and plugins, consisting of text
replacement, a buddy ticker, extended message notification, iconify on away,
and more.
(Adapted from the About Pidgin page.)
Libgaim is a backend library and protocol modules needed for Pidgin frontend
frontends such as the GTK+ and console UIs.
The biggest difference between runwhen and other schedulers is that
runwhen doesn't have a single daemon overseeing multiple jobs.
The runwhen tools essentially act as a glorified sleep command.
Perhaps runwhen does nothing that at(1) doesn't, and there are
lots of things at(1) does that runwhen doesn't:
- runwhen doesn't change user IDs - thus it will never run
anything as the wrong user.
- It doesn't keep a central daemon running at all times -
thus it won't break if that daemon dies.
- It doesn't require any modifications to the system boot procedure.
- It doesn't log through syslog(3) - thus it won't make a mess
on the console if syslogd(1) isn't running.
- It doesn't centralize storage of scheduled jobs (or any other
per-job information) - thus unprivileged users can install and use it
without cooperation from root, and without the use of a setuid program
to handle changes.
- It doesn't send output through mail - thus it doesn't break
if there is no mail system installed.
- It doesn't check access control files - thus it doesn't gratuitously
deny users.
http://www.linuxtv.org/vdrwiki/index.php/Remote-plugin
This plugin extends the remote control capabilities of vdr.
The following remote control devices are supported:
(a) Linux input device driver ('/dev/input/eventX', X=0,1,2,...)
(currently not supported on FreeBSD)
(b) keyboard (tty driver): /dev/console, /dev/ttyX
(c) TCP connection (telnet)
(d) LIRC
(e) some(?) FreeBSD uhid(4) devices (experimental support added by this port)
To use, add something like this to vdr_flags: '-Premote -h /dev/uhid0',
(re)start vdr, then the osd should ask you to configure the
remote by pressing the buttons you want to assign.
Note: If your remote is detected as a keyboard you'll have to
tell ukbd(4) to ignore it first by doing (as root) something like:
usbconfig add_dev_quirk_vplh 0x1241 0xe000 0 0xffff UQ_KBD_IGNORE
(and possibly unplug it for a moment or reset it via usbconfig,
0x1241 there is the vendor id, 0xe000 the product id of the
device, you can get yours by doing
usbconfig -d 1.2 dump_device_desc
and looking for idVendor and idProduct, -d 1.2 there corresponds
to ugen1.2 listed by usbconfig w/o args.)
You can check with:
usbconfig show_ifdrv
if the device is then listed as ugen...: uhid... you're good to go.
2nd note: If vdr cannot open your uhid device check it is not claimed
by xorg:
fstat |grep uhid
If it is you may need an xorg.conf(5) with manually defined
InputDevice sections for mouse and keyboard and
Option "AutoAddDevices" "False"
in the ServerFlags section.
And if for some reason you want to reassign the buttons on the
remote you can stop vdr and do:
touch /usr/local/etc/vdr/channels.conf
and/or remove uhid entries from
/usr/local/etc/vdr/remote.conf .
When you then start vdr again it should ask to configure the
remote again.