opt
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 119
syncopt 1.1
syncopt is a flexible and simple approach to package install. more>>
The syncopt script and its associated work practices are yet another approach to the standard sysadmin problem of keeping multiple machines software installations up to date.
It is independent of the vendors packaging scheme and thus you can use either your vendors system or syncopt, or both!
The core notion is that the install is done once on a central machine and then syncopt takes care of attaching that to every client, often via cron.
- easy to use
- flexible enough to permit control of what is installed locally on a machine and what is served remotely from a central server (for disc space or other reasons)
- keep out of the way of the ``vendors namespace, to avoid treading on the vendors install and conversely to protect our additions from damage by vendor upgrades and patches.
Main features:
lightweight
- If a package is not to be installed local to a client then the burden is usually just two symlinks on the client.
optional
- You can install packages with syncopt or with the vendors packaging scheme, or both!
permits trial installs
- Under syncopt you can install multiple versions of the same package for trial or legacy purposes.
centralised
- The default package version is controlled by a symlink on the master host; change that and all the clients will follow suit next time they run syncopt.
customisable
- Clients can control which packages are local and also override which version is their default for a given package.
Using
Local Package Install
As a consequence, to make an instance of something local to a client machine (lets call it pkg, release version), remove the local symlink:
$ rm /opt/pkg-version
Make a stub directory:
$ mkdir /opt/pkg-version
Alternatively, just edit the .syncopt file and add this line:
pkg-version local
Run syncopt:
$ syncopt -x
That syncs everything. You can just do the new package like this:
$ syncopt -x pkg pkg-version
which syncs the generic (unversioned) link and the version specific local directory.
Undoing a Local Package Install
To make a once-local copy remote, remove the local copy:
$ rm -rf /opt/pkg-version
Also, if you edited the .syncopt file as above, remove that line.
Run syncopt:
$ syncopt -x pkg pkg-version
Bringing a Client into Sync after a New Package Install
To set up a new clients /opt directory after a fresh install:
$ mkdir /opt # if necessary
$ syncopt -x
/opt/.syncopt
The behaviour deduced from the presence or absence of a directory can be overridden with the /opt/.syncopt file, which contains line of the form:
pkg version
to make version the default package version on this particular machine, or
pkg local
to force a package to be local on this machine, or
pkg-version local
to make a particular version local, or
pkg nosync
to not run syncopt on it at all.
<<lessIt is independent of the vendors packaging scheme and thus you can use either your vendors system or syncopt, or both!
The core notion is that the install is done once on a central machine and then syncopt takes care of attaching that to every client, often via cron.
- easy to use
- flexible enough to permit control of what is installed locally on a machine and what is served remotely from a central server (for disc space or other reasons)
- keep out of the way of the ``vendors namespace, to avoid treading on the vendors install and conversely to protect our additions from damage by vendor upgrades and patches.
Main features:
lightweight
- If a package is not to be installed local to a client then the burden is usually just two symlinks on the client.
optional
- You can install packages with syncopt or with the vendors packaging scheme, or both!
permits trial installs
- Under syncopt you can install multiple versions of the same package for trial or legacy purposes.
centralised
- The default package version is controlled by a symlink on the master host; change that and all the clients will follow suit next time they run syncopt.
customisable
- Clients can control which packages are local and also override which version is their default for a given package.
Using
Local Package Install
As a consequence, to make an instance of something local to a client machine (lets call it pkg, release version), remove the local symlink:
$ rm /opt/pkg-version
Make a stub directory:
$ mkdir /opt/pkg-version
Alternatively, just edit the .syncopt file and add this line:
pkg-version local
Run syncopt:
$ syncopt -x
That syncs everything. You can just do the new package like this:
$ syncopt -x pkg pkg-version
which syncs the generic (unversioned) link and the version specific local directory.
Undoing a Local Package Install
To make a once-local copy remote, remove the local copy:
$ rm -rf /opt/pkg-version
Also, if you edited the .syncopt file as above, remove that line.
Run syncopt:
$ syncopt -x pkg pkg-version
Bringing a Client into Sync after a New Package Install
To set up a new clients /opt directory after a fresh install:
$ mkdir /opt # if necessary
$ syncopt -x
/opt/.syncopt
The behaviour deduced from the presence or absence of a directory can be overridden with the /opt/.syncopt file, which contains line of the form:
pkg version
to make version the default package version on this particular machine, or
pkg local
to force a package to be local on this machine, or
pkg-version local
to make a particular version local, or
pkg nosync
to not run syncopt on it at all.
Download (0.010MB)
Added: 2005-04-07 License: Freely Distributable Price:
1660 downloads
frag-opt 0.5.5
frag-opt is a portable, re-entrant argument parsing library. more>>
frag-opt is a re-entrant, portable command-line parsing library. To see how you can use this in your program, take a look at doc/example.c or take a look at the man-page ("man frag-opt") once youve installed.
The man-page talks about an info-page, but as its still incomplete, I decided not to include it with the distribution yet.
Installation:
./configure (the standard options work here, nothing frag-opt specific)
make
make check (optional)
make install (become root if necessary)
Should compile on any ANSI C compiler. Should compile on C++ compilers too (at least does with g++).
Enhancements:
- FRAG_POSIX works (I think)
- large amounts of different options for one option are now printed better
- removed some obsolete stuff from the header-file
- some additions and fixes to the man-page
- the term cluster is now deprecated. group is used instead.
- added a healthy dose of consts (thanks to chisel)
- changed the help-message format a little
- tuned the wrapping-algorithm
- added -D_REENTRANT to build-flags to make the library magically better (unless Im mistaken, theres something in (g)libc that requires this to make it re-entrant)
<<lessThe man-page talks about an info-page, but as its still incomplete, I decided not to include it with the distribution yet.
Installation:
./configure (the standard options work here, nothing frag-opt specific)
make
make check (optional)
make install (become root if necessary)
Should compile on any ANSI C compiler. Should compile on C++ compilers too (at least does with g++).
Enhancements:
- FRAG_POSIX works (I think)
- large amounts of different options for one option are now printed better
- removed some obsolete stuff from the header-file
- some additions and fixes to the man-page
- the term cluster is now deprecated. group is used instead.
- added a healthy dose of consts (thanks to chisel)
- changed the help-message format a little
- tuned the wrapping-algorithm
- added -D_REENTRANT to build-flags to make the library magically better (unless Im mistaken, theres something in (g)libc that requires this to make it re-entrant)
Download (0.031MB)
Added: 2005-10-07 License: GPL (GNU General Public License) Price:
1480 downloads
Tk::Getopt 0.49
Tk::Getopt is a user configuration window for Tk with interface to Getopt::Long. more>>
Tk::Getopt is a user configuration window for Tk with interface to Getopt::Long.
SYNOPSIS
use Tk::Getopt;
@opttable = ([opt1, =s, default], [opt2, !, 1], ...);
$opt = new Tk::Getopt(-opttable => @opttable,
-options => %options,
-filename => "$ENV{HOME}/.options");
$opt->set_defaults; # set default values
$opt->load_options; # configuration file
$opt->get_options; # command line
$opt->process_options; # process callbacks, check restrictions ...
print $options->{opt1}, $options->{opt2} ...;
...
$top = new MainWindow;
$opt->option_editor($top);
or using a Getopt::Long-like interface
$opt = new Tk::Getopt(-getopt => [help => $HELP,
file:s => $FILE,
foo! => $FOO,
num:i => $NO,
]);
or an alternative Getopt::Long interface
%optctl = (foo => $foo,
bar => $bar);
$opt = new Tk::Getopt(-getopt => [%optctl, "foo!", "bar=s"]);
Tk::Getopt provides an interface to access command line options via Getopt::Long and editing with a graphical user interface via a Tk window.
Unlike Getopt::Long, this package uses a object oriented interface, so you have to create a new Tk::Getopt object with new. Unlike other packages in the Tk hierarchy, this package does not define a Tk widget. The graphical interface is calles by the method option_editor.
After creating an object with new, you can parse command line options by calling get_options. This method calls itself Getopt::Long::GetOptions.
<<lessSYNOPSIS
use Tk::Getopt;
@opttable = ([opt1, =s, default], [opt2, !, 1], ...);
$opt = new Tk::Getopt(-opttable => @opttable,
-options => %options,
-filename => "$ENV{HOME}/.options");
$opt->set_defaults; # set default values
$opt->load_options; # configuration file
$opt->get_options; # command line
$opt->process_options; # process callbacks, check restrictions ...
print $options->{opt1}, $options->{opt2} ...;
...
$top = new MainWindow;
$opt->option_editor($top);
or using a Getopt::Long-like interface
$opt = new Tk::Getopt(-getopt => [help => $HELP,
file:s => $FILE,
foo! => $FOO,
num:i => $NO,
]);
or an alternative Getopt::Long interface
%optctl = (foo => $foo,
bar => $bar);
$opt = new Tk::Getopt(-getopt => [%optctl, "foo!", "bar=s"]);
Tk::Getopt provides an interface to access command line options via Getopt::Long and editing with a graphical user interface via a Tk window.
Unlike Getopt::Long, this package uses a object oriented interface, so you have to create a new Tk::Getopt object with new. Unlike other packages in the Tk hierarchy, this package does not define a Tk widget. The graphical interface is calles by the method option_editor.
After creating an object with new, you can parse command line options by calling get_options. This method calls itself Getopt::Long::GetOptions.
Download (0.022MB)
Added: 2006-11-03 License: Perl Artistic License Price:
1085 downloads
Getopt::EvaP 2.3.5
Getopt::EvaP is a Perl module to evaluate Perl command line parameters. more>>
Getopt::EvaP is a Perl module to evaluate Perl command line parameters.
SYNOPSIS
use vars qw/@PDT @MM %OPT/;
use Getopt::EvaP;
EvaP @PDT, @MM, %OPT;
EXPORT
use Getopt::EvaP exports the subs EvaP and EvaP_PAC into your name space.
@PDT is the Parameter Description Table, which is a reference to a list of strings describing the command line parameters, aliases, types and default values. @MM is the Message Module, which is also a reference to a list of strings describing the command and its parameters. %OPT is an optional hash reference where Evaluate Parameters should place its results. If specified, the historical behaviour of modifying the calling routines namespace by storing option values in %Options, %options and $opt* is disabled.
<<lessSYNOPSIS
use vars qw/@PDT @MM %OPT/;
use Getopt::EvaP;
EvaP @PDT, @MM, %OPT;
EXPORT
use Getopt::EvaP exports the subs EvaP and EvaP_PAC into your name space.
@PDT is the Parameter Description Table, which is a reference to a list of strings describing the command line parameters, aliases, types and default values. @MM is the Message Module, which is also a reference to a list of strings describing the command and its parameters. %OPT is an optional hash reference where Evaluate Parameters should place its results. If specified, the historical behaviour of modifying the calling routines namespace by storing option values in %Options, %options and $opt* is disabled.
Download (0.051MB)
Added: 2006-11-02 License: Perl Artistic License Price:
1087 downloads
Getopt::Lucid 0.16
Getopt::Lucid is a clear, readable syntax for command line processing. more>>
Getopt::Lucid is a clear, readable syntax for command line processing.
SYNOPSIS
use Getopt::Lucid qw( :all );
# basic option specifications with aliases
@specs = (
Switch("version|V"),
Counter("verbose|v"),
Param("config|C"),
List("lib|l|I"),
Keypair("define"),
Switch("help|h")
);
$opt = Getopt::Lucid->getopt( @specs );
$verbosity = $opt->get_verbose;
@libs = $opt->get_lib;
%defs = $opt->get_define;
%all_options = $opt->options;
# advanced option specifications
@adv_spec = (
Param("input")->required, # required
Param("mode")->default("tcp"), # defaults
Param("host")->needs("port"), # dependencies
Param("port", qr/d+/ )->required, # regex validation
Param("config", sub { -r } ), # custom validation
Param("help")->anycase, # case insensitivity
);
# example with a config file
use Config::Std;
if ( -r $opt->get_config ) {
read_config( $opt->get_config() => my %config_hash );
$opt->merge_defaults( $config_hash{} );
}
The goal of this module is providing good code readability and clarity of intent for command-line option processing. While readability is a subjective standard, Getopt::Lucid relies on a more verbose, plain-English option specification as compared against the more symbolic approach of Getopt::Long.
Main features:
- Five option types: switches, counters, parameters, lists, and keypairs
- Three option styles: long, short (including bundled), and bare (without dashes)
- Specification of defaults, required options and option dependencies
- Validation of options with regexes or subroutines
- Negation of options on the command line
- Support for parsing any array, not just the default @ARGV
- Incorporation of external defaults (e.g. from a config file) with user control of precedence
<<lessSYNOPSIS
use Getopt::Lucid qw( :all );
# basic option specifications with aliases
@specs = (
Switch("version|V"),
Counter("verbose|v"),
Param("config|C"),
List("lib|l|I"),
Keypair("define"),
Switch("help|h")
);
$opt = Getopt::Lucid->getopt( @specs );
$verbosity = $opt->get_verbose;
@libs = $opt->get_lib;
%defs = $opt->get_define;
%all_options = $opt->options;
# advanced option specifications
@adv_spec = (
Param("input")->required, # required
Param("mode")->default("tcp"), # defaults
Param("host")->needs("port"), # dependencies
Param("port", qr/d+/ )->required, # regex validation
Param("config", sub { -r } ), # custom validation
Param("help")->anycase, # case insensitivity
);
# example with a config file
use Config::Std;
if ( -r $opt->get_config ) {
read_config( $opt->get_config() => my %config_hash );
$opt->merge_defaults( $config_hash{} );
}
The goal of this module is providing good code readability and clarity of intent for command-line option processing. While readability is a subjective standard, Getopt::Lucid relies on a more verbose, plain-English option specification as compared against the more symbolic approach of Getopt::Long.
Main features:
- Five option types: switches, counters, parameters, lists, and keypairs
- Three option styles: long, short (including bundled), and bare (without dashes)
- Specification of defaults, required options and option dependencies
- Validation of options with regexes or subroutines
- Negation of options on the command line
- Support for parsing any array, not just the default @ARGV
- Incorporation of external defaults (e.g. from a config file) with user control of precedence
Download (0.039MB)
Added: 2007-01-16 License: Perl Artistic License Price:
1012 downloads
Getopt::ExPar 0.01
Getopt::ExPar contains extended parameters command line parser. more>>
Getopt::ExPar contains extended parameters command line parser.
SYNOPSIS
use Getopt::ExPar;
my(@PDT, @MM, %OPT);
ExPar @PDT, @MM, $OPT;
EXPORT
use Getopt::ExPar exports the sub ExPar into your name space.
ExPar is a perl5 module used to parse command line parameters. This package uses the @PDT, Parameter Description Table, and the @MM, Message Module, to return %OPT which is a hash reference containing the command line option data. The function of Getopt::ExPar is based on Getopt::EvaP, created by Stephen O. Lidie.
Introduction
The ExPar function parses a perl command line. Using the option definitions in the @PDT, argument types are checked and the arguments themselves may be checked against a specified range or pattern. By using both @PDT and @MM, several types of help may be retured to the user. ExPar handles command lines with this format:
command [-parameters] [file_list]
where any parameters and file_list are optional.
Parameter Description Table (PDT) Syntax
Here is the PDT syntax. Optional constructs are enclosed in [], and the | character separates possible values in a list.
PDT [program_name, alias]
[parameter_name[, alias]: type [pattern | range] [ = [default_variable,] default_value]]
PDTEND [flag_list]
flag_list is one or more of the following flags: optional_file_list | required_file_list | no_file_list: specifies condition of list of files at end of command line. (only one of these may be specified) abbreviations: allows for abbreviations of commands or aliases as long as enough of the command is given to make it distinguishable from all others. If not, a message is printed so the user may be more specific. switchglomming: allows for multiple single-letter switch options to be specified as single option (must be first option). pdt_warnings: for debugging a @PDT, it prints out messages that are not necessarily errors, like inconsistent number of default values in a list, etc.
The default_variable is an environment variable - see the section Usage Notes for complete details.
So, the simplest possible PDT would be:
PDT
PDTEND
This PDT would simply define a -help switch for the command, but is rather useless.
A typical PDT would look more like this:
PDT frog
number, n: integer = 1
chars, c: string = "default_string"
PDTEND no_file_list
This PDT, for command frog, defines two parameters, number (or n), of type integer with a default value of 1, and chars (or c), of type string with a default value of "default_string". The PDTEND no_file_list indicator indicates that no trailing file_list can appear on the command line. Of course, the -help switch is defined automatically.
Each of these options may be further refined by using a range and a pattern, respectively:
PDT frog
number, n: integer (((#100, the # is implied. Other simple conditions are < and == (a single = is accepted as ==, not an assignment). Ex: This condition: (#>10, #<<less
SYNOPSIS
use Getopt::ExPar;
my(@PDT, @MM, %OPT);
ExPar @PDT, @MM, $OPT;
EXPORT
use Getopt::ExPar exports the sub ExPar into your name space.
ExPar is a perl5 module used to parse command line parameters. This package uses the @PDT, Parameter Description Table, and the @MM, Message Module, to return %OPT which is a hash reference containing the command line option data. The function of Getopt::ExPar is based on Getopt::EvaP, created by Stephen O. Lidie.
Introduction
The ExPar function parses a perl command line. Using the option definitions in the @PDT, argument types are checked and the arguments themselves may be checked against a specified range or pattern. By using both @PDT and @MM, several types of help may be retured to the user. ExPar handles command lines with this format:
command [-parameters] [file_list]
where any parameters and file_list are optional.
Parameter Description Table (PDT) Syntax
Here is the PDT syntax. Optional constructs are enclosed in [], and the | character separates possible values in a list.
PDT [program_name, alias]
[parameter_name[, alias]: type [pattern | range] [ = [default_variable,] default_value]]
PDTEND [flag_list]
flag_list is one or more of the following flags: optional_file_list | required_file_list | no_file_list: specifies condition of list of files at end of command line. (only one of these may be specified) abbreviations: allows for abbreviations of commands or aliases as long as enough of the command is given to make it distinguishable from all others. If not, a message is printed so the user may be more specific. switchglomming: allows for multiple single-letter switch options to be specified as single option (must be first option). pdt_warnings: for debugging a @PDT, it prints out messages that are not necessarily errors, like inconsistent number of default values in a list, etc.
The default_variable is an environment variable - see the section Usage Notes for complete details.
So, the simplest possible PDT would be:
PDT
PDTEND
This PDT would simply define a -help switch for the command, but is rather useless.
A typical PDT would look more like this:
PDT frog
number, n: integer = 1
chars, c: string = "default_string"
PDTEND no_file_list
This PDT, for command frog, defines two parameters, number (or n), of type integer with a default value of 1, and chars (or c), of type string with a default value of "default_string". The PDTEND no_file_list indicator indicates that no trailing file_list can appear on the command line. Of course, the -help switch is defined automatically.
Each of these options may be further refined by using a range and a pattern, respectively:
PDT frog
number, n: integer (((#100, the # is implied. Other simple conditions are < and == (a single = is accepted as ==, not an assignment). Ex: This condition: (#>10, #<<less
Download (0.018MB)
Added: 2007-08-07 License: Perl Artistic License Price:
808 downloads
Getopt::Fancy 0.02
Getopt::Fancy is an object approach to handling command line options, focusing on end user happiness. more>>
Getopt::Fancy is an object approach to handling command line options, focusing on end user happiness.
SYNOPSIS
use Getopt::Fancy;
my $opts = Getopt::Fancy->new();
$opts->add("db", GT => "=s",
EX => " ",
DESC => "The database to dump. Leave unset for all databases.",
DEF => "teen_titans",
ALLOWED => ["--all-databases", "mydb", "teen_titans"],
REGEX => ^[a-zA-Z0-9_]+$,
REQ => 0,
SECTION => "Required DB Params");
# Allow just printing out of set options
$opts->add("check_args", DESC => "Just print all the options", SECTION => "Misc Params");
# Allow user to specify list of options s/he needs help with
$opts->add("help", GT => ":s@", EX => "[option1,option2..]",
DESC => "Give option names and itll print the help for just those options, otherwise all.",
SECTION=>"Misc Params", COMMAS=>1);
# Get the command line options
my $error_msg = $opts->get_options();
print_usage($error_msg) if $error_msg;
print "Will dump this database: $opts->{db} n";
print "User wants help information on these: " . join(", ", @{$opts->{help}}) . "n" if ($opts->{help});
print_usage() if $opts->{help};
print_args() if $opts->{check_args};
sub print_args
{
print $opts->get_values();
exit(0);
}
sub print_usage
{
my $hopts;
my $msg = shift;
$hopts = $opts->{help} unless (scalar @{$opts->{help}} == 0);
print "usage: $0 n";
print $opts->get_usage($hopts);
print "ERROR: $msgn" if $msg;
exit(0);
}
Getopt::Fancy Allows command line options to be all in one place in your script including default values, allowed values, user-friendly descriptions, required flags and pattern matching requirements. Ofttimes script writers skimp on the usage information or have out-dated help information. This modules helps script writers to be better citizens.
This module uses Getopt::Long, so the same rules apply.
<<lessSYNOPSIS
use Getopt::Fancy;
my $opts = Getopt::Fancy->new();
$opts->add("db", GT => "=s",
EX => " ",
DESC => "The database to dump. Leave unset for all databases.",
DEF => "teen_titans",
ALLOWED => ["--all-databases", "mydb", "teen_titans"],
REGEX => ^[a-zA-Z0-9_]+$,
REQ => 0,
SECTION => "Required DB Params");
# Allow just printing out of set options
$opts->add("check_args", DESC => "Just print all the options", SECTION => "Misc Params");
# Allow user to specify list of options s/he needs help with
$opts->add("help", GT => ":s@", EX => "[option1,option2..]",
DESC => "Give option names and itll print the help for just those options, otherwise all.",
SECTION=>"Misc Params", COMMAS=>1);
# Get the command line options
my $error_msg = $opts->get_options();
print_usage($error_msg) if $error_msg;
print "Will dump this database: $opts->{db} n";
print "User wants help information on these: " . join(", ", @{$opts->{help}}) . "n" if ($opts->{help});
print_usage() if $opts->{help};
print_args() if $opts->{check_args};
sub print_args
{
print $opts->get_values();
exit(0);
}
sub print_usage
{
my $hopts;
my $msg = shift;
$hopts = $opts->{help} unless (scalar @{$opts->{help}} == 0);
print "usage: $0 n";
print $opts->get_usage($hopts);
print "ERROR: $msgn" if $msg;
exit(0);
}
Getopt::Fancy Allows command line options to be all in one place in your script including default values, allowed values, user-friendly descriptions, required flags and pattern matching requirements. Ofttimes script writers skimp on the usage information or have out-dated help information. This modules helps script writers to be better citizens.
This module uses Getopt::Long, so the same rules apply.
Download (0.005MB)
Added: 2006-11-04 License: Perl Artistic License Price:
1084 downloads
PDL::Opt::NonLinear 0.02
PDL::Opt::NonLinear is a Perl module with non linear optimization routines. more>>
PDL::Opt::NonLinear is a Perl module with non linear optimization routines.
SYNOPSIS
use PDL::Opt::NonLinear;
$x = random(5);
$gx = rosen_grad($x);
$fx = rosen($x);
$xtol = pdl(1e-16);
$gtol = pdl(0.9);
$eps = pdl(1e-10);
$print = ones(2);
$maxit = pdl(long, 200);
$info = pdl(long,0);
sub fg_func{
my ($f, $g, $x) = @_;
$f .= rosen($x);
$g .= rosen_grad($x);
}
cgfam($fx, $gx, $x, $maxit, $eps, $xtol, $gtol,$print,$info,1,&fg_func);
<<lessSYNOPSIS
use PDL::Opt::NonLinear;
$x = random(5);
$gx = rosen_grad($x);
$fx = rosen($x);
$xtol = pdl(1e-16);
$gtol = pdl(0.9);
$eps = pdl(1e-10);
$print = ones(2);
$maxit = pdl(long, 200);
$info = pdl(long,0);
sub fg_func{
my ($f, $g, $x) = @_;
$f .= rosen($x);
$g .= rosen_grad($x);
}
cgfam($fx, $gx, $x, $maxit, $eps, $xtol, $gtol,$print,$info,1,&fg_func);
Download (0.24MB)
Added: 2007-07-05 License: Perl Artistic License Price:
841 downloads
Tk::Optionmenu 804.027
Tk::Optionmenu will let the user select one of some predefined options values. more>>
Tk::Optionmenu will let the user select one of some predefined options values.
SYNOPSIS
use Optionmenu;
$opt = $w->Optionmenu(
-options => REFERENCE_to_OPTIONLIST,
-command => CALLBACK,
-variable => SCALAR_REF,
);
$opt->addOptions( OPTIONLIST );
# OPTION LIST is
# a) $val1, $val2, $val3,...
# b) [ $lab1=>$val1], [$lab2=>val2], ... ]
# c) combination of a) and b), e.g.,
# val1, [$lab2=>val2], val3, val4, [...], ...
The Optionmenu widget allows the user chose between a given set of options.
If the user should be able to change the available option have a look at Tk::BrowseEntry.
OPTIONS
-options
(Re)sets the list of options presented.
-command
Defines the callback that is invokes when a new option is selected.
-variable
Reference to a scalar that contains the current value of the selected option.
-textvariable
Reference to a scalar that contains the text label of the current value of the selected option.
METHODS
addOptions
Adds OPTION_LIST to the already available options.
EXAMPLE
use Tk;
my $mw = MainWindow->new();
my ($var, $tvar);
my $opt = $mw->Optionmenu(
-options => [[jan=>1], [feb=>2], [mar=>3], [apr=>4]],
-command => sub { print "got: ", shift, "n" },
-variable => $var,
-textvariable => $tvar
)->pack;
$opt->addOptions([may=>5],[jun=>6],[jul=>7],[aug=>8]);
my $f = $mw->Frame(-relief=>groove, -borderwidth => 2)->pack;
$f->Label(-textvariable=>$tvar)->pack(-side => left);
$f->Label(-text => " -> ")->pack(-side => left);
$f->Label(-textvariable=>$var)->pack(-side => left);
$mw->Button(-text=>Exit, -command=>sub{$mw->destroy})->pack;
MainLoop;
<<lessSYNOPSIS
use Optionmenu;
$opt = $w->Optionmenu(
-options => REFERENCE_to_OPTIONLIST,
-command => CALLBACK,
-variable => SCALAR_REF,
);
$opt->addOptions( OPTIONLIST );
# OPTION LIST is
# a) $val1, $val2, $val3,...
# b) [ $lab1=>$val1], [$lab2=>val2], ... ]
# c) combination of a) and b), e.g.,
# val1, [$lab2=>val2], val3, val4, [...], ...
The Optionmenu widget allows the user chose between a given set of options.
If the user should be able to change the available option have a look at Tk::BrowseEntry.
OPTIONS
-options
(Re)sets the list of options presented.
-command
Defines the callback that is invokes when a new option is selected.
-variable
Reference to a scalar that contains the current value of the selected option.
-textvariable
Reference to a scalar that contains the text label of the current value of the selected option.
METHODS
addOptions
Adds OPTION_LIST to the already available options.
EXAMPLE
use Tk;
my $mw = MainWindow->new();
my ($var, $tvar);
my $opt = $mw->Optionmenu(
-options => [[jan=>1], [feb=>2], [mar=>3], [apr=>4]],
-command => sub { print "got: ", shift, "n" },
-variable => $var,
-textvariable => $tvar
)->pack;
$opt->addOptions([may=>5],[jun=>6],[jul=>7],[aug=>8]);
my $f = $mw->Frame(-relief=>groove, -borderwidth => 2)->pack;
$f->Label(-textvariable=>$tvar)->pack(-side => left);
$f->Label(-text => " -> ")->pack(-side => left);
$f->Label(-textvariable=>$var)->pack(-side => left);
$mw->Button(-text=>Exit, -command=>sub{$mw->destroy})->pack;
MainLoop;
Download (5.7MB)
Added: 2007-08-21 License: Perl Artistic License Price:
794 downloads
IO::Util 1.5
IO::Util is a selection of general-utility IO function. more>>
IO::Util is a selection of general-utility IO function.
SYNOPSIS
use IO::Util qw(capture slurp Tid Lid Uid load_mml);
capture()
# captures the selected filehandle
$output_ref = capture { any_printing_code() } ;
# now $$output_ref eq something
# captures FILEHANDLE
$output_ref = capture { any_special_printing_code() } *FILEHEANDLER ;
# append the output to $captured
capture { any_printing_code() } *FILEHEANDLER , $captured
# now $captured eq something
# use another class to tie the handler
use IO::Scalar ;
$IO::Util::TIE_HANDLE_CLASS = IO::Scalar
slurp()
$_ = /path/to/file ;
$content_ref = slurp ;
$content_ref = slurp /path/to/file ;
$content_ref = slurp *FILEHANDLE ;
# append the file content to $content
$_ = /path/to/file ;
slurp $content;
slurp /path/to/file, $content ;
slurp *FILEHANDLE, $content ;
Tid(), Lid(), Uid()
$temporarily_unique_id = Tid ; # Q9MU1N_NVRM
$locally_unique_id = Lid ; # 2MS_Q9MU1N_P5F6
$universally_unique_id = Uid ; # MGJFSBTK_2MS_Q9MU1N_PWES
A MML file (Minimal Markup Language)
< opt >
< !-- a multi line
comment-- >
< parA >
< optA >01< /optA >
< optA >02< /optA >
< optA >03< /optA >
< /parA >
< parB >
< optA >04< /optA >
< optA >05< /optA >
< optA >06< /optA >
< optB >
< key >any key< /key >
< /optB >
< /parB >
< /opt >
load_mml()
$struct = load_mml path/to/mml_file ;
$struct = load_mml $mml_string ;
$struct = load_mml *MMLFILE ;
$struct = load_mml ..., %options ;
# $struct = {
# parA => {
# optA => [
# 01,
# 02,
# 03
# ]
# },
# parB => {
# optA => [
# 04,
# 05,
# 06
# ],
# optB => {
# key => any key
# }
# }
# }
<<lessSYNOPSIS
use IO::Util qw(capture slurp Tid Lid Uid load_mml);
capture()
# captures the selected filehandle
$output_ref = capture { any_printing_code() } ;
# now $$output_ref eq something
# captures FILEHANDLE
$output_ref = capture { any_special_printing_code() } *FILEHEANDLER ;
# append the output to $captured
capture { any_printing_code() } *FILEHEANDLER , $captured
# now $captured eq something
# use another class to tie the handler
use IO::Scalar ;
$IO::Util::TIE_HANDLE_CLASS = IO::Scalar
slurp()
$_ = /path/to/file ;
$content_ref = slurp ;
$content_ref = slurp /path/to/file ;
$content_ref = slurp *FILEHANDLE ;
# append the file content to $content
$_ = /path/to/file ;
slurp $content;
slurp /path/to/file, $content ;
slurp *FILEHANDLE, $content ;
Tid(), Lid(), Uid()
$temporarily_unique_id = Tid ; # Q9MU1N_NVRM
$locally_unique_id = Lid ; # 2MS_Q9MU1N_P5F6
$universally_unique_id = Uid ; # MGJFSBTK_2MS_Q9MU1N_PWES
A MML file (Minimal Markup Language)
< opt >
< !-- a multi line
comment-- >
< parA >
< optA >01< /optA >
< optA >02< /optA >
< optA >03< /optA >
< /parA >
< parB >
< optA >04< /optA >
< optA >05< /optA >
< optA >06< /optA >
< optB >
< key >any key< /key >
< /optB >
< /parB >
< /opt >
load_mml()
$struct = load_mml path/to/mml_file ;
$struct = load_mml $mml_string ;
$struct = load_mml *MMLFILE ;
$struct = load_mml ..., %options ;
# $struct = {
# parA => {
# optA => [
# 01,
# 02,
# 03
# ]
# },
# parB => {
# optA => [
# 04,
# 05,
# 06
# ],
# optB => {
# key => any key
# }
# }
# }
Download (0.014MB)
Added: 2006-09-12 License: Perl Artistic License Price:
1137 downloads
OpenCCG 0.9.0
OpenCCG project is a collection of natural language processing components. more>>
OpenCCG project is a collection of natural language processing components.
OpenCCG, the OpenNLP CCG Library, is a collection of natural language processing components and tools which provide support for parsing and realization with Combinatory Categorial Grammar (CCG).
Enhancements:
- Refactored realizer to put all no-sem edges on the agenda, which requires making an exception for edges with no indices in the implementation of the index filter, but otherwise yields a more uniform approach to creating edges.
- Refactored realizer to use representative edges (one per cat) instead of edge groups, which ends up being simpler on the whole and should be easier to explain.
- Refactored categories to allow for equality checks with and without taking the LFs into consideration.
- Refactored edge equiv classes to use coverage bit vector and cat sans LF to check equality.
- Refactored lex instantiation to produce all possible instantiations that respect the alt exclusivity constraints.
- Changed Sign, DerivationHistory to store rule object.
- Changed alt edge construction to create new LF from input signs and rule, since signs in equiv class of alts can now have different LFs.
- Added active alt tracking and completing of edges with optional bits.
- Changed HyloVar to check for equal types when checking for equality up to var renaming.
- Refactored generics to avoid type warnings in Eclipse.
- Relaxed LF chunking constraints to allow combinations with edges (or trackers more generally) that are shared across multiple alt set options.
- Added "shared" attribute to nominal terms to indicate references to nodes that are shared across alternatives in a disjunctive LF; then revamped and reinforced the LF chunking constraints.
- Fixed problem with signMap not pointing to opt-completed edge.
- Improved edge printing from realizer chart to show derivations.
- Updated realizer to keep edges whose signs have the simplest derivation, among those with the same surface words.
- Added filter for ungrammatical test cases in ccg-test text output.
- Added first draft of realizer manual.
<<lessOpenCCG, the OpenNLP CCG Library, is a collection of natural language processing components and tools which provide support for parsing and realization with Combinatory Categorial Grammar (CCG).
Enhancements:
- Refactored realizer to put all no-sem edges on the agenda, which requires making an exception for edges with no indices in the implementation of the index filter, but otherwise yields a more uniform approach to creating edges.
- Refactored realizer to use representative edges (one per cat) instead of edge groups, which ends up being simpler on the whole and should be easier to explain.
- Refactored categories to allow for equality checks with and without taking the LFs into consideration.
- Refactored edge equiv classes to use coverage bit vector and cat sans LF to check equality.
- Refactored lex instantiation to produce all possible instantiations that respect the alt exclusivity constraints.
- Changed Sign, DerivationHistory to store rule object.
- Changed alt edge construction to create new LF from input signs and rule, since signs in equiv class of alts can now have different LFs.
- Added active alt tracking and completing of edges with optional bits.
- Changed HyloVar to check for equal types when checking for equality up to var renaming.
- Refactored generics to avoid type warnings in Eclipse.
- Relaxed LF chunking constraints to allow combinations with edges (or trackers more generally) that are shared across multiple alt set options.
- Added "shared" attribute to nominal terms to indicate references to nodes that are shared across alternatives in a disjunctive LF; then revamped and reinforced the LF chunking constraints.
- Fixed problem with signMap not pointing to opt-completed edge.
- Improved edge printing from realizer chart to show derivations.
- Updated realizer to keep edges whose signs have the simplest derivation, among those with the same surface words.
- Added filter for ungrammatical test cases in ccg-test text output.
- Added first draft of realizer manual.
Download (4.9MB)
Added: 2006-10-19 License: LGPL (GNU Lesser General Public License) Price:
1102 downloads
Env::Path 0.18
Env::Path is a Perl module with advanced operations on path variables. more>>
Env::Path is a Perl module with advanced operations on path variables.
SYNOPSIS
use Env::Path;
# basic usage
my $manpath = Env::Path->MANPATH;
$manpath->Append(/opt/samba/man);
for ($manpath->List) { print $_, "n" };
# similar to above using the "implicit object" shorthand
Env::Path->MANPATH;
MANPATH->Append(/opt/samba/man);
for (MANPATH->List) { print $_, "n" };
# one-shot use
Env::Path->PATH->Append(/usr/sbin);
# change instances of /usr/local/bin to an architecture-specific dir
Env::Path->PATH->Replace(/usr/local/bin, "/usr/local/$ENV{PLATFORM}/bin");
# more complex use (different names for same semantics)
my $libpath;
if ($^O =~ /aix/) {
$libpath = Env::Path->LIBPATH;
} else {
$libpath = Env::Path->LD_LIBRARY_PATH;
}
$libpath->Assign(qw(/usr/lib /usr/openwin/lib));
$libpath->Prepend(/usr/ucblib) unless $libpath->Contains(/usr/ucblib);
$libpath->InsertAfter(/usr/ucblib, /xx/yy/zz);
$libpath->Uniqify;
$libpath->DeleteNonexistent;
$libpath->Remove(/usr/local/lib);
print $libpath->Name, ":";
for ($libpath->List) { print " $_" };
print "n";
# simplest usage: bless all existing EVs as Env::Path objects
use Env::Path :all;
my @cats = PATH->Whence(cat*);
print "@catsn";
<<lessSYNOPSIS
use Env::Path;
# basic usage
my $manpath = Env::Path->MANPATH;
$manpath->Append(/opt/samba/man);
for ($manpath->List) { print $_, "n" };
# similar to above using the "implicit object" shorthand
Env::Path->MANPATH;
MANPATH->Append(/opt/samba/man);
for (MANPATH->List) { print $_, "n" };
# one-shot use
Env::Path->PATH->Append(/usr/sbin);
# change instances of /usr/local/bin to an architecture-specific dir
Env::Path->PATH->Replace(/usr/local/bin, "/usr/local/$ENV{PLATFORM}/bin");
# more complex use (different names for same semantics)
my $libpath;
if ($^O =~ /aix/) {
$libpath = Env::Path->LIBPATH;
} else {
$libpath = Env::Path->LD_LIBRARY_PATH;
}
$libpath->Assign(qw(/usr/lib /usr/openwin/lib));
$libpath->Prepend(/usr/ucblib) unless $libpath->Contains(/usr/ucblib);
$libpath->InsertAfter(/usr/ucblib, /xx/yy/zz);
$libpath->Uniqify;
$libpath->DeleteNonexistent;
$libpath->Remove(/usr/local/lib);
print $libpath->Name, ":";
for ($libpath->List) { print " $_" };
print "n";
# simplest usage: bless all existing EVs as Env::Path objects
use Env::Path :all;
my @cats = PATH->Whence(cat*);
print "@catsn";
Download (0.010MB)
Added: 2007-04-14 License: Perl Artistic License Price:
924 downloads
filofant 1.1.5
filofant project is a mail archiving and document indexing software. more>>
filofant project is a mail archiving and document indexing software intended for using in companies or workgroups which wants to share the knowledge embedded in their documents and emails.
Installation:
Currently there is no installscript, so you have to do all at your own...
1) Binaries
configure && make & make install
in the src directory.
It is recommended to provide an prefix for the installation like --prefix=/opt/filofant
2) CGIs
The CGIs will be installed in $PREFIX/bin/cgi-bin. If this is not the cgi-directory of your webserver, you should move them there.
3) Environment
filofant needs the variable FILOFANT_HOME to declared, to find its config and binary files. It this variable is not defined, the base config has to be stored at /etc/filofant.rc
This variable has to be set for the CGI also, eg in Apache you could set it with the SetEnv directive.
4) System
Create a systemuser for the filofant (eg. filofant). The user has to be access to the base directory ($FILOFANT_HOME) of the installation.
5) Database
PostgreSQL: Create a database with the createdb command, create an user of the same name as the system user with the createuser command (This user has to be database administrator).
su to the filofant user. Insert database schema from the file filofant.sql (in directory sql) If you have nonstandard system user for the webserver or the filofant, please correct the grants in the sql file before inserting it.
6) Base configuration
The file filofant.rc has to be located in the directory $FILOFANT_HOME/etc. Edit (or create) this file and enter the following lines:
BaseDir=/opt/filofant
User=filofant
DBUser=filofant
DBName=filofant
Fill in the appropriate data. I you have password protection at the database or the database is not at the same machine, add the following lines:
DBPwd=
DBPort=
DBHost=
Enhancements:
- A new binary for resolving system variables without password query changes access to system settings in scripts for cronjobs.
- This allows a tighter security setting for the database.
- Internal references in HTML previews will now be translated correctly to the filofant preview page.
- A bug regarding the embedding of images in HTML previews has been fixed.
- When using the fulltext search engine with more than one stopword, only the first was detected.
- This has been fixed.
<<lessInstallation:
Currently there is no installscript, so you have to do all at your own...
1) Binaries
configure && make & make install
in the src directory.
It is recommended to provide an prefix for the installation like --prefix=/opt/filofant
2) CGIs
The CGIs will be installed in $PREFIX/bin/cgi-bin. If this is not the cgi-directory of your webserver, you should move them there.
3) Environment
filofant needs the variable FILOFANT_HOME to declared, to find its config and binary files. It this variable is not defined, the base config has to be stored at /etc/filofant.rc
This variable has to be set for the CGI also, eg in Apache you could set it with the SetEnv directive.
4) System
Create a systemuser for the filofant (eg. filofant). The user has to be access to the base directory ($FILOFANT_HOME) of the installation.
5) Database
PostgreSQL: Create a database with the createdb command, create an user of the same name as the system user with the createuser command (This user has to be database administrator).
su to the filofant user. Insert database schema from the file filofant.sql (in directory sql) If you have nonstandard system user for the webserver or the filofant, please correct the grants in the sql file before inserting it.
6) Base configuration
The file filofant.rc has to be located in the directory $FILOFANT_HOME/etc. Edit (or create) this file and enter the following lines:
BaseDir=/opt/filofant
User=filofant
DBUser=filofant
DBName=filofant
Fill in the appropriate data. I you have password protection at the database or the database is not at the same machine, add the following lines:
DBPwd=
DBPort=
DBHost=
Enhancements:
- A new binary for resolving system variables without password query changes access to system settings in scripts for cronjobs.
- This allows a tighter security setting for the database.
- Internal references in HTML previews will now be translated correctly to the filofant preview page.
- A bug regarding the embedding of images in HTML previews has been fixed.
- When using the fulltext search engine with more than one stopword, only the first was detected.
- This has been fixed.
Download (3.1MB)
Added: 2007-01-22 License: GPL (GNU General Public License) Price:
1005 downloads
SLAMPP Lite 2.0
SLAMPPLite is a linux live CD that will turn your personal computer to a simple home server. more>>
SLAMPPLite is a linux live CD that will turn your personal computer to a simple home server.
What makes it different is that SLAMPPLite has smaller size that will fit into a 256 MB compact disk or usb stick. It contains only essential server applications like Apache, MySQL, ProFTPD, BIND, DHCPD, SSH and mail server.
Several programming languages such as PHP, Perl and Python and other tools to support your web development work are also included.
To keep SLAMPPLite slim and make it easy to update the applications, SLAMPPLite uses server suite provided by XAMPP.
SLAMPPLite is compiled intended to be your showcase box. So, when you have something to show to your (potential) users or clients, just put your web applications on SLAMPPLite and you will have an instant mobile portfolio.
Therefore I advise you not to use SLAMPPLite for production purpose, just use the standard SLAMPP instead. Although through some tweaks here and there, SLAMPPLite is also ready for that. Please remember, SLAMPPLite comes with ABSOLUTELY NO WARRANTY. It is provided as AS IS product. Please use it at your own risk.
Main features:
- Linux kernel: 2.6.16
- Desktop: Xfce 4.2.2
- Web, FTP and database servers: XAMPP 1.5.1
- Other servers: BIND, DHCP, Sendmail. Dovecot, SSH
- Programming:
- Languages: PHP 4.4.1/5.0.5, Perl 5.8.7, Python 2.4.1
- Editor: Bluefish 1.0.4
- Office: Xpdf
- Graphics: Xpaint
- Multimedia: Beep Media Player, BashBurn
- Network: Nmap, Putty, BitTorrent 4.2.1 (tracker/client), FTP client, Firestarter firewall
- Internet: Mozilla Firefox 1.5, Sylpheed 2.0.4, Gaim 1.5.0
- Package management: pkgtool, slapt-get/gslapt
- Antivirus: ClamAV 0.87.1, FetCav (GUI)
- Utilities: GParted, EmelFM2, Dufie, htop, rkhunter, Qemu, backup system and hard disk installation scripts
- Complete list of packages can be found over here, SLitePackages.
Enhancements:
- Updated and upgraded existing applications included in previous SLAMPPLite Live CD
- Powered by XAMPP 1.5.1 and now it exists as module (xampp_1_5_1.mo)
- Based on Slackware current
- Used linux kernel 2.6.16
- Compiled with Linux Live scripts 5.4.1
- Added NASLite File Servers applications of Server Elements for SMB, FTP and NFS. They can be found under /tools directory of CD.
- Added Abiword 2.4.1
- Added Freerock GNOME support via slapt-get
- New hard disk installation program provided by Nonux
- Web documents installation scripts is now separated from XAMPP boot scripts. You can execute it from Xfce menu, or manually: # bash /opt/slampp/install.sh
- Fixed fstab
<<lessWhat makes it different is that SLAMPPLite has smaller size that will fit into a 256 MB compact disk or usb stick. It contains only essential server applications like Apache, MySQL, ProFTPD, BIND, DHCPD, SSH and mail server.
Several programming languages such as PHP, Perl and Python and other tools to support your web development work are also included.
To keep SLAMPPLite slim and make it easy to update the applications, SLAMPPLite uses server suite provided by XAMPP.
SLAMPPLite is compiled intended to be your showcase box. So, when you have something to show to your (potential) users or clients, just put your web applications on SLAMPPLite and you will have an instant mobile portfolio.
Therefore I advise you not to use SLAMPPLite for production purpose, just use the standard SLAMPP instead. Although through some tweaks here and there, SLAMPPLite is also ready for that. Please remember, SLAMPPLite comes with ABSOLUTELY NO WARRANTY. It is provided as AS IS product. Please use it at your own risk.
Main features:
- Linux kernel: 2.6.16
- Desktop: Xfce 4.2.2
- Web, FTP and database servers: XAMPP 1.5.1
- Other servers: BIND, DHCP, Sendmail. Dovecot, SSH
- Programming:
- Languages: PHP 4.4.1/5.0.5, Perl 5.8.7, Python 2.4.1
- Editor: Bluefish 1.0.4
- Office: Xpdf
- Graphics: Xpaint
- Multimedia: Beep Media Player, BashBurn
- Network: Nmap, Putty, BitTorrent 4.2.1 (tracker/client), FTP client, Firestarter firewall
- Internet: Mozilla Firefox 1.5, Sylpheed 2.0.4, Gaim 1.5.0
- Package management: pkgtool, slapt-get/gslapt
- Antivirus: ClamAV 0.87.1, FetCav (GUI)
- Utilities: GParted, EmelFM2, Dufie, htop, rkhunter, Qemu, backup system and hard disk installation scripts
- Complete list of packages can be found over here, SLitePackages.
Enhancements:
- Updated and upgraded existing applications included in previous SLAMPPLite Live CD
- Powered by XAMPP 1.5.1 and now it exists as module (xampp_1_5_1.mo)
- Based on Slackware current
- Used linux kernel 2.6.16
- Compiled with Linux Live scripts 5.4.1
- Added NASLite File Servers applications of Server Elements for SMB, FTP and NFS. They can be found under /tools directory of CD.
- Added Abiword 2.4.1
- Added Freerock GNOME support via slapt-get
- New hard disk installation program provided by Nonux
- Web documents installation scripts is now separated from XAMPP boot scripts. You can execute it from Xfce menu, or manually: # bash /opt/slampp/install.sh
- Fixed fstab
Download (239.8MB)
Added: 2006-04-10 License: GPL (GNU General Public License) Price:
1301 downloads
Potracegui 1.3.4
Potracegui is a GUI interface for potrace and autotrace two programs for tracing bitmapped images. more>>
Potracegui is a GUI interface for potrace and autotrace, two programs for tracing bitmapped images.
It really doesnt do much, all the dirt work is done by potrace and autotrace, my app is simply an interface: it collects informations in an easy way (hopefully) and then it launches potrace or autotrace with all the relevant options.
Potrace and autotrace, on the contrary, are great apps for tracing so that they can be scaled, rotated, and transformed in general, without loss of quality.
Well, using a GUI sometimes is more comfortable (particularly if working with images), even if Im a strong supporter of command-line programs. On the other hand, Potracegui (thanks to Jakub Stachowski) can now load remote files (web, ftp...), use any image format recognized by KDE (potrace uses only a few bitmapped formats) and support drag and drop.
Installation:
Potracegui is installed with the usual:
./configure
make
su
make install
Installation on SuSE linux + kde 3.1 or KDE 3.2
If you are using SuSE, you have to specify to configure the directory where KDE is installed (/opt/kde3):
./configure --prefix=/opt/kde3
make
su
make install
Installation on Mandrake 9.2 with KDE3.2:
If you are using Mandrake and NVIDIA drivers, you have to consider two problems before compiling Potracegui:
Potracegui expects to find the library /usr/X11R6/lib/libGL.la, but in this distribution the library is installed in /usr/lib/libGL.la. All you have to do is symlink it:
cd /usr/X11R6/lib
ln -s /usr/lib/libGL.la .
Enhancements:
- Quick bugfix: deleted debug() method from options.cpp
<<lessIt really doesnt do much, all the dirt work is done by potrace and autotrace, my app is simply an interface: it collects informations in an easy way (hopefully) and then it launches potrace or autotrace with all the relevant options.
Potrace and autotrace, on the contrary, are great apps for tracing so that they can be scaled, rotated, and transformed in general, without loss of quality.
Well, using a GUI sometimes is more comfortable (particularly if working with images), even if Im a strong supporter of command-line programs. On the other hand, Potracegui (thanks to Jakub Stachowski) can now load remote files (web, ftp...), use any image format recognized by KDE (potrace uses only a few bitmapped formats) and support drag and drop.
Installation:
Potracegui is installed with the usual:
./configure
make
su
make install
Installation on SuSE linux + kde 3.1 or KDE 3.2
If you are using SuSE, you have to specify to configure the directory where KDE is installed (/opt/kde3):
./configure --prefix=/opt/kde3
make
su
make install
Installation on Mandrake 9.2 with KDE3.2:
If you are using Mandrake and NVIDIA drivers, you have to consider two problems before compiling Potracegui:
Potracegui expects to find the library /usr/X11R6/lib/libGL.la, but in this distribution the library is installed in /usr/lib/libGL.la. All you have to do is symlink it:
cd /usr/X11R6/lib
ln -s /usr/lib/libGL.la .
Enhancements:
- Quick bugfix: deleted debug() method from options.cpp
Download (0.71MB)
Added: 2005-07-18 License: GPL (GNU General Public License) Price:
1560 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 opt 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
