encoded data
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5210
Encode 2.21
Encode is a Perl module created to deal with character encodings. more>>
Encode is a Perl module created to deal with character encodings.
SYNOPSIS
use Encode;
Table of Contents
Encode consists of a collection of modules whose details are too big to fit in one document. This POD itself explains the top-level APIs and general topics at a glance. For other topics and more details, see the PODs below:
Name Description
--------------------------------------------------------
Encode::Alias Alias definitions to encodings
Encode::Encoding Encode Implementation Base Class
Encode::Supported List of Supported Encodings
Encode::CN Simplified Chinese Encodings
Encode::JP Japanese Encodings
Encode::KR Korean Encodings
Encode::TW Traditional Chinese Encodings
--------------------------------------------------------
The Encode module provides the interfaces between Perls strings and the rest of the system. Perl strings are sequences of characters.
The repertoire of characters that Perl can represent is at least that defined by the Unicode Consortium. On most platforms the ordinal values of the characters (as returned by ord(ch)) is the "Unicode codepoint" for the character (the exceptions are those platforms where the legacy encoding is some variant of EBCDIC rather than a super-set of ASCII - see perlebcdic).
Traditionally, computer data has been moved around in 8-bit chunks often called "bytes". These chunks are also known as "octets" in networking standards. Perl is widely used to manipulate data of many types - not only strings of characters representing human or computer languages but also "binary" data being the machines representation of numbers, pixels in an image - or just about anything.
When Perl is processing "binary data", the programmer wants Perl to process "sequences of bytes". This is not a problem for Perl - as a byte has 256 possible values, it easily fits in Perls much larger "logical character".
<<lessSYNOPSIS
use Encode;
Table of Contents
Encode consists of a collection of modules whose details are too big to fit in one document. This POD itself explains the top-level APIs and general topics at a glance. For other topics and more details, see the PODs below:
Name Description
--------------------------------------------------------
Encode::Alias Alias definitions to encodings
Encode::Encoding Encode Implementation Base Class
Encode::Supported List of Supported Encodings
Encode::CN Simplified Chinese Encodings
Encode::JP Japanese Encodings
Encode::KR Korean Encodings
Encode::TW Traditional Chinese Encodings
--------------------------------------------------------
The Encode module provides the interfaces between Perls strings and the rest of the system. Perl strings are sequences of characters.
The repertoire of characters that Perl can represent is at least that defined by the Unicode Consortium. On most platforms the ordinal values of the characters (as returned by ord(ch)) is the "Unicode codepoint" for the character (the exceptions are those platforms where the legacy encoding is some variant of EBCDIC rather than a super-set of ASCII - see perlebcdic).
Traditionally, computer data has been moved around in 8-bit chunks often called "bytes". These chunks are also known as "octets" in networking standards. Perl is widely used to manipulate data of many types - not only strings of characters representing human or computer languages but also "binary" data being the machines representation of numbers, pixels in an image - or just about anything.
When Perl is processing "binary data", the programmer wants Perl to process "sequences of bytes". This is not a problem for Perl - as a byte has 256 possible values, it easily fits in Perls much larger "logical character".
Download (1.9MB)
Added: 2007-05-15 License: Perl Artistic License Price:
894 downloads
Libqrencode 1.0.2
Libqrencode is a C library for encoding data in a QR Code symbol. more>>
Libqrencode is a C library for encoding data in a QR Code symbol, a kind of 2D symbology that can be scanned by handy terminals such as a mobile phone with CCD. The capacity of QR Code is up to 7000 digits or 4000 characters, and is highly robustness.
Libqrencode supports QR Code model 2, described in JIS (Japanese Industrial Standards) X0510:2004 or ISO/IEC 18004. Currently the following features are not supported:
- ECI and FNC1 mode
- Structured Append Feature
- Micro QR Code
- QR Code model 1
<<lessLibqrencode supports QR Code model 2, described in JIS (Japanese Industrial Standards) X0510:2004 or ISO/IEC 18004. Currently the following features are not supported:
- ECI and FNC1 mode
- Structured Append Feature
- Micro QR Code
- QR Code model 1
Download (0.34MB)
Added: 2007-03-25 License: LGPL (GNU Lesser General Public License) Price:
949 downloads
Encode::PerlIO 5.8.1
Encode::PerlIO is a detailed document on Encode and PerlIO. more>>
Encode::PerlIO is a detailed document on Encode and PerlIO.
Overview
It is very common to want to do encoding transformations when reading or writing files, network connections, pipes etc. If Perl is configured to use the new perlio IO system then Encode provides a "layer" (see PerlIO) which can transform data as it is read or written.
Here is how the blind poet would modernise the encoding:
use Encode;
open(my $iliad,:utf8,iliad.utf8);
my @epic = < $iliad >;
print $utf8 @epic;
close($utf8);
close($illiad);
In addition, the new IO system can also be configured to read/write UTF-8 encoded characters (as noted above, this is efficient):
open(my $fh,>:utf8,anything);
print $fh "Any x{0021} string N{SMILEY FACE}n";
Either of the above forms of "layer" specifications can be made the default for a lexical scope with the use open ... pragma. See open.
Once a handle is open, its layers can be altered using binmode.
Without any such configuration, or if Perl itself is built using the systems own IO, then write operations assume that the file handle accepts only bytes and will die if a character larger than 255 is written to the handle. When reading, each octet from the handle becomes a byte-in-a-character. Note that this default is the same behaviour as bytes-only languages (including Perl before v5.6) would have, and is sufficient to handle native 8-bit encodings e.g. iso-8859-1, EBCDIC etc. and any legacy mechanisms for handling other encodings and binary data.
In other cases, it is the programs responsibility to transform characters into bytes using the API above before doing writes, and to transform the bytes read from a handle into characters before doing "character operations" (e.g. lc, /W+/, ...).
You can also use PerlIO to convert larger amounts of data you dont want to bring into memory. For example, to convert between ISO-8859-1 (Latin 1) and UTF-8 (or UTF-EBCDIC in EBCDIC machines):
open(F, ":utf8", "data.utf") or die $!;
while (< F >) { print G }
# Could also do "print G < F >" but that would pull
# the whole file into memory just to write it out again.
More examples:
open(my $f, ":encoding(iso-8859-2)")
open(my $h, ">:encoding(latin9)") # iso-8859-15
<<lessOverview
It is very common to want to do encoding transformations when reading or writing files, network connections, pipes etc. If Perl is configured to use the new perlio IO system then Encode provides a "layer" (see PerlIO) which can transform data as it is read or written.
Here is how the blind poet would modernise the encoding:
use Encode;
open(my $iliad,:utf8,iliad.utf8);
my @epic = < $iliad >;
print $utf8 @epic;
close($utf8);
close($illiad);
In addition, the new IO system can also be configured to read/write UTF-8 encoded characters (as noted above, this is efficient):
open(my $fh,>:utf8,anything);
print $fh "Any x{0021} string N{SMILEY FACE}n";
Either of the above forms of "layer" specifications can be made the default for a lexical scope with the use open ... pragma. See open.
Once a handle is open, its layers can be altered using binmode.
Without any such configuration, or if Perl itself is built using the systems own IO, then write operations assume that the file handle accepts only bytes and will die if a character larger than 255 is written to the handle. When reading, each octet from the handle becomes a byte-in-a-character. Note that this default is the same behaviour as bytes-only languages (including Perl before v5.6) would have, and is sufficient to handle native 8-bit encodings e.g. iso-8859-1, EBCDIC etc. and any legacy mechanisms for handling other encodings and binary data.
In other cases, it is the programs responsibility to transform characters into bytes using the API above before doing writes, and to transform the bytes read from a handle into characters before doing "character operations" (e.g. lc, /W+/, ...).
You can also use PerlIO to convert larger amounts of data you dont want to bring into memory. For example, to convert between ISO-8859-1 (Latin 1) and UTF-8 (or UTF-EBCDIC in EBCDIC machines):
open(F, ":utf8", "data.utf") or die $!;
while (< F >) { print G }
# Could also do "print G < F >" but that would pull
# the whole file into memory just to write it out again.
More examples:
open(my $f, ":encoding(iso-8859-2)")
open(my $h, ">:encoding(latin9)") # iso-8859-15
Download (11.3MB)
Added: 2007-08-07 License: Perl Artistic License Price:
809 downloads
readcdda 1.003
readcdda is a Perl module that reads digital audio from a CD. more>>
readcdda is a Perl module that reads digital audio from a CD.
SYNOPSIS
readcdda [OPTION]...
This is a program to read (or "rip") CD digital audio from a CD and output the PCM data. Typically this is an initial stage in encoding data to MP3 format.
The output data is raw 16 bit 44.1kHz stereo data. This format is directly readable by software like sox and various MP3 encoders, e.g.:
readcdda -Dsg3 -v -F |sox -r44100 -c2 -tsw - -twav %02d.wav
Will read a CD and create WAV files in the current directory with names 00.wav..99.wav. Alternatively, you can read and encode directly to MP3 with something like:
readcdda -Dsg3 -v -F |mp3enc -v -sti -of %02d.mp3 -br 160000 -qual 6
-D, --dev, --device=DEVICE
SCSI device name or number to use.
-L, --list
Prints a list of all CD devices and their name/number, then exits.
-T, --toc
Prints a list of tracks on the CD, then exits.
-f, --first=TRACK
Selects the first track to read. Defaults to the first track on the CD.
-l, --last=TRACK
Selects the last track to read. Defaults to the same as -f if that was selected (i.e. read just one track) or the last track on the CD if it was not (i.e. read the whole CD.)
-d, --dir, --directory=DIR
Output is saved in this directory, with names of "00".."99".
-s, --stdout
Output is sent to standard output.
-F, --format=FORMAT
Output is sent to a name generated by a printf()-style format, e.g. "%02d".
-v, --verbose
Gives progress reports.
-V, --version
Givess script and module versions and exits.
-h, --help
Prints this text and exits.
<<lessSYNOPSIS
readcdda [OPTION]...
This is a program to read (or "rip") CD digital audio from a CD and output the PCM data. Typically this is an initial stage in encoding data to MP3 format.
The output data is raw 16 bit 44.1kHz stereo data. This format is directly readable by software like sox and various MP3 encoders, e.g.:
readcdda -Dsg3 -v -F |sox -r44100 -c2 -tsw - -twav %02d.wav
Will read a CD and create WAV files in the current directory with names 00.wav..99.wav. Alternatively, you can read and encode directly to MP3 with something like:
readcdda -Dsg3 -v -F |mp3enc -v -sti -of %02d.mp3 -br 160000 -qual 6
-D, --dev, --device=DEVICE
SCSI device name or number to use.
-L, --list
Prints a list of all CD devices and their name/number, then exits.
-T, --toc
Prints a list of tracks on the CD, then exits.
-f, --first=TRACK
Selects the first track to read. Defaults to the first track on the CD.
-l, --last=TRACK
Selects the last track to read. Defaults to the same as -f if that was selected (i.e. read just one track) or the last track on the CD if it was not (i.e. read the whole CD.)
-d, --dir, --directory=DIR
Output is saved in this directory, with names of "00".."99".
-s, --stdout
Output is sent to standard output.
-F, --format=FORMAT
Output is sent to a name generated by a printf()-style format, e.g. "%02d".
-v, --verbose
Gives progress reports.
-V, --version
Givess script and module versions and exits.
-h, --help
Prints this text and exits.
Download (0.009MB)
Added: 2006-06-22 License: Perl Artistic License Price:
1219 downloads
Encode::MIME::Header 2.23
Encode::MIME::Header is a Perl module that contains MIME B and Q header encoding. more>>
Encode::MIME::Header is a Perl module that contains MIME B and Q header encoding.
SYNOPSIS
use Encode qw/encode decode/;
$utf8 = decode(MIME-Header, $header);
$header = encode(MIME-Header, $utf8);
ABSTRACT
This module implements RFC 2047 Mime Header Encoding. There are 3 variant encoding names; MIME-Header, MIME-B and MIME-Q. The difference is described below
decode() encode()
----------------------------------------------
MIME-Header Both B and Q =?UTF-8?B?....?=
MIME-B B only; Q croaks =?UTF-8?B?....?=
MIME-Q Q only; B croaks =?UTF-8?Q?....?=
When you decode(=?encoding?X?ENCODED WORD?=), ENCODED WORD is extracted and decoded for X encoding (B for Base64, Q for Quoted-Printable). Then the decoded chunk is fed to decode(encoding). So long as encoding is supported by Encode, any source encoding is fine.
When you encode, it just encodes UTF-8 string with X encoding then quoted with =?UTF-8?X?....?= . The parts that RFC 2047 forbids to encode are left as is and long lines are folded within 76 bytes per line.
<<lessSYNOPSIS
use Encode qw/encode decode/;
$utf8 = decode(MIME-Header, $header);
$header = encode(MIME-Header, $utf8);
ABSTRACT
This module implements RFC 2047 Mime Header Encoding. There are 3 variant encoding names; MIME-Header, MIME-B and MIME-Q. The difference is described below
decode() encode()
----------------------------------------------
MIME-Header Both B and Q =?UTF-8?B?....?=
MIME-B B only; Q croaks =?UTF-8?B?....?=
MIME-Q Q only; B croaks =?UTF-8?Q?....?=
When you decode(=?encoding?X?ENCODED WORD?=), ENCODED WORD is extracted and decoded for X encoding (B for Base64, Q for Quoted-Printable). Then the decoded chunk is fed to decode(encoding). So long as encoding is supported by Encode, any source encoding is fine.
When you encode, it just encodes UTF-8 string with X encoding then quoted with =?UTF-8?X?....?= . The parts that RFC 2047 forbids to encode are left as is and long lines are folded within 76 bytes per line.
Download (1.9MB)
Added: 2007-07-17 License: Perl Artistic License Price:
829 downloads
Stickloader 0.5
Stickloader is a LAME front end for quick filling of mp3 sticks. more>>
Stickloader is an easy solution for copying music files from your hard disk to your USB stick and re-encoding them at a lower bitrate for more efficient usage of your MP3 player disk space.
Stickloader is a LAME front end for quick filling of mp3 sticks.
MP3 files and whole directories can be easily dragged on the Stickloader window (which always stays on top) and they are automatically re-encoded using LAME and copied to your USB stick by using a temporary directory to avoid blocking the encoding process.
The programm is written with Java 5.0 using the Standard Widget Toolkit SWT and is using LAME for encoding the data. Therefore it should be system-independent and run on every system where Java, SWT and LAME are available.
<<lessStickloader is a LAME front end for quick filling of mp3 sticks.
MP3 files and whole directories can be easily dragged on the Stickloader window (which always stays on top) and they are automatically re-encoded using LAME and copied to your USB stick by using a temporary directory to avoid blocking the encoding process.
The programm is written with Java 5.0 using the Standard Widget Toolkit SWT and is using LAME for encoding the data. Therefore it should be system-independent and run on every system where Java, SWT and LAME are available.
Download (0.82MB)
Added: 2006-07-21 License: Freely Distributable Price:
1190 downloads
Test::Data 1.20
Test::Data is a Perl module to test functions for particular variable types. more>>
Test::Data is a Perl module to test functions for particular variable types.
SYNOPSIS
use Test::Data qw(Scalar Array Hash Function);
Test::Data provides utility functions to check properties and values of data and variables.
Functions
Plug-in modules define functions for each data type. See the appropriate module.
How it works
The Test::Data module simply emports functions from Test::Data::* modules. Each module defines a self-contained function, and puts that function name into @EXPORT. Test::Data defines its own import function, but that does not matter to the plug-in modules.
If you want to write a plug-in module, follow the example of one that already exists. Name the module Test::Data::Foo, where you replace Foo with the right name. Test::Data should automatically find it.
<<lessSYNOPSIS
use Test::Data qw(Scalar Array Hash Function);
Test::Data provides utility functions to check properties and values of data and variables.
Functions
Plug-in modules define functions for each data type. See the appropriate module.
How it works
The Test::Data module simply emports functions from Test::Data::* modules. Each module defines a self-contained function, and puts that function name into @EXPORT. Test::Data defines its own import function, but that does not matter to the plug-in modules.
If you want to write a plug-in module, follow the example of one that already exists. Name the module Test::Data::Foo, where you replace Foo with the right name. Test::Data should automatically find it.
Download (0.008MB)
Added: 2007-05-03 License: Perl Artistic License Price:
904 downloads
SOAP::Data 0.69
SOAP::Data is a Perl class that provides the means by which to explicitly manipulate and control all aspects of the way. more>>
SOAP::Data is a Perl class that provides the means by which to explicitly manipulate and control all aspects of the way in which Perl data gets expressed as SOAP data entities.
The SOAP::Data class provides the means by which to explicitly manipulate and control all aspects of the way in which Perl data gets expressed as SOAP data entities. Most of the methods are accessors, which like those in SOAP::Lite are designed to return the current value if no new one is passed, while returning the object reference otherwise (allowing for chained method calls). Note that most accessors (except value) accept a new value for the data object as a second argument.
METHODS
new(optional key/value pairs)
$obj = SOAP::Data->new(name => idx, value => 5);
This is the class constructor. Almost all of the attributes related to the class may be passed to the constructor as key/value pairs. This method isnt often used directly because SOAP::Data objects are generally created for temporary use. It is available for those situations that require it.
name(new name, optional value)
$obj->name(index);
Gets or sets the current value of the name, as the object regards it. The name is what the serializer will use for the tag when generating the XML for this object. It is what will become the accessor for the data element. Optionally, the objects value may be updated if passed as a second argument.
type(new type, optional value)
$obj->type(int);
Gets or sets the type associated with the current value in the object. This is useful for those cases where the SOAP::Data object is used to explicitly specify the type of data that would otherwise be interpreted as a different type completely (such as perceiving the string 123 as an integer, instead). Allows the setting of the objects value, if passed as a second argument to the method.
uri(new uri, optional value)
$obj->uri(http://www.perl.com/SOAP);
Gets or sets the URI that will be used as the namespace for the resulting XML entity, if one is desired. This doesnt set the label for the namespace. If one isnt provided by means of the prefix method, one is generated automatically when needed. Also allows the setting of the objects value, if passed as a second argument to the method.
prefix(new prefix, optional value)
$obj->prefix(perl);
Provides the prefix, or label, for use when associating the data object with a specific namespace. Also allows the setting of the objects value, if passed as a second argument to the method.
attr(hash reference of attributes, optional value)
$obj->attr({ attr1 => value });
Allows for the setting of arbitrary attributes on the data object. Keep in mind the requirement that any attributes not natively known to SOAP must be namespace-qualified. Also allows the setting of the objects value, if passed as a second argument to the method.
value(new value)
$obj->value(10);
Fetches the current value encapsulated by the object, or explicitly sets it.
The last four methods are convenience shortcuts for the attributes that SOAP itself supports. Each also permits inclusion of a new value, as an optional second argument.
actor(new actor, optional value)
$obj->actor($new_actor_name);
Gets or sets the value of the actor attribute; useful only when the object generates an entity for the message header.
mustUnderstand(boolean, optional value)
$obj->mustUnderstand(0);
Manipulates the mustUnderstand attribute, which tells the SOAP processor whether it is required to understand the entity in question.
encodingStyle(new encoding URN, optional value)
$obj->encodingStyle($soap_11_encoding);
This method is most likely to be used in places outside the header creation. Sets encodingStyle, which specifies an encoding that differs from the one that would otherwise be defaulted to.
root(boolean, optional value)
$obj->root(1);
When the application must explicitly specify which data element is to be regarded as the root element for the sake of generating the object model, this method provides the access to the root attribute.
<<lessThe SOAP::Data class provides the means by which to explicitly manipulate and control all aspects of the way in which Perl data gets expressed as SOAP data entities. Most of the methods are accessors, which like those in SOAP::Lite are designed to return the current value if no new one is passed, while returning the object reference otherwise (allowing for chained method calls). Note that most accessors (except value) accept a new value for the data object as a second argument.
METHODS
new(optional key/value pairs)
$obj = SOAP::Data->new(name => idx, value => 5);
This is the class constructor. Almost all of the attributes related to the class may be passed to the constructor as key/value pairs. This method isnt often used directly because SOAP::Data objects are generally created for temporary use. It is available for those situations that require it.
name(new name, optional value)
$obj->name(index);
Gets or sets the current value of the name, as the object regards it. The name is what the serializer will use for the tag when generating the XML for this object. It is what will become the accessor for the data element. Optionally, the objects value may be updated if passed as a second argument.
type(new type, optional value)
$obj->type(int);
Gets or sets the type associated with the current value in the object. This is useful for those cases where the SOAP::Data object is used to explicitly specify the type of data that would otherwise be interpreted as a different type completely (such as perceiving the string 123 as an integer, instead). Allows the setting of the objects value, if passed as a second argument to the method.
uri(new uri, optional value)
$obj->uri(http://www.perl.com/SOAP);
Gets or sets the URI that will be used as the namespace for the resulting XML entity, if one is desired. This doesnt set the label for the namespace. If one isnt provided by means of the prefix method, one is generated automatically when needed. Also allows the setting of the objects value, if passed as a second argument to the method.
prefix(new prefix, optional value)
$obj->prefix(perl);
Provides the prefix, or label, for use when associating the data object with a specific namespace. Also allows the setting of the objects value, if passed as a second argument to the method.
attr(hash reference of attributes, optional value)
$obj->attr({ attr1 => value });
Allows for the setting of arbitrary attributes on the data object. Keep in mind the requirement that any attributes not natively known to SOAP must be namespace-qualified. Also allows the setting of the objects value, if passed as a second argument to the method.
value(new value)
$obj->value(10);
Fetches the current value encapsulated by the object, or explicitly sets it.
The last four methods are convenience shortcuts for the attributes that SOAP itself supports. Each also permits inclusion of a new value, as an optional second argument.
actor(new actor, optional value)
$obj->actor($new_actor_name);
Gets or sets the value of the actor attribute; useful only when the object generates an entity for the message header.
mustUnderstand(boolean, optional value)
$obj->mustUnderstand(0);
Manipulates the mustUnderstand attribute, which tells the SOAP processor whether it is required to understand the entity in question.
encodingStyle(new encoding URN, optional value)
$obj->encodingStyle($soap_11_encoding);
This method is most likely to be used in places outside the header creation. Sets encodingStyle, which specifies an encoding that differs from the one that would otherwise be defaulted to.
root(boolean, optional value)
$obj->root(1);
When the application must explicitly specify which data element is to be regarded as the root element for the sake of generating the object model, this method provides the access to the root attribute.
Download (0.23MB)
Added: 2006-09-16 License: Perl Artistic License Price:
1133 downloads
Google::Adwords::Data 0.6.0
Google::Adwords::Data is base class for the Data modules. more>>
Google::Adwords::Data is base class for the Data modules.
This module is not supposed to be used directly. Use the child data modules.
<<lessThis module is not supposed to be used directly. Use the child data modules.
Download (0.041MB)
Added: 2006-11-28 License: Perl Artistic License Price:
1060 downloads
Yukatan data model 1.0
Yukatan data model project is the schema definition of the Yukatan webmail database. more>>
Yukatan data model project is the schema definition of the Yukatan webmail database.
The PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented
<<lessThe PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented
Download (0.035MB)
Added: 2007-02-19 License: GPL (GNU General Public License) Price:
983 downloads
WWW::Myspace::Data 0.13
WWW::Myspace::Data is a WWW::Myspace database interaction. more>>
WWW::Myspace::Data is a WWW::Myspace database interaction.
SYNOPSIS
This module is the database interface for the WWW::Myspace modules. It imports methods into the callers namespace which allow the caller to bypass the loader object by calling the methods directly. This module is intended to be used as a back end for the Myspace modules, but it can also be called directly from a script if you need direct database access.
my %db = (
dsn => dbi:mysql:database_name,
user => username,
password => password,
);
# create a new object
my $data = WWW::Myspace::Data->new( $myspace, { db => %db } );
# set up a database connection
my $loader = $data->loader();
# initialize the database with Myspace login info
my $account_id = $data->set_account( $username, $password );
# now do something useful...
my $update = $data->update_friend( $friend_id );
<<lessSYNOPSIS
This module is the database interface for the WWW::Myspace modules. It imports methods into the callers namespace which allow the caller to bypass the loader object by calling the methods directly. This module is intended to be used as a back end for the Myspace modules, but it can also be called directly from a script if you need direct database access.
my %db = (
dsn => dbi:mysql:database_name,
user => username,
password => password,
);
# create a new object
my $data = WWW::Myspace::Data->new( $myspace, { db => %db } );
# set up a database connection
my $loader = $data->loader();
# initialize the database with Myspace login info
my $account_id = $data->set_account( $username, $password );
# now do something useful...
my $update = $data->update_friend( $friend_id );
Download (0.016MB)
Added: 2007-07-26 License: Perl Artistic License Price:
824 downloads
MySpace Data Mining Tools 1.1
MySpace Data Mining Tools are a set of Java classes designed to mine information from MySpace profile and blog pages. more>>
MySpace Data Mining Tools are a set of Java classes designed to mine information from MySpace profile and blog pages using a multi-threaded Web page access method.
Enhancements:
- Direct database connectivity via JDBC was implemented for data storage.
- A basic user profile class was created to handle both user data compression and database access.
- Minor bugs were fixed for some of the raw data accessing routines.
<<lessEnhancements:
- Direct database connectivity via JDBC was implemented for data storage.
- A basic user profile class was created to handle both user data compression and database access.
- Minor bugs were fixed for some of the raw data accessing routines.
Download (0.035MB)
Added: 2006-07-30 License: GPL (GNU General Public License) Price:
1191 downloads
Convert::ASN1 0.20
Convert::ASN1 is an ASN.1 Encode/Decode library. more>>
Convert::ASN1 is an ASN.1 Encode/Decode library.
SYNOPSYS
use Convert::ASN1;
$asn = Convert::ASN1->new;
$asn->prepare(q<
[APPLICATION 7] SEQUENCE {
int INTEGER,
str OCTET STRING
}
>);
$pdu = $asn->encode( int => 7, str => "string");
$out = $asn->decode($pdu);
print $out->{int}," ",$out->{str},"n";
use Convert::ASN1 qw(:io);
$peer = asn_recv($sock,$buffer,0);
$nbytes = asn_read($fh, $buffer);
$nbytes = asn_send($sock, $buffer, $peer);
$nbytes = asn_send($sock, $buffer);
$nbytes = asn_write($fh, $buffer);
$buffer = asn_get($fh);
$yes = asn_ready($fh)
Convert::ASN1 encodes and decodes ASN.1 data structures using BER/DER rules.
<<lessSYNOPSYS
use Convert::ASN1;
$asn = Convert::ASN1->new;
$asn->prepare(q<
[APPLICATION 7] SEQUENCE {
int INTEGER,
str OCTET STRING
}
>);
$pdu = $asn->encode( int => 7, str => "string");
$out = $asn->decode($pdu);
print $out->{int}," ",$out->{str},"n";
use Convert::ASN1 qw(:io);
$peer = asn_recv($sock,$buffer,0);
$nbytes = asn_read($fh, $buffer);
$nbytes = asn_send($sock, $buffer, $peer);
$nbytes = asn_send($sock, $buffer);
$nbytes = asn_write($fh, $buffer);
$buffer = asn_get($fh);
$yes = asn_ready($fh)
Convert::ASN1 encodes and decodes ASN.1 data structures using BER/DER rules.
Download (0.060MB)
Added: 2006-08-22 License: Perl Artistic License Price:
1178 downloads
DOG Data Organizer 0.4.2
DOG Data Organizer provides a bookmark organizer for various bookmark types. more>>
DOG Data Organizer provides a bookmark organizer for various bookmark types.
DOG is a personal knowledge manager based on topic maps. It currently specializes in managing bookmarks.
It imports and exports Netscape, Mozilla, and KDE2 (XBEL) bookmark files, and it imports KDE1 bookmarks and Windows IE Favorites.
<<lessDOG is a personal knowledge manager based on topic maps. It currently specializes in managing bookmarks.
It imports and exports Netscape, Mozilla, and KDE2 (XBEL) bookmark files, and it imports KDE1 bookmarks and Windows IE Favorites.
Download (0.42MB)
Added: 2007-03-12 License: GPL (GNU General Public License) Price:
960 downloads
Local Data Manager 6.6.5
Local Data Manager is a collection of cooperating programs that select, capture, manage, and distribute arbitrary data products. more>>
Local Data Manager (LDM) is a collection of cooperating programs that select, capture, manage, and distribute arbitrary data products.
The system is designed for event-driven data distribution, and is currently used in the Unidata Internet Data Distribution (IDD) project. The LDM system includes network client and server programs and their shared protocols.
An important characteristic of the LDM is its support for flexible, site-specific configuration.
Enhancements:
- Fixes for timestamp bugs.
<<lessThe system is designed for event-driven data distribution, and is currently used in the Unidata Internet Data Distribution (IDD) project. The LDM system includes network client and server programs and their shared protocols.
An important characteristic of the LDM is its support for flexible, site-specific configuration.
Enhancements:
- Fixes for timestamp bugs.
Download (0.61MB)
Added: 2007-08-09 License: BSD License Price:
809 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 encoded data 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