SandUhr is an alarm clock, which is designed as a sand-glass. The program uses
the X Window System and the GNOME desktop environment. The alarm is delivered
to you by either ringing the console bell, by playing a sound file, or by
starting an external program of your choice.
The program is fully integrated into the GNOME application framework.
o Drag and drop: you may drop a color onto the timer to change the sand's visual
appearance.
o It uses the GNOME help system to provide a manual.
o Use of CORBA: The program provides a CORBA interface. So you may control the
SandUhr from within your own programs.
Genmenu is a script capable of generating menus for Blackbox, Fluxbox,
Openbox, WindowMaker and Enlightenment. It works by checking the current
user's $PATH for a predefined list of binaries and adding them to menu
if they are found.
The following options can be configured during runtime:
* Default font to use in all X terminals
* Default X terminal (will be used to launch all console apps in the menu)
* Default size of all web browser windows
* Include menu for starting other window managers (yes|no)
A debugger is a computer program that is used to debug other programs.
Devel::ebug is a simple, extensible Perl debugger with a clean API.
Using this module, you may easily write a Perl debugger to debug your
programs. Alternatively, it comes with an interactive debugger, ebug.
perl5db.pl, Perl's current debugger is currently 2,600 lines of magic
and special cases. The code is nearly unreadable: fixing bugs and
adding new features is fraught with difficulties. The debugger has no
test suite which has caused breakage with changes that couldn't be
properly tested. It will also not debug regexes. Devel::ebug is aimed
at fixing these problems and delivering a replacement debugger which
provides a well-tested simple programmatic interface to debugging
programs. This makes it easier to build debuggers on top of
Devel::ebug, be they console-, curses-, GUI- or Ajax-based.
There are currently two user interfaces to Devel::debug, ebug and
ebug_http. ebug is a console-based interface to debugging programs,
much like perl5db.pl. ebug_http is an innovative web-based interface
to debugging programs.
Flasher monitors changes to one or more files, and indicates the
number of writes to these files by briefly flashing a console LED
once for each write. The flashing sequence is repeated, after a
brief pause, until the files have been read. As the files are
subsequently read, the number of LED flashes is reduced. When all
monitored files have been read, the console LED will be disabled.
The most obvious use is to monitor specific system log or mail files.
Multiple LEDs can be used. Each possible LED (-c, -n or -s) takes
a list of colon-separated file arguments. For example, when invoked
as:
# ./flasher -s /var/log/messages:/var/mail/root
the Scroll Lock LED will flash once for each write made to either
of these files, until the files are read. When /var/log/messages
has been read, the Scroll Lock LED will continue to flash once for
each write that has been made to /var/mail/root, until it also has
been read.
The list of files can include files that don't yet exist.
RipIT is used to create MPEG-1 Layer 3 (mp3) using Lame, or uses Flac (flac),
Ogg Vorbis (ogg) or Faac (m4a) to convert audio files (wav) extracted from an
audio CD. It is a console based front-end (no GUI here), written in Perl, for
various programs.
The program will do the following without user intervention:
* getting the audio CD Album/Artist/Tracks information from CDDB
* ripping the audio CD Tracks
* encoding to Flac, mp3 or Ogg
* id3 tags encoded songs
* creating an playlist (m3u) file
* optionally generating a toc (cue) sheet for nice DAO burning
* optionally preparing and send a CDDB submission and save it locally
* optionally extracting hidden songs and split ghost songs
* optionally creating md5sum files for all tracks
* running several encoder processes at the same time and same run
The heart of the package is 'libcw'. This is a library which, when built,
offers the following basic CW services to a caller program:
o Morse code character translation tables, and lookup functions
o Morse code low-level timing calculations
o A 'sidetone' generation and queueing system, using either the system sound
card, the console speaker, or both
o Optional keying control for an external device, say a transmitter, or an
oscillator
o CW character and string send routines, tied in with the character lookup
o CW receive routines, also tied in to the character lookup
o Adaptive speed tracking of received CW
o An iambic keyer, with both Curtis 8044 types A and B timing
o Straight key emulation
iSQL-Viewer is an open-source JDBC 2.x compliant database front end written
in Java. It implements across multiple platforms features of the JDBC API.
It does everything through a single interface.
iSQL-Viewer works with most database platforms, including PostgreSQL, MySQL,
Oracle, and Informix. iSQL-Viewer provides a variety of tools and features
to carry out common database tasks. It includes:
* Scripting support using JPython and the IBM BSF framework
* A guided query builder for creating simple and complex SQL queries
* Enhanced object viewing for images, HTML, and other binary format files
* A friendly SQL console for executing SQL statements
* Batch processing of SQL files
* Database introspection
* "Bookmarks" to store SQL commands you commonly use
* Import and export to popular file formats such as Microsoft Excel, XML,
HTML and ASCII delimited.
* Enhanced interface support across platforms
iSQL-Viewer is designed to meet the needs of JDBC Driver developers and
database developers who work in single or multi-platform environments.
Bugzilla is one example of a class of programs called "Defect Tracking
Systems", or, more commonly, "Bug-Tracking Systems". Defect Tracking
Systems allow individual or groups of developers to keep track of
outstanding bugs in their product effectively.
Bugzilla has matured immensely, and now boasts many advanced features.
These include:
* integrated, product-based granular security schema
* inter-bug dependencies and dependency graphing
* advanced reporting capabilities
* a robust, stable RDBMS back-end
* extensive configurability
* a very well-understood and well-thought-out natural bug resolution
protocol
* email, XML, console, and HTTP APIs
* available integration with automated software configuration
management systems, including Perforce and CVS (through the
Bugzilla email interface and checkin/checkout scripts)
* too many more features to list
Bugzilla is one example of a class of programs called "Defect Tracking
Systems", or, more commonly, "Bug-Tracking Systems". Defect Tracking
Systems allow individual or groups of developers to keep track of
outstanding bugs in their product effectively.
Bugzilla has matured immensely, and now boasts many advanced features.
These include:
* integrated, product-based granular security schema
* inter-bug dependencies and dependency graphing
* advanced reporting capabilities
* a robust, stable RDBMS back-end
* extensive configurability
* a very well-understood and well-thought-out natural bug resolution
protocol
* email, XML, console, and HTTP APIs
* available integration with automated software configuration
management systems, including Perforce and CVS (through the
Bugzilla email interface and checkin/checkout scripts)
* too many more features to list
pty is a tool to help debug console programs which take the terminal out of
canonical mode, by allowing the program being debugged and the debugger to run
on separate terminal devices.
To use pty, the programmer changes to the terminal device where he or she
wishes to interact with the program to be debugged, and at the shell
prompt, runs pty with no arguments. Pty will print out the filename of the
slave side of the pseudo-terminal it has opened. Inside the debugger,
running in another terminal device, one then redirects the program to be
debugged's IO to the slave (tty command of gdb). When you are finished
using pty, you must manually kill it. When pty starts it prints out its
pid.