Free surprise software for linux

Streamripper records shoutcast-compatible streams. For shoutcast style streams it finds the "meta data" or track separation data, and uses that as a marker for where the track should be separated.
The MP3 data is decoded and scanned for a silent point, which is where tracks will be created.
Streamripper was started sometime back in early 2000. Streamripper started as a way to separate tracks via Shoutcasts title-streaming feature. This has now been expanded into a much more generic feature, where part of the program only tries to "hint" at where one track starts and another ends, thus allowing a mp3 decoding engine to scan for a silent mark, which is used to find an exact track separation.
Streamripper is now part of the FreeBSD standard distribution, mentioned in the Linux MP3 HOWTO, known to compile on many platforms such as Linux, Windows, FreeBSD, BeOS, OS/2. This is not surprising as portability was a constant consideration during development.
With the emergence of file sharing protocols such as Napster, Gnutella, and now Mojonation and Freenet, the average Internet user can download nearly any mp3 he wants in a matter of no time, but many times people dont know what they want.
Streamripper allows you to download an entire station of music. Many of these mp3 radio stations only play certain genres, so you can now download an entire collection of goa/trance music, an entire collection of jazz, punk rock, whatever you want.
Enhancements:
- Fix problem with -E flag

PXR::Parser is a Pure Perl SAX XML Push Parser.

SYNOPSIS

use PXR::Parser;

my $parser = PXR::Parser->new(
Handlers => {
startDocument => &start_doc,
endDocument => &end_doc,
startElement => &start_element,
endElement => &end_element,
characters => &characters,
}
);

$parser->parse($data);

$parser->setHandlers(startDocument => &different_start);

A simple, fast, efficient pure perl sax xml parser.

BUGS AND NOTES

This Parser was blatantly ripped and modified from XML::Stream::Parser because it was the only pure perl parser simple and speedy enough to be included by default in various other things such as PXR or PoCo::Jabber. Just note that there is no recovering or detecting XML malformedness. So if you feed this little pet something non-tasty, you are in for a surprise (mainly memory leaking everywhere, and other things like gnawing on furniture).

That is the trade off for its speed. In situtations where you know you are not going to get malformed XML such as a connection to a jabber server (or other XML pushing entities) then this parser is ideal. Currently, the speed difference between this parser and XML::Parser::Expat are about 30 percent in favor of XML::Parser::Expat (which says alot of the speed of this pure perl implementation).

Thanks to Ryan Eatmon for writing and releasing this code. It has been a boon to those of us that really appreciate a simple small solution.

Slicetime is a program that helps you track time you spend on projects. Slicetime is designed to make it easy to switch between different projects, the main window is in the shape of vertical sidebar that makes it convenient to keep it always visible on the side of the screen. In short, continuous tracking of time taken on projects is made as effortless as possible.
The purpose of the program is to make you aware of which tasks take more time, and which take less; it can also be used to keep track and charge time if youre working for someone on hourly basis. The advantage of the program is that it lets you switch back and forth very easily, letting you keep a very accurate account of how much a task took even if you have to stop it frequently and work on something else.
The results can be very surprising, something may feel like it took only a few minutes whereas it took almost an hour in real time; the reverse is sometimes true although not as often.
Slicetime main window is a vertical bar with a row of buttons, each button representing a project. When the button is pressed in, the project is active, the rest of projects are inactive. Each project button shows the time taken on the project today. At 12 oclock the daily time is reset and new days count is started.
Time is kept for current day, week, month and total. Example: I may have a slicetime project that has 3:59 time today, 8:00 this week (including today), 17:00 this month (including this week) and 125:00 total time, which may have been accumulated over years.
Slicetime makes it easy to change project time for current day if you forgot to check in or check out. Menu command (add or subtract project time) will add or subtract the time for today. Another command will set all times for total, month, week and day.
Slicetime as of now has two report options, it can report by time taken for each project on a daily, weekly, montly and total basis and the same by percentage. For example, it will show that today project A was 60%, project B - 30% and C - 10%, and will do the same for current week, month and total.
Note that Slicetime does not keep separate time accounting from previous week, month, day, etc. It will not tell you that you spend 5 hours last saturday. It will only tell you total time, time taken on current month, week and day; but it makes perfect sense to keep this data as well, and I will almost certainly add it.
Functionality:
- Add project
- Remove project (deletes all data and button, irrecoverable, use sparingly!)
- Report by time
- Report by percentage
- Set project time
- Add or subtract project time
Version restrictions:
- Number of project buttons is effectively limited by vertical size of screen. On a common 1024 res, you can fit in around 42 projects, which should be enough for anyone, but I will add an option of hiding projects from main window if requested.
- Latest version not tested in Unix, but will most likely work. I will test it soon & fix if needed.
- Could keep time for each past day, week, month, year. Most likely will be added eventually.
Enhancements:
- Several bugs were fixed.
- The interface was changed to be more user friendly.
- Autosave functionality was added to make up for some stability problems on WinXP.

