html objects 1.2.4
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5024
HTML Objects 1.2.4
HTML Objects is a Perl module library for turning HTML tags into Perl objects. more>>
HTML Objects is a Perl module library for turning HTML tags into Perl objects. HTML Objects allows Web pages to be manipulated as a data structure rather than text.
Once manipulation is done, the entire page is generated via depth-first recursion.
<<lessOnce manipulation is done, the entire page is generated via depth-first recursion.
Download (0.025MB)
Added: 2006-05-09 License: GPL (GNU General Public License) Price:
1263 downloads
Rose::HTML::Objects 0.547
Rose::HTML::Objects is a Perl object-oriented interfaces for HTML. more>>
Rose::HTML::Objects is a Perl object-oriented interfaces for HTML.
SYNOPSIS
use Rose::HTML::Form;
$form = Rose::HTML::Form->new(action => /foo,
method => post);
$form->add_fields
(
name => { type => text, size => 20, required => 1 },
height => { type => text, size => 5, maxlength => 5 },
bday => { type => datetime },
);
$form->params(name => John, height => 6ft, bday => 01/24/1984);
$form->init_fields();
$bday = $form->field(bday)->internal_value; # DateTime object
print $bday->strftime(%A); # Tuesday
print $form->field(bday)->html;
The Rose::HTML::Object::* family of classes represent HTML tags, or groups of tags. These objects allow HTML to be arbitrarily manipulated, then serialized to actual HTML (or XHTML). Currently, the process only works in one direction. Objects cannot be constructed from their serialized representations. In practice, given the purpose of these modules, this is not an important limitation.
Any HTML tag can theoretically be represented by a Rose::HTML::Object-derived class, but this family of modules was originally motivated by a desire to simplify the use of HTML forms.
The form/field object interfaces have been heavily abstracted to allow for input and output filtering, inflation/deflation of values, and compound fields (fields that contain other fields). The classes are also designed to be subclassed. The creation of custom form and field subclasses is really the "big win" for these modules.
There is also a simple image tag class which is useful for auto-populating the width and height attributes of img tags. Future releases may include object representations of other HTML tags. Contributions are welcome.
<<lessSYNOPSIS
use Rose::HTML::Form;
$form = Rose::HTML::Form->new(action => /foo,
method => post);
$form->add_fields
(
name => { type => text, size => 20, required => 1 },
height => { type => text, size => 5, maxlength => 5 },
bday => { type => datetime },
);
$form->params(name => John, height => 6ft, bday => 01/24/1984);
$form->init_fields();
$bday = $form->field(bday)->internal_value; # DateTime object
print $bday->strftime(%A); # Tuesday
print $form->field(bday)->html;
The Rose::HTML::Object::* family of classes represent HTML tags, or groups of tags. These objects allow HTML to be arbitrarily manipulated, then serialized to actual HTML (or XHTML). Currently, the process only works in one direction. Objects cannot be constructed from their serialized representations. In practice, given the purpose of these modules, this is not an important limitation.
Any HTML tag can theoretically be represented by a Rose::HTML::Object-derived class, but this family of modules was originally motivated by a desire to simplify the use of HTML forms.
The form/field object interfaces have been heavily abstracted to allow for input and output filtering, inflation/deflation of values, and compound fields (fields that contain other fields). The classes are also designed to be subclassed. The creation of custom form and field subclasses is really the "big win" for these modules.
There is also a simple image tag class which is useful for auto-populating the width and height attributes of img tags. Future releases may include object representations of other HTML tags. Contributions are welcome.
Download (0.13MB)
Added: 2007-03-26 License: Perl Artistic License Price:
942 downloads
HTML::EmbperlObject 1.3.6
HTML::EmbperlObject is a Perl module that extents HTML::Embperl for building whole website with reusable components and objects. more>>
HTML::EmbperlObject is a Perl module that extents HTML::Embperl for building whole website with reusable components and objects.
SYNOPSIS
< Location /foo >
PerlSetEnv EMBPERL_OBJECT_BASE base.htm
PerlSetEnv EMBPERL_FILESMATCH ".htm.?|.epl$"
SetHandler perl-script
PerlHandler HTML::EmbperlObject
Options ExecCGI
< /Location >
HTML::EmbperlObject allows you to build object-oriented (OO) websites using HTML components which implement inheritance via subdirectories. This enables elegant architectures and encourages code reuse. The use of inheritance also enables a website-wide "look and feel" to be specified in a single HTML file, which is then used as a template for every other page on the site. This template can include other modules which can be overridden in subdirectories; even the template itself can be overridden. In a nutshell, EmbperlObject makes the design of large websites much more intuitive, allowing object-oriented concepts to be utilised to the fullest while staying within the "rapid application development" model of Perl and HTML.
HTML::EmbperlObject is basicly a mod_perl handler or could be invoked offline and helps you to build a whole page out of smaller parts. Basicly it does the following:
When a request comes in, a page, which name is specified by EMBPERL_OBJECT_BASE, is searched in the same directory as the requested page. If the pages isnt found, EmbperlObject walking up the directory tree until it finds the page, or it reaches DocumentRoot or the directory specified by EMBPERL_OBJECT_STOPDIR.
This page is then called as frame for building the real page. Addtionaly EmbperlObject sets the search path to contain all directories it had to walk before finding that page. If EMBPERL_OBJECT_STOPDIR is set the path contains all directories up to the in EMBPERL_OBJECT_STOPDIR specified one.
This frame page can now include other pages, using the HTML::Embperl::Execute method. Because the search path is set by EmbperlObject the included files are searched in the directories starting at the directory of the original request walking up thru the directory which contains the base page. This means that you can have common files, like header, footer etc. in the base directory and override them as necessary in the subdirectory.
To include the original requested file, you need to call Execute with a * as filename. To call the the same file, but in an upper directory you can use the special shortcut ../*.
Additionaly EmbperlObject sets up a inherence hierachie for you: The requested page inherit from the base page and the base page inherit from a class which could be specified by EMBPERL_OBJECT_HANDLER_CLASS, or if EMBPERL_OBJECT_HANDLER_CLASS is not set, from HTML::Embperl::Req. That allows you to define methods in base page and overwrite them as neccessary in the original requested files.
For this purpose a request object, which is blessed into the package of the requested page, is given as first parameter to each page (in $_[0]). Because this request object is a hashref, you can also use it to store additional data, which should be available in all components. Embperl does not use this hash itself, so you are free to store whatever you want. Methods can be ordinary Perl subs (defined with [! sub foo { ... } !] ) or Embperl subs (defined with [$sub foo $] .... [$endsub $]) .
<<lessSYNOPSIS
< Location /foo >
PerlSetEnv EMBPERL_OBJECT_BASE base.htm
PerlSetEnv EMBPERL_FILESMATCH ".htm.?|.epl$"
SetHandler perl-script
PerlHandler HTML::EmbperlObject
Options ExecCGI
< /Location >
HTML::EmbperlObject allows you to build object-oriented (OO) websites using HTML components which implement inheritance via subdirectories. This enables elegant architectures and encourages code reuse. The use of inheritance also enables a website-wide "look and feel" to be specified in a single HTML file, which is then used as a template for every other page on the site. This template can include other modules which can be overridden in subdirectories; even the template itself can be overridden. In a nutshell, EmbperlObject makes the design of large websites much more intuitive, allowing object-oriented concepts to be utilised to the fullest while staying within the "rapid application development" model of Perl and HTML.
HTML::EmbperlObject is basicly a mod_perl handler or could be invoked offline and helps you to build a whole page out of smaller parts. Basicly it does the following:
When a request comes in, a page, which name is specified by EMBPERL_OBJECT_BASE, is searched in the same directory as the requested page. If the pages isnt found, EmbperlObject walking up the directory tree until it finds the page, or it reaches DocumentRoot or the directory specified by EMBPERL_OBJECT_STOPDIR.
This page is then called as frame for building the real page. Addtionaly EmbperlObject sets the search path to contain all directories it had to walk before finding that page. If EMBPERL_OBJECT_STOPDIR is set the path contains all directories up to the in EMBPERL_OBJECT_STOPDIR specified one.
This frame page can now include other pages, using the HTML::Embperl::Execute method. Because the search path is set by EmbperlObject the included files are searched in the directories starting at the directory of the original request walking up thru the directory which contains the base page. This means that you can have common files, like header, footer etc. in the base directory and override them as necessary in the subdirectory.
To include the original requested file, you need to call Execute with a * as filename. To call the the same file, but in an upper directory you can use the special shortcut ../*.
Additionaly EmbperlObject sets up a inherence hierachie for you: The requested page inherit from the base page and the base page inherit from a class which could be specified by EMBPERL_OBJECT_HANDLER_CLASS, or if EMBPERL_OBJECT_HANDLER_CLASS is not set, from HTML::Embperl::Req. That allows you to define methods in base page and overwrite them as neccessary in the original requested files.
For this purpose a request object, which is blessed into the package of the requested page, is given as first parameter to each page (in $_[0]). Because this request object is a hashref, you can also use it to store additional data, which should be available in all components. Embperl does not use this hash itself, so you are free to store whatever you want. Methods can be ordinary Perl subs (defined with [! sub foo { ... } !] ) or Embperl subs (defined with [$sub foo $] .... [$endsub $]) .
Download (0.35MB)
Added: 2006-09-01 License: Perl Artistic License Price:
1148 downloads
Python Web Objects 1.3
Python Web Objects is a dynamic page generation system that allows the developer to embed Python code inside HTML. more>>
Python Web Objects is a dynamic page generation system that allows the developer to embed Python code inside HTML. It is similar in function to what JSP is to Java. ts a module that runs under mod_python and the Apache webserver. It is designed to offer a good balance between a providing a clean way to integrate design content from code, while doing so as fast as possible.
Download the latest version, then read the documentation. If youre into antiques, you can always browse the archives, but theres no reason to use an old version.
To install PWO, first decompress the tarball you downloaded.
$ gunzip pwo-0.XX.tar.gz
$ tar xvf pwo-0.XX.tar
Then, copy the pwo.py module into some location in your PYTHONPATH. The proper location is usually /usr/local/lib/python2.x/site-packages/
$ cp pwo-0.XX/pwo.py /usr/local/lib/python2.2/site-packages/
PWO should now be ready to use.
To configure a directory to make PWO pages, you first need to make sure that the directory is visible on the web. Ask your friendly Apache sysadmin if you dont know what this means. In this document, the path youll be keeping your .pwo files in is called /path/to/pwodir/, and its corresponding URL is http://yourserver/url/to/pwodir/.
Let Apache and mod_python know that the pwo.py will be handling requests to .pwo files in that directory. Do this by adding a few lines to our entry in your httpd.conf file.
AddHandler python-program .pwo
PythonHandler pwo
PythonDebug On
The PythonDebug directive is optional, but you will most likely want it enabled while you are developing. It will make exceptions print tracebacks to the browser in plain-text format. For security reasons, you should comment it out on production systems.
Now a file /path/to/pwodir/some_file.pwo will generate its page at http://yourserver/url/to/pwodir/some_file.pwo. Try copying a simple one of the included samples, like hello.pwo, to this directory to test your installation.
If youve never used PWO before, learn the syntax, and/or check out some sample pages.
<<lessDownload the latest version, then read the documentation. If youre into antiques, you can always browse the archives, but theres no reason to use an old version.
To install PWO, first decompress the tarball you downloaded.
$ gunzip pwo-0.XX.tar.gz
$ tar xvf pwo-0.XX.tar
Then, copy the pwo.py module into some location in your PYTHONPATH. The proper location is usually /usr/local/lib/python2.x/site-packages/
$ cp pwo-0.XX/pwo.py /usr/local/lib/python2.2/site-packages/
PWO should now be ready to use.
To configure a directory to make PWO pages, you first need to make sure that the directory is visible on the web. Ask your friendly Apache sysadmin if you dont know what this means. In this document, the path youll be keeping your .pwo files in is called /path/to/pwodir/, and its corresponding URL is http://yourserver/url/to/pwodir/.
Let Apache and mod_python know that the pwo.py will be handling requests to .pwo files in that directory. Do this by adding a few lines to our entry in your httpd.conf file.
AddHandler python-program .pwo
PythonHandler pwo
PythonDebug On
The PythonDebug directive is optional, but you will most likely want it enabled while you are developing. It will make exceptions print tracebacks to the browser in plain-text format. For security reasons, you should comment it out on production systems.
Now a file /path/to/pwodir/some_file.pwo will generate its page at http://yourserver/url/to/pwodir/some_file.pwo. Try copying a simple one of the included samples, like hello.pwo, to this directory to test your installation.
If youve never used PWO before, learn the syntax, and/or check out some sample pages.
Download (0.017MB)
Added: 2006-06-23 License: BSD License Price:
1218 downloads
HTML::Tree::AboutObjects 3.23
HTML::Tree::AboutObjects is an article: Users View of Object-Oriented Modules. more>>
HTML::Tree::AboutObjects is an article: "Users View of Object-Oriented Modules".
SYNOPSIS
# This an article, not a module.
The following article by Sean M. Burke first appeared in The Perl Journal #17 and is copyright 2000 The Perl Journal. It appears courtesy of Jon Orwant and The Perl Journal. This document may be distributed under the same terms as Perl itself.
<<lessSYNOPSIS
# This an article, not a module.
The following article by Sean M. Burke first appeared in The Perl Journal #17 and is copyright 2000 The Perl Journal. It appears courtesy of Jon Orwant and The Perl Journal. This document may be distributed under the same terms as Perl itself.
Download (0.11MB)
Added: 2007-08-15 License: Perl Artistic License Price:
800 downloads
Active Objects 2007-03-04
Active Objects is an implementation of the Active Object concept based on the boost::thread, boost::bind, boost::function libs. more>>
Active Objects is an implementation of the Active Object concept based on the boost::thread, boost::bind, and boost::function libraries.
The point of the library is to make taking advantage of multiprocessor machines as easy as possible. The library provides two types of functionality. The first is the ability to execute a function in a separate thread and automatically synchronize with the thread when the return value is needed.
The second is the ability to easily create a message cue for any existing class, and have that class process its messages asynchronously.
Enhancements:
- Minor code cleanup and code documentation updates.
<<lessThe point of the library is to make taking advantage of multiprocessor machines as easy as possible. The library provides two types of functionality. The first is the ability to execute a function in a separate thread and automatically synchronize with the thread when the return value is needed.
The second is the ability to easily create a message cue for any existing class, and have that class process its messages asynchronously.
Enhancements:
- Minor code cleanup and code documentation updates.
Download (0.32MB)
Added: 2007-03-07 License: Other/Proprietary License with Source Price:
961 downloads
pHoToMoLo 1.2.4
pHoToMoLo is a toolset for managing JPEG images in JFIF or Exif format. more>>
pHoToMoLo is a toolset for managing JPEG images in Exif or JFIF format. Photomolo generates a static HTML 4.01- and CSS 1-based multi-resolution image gallery for a directory tree containing images.
Exifiron losslessly compresses and corrects the orientation of Exif JPEG images. Jpegnail removes or embeds thumbnails. Jpegcom lets you edit embedded image comments using any text editor and image viewer.
A shell script frontend for Exifiron is included for copying images from removable storage, such as USB or Compact Flash.+
photomolo
generates a static HTML and CSS based multi-resolution image gallery for a directory tree containing images
exifiron
losslessly compresses and corrects the orientation of Exif JPEG images.
jpegnail
removes or embeds thumbnails to reduce file size or to speed up programs that make use of embedded thumbnails
jpegcom
lets you edit embedded image comments using any text editor and image viewer
Installation:
The "photomolo", "exifiron" and "jpegnail" utilities depend on the JPEG library by the Independent JPEG Group.
The files in the "examples" directory are in the public domain. They are not installed by default, as you will probably want to adapt them for your needs.
The "photocopy" script is a simple front-end for exifiron, for copying and optimising images from the file system of a digital camera.
To build and install the "photomolo", "exifiron", "jpegnail" and "jpegcom" programs on Debian GNU/Linux, you may use the following commands:
apt-get install libjpeg62-dev
make
make PREFIX=/usr/local install installman
To build the programs on other Unix-like systems:
# get and unpack the libjpeg source code
wget ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz
gzip -dc jpegsrc.v6b.tar.gz | tar xf -
# compile libjpeg
cd jpeg-6b; ./configure; make; cd ..
# unpack the photomolo source code
gzip -dc photomolo-1.2.4.tar.gz | tar xf -
# compile "photomolo", "exifiron", "jpegnail" and "jpegcom"
cd photomolo-1.2.4
make INCLUDES=-I../jpeg-6b LIBS=../jpeg-6b/libjpeg.a
make PREFIX=/usr/local install installman
<<lessExifiron losslessly compresses and corrects the orientation of Exif JPEG images. Jpegnail removes or embeds thumbnails. Jpegcom lets you edit embedded image comments using any text editor and image viewer.
A shell script frontend for Exifiron is included for copying images from removable storage, such as USB or Compact Flash.+
photomolo
generates a static HTML and CSS based multi-resolution image gallery for a directory tree containing images
exifiron
losslessly compresses and corrects the orientation of Exif JPEG images.
jpegnail
removes or embeds thumbnails to reduce file size or to speed up programs that make use of embedded thumbnails
jpegcom
lets you edit embedded image comments using any text editor and image viewer
Installation:
The "photomolo", "exifiron" and "jpegnail" utilities depend on the JPEG library by the Independent JPEG Group.
The files in the "examples" directory are in the public domain. They are not installed by default, as you will probably want to adapt them for your needs.
The "photocopy" script is a simple front-end for exifiron, for copying and optimising images from the file system of a digital camera.
To build and install the "photomolo", "exifiron", "jpegnail" and "jpegcom" programs on Debian GNU/Linux, you may use the following commands:
apt-get install libjpeg62-dev
make
make PREFIX=/usr/local install installman
To build the programs on other Unix-like systems:
# get and unpack the libjpeg source code
wget ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz
gzip -dc jpegsrc.v6b.tar.gz | tar xf -
# compile libjpeg
cd jpeg-6b; ./configure; make; cd ..
# unpack the photomolo source code
gzip -dc photomolo-1.2.4.tar.gz | tar xf -
# compile "photomolo", "exifiron", "jpegnail" and "jpegcom"
cd photomolo-1.2.4
make INCLUDES=-I../jpeg-6b LIBS=../jpeg-6b/libjpeg.a
make PREFIX=/usr/local install installman
Download (0.076MB)
Added: 2006-02-24 License: GPL (GNU General Public License) Price:
1337 downloads
Database of Managed Objects 2.4 Beta
DMO stands for Database of Managed Objects. more>>
DMO stands for "Database of Managed Objects." This is a tool for documenting all objects within a data center.
Database of Managed Objects provides an object-based overlay on a MySQL database, with a Web-based interface, which allows new objects to be defined in a hierarchy.
Each object can have attributes defined, which are inherited by objects below in the hierarchy. Information can be imported in CSV or XML format, and reports can be produced in XML, CSV, PDF and HTML formats.
DMO uses PHP and MySQL to support documentation of all network and system objects within your computing environment. It offers a Web interface that enables easy navigation through objects, instances and attributes, with XML and access controls.
Enhancements:
- This is the first significant release of DMO for nearly two years.
- It works with Linux and Windows (XAMPP), but should work well with any LAMP stack including PHP4.
- New features include much more graphical viewing, as well as mapping objects onto maps with drill-down to additional layers of maps following dependency trails, a new Flash viewer for browsing through objects, and the ability to create chains of objects based on any attribute type (where any other object can be an attribute of any other object).
<<lessDatabase of Managed Objects provides an object-based overlay on a MySQL database, with a Web-based interface, which allows new objects to be defined in a hierarchy.
Each object can have attributes defined, which are inherited by objects below in the hierarchy. Information can be imported in CSV or XML format, and reports can be produced in XML, CSV, PDF and HTML formats.
DMO uses PHP and MySQL to support documentation of all network and system objects within your computing environment. It offers a Web interface that enables easy navigation through objects, instances and attributes, with XML and access controls.
Enhancements:
- This is the first significant release of DMO for nearly two years.
- It works with Linux and Windows (XAMPP), but should work well with any LAMP stack including PHP4.
- New features include much more graphical viewing, as well as mapping objects onto maps with drill-down to additional layers of maps following dependency trails, a new Flash viewer for browsing through objects, and the ability to create chains of objects based on any attribute type (where any other object can be an attribute of any other object).
Download (14.4MB)
Added: 2007-08-01 License: GPL (GNU General Public License) Price:
814 downloads
HTML::LoL 1.3
HTML::LoL is a Perl module that can construct HTML from pleasing Perl data structures. more>>
HTML::LoL is a Perl module that can construct HTML from pleasing Perl data structures.
SYNOPSIS
use HTML::LoL;
&hl(sub { print shift },
[body => {bgcolor => white},
[p => Document body, ...], ...]);
This module allows you to use Perl syntax to express HTML. The function hl() converts Perl list-of-list structures into HTML strings.
The first argument to hl() is a callback function thats passed one argument: a fragment of generated HTML. This callback is invoked repeatedly with successive fragments until all the HTML is generated; the callback is responsible for assembling the fragments in the desired output location (e.g., a string or file).
The remaining arguments to hl() are Perl objects representing HTML, as follows:
[TAG, ...]
TAG is a string (the name of an HTML element); remaining list items are any of the forms described herein. Corresponds to < TAG >...< /TAG >. If TAG is an "empty element" according to %HTML::Tagset::emptyElement, then the < /TAG > is omitted.
[TAG => {ATTR1 => VAL1, ATTR2 => VAL2, ...}, ...]
Corresponds to < TAG ATTR1="VAL1" ATTR2="VAL2" ... >...< /TAG >. (As above, < /TAG > is omitted if TAG is an "empty element.") Each ATTR is a string. Each VAL is either a string, in which case the value gets HTML-entity-encoded when copied to the output, or a list reference containing a single string (viz. [VAL]) in which case the value is copied literally.
Finally, for boolean-valued attributes, VAL may be hl_bool(BOOLEAN), where BOOLEAN is a Perl expression. If BOOLEAN is true, the attribute is included in the output; otherwise its omitted.
Any string
Strings are copied verbatim to the output after entity-encoding.
hl_noquote(...)
Suppresses entity-encoding of its arguments.
hl_requote(...)
Reenables entity-encoding of its arguments (use it inside a call to hl_noquote()).
hl_preserve(...)
Normally, HTML::LoL tries to optimize the whitespace in the HTML it emits (without changing the meaning of the HTML). This suppresses that behavior within its arguments.
hl_entity(NAME)
Includes the HTML character-entity named NAME.
The return value of hl() is the result of the last call to the callback function. This means its possible to write
&hl(sub { $accumulator .= shift }, ...)
to have hl() return a string containing the completely rendered HTML.
<<lessSYNOPSIS
use HTML::LoL;
&hl(sub { print shift },
[body => {bgcolor => white},
[p => Document body, ...], ...]);
This module allows you to use Perl syntax to express HTML. The function hl() converts Perl list-of-list structures into HTML strings.
The first argument to hl() is a callback function thats passed one argument: a fragment of generated HTML. This callback is invoked repeatedly with successive fragments until all the HTML is generated; the callback is responsible for assembling the fragments in the desired output location (e.g., a string or file).
The remaining arguments to hl() are Perl objects representing HTML, as follows:
[TAG, ...]
TAG is a string (the name of an HTML element); remaining list items are any of the forms described herein. Corresponds to < TAG >...< /TAG >. If TAG is an "empty element" according to %HTML::Tagset::emptyElement, then the < /TAG > is omitted.
[TAG => {ATTR1 => VAL1, ATTR2 => VAL2, ...}, ...]
Corresponds to < TAG ATTR1="VAL1" ATTR2="VAL2" ... >...< /TAG >. (As above, < /TAG > is omitted if TAG is an "empty element.") Each ATTR is a string. Each VAL is either a string, in which case the value gets HTML-entity-encoded when copied to the output, or a list reference containing a single string (viz. [VAL]) in which case the value is copied literally.
Finally, for boolean-valued attributes, VAL may be hl_bool(BOOLEAN), where BOOLEAN is a Perl expression. If BOOLEAN is true, the attribute is included in the output; otherwise its omitted.
Any string
Strings are copied verbatim to the output after entity-encoding.
hl_noquote(...)
Suppresses entity-encoding of its arguments.
hl_requote(...)
Reenables entity-encoding of its arguments (use it inside a call to hl_noquote()).
hl_preserve(...)
Normally, HTML::LoL tries to optimize the whitespace in the HTML it emits (without changing the meaning of the HTML). This suppresses that behavior within its arguments.
hl_entity(NAME)
Includes the HTML character-entity named NAME.
The return value of hl() is the result of the last call to the callback function. This means its possible to write
&hl(sub { $accumulator .= shift }, ...)
to have hl() return a string containing the completely rendered HTML.
Download (0.005MB)
Added: 2007-07-05 License: Perl Artistic License Price:
843 downloads
HTML::GenToc 2.30
HTML::GenToc is a Perl module that generate a Table of Contents for HTML documents. more>>
HTML::GenToc is a Perl module that generate a Table of Contents for HTML documents.
SYNOPSIS
use HTML::GenToc;
# create a new object
my $toc = new HTML::GenToc();
my $toc = new HTML::GenToc(title=>"Table of Contents",
toc=>$my_toc_file,
toc_entry=>{
H1=>1,
H2=>2
},
toc_end=>{
H1=>/H1,
H2=>/H2
}
);
# add further arguments
$toc->args(toc_tag=>"BODY",
toc_tag_replace=>0,
);
# generate anchors for a file
$toc->generate_anchors(infile=>$html_file,
overwrite=>0,
);
# generate a ToC from a file
$toc->generate_toc(infile=>$html_file,
footer=>$footer_file,
header=>$header_file
);
HTML::GenToc generates anchors and a table of contents for HTML documents. Depending on the arguments, it will insert the information it generates, or output to a string, a separate file or STDOUT.
While it defaults to taking H1 and H2 elements as the significant elements to put into the table of contents, any tag can be defined as a significant element. Also, it doesnt matter if the input HTML code is complete, pure HTML, one can input pseudo-html or page-fragments, which makes it suitable for using on templates and HTML meta-languages such as WML.
Also included in the distrubution is hypertoc, a script which uses the module so that one can process files on the command-line in a user-friendly manner.
<<lessSYNOPSIS
use HTML::GenToc;
# create a new object
my $toc = new HTML::GenToc();
my $toc = new HTML::GenToc(title=>"Table of Contents",
toc=>$my_toc_file,
toc_entry=>{
H1=>1,
H2=>2
},
toc_end=>{
H1=>/H1,
H2=>/H2
}
);
# add further arguments
$toc->args(toc_tag=>"BODY",
toc_tag_replace=>0,
);
# generate anchors for a file
$toc->generate_anchors(infile=>$html_file,
overwrite=>0,
);
# generate a ToC from a file
$toc->generate_toc(infile=>$html_file,
footer=>$footer_file,
header=>$header_file
);
HTML::GenToc generates anchors and a table of contents for HTML documents. Depending on the arguments, it will insert the information it generates, or output to a string, a separate file or STDOUT.
While it defaults to taking H1 and H2 elements as the significant elements to put into the table of contents, any tag can be defined as a significant element. Also, it doesnt matter if the input HTML code is complete, pure HTML, one can input pseudo-html or page-fragments, which makes it suitable for using on templates and HTML meta-languages such as WML.
Also included in the distrubution is hypertoc, a script which uses the module so that one can process files on the command-line in a user-friendly manner.
Download (0.043MB)
Added: 2006-06-16 License: Perl Artistic License Price:
1225 downloads
HTML::QuickTable 1.12
HTML::QuickTable is a Perl module to quickly create fairly complex HTML tables. more>>
HTML::QuickTable is a Perl module to quickly create fairly complex HTML tables.
SYNOPSIS
use HTML::QuickTable;
my $qt = HTML::QuickTable->new(
table_width => 95%, # opt method 1
td => {bgcolor => gray}, # opt method 2
font_face => arial, # set font
font => {face => arial}, # same thing
labels => 1, # make top
<<lessSYNOPSIS
use HTML::QuickTable;
my $qt = HTML::QuickTable->new(
table_width => 95%, # opt method 1
td => {bgcolor => gray}, # opt method 2
font_face => arial, # set font
font => {face => arial}, # same thing
labels => 1, # make top
Download (0.014MB)
Added: 2006-09-29 License: Perl Artistic License Price:
1123 downloads
HTML::Seamstress 4.26
HTML::Seamstress is a HTML::Tree subclass for HTML templating via tree rewriting. more>>
HTML::Seamstress is a HTML::Tree subclass for HTML templating via tree rewriting.
SYNOPSIS
HTML::Seamstress provides "fourth generation" dynamic HTML generation (templating).
In the beginning we had...
First generation dynamic HTML production
First generation dynamic HTML production used server-side includes:
< p >Todays date is < !--#echo var="DATE_LOCAL" -- > < /p >
Second generation dynamic HTML production
The next phase of HTML generation saw embedded HTML snippets in Perl code. For example:
sub header {
my $title = shift;
print $title< /title >
< /head >
EOHEADER
}
<<lessSYNOPSIS
HTML::Seamstress provides "fourth generation" dynamic HTML generation (templating).
In the beginning we had...
First generation dynamic HTML production
First generation dynamic HTML production used server-side includes:
< p >Todays date is < !--#echo var="DATE_LOCAL" -- > < /p >
Second generation dynamic HTML production
The next phase of HTML generation saw embedded HTML snippets in Perl code. For example:
sub header {
my $title = shift;
print $title< /title >
< /head >
EOHEADER
}
Download (0.048MB)
Added: 2006-09-14 License: Perl Artistic License Price:
1135 downloads
HTML::ActiveLink 1.02
HTML::ActiveLink module dynamically activate HTML links based on URL. more>>
HTML::ActiveLink module dynamically activate HTML links based on URL.
SYNOPSIS
use HTML::ActiveLink;
my $al = new HTML::ActiveLink;
print $al->activelink(@html_doc);
I dont know about you, but one of the main problems I have with HTML content is getting images and links to "turn on" depending on the current URL location. That is, I like authoring one set of templates, something like this:
[ < a href="/" >Home< /a > | < a href="/faq/" >FAQ< /a >
| < a href="/about/" >About Us< /a > ]
And then having the appropriate link turned on, so that if Im running inside the /home/ directory, the above turns into this:
[ < font color="red" >Home< /font > | < a href="/faq/" >FAQ< /a >
| < a href="/about/" >About Us< /a > ]
Without having to write a whole bunch of ifs, or writing a bunch of different sets of templates, etc.
This module handles the above process automatically. By default, it will activate any text or images with < a href > tags around them by stripping the link off and changing the appearance of text and names of images. All transformations are fully customizable, allowing you to choose how your active text should look. HTML::ActiveLink can even automatically construct imagemaps depending on your location.
In the simplest case, all you have to do is create a new object by a call to new(), and then call the main activelink() function which takes care of the transformation. To customize what the output HTML looks like, keep reading...
<<lessSYNOPSIS
use HTML::ActiveLink;
my $al = new HTML::ActiveLink;
print $al->activelink(@html_doc);
I dont know about you, but one of the main problems I have with HTML content is getting images and links to "turn on" depending on the current URL location. That is, I like authoring one set of templates, something like this:
[ < a href="/" >Home< /a > | < a href="/faq/" >FAQ< /a >
| < a href="/about/" >About Us< /a > ]
And then having the appropriate link turned on, so that if Im running inside the /home/ directory, the above turns into this:
[ < font color="red" >Home< /font > | < a href="/faq/" >FAQ< /a >
| < a href="/about/" >About Us< /a > ]
Without having to write a whole bunch of ifs, or writing a bunch of different sets of templates, etc.
This module handles the above process automatically. By default, it will activate any text or images with < a href > tags around them by stripping the link off and changing the appearance of text and names of images. All transformations are fully customizable, allowing you to choose how your active text should look. HTML::ActiveLink can even automatically construct imagemaps depending on your location.
In the simplest case, all you have to do is create a new object by a call to new(), and then call the main activelink() function which takes care of the transformation. To customize what the output HTML looks like, keep reading...
Download (0.006MB)
Added: 2007-08-07 License: Perl Artistic License Price:
809 downloads
HTML::Toc 0.21
HTML::Toc module can generate, insert and update HTML Table of Contents. more>>
HTML::Toc module can generate, insert and update HTML Table of Contents.
The HTML::Toc consists out of the following packages:
HTML::Toc
HTML::TocGenerator
HTML::TocInsertor
HTML::TocUpdator
HTML::Toc is the object which will eventually hold the Table of Contents. HTML::TocGenerator does the actual generation of the ToC. HTML::TocInsertor handles the insertion of the ToC in the source. HTML::TocUpdator takes care of updating previously inserted ToCs.
HTML::Parser is the base object of HTML::TocGenerator, HTML::TocInsertor and HTML::TocUpdator. Each of these objects uses its predecessor as its ancestor, as shown in the UML diagram underneath:
+---------------------+
| HTML::Parser |
+---------------------+
+---------------------+
| +parse() |
| +parse_file() |
+----------+----------+
/_
|
+----------+----------+ +-----------+
| HTML::TocGenerator + - - - - - -+ HTML::Toc |
+---------------------+ +-----------+
+---------------------+ +-----------+
| +extend() | | +clear() |
| +extendFromFile() | | +format() |
| +generate() | +-----+-----+
| +generateFromFile() | :
+----------+----------+ :
/_ :
| :
+----------+----------+ :
| HTML::TocInsertor + - - - - - - - - -+
+---------------------+ :
+---------------------+ :
| +insert() | :
| +insertIntoFile() | :
+----------+----------+ :
/_ :
| :
+----------+----------+ :
| HTML::TocUpdator + - - - - - - - - -+
+---------------------+
+---------------------+
| +insert() |
| +insertIntoFile() |
| +update() |
| +updateFile() |
+---------------------+
When generating a ToC youll have to decide which object you want to use:
TocGenerator:
for generating a ToC without inserting the ToC into the source
TocInsertor:
for generating a ToC and inserting the ToC into the source
TocUpdator:
for generating and inserting a ToC, removing any previously inserted ToC elements
Thus in tabular view, each object is capable of:
generating inserting updating
---------------------------------
TocGenerator X
TocInsertor X X
TocUpdator X X X
<<lessThe HTML::Toc consists out of the following packages:
HTML::Toc
HTML::TocGenerator
HTML::TocInsertor
HTML::TocUpdator
HTML::Toc is the object which will eventually hold the Table of Contents. HTML::TocGenerator does the actual generation of the ToC. HTML::TocInsertor handles the insertion of the ToC in the source. HTML::TocUpdator takes care of updating previously inserted ToCs.
HTML::Parser is the base object of HTML::TocGenerator, HTML::TocInsertor and HTML::TocUpdator. Each of these objects uses its predecessor as its ancestor, as shown in the UML diagram underneath:
+---------------------+
| HTML::Parser |
+---------------------+
+---------------------+
| +parse() |
| +parse_file() |
+----------+----------+
/_
|
+----------+----------+ +-----------+
| HTML::TocGenerator + - - - - - -+ HTML::Toc |
+---------------------+ +-----------+
+---------------------+ +-----------+
| +extend() | | +clear() |
| +extendFromFile() | | +format() |
| +generate() | +-----+-----+
| +generateFromFile() | :
+----------+----------+ :
/_ :
| :
+----------+----------+ :
| HTML::TocInsertor + - - - - - - - - -+
+---------------------+ :
+---------------------+ :
| +insert() | :
| +insertIntoFile() | :
+----------+----------+ :
/_ :
| :
+----------+----------+ :
| HTML::TocUpdator + - - - - - - - - -+
+---------------------+
+---------------------+
| +insert() |
| +insertIntoFile() |
| +update() |
| +updateFile() |
+---------------------+
When generating a ToC youll have to decide which object you want to use:
TocGenerator:
for generating a ToC without inserting the ToC into the source
TocInsertor:
for generating a ToC and inserting the ToC into the source
TocUpdator:
for generating and inserting a ToC, removing any previously inserted ToC elements
Thus in tabular view, each object is capable of:
generating inserting updating
---------------------------------
TocGenerator X
TocInsertor X X
TocUpdator X X X
Download (0.042MB)
Added: 2007-08-15 License: Perl Artistic License Price:
800 downloads
HTML::DWT 2.08
HTML::DWT is a Perl module with DreamWeaver HTML Template. more>>
HTML::DWT is a Perl module with DreamWeaver HTML Template.
INSTALLATION
Unzip/tar the archive:
tar xvfz HTML-DWT-2.08
Create the makefile
perl Makefile.PL
Make the module (must have root access to install)
make
make test
make install
SYNOPSIS
use HTML::DWT;
$template = new HTML::DWT(filename => "file.dwt");
%dataHash = (
doctitle => DWT Generated,
leftcont => some HTML content here
);
$html = $template->fill(%dataHash);
or
use HTML::DWT qw(:Template);
$template = new HTML::DWT(filename => "file.dwt");
$template->param(
doctitle => < title >DWT Generated< /title >,
leftcont => Some HTML content here
);
$html = $template->output();
A perl module designed to parse a simple HTML template file generated by Macromedia Dreamweaver and replace fields in the template with values from a CGI script.
<<lessINSTALLATION
Unzip/tar the archive:
tar xvfz HTML-DWT-2.08
Create the makefile
perl Makefile.PL
Make the module (must have root access to install)
make
make test
make install
SYNOPSIS
use HTML::DWT;
$template = new HTML::DWT(filename => "file.dwt");
%dataHash = (
doctitle => DWT Generated,
leftcont => some HTML content here
);
$html = $template->fill(%dataHash);
or
use HTML::DWT qw(:Template);
$template = new HTML::DWT(filename => "file.dwt");
$template->param(
doctitle => < title >DWT Generated< /title >,
leftcont => Some HTML content here
);
$html = $template->output();
A perl module designed to parse a simple HTML template file generated by Macromedia Dreamweaver and replace fields in the template with values from a CGI script.
Download (0.017MB)
Added: 2006-09-20 License: Perl Artistic License Price:
1141 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 html objects 1.2.4 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