target
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 985
Target 1.0
Target is an AJAX-enabled application that allows users to create and track one or more target areas. more>>
Target project is an AJAX-enabled application that allows users to create and track one or more target areas.
The target area can then be resized and moved to new locations on the image. With a right-click, the movement and resize history can be replayed with DHTML animation and AJAX.
<<lessThe target area can then be resized and moved to new locations on the image. With a right-click, the movement and resize history can be replayed with DHTML animation and AJAX.
Download (0.28MB)
Added: 2006-10-06 License: GPL (GNU General Public License) Price:
1113 downloads
Mtp Target 1.2.2
Mtp Target is a Monkey Target clone (one of the six mini-games from the video game : Super Monkey Ball). more>>
Mtp Target is a Monkey Target clone (one of the six mini-games from the video game : Super Monkey Ball).
After rolling your pingoo ball down a giant ramp, your goal is to hit a target as accurately as possible. You can play on Internet or LAN up to 16 players simultaneously.
Mtp Target is entirely under GNU GPL License. Both client and server run under Windows and GNU/Linux.
<<lessAfter rolling your pingoo ball down a giant ramp, your goal is to hit a target as accurately as possible. You can play on Internet or LAN up to 16 players simultaneously.
Mtp Target is entirely under GNU GPL License. Both client and server run under Windows and GNU/Linux.
Download (12.2MB)
Added: 2006-08-28 License: GPL (GNU General Public License) Price:
671 downloads
Stargun 0.2
Stargun is a 2D space shooter game. more>>
Stargun project is a 2D space shooter game.
Stargun is a space shooter, vertical scroller game. Its platform independent (or at least it is the objetive). The target OS are Windows and Linux. There are plans to port Stargun to BeOs, FreeBSD and Amiga.
Stargun is written in C++ and uses SDL library.
This project is under GPL lisence.
Enhancements:
- Music & sound added
- Joystick support
- Levels support
- some bugs fixed
<<lessStargun is a space shooter, vertical scroller game. Its platform independent (or at least it is the objetive). The target OS are Windows and Linux. There are plans to port Stargun to BeOs, FreeBSD and Amiga.
Stargun is written in C++ and uses SDL library.
This project is under GPL lisence.
Enhancements:
- Music & sound added
- Joystick support
- Levels support
- some bugs fixed
Download (0.43MB)
Added: 2006-12-07 License: GPL (GNU General Public License) Price:
1054 downloads
FireAnt 1.0
FireAnt is an Eclipse plugin for modeling complex remote deployment and configuration processes for EJBs. more>>
FireAnt is an Eclipse plugin for modeling complex remote deployment and configuration processes for EJBs.
It allows developers to model the deployment and execution of groups of packages and configuration scripts on remote targets.
After modeling a deployment plan, FireAnts runtime infrastructure SSHs into each target, copies over the specified files, deploys the EJBs and Webapps, runs any required deployment scripts, and then cleans the staging environment.
<<lessIt allows developers to model the deployment and execution of groups of packages and configuration scripts on remote targets.
After modeling a deployment plan, FireAnts runtime infrastructure SSHs into each target, copies over the specified files, deploys the EJBs and Webapps, runs any required deployment scripts, and then cleans the staging environment.
Download (6.7MB)
Added: 2005-09-26 License: GPL (GNU General Public License) Price:
1990 downloads
VK Tafe 0.8g
VK Tafe is a program that parses and analyzes MPEG-2 transport streams. more>>
VK Tafe is a program that parses and analyzes MPEG-2 transport streams (e.g., DVB, ATSC, etc.).
Enhancements:
vk_tafe
- UI changes to PCR Analysis screen
- New PTS/DTS graph (graphs PTS/DTS values against current PCR)
- UI log for STD buffer analysis
- Updated HTML documentation
- Target build platform updated to a "modern" distro -- SuSE 10. The older Mandrake version is frozen at version 0.8f which is still included in the VK-Tools packets
- Updated win32 port
view_knot_dump
- UI no longer depends on icons subdirectory to properly display
- If local .view_knot_view config does not specify the location of vk_tafe we assume its somewhere in the PATH and try to launc it
- Updated HTML documentation
- Target build platform updated to a "modern" distro -- SuSE 10. The older Mandrake version is frozen at version 0.8f which is still included in the VK-Tools packets
- Updated win32 port
- Removed Plugins. Theyve only been broken for 5 years now :)
view_knot_viewer
- No changes
<<lessEnhancements:
vk_tafe
- UI changes to PCR Analysis screen
- New PTS/DTS graph (graphs PTS/DTS values against current PCR)
- UI log for STD buffer analysis
- Updated HTML documentation
- Target build platform updated to a "modern" distro -- SuSE 10. The older Mandrake version is frozen at version 0.8f which is still included in the VK-Tools packets
- Updated win32 port
view_knot_dump
- UI no longer depends on icons subdirectory to properly display
- If local .view_knot_view config does not specify the location of vk_tafe we assume its somewhere in the PATH and try to launc it
- Updated HTML documentation
- Target build platform updated to a "modern" distro -- SuSE 10. The older Mandrake version is frozen at version 0.8f which is still included in the VK-Tools packets
- Updated win32 port
- Removed Plugins. Theyve only been broken for 5 years now :)
view_knot_viewer
- No changes
Download (0.012MB)
Added: 2006-01-18 License: Freely Distributable Price:
1375 downloads
TinyMake 0.06
TinyMake is a minimalist build language, similar in purpose to make and ant. more>>
TinyMake is a minimalist build language, similar in purpose to make and ant.
SYNOPSIS
use TinyMake :all;
# a file statement without a rule is like a symbolic target
file all => ["codeGen", "compile", "dataLoad", "test"];
file codeGen => ["database.spec"], sub {
# generate code here
sh "touch $target";
} ;
file compile => ["codeGen"], sub {
# compile code here
sh "touch $target";
} ;
file dataLoad => ["codeGen"], sub {
# load data here
sh "touch $target"
} ;
file test => ["compile", "dataLoad"], sub {
# test code here
sh "touch $target";
} ;
# a file statement without prerequisites will be executed
# if the target doesnt exist.
file clean => sub {
# perform cleanup here
sh "rm compile codeGen dataLoad test"
} ;
make @ARGV
This Perl Module allows you to define file-based dependencies similar to how make works.Rather than placing the build rules in a separate Makefile or build.xml, the build rules are declared using standard Perl syntax. TinyMake is effectively an inline domain-specific language. Using make you might write a makefile that looks like this...
test: compile dataLoad
# test
touch test
codeGen: database.spec
# generate code
touch codeGen
compile: codeGen
# compile code
touch compile
dataLoad: codeGen
# load data
touch dataLoad
database.spec: # source file
The equivalent perl code using TinyMake would look like this...
use TinyMake :all;
# some perl code
.
.
.
file test => ["compile","dataLoad"], sub { # test
`touch test`;
} ;
file codeGen => "database.spec", sub { # generate code
`touch codeGen`;
} ;
# some more perl code
.
.
.
file compile => "codeGen", sub { # compile code
`touch compile`;
} ;
file dataload => "codeGen", sub { # load data
`touch dataLoad`;
} ;
make @ARGV;
<<lessSYNOPSIS
use TinyMake :all;
# a file statement without a rule is like a symbolic target
file all => ["codeGen", "compile", "dataLoad", "test"];
file codeGen => ["database.spec"], sub {
# generate code here
sh "touch $target";
} ;
file compile => ["codeGen"], sub {
# compile code here
sh "touch $target";
} ;
file dataLoad => ["codeGen"], sub {
# load data here
sh "touch $target"
} ;
file test => ["compile", "dataLoad"], sub {
# test code here
sh "touch $target";
} ;
# a file statement without prerequisites will be executed
# if the target doesnt exist.
file clean => sub {
# perform cleanup here
sh "rm compile codeGen dataLoad test"
} ;
make @ARGV
This Perl Module allows you to define file-based dependencies similar to how make works.Rather than placing the build rules in a separate Makefile or build.xml, the build rules are declared using standard Perl syntax. TinyMake is effectively an inline domain-specific language. Using make you might write a makefile that looks like this...
test: compile dataLoad
# test
touch test
codeGen: database.spec
# generate code
touch codeGen
compile: codeGen
# compile code
touch compile
dataLoad: codeGen
# load data
touch dataLoad
database.spec: # source file
The equivalent perl code using TinyMake would look like this...
use TinyMake :all;
# some perl code
.
.
.
file test => ["compile","dataLoad"], sub { # test
`touch test`;
} ;
file codeGen => "database.spec", sub { # generate code
`touch codeGen`;
} ;
# some more perl code
.
.
.
file compile => "codeGen", sub { # compile code
`touch compile`;
} ;
file dataload => "codeGen", sub { # load data
`touch dataLoad`;
} ;
make @ARGV;
Download (0.010MB)
Added: 2007-06-06 License: Perl Artistic License Price:
873 downloads
reflect 1.0.1
reflect is a symlink-style package management tool similar to stow. more>>
reflect is a symlink-style package management tool similar to depot, stow, graft, epkg, etc. Unlike these, it has much less prerequisites, in that it only requires bash and coreutils. Configuration is per-package, and multiple target directories are permitted.
Main features:
- reflect is written in bash. Currently it depends on the following to be installed: cd, mkdir, ls, ln, cmp, rm, md5sum, and, well, bash.
- reflect will only delete symbolic links, and only those which belong to the package reflect is currently working on.
- All configuration is per-package, in a file /pack/ /reflect.conf.
- It is possible to configure (in reflect.conf) multiple target directories for a package.
<<lessMain features:
- reflect is written in bash. Currently it depends on the following to be installed: cd, mkdir, ls, ln, cmp, rm, md5sum, and, well, bash.
- reflect will only delete symbolic links, and only those which belong to the package reflect is currently working on.
- All configuration is per-package, in a file /pack/ /reflect.conf.
- It is possible to configure (in reflect.conf) multiple target directories for a package.
Download (0.016MB)
Added: 2005-04-07 License: GPL (GNU General Public License) Price:
1661 downloads
Content Area Focus 0.1
Content Area Focus is an extension used to solve the content area focus loss. more>>
Content Area Focus is an extension used to solve the content area focus loss.
Target audience: those who are mostly using the keyboard to navigate around and switch between tabs; frequently they encounter situations in which the content area doesnt have focus.
Method: just giving focus to the content area for any "regular" keystrokes made when the main-window is in focus.
<<lessTarget audience: those who are mostly using the keyboard to navigate around and switch between tabs; frequently they encounter situations in which the content area doesnt have focus.
Method: just giving focus to the content area for any "regular" keystrokes made when the main-window is in focus.
Download (0.001MB)
Added: 2007-04-03 License: MPL (Mozilla Public License) Price:
937 downloads
Link Alert 0.7.2
Link Alert is a Firefox extension that changes the cursor to indicate the target of a link. more>>
Link Alert is a Firefox extension that changes the cursor to indicate the target of a link.
Highlights links to the following:
-New Windows
-Secure Sites
-Email Links
-Javascript
-Word Documents
-Excel Spreadsheets
-PDF Files
-Zip Files
-Applications
-Text Files
-Images
-RSS Feeds
-AIM: Links
-and more...
<<lessHighlights links to the following:
-New Windows
-Secure Sites
-Email Links
-Javascript
-Word Documents
-Excel Spreadsheets
-PDF Files
-Zip Files
-Applications
-Text Files
-Images
-RSS Feeds
-AIM: Links
-and more...
Download (0.012MB)
Added: 2007-07-16 License: MPL (Mozilla Public License) Price:
837 downloads
Garbure 20050105
Garbure is a collection of dedicated platforms proposed as GNU/Linux distributions. more>>
Garbure is a collection of dedicated platforms proposed as GNU/Linux distributions. Each distribution provides you with carefully selected tools for a specific target domain, and is completed with examples and documentation.
The set of platforms included in Garbure forms an entity, but each distribution works also on its own. They complement each other like tools in a toolbox or volumes of an encyclopedia.
Tools, documentation and examples are chosen, tested and if necessary created by people active in the target domain.
All elements are arranged in the same way for each distribution. If you are for example used to work with the ratatouille distribution for animation movies, you will be able to use burek dedicated to audiovisual performance without much extra effort. In addition, it will be easy to advise and demonstrate a distribution you are not familiar with to a friend who is working in another domain.
These distributions are intended to be used as work station. The installation and distribution media is the LiveCD, making it also useful for demonstration purposes, promotion, occasional usage or rescue system. Meta-package installation is planned.
<<lessThe set of platforms included in Garbure forms an entity, but each distribution works also on its own. They complement each other like tools in a toolbox or volumes of an encyclopedia.
Tools, documentation and examples are chosen, tested and if necessary created by people active in the target domain.
All elements are arranged in the same way for each distribution. If you are for example used to work with the ratatouille distribution for animation movies, you will be able to use burek dedicated to audiovisual performance without much extra effort. In addition, it will be easy to advise and demonstrate a distribution you are not familiar with to a friend who is working in another domain.
These distributions are intended to be used as work station. The installation and distribution media is the LiveCD, making it also useful for demonstration purposes, promotion, occasional usage or rescue system. Meta-package installation is planned.
Download (0.68MB)
Added: 2005-09-01 License: GPL (GNU General Public License) Price:
848 downloads
Make 1.00
Make is a Perl module for processing makefiles. more>>
Make is a Perl module for processing makefiles.
SYNOPSIS
require Make;
my $make = Make->new(...);
$make->parse($file);
$make->Script(@ARGV)
$make->Make(@ARGV)
$make->Print(@ARGV)
my $targ = $make->Target($name);
$targ->colon([dependancy...],[command...]);
$targ->dolon([dependancy...],[command...]);
my @depends = $targ->colon->depend;
my @commands = $targ->colon->command;
Make->new creates an object if new(Makefile => $file) is specified then it is parsed. If not the usual makefile Makefile sequence is used. (If GNU => 1 is passed to new then GNUmakefile is looked for first.)
$make->Make(target...) makes the target(s) specified (or the first real target in the makefile).
$make->Print can be used to print to current selected stream a form of the makefile with all variables expanded.
$make->Script(target...) can be used to print to current selected stream the equivalent bourne shell script that a make would perform i.e. the output of make -n.
There are other methods (used by parse) which can be used to add and manipulate targets and their dependants. There is a hierarchy of classes which is still evolving. These classes and their methods will be documented when they are a little more stable.
The syntax of makefile accepted is reasonably generic, but I have not re-read any documentation yet, rather I have implemented my own mental model of how make works (then fixed it...).
In addition to traditional
.c.o :
$(CC) -c ...
GNU makes pattern rules e.g.
%.o : %.c
$(CC) -c ...
Likewise a subset of GNU makes $(function arg...) syntax is supported.
Via pmake Make has built perl/Tk from the MakeMaker generated Makefiles...
<<lessSYNOPSIS
require Make;
my $make = Make->new(...);
$make->parse($file);
$make->Script(@ARGV)
$make->Make(@ARGV)
$make->Print(@ARGV)
my $targ = $make->Target($name);
$targ->colon([dependancy...],[command...]);
$targ->dolon([dependancy...],[command...]);
my @depends = $targ->colon->depend;
my @commands = $targ->colon->command;
Make->new creates an object if new(Makefile => $file) is specified then it is parsed. If not the usual makefile Makefile sequence is used. (If GNU => 1 is passed to new then GNUmakefile is looked for first.)
$make->Make(target...) makes the target(s) specified (or the first real target in the makefile).
$make->Print can be used to print to current selected stream a form of the makefile with all variables expanded.
$make->Script(target...) can be used to print to current selected stream the equivalent bourne shell script that a make would perform i.e. the output of make -n.
There are other methods (used by parse) which can be used to add and manipulate targets and their dependants. There is a hierarchy of classes which is still evolving. These classes and their methods will be documented when they are a little more stable.
The syntax of makefile accepted is reasonably generic, but I have not re-read any documentation yet, rather I have implemented my own mental model of how make works (then fixed it...).
In addition to traditional
.c.o :
$(CC) -c ...
GNU makes pattern rules e.g.
%.o : %.c
$(CC) -c ...
Likewise a subset of GNU makes $(function arg...) syntax is supported.
Via pmake Make has built perl/Tk from the MakeMaker generated Makefiles...
Download (0.012MB)
Added: 2007-05-09 License: Perl Artistic License Price:
944 downloads
GenIP 1.0
GenIP is a small utility, based on the NMap target specification code, for quickly and easily generating lists of IP addresses. more>>
GenIP is a small utility, based on the NMap target specification code, for quickly and easily generating lists of IP addresses.
Usage:
genip [ -h ] [ -i filename ] [ < target-spec > ... ]
genip -r < ipaddress > < ipaddress >
Options:
-h
Display uage information.
-i
Read target specifications from the give filename. If a filename of "-" used, target specifications are read from standard in. Target specifications read from input files are processed in NMap mode regardless of the presence of the -r option.
-r
Specify range mode (see below).
Modes:
GenIP has two modes of operation that are detailed below:
NMap Mode (Default)
In this mode genip will expand all target specifications listed on the command line. Since genip is essentially just the NMap target parsing code it functions in exactly the same way. Here is what the NMap documentation has to say about target specification:
Everything that isnt an option (or option argument) is treated as a target host specification. The simplest case is listing single hostnames or IP addresses on the command line. If you want to scan a subnet of IP addresses, you can append /mask to the hostname or IP address. mask must be between 0 (scan the whole Internet) and 32 (scan the single host specified). Use /24 to scan a class "C" address and /16 for a class "B". There is also a more powerful notation which lets you specify an IP address using lists/ranges for each element. Thus you can scan the whole class "B" network 192.168.*.* by specifying "192.168.*.*" or "192.168.0-255.0-255" or even "192.168.1-50,51-255.1,2,3,4,5-255". And of course you can use the mask notation: "192.168.0.0/16". These are all equivalent. If you use asterisks ("*"), remember that most shells require you to escape them with back slashes or protect them with quotes.
Range Mode
In this mode two (and only two!) IP addresses must be specified, in dotted quad notation, and the output is all the addresses between the two (inclusive). This mode can be used to cross class boundaries.
Example:
In its most basic form genip simply echos the IP addresses listed on the command line:
> genip 10.1.1.1 10.3.4.5
10.1.1.1
10.3.4.5
By use one of the many expansion methods detailed above a large number of IP addresses can be generated from simple command line specifications:
> genip 10.1.1.1-3
10.1.2.0
10.1.2.1
10.1.2.2
By selecting range mode (with the use of the -r flag) it is a simple matter to generate address lists that cross class boundaries:
> genip -r 10.1.1.254 10.1.2.2
10.1.1.254
10.1.1.255
10.1.2.0
10.1.2.1
10.1.2.2
<<lessUsage:
genip [ -h ] [ -i filename ] [ < target-spec > ... ]
genip -r < ipaddress > < ipaddress >
Options:
-h
Display uage information.
-i
Read target specifications from the give filename. If a filename of "-" used, target specifications are read from standard in. Target specifications read from input files are processed in NMap mode regardless of the presence of the -r option.
-r
Specify range mode (see below).
Modes:
GenIP has two modes of operation that are detailed below:
NMap Mode (Default)
In this mode genip will expand all target specifications listed on the command line. Since genip is essentially just the NMap target parsing code it functions in exactly the same way. Here is what the NMap documentation has to say about target specification:
Everything that isnt an option (or option argument) is treated as a target host specification. The simplest case is listing single hostnames or IP addresses on the command line. If you want to scan a subnet of IP addresses, you can append /mask to the hostname or IP address. mask must be between 0 (scan the whole Internet) and 32 (scan the single host specified). Use /24 to scan a class "C" address and /16 for a class "B". There is also a more powerful notation which lets you specify an IP address using lists/ranges for each element. Thus you can scan the whole class "B" network 192.168.*.* by specifying "192.168.*.*" or "192.168.0-255.0-255" or even "192.168.1-50,51-255.1,2,3,4,5-255". And of course you can use the mask notation: "192.168.0.0/16". These are all equivalent. If you use asterisks ("*"), remember that most shells require you to escape them with back slashes or protect them with quotes.
Range Mode
In this mode two (and only two!) IP addresses must be specified, in dotted quad notation, and the output is all the addresses between the two (inclusive). This mode can be used to cross class boundaries.
Example:
In its most basic form genip simply echos the IP addresses listed on the command line:
> genip 10.1.1.1 10.3.4.5
10.1.1.1
10.3.4.5
By use one of the many expansion methods detailed above a large number of IP addresses can be generated from simple command line specifications:
> genip 10.1.1.1-3
10.1.2.0
10.1.2.1
10.1.2.2
By selecting range mode (with the use of the -r flag) it is a simple matter to generate address lists that cross class boundaries:
> genip -r 10.1.1.254 10.1.2.2
10.1.1.254
10.1.1.255
10.1.2.0
10.1.2.1
10.1.2.2
Download (0.011MB)
Added: 2007-08-18 License: GPL (GNU General Public License) Price:
798 downloads
Event 1.09
Event is an Event loop processing. more>>
Event is an Event loop processing.
SYNOPSIS
use Event qw(loop unloop);
# initialize application
Event->flavor(attribute => value, ...);
my $ret = loop();
# and some callback will call
unloop(ok);
The Event module provide a central facility to watch for various types of events and invoke a callback when these events occur. The idea is to delay the handling of events so that they may be dispatched in priority order when it is safe for callbacks to execute.
Events (in the ordinary sense of the word) are detected by watchers, which reify them as events (in the special Event module sense). For clarity, the former type of events may be called "source events", and the latter "target events". Source events, such as signals arriving, happen whether or not they are being watched. If a source event occurs which a watcher is actively watching then the watcher generates a corresponding target event. Target events are only created by watchers. If several watchers are interested in the same source event then each will generate their own target event. Hence, any particular source event may result in zero, one, two, or any number of target events: the same as the number of watchers which were actively watching for it.
Target events are queued to be processed in priority order (priority being determined by the creating watcher) and in FIFO order among events of the same priority. Queued ("pending") events can, in some cases, be cancelled before being processed. A queued event is processed by being passed to the callback function (or method on a particular object or class) which was specified to the watcher.
A watcher, once created, operates autonomously without the Event user having to retain any reference to it. However, keeping a reference makes it possible to modify most of the watchers characteristics. A watcher can be switched between active and inactive states. When inactive, it does not generate target events.
Some types of source event are not reified as target events immediately. Signals received, for example, are counted initially. The counted signals are reified at certain execution points. Hence, signal events may be processed out of order, and if handled carelessly, on the wrong side of a state change in event handling. A useful way to view this is that occurrence of the source event is not actually the arrival of the signal but is triggered by the counting of the signal.
Reification can be forced when necessary. The schedule on which some other events are created is non-obvious. This is especially the case with watchers that watch for a condition rather than an event. In some cases, target events are generated on a schedule that depends on the operation of the event loop.
<<lessSYNOPSIS
use Event qw(loop unloop);
# initialize application
Event->flavor(attribute => value, ...);
my $ret = loop();
# and some callback will call
unloop(ok);
The Event module provide a central facility to watch for various types of events and invoke a callback when these events occur. The idea is to delay the handling of events so that they may be dispatched in priority order when it is safe for callbacks to execute.
Events (in the ordinary sense of the word) are detected by watchers, which reify them as events (in the special Event module sense). For clarity, the former type of events may be called "source events", and the latter "target events". Source events, such as signals arriving, happen whether or not they are being watched. If a source event occurs which a watcher is actively watching then the watcher generates a corresponding target event. Target events are only created by watchers. If several watchers are interested in the same source event then each will generate their own target event. Hence, any particular source event may result in zero, one, two, or any number of target events: the same as the number of watchers which were actively watching for it.
Target events are queued to be processed in priority order (priority being determined by the creating watcher) and in FIFO order among events of the same priority. Queued ("pending") events can, in some cases, be cancelled before being processed. A queued event is processed by being passed to the callback function (or method on a particular object or class) which was specified to the watcher.
A watcher, once created, operates autonomously without the Event user having to retain any reference to it. However, keeping a reference makes it possible to modify most of the watchers characteristics. A watcher can be switched between active and inactive states. When inactive, it does not generate target events.
Some types of source event are not reified as target events immediately. Signals received, for example, are counted initially. The counted signals are reified at certain execution points. Hence, signal events may be processed out of order, and if handled carelessly, on the wrong side of a state change in event handling. A useful way to view this is that occurrence of the source event is not actually the arrival of the signal but is triggered by the counting of the signal.
Reification can be forced when necessary. The schedule on which some other events are created is non-obvious. This is especially the case with watchers that watch for a condition rather than an event. In some cases, target events are generated on a schedule that depends on the operation of the event loop.
Download (0.24MB)
Added: 2007-06-06 License: Perl Artistic License Price:
872 downloads
Qtractor 0.0.4.675
Qtractor project is an Audio/MIDI multi-track sequencer application written in C++ around the Qt4 toolkit using Qt Designer. more>>
Qtractor project is an Audio/MIDI multi-track sequencer application written in C++ around the Qt4 toolkit using Qt Designer.
The initial target platform will be Linux, where the Jack Audio Connection Kit (JACK) for audio, and the Advanced Linux Sound Architecture (ALSA) for MIDI, are the main infrastructures to evolve as a fairly-featured Linux Desktop Audio Workstation GUI, specially dedicated to the personal home-studio.
<<lessThe initial target platform will be Linux, where the Jack Audio Connection Kit (JACK) for audio, and the Advanced Linux Sound Architecture (ALSA) for MIDI, are the main infrastructures to evolve as a fairly-featured Linux Desktop Audio Workstation GUI, specially dedicated to the personal home-studio.
Download (0.34MB)
Added: 2007-07-20 License: GPL (GNU General Public License) Price:
836 downloads
srcpkg 1.1
srcpkg is a program for managing separate software packages under the same directory hierarchy. more>>
SouRCe PacKaGer (srcpkg) is a program for managing separate software packages under the same directory hierarchy. It is especially useful for packages distributed as source code.
srcpkg is similar to GNU Stow, Depot, etc., but is designed to be able to handle large, complex, interdependent packages such as those of KDE and GNOME.
srcpkg works by creating packages from new files found in the target directory tree. This allows packages to be installed as they were intended, into a specific prefix (eg. /usr/local), and srcpkg takes care of moving the new files to a separate package directory and creating symlinks into the target tree.
srcpkg is a Perl script, so it requires Perl 5.6 or above. srcpkg may be ported to C in a future version; if this would be beneficial to you, please contact the author.
srcpkg project has successfully been used to manage a large number of software packages, notably Gnome and KDE.
<<lesssrcpkg is similar to GNU Stow, Depot, etc., but is designed to be able to handle large, complex, interdependent packages such as those of KDE and GNOME.
srcpkg works by creating packages from new files found in the target directory tree. This allows packages to be installed as they were intended, into a specific prefix (eg. /usr/local), and srcpkg takes care of moving the new files to a separate package directory and creating symlinks into the target tree.
srcpkg is a Perl script, so it requires Perl 5.6 or above. srcpkg may be ported to C in a future version; if this would be beneficial to you, please contact the author.
srcpkg project has successfully been used to manage a large number of software packages, notably Gnome and KDE.
Download (0.058MB)
Added: 2006-08-23 License: GPL (GNU General Public License) Price:
1157 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 target 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