classesfaq is a Perl module with frequently asked questions about the Perl classes pragma.
Main features:
- Compile-time classes, no base class required
- Dynamic classes, alter or create at run-time
- Attributes, class and object, private, read-only, public
- Mixins, methods by name or regx, attributes also
- Single and multiple inheritance
- Accessors, optimized, overridable with read-only
- Accessor dispatch methods set and get
- Method declaration, delegation, ABSTRACT and EMPTY
- Separate new and clone methods, overridable
- Optional initialize method, aggregation
- Utility methods: dump, load, CLASS, SUPER
- Dynamically preserved declaration and mixin tracking
- Simplified exceptions, one line exception classes with inheritance trees
- Base exception class, light, robust, traceable
- 8 reusable exception classes in X:: namespace
- Compatible standard internals, easy porting, no surprises
What is the classes pragma?
A simple, stable, fast, and flexible way to use Perl 5 classes. If you look at no other Perl OO module look at this one, really. If you have done OO in Perl you will find this comfortably familiar. If not you may save yourself time and pain learning the classes pragma first or as you learn Perl OO--many have already.
Why should I use the classes pragma?
- Relevant: fills real-world need for conventional Perl OO
- Lazy: 100+ conventional lines reduced to 1
- Simple: standard readable terms, UML friendly
- Stable: 1000+ unit test points, used reliably in large applications
- Portable: OS independent, single file, 100% pure perl
- Fast: benchmarks faster or equal to the long way
- Light: only standard deps, requires greater than 5.6.1
- Sustainable: tag model, clean, commented
- Open: Perl artistic license, multi-language friendly
- Supported: mailing list, site, documented, actively maintained
If for no other reason because it is a new approach.

Stat::lsMode Perl module can format file modes like the ls -l command does.

SYNOPSIS

use Stat::lsMode;

$mode = (stat $file)[2];
$permissions = format_mode($mode);
# $permissions is now something like `drwxr-xr-x

$permissions = file_mode($file); # Same as above

$permissions = format_perms(0644); # Produces just rw-r--r--

$permissions = format_perms(644); # This generates a warning message:
# mode 644 is very surprising. Perhaps you meant 0644...

Stat::lsMode->novice(0); # Disable warning messages

Stat::lsMode generates mode and permission strings that look like the ones generated by the Unix ls -l command. For example, a regular file that is readable by everyone and writable only by its owner has the mode string -rw-r--r--. Stat::lsMode will either examine the file and produce the right mode string for you, or you can pass it the mode that you get back from Perls stat call.

format_mode

Given a mode number (such as the third element of the list returned by stat), return the appopriate ten-character mode string as it would have been generated by ls -l. For example, consider a directory that is readable and searchable by everyone, and also writable by its owner. Such a directory will have mode 040755. When passed this value, format_mode will return the string drwxr-xr-x.
If format_mode is passed a permission number like 0755, it will return a nine-character string insted, with no leading character to say what the file type is. For example, format_mode(0755) will return just rwxr-xr-x, without the leading d.

file_mode

Given a filename, do lstat on the file to determine the mode, and return the mode, formatted as above.

Novice Operation Mode

A common mistake when dealing with permission modes is to use 644 where you meant to use 0644. Every permission has a numeric representation, but the representation only makes sense when you write the number in octal. The decimal number 644 corresponds to a permission setting, but not the one you think. If you write it in octal you get 01204, which corresponds to the unlikely permissions -w----r-T, not to rw-r--r--.

The appearance of the bizarre permission -w----r-T in a program is almost a sure sign that someone used 644 when they meant to use 0644. By default, this module will detect the use of such unlikely permissions and issue a warning if you try to format them. To disable these warnings, use

Stat::lsMode->novice(0); # disable novice mode

Stat::lsMode->novice(1); # enable novice mode again

The surprising permissions that are diagnosed by this mode are:

