Chip 2000 May

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2000 May / Chip_2000-05_cd1.bin / zkuste / Perl / ActivePerl-5.6.0.613.msi / 䆊䌷䈹䈙䏵-䞅䞆䞀㡆䞃䄦䠥 / _a58fed799f362cbf5d805bc4b7f5a089 < prev next >

Wrap

Text File | 2000-03-23 | 38.4 KB | 903 lines

<HTML> <HEAD> <TITLE>HTML::Stream - HTML output stream class, and some markup utilities</TITLE> <LINK REL="stylesheet" HREF="../../../Active.css" TYPE="text/css"> <LINK REV="made" HREF="mailto:"> </HEAD> <BODY> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> HTML::Stream - HTML output stream class, and some markup utilities </TD></TR> </TABLE> <A NAME="__index__"></A>  <UL> <LI><A HREF="#name">NAME</A></LI><LI><A HREF="#supportedplatforms">SUPPORTED PLATFORMS</A></LI> <LI><A HREF="#synopsis">SYNOPSIS</A></LI> <LI><A HREF="#description">DESCRIPTION</A></LI> <LI><A HREF="#introduction (the neapolitan dessert special)">INTRODUCTION (the Neapolitan dessert special)</A></LI> <UL> <LI><A HREF="#function interface">Function interface</A></LI> <LI><A HREF="#oo interface, vanilla">OO interface, vanilla</A></LI> <LI><A HREF="#oo interface, chocolate">OO interface, chocolate</A></LI> <LI><A HREF="#oo interface, with whipped cream">OO interface, with whipped cream</A></LI> <LI><A HREF="#oo interface, strawberry">OO interface, strawberry</A></LI> </UL> <LI><A HREF="#advanced topics">ADVANCED TOPICS</A></LI> <UL> <LI><A HREF="#autoformatting and inserting newlines">Auto-formatting and inserting newlines</A></LI> <LI><A HREF="#entities">Entities</A></LI> <LI><A HREF="#autoescaping: changing the way text is escaped">Auto-escaping: changing the way text is escaped</A></LI> <LI><A HREF="#outputting html to things besides filehandles">Outputting HTML to things besides filehandles</A></LI> <LI><A HREF="#subclassing">Subclassing</A></LI> </UL> <LI><A HREF="#public interface">PUBLIC INTERFACE</A></LI> <UL> <LI><A HREF="#functions">Functions</A></LI> <LI><A HREF="#vanilla">Vanilla</A></LI> <LI><A HREF="#strawberry">Strawberry</A></LI> <LI><A HREF="#chocolate">Chocolate</A></LI> </UL> <LI><A HREF="#subclasses">SUBCLASSES</A></LI> <UL> <LI><A HREF="#html::stream::latin1">HTML::Stream::Latin1</A></LI> </UL> <LI><A HREF="#performance">PERFORMANCE</A></LI> <LI><A HREF="#why in the world did i write this">WHY IN THE WORLD DID I WRITE THIS?</A></LI> <LI><A HREF="#change log">CHANGE LOG</A></LI> <LI><A HREF="#version">VERSION</A></LI> <LI><A HREF="#acknowledgements">ACKNOWLEDGEMENTS</A></LI> <LI><A HREF="#author">AUTHOR</A></LI> </UL>  <HR> <H1><A NAME="name">NAME</A></H1> HTML::Stream - HTML output stream class, and some markup utilities <HR> <H1><A NAME="supportedplatforms">SUPPORTED PLATFORMS</A></H1> <UL> <LI>Linux</LI> <LI>Solaris</LI> <LI>Windows</LI> </UL> <HR> <H1><A NAME="synopsis">SYNOPSIS</A></H1> Here's small sample of some of the non-OO ways you can use this module: <PRE> use HTML::Stream qw(:funcs); </PRE> <PRE> print html_tag('A', HREF=>$link); print html_escape("<<Hello & welcome!>>");</PRE> And some of the OO ways as well: <PRE> use HTML::Stream; $HTML = new HTML::Stream \*STDOUT; </PRE> <PRE> # The vanilla interface... $HTML->tag('A', HREF=>"$href"); $HTML->tag('IMG', SRC=>"logo.gif", ALT=>"LOGO"); $HTML->text($copyright); $HTML->tag('_A');</PRE> <PRE> # The chocolate interface... $HTML -> A(HREF=>"$href"); $HTML -> IMG(SRC=>"logo.gif", ALT=>"LOGO"); $HTML -> t($caption); $HTML -> _A;</PRE> <PRE> # The chocolate interface, with whipped cream... $HTML -> A(HREF=>"$href") -> IMG(SRC=>"logo.gif", ALT=>"LOGO") -> t($caption) -> _A;</PRE> <PRE> # The strawberry interface... output $HTML [A, HREF=>"$href"], [IMG, SRC=>"logo.gif", ALT=>"LOGO"], $caption, [_A];</PRE> <HR> <H1><A NAME="description">DESCRIPTION</A></H1> The HTML::Stream module provides you with an object-oriented (and subclassable) way of outputting HTML. Basically, you open up an ``HTML stream'' on an existing filehandle, and then do all of your output to the HTML stream. You can intermix HTML-stream-output and ordinary-print-output, if you like. There's even a small built-in subclass, HTML::Stream::Latin1, which can handle Latin-1 input right out of the box. But all in good time... <HR> <H1><A NAME="introduction (the neapolitan dessert special)">INTRODUCTION (the Neapolitan dessert special)</A></H1> <H2><A NAME="function interface">Function interface</A></H2> Let's start out with the simple stuff. This module provides a collection of non-OO utility functions for escaping HTML text and producing HTML tags, like this: <PRE> use HTML::Stream qw(:funcs); # imports functions from @EXPORT_OK </PRE> <PRE> print html_tag(A, HREF=>$url); print '© 1996 by', html_escape($myname), '!'; print html_tag('/A');</PRE> By the way: that last line could be rewritten as: <PRE> print html_tag(_A);</PRE> And if you need to get a parameter in your tag that doesn't have an associated value, supply the undefined value (not the empty string!): <PRE> print html_tag(TD, NOWRAP=>undef, ALIGN=>'LEFT'); </PRE> <PRE> <TD NOWRAP ALIGN=LEFT></PRE> <PRE> print html_tag(IMG, SRC=>'logo.gif', ALT=>'');</PRE> <PRE> <IMG SRC="logo.gif" ALT=""></PRE> There are also some routines for reversing the process, like: <PRE> $text = "This isn't "fun"..."; print html_unmarkup($text); </PRE> <PRE> This isn't "fun"...</PRE> <PRE> print html_unescape($text);</PRE> <PRE> This isn't "fun"...</PRE> Yeah, yeah, yeah, I hear you cry. We've seen this stuff before. But wait! There's more... <H2><A NAME="oo interface, vanilla">OO interface, vanilla</A></H2> Using the function interface can be tedious... so we also provide an ``HTML output stream'' class. Messages to an instance of that class generally tell that stream to output some HTML. Here's the above example, rewritten using HTML streams: <PRE> use HTML::Stream; $HTML = new HTML::Stream \*STDOUT; </PRE> <PRE> $HTML->tag(A, HREF=>$url); $HTML->ent('copy'); $HTML->text(" 1996 by $myname!"); $HTML->tag(_A);</PRE> As you've probably guessed: <PRE> text() Outputs some text, which will be HTML-escaped. </PRE> <PRE> tag() Outputs an ordinary tag, like <A>, possibly with parameters. The parameters will all be HTML-escaped automatically.</PRE> <PRE> ent() Outputs an HTML entity, like the © or < . You mostly don't need to use it; you can often just put the Latin-1 representation of the character in the text().</PRE> You might prefer to use <CODE>t()</CODE> and <CODE>e()</CODE> instead of <CODE>text()</CODE> and <A HREF="#item_ent"><CODE>ent()</CODE></A>: they're absolutely identical, and easier to type: <PRE> $HTML -> tag(A, HREF=>$url); $HTML -> e('copy'); $HTML -> t(" 1996 by $myname!"); $HTML -> tag(_A);</PRE> Now, it wouldn't be nice to give you those <CODE>text()</CODE> and <A HREF="#item_ent"><CODE>ent()</CODE></A> shortcuts without giving you one for <CODE>tag()</CODE>, would it? Of course not... <H2><A NAME="oo interface, chocolate">OO interface, chocolate</A></H2> The known HTML tags are even given their own tag-methods, compiled on demand. The above code could be written even more compactly as: <PRE> $HTML -> A(HREF=>$url); $HTML -> e('copy'); $HTML -> t(" 1996 by $myname!"); $HTML -> _A;</PRE> As you've probably guessed: <PRE> A(HREF=>$url) == tag(A, HREF=>$url) == <A HREF="/the/url"> _A == tag(_A) == </A></PRE> All of the autoloaded ``tag-methods'' use the tagname in all-uppercase. A <CODE>"_"</CODE> prefix on any tag-method means that an end-tag is desired. The <CODE>"_"</CODE> was chosen for several reasons: (1) it's short and easy to type, (2) it doesn't produce much visual clutter to look at, (3) <CODE>_TAG</CODE> looks a little like <CODE>/TAG</CODE> because of the straight line. <UL> <LI> I know, I know... it looks like a private method. You get used to it. Really. </UL> I should stress that this module will only auto-create tag methods for known HTML tags. So you're protected from typos like this (which will cause a fatal exception at run-time): <PRE> $HTML -> IMGG(SRC=>$src);</PRE> (You're not yet protected from illegal tag parameters, but it's a start, ain't it?) If you need to make a tag known (sorry, but this is currently a global operation, and not stream-specific), do this: <PRE> accept_tag HTML::Stream 'MARQUEE'; # for you MSIE fans...</PRE> Note: there is no corresponding ``reject_tag''. I thought and thought about it, and could not convince myself that such a method would do anything more useful than cause other people's modules to suddenly stop working because some bozo function decided to reject the <CODE>FONT</CODE> tag. <H2><A NAME="oo interface, with whipped cream">OO interface, with whipped cream</A></H2> In the grand tradition of C++, output method chaining is supported in both the Vanilla Interface and the Chocolate Interface. So you can (and probably should) write the above code as: <PRE> $HTML -> A(HREF=>$url) -> e('copy') -> t(" 1996 by $myname!") -> _A;</PRE> But wait! Neapolitan ice cream has one more flavor... <H2><A NAME="oo interface, strawberry">OO interface, strawberry</A></H2> I was jealous of the compact syntax of HTML::AsSubs, but I didn't want to worry about clogging the namespace with a lot of functions like p(), a(), etc. (especially when markup-functions like <A HREF="../../../lib/Pod/perlfunc.html#item_tr"><CODE>tr()</CODE></A> conflict with existing Perl functions). So I came up with this: <PRE> output $HTML [A, HREF=>$url], "Here's my $caption", [_A];</PRE> Conceptually, arrayrefs are sent to <CODE>html_tag()</CODE>, and strings to <CODE>html_escape()</CODE>. <HR> <H1><A NAME="advanced topics">ADVANCED TOPICS</A></H1> <H2><A NAME="autoformatting and inserting newlines">Auto-formatting and inserting newlines</A></H2> Auto-formatting is the name I give to the Chocolate Interface feature whereby newlines (and maybe, in the future, other things) are inserted before or after the tags you output in order to make your HTML more readable. So, by default, this: <PRE> $HTML -> HTML -> HEAD -> TITLE -> t("Hello!") -> _TITLE -> _HEAD -> BODY(BGCOLOR=>'#808080');</PRE> Actually produces this: <PRE> <HTML><HTML> <HEAD> <TITLE>Hello!</TITLE> </HEAD> <BODY BGCOLOR="#808080"></PRE> To turn off autoformatting altogether on a given HTML::Stream object, use the <CODE>auto_format()</CODE> method: <PRE> $HTML->auto_format(0); # stop autoformatting!</PRE> To change whether a newline is automatically output before/after the begin/end form of a tag at a global level, use <CODE>set_tag()</CODE>: <PRE> HTML::Stream->set_tag('B', Newlines=>15); # 15 means "\n\n \n\n" HTML::Stream->set_tag('I', Newlines=>7); # 7 means "\n\n \n "</PRE> To change whether a newline is automatically output before/after the begin/end form of a tag for a given stream level, give the stream its own private ``tag info'' table, and then use <CODE>set_tag()</CODE>: <PRE> $HTML->private_tags; $HTML->set_tag('B', Newlines=>0); # won't affect anyone else!</PRE> To output newlines explicitly, just use the special <CODE>nl</CODE> method in the Chocolate Interface: <PRE> $HTML->nl; # one newline $HTML->nl(6); # six newlines</PRE> I am sometimes asked, ``why don't you put more newlines in automatically?'' Well, mostly because... <UL> <LI> Sometimes you'll be outputting stuff inside a <CODE>PRE</CODE> environment. <LI> Sometimes you really do want to jam things (like images, or table cell delimiters and the things they contain) right up against each other. </UL> So I've stuck to outputting newlines in places where it's most likely to be harmless. <H2><A NAME="entities">Entities</A></H2> As shown above, You can use the <A HREF="#item_ent"><CODE>ent()</CODE></A> (or <CODE>e()</CODE>) method to output an entity: <PRE> $HTML->t('Copyright ')->e('copy')->t(' 1996 by Me!');</PRE> But this can be a pain, particularly for generating output with non-ASCII characters: <PRE> $HTML -> t('Copyright ') -> e('copy') -> t(' 1996 by Fran') -> e('ccedil') -> t('ois, Inc.!');</PRE> Granted, Europeans can always type the 8-bit characters directly in their Perl code, and just have this: <PRE> $HTML -> t("Copyright \251 1996 by Fran\347ois, Inc.!');</PRE> But folks without 8-bit text editors can find this kind of output cumbersome to generate. Sooooooooo... <H2><A NAME="autoescaping: changing the way text is escaped">Auto-escaping: changing the way text is escaped</A></H2> Auto-escaping is the name I give to the act of taking an ``unsafe'' string (one with ``>'', ``&'', etc.), and magically outputting ``safe'' HTML. The default ``auto-escape'' behavior of an HTML stream can be a drag if you've got a lot character entities that you want to output, or if you're using the Latin-1 character set, or some other input encoding. Fortunately, you can use the <CODE>auto_escape()</CODE> method to change the way a particular HTML::Stream works at any time. First, here's a couple of special invocations: <PRE> $HTML->auto_escape('ALL'); # Default; escapes [<>"&] and 8-bit chars. $HTML->auto_escape('LATIN_1'); # Like ALL, but uses Latin-1 entities # instead of decimal equivalents. $HTML->auto_escape('NON_ENT'); # Like ALL, but leaves "&" alone.</PRE> You can also install your own auto-escape function (note that you might very well want to install it for just a little bit only, and then de-install it): <PRE> sub my_auto_escape { my $text = shift; HTML::Entities::encode($text); # start with default $text =~ s/$c$/©/ig; # (C) becomes copyright $text =~ s/\\,(c)/\&$1cedil;/ig; # \,c becomes a cedilla $text; } </PRE> <PRE> # Start using my auto-escape: my $old_esc = $HTML->auto_escape(\&my_auto_escape);</PRE> <PRE> # Output some stuff: $HTML-> IMG(SRC=>'logo.gif', ALT=>'Fran\,cois, Inc'); output $HTML 'Copyright (C) 1996 by Fran\,cois, Inc.!';</PRE> <PRE> # Stop using my auto-escape: $HTML->auto_escape($old_esc);</PRE> If you find yourself in a situation where you're doing this a lot, a better way is to create a subclass of HTML::Stream which installs your custom function when constructed. For an example, see the HTML::Stream::Latin1 subclass in this module. <H2><A NAME="outputting html to things besides filehandles">Outputting HTML to things besides filehandles</A></H2> As of Revision 1.21, you no longer need to supply <CODE>new()</CODE> with a filehandle: any object that responds to a print() method will do. Of course, this includes blessed FileHandles, and IO::Handles. If you supply a GLOB reference (like <CODE>\*STDOUT</CODE>) or a string (like <CODE>"Module::FH"</CODE>), HTML::Stream will automatically create an invisible object for talking to that filehandle (I don't dare bless it into a FileHandle, since the underlying descriptor would get closed when the HTML::Stream is destroyed, and you might not want that). You say you want to print to a string? For kicks and giggles, try this: <PRE> package StringHandle; sub new { my $self = ''; bless \$self, shift; } sub print { my $self = shift; $$self .= join('', @_); } </PRE> <PRE> package main; use HTML::Stream;</PRE> <PRE> my $SH = new StringHandle; my $HTML = new HTML::Stream $SH; $HTML -> H1 -> t("Hello & <<welcome>>!") -> _H1; print "PRINTED STRING: ", $$SH, "\n";</PRE> <H2><A NAME="subclassing">Subclassing</A></H2> This is where you can make your application-specific HTML-generating code much easier to look at. Consider this: <PRE> package MY::HTML; @ISA = qw(HTML::Stream); </PRE> <PRE> sub Aside { $_[0] -> FONT(SIZE=>-1) -> I; } sub _Aside { $_[0] -> _I -> _FONT; }</PRE> Now, you can do this: <PRE> my $HTML = new MY::HTML \*STDOUT; </PRE> <PRE> $HTML -> Aside -> t("Don't drink the milk, it's spoiled... pass it on...") -> _Aside;</PRE> If you're defining these markup-like, chocolate-interface-style functions, I recommend using mixed case with a leading capital. You probably shouldn't use all-uppercase, since that's what this module uses for real HTML tags. <HR> <H1><A NAME="public interface">PUBLIC INTERFACE</A></H1> <H2><A NAME="functions">Functions</A></H2> <DL> <DT><A NAME="item_html_escape_TEXT">html_escape TEXT</A> <DD> Given a TEXT string, turn the text into valid HTML by escaping ``unsafe'' characters. Currently, the ``unsafe'' characters are 8-bit characters plus: <PRE> < > = &</PRE> Note: provided for convenience and backwards-compatibility only. You may want to use the more-powerful HTML::Entities::encode function instead. <DT><A NAME="item_html_tag_TAG_%5B%2C_PARAM%3D%3EVALUE%2C_%2E%2E%2E%">html_tag TAG [, PARAM=>VALUE, ...]</A> <DD> Return the text for a given TAG, possibly with parameters. As an efficiency hack, only the values are HTML-escaped currently: it is assumed that the tag and parameters will already be safe. For convenience and readability, you can say <CODE>_A</CODE> instead of <CODE>"/A"</CODE> for the first tag, if you're into barewords. <DT><A NAME="item_html_unescape_TEXT">html_unescape TEXT</A> <DD> Remove angle-tag markup, and convert the standard ampersand-escapes (<CODE>lt</CODE>, <CODE>gt</CODE>, <CODE>amp</CODE>, <CODE>quot</CODE>, and <CODE>#ddd</CODE>) into ASCII characters. Note: provided for convenience and backwards-compatibility only. You may want to use the more-powerful HTML::Entities::decode function instead: unlike this function, it can collapse entities like <CODE>copy</CODE> and <CODE>ccedil</CODE> into their Latin-1 byte values. <DT><A NAME="item_html_unmarkup_TEXT">html_unmarkup TEXT</A> <DD> Remove angle-tag markup from TEXT, but do not convert ampersand-escapes. Cheesy, but theoretically useful if you want to, say, incorporate externally-provided HTML into a page you're generating, and are worried that the HTML might contain undesirable markup. </DL> <H2><A NAME="vanilla">Vanilla</A></H2> <DL> <DT><A NAME="item_new_%5BPRINTABLE%5D">new [PRINTABLE]</A> <DD> Class method. Create a new HTML output stream. The PRINTABLE may be a FileHandle, a glob reference, or any object that responds to a <A HREF="../../../lib/Pod/perlfunc.html#item_print"><CODE>print()</CODE></A> message. If no PRINTABLE is given, does a <A HREF="../../../lib/Pod/perlfunc.html#item_select"><CODE>select()</CODE></A> and uses that. <DT><A NAME="item_auto_escape_%5BNAME%7CSUBREF%5D">auto_escape [NAME|SUBREF]</A> <DD> Instance method. Set the auto-escape function for this HTML stream. If the argument is a subroutine reference SUBREF, then that subroutine will be used. Declare such subroutines like this: <PRE> sub my_escape { my $text = shift; # it's passed in the first argument ... $text; }</PRE> If a textual NAME is given, then one of the appropriate built-in functions is used. Possible values are: <DL> <DT><A NAME="item_ALL">ALL</A> <DD> Default for HTML::Stream objects. This escapes angle brackets, ampersands, double-quotes, and 8-bit characters. 8-bit characters are escaped using decimal entity codes (like <CODE>#123</CODE>). <DT><A NAME="item_LATIN_1">LATIN_1</A> <DD> Like <CODE>"ALL"</CODE>, but uses Latin-1 entity names (like <CODE>ccedil</CODE>) instead of decimal entity codes to escape characters. This makes the HTML more readable but it is currently not advised, as ``older'' browsers (like Netscape 2.0) do not recognize many of the ISO-8859-1 entity names (like <CODE>deg</CODE>). Warning: If you specify this option, you'll find that it attempts to ``require'' HTML::Entities at run time. That's because I didn't want to force you to have that module just to use the rest of HTML::Stream. To pick up problems at compile time, you are advised to say: <PRE> use HTML::Stream; use HTML::Entities;</PRE> in your source code. <DT><A NAME="item_NON_ENT">NON_ENT</A> <DD> Like <CODE>"ALL"</CODE>, except that ampersands (&) are not escaped. This allows you to use &-entities in your text strings, while having everything else safely escaped: <PRE> output $HTML "If A is an acute angle, then A > 90°";</PRE> </DL> Returns the previously-installed function, in the manner of <A HREF="../../../lib/Pod/perlfunc.html#item_select"><CODE>select()</CODE></A>. No arguments just returns the currently-installed function. <DT><A NAME="item_auto_format_ONOFF">auto_format ONOFF</A> <DD> Instance method. Set the auto-formatting characteristics for this HTML stream. Currently, all you can do is supply a single defined boolean argument, which turns auto-formatting ON (1) or OFF (0). The self object is returned. Please use no other values; they are reserved for future use. <DT><A NAME="item_comment">comment COMMENT</A> <DD> Instance method. Output an HTML comment. As of 1.29, a newline is automatically appended. <DT><A NAME="item_ent">ent ENTITY</A> <DD> Instance method. Output an HTML entity. For example, here's how you'd output a non-breaking space: <PRE> $html->ent('nbsp');</PRE> You may abbreviate this method name as <CODE>e</CODE>: <PRE> $html->e('nbsp');</PRE> Warning: this function assumes that the entity argument is legal. <DT><A NAME="item_io">io</A> <DD> Return the underlying output handle for this HTML stream. All you can depend upon is that it is some kind of object which responds to a <A HREF="../../../lib/Pod/perlfunc.html#item_print"><CODE>print()</CODE></A> message: <PRE> $HTML->io->print("This is not auto-escaped or nuthin!");</PRE> <DT><A NAME="item_nl_%5BCOUNT%5D">nl [COUNT]</A> <DD> Instance method. Output COUNT newlines. If undefined, COUNT defaults to 1. <DT><A NAME="item_tag_TAGNAME_%5B%2C_PARAM%3D%3EVALUE%2C_%2E%2E%2E%5">tag TAGNAME [, PARAM=>VALUE, ...]</A> <DD> Instance method. Output a tag. Returns the self object, to allow method chaining. You can say <CODE>_A</CODE> instead of <CODE>"/A"</CODE>, if you're into barewords. <DT><A NAME="item_text_TEXT%2E%2E%2E">text TEXT...</A> <DD> Instance method. Output some text. You may abbreviate this method name as <CODE>t</CODE>: <PRE> $html->t('Hi there, ', $yournamehere, '!');</PRE> Returns the self object, to allow method chaining. <DT><A NAME="item_text_nbsp_TEXT%2E%2E%2E">text_nbsp TEXT...</A> <DD> Instance method. Output some text, but with all spaces output as non-breaking-space characters: <PRE> $html->t("To list your home directory, type: ") ->text_nbsp("ls -l ~yourname.")</PRE> Returns the self object, to allow method chaining. </DL> <H2><A NAME="strawberry">Strawberry</A></H2> <DL> <DT><A NAME="item_output_ITEM%2C%2E%2E%2E%2CITEM">output ITEM,...,ITEM</A> <DD> Instance method. Go through the items. If an item is an arrayref, treat it like the array argument to <CODE>html_tag()</CODE> and output the result. If an item is a text string, escape the text and output the result. Like this: <PRE> output $HTML [A, HREF=>$url], "Here's my $caption!", [_A];</PRE> </DL> <H2><A NAME="chocolate">Chocolate</A></H2> <DL> <DT><A NAME="item_accept_tag_TAG">accept_tag TAG</A> <DD> Class method. Declares that the tag is to be accepted as valid HTML (if it isn't already). For example, this... <PRE> # Make sure methods MARQUEE and _MARQUEE are compiled on demand: HTML::Stream->accept_tag('MARQUEE');</PRE> ...gives the Chocolate Interface permission to create (via AUTOLOAD) definitions for the MARQUEE and _MARQUEE methods, so you can then say: <PRE> $HTML -> MARQUEE -> t("Hi!") -> _MARQUEE;</PRE> If you want to set the default attribute of the tag as well, you can do so via the <CODE>set_tag()</CODE> method instead; it will effectively do an <CODE>accept_tag()</CODE> as well. <PRE> # Make sure methods MARQUEE and _MARQUEE are compiled on demand, # *and*, set the characteristics of that tag. HTML::Stream->set_tag('MARQUEE', Newlines=>9);</PRE> <DT><A NAME="item_private_tags">private_tags</A> <DD> Instance method. Normally, HTML streams use a reference to a global table of tag information to determine how to do such things as auto-formatting, and modifications made to that table by <CODE>set_tag</CODE> will affect everyone. However, if you want an HTML stream to have a private copy of that table to munge with, just send it this message after creating it. Like this: <PRE> my $HTML = new HTML::Stream \*STDOUT; $HTML->private_tags;</PRE> Then, you can say stuff like: <PRE> $HTML->set_tag('PRE', Newlines=>0); $HTML->set_tag('BLINK', Newlines=>9);</PRE> And it won't affect anyone else's auto-formatting (although they will possibly be able to use the BLINK tag method without a fatal exception <CODE>:-(</CODE> ). Returns the self object. <DT><A NAME="item_set_tag_TAG%2C_%5BTAGINFO%2E%2E%2E%5D">set_tag TAG, [TAGINFO...]</A> <DD> Class/instance method. Accept the given TAG in the Chocolate Interface, and (if TAGINFO is given) alter its characteristics when being output. <UL> <LI> If invoked as a class method, this alters the ``master tag table'', and allows a new tag to be supported via an autoloaded method: <PRE> HTML::Stream->set_tag('MARQUEE', Newlines=>9);</PRE> Once you do this, all HTML streams you open from then on will allow that tag to be output in the chocolate interface. <LI> If invoked as an instance method, this alters the ``tag table'' referenced by that HTML stream, usually for the purpose of affecting things like the auto-formatting on that HTML stream. Warning: by default, an HTML stream just references the ``master tag table'' (this makes <CODE>new()</CODE> more efficient), so by default, the instance method will behave exactly like the class method. <PRE> my $HTML = new HTML::Stream \*STDOUT; $HTML->set_tag('BLINK', Newlines=>0); # changes it for others!</PRE> If you want to diddle with one stream's auto-formatting only, you'll need to give that stream its own private tag table. Like this: <PRE> my $HTML = new HTML::Stream \*STDOUT; $HTML->private_tags; $HTML->set_tag('BLINK', Newlines=>0); # doesn't affect other streams</PRE> Note: this will still force an default entry for BLINK in the master tag table: otherwise, we'd never know that it was legal to AUTOLOAD a BLINK method. However, it will only alter the characteristics of the BLINK tag (like auto-formatting) in the object's tag table. </UL> The TAGINFO, if given, is a set of key=>value pairs with the following possible keys: <DL> <DT><A NAME="item_Newlines">Newlines</A> <DD> Assumed to be a number which encodes how newlines are to be output before/after a tag. The value is the logical OR (or sum) of a set of flags: <PRE> 0x01 newline before <TAG> .<TAG>. .</TAG>. 0x02 newline after <TAG> | | | | 0x04 newline before </TAG> 1 2 4 8 0x08 newline after </TAG></PRE> Hence, to output BLINK environments which are preceded/followed by newlines: <PRE> set_tag HTML::Stream 'BLINK', Newlines=>9;</PRE> </DL> Returns the self object on success. <DT><A NAME="item_tags">tags</A> <DD> Class/instance method. Returns an unsorted list of all tags in the class/instance tag table (see <CODE>set_tag</CODE> for class/instance method differences). </DL> <HR> <H1><A NAME="subclasses">SUBCLASSES</A></H1> <H2><A NAME="html::stream::latin1">HTML::Stream::Latin1</A></H2> A small, public package for outputting Latin-1 markup. Its default auto-escape function is <A HREF="#item_LATIN_1"><CODE>LATIN_1</CODE></A>, which tries to output the mnemonic entity markup (e.g., <CODE>ç</CODE>) for ISO-8859-1 characters. So using HTML::Stream::Latin1 like this: <PRE> use HTML::Stream; </PRE> <PRE> $HTML = new HTML::Stream::Latin1 \*STDOUT; output $HTML "\253A right angle is 90\260, \277No?\273\n";</PRE> Prints this: <PRE> «A right angle is 90°, ¿No?»</PRE> Instead of what HTML::Stream would print, which is this: <PRE> «A right angle is 90°, ¿No?»</PRE> Warning: a lot of Latin-1 HTML markup is not recognized by older browsers (e.g., Netscape 2.0). Consider using HTML::Stream; it will output the decimal entities which currently seem to be more ``portable''. Note: using this class ``requires'' that you have HTML::Entities. <HR> <H1><A NAME="performance">PERFORMANCE</A></H1> Slower than I'd like. Both the <CODE>output()</CODE> method and the various ``tag'' methods seem to run about 5 times slower than the old just-hardcode-the-darn stuff approach. That is, in general, this: <PRE> ### Approach #1... tag $HTML 'A', HREF=>"$href"; tag $HTML 'IMG', SRC=>"logo.gif", ALT=>"LOGO"; text $HTML $caption; tag $HTML '_A'; text $HTML $a_lot_of_text;</PRE> And this: <PRE> ### Approach #2... output $HTML [A, HREF=>"$href"], [IMG, SRC=>"logo.gif", ALT=>"LOGO"], $caption, [_A]; output $HTML $a_lot_of_text;</PRE> And this: <PRE> ### Approach #3... $HTML -> A(HREF=>"$href") -> IMG(SRC=>"logo.gif", ALT=>"LOGO") -> t($caption) -> _A -> t($a_lot_of_text);</PRE> Each run about 5x slower than this: <PRE> ### Approach #4... print '<A HREF="', html_escape($href), '>', '<IMG SRC="logo.gif" ALT="LOGO">', html_escape($caption), '</A>'; print html_escape($a_lot_of_text);</PRE> Of course, I'd much rather use any of first three (especially #3) if I had to get something done right in a hurry. Or did you not notice the typo in approach #4? <CODE>;-)</CODE> (BTW, thanks to Benchmark:: for allowing me to... er... benchmark stuff.) <HR> <H1><A NAME="why in the world did i write this">WHY IN THE WORLD DID I WRITE THIS?</A></H1> I was just mucking about with different ways of generating large HTML documents, seeing which ways I liked the most/least. <HR> <H1><A NAME="change log">CHANGE LOG</A></H1> <DL> <DT><A NAME="item_Version_1%2E45">Version 1.45</A> <DD> Cleanup for Perl 5.005: removed duplicate typeglob assignments. <DT><A NAME="item_Version_1%2E44">Version 1.44</A> <DD> Win95 install (5.004) now works. Added SYNOPSIS to POD. <DT><A NAME="item_Version_1%2E41">Version 1.41</A> <DD> Removed $& for efficiency. Thanks, Andreas! Added support for OPTION, and default now puts newlines after SELECT and /SELECT. Also altered ``TELEM'' syntax to put newline after end-tags of list element tags (like /OPTION, /LI, etc.). In theory, this change could produce undesireable results for folks who embed lists inside of PRE environments... however, that kind of stuff was done in the days before TABLEs; also, you can always turn it off if you really need to. Thanks to John D Groenveld for these patches. Added text_nbsp(). Thanks to John D Groenveld for the patch. This method may also be invoked as <CODE>nbsp_text()</CODE> as in the original patch, but that's sort of a private tip-of-the-hat to the patch author, and the synonym may go away in the future. <DT><A NAME="item_Version_1%2E37">Version 1.37</A> <DD> No real change; just trying to make CPAN.pm happier. <DT><A NAME="item_Version_1%2E32">Version 1.32</A> <DD> NEW TOOL for generating Perl code which uses HTML::Stream! Check your toolkit for html2perlstream. Added built-in support for escaping 8-bit characters. Added <A HREF="#item_LATIN_1"><CODE>LATIN_1</CODE></A> auto-escape, which uses HTML::Entities to generate mnemonic entities. This is now the default method for HTML::Stream::Latin1. Added <CODE>auto_format(),</CODE> so you can now turn auto-formatting off/on. Added <A HREF="#item_private_tags"><CODE>private_tags()</CODE></A>, so it is now possible for HTML streams to each have their own ``private'' copy of the %Tags table, for use by <CODE>set_tag()</CODE>. Added <CODE>set_tag()</CODE>. The tags tables may now be modified dynamically so as to change how formatting is done on-the-fly. This will hopefully not compromise the efficiency of the chocolate interface (until now, the formatting was compiled into the method itself), and will add greater flexibility for more-complex programs. Added POD documentation for all subroutines in the public interface. <DT><A NAME="item_Version_1%2E29">Version 1.29</A> <DD> Added terminating newline to comment(). Thanks to John D Groenveld for the suggestion and the patch. <DT><A NAME="item_Version_1%2E27">Version 1.27</A> <DD> Added built-in HTML::Stream::Latin1, which does a very simple encoding of all characters above ASCII 127. Fixed bug in accept_tag(), where 'my' variable was shadowing argument. Thanks to John D Groenveld for the bug report and the patch. <DT><A NAME="item_Version_1%2E26">Version 1.26</A> <DD> Start of history. </DL> <HR> <H1><A NAME="version">VERSION</A></H1> $Revision: 1.45 $ <HR> <H1><A NAME="acknowledgements">ACKNOWLEDGEMENTS</A></H1> Warmest thanks to... <PRE> John Buckman For suggesting that I write an "html2perlstream", and inspiring me to look at supporting Latin-1. Tony Cebzanov For suggesting that I write an "html2perlstream" John D Groenveld Bug reports, patches, and suggestions B. K. Oxley (binkley) For suggesting the support of "writing to strings" which became the "printable" interface.</PRE> <HR> <H1><A NAME="author">AUTHOR</A></H1> Eryq, <A HREF="mailto:eryq@zeegee.com">eryq@zeegee.com</A>. President, Zero G Inc. (<A HREF="http://www.zeegee.com">http://www.zeegee.com</A>). Enjoy. <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> HTML::Stream - HTML output stream class, and some markup utilities </TD></TR> </TABLE> </BODY> </HTML>