Free features found software for linux

Gimp::Feature is a Perl module that can check for specific features to be present before registering the script.

SYNOPSIS

use Gimp::Feature;
or
use Gimp::Feature qw(feature1 feature2 ...);

This module can be used to check for specific features to be present. This can be used to deny running the script when neccessary features are not present. While some features can be checked for at any time, the Gimp::Fu module offers a nicer way to check for them.

gtk

checks for the presence of the gtk interface module.

gtk-1.1, gtk-1.2

checks for the presence of gtk-1.1 (1.2) or higher.

perl-5.005

checks for perl version 5.005 or higher.

pdl

checks for the presence of a suitable version of PDL (>=1.9906).

gnome

checks for the presence of the Gnome-Perl module.

gtkxmhtl

checks for the presence of the Gtk::XmHTML module.

unix

checks wether the script runs on a unix-like operating system. At the moment, this is every system except windows, macos, os2 and vms.

persistency

checks wether the Gimp::Data module (Gimp::Data) can handle complex persistent data structures, i.e. perl references in addition to plain strings.

The following features can only be checked after Gimp-main> has been called (usually found in the form exit main). See Gimp::Fu on how to check for these.
gimp-1.1, gimp-1.2

checks for the presense of gimp in at least version 1.1 (1.2).

FUNCTIONS

present(feature)

Checks for the presense of the single feature given as the argument. Returns true if the feature is present, false otherwise.

need(feature,[function-name])

Require a specific feature. If the required feature is not present the program will exit gracefully, logging an appropriate message. You can optionally supply a function name to further specify the place where this feature was missing.

This is the function used when importing symbols from the module.

missing(feature-description,[function-name])

Indicates that a generic feature (described by the first argument) is missing. A function name can further be specified. This function will log the given message and exit gracefully.

describe(feature)

Returns a string describing the given feature in more detail, or undef if there is no description for this feature.

list()

Returns a list of features that can be checked for. This list might not be complete.

Lingua::Phonology::Features is a module to handle a set of hierarchical features.

SYNOPSIS

use Lingua::Phonology;

my $phono = new Lingua::Phonology;
my $features = $phono->features;

# Add features programmatically
$features->add_feature(
Node => { type => privative, children => [Scalar, Binary, Privative] },
Scalar => { type => scalar },
Binary => { type => binary },
Privative => { type => privative }
);

# Drop features
$features->drop_feature(Privative);

# Load feature definitions from a file
$features->loadfile(phono.xml);

# Load default features
$features->loadfile;

Lingua::Phonology::Features allows you to create a hierarchy of features of various types, and includes methods for adding and deleting features and changing the relationships between them.

By "heirarchical features" we mean that some features dominate some other features, as in a tree. By having heirarchical features, it becomes possible to set multiple features at once by assigning to a node, and to indicate conceptually related features that are combined under the same node. This module, however, does not instantiate values of features, but only establishes the relationships between features.

Lingua::Phonology::Features recognizes multiple types of features. Features may be privative (which means that their legal values are either true or undef), binary (which means they may be true, false, or undef), or scalar (which means that their legal value may be anything). You can freely mix different kinds of features into the same set of features.

Finally, while this module provides a full set of methods to add and delete features programmatically, it also provides the option of reading feature definitions from a file. This is usually faster and more convenient. The method to do this is "loadfile". Lingua::Phonology::Features also comes with an extensive default feature set.

Email::Find allows you to find RFC 822 email addresses in plain text.

Email::Find is a module for finding a subset of RFC 822 email addresses in arbitrary text (see "CAVEATS"). The addresses it finds are not guaranteed to exist or even actually be email addresses at all (see "CAVEATS"), but they will be valid RFC 822 syntax.

Email::Find will perform some heuristics to avoid some of the more obvious red herrings and false addresses, but theres only so much which can be done without a human.

Finds email addresses in the text and executes callback registered.

The callback is given two arguments. The first is a Mail::Address object representing the address found. The second is the actual original email as found in the text. Whatever the callback returns will replace the original text.

NetAddr::IP::Find is a Perl module to find IP addresses in plain text.

SYNOPSIS

use NetAddr::IP::Find;
$num_found = find_ipaddrs($text, &callback);

This is a module for finding IP addresses in plain text.

Functions

NetAddr::IP::Find exports one function, find_ipaddrs(). It works very similar to URI::Finds find_uris() or Email::Finds find_emails().

$num_ipaddrs_found = find_ipaddrs($text, &callback);

The first argument is a text to search through and manipulate. Second is a callback routine which defines what to do with each IP address as theyre found. It returns the total number of IP addresses found.

The callback is given two arguments. The first is a NetAddr::IP instance representing the IP address found. The second is the actual IP address as found in the text. Whatever the callback returns will replace the original text.

EXAMPLES

# For each IP address found, ping its host to see if its alive.
use Net::Ping;
my $pinger = Net::Ping->new;
my %pinged;
find_ipaddrs($text, sub {
my($ipaddr, $orig) = @_;
my $host = $ipaddr->to_string;
next if exists $pinged{$host};
$pinged{$host} = $pinger->ping($host);
});

while (my($host, $up) == each %pinged) {
print "$host is " . $up ? up : down . "n";
}


# Resolve IP address to FQDN
find_ipaddrs($text, sub {
my($ipaddr, $orig) = @_;
resolve_ip($ipaddr->to_string);
});

sub resolve_ip {
use Net::DNS;
# see perldoc Net::DNS for details
}

TunesBrowser project is a simple music player, capable of playing music found on iTunes shares.
TunesBrowser can connect to the latest iTunes applications (as of April 29 2004) and is implemented on top of libopendaap.
TunesBrowsers interface is quite similar to that of iTunes. TunesBrowser was written with the purpose of being a prototype front-end for libopendaap. I intend to integrate libopendaap with other, more mature, players.
Main features:
- Play mp3s off other computers running iTunes
- Discovery of hosts over Rendezvous.

htb-stats.sh is a useful script for htb class summarization. htb-stats is designed to allow simple, non-root usage, e.g. "./htb-stats.sh eth0".
If an htb.init, tcng.init, or htb-gen configuration is found, it will label traffic output with information taken from respective configuration files.
Enhancements:
- support label-less , adapt to newer tcs backlog output