moosic 0.09
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 67
Audio::Moosic 0.09
Audio::Moosic is a Moosic client library for Perl. more>>
Audio::Moosic is a Moosic client library for Perl.
SYNOPSIS
use Audio::Moosic;
$moo = Audio::Moosic::Unix->new();
$moosic->append(/home/me/somewhat.ogg);
$moosic->play;
print $moosic->current, "n";
$moosic->pause;
...
Audio::Moosic acts as a client for the musical jukebox programm Moosic (http://nanoo.org/~daniel/moosic/) by Daniel Pearson.
Using Audio::Moosic you can connect to a moosic server either via an UNIX socket or an INET socket.
<<lessSYNOPSIS
use Audio::Moosic;
$moo = Audio::Moosic::Unix->new();
$moosic->append(/home/me/somewhat.ogg);
$moosic->play;
print $moosic->current, "n";
$moosic->pause;
...
Audio::Moosic acts as a client for the musical jukebox programm Moosic (http://nanoo.org/~daniel/moosic/) by Daniel Pearson.
Using Audio::Moosic you can connect to a moosic server either via an UNIX socket or an INET socket.
Download (0.009MB)
Added: 2007-01-03 License: Perl Artistic License Price:
1025 downloads
moosicWebGUI 0.9
moosicWebGUI is a stand alone client program for controlling the moosic jukebox system. more>>
moosicWebGUI is a stand alone client program for controlling the moosic jukebox system. moosicWebGUI implements not only basic basic player functions but also more sophisticated functions for manipulating the playlist. It incorporates a small Web server based on Pythons SimpleHTTPServer library.
Main features:
- general player commands:
start, stop, next, previous, pause, skip +10/-10, repeat (loop), ...
- playlist commands:
shuffle, sort, reverse, delete duplicates, clear, save to file, load from file
- browse and search modes:
browse/search playlist, browse/search history, browse/search local files, tree view
- insert options:
single files or all music files in single directory or whole directory tree;
- add to top or bottom of playlist or mixin
Enhancements:
- Startup was accelerated.
- An online handbook was started.
- Links to the online handbook and to the manual page were added to the template.
- The man page was improved.
<<lessMain features:
- general player commands:
start, stop, next, previous, pause, skip +10/-10, repeat (loop), ...
- playlist commands:
shuffle, sort, reverse, delete duplicates, clear, save to file, load from file
- browse and search modes:
browse/search playlist, browse/search history, browse/search local files, tree view
- insert options:
single files or all music files in single directory or whole directory tree;
- add to top or bottom of playlist or mixin
Enhancements:
- Startup was accelerated.
- An online handbook was started.
- Links to the online handbook and to the manual page were added to the template.
- The man page was improved.
Download (0.027MB)
Added: 2005-12-04 License: GPL (GNU General Public License) Price:
1419 downloads
Goo 0.09
Goo - stick things together with The Goo. more>>
Goo - stick things together with The Goo.
SYNOPSIS
shell> goo -p Object.pm # show a [P]rofile of Object.pm
shell> goo -l Object.pm # show Back [L]inks to Object.pm
shell> goo -r Object.pm # [R]un Object.pm
shell> goo -i Object.pm # comp[I]le Object.pm
shell> goo -p access.log # show a [P]rofile of access.log
shell> goo -c Object.pm # [C]lone Object.pm into another Thing
shell> goo -o # the Care[O]Meter shows Things you care about while coding (e.g., tasks, bugs)
shell> goo -z # show Things in your working [Z]one or mental buffer
"The Goo" helps you stick "Things" together in your working environment.
Things include Perl modules, Perl scripts, log files, javascripts, configuration files, database tables, templates etc.
The Goo records a "Trail" as you jump quickly from Thing to Thing in a simple, text-based console. It remembers how you associate Things in your environment.
Accelerate your work by quickly traversing the Trail of associations between Things.
METHODS
check_environment
Check and set up the environment.
do_action
Take a command line switch (e.g., -p) and map it to an action handler (e.g., [P]rofile) and perform the action on the Thing.
<<lessSYNOPSIS
shell> goo -p Object.pm # show a [P]rofile of Object.pm
shell> goo -l Object.pm # show Back [L]inks to Object.pm
shell> goo -r Object.pm # [R]un Object.pm
shell> goo -i Object.pm # comp[I]le Object.pm
shell> goo -p access.log # show a [P]rofile of access.log
shell> goo -c Object.pm # [C]lone Object.pm into another Thing
shell> goo -o # the Care[O]Meter shows Things you care about while coding (e.g., tasks, bugs)
shell> goo -z # show Things in your working [Z]one or mental buffer
"The Goo" helps you stick "Things" together in your working environment.
Things include Perl modules, Perl scripts, log files, javascripts, configuration files, database tables, templates etc.
The Goo records a "Trail" as you jump quickly from Thing to Thing in a simple, text-based console. It remembers how you associate Things in your environment.
Accelerate your work by quickly traversing the Trail of associations between Things.
METHODS
check_environment
Check and set up the environment.
do_action
Take a command line switch (e.g., -p) and map it to an action handler (e.g., [P]rofile) and perform the action on the Thing.
Download (0.096MB)
Added: 2007-05-09 License: Perl Artistic License Price:
898 downloads
Moosic 1.5.4
Moosic is a music player for Unix systems. more>>
Moosic is a music player for Unix systems. It focuses on convenient and powerful playlist management. This project consists of a server process that maintains a queue of songs to be played and one or more client programs which sends commands to the server.
The server continually runs through its song queue, popping songs off the top of the list and playing each with an external program. The client is a simple command-line utility which allows you to easily perform powerful operations upon the servers queue, including the addition of whole directory trees, automatic shuffling, and song removal according to regular expressions.
The server comes configured to play MP3, Ogg, MIDI, MOD, and WAV files, but can be configured to also play any other file format you want.
<<lessThe server continually runs through its song queue, popping songs off the top of the list and playing each with an external program. The client is a simple command-line utility which allows you to easily perform powerful operations upon the servers queue, including the addition of whole directory trees, automatic shuffling, and song removal according to regular expressions.
The server comes configured to play MP3, Ogg, MIDI, MOD, and WAV files, but can be configured to also play any other file format you want.
Download (0.16MB)
Added: 2007-07-14 License: GPL (GNU General Public License) Price:
832 downloads
Perlbox Voice 0.09
Perlbox Voice is a voice command system. more>>
Perlbox.org provides voice solutions for Linux and Unix desktop control. There is great need for quality accessibility for the Linux desktop.
The need will only grow as Linux and open source Unix continue to grow more popular on home, educational, corporate and government desktops and servers. Contact us for more information.
Linux should be accessible. We have worked with the open source community for three years to grow several free software products centered around voice and speech recognition, accessible interfaces, and voice control for Linux.
<<lessThe need will only grow as Linux and open source Unix continue to grow more popular on home, educational, corporate and government desktops and servers. Contact us for more information.
Linux should be accessible. We have worked with the open source community for three years to grow several free software products centered around voice and speech recognition, accessible interfaces, and voice control for Linux.
Download (1.22MB)
Added: 2005-09-15 License: GPL (GNU General Public License) Price:
1520 downloads
MoosicApplet 0.3.2
MoosicApplet is a GNOME panel applet that displays the status of the Moosic server. more>>
MoosicApplet is a GNOME panel applet which displays the current status of the Moosic jukebox server.
It also provides some basic features for controlling the song player. MoosicApplet features a configurable layout and the ability to rewrite the song name in various ways to make it easier to read.
<<lessIt also provides some basic features for controlling the song player. MoosicApplet features a configurable layout and the ability to rewrite the song name in various ways to make it easier to read.
Download (0.030MB)
Added: 2005-11-14 License: GPL (GNU General Public License) Price:
1439 downloads
wmifinfo 0.09
wmifinfo is a simple applet showing basic network info for all available interfaces. more>>
wmifinfo is a simple applet showing basic network info for all available interfaces. It shows IP address, netmask, gateway and MAC address.
Left-button click moves to the next interface, right-button click calls ifup/ifdown scripts.
Please report bugs if you find any.
Left-button click moves to the next interface, right-button click calls ifup/ifdown scripts. These can be set with the -u and -d options. The %s variable is replaced with the interface name.
Example:
$ wmifinfo -i ppp0 -u "/sbin/ifup %s" -d "/sbin/ifdown %s"
(ifup/ifdown or the wmifinfo binaries should be suid root for this to work)
Led color Meaning
-------------------------------------------------------------------
red interface is down
yellow ifup/ifdown script is busy
dark green interface is up, no traffic
light green interface is up, and sending or receiving
<<lessLeft-button click moves to the next interface, right-button click calls ifup/ifdown scripts.
Please report bugs if you find any.
Left-button click moves to the next interface, right-button click calls ifup/ifdown scripts. These can be set with the -u and -d options. The %s variable is replaced with the interface name.
Example:
$ wmifinfo -i ppp0 -u "/sbin/ifup %s" -d "/sbin/ifdown %s"
(ifup/ifdown or the wmifinfo binaries should be suid root for this to work)
Led color Meaning
-------------------------------------------------------------------
red interface is down
yellow ifup/ifdown script is busy
dark green interface is up, no traffic
light green interface is up, and sending or receiving
Download (0.015MB)
Added: 2006-01-27 License: GPL (GNU General Public License) Price:
775 downloads
Math::Combinatorics 0.09
Math::Combinatorics is a Perl module that can perform combinations and permutations on lists. more>>
Math::Combinatorics is a Perl module that can perform combinations and permutations on lists.
SYNOPSIS
Available as an object oriented API.
use Math::Combinatorics;
my @n = qw(a b c);
my $combinat = Math::Combinatorics->new(count => 2,
data => [@n],
);
print "combinations of 2 from: ".join(" ",@n)."n";
print "------------------------".("--" x scalar(@n))."n";
while(my @combo = $combinat->next_combination){
print join( , @combo)."n";
}
print "n";
print "permutations of 3 from: ".join(" ",@n)."n";
print "------------------------".("--" x scalar(@n))."n";
while(my @permu = $combinat->next_permutation){
print join( , @permu)."n";
}
output:
Or available via exported functions permute, combine, and factorial.
use Math::Combinatorics;
my @n = qw(a b c);
print "combinations of 2 from: ".join(" ",@n)."n";
print "------------------------".("--" x scalar(@n))."n";
print join("n", map { join " ", @$_ } combine(2,@n)),"n";
print "n";
print "permutations of 3 from: ".join(" ",@n)."n";
print "------------------------".("--" x scalar(@n))."n";
print join("n", map { join " ", @$_ } permute(@n)),"n";
Output:
combinations of 2 from: a b c
------------------------------
a b
a c
b c
permutations of 3 from: a b c
------------------------------
a b c
a c b
b a c
b c a
c a b
c b a
Output from both types of calls is the same, but the object-oriented approach consumes much less memory for large sets.
<<lessSYNOPSIS
Available as an object oriented API.
use Math::Combinatorics;
my @n = qw(a b c);
my $combinat = Math::Combinatorics->new(count => 2,
data => [@n],
);
print "combinations of 2 from: ".join(" ",@n)."n";
print "------------------------".("--" x scalar(@n))."n";
while(my @combo = $combinat->next_combination){
print join( , @combo)."n";
}
print "n";
print "permutations of 3 from: ".join(" ",@n)."n";
print "------------------------".("--" x scalar(@n))."n";
while(my @permu = $combinat->next_permutation){
print join( , @permu)."n";
}
output:
Or available via exported functions permute, combine, and factorial.
use Math::Combinatorics;
my @n = qw(a b c);
print "combinations of 2 from: ".join(" ",@n)."n";
print "------------------------".("--" x scalar(@n))."n";
print join("n", map { join " ", @$_ } combine(2,@n)),"n";
print "n";
print "permutations of 3 from: ".join(" ",@n)."n";
print "------------------------".("--" x scalar(@n))."n";
print join("n", map { join " ", @$_ } permute(@n)),"n";
Output:
combinations of 2 from: a b c
------------------------------
a b
a c
b c
permutations of 3 from: a b c
------------------------------
a b c
a c b
b a c
b c a
c a b
c b a
Output from both types of calls is the same, but the object-oriented approach consumes much less memory for large sets.
Download (0.010MB)
Added: 2007-06-28 License: Perl Artistic License Price:
849 downloads
Embedix::ECD 0.09
Embedix::ECD is a Perl module with Embedix Component Descriptions as objects. more>>
Embedix::ECD is a Perl module with Embedix Component Descriptions as objects.
SYNOPSIS
instantiate from a file
my $ecd = Embedix::ECD->newFromFile(busybox.ecd);
my $other_ecd = Embedix::ECD->newFromFile(tinylogin.ecd);
access nodes
my $busybox = $ecd->System->Utilities->busybox;
build from scratch
my $server = Embedix::ECD::Group->new(name => Server);
my $www = Embedix::ECD::Group->new(name => WWW);
my $apache = Embedix::ECD::Component->new (
name => apache,
srpm => apache,
prompt => Include apache web server?,
help => The most popular http server on the internet,
);
$ecd->addChild($server);
$ecd->Server->addChild($www);
$ecd->Server->WWW->addChild($apache);
get/set attributes
my $srpm = $busybox->srpm();
$busybox->help(i am busybox of borg -- unix will be assimilated.);
$busybox->requires([
libc.so.6,
ld-linux.so.2,
skellinux,
]);
combine Embedix::ECD objects together
$ecd->mergeWith($other_ecd);
print as text
print $ecd->toString;
print as XML
use Embedix::ECD::XMLv1 qw(xml_from_cons);
print $ecd->toXML(shiftwidth => 4, dtd => yes);
my $cons = Embedix::ECD->consFromFile(minicom.ecd);
print xml_from_cons($cons);
Embedix::ECD allows one to represent ECD files as a tree of perl objects. One can construct objects by parsing an ECD file, or one can build an ECD object from scratch by combining instances of Embedix::ECD and its subclasses. These objects can then be turned back into ECD files via the toString() method.
ECD stands for Embedix Component Description, and its purpose is to contain meta-data regarding packages (aka components) in the Embedix distribution. ECD files contain much of the same data a .spec file does for an RPM. A major difference however is that ECD files do not contain building instructions whereas .spec files do. Another major difference between .spec files and ECD files is the structure. ECD files are hierarchically structured whereas .spec files are comparatively flat.
The ECD format reminds me of the syntax for Apache configuration files. Items are tag-delimited (like in XML) and attributes are found between these tags. Comments are written by prefixing them with /^s*#/. Unlike apache configurations, attribute names and values are separated by an "=" sign, whereas in apache the first token is the attribute name and everything after that (sans leading whitespace) and up to the end of the line is the attributes value. Also, unlike apache configurations, attributes may also be enclosed in tags, whereas in apache tags are used only to describe nodes.
ECD files look like pseudo-XML with shell-styled comments.
<<lessSYNOPSIS
instantiate from a file
my $ecd = Embedix::ECD->newFromFile(busybox.ecd);
my $other_ecd = Embedix::ECD->newFromFile(tinylogin.ecd);
access nodes
my $busybox = $ecd->System->Utilities->busybox;
build from scratch
my $server = Embedix::ECD::Group->new(name => Server);
my $www = Embedix::ECD::Group->new(name => WWW);
my $apache = Embedix::ECD::Component->new (
name => apache,
srpm => apache,
prompt => Include apache web server?,
help => The most popular http server on the internet,
);
$ecd->addChild($server);
$ecd->Server->addChild($www);
$ecd->Server->WWW->addChild($apache);
get/set attributes
my $srpm = $busybox->srpm();
$busybox->help(i am busybox of borg -- unix will be assimilated.);
$busybox->requires([
libc.so.6,
ld-linux.so.2,
skellinux,
]);
combine Embedix::ECD objects together
$ecd->mergeWith($other_ecd);
print as text
print $ecd->toString;
print as XML
use Embedix::ECD::XMLv1 qw(xml_from_cons);
print $ecd->toXML(shiftwidth => 4, dtd => yes);
my $cons = Embedix::ECD->consFromFile(minicom.ecd);
print xml_from_cons($cons);
Embedix::ECD allows one to represent ECD files as a tree of perl objects. One can construct objects by parsing an ECD file, or one can build an ECD object from scratch by combining instances of Embedix::ECD and its subclasses. These objects can then be turned back into ECD files via the toString() method.
ECD stands for Embedix Component Description, and its purpose is to contain meta-data regarding packages (aka components) in the Embedix distribution. ECD files contain much of the same data a .spec file does for an RPM. A major difference however is that ECD files do not contain building instructions whereas .spec files do. Another major difference between .spec files and ECD files is the structure. ECD files are hierarchically structured whereas .spec files are comparatively flat.
The ECD format reminds me of the syntax for Apache configuration files. Items are tag-delimited (like in XML) and attributes are found between these tags. Comments are written by prefixing them with /^s*#/. Unlike apache configurations, attribute names and values are separated by an "=" sign, whereas in apache the first token is the attribute name and everything after that (sans leading whitespace) and up to the end of the line is the attributes value. Also, unlike apache configurations, attributes may also be enclosed in tags, whereas in apache tags are used only to describe nodes.
ECD files look like pseudo-XML with shell-styled comments.
Download (0.040MB)
Added: 2006-09-26 License: Perl Artistic License Price:
1124 downloads
Games::3D 0.09
Games::3D is a package containing an object system for (not only) 3D games. more>>
Games::3D is a package containing an object system for (not only) 3D games.
SYNOPSIS
use Games::3D::World;
my $world = Games::3D::World->new();
$world->save_to_file( $filename );
my $loaded = Games::3D::world->load_from_file( $filename );
my $thing1 = $world->add ( Games::3D::Thingy->new( ... ) );
my $thing2 = $world->add ( Games::3D::Thingy->new( ... ) );
$world->link($thing1, $thing2);
Games::3D::World provides you with a container class that will contain every object in your game object system. This are primarily objects that have states, change these states and need to announce the states to other objects.
The Games::3D::World container also enables you to save and restore snapshots of your objects system.
Basic things that you object system contains are derived from a class called Games::3D::Thingy. These can represent physical objects (buttons, levers, doors, lights etc) as well as virtual objects (trigger, sensors, links, markers, sound sources etc).
You can link Thingys together, either directly or via Games::3D::Links. The links have some more features than direct linking, which are explained below.
This package also provides you with Games::3D::Sensor, a class for objects that sense state changes and act upon them. Or not, depending on the sensor. Sensors are primarily used to watch for certain conditions and then act when they are met. Examples are the death of an object, values that go below a certain threshold etc.
State changes are transported in the object system with signals.
<<lessSYNOPSIS
use Games::3D::World;
my $world = Games::3D::World->new();
$world->save_to_file( $filename );
my $loaded = Games::3D::world->load_from_file( $filename );
my $thing1 = $world->add ( Games::3D::Thingy->new( ... ) );
my $thing2 = $world->add ( Games::3D::Thingy->new( ... ) );
$world->link($thing1, $thing2);
Games::3D::World provides you with a container class that will contain every object in your game object system. This are primarily objects that have states, change these states and need to announce the states to other objects.
The Games::3D::World container also enables you to save and restore snapshots of your objects system.
Basic things that you object system contains are derived from a class called Games::3D::Thingy. These can represent physical objects (buttons, levers, doors, lights etc) as well as virtual objects (trigger, sensors, links, markers, sound sources etc).
You can link Thingys together, either directly or via Games::3D::Links. The links have some more features than direct linking, which are explained below.
This package also provides you with Games::3D::Sensor, a class for objects that sense state changes and act upon them. Or not, depending on the sensor. Sensors are primarily used to watch for certain conditions and then act when they are met. Examples are the death of an object, values that go below a certain threshold etc.
State changes are transported in the object system with signals.
Download (0.032MB)
Added: 2006-10-02 License: Perl Artistic License Price:
1124 downloads
File::Sync 0.09
File::Sync is a Perl access to fsync() and sync() function calls. more>>
File::Sync is a Perl access to fsync() and sync() function calls.
SYNOPSIS
use File::Sync qw(fsync sync);
fsync(*FILEHANDLE) or die "fsync: $!";
sync();
use File::Sync qw(fsync);
use IO::File;
$fh = IO::File->new("> /tmp/foo")
or die "new IO::File: $!";
...
fsync($fh) or die "fsync: $!";
The fsync() function takes a Perl file handle as its only argument, and passes its fileno() to the C function fsync(). It returns undef on failure, or true on success.
The fsync_fd() function is used internally by fsync(); it takes a file descriptor as its only argument.
The sync() function is identical to the C function sync().
This module does not export any methods by default, but fsync() is made available as a method of the FileHandle and IO::Handle classes.
<<lessSYNOPSIS
use File::Sync qw(fsync sync);
fsync(*FILEHANDLE) or die "fsync: $!";
sync();
use File::Sync qw(fsync);
use IO::File;
$fh = IO::File->new("> /tmp/foo")
or die "new IO::File: $!";
...
fsync($fh) or die "fsync: $!";
The fsync() function takes a Perl file handle as its only argument, and passes its fileno() to the C function fsync(). It returns undef on failure, or true on success.
The fsync_fd() function is used internally by fsync(); it takes a file descriptor as its only argument.
The sync() function is identical to the C function sync().
This module does not export any methods by default, but fsync() is made available as a method of the FileHandle and IO::Handle classes.
Download (0.004MB)
Added: 2006-06-29 License: Perl Artistic License Price:
1213 downloads
VCShell 0.09
VCShell is a command line interface for VCS::Lite::Repository. more>>
VCShell is a command line interface for VCS::Lite::Repository.
SYNOPSIS
B< add > element|repository [element|repository...]
B< remove > name [name...]
B< ci >|check_in name [name...]
B< co >|check_out parent_repository
B< commit >
B< update >
B< cd > repository
B< fetch > name@@gen [>outfile]
B< diff > file1[@@gen1] [file2[@@gen2]] [>outfile]
VCShell provides a command line interface to the VCS Lite Repository. This aims to be usable by non-Perl programmers, as it provides a wrapper to the functionality in the module.
COMMANDS
add
The add command adds something to a repository: an element or a repository. If the parameter given is a directory, it makes it a repository, otherwise an element. An empty file is created for the element if none exists.
remove
Remove breaks the association between a repository and something it contains. It does not delete any files.
ci
This command is used to check in changes to one or more elements and repositories. Each repository checked in is also recursively checked in.
clone
This makes a clone of one repository into another, and recursively for everything in it. The new repository contains a parent link which points at the original.
commit
If the repository is a clone of a parent repository, this propagates any changes to the parent. Note, a check in (ci) is needed on the parent, for this change to be applied.
update
This command is used to apply any changes that have happened to the parent. Three way merging occurs for any change that has happened in the mean time.
diff
This command outputs a udiff listing for two generations of an element, or for two different elements. The default generation used is the latest, and the default generation for the "from" file is the predecessor to the "to" generation if comparing the same element.
The output is in diff -u format.
<<lessSYNOPSIS
B< add > element|repository [element|repository...]
B< remove > name [name...]
B< ci >|check_in name [name...]
B< co >|check_out parent_repository
B< commit >
B< update >
B< cd > repository
B< fetch > name@@gen [>outfile]
B< diff > file1[@@gen1] [file2[@@gen2]] [>outfile]
VCShell provides a command line interface to the VCS Lite Repository. This aims to be usable by non-Perl programmers, as it provides a wrapper to the functionality in the module.
COMMANDS
add
The add command adds something to a repository: an element or a repository. If the parameter given is a directory, it makes it a repository, otherwise an element. An empty file is created for the element if none exists.
remove
Remove breaks the association between a repository and something it contains. It does not delete any files.
ci
This command is used to check in changes to one or more elements and repositories. Each repository checked in is also recursively checked in.
clone
This makes a clone of one repository into another, and recursively for everything in it. The new repository contains a parent link which points at the original.
commit
If the repository is a clone of a parent repository, this propagates any changes to the parent. Note, a check in (ci) is needed on the parent, for this change to be applied.
update
This command is used to apply any changes that have happened to the parent. Three way merging occurs for any change that has happened in the mean time.
diff
This command outputs a udiff listing for two generations of an element, or for two different elements. The default generation used is the latest, and the default generation for the "from" file is the predecessor to the "to" generation if comparing the same element.
The output is in diff -u format.
Download (0.026MB)
Added: 2007-07-09 License: Perl Artistic License Price:
840 downloads
Data::Secs2 0.09
Data::Secs2 is a Perl module to pack, unpack, format, transform from Perl data SEMI E5-94 nested data. more>>
Data::Secs2 is a Perl module to pack, unpack, format, transform from Perl data SEMI E5-94 nested data.
SYNOPSIS
#####
# Subroutine interface
#
use Data::Secs2 qw(arrayify config listify neuterify numberify perlify
perl_typify secsify secs_elementify stringify textify transify);
@array = arrayify($ref, @options);
$old_value = config( $option );
$old_value = config( $option => $new_value);
$body = secs_elementify($format, $cells, @options);
@secs_obj = listify(@vars);
@secs_obj = neuterify($binary_secs, @options);
@vars = perlify(@secs_obj, @options);
$ref = perl_typify(@array, @options);
$ascii_secs = secsify( @secs_obj, @options);
$binary_secs = secsify( @secs_obj, type => binary);
$string = stringify(@arg, [@options]);
@secs_obj = transify($acsii_secs, @options);
#####
# Class, Object interface
#
# For class interface, use Data::Secs2 instead of $self
# use Data::Secs2;
#
$secs2 = Data::Secs2 # uses built-in config object
$secs2 = new Data::Secs2( @options );
@array = secs2->arrayify( $ref, @options );
$old_value = secs2->secs_config( $option);
$old_value = secs2->secs_config( $option => $new_value);
$body = secs2->secs_elementify($format, $cells, @options);
@secs_obj = secs2->listify(@vars, @options);
@secs_obj = secs2->neuterify($binary_secs, @options);
@vars = secs2->perlify(@secs_obj, @options);
$ref = secs2->perl_typify(@array, @options);
$ascii_secs = secs2->secsify( @secs_obj, @options);
$binary_secs = secs2->secsify( @secs_obj, type => binary);
$body = secs2->stringify( @arg );
@secs_obj = secs2->transify($acsii_secs, @options);
Generally, if a subroutine will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}. If a subroutine will process an array reference, @options, [@options], that subroutine will also process a hash reference, %options, {@options}. See the description for a subroutine for details and exceptions.
<<lessSYNOPSIS
#####
# Subroutine interface
#
use Data::Secs2 qw(arrayify config listify neuterify numberify perlify
perl_typify secsify secs_elementify stringify textify transify);
@array = arrayify($ref, @options);
$old_value = config( $option );
$old_value = config( $option => $new_value);
$body = secs_elementify($format, $cells, @options);
@secs_obj = listify(@vars);
@secs_obj = neuterify($binary_secs, @options);
@vars = perlify(@secs_obj, @options);
$ref = perl_typify(@array, @options);
$ascii_secs = secsify( @secs_obj, @options);
$binary_secs = secsify( @secs_obj, type => binary);
$string = stringify(@arg, [@options]);
@secs_obj = transify($acsii_secs, @options);
#####
# Class, Object interface
#
# For class interface, use Data::Secs2 instead of $self
# use Data::Secs2;
#
$secs2 = Data::Secs2 # uses built-in config object
$secs2 = new Data::Secs2( @options );
@array = secs2->arrayify( $ref, @options );
$old_value = secs2->secs_config( $option);
$old_value = secs2->secs_config( $option => $new_value);
$body = secs2->secs_elementify($format, $cells, @options);
@secs_obj = secs2->listify(@vars, @options);
@secs_obj = secs2->neuterify($binary_secs, @options);
@vars = secs2->perlify(@secs_obj, @options);
$ref = secs2->perl_typify(@array, @options);
$ascii_secs = secs2->secsify( @secs_obj, @options);
$binary_secs = secs2->secsify( @secs_obj, type => binary);
$body = secs2->stringify( @arg );
@secs_obj = secs2->transify($acsii_secs, @options);
Generally, if a subroutine will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}. If a subroutine will process an array reference, @options, [@options], that subroutine will also process a hash reference, %options, {@options}. See the description for a subroutine for details and exceptions.
Download (0.096MB)
Added: 2007-02-15 License: Perl Artistic License Price:
981 downloads
Tk::ToolBar 0.09
Tk::ToolBar is a toolbar widget for Perl/Tk. more>>
Tk::ToolBar is a toolbar widget for Perl/Tk.
SYNOPSIS
use Tk;
use Tk::ToolBar;
my $mw = new MainWindow;
my $tb = $mw->ToolBar(qw/-movable 1 -side top
-indicatorcolor blue/);
$tb->ToolButton (-text => Button,
-tip => tool tip,
-command => sub { print "hin" });
$tb->ToolLabel (-text => A Label);
$tb->Label (-text => Another Label);
$tb->ToolLabEntry(-label => A LabEntry,
-labelPack => [-side => "left",
-anchor => "w"]);
my $tb2 = $mw->ToolBar;
$tb2->ToolButton(-image => navback22,
-tip => back,
-command => &back);
$tb2->ToolButton(-image => navforward22,
-tip => forward,
-command => &forward);
$tb2->separator;
$tb2->ToolButton(-image => navhome22,
-tip => home,
-command => &home);
$tb2->ToolButton(-image => actreload22,
-tip => reload,
-command => &reload);
MainLoop;
This module implements a dockable toolbar. It is in the same spirit as the "short-cut" toolbars found in most major applications, such as most web browsers and text editors (where you find the "back" or "save" and other shortcut buttons).
Buttons of any type (regular, menu, check, radio) can be created inside this widget. You can also create Label, Entry and LabEntry widgets. Moreover, the ToolBar itself can be made dockable, such that it can be dragged to any edge of your window. Dragging is done in "real-time" so that you can see the contents of your ToolBar as you are dragging it. Furthermore, if you are close to a stickable edge, a visual indicator will show up along that edge to guide you.
ToolBars can be made "floatable" such that if they are dragged beyond their associated window, they will detach and float on the desktop. Also, multiple ToolBars are embeddable inside each other.
If you drag a ToolBar to within 15 pixels of an edge, it will stick to that edge. If the ToolBar is further than 15 pixels away from an edge and still inside the window, but you release it over another ToolBar widget, then it will be embedded inside the second ToolBar. You can "un-embed" an embedded ToolBar simply by dragging it out. You can change the 15 pixel limit using the -close option.
Various icons are built into the Tk::ToolBar widget. Those icons can be used as images for ToolButtons (see "SYNOPSIS"). A demo program is bundled with the module that should be available under the User Contributed Demonstrations when you run the widget program. Run it to see a list of the available images.
Tk::ToolBar attempts to use Tk::CursorControl if its already installed on the system. You can further control this using the -cursorcontrol option. See "PREREQUISITES".
The ToolBar is supposed to be created as a child of a Toplevel (MainWindow is a Toplevel widget) or a Frame. You are free to experiment otherwise, but expect the unexpected.
<<lessSYNOPSIS
use Tk;
use Tk::ToolBar;
my $mw = new MainWindow;
my $tb = $mw->ToolBar(qw/-movable 1 -side top
-indicatorcolor blue/);
$tb->ToolButton (-text => Button,
-tip => tool tip,
-command => sub { print "hin" });
$tb->ToolLabel (-text => A Label);
$tb->Label (-text => Another Label);
$tb->ToolLabEntry(-label => A LabEntry,
-labelPack => [-side => "left",
-anchor => "w"]);
my $tb2 = $mw->ToolBar;
$tb2->ToolButton(-image => navback22,
-tip => back,
-command => &back);
$tb2->ToolButton(-image => navforward22,
-tip => forward,
-command => &forward);
$tb2->separator;
$tb2->ToolButton(-image => navhome22,
-tip => home,
-command => &home);
$tb2->ToolButton(-image => actreload22,
-tip => reload,
-command => &reload);
MainLoop;
This module implements a dockable toolbar. It is in the same spirit as the "short-cut" toolbars found in most major applications, such as most web browsers and text editors (where you find the "back" or "save" and other shortcut buttons).
Buttons of any type (regular, menu, check, radio) can be created inside this widget. You can also create Label, Entry and LabEntry widgets. Moreover, the ToolBar itself can be made dockable, such that it can be dragged to any edge of your window. Dragging is done in "real-time" so that you can see the contents of your ToolBar as you are dragging it. Furthermore, if you are close to a stickable edge, a visual indicator will show up along that edge to guide you.
ToolBars can be made "floatable" such that if they are dragged beyond their associated window, they will detach and float on the desktop. Also, multiple ToolBars are embeddable inside each other.
If you drag a ToolBar to within 15 pixels of an edge, it will stick to that edge. If the ToolBar is further than 15 pixels away from an edge and still inside the window, but you release it over another ToolBar widget, then it will be embedded inside the second ToolBar. You can "un-embed" an embedded ToolBar simply by dragging it out. You can change the 15 pixel limit using the -close option.
Various icons are built into the Tk::ToolBar widget. Those icons can be used as images for ToolButtons (see "SYNOPSIS"). A demo program is bundled with the module that should be available under the User Contributed Demonstrations when you run the widget program. Run it to see a list of the available images.
Tk::ToolBar attempts to use Tk::CursorControl if its already installed on the system. You can further control this using the -cursorcontrol option. See "PREREQUISITES".
The ToolBar is supposed to be created as a child of a Toplevel (MainWindow is a Toplevel widget) or a Frame. You are free to experiment otherwise, but expect the unexpected.
Download (0.055MB)
Added: 2006-06-12 License: Perl Artistic License Price:
1232 downloads
XMMS Announcer 0.09.5
XMMS Announcer is a simple utility that neatly prints the current track playing in XMMS. more>>
XMMS Announcer is a simple utility that neatly prints the current track playing in XMMS. XMMS Announcer has optional command line arguments that allow for more detailed information about the track.
The unique feature is that it allows for an easily customizable output string format, which is done by using the -f switch on the command line.
<<lessThe unique feature is that it allows for an easily customizable output string format, which is done by using the -f switch on the command line.
Download (0.007MB)
Added: 2006-04-11 License: GPL (GNU General Public License) Price:
1291 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above moosic 0.09 search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed