codes
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5141
Telephony::CountryDialingCodes 1.02
Telephony::CountryDialingCodes is a Perl module that can convert international dialing codes to country codes and vice versa. more>>
Telephony::CountryDialingCodes is a Perl module that can convert international dialing codes to country codes and vice versa.
SYNOPSIS
# Usage method 1 (using object methods):
use Telephony::CountryDialingCodes;
my $o = new Telephony::CountryDialingCodes();
my $country_code = NL;
print "The dialing access code for country $country_code is " . $o->dialing_code($country_code) . "n";
my $dialing_code = 1;
my @country_codes = $o->country_codes($dialing_code);
print "The country code(s) for dialing access code $dialing_code is/are: " . join(,,@country_codes) . "n";
# Usage method 2 (using class methods):
use Telephony::CountryDialingCodes;
my $country_code = NL;
print "The dialing access code for country $country_code is " . Telephony::CountryDialingCodes->dialing_code($country_code) . "n";
my $dialing_code = 1;
my @country_codes = Telephony::CountryDialingCodes->country_codes($dialing_code);
print "The country code(s) for dialing access code $dialing_code is/are: " . join(,,@country_codes) . "n";
# Extracting an intl dialing code from an intl phone number:
use Telephony::CountryDialingCodes;
my $o = new Telephony::CountryDialingCodes();
my $dialing_code = $o->extract_dialing_code(+521234567890);
# $dialing_code will contain 52.
This class exports a method for determining a countrys international dialing code, and another method for doing the reverse: i.e. determining the country code(s) that belong(s) to a given international dialing code.
You can call these methods as class methods or you can create an object and call these methods as object methods. The difference is that if you call them in object context that the internal lookup tables are freed when the object is destroyed, otherwise if you call the methods in class context, then the internal lookup tables are global and will persist for the lifespan of the current process. Its not really a big deal which approach you choose, so for the sake of style, use the object method approach if you have no clue which is better.
<<lessSYNOPSIS
# Usage method 1 (using object methods):
use Telephony::CountryDialingCodes;
my $o = new Telephony::CountryDialingCodes();
my $country_code = NL;
print "The dialing access code for country $country_code is " . $o->dialing_code($country_code) . "n";
my $dialing_code = 1;
my @country_codes = $o->country_codes($dialing_code);
print "The country code(s) for dialing access code $dialing_code is/are: " . join(,,@country_codes) . "n";
# Usage method 2 (using class methods):
use Telephony::CountryDialingCodes;
my $country_code = NL;
print "The dialing access code for country $country_code is " . Telephony::CountryDialingCodes->dialing_code($country_code) . "n";
my $dialing_code = 1;
my @country_codes = Telephony::CountryDialingCodes->country_codes($dialing_code);
print "The country code(s) for dialing access code $dialing_code is/are: " . join(,,@country_codes) . "n";
# Extracting an intl dialing code from an intl phone number:
use Telephony::CountryDialingCodes;
my $o = new Telephony::CountryDialingCodes();
my $dialing_code = $o->extract_dialing_code(+521234567890);
# $dialing_code will contain 52.
This class exports a method for determining a countrys international dialing code, and another method for doing the reverse: i.e. determining the country code(s) that belong(s) to a given international dialing code.
You can call these methods as class methods or you can create an object and call these methods as object methods. The difference is that if you call them in object context that the internal lookup tables are freed when the object is destroyed, otherwise if you call the methods in class context, then the internal lookup tables are global and will persist for the lifespan of the current process. Its not really a big deal which approach you choose, so for the sake of style, use the object method approach if you have no clue which is better.
Download (0.004MB)
Added: 2006-09-20 License: Perl Artistic License Price:
1130 downloads
Code::Splice 0.01
Code::Splice injects the contents of one subroutine at a specified point elsewhere. more>>
Code::Splice injects the contents of one subroutine at a specified point elsewhere.
SYNOPSIS
use Code::Splice;
Code::Splice::inject(
code => sub { print "fredn"; },
package => main,
method => foo,
precondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/four/;
},
postcondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/five/;
},
);
sub foo {
print "onen";
print "twon";
print "threen";
print "fourn";
print "fiven";
}
This module removes the contents of a subroutine (usually an anonymous subroutine created just for the purpose) and splices in into the program elsewhere.
Why, you ask?
Write stronger unit tests than the granularity of the API would otherwise allow
Write unit tests for nasty, interdependant speghetti code (my motivation -- hey, you gotta have tests before you can start refactoring, and if you cant write tests for the code, youre screwed)
Fix stupid bugs and remove stupid restrictions in other peoples code in a way thats more resiliant across upgrades than editing files you dont own
Be what "aspects" should be
Screw with your cow-orkers by introducing monster heisenbugs
Play with self-modifying code
Write self-replicating code (but be nice, were all friends here, right?)
The specifics:
The body of the code { } block are extracted from the subroutine and inserted in a place in the code specified by the call to the splice() function. Where the new code is spliced in, the old code is spliced out. The package and method arguments are required and tell the thing how to find the code to be modified. The code argument is required as it specifies the code to be spliced in. That same code block should not be used for anything else under penalty of coredump.
The rest of the argumets specify where the code is to be inserted. Any number of precondition and postcondition arguments provide callbacks to help locate the exact area to splice the code in at. Before the code can e spliced in, all of the precondition blocks must have returned true, and none of the postcondition blocks may have yet returned true. If a postcondition returns true before all of the precondition blocks have, an error is raised. Both blocks get called numerous times per line and get passed a reference to the B OP object currently under consideration and the text of the current line:
precondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/four/;
},
... or...
precondition => sub { my $op = shift; $op->name eq padsv and $op->sv->sv =~ m/fred/; },
Its possible to insert code in the middle of an expression when testing ops, but when testing the text of the line of code, the spliced in code will always replace the whole line.
Ill probably drop sending in the opcode in a future version, at least for the precondition/postcondition blocks, or maybe Ill swap them to the 2nd arg so theyre more optional.
Do not attempt to match text in comments as it wont be there. The code in $line is re-generated from the bytecode using B::Deparse and will vary from the original source code in a few ways, including changes to formatting, changes to some idioms and details of the expressions, and formatting of the code with regards to whitespace.
The splicing code will die if it fails for any reason. This will likely change in possible future versions.
There are also label and line arguments that create preconditions for you, for simple cases. Of course, you shouldnt use line for anything other than simple experimentation.
References to lexical variables in the code to be injected are replaced with references to the lexical variables of the same name in the location the code is inserted into. If a variable of the same name doesnt exist there, its an error. ... but it probably shouldnt be an error, at least in the cases where the code being spliced in declares that lexical with my, or when the variable was initiailized entirely outside of the sub block being spliced in and was merely closed over by it.
See the comments in the source code (at the top, in a nice block) for my todo/desired features. Let me know if there are any features in there or yet unsuggested that you want. I wont promise them, but I would like to hear about them.
<<lessSYNOPSIS
use Code::Splice;
Code::Splice::inject(
code => sub { print "fredn"; },
package => main,
method => foo,
precondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/four/;
},
postcondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/five/;
},
);
sub foo {
print "onen";
print "twon";
print "threen";
print "fourn";
print "fiven";
}
This module removes the contents of a subroutine (usually an anonymous subroutine created just for the purpose) and splices in into the program elsewhere.
Why, you ask?
Write stronger unit tests than the granularity of the API would otherwise allow
Write unit tests for nasty, interdependant speghetti code (my motivation -- hey, you gotta have tests before you can start refactoring, and if you cant write tests for the code, youre screwed)
Fix stupid bugs and remove stupid restrictions in other peoples code in a way thats more resiliant across upgrades than editing files you dont own
Be what "aspects" should be
Screw with your cow-orkers by introducing monster heisenbugs
Play with self-modifying code
Write self-replicating code (but be nice, were all friends here, right?)
The specifics:
The body of the code { } block are extracted from the subroutine and inserted in a place in the code specified by the call to the splice() function. Where the new code is spliced in, the old code is spliced out. The package and method arguments are required and tell the thing how to find the code to be modified. The code argument is required as it specifies the code to be spliced in. That same code block should not be used for anything else under penalty of coredump.
The rest of the argumets specify where the code is to be inserted. Any number of precondition and postcondition arguments provide callbacks to help locate the exact area to splice the code in at. Before the code can e spliced in, all of the precondition blocks must have returned true, and none of the postcondition blocks may have yet returned true. If a postcondition returns true before all of the precondition blocks have, an error is raised. Both blocks get called numerous times per line and get passed a reference to the B OP object currently under consideration and the text of the current line:
precondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/four/;
},
... or...
precondition => sub { my $op = shift; $op->name eq padsv and $op->sv->sv =~ m/fred/; },
Its possible to insert code in the middle of an expression when testing ops, but when testing the text of the line of code, the spliced in code will always replace the whole line.
Ill probably drop sending in the opcode in a future version, at least for the precondition/postcondition blocks, or maybe Ill swap them to the 2nd arg so theyre more optional.
Do not attempt to match text in comments as it wont be there. The code in $line is re-generated from the bytecode using B::Deparse and will vary from the original source code in a few ways, including changes to formatting, changes to some idioms and details of the expressions, and formatting of the code with regards to whitespace.
The splicing code will die if it fails for any reason. This will likely change in possible future versions.
There are also label and line arguments that create preconditions for you, for simple cases. Of course, you shouldnt use line for anything other than simple experimentation.
References to lexical variables in the code to be injected are replaced with references to the lexical variables of the same name in the location the code is inserted into. If a variable of the same name doesnt exist there, its an error. ... but it probably shouldnt be an error, at least in the cases where the code being spliced in declares that lexical with my, or when the variable was initiailized entirely outside of the sub block being spliced in and was merely closed over by it.
See the comments in the source code (at the top, in a nice block) for my todo/desired features. Let me know if there are any features in there or yet unsuggested that you want. I wont promise them, but I would like to hear about them.
Download (0.010MB)
Added: 2007-08-14 License: Perl Artistic License Price:
806 downloads
XML::Code 0.04
XML::Diff is a Perl module for XML DOM-Tree based Diff & Patch Module. more>>
XML::Diff is a Perl module for XML DOM-Tree based Diff & Patch Module.
SYNOPSIS
my $diff = XML::Diff->new();
# to generate a diffgram of two XML files, use compare.
# $old and $new can be filepaths, XML as a string,
# XML::LibXML::Document or XML::LibXML::Element objects.
# The diffgram is a XML::LibXML::Document by default.
my $diffgram = $diff->compare(
-old => $old_xml,
-new => $new_xml,
);
# To patch an XML document, an patch. $old and $diffgram
# follow the same formatting rules as compare.
# The resulting XML is a XML::LibXML::Document by default.
my $patched = $diff->patch(
-old => $old,
-diffgram => $diffgram,
);
This module provides methods for generating and applying an XML diffgram of two related XML files. The basis of the algorithm is tree-wise comparison using the DOM model as provided by XML::LibXML.
The Diffgram is well-formed XML in the XVCS namespance and supports update, insert, delete and move operations. It is meant to be human and machine readable. It uses XPath expressions for locating the nodes to operate on.
<<lessSYNOPSIS
my $diff = XML::Diff->new();
# to generate a diffgram of two XML files, use compare.
# $old and $new can be filepaths, XML as a string,
# XML::LibXML::Document or XML::LibXML::Element objects.
# The diffgram is a XML::LibXML::Document by default.
my $diffgram = $diff->compare(
-old => $old_xml,
-new => $new_xml,
);
# To patch an XML document, an patch. $old and $diffgram
# follow the same formatting rules as compare.
# The resulting XML is a XML::LibXML::Document by default.
my $patched = $diff->patch(
-old => $old,
-diffgram => $diffgram,
);
This module provides methods for generating and applying an XML diffgram of two related XML files. The basis of the algorithm is tree-wise comparison using the DOM model as provided by XML::LibXML.
The Diffgram is well-formed XML in the XVCS namespance and supports update, insert, delete and move operations. It is meant to be human and machine readable. It uses XPath expressions for locating the nodes to operate on.
Download (0.017MB)
Added: 2006-09-14 License: Perl Artistic License Price:
1138 downloads
Code::Perl 0.03
Code::Perl is a Perl module to produce Perl code from a tree. more>>
Code::Perl is a Perl module to produce Perl code from a tree.
SYNOPSIS
use Code::Perl::Expr qw( :easy );
my $c = derefh(scal(hash), calls(getkey));
print $c->perl; # ($hash)->{getkey()}
Code::Perl allows you to build chunks of Perl code as a tree and then when youre finished building, the tree can output the Perl code. This is useful if you have built your own mini-language and you want to generate Perl from it. Rather than generating the Perl at parse time and having to worry about quoting, escaping, parenthese etc, you can just build a tree using Code::Perl and then dump out the correct Perl at the end.
<<lessSYNOPSIS
use Code::Perl::Expr qw( :easy );
my $c = derefh(scal(hash), calls(getkey));
print $c->perl; # ($hash)->{getkey()}
Code::Perl allows you to build chunks of Perl code as a tree and then when youre finished building, the tree can output the Perl code. This is useful if you have built your own mini-language and you want to generate Perl from it. Rather than generating the Perl at parse time and having to worry about quoting, escaping, parenthese etc, you can just build a tree using Code::Perl and then dump out the correct Perl at the end.
Download (0.017MB)
Added: 2006-10-05 License: Perl Artistic License Price:
1127 downloads
Code::Blocks 1.0 RC2
Code::Blocks is a C/C++ IDE built with configurability and extensibility in mind. more>>
Code::Blocks is a free C++ IDE built specifically to meet the most demanding needs of its users. The Code::Blocks project was designed, right from the start, to be extensible and configurable.
Built around a plugin framework, Code::Blocks can be extended with plugin DLLs. It includes a plugin wizard so you can compile your own plugins! (Free SDK downloaded separately)
Main features:
- Open Source! GPL2, no hidden costs.
- Cross-platform. Runs on Linux or Windows (uses wxWidgets).
- Made in GNU C++. No interpreted languages or proprietary libs needed.
- Comes in two presentations: Standalone, and MinGW bundle
- Devpack support (optional)
- Extensible thru plugins (SDK available in the downloads section)
- Multiple compiler support:
- GCC (MingW / Linux GCC)
- MSVC++
- Digital Mars
- Borland C++ 5.5
- Open Watcom
- Compiles directly or with makefiles
- Predefined project templates
- Custom template support
- Uses XML format for project files.
- Multi-target projects
- Workspaces support
- Imports MSVC projects and workspaces (NOTE: assembly code and inter-project dependencies not supported yet)
- Imports Dev-C++ projects
- Integrates with GDB for debugging
- Syntax highlighting, customizable and extensible
- Code folding for C++ and XML files.
- Tabbed interface
- Code completion plugin
- Class Browser
- Smart indent
- One-key swap between .h and .c/.cpp files
- Open files list for quick switching between files (optional)
- External customizable "Tools"
- To-do list management with different users
<<lessBuilt around a plugin framework, Code::Blocks can be extended with plugin DLLs. It includes a plugin wizard so you can compile your own plugins! (Free SDK downloaded separately)
Main features:
- Open Source! GPL2, no hidden costs.
- Cross-platform. Runs on Linux or Windows (uses wxWidgets).
- Made in GNU C++. No interpreted languages or proprietary libs needed.
- Comes in two presentations: Standalone, and MinGW bundle
- Devpack support (optional)
- Extensible thru plugins (SDK available in the downloads section)
- Multiple compiler support:
- GCC (MingW / Linux GCC)
- MSVC++
- Digital Mars
- Borland C++ 5.5
- Open Watcom
- Compiles directly or with makefiles
- Predefined project templates
- Custom template support
- Uses XML format for project files.
- Multi-target projects
- Workspaces support
- Imports MSVC projects and workspaces (NOTE: assembly code and inter-project dependencies not supported yet)
- Imports Dev-C++ projects
- Integrates with GDB for debugging
- Syntax highlighting, customizable and extensible
- Code folding for C++ and XML files.
- Tabbed interface
- Code completion plugin
- Class Browser
- Smart indent
- One-key swap between .h and .c/.cpp files
- Open files list for quick switching between files (optional)
- External customizable "Tools"
- To-do list management with different users
Download (2.6MB)
Added: 2005-11-28 License: GPL (GNU General Public License) Price:
1591 downloads
mod_fortress 1.0
mod_fortress is an application level firewall and intrusion detection system. more>>
mod_fortress is an application level firewall and intrusion detection system. mod_fortress is designed to intercept certain CGI/HTTP attacks by acting as a non-transparent proxy between an Apache server and an HTTP client.
Main features:
- Detects and Logs common known cgi/http security requests and scans
- SSL support
- Detects all known(and hopefully unknown) Anti-IDS Evasive Scaning methods (Whisker, twwwscan, VoidEye...etc)
- "Fortress In the Middle": Ability to act as a non-transparent proxy to modify HTTP return error codes.
- Custom logging option via a changeable format string.
- Supports Apache 1.3/2.0 (2.0 port by Anton Soudouvstev).
<<lessMain features:
- Detects and Logs common known cgi/http security requests and scans
- SSL support
- Detects all known(and hopefully unknown) Anti-IDS Evasive Scaning methods (Whisker, twwwscan, VoidEye...etc)
- "Fortress In the Middle": Ability to act as a non-transparent proxy to modify HTTP return error codes.
- Custom logging option via a changeable format string.
- Supports Apache 1.3/2.0 (2.0 port by Anton Soudouvstev).
Download (0.014MB)
Added: 2006-05-16 License: GPL (GNU General Public License) Price:
1259 downloads
LoggedFS 0.5
LoggedFS is a transparent fuse-filesystem which allows you to log every operation that happens in the backend filesystem. more>>
LoggedFS is a transparent fuse-filesystem which allows you to log every operation that happens in the backend filesystem.
Logs can be written to syslog, to a file, or to standard output. LoggedFS project comes with an XML configuration file in which you can choose exactly what you want to log.
You can add filters on users, operations (open, read, write, chown, chmod, etc.), filenames, and return codes.
Filenames filters are regular expressions. Since it is fuse-based, you dont need to change anything in your kernel or hard disk partition to use it.
<<lessLogs can be written to syslog, to a file, or to standard output. LoggedFS project comes with an XML configuration file in which you can choose exactly what you want to log.
You can add filters on users, operations (open, read, write, chown, chmod, etc.), filenames, and return codes.
Filenames filters are regular expressions. Since it is fuse-based, you dont need to change anything in your kernel or hard disk partition to use it.
Download (0.008MB)
Added: 2007-01-24 License: GPL (GNU General Public License) Price:
1004 downloads
BBCodeXtra 0.2.5.6
BBCodeXtra is a Firefox extension that adds to the context menu new commands to insert BBCode/Html/XHtml codes. more>>
BBCodeXtra is a Firefox extension that adds to the context menu new commands to insert BBCode/Html/XHtml codes in an easy and fast way. It is compatible with Mozilla FireFox and Mozilla Suite.
BBCodeXtra suits well with all forum types, for example:
- phpBB
- Invision
- VBullettin
This extension can really simplify your life with all forums that use BBCode or Html codes when posting new messages.
BBCodeXtra has been tested and verified with these browsers:
- Mozilla FireFox 0.8
- Mozilla FireFox 0.9.x
- Mozilla FireFox 1.0.x
- Mozilla Firefox 1.5.0.*
- Mozilla Firefox 2.0.*
- SeaMonkey 1.0.*
- Mozilla Suite 1.7.x
- Mozilla Suite 1.8a2
<<lessBBCodeXtra suits well with all forum types, for example:
- phpBB
- Invision
- VBullettin
This extension can really simplify your life with all forums that use BBCode or Html codes when posting new messages.
BBCodeXtra has been tested and verified with these browsers:
- Mozilla FireFox 0.8
- Mozilla FireFox 0.9.x
- Mozilla FireFox 1.0.x
- Mozilla Firefox 1.5.0.*
- Mozilla Firefox 2.0.*
- SeaMonkey 1.0.*
- Mozilla Suite 1.7.x
- Mozilla Suite 1.8a2
Download (0.071MB)
Added: 2007-05-03 License: MPL (Mozilla Public License) Price:
998 downloads
Pretty Code Web 1.00
Pretty Code Web is a syntax highlighter for publishing code, written in any programming language, to the Web. more>>
Pretty Code Web is a syntax highlighter for publishing code, written in any programming language, to the web.
Written in php it uses syntax files separate from the main code to highlight a specified language.
Main features:
- Syntax highlighting for (potentially) any language.
- User defined syntax files.
- User defined colors
- Separate colors for:
- 6 Keyword Groups
- Text Strings
- Operators
- Block and Line Comments
- Bracket Characters
<<lessWritten in php it uses syntax files separate from the main code to highlight a specified language.
Main features:
- Syntax highlighting for (potentially) any language.
- User defined syntax files.
- User defined colors
- Separate colors for:
- 6 Keyword Groups
- Text Strings
- Operators
- Block and Line Comments
- Bracket Characters
Download (0.024MB)
Added: 2005-10-20 License: Free for non-commercial use Price:
1470 downloads

Html Code Convert 3.3
Speed up the conversion of HTML code into different format more>>
HTML Code Convert helps speed up the conversion of HTML code into different format including Java Script, JavaServer Pages, Microsoft ASP, PHP, Perl, Python, and the UNIX Shell. It is particularly useful in CGI scripting.
Enhancements:
- Colors and font selected in prefeferences box.
- Fixe bug with Quit button. First try to support accessibility.
- Updated schemas.
<<lessEnhancements:
- Colors and font selected in prefeferences box.
- Fixe bug with Quit button. First try to support accessibility.
- Updated schemas.
Download (184KB)
Added: 2009-04-29 License: Freeware Price:
198 downloads
GNU barcode 0.98 Beta
GNU Barcode is a tool to convert text strings to printed bars. more>>
GNU Barcode is a tool to convert text strings to printed bars. GNU barcode supports a variety of standard codes to represent the textual strings and creates postscript output.
Main features:
- Available as both a library and an executable program
- Supports UPC, EAN, ISBN, CODE39 and other encoding standards
- Postscript and Encapsulated Postscript output
- Accepts sizes and positions as inches, centimeters, millimeters
- Can create tables of barcodes (to print labels on sticker pages)
<<lessMain features:
- Available as both a library and an executable program
- Supports UPC, EAN, ISBN, CODE39 and other encoding standards
- Postscript and Encapsulated Postscript output
- Accepts sizes and positions as inches, centimeters, millimeters
- Can create tables of barcodes (to print labels on sticker pages)
Download (0.32MB)
Added: 2006-06-07 License: GPL (GNU General Public License) Price:
1240 downloads
Barcode::Code128 2.01
Barcode::Code128 is a Perl module that can generate CODE 128 bar codes. more>>
Barcode::Code128 is a Perl module that can generate CODE 128 bar codes.
SYNOPSIS
use Barcode::Code128;
$code = new Barcode::Code128;
EXPORTS
By default, nothing. However there are a number of constants that represent special characters used in the CODE 128 symbology that you may wish to include. For example if you are using the EAN-128 or UCC-128 code, the string to encode begins with the FNC1 character. To encode the EAN-128 string "00 0 0012345 555555555 8", you would do the following:
use Barcode::Code128 FNC1;
$code = new Barcode::Code128;
$code->text(FNC1.00000123455555555558);
To have this module export one or more of these characters, specify them on the use statement or use the special token :all instead to include all of them. Examples:
use Barcode::Code128 qw(FNC1 FNC2 FNC3 FNC4 Shift);
use Barcode::Code128 qw(:all);
Here is the complete list of the exportable characters. They are assigned to high-order ASCII characters purely arbitrarily for the purposes of this module; the values used do not reflect any part of the CODE 128 standard. Warning: Using the CodeA, CodeB, CodeC, StartA, StartB, StartC, and Stop codes may cause your barcodes to be invalid, and be rejected by scanners. They are inserted automatically as needed by this module.
CodeA 0xf4 CodeB 0xf5 CodeC 0xf6
FNC1 0xf7 FNC2 0xf8 FNC3 0xf9
FNC4 0xfa Shift 0xfb StartA 0xfc
StartB 0xfd StartC 0xfe Stop 0xff
Barcode::Code128 generates bar codes using the CODE 128 symbology. It can generate images in PNG or GIF format using the GD package, or it can generate a text string representing the barcode that you can render using some other technology if desired.
The intended use of this module is to create a web page with a bar code on it, which can then be printed out and faxed or mailed to someone who will scan the bar code. The application which spurred its creation was an expense report tool, where the employee submitting the report would print out the web page and staple the receipts to it, and the Accounts Payable clerk would scan the bar code to indicate that the receipts were received.
The default settings for this module produce a large image that can safely be FAXed several times and still scanned easily. If this requirement is not important you can generate smaller image using optional parameters, described below.
If you wish to generate images with this module you must also have the GD.pm module (written by Lincoln Stein, and available from CPAN) installed. Version 1.20 or higher of GD generates a PNG file, due to issues with the GIF patent. If you want to create a GIF, you must use version 1.19 or earlier of GD. However, most browsers have no trouble with PNG files.
If the GD module is not present, you can still use the module, but you will not be able to use its functions for generating images. You can use the barcode() method to get a string of "#" and " " (hash and space) characters, and use your own image-generating routine with that as input.
To use the the GD module, you will need to install it along with this module. You can obtain it from the CPAN (Comprehensive Perl Archive Network) repository of your choice under the directory authors/id/LDS. Visit http://www.cpan.org/ for more information about CPAN. The GD home page is: http://stein.cshl.org/WWW/software/GD/GD.html
<<lessSYNOPSIS
use Barcode::Code128;
$code = new Barcode::Code128;
EXPORTS
By default, nothing. However there are a number of constants that represent special characters used in the CODE 128 symbology that you may wish to include. For example if you are using the EAN-128 or UCC-128 code, the string to encode begins with the FNC1 character. To encode the EAN-128 string "00 0 0012345 555555555 8", you would do the following:
use Barcode::Code128 FNC1;
$code = new Barcode::Code128;
$code->text(FNC1.00000123455555555558);
To have this module export one or more of these characters, specify them on the use statement or use the special token :all instead to include all of them. Examples:
use Barcode::Code128 qw(FNC1 FNC2 FNC3 FNC4 Shift);
use Barcode::Code128 qw(:all);
Here is the complete list of the exportable characters. They are assigned to high-order ASCII characters purely arbitrarily for the purposes of this module; the values used do not reflect any part of the CODE 128 standard. Warning: Using the CodeA, CodeB, CodeC, StartA, StartB, StartC, and Stop codes may cause your barcodes to be invalid, and be rejected by scanners. They are inserted automatically as needed by this module.
CodeA 0xf4 CodeB 0xf5 CodeC 0xf6
FNC1 0xf7 FNC2 0xf8 FNC3 0xf9
FNC4 0xfa Shift 0xfb StartA 0xfc
StartB 0xfd StartC 0xfe Stop 0xff
Barcode::Code128 generates bar codes using the CODE 128 symbology. It can generate images in PNG or GIF format using the GD package, or it can generate a text string representing the barcode that you can render using some other technology if desired.
The intended use of this module is to create a web page with a bar code on it, which can then be printed out and faxed or mailed to someone who will scan the bar code. The application which spurred its creation was an expense report tool, where the employee submitting the report would print out the web page and staple the receipts to it, and the Accounts Payable clerk would scan the bar code to indicate that the receipts were received.
The default settings for this module produce a large image that can safely be FAXed several times and still scanned easily. If this requirement is not important you can generate smaller image using optional parameters, described below.
If you wish to generate images with this module you must also have the GD.pm module (written by Lincoln Stein, and available from CPAN) installed. Version 1.20 or higher of GD generates a PNG file, due to issues with the GIF patent. If you want to create a GIF, you must use version 1.19 or earlier of GD. However, most browsers have no trouble with PNG files.
If the GD module is not present, you can still use the module, but you will not be able to use its functions for generating images. You can use the barcode() method to get a string of "#" and " " (hash and space) characters, and use your own image-generating routine with that as input.
To use the the GD module, you will need to install it along with this module. You can obtain it from the CPAN (Comprehensive Perl Archive Network) repository of your choice under the directory authors/id/LDS. Visit http://www.cpan.org/ for more information about CPAN. The GD home page is: http://stein.cshl.org/WWW/software/GD/GD.html
Download (0.014MB)
Added: 2007-07-24 License: Perl Artistic License Price:
834 downloads
ICD Browser 0.1
ICD Browser for the ICD-10 codes from W.H.O. more>>
ICD Browser for the ICD-10 codes from W.H.O.
This program is an easy to use browser with search capability for the International Classification of Diseases (ICD) codes, as they are published from the W.H.O.
Main features:
- Three versions, for Windows (XP, 2000, 98), Linux and Pocket PC (WM2003, WM5).
- Two ways for displaying codes, Grouped all together into a treebox, or separeted into chapters, sections and subsections.
- Search codes.
- Easy to use interface.
<<lessThis program is an easy to use browser with search capability for the International Classification of Diseases (ICD) codes, as they are published from the W.H.O.
Main features:
- Three versions, for Windows (XP, 2000, 98), Linux and Pocket PC (WM2003, WM5).
- Two ways for displaying codes, Grouped all together into a treebox, or separeted into chapters, sections and subsections.
- Search codes.
- Easy to use interface.
Download (0.15MB)
Added: 2007-01-15 License: GPL (GNU General Public License) Price:
1103 downloads
Convert::GeekCode 0.51
Convert::GeekCode is a Perl module that can convert and generate geek code sequences. more>>
Convert::GeekCode is a Perl module that can convert and generate geek code sequences.
SYNOPSIS
use Convert::GeekCode; # exports geek_decode()
my @out = geek_decode(q(
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GB/C/CM/CS/CC/ED/H/IT/L/M/MU/P/SS/TW/AT d---x s+: a-- C++++ UB++++$
P++++$ L+ E--->+ W+++$ N++ !o K w--(++) O-- M-@ !V PS+++ PE Y+>++
PGP++ t+ 5? X+ R+++ !tv b++++ DI+++@ D++ G++++ e-(--) h* r++(+) z++*
------END GEEK CODE BLOCK------
)); # yes, thats the authors geek code
my ($key, $val);
print "[$key]n$valnn" while (($key, $val) = splice(@out, 0, 2));
Convert::GeekCode converts and generates Geek Code sequences (cf. http://geekcode.com/). It supports different langugage codes and user-customizable codesets.
Since version 0.5, this module uses YAML to represent the geek code tables, for greater readability and ease of deserialization. Please refer to http://www.yaml.org/ for more related information.
The geekgen and geekdec utilities are installed by default, and may be used to generate / decode geek code blocks, respectively
<<lessSYNOPSIS
use Convert::GeekCode; # exports geek_decode()
my @out = geek_decode(q(
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GB/C/CM/CS/CC/ED/H/IT/L/M/MU/P/SS/TW/AT d---x s+: a-- C++++ UB++++$
P++++$ L+ E--->+ W+++$ N++ !o K w--(++) O-- M-@ !V PS+++ PE Y+>++
PGP++ t+ 5? X+ R+++ !tv b++++ DI+++@ D++ G++++ e-(--) h* r++(+) z++*
------END GEEK CODE BLOCK------
)); # yes, thats the authors geek code
my ($key, $val);
print "[$key]n$valnn" while (($key, $val) = splice(@out, 0, 2));
Convert::GeekCode converts and generates Geek Code sequences (cf. http://geekcode.com/). It supports different langugage codes and user-customizable codesets.
Since version 0.5, this module uses YAML to represent the geek code tables, for greater readability and ease of deserialization. Please refer to http://www.yaml.org/ for more related information.
The geekgen and geekdec utilities are installed by default, and may be used to generate / decode geek code blocks, respectively
Download (0.025MB)
Added: 2006-08-03 License: GPL (GNU General Public License) Price:
1180 downloads
Tamil Converters 2.7.1
Tamil Converters is a package containing five programs that convert Tamil text from ISCII to Unicode. more>>
Tamil Converters is a package containing five programs that convert Tamil text from ISCII to Unicode, Unicode to ISCII, ITRANS to ISCII, ITRANS to ISCII, and TSCII to Unicode.
All five programs provide fairly extensive checking of their input for errors and untranslatable codes. The ITRANS used is, by default, extended to include codes for the Tamil digits and to include HZ escapes (as defined in RFC 1843) that delimit the Tamil portion.
This allows processing of mixed Tamil and ASCII text. The extensions and use of HZ escapes can be disabled by command-line switches.
Enhancements:
- Several programs inadvertently omitted from the previous version of the package are now included.
- Several errors in the Makefile have been fixed.
<<lessAll five programs provide fairly extensive checking of their input for errors and untranslatable codes. The ITRANS used is, by default, extended to include codes for the Tamil digits and to include HZ escapes (as defined in RFC 1843) that delimit the Tamil portion.
This allows processing of mixed Tamil and ASCII text. The extensions and use of HZ escapes can be disabled by command-line switches.
Enhancements:
- Several programs inadvertently omitted from the previous version of the package are now included.
- Several errors in the Makefile have been fixed.
Download (0.096MB)
Added: 2007-05-28 License: GPL (GNU General Public License) Price:
902 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 codes 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