111 => --xr-xrwx
400 => rw--w----
440 => rw-rwx---
444 => rw-rwxr--
551 => ---r--rwt
600 => --x-wx--T
640 => -w------T
644 => -w----r-T
660 => -w--w-r-T
664 => -w--wx--T
666 => -w--wx-wT
700 => -w-rwxr-T
711 => -wx---rwt
750 => -wxr-xrwT
751 => -wxr-xrwt
751 => -wxr-xrwt
755 => -wxrw--wt
770 => r------wT
771 => r------wt
775 => r-----rwt
777 => r----x--t

Of these, only 400 is remotely plausible.

BUGS

As far as I know, the precise definition of the mode bits is portable between varieties of Unix. The module should, however, examine stat.h or use some other method to find out if there are any local variations, because Unix being Unix, someone somewhere probably does it differently.

Maybe it file_mode should have an option that says that if the file is a symlink, to format the mode of the pointed to file instead of the mode of the link itself, the way ls -Ll does.

PDL::Indexing Perl module contains a tutorial on how to index piddles.

This manpage should serve as a first tutorial on the indexing and threading features of PDL.

This manpage is still in alpha development and not yet complete. "Meta" comments that point out deficiencies/omissions of this document will be surrounded by square brackets ([]), e.g. [ Hopefully I will be able to remove this paragraph at some time in the future ]. Furthermore, it is possible that there are errors in the code examples. Please report any errors to Christian Soeller (c.soeller@auckland.ac.nz).

Still to be done are (please bear with us and/or ask on the mailing list, see PDL::FAQ):

document perl level threading
threadids
update and correct description of slice
new functions in slice.pd (affine, lag, splitdim)
reworking of paragraph on explicit threading

Indexing and threading with PDL

A lot of the flexibility and power of PDL relies on the indexing and looping features of the perl extension. Indexing allows access to the data of a pdl object in a very flexible way. Threading provides efficient implicit looping functionality (since the loops are implemented as optimized C code).

Pdl objects (later often called "pdls") are perl objects that represent multidimensional arrays and operations on those. In contrast to simple perl @x style lists the array data is compactly stored in a single block of memory thus taking up a lot less memory and enabling use of fast C code to implement operations (e.g. addition, etc) on pdls.

pdls can have children

Central to many of the indexing capabilities of PDL are the relation of "parent" and "child" between pdls. Many of the indexing commands create a new pdl from an existing pdl. The new pdl is the "child" and the old one is the "parent". The data of the new pdl is defined by a transformation that specifies how to generate (compute) its data from the parents data. The relation between the child pdl and its parent are often bidirectional, meaning that changes in the childs data are propagated back to the parent. (Note: You see, we are aiming in our terminology already towards the new dataflow features. The kind of dataflow that is used by the indexing commands (about which you will learn in a minute) is always in operation, not only when you have explicitly switched on dataflow in your pdl by saying $a->doflow. For further information about data flow check the dataflow manpage.)

Another way to interpret the pdls created by our indexing commands is to view them as a kind of intelligent pointer that points back to some portion or all of its parents data. Therefore, it is not surprising that the parents data (or a portion of it) changes when manipulated through this "pointer". After these introductory remarks that hopefully prepared you for what is coming (rather than confuse you too much) we are going to dive right in and start with a description of the indexing commands and some typical examples how they might be used in PDL programs. We will further illustrate the pointer/dataflow analogies in the context of some of the examples later on.

There are two different implementations of this ``smart pointer relationship: the first one, which is a little slower but works for any transformation is simply to do the transformation forwards and backwards as necessary. The other is to consider the child piddle a ``virtual piddle, which only stores a pointer to the parent and access information so that routines which use the child piddle actually directly access the data in the parent. If the virtual piddle is given to a routine which cannot use it, PDL transparently physicalizes the virtual piddle before letting the routine use it.

Currently (1.94_01) all transformations which are ``affine, i.e. the indices of the data item in the parent piddle are determined by a linear transformation (+ constant) from the indices of the child piddle result in virtual piddles. All other indexing routines (e.g. ->index(...)) result in physical piddles. All routines compiled by PP can accept affine piddles (except those routines that pass pointers to external library functions).

Note that whether something is affine or not does not affect the semantics of what you do in any way: both

$a->index(...) .= 5;
$a->slice(...) .= 5;

change the data in $a. The affinity does, however, have a significant impact on memory usage and performance.