Free similarity software for linux

WordNet::Similarity::Visual is a Perl extension for providing visualization tools for WordNet::Similarity.

SYNOPSIS

Basic Usage Example

use WordNet::Similarity::Visual;

$gui = WordNet::Similarity::Visual->new;

$gui->initialize;

This package provides a graphical extension for WordNet::Similarity. It provides a gui for WordNet::Similarity and visualization tools for the various edge counting measures like path, wup, lch and hso.

Smart DJ lets you find tracks based on how similar they sound to each other.

Smart DJ can also automatically add new tracks to your playlist based on how similar they are to what youve been listening to.

You already know how powerful amaroKs search and playlist management capabilities are. Just imagine how cool it would be to find songs that sounds like the one youre listening to, right now. Similar genre, similar sound, similar tempo. Now imagine this: you start playing one of your favorite songs, and, as time goes by, amaroK adds similar songs to your playlist, maintaining the mood. Not just "songs someone else found similar", but songs that truly sound alike, same genre, same mood, same tempo.

Thats what Smart DJ does. Start with a good song, and let amaroK Smart DJs Auto DJ do the rest. Or scratch on your favorite DJ program, and Smart DJ will let you find what to play next real quick. Or build fantastic playlists, sorted by tempo, or song similarity, the sky is the limit. Or simply take any of Smart DJs suggestions for similar songs in the Context browser. Thats the greatest way to discover an entire music collection.

This plug-in is perfect for people who hate making playlists, or hate the predictibility of hearing a playlist, or hate amaroKs Dynamic mode tendency to add songs that ruin the mood. This plug-in is also for people who want to discover the lost and unknown good songs in their own collection. Finally, this plug-in is perfect for DJs who want to plan good sets of songs and playlists for live performance.

The Databionic MusicMiner is a browser for music based on data mining techniques. You can create MusicMaps to visualize the similarity of songs and artists. Explore your music and create playlists based on the paradigm of geographical maps!
Main features:
- Automatic parsing of a folder tree with music files (MP3, OGG, WMA, M4A, MP2, WAV).
- Automatic description of digital audio files by sound.
- Creation of MusicMaps to navigate the sound space based on the paradigm of geographical maps.
- Visual creation of playlists.
- Similarity search in music collection based on sound.
- Customizable hierarchichal browsing of the database by e.g. genre/artist/album or year/artist.
- Flexible database including the seperate storage of several artists per song, albums and playlists as part of a playlist.
- Import and export of meta information based on XML.
Enhancements:
- This release offers better sound descriptors resulting from more experiments with audio features.
- The processing of audio files is more robust, the import of meta information is much faster, and more audio formats are supported.
- MusicMiner now also runs on OS X with some manual setup work described in a howto.

osdchat is a simple messaging utility that allows you to remotely send messages directly to the screen as an on-screen display (OSD).

This may be used a lightweight messaging service in a local area network to message busy admins or communicate with friends who like to watch fullscreen movies or otherwise cannot see whats going on in the background.

There is a wide assortment of options to customize the look, feel, and location of the incoming messages.

I suppose it also shares some similarity with the ancient UNIX utility write, except that tty has been replaced with X. osdchat has been tested only under Linux, specifically Gentoo 1.4 and Slackware 9.0/1, but should work on any full distribution meeting the dependencies.

Installlation:

tar zxvf osdchat-[version].tar.gz
cd osdchat-[version]

Edit the Makefile as needed to change the install paths.

make check (md5sum check to make sure files are intact)
make
make install (need to be root, or have proper capabilities)

Copy sample osdchatd.conf configuration file to /etc or rename to .osdchatd and place it in your home directory. Change settings as desired.

The sample config file is equivalent to the built-in defaults, so a config file is not needed to just test the package.

Exploring Tk::JComboBox Perl module contains a tutorial for usage of the Tk::JComboBox widget.

Overview

This tutorial assumes a familiarity with basic Perl/Tk concepts. It is meant to be used alongside the JComboBox class reference.

What is it and what is it good for?

JComboBox is yet another combo box implementation for use with the Perl/Tk Toolkit. A combo box is a widget that can activate a popup (or dropdown) listbox with a number of selectable items. After an item is selected, the listbox disappears and that item appears on the widget. This is a space-saving alternative to having a full list in the interface, or having a very long Frame or Menu full of radio buttons. In addition to providing a way of selecting one item from a list of options, a Combo Box can also allow a user to add an entry that does not necessarily appear within the list.

This implementation is named for the JComboBox component in the Java Swing classes, and those familiar with that component should have no problem using this because both share several superficial similarities including method names and general behavior -- its a passing resemblance at best.

When compared to other similar Perl/Tk widgets, JComboBox is probably the most bloated or to put it another way, feature-rich. It has a slightly larger overhead associated with it than any of the others. Simply put, there is more code required to support the extra options and methods it offers. In applications I have used it in, Ive found that the cost is negligible and that the benefits outweigh the cost, but since requirements and constraints vary, its probably best to determine this for yourself, and to check out the alternatives.

Two Modes of Operation

Like other Combo Box implementations, the JComboBox has more than one mode of operation: uneditable and editable. The mode can only be set once, at creation time. To better distinguish the two modes, the uneditable mode is called readonly. Unlike other similar Combo box implementations, each mode is distinctive and like having two different Widgets bundled as one. Each mode has a separate default visual appearance, and can affect how options are processed. This is done to emphasize the differences between the two. The basic question is why should an element that looks like a text field, not be editable like a text field and vice versa? So, when a JComboBox is editable it resembles a text field. A user can edit it directly like other text fields, or select one of the items from the list of choices. In readonly mode, the JComboBox resembles a Button, that displays the selected item on its face.

Rose::URI is a standalone URI class allowing easy and efficient manipulation of query parameters and other URI components.

SYNOPSIS

use Rose::URI;

$uri = Rose::URI->new(http://un:pw@foo.com/bar/baz?a=1&b=two+3);

$scheme = $uri->scheme;
$user = $uri->username;
$pass = $uri->password;
$host = $uri->host;
$path = $uri->path;
...

$b = $uri->query_param(b); # $b = "two 3"
$a = $uri->query_param(a); # $a = 1

$uri->query_param_delete(b);
$uri->query_param(c => blah blah);
...

print $uri;

Rose::URI is an alternative to URI. The important differences are as follows.

Rose::URI provides a rich set of query string manipulation methods. Query parameters can be added, removed, and checked for their existence. URI allows the entire query to be set or returned as a whole via the query_form or query methods, and the URI::QueryParam module provides a few more methods for query string manipulation.

Rose::URI supports query parameters with multiple values (e.g. "a=1&a=2"). URI has limited support for this (through query_forms list return value. Better methods are available in URI::QueryParam.

Rose::URI uses Apaches C-based URI parsing and HTML escaping functions when running in a mod_perl 1.x web server environment.

Rose::URI stores each URI "in pieces" (scheme, host, path, etc.) and then assembles those pieces when the entire URI is needed as a string. This technique is based on the assumption that the URI will be manipulated many more times than it is stringified. If this is not the case in your usage scenario, then URI may be a better alternative.

Now some similarities: both classes use the overload module to allow "magic" stringification. Both URI and Rose::URI objects can be printed and compared as if they were strings.
Rose::URI actually uses the URI class to do the heavy lifting of parsing URIs when not running in a mod_perl 1.x environment.

Finally, a caveat: Rose::URI supports only "http"-like URIs. This includes ftp, http, https, and other similar looking URIs. URI supports many more esoteric URI types (gopher, mailto, etc.) If you need to support these formats, use URI instead.