jformdesigner tutorial
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 245
Derbrill Tutorials
Derbrill Tutorials are Free Tutorials For Writing Games and Multimedia Applications in Runtime Revolution with ArcadeEngine. more>>
Derbrill Tutorials are Free Tutorials For Writing Games and Multimedia Applications in Runtime Revolution with ArcadeEngine.
The tutorials come in a visually appealing e-book format which is both easy to read and use, the range of topics covered includes:
* The basics of Revolution such as: stacks, cards, scripts, messages and timers
* How to use geometric properties such as distances, angles and intersection rectangles
* Understanding and using different movements including linear, polygonal, circular and elliptic
* Advanced use of images
* Using the built-in collision detection
<<lessThe tutorials come in a visually appealing e-book format which is both easy to read and use, the range of topics covered includes:
* The basics of Revolution such as: stacks, cards, scripts, messages and timers
* How to use geometric properties such as distances, angles and intersection rectangles
* Understanding and using different movements including linear, polygonal, circular and elliptic
* Advanced use of images
* Using the built-in collision detection
Download (4.2MB)
Added: 2005-10-17 License: Freeware Price:
1470 downloads
Imager::Tutorial 0.54
Imager::Tutorial is an introduction to Imager. more>>
Imager::Tutorial is an introduction to Imager.
Before you start
If you have the necessary knowledge, install the image format libraries you want Imager image file support for, and Imager itself, otherwise arrange to have it done.
You will also want some sort of image viewer tool, whether an image editor like Photoshop or the GIMP, or a web browser.
Hello Boxes! - A Simple Start
As with any perl program its useful to start with a #! line, and to enable strict mode:
#!/usr/bin/perl -w
# you might to use warnings; instead of the -w above
use strict;
These lines will be omitted in further examples.
As with any module, you need to load it:
use Imager;
Now create a image to draw on:
my $image = Imager->new(xsize => 100, ysize => 100);
and draw a couple of filled rectangles on it:
$image->box(xmin => 0, ymin => 0, xmax => 99, ymax => 99,
filled => 1, color => blue);
$image->box(xmin => 20, ymin => 20, xmax => 79, ymax => 79,
filled => 1, color => green);
Since the first box fills the whole image, it can be simplified to:
$image->box(filled => 1, color => blue);
and save it to a file:
$image->write(file=>tutorial1.ppm)
or die Cannot save tutorial1.ppm: , $image->errstr;
So our completed program is:
use Imager;
my $image = Imager->new(xsize => 100, ysize => 100);
$image->box(filled => 1, color => blue);
$image->box(xmin => 20, ymin => 20, xmax => 79, ymax => 79,
filled => 1, color => green);
$image->write(file=>tutorial1.ppm)
or die Cannot save tutorial1.ppm: , $image->errstr;
<<lessBefore you start
If you have the necessary knowledge, install the image format libraries you want Imager image file support for, and Imager itself, otherwise arrange to have it done.
You will also want some sort of image viewer tool, whether an image editor like Photoshop or the GIMP, or a web browser.
Hello Boxes! - A Simple Start
As with any perl program its useful to start with a #! line, and to enable strict mode:
#!/usr/bin/perl -w
# you might to use warnings; instead of the -w above
use strict;
These lines will be omitted in further examples.
As with any module, you need to load it:
use Imager;
Now create a image to draw on:
my $image = Imager->new(xsize => 100, ysize => 100);
and draw a couple of filled rectangles on it:
$image->box(xmin => 0, ymin => 0, xmax => 99, ymax => 99,
filled => 1, color => blue);
$image->box(xmin => 20, ymin => 20, xmax => 79, ymax => 79,
filled => 1, color => green);
Since the first box fills the whole image, it can be simplified to:
$image->box(filled => 1, color => blue);
and save it to a file:
$image->write(file=>tutorial1.ppm)
or die Cannot save tutorial1.ppm: , $image->errstr;
So our completed program is:
use Imager;
my $image = Imager->new(xsize => 100, ysize => 100);
$image->box(filled => 1, color => blue);
$image->box(xmin => 20, ymin => 20, xmax => 79, ymax => 79,
filled => 1, color => green);
$image->write(file=>tutorial1.ppm)
or die Cannot save tutorial1.ppm: , $image->errstr;
Download (0.83MB)
Added: 2006-10-27 License: Perl Artistic License Price:
1094 downloads
KDE Simple Programming Tutorial 1.2
KDE Simple Programming Tutorial is a tutorial for developing a KDE application. more>>
KDE Simple Programming Tutorial is a tutorial for developing a KDE application.
With the only requirement of a little C++ knowledge, and using the latest KDE snapshots, the reader will learn how to build his/her first KDE application from a simple "Hello world" button to a Web browser with a DCOP interface that communicates with a bookmark application running in a separate process.
Theres also a spanish and a romanian version of the documentation.
<<lessWith the only requirement of a little C++ knowledge, and using the latest KDE snapshots, the reader will learn how to build his/her first KDE application from a simple "Hello world" button to a Web browser with a DCOP interface that communicates with a bookmark application running in a separate process.
Theres also a spanish and a romanian version of the documentation.
Download (MB)
Added: 2006-10-04 License: GPL (GNU General Public License) Price:
1121 downloads
RiveScript::Tutorial 1.02
RiveScript::Tutorial is a beginners guide to creating their first RiveScript brain. more>>
RiveScript::Tutorial is a beginners guide to creating their first RiveScript brain.
This tutorial outlines the various capabilities of the RiveScript specification and offers some recommended pointers for creating a well-formed RiveScript brain. What you do with this knowledge is up to you; be creative!
Be sure to skim over the RiveScript manpage first, because this tutorial jumps right in to using the various RiveScript commands without always explaining what each of them do.
A Simple RiveScript Interpreter
Here is a simple Perl script for running a RiveScript interpreter. This assumes that the brains RS files will be stored in a directory called "tutorial", local to the Perl script. Youd want to edit certain parameters in this code if you see fit.
#!/usr/bin/perl -w
use strict;
use warnings;
use RiveScript;
# Create the RiveScript interpreter.
my $rive = new RiveScript();
# Load the RS tutorial brain.
$rive->loadDirectory ("./tutorial");
# Sort them.
$rive->sortReplies;
# Go into a chatting loop.
while (1) {
print "User> ";
my $msg = ;
chomp $msg;
# Grab a reply.
my @reply = $rive->reply (user,$msg);
print " Bot> $_n" foreach(@reply);
}
<<lessThis tutorial outlines the various capabilities of the RiveScript specification and offers some recommended pointers for creating a well-formed RiveScript brain. What you do with this knowledge is up to you; be creative!
Be sure to skim over the RiveScript manpage first, because this tutorial jumps right in to using the various RiveScript commands without always explaining what each of them do.
A Simple RiveScript Interpreter
Here is a simple Perl script for running a RiveScript interpreter. This assumes that the brains RS files will be stored in a directory called "tutorial", local to the Perl script. Youd want to edit certain parameters in this code if you see fit.
#!/usr/bin/perl -w
use strict;
use warnings;
use RiveScript;
# Create the RiveScript interpreter.
my $rive = new RiveScript();
# Load the RS tutorial brain.
$rive->loadDirectory ("./tutorial");
# Sort them.
$rive->sortReplies;
# Go into a chatting loop.
while (1) {
print "User> ";
my $msg = ;
chomp $msg;
# Grab a reply.
my @reply = $rive->reply (user,$msg);
print " Bot> $_n" foreach(@reply);
}
Download (0.20MB)
Added: 2006-12-06 License: Perl Artistic License Price:
1064 downloads
Prima::tutorial 1.20
Prima::tutorial is an introductory tutorial. more>>
Prima::tutorial is an introductory tutorial.
Programming graphic interfaces is often considered somewhat boring, and not without a cause. It is a small pride in knowing that your buttons and scrollbars work exactly as millions of others buttons and scrollbars do, so whichever GUI toolkit is chosen, it is usually regarded as a tool of small importance, and the less obtrusive, the better.
Given that, and trying to live up to the famous Perl making easy things easy and hard things possible mantra, this manual page is an introductory tutorial meant to show how to write easy things easy. The hard things are explained in the other Prima manual pages ( see Prima ).
<<lessProgramming graphic interfaces is often considered somewhat boring, and not without a cause. It is a small pride in knowing that your buttons and scrollbars work exactly as millions of others buttons and scrollbars do, so whichever GUI toolkit is chosen, it is usually regarded as a tool of small importance, and the less obtrusive, the better.
Given that, and trying to live up to the famous Perl making easy things easy and hard things possible mantra, this manual page is an introductory tutorial meant to show how to write easy things easy. The hard things are explained in the other Prima manual pages ( see Prima ).
Download (1.4MB)
Added: 2006-08-24 License: Perl Artistic License Price:
1162 downloads
Sub::Exporter::Tutorial 0.970
Sub::Exporter::Tutorial is a friendly guide to exporting with Sub::Exporter. more>>
Sub::Exporter::Tutorial is a friendly guide to exporting with Sub::Exporter.
Whats an Exporter?
When you use a module, first it is required, then its import method is called. The Perl documentation tells us that the following two lines are equivalent:
use Module LIST;
BEGIN { require Module; Module->import(LIST); }
The import method is the modules exporter.
The Basics of Sub::Exporter
Sub::Exporter builds a custom exporter which can then be installed into your module. It builds this method based on configuration passed to its setup_exporter method.
A very basic use case might look like this:
package Addition;
use Sub::Exporter;
Sub::Exporter::setup_exporter({ exports => [ qw(plus) ]});
sub plus { my ($x, $y) = @_; return $x + $y; }
This would mean that when someone used your Addition module, they could have its plus routine imported into their package:
use Addition qw(plus);
my $z = plus(2, 2); # this works, because now plus is in the main package
That syntax to set up the exporter, above, is a little verbose, so for the simple case of just naming some exports, you can write this:
use Sub::Exporter -setup => { exports => [ qw(plus) ] };
...which is the same as the original example -- except that now the exporter is built and installed at compile time. Well, that and you typed less.
Using Export Groups
You can specify whole groups of things that should be exportable together. These are called groups. Exporter calls these tags. To specify groups, you just pass a groups key in your exporter configuration:
package Food;
use Sub::Exporter -setup => {
exports => [ qw(apple banana beef fluff lox rabbit) ],
groups => {
fauna => [ qw(beef lox rabbit) ],
flora => [ qw(apple banana) ],
}
};
Now, to import all that delicious foreign meat, your consumer needs only to write:
use Food qw(:fauna);
use Food qw(-fauna);
Either one of the above is acceptable. A colon is more traditional, but barewords with a leading colon cant be enquoted by a fat arrow. Well see why that matters later on.
Groups can contain other groups. If you include a group name (with the leading dash or colon) in a group definition, it will be expanded recursively when the exporter is called. The exporter will not recurse into the same group twice while expanding groups.
There are two special groups: all and default. The all group is defined by default, and contains all exportable subs. You can redefine it, if you want to export only a subset when all exports are requested. The default group is the set of routines to export when nothing specific is requested. By default, there is no default group.
<<lessWhats an Exporter?
When you use a module, first it is required, then its import method is called. The Perl documentation tells us that the following two lines are equivalent:
use Module LIST;
BEGIN { require Module; Module->import(LIST); }
The import method is the modules exporter.
The Basics of Sub::Exporter
Sub::Exporter builds a custom exporter which can then be installed into your module. It builds this method based on configuration passed to its setup_exporter method.
A very basic use case might look like this:
package Addition;
use Sub::Exporter;
Sub::Exporter::setup_exporter({ exports => [ qw(plus) ]});
sub plus { my ($x, $y) = @_; return $x + $y; }
This would mean that when someone used your Addition module, they could have its plus routine imported into their package:
use Addition qw(plus);
my $z = plus(2, 2); # this works, because now plus is in the main package
That syntax to set up the exporter, above, is a little verbose, so for the simple case of just naming some exports, you can write this:
use Sub::Exporter -setup => { exports => [ qw(plus) ] };
...which is the same as the original example -- except that now the exporter is built and installed at compile time. Well, that and you typed less.
Using Export Groups
You can specify whole groups of things that should be exportable together. These are called groups. Exporter calls these tags. To specify groups, you just pass a groups key in your exporter configuration:
package Food;
use Sub::Exporter -setup => {
exports => [ qw(apple banana beef fluff lox rabbit) ],
groups => {
fauna => [ qw(beef lox rabbit) ],
flora => [ qw(apple banana) ],
}
};
Now, to import all that delicious foreign meat, your consumer needs only to write:
use Food qw(:fauna);
use Food qw(-fauna);
Either one of the above is acceptable. A colon is more traditional, but barewords with a leading colon cant be enquoted by a fat arrow. Well see why that matters later on.
Groups can contain other groups. If you include a group name (with the leading dash or colon) in a group definition, it will be expanded recursively when the exporter is called. The exporter will not recurse into the same group twice while expanding groups.
There are two special groups: all and default. The all group is defined by default, and contains all exportable subs. You can redefine it, if you want to export only a subset when all exports are requested. The default group is the set of routines to export when nothing specific is requested. By default, there is no default group.
Download (0.034MB)
Added: 2006-10-16 License: Perl Artistic License Price:
1104 downloads
Test::Unit::Tutorial 0.14
Test::Unit::Tutorial is a Perl module that contains a tutorial on unit testing. more>>
Test::Unit::Tutorial is a Perl module that contains a tutorial on unit testing.
SYNOPSIS
perldoc Test::Unit::Tutorial
Here should be extensive documentation on what unit testing is, why it is useful, and how to do it with the Test::Unit collection of modules.
Sorry for not implementing this yet.
Please have a look at the examples in the examples directory and read the README file that came with this distribution.
A short tutorial on how to use the unit testing framework is included in Test::Unit::TestCase.
Further examples can be found by looking at the self test collection, starting in Test::Unit::tests::AllTests.
<<lessSYNOPSIS
perldoc Test::Unit::Tutorial
Here should be extensive documentation on what unit testing is, why it is useful, and how to do it with the Test::Unit collection of modules.
Sorry for not implementing this yet.
Please have a look at the examples in the examples directory and read the README file that came with this distribution.
A short tutorial on how to use the unit testing framework is included in Test::Unit::TestCase.
Further examples can be found by looking at the self test collection, starting in Test::Unit::tests::AllTests.
Download (0.044MB)
Added: 2007-06-13 License: Perl Artistic License Price:
863 downloads
DateTime::Format::Builder::Tutorial 0.7807
DateTime::Format::Builder::Tutorial is a quick class on using Builder. more>>
DateTime::Format::Builder::Tutorial is a quick class on using Builder.
CREATING A CLASS
As most people who are writing modules know, you start a package with a package declaration and some indication of module version:
package DateTime::Format::ICal;
our $VERSION = 0.04;
After that, you call Builder with some options. There are only a few (detailed later). Right now, were only interested in parsers.
use DateTime::Format::Builder
(
parsers => {
...
}
);
The parsers option takes a reference to a hash of method names and specifications:
parsers => {
parse_datetime => ... ,
parse_datetime_with_timezone => ... ,
...
}
Builder will create methods in your class, each method being a parser that follows the given specifications. It is strongly recommended that one method is called parse_datetime, be it a Builder created method or one of your own.
In addition to creating any of the parser methods it also creates a new() method that can instantiate (or clone) objects of this class. This behaviour can be modified with the constructor option, but we dont need to know that yet.
Each value corresponding to a method name in the parsers list is either a single specification, or a list of specifications. Well start with the simple case.
parse_briefdate => {
params => [ qw( year month day ) ],
regex => qr/^(dddd)(dd)(dd)$/,
},
This will result in a method named parse_briefdate which will take strings in the form 20040716 and return DateTime objects representing that date. A user of the class might write:
use DateTime::Format::ICal;
my $date = "19790716";
my $dt = DateTime::Format::ICal->parse_briefdate( $date );
print "My birth month is ", $dt->month_name, "n";
The regex is applied to the input string, and if it matches, then $1, $2, ... are mapped to the params given and handed to DateTime->new(). Essentially:
my $rv = DateTime->new( year => $1, month => $2, day => $3 );
There are more complicated things one can do within a single specification, but well cover those later.
Often, youll want a method to be able to take one string, and run it against multiple parser specifications. It would be very irritating if the user had to work out what format the datetime string was in and then which method was most appropriate.
So, Builder lets you specify multiple specifications:
parse_datetime => [
{
params => [ qw( year month day hour minute second ) ],
regex => qr/^(dddd)(dd)(dd)T(dd)(dd)(dd)$/,
},
{
params => [ qw( year month day hour minute ) ],
regex => qr/^(dddd)(dd)(dd)T(dd)(dd)$/,
},
{
params => [ qw( year month day hour ) ],
regex => qr/^(dddd)(dd)(dd)T(dd)$/,
},
{
params => [ qw( year month day ) ],
regex => qr/^(dddd)(dd)(dd)$/,
},
],
Its an arrayref of specifications. A parser will be created that will try each of these specifications sequentially, in the order you specified.
<<lessCREATING A CLASS
As most people who are writing modules know, you start a package with a package declaration and some indication of module version:
package DateTime::Format::ICal;
our $VERSION = 0.04;
After that, you call Builder with some options. There are only a few (detailed later). Right now, were only interested in parsers.
use DateTime::Format::Builder
(
parsers => {
...
}
);
The parsers option takes a reference to a hash of method names and specifications:
parsers => {
parse_datetime => ... ,
parse_datetime_with_timezone => ... ,
...
}
Builder will create methods in your class, each method being a parser that follows the given specifications. It is strongly recommended that one method is called parse_datetime, be it a Builder created method or one of your own.
In addition to creating any of the parser methods it also creates a new() method that can instantiate (or clone) objects of this class. This behaviour can be modified with the constructor option, but we dont need to know that yet.
Each value corresponding to a method name in the parsers list is either a single specification, or a list of specifications. Well start with the simple case.
parse_briefdate => {
params => [ qw( year month day ) ],
regex => qr/^(dddd)(dd)(dd)$/,
},
This will result in a method named parse_briefdate which will take strings in the form 20040716 and return DateTime objects representing that date. A user of the class might write:
use DateTime::Format::ICal;
my $date = "19790716";
my $dt = DateTime::Format::ICal->parse_briefdate( $date );
print "My birth month is ", $dt->month_name, "n";
The regex is applied to the input string, and if it matches, then $1, $2, ... are mapped to the params given and handed to DateTime->new(). Essentially:
my $rv = DateTime->new( year => $1, month => $2, day => $3 );
There are more complicated things one can do within a single specification, but well cover those later.
Often, youll want a method to be able to take one string, and run it against multiple parser specifications. It would be very irritating if the user had to work out what format the datetime string was in and then which method was most appropriate.
So, Builder lets you specify multiple specifications:
parse_datetime => [
{
params => [ qw( year month day hour minute second ) ],
regex => qr/^(dddd)(dd)(dd)T(dd)(dd)(dd)$/,
},
{
params => [ qw( year month day hour minute ) ],
regex => qr/^(dddd)(dd)(dd)T(dd)(dd)$/,
},
{
params => [ qw( year month day hour ) ],
regex => qr/^(dddd)(dd)(dd)T(dd)$/,
},
{
params => [ qw( year month day ) ],
regex => qr/^(dddd)(dd)(dd)$/,
},
],
Its an arrayref of specifications. A parser will be created that will try each of these specifications sequentially, in the order you specified.
Download (0.047MB)
Added: 2006-10-16 License: Perl Artistic License Price:
1103 downloads
XML::Smart::Tutorial 1.6.9
XML::Smart::Tutorial is a Perl module with tutorials and examples for XML::Smart. more>>
XML::Smart::Tutorial is a Perl module with tutorials and examples for XML::Smart.
SYNOPSIS
This document is a tutorial for XML::Smart and shows some examples of usual things.
<<lessSYNOPSIS
This document is a tutorial for XML::Smart and shows some examples of usual things.
Download (0.049MB)
Added: 2006-09-12 License: GPL (GNU General Public License) Price:
1144 downloads
Gantry::Docs::Tutorial 3.40
Gantry::Docs::Tutorial is a Perl module for The Gantry Tutorial. more>>
Gantry::Docs::Tutorial is a Perl module for The Gantry Tutorial.
Gantry is a mature web framework, released in late 2005 onto an unsuspecting world. For more information on the framework, its features and history, see Gantry::Docs::About.
Here we will explore the basic workings of Gantry by constructing a very simple application. Dont let the simplicity of this example fool you -- this framework has extreme flexibility in delivering applications with web and scripted components. The example in this document is only to get you started.
This document begins by describing a simple one-table management application. It walks through the process of building the application. Then, it shows a tool -- called Bigtop -- which can be used to build the application from a relatively small configuration file. Finally, it shows how to add another table and regenerate the app via Bigtop.
<<lessGantry is a mature web framework, released in late 2005 onto an unsuspecting world. For more information on the framework, its features and history, see Gantry::Docs::About.
Here we will explore the basic workings of Gantry by constructing a very simple application. Dont let the simplicity of this example fool you -- this framework has extreme flexibility in delivering applications with web and scripted components. The example in this document is only to get you started.
This document begins by describing a simple one-table management application. It walks through the process of building the application. Then, it shows a tool -- called Bigtop -- which can be used to build the application from a relatively small configuration file. Finally, it shows how to add another table and regenerate the app via Bigtop.
Download (0.19MB)
Added: 2006-09-26 License: Perl Artistic License Price:
1123 downloads
Template::Tutorial 2.15
Template::Tutorial are template toolkit tutorials. more>>
Template::Tutorial are template toolkit tutorials.
This section includes tutorials on using the Template Toolkit. Subjects currently include an general overview of the Template Toolkit, showing users how to get quickly up to speed building web content, and a tutorial on generating and using data files, with particular reference to XML.
Template::Tutorial::Web
Generating Web Content Using the Template Toolkit
This tutorial provides an introduction to the Template Toolkit and a "quick start" guide to getting up to speed. Its primarily focus is on using the Template Toolkit to build web content and it covers 4 basic areas: using tpage and ttree; using the Template.pm module in CGI scripts; writing Apache/mod_perl handlers; and extending the toolkit by writing plugins.
Template::Tutorial::Datafile
Creating Data Output Files Using the Template Toolkit
This tutorial gives an overview of the Template Toolkit, showing in particular how to use it to read and write data files in various different formats and styles. It was written by Dave Cross and first appeared as a lead article at http://www.perl.com/ earlier in the year (2001).
<<lessThis section includes tutorials on using the Template Toolkit. Subjects currently include an general overview of the Template Toolkit, showing users how to get quickly up to speed building web content, and a tutorial on generating and using data files, with particular reference to XML.
Template::Tutorial::Web
Generating Web Content Using the Template Toolkit
This tutorial provides an introduction to the Template Toolkit and a "quick start" guide to getting up to speed. Its primarily focus is on using the Template Toolkit to build web content and it covers 4 basic areas: using tpage and ttree; using the Template.pm module in CGI scripts; writing Apache/mod_perl handlers; and extending the toolkit by writing plugins.
Template::Tutorial::Datafile
Creating Data Output Files Using the Template Toolkit
This tutorial gives an overview of the Template Toolkit, showing in particular how to use it to read and write data files in various different formats and styles. It was written by Dave Cross and first appeared as a lead article at http://www.perl.com/ earlier in the year (2001).
Download (0.76MB)
Added: 2006-10-16 License: Perl Artistic License Price:
1107 downloads
IPTables-tutorial 1.2.2
IPTables-tutorials aim is to explain iptables in a complete and simple way. more>>
IPTables-tutorials aim is to explain iptables in a complete and simple way. The iptables-tutorial is currently rather stable, and contains information on all the currently available matches and targets (in kernel), as well as a couple of complete example scripts and explanations. It contains a complete section on iptables syntax, as well as other interesting commands such as iptables-save and iptables-restore.
The tutorial has recently been under heavy scrutiny and updating, as can be seen in this, the latest version of the tutorial. It is now also available in bookform from Lulu.com. If you feel like contributing or donating to the author of this tutorial, please do buy the book! Thank you!
If you need help, you are better off by asking the netfilter mailing list which you can reach at netfilter at lists.netfilter.org. For more information on this, visit the netfilter mailinglist page. You may also contact the linuxsecurity mailing list at security-discuss AT linuxsecurity dotcom. Both are fairly large, and should be able to help you much much better than I can.
<<lessThe tutorial has recently been under heavy scrutiny and updating, as can be seen in this, the latest version of the tutorial. It is now also available in bookform from Lulu.com. If you feel like contributing or donating to the author of this tutorial, please do buy the book! Thank you!
If you need help, you are better off by asking the netfilter mailing list which you can reach at netfilter at lists.netfilter.org. For more information on this, visit the netfilter mailinglist page. You may also contact the linuxsecurity mailing list at security-discuss AT linuxsecurity dotcom. Both are fairly large, and should be able to help you much much better than I can.
Download (9.0MB)
Added: 2006-11-22 License: (FDL) GNU Free Documentation License Price:
669 downloads
PAR::Tutorial 0.941
PAR::Tutorial is a cross-platform Packaging and Deployment with PAR. more>>
PAR::Tutorial is a cross-platform Packaging and Deployment with PAR.
SYNOPSIS
This is a tutorial on PAR, first appeared at the 7th Perl Conference. The HTML version of this tutorial is available online as http://aut.dyndns.org/par-tutorial/.
On Deploying Perl Applications
% sshnuke.pl 10.2.2.2 -rootpw="Z1ON0101"
Perl v5.6.1 required--this is only v5.6.0, stopped at sshnuke.pl line 1.
BEGIN failed--compilation aborted at sshnuke.pl line 1.
Q: "Help! I cant run your program!"
A1: Install Perl & perl -MCPAN -einstall(...)
How do we know which modules are needed?
New versions of CPAN modules may break sshnuke.pl
A2: Install Perl & tar zxf my_perllib.tgz
Possibly overwriting existing modules; not cross-platform at all
A3: Use the executable generated by perlcc sshnuke.pl
Impossible to debug; perlcc usually does not work anyway
<<lessSYNOPSIS
This is a tutorial on PAR, first appeared at the 7th Perl Conference. The HTML version of this tutorial is available online as http://aut.dyndns.org/par-tutorial/.
On Deploying Perl Applications
% sshnuke.pl 10.2.2.2 -rootpw="Z1ON0101"
Perl v5.6.1 required--this is only v5.6.0, stopped at sshnuke.pl line 1.
BEGIN failed--compilation aborted at sshnuke.pl line 1.
Q: "Help! I cant run your program!"
A1: Install Perl & perl -MCPAN -einstall(...)
How do we know which modules are needed?
New versions of CPAN modules may break sshnuke.pl
A2: Install Perl & tar zxf my_perllib.tgz
Possibly overwriting existing modules; not cross-platform at all
A3: Use the executable generated by perlcc sshnuke.pl
Impossible to debug; perlcc usually does not work anyway
Download (0.19MB)
Added: 2006-07-20 License: Perl Artistic License Price:
1194 downloads
JOpt.SDK Vehicle Routing Component 2.0.0 (Tutorial)
JOpt.SDK library is a routing software for Java that uses specialized genetic algorithms. more>>
JOpt.SDK library is a routing software for Java that uses specialized genetic algorithms to calculate an optimized allocation of orders and stops to mobile resources.
The algorithm not only provides tours at minimum costs but also considers an arbitrary set of constraints for each tour. You may define your own constraints and optimization goals in order to customize JOpt.SDK to your specific planning needs or you decide to use one of our best practices addons in order to achieve a fast application of our optimization algorithms to selected industries.
JOpt.SDK can solve nearly any problem that can be classified by one of the following types:
TSP - Traveling Salesman Problem. JOpt.SDK finds the shortest or fastest path for your mobile resources
VRPTW - Vehicle routing problem with time windows - like TSP but for a set of vehicles. JOpt.SDK finds an optimal allocation of orders and stops within a vehicle fleet. It may also consider different constraints for vehicles, drivers and stops.
JOpt.SDK functionality can be accessed via Java API and thus fits seamlessly into any JAVA application. Software developers may integrate the JOpt.SDK component into their application in order to offer their customers a consistent solution including optimization of mobile workforce schedules.
Enhancements:
- The tutorial has been revised to reflect some major API changes introduced since JOpt 2.0.0.
<<lessThe algorithm not only provides tours at minimum costs but also considers an arbitrary set of constraints for each tour. You may define your own constraints and optimization goals in order to customize JOpt.SDK to your specific planning needs or you decide to use one of our best practices addons in order to achieve a fast application of our optimization algorithms to selected industries.
JOpt.SDK can solve nearly any problem that can be classified by one of the following types:
TSP - Traveling Salesman Problem. JOpt.SDK finds the shortest or fastest path for your mobile resources
VRPTW - Vehicle routing problem with time windows - like TSP but for a set of vehicles. JOpt.SDK finds an optimal allocation of orders and stops within a vehicle fleet. It may also consider different constraints for vehicles, drivers and stops.
JOpt.SDK functionality can be accessed via Java API and thus fits seamlessly into any JAVA application. Software developers may integrate the JOpt.SDK component into their application in order to offer their customers a consistent solution including optimization of mobile workforce schedules.
Enhancements:
- The tutorial has been revised to reflect some major API changes introduced since JOpt 2.0.0.
Download (MB)
Added: 2007-05-08 License: Free For Educational Use Price:
903 downloads
Test::LectroTest::Tutorial 0.3500
Test::LectroTest::Tutorial is a Perl module that contains documentation on how to use LectroTest to test your software. more>>
Test::LectroTest::Tutorial is a Perl module that contains documentation on how to use LectroTest to test your software.
SYNOPSIS
LectroTest is an automated, specification-based testing system. To use it, declare properties that specify the expected behavior of your software. Then invoke LectroTest to test whether those properties hold.
LectroTest does this by running repeated random trials against your software. If LectroTest finds that a property doesnt hold, it emits the counterexample that "broke" your software. You can then plug the counterexample into your software to debug the problem. (Its also a good idea to add the counterexample to your list of regression tests.)
Think of your softwares behavior as a haystack that youre searching for needles. Each error is a needle. You want to find the needles and remove of them. LectroTest will search the haystack for you -- its nice that way -- but first you must tell it about the shape of the haystack and how to recognize a needle when it sees one.
The Haystack
The shape of the haystack is defined by a set of "generator bindings," in which variables are bound to the output of value generators:
x = 0;
The above asserts for each point in the haystack that the output of the function the_thing_we_are_testing must be non-negative.
Put them together to make a Property
The generator bindings and needle recognizer are combined to make a property:
Property {
##[ x = 0;
}, name => "the_thing_we_are_testing(...) is non-negative";
Youll note that we also added a meaningful name. Although not strictly required, its an excellent practice that makes life easier. (Youll also note that we placed the generator bindings inside of the magic delimiters ##[ ]##. This tells Perl that our bindings are bindings and not regular Perl code.)
We can read the above property like so: "For all integers x and all characters c in the range A through Z, we assert that the_thing_we_are_testing is non-negative."
Testing whether your Properties hold
After you define properties for your software, just add them to a small Perl program that uses the Test::LectroTest module:
# MyProperties.l.t
use MyModule; # provides the_thing_we_are_testing
use Test::LectroTest;
Property {
##[ x = 0;
}, name => "the_thing_we_are_testing(...) is non-negative";
Then you can test your properties simply by running the program:
$ perl MyProperties.l.t
If your properties check out, youll see something like this:
1..1
ok 1 - the_thing_we_are_testing(...) is non-negative (1000 attempts)
If something goes wrong, however, LectroTest will tell you where it happened:
1..1
not ok 1 - the_thing_we_are_testing(...) is non-negative
falsified in 23 attempts
# Counterexample:
# $x = 4
# $c = "R"
What this says is that at the point (x=4, c="R") in the haystack, there is a needle (i.e., your property doesnt hold). With this information, you can examine your code to determine the cause of the error.
<<lessSYNOPSIS
LectroTest is an automated, specification-based testing system. To use it, declare properties that specify the expected behavior of your software. Then invoke LectroTest to test whether those properties hold.
LectroTest does this by running repeated random trials against your software. If LectroTest finds that a property doesnt hold, it emits the counterexample that "broke" your software. You can then plug the counterexample into your software to debug the problem. (Its also a good idea to add the counterexample to your list of regression tests.)
Think of your softwares behavior as a haystack that youre searching for needles. Each error is a needle. You want to find the needles and remove of them. LectroTest will search the haystack for you -- its nice that way -- but first you must tell it about the shape of the haystack and how to recognize a needle when it sees one.
The Haystack
The shape of the haystack is defined by a set of "generator bindings," in which variables are bound to the output of value generators:
x = 0;
The above asserts for each point in the haystack that the output of the function the_thing_we_are_testing must be non-negative.
Put them together to make a Property
The generator bindings and needle recognizer are combined to make a property:
Property {
##[ x = 0;
}, name => "the_thing_we_are_testing(...) is non-negative";
Youll note that we also added a meaningful name. Although not strictly required, its an excellent practice that makes life easier. (Youll also note that we placed the generator bindings inside of the magic delimiters ##[ ]##. This tells Perl that our bindings are bindings and not regular Perl code.)
We can read the above property like so: "For all integers x and all characters c in the range A through Z, we assert that the_thing_we_are_testing is non-negative."
Testing whether your Properties hold
After you define properties for your software, just add them to a small Perl program that uses the Test::LectroTest module:
# MyProperties.l.t
use MyModule; # provides the_thing_we_are_testing
use Test::LectroTest;
Property {
##[ x = 0;
}, name => "the_thing_we_are_testing(...) is non-negative";
Then you can test your properties simply by running the program:
$ perl MyProperties.l.t
If your properties check out, youll see something like this:
1..1
ok 1 - the_thing_we_are_testing(...) is non-negative (1000 attempts)
If something goes wrong, however, LectroTest will tell you where it happened:
1..1
not ok 1 - the_thing_we_are_testing(...) is non-negative
falsified in 23 attempts
# Counterexample:
# $x = 4
# $c = "R"
What this says is that at the point (x=4, c="R") in the haystack, there is a needle (i.e., your property doesnt hold). With this information, you can examine your code to determine the cause of the error.
Download (0.053MB)
Added: 2007-01-09 License: Perl Artistic License Price:
1018 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 jformdesigner tutorial 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
