Changes

==== make_html_tag_group( NAME[, PARAMS[, TEXT[, LIST]]] ) ====

==== make_html_tag_group( NAME[, PARAMS[, TEXT[, LIST]]] ) ====

This method is used internally to do the actual construction of html tag groups.  You can call it directly when you want faster code and/or more control over how tags are made.  The first argument, NAME, is a scalar that defines the actual name of the tag we are making (eg: ’br’); it is case-insensitive.  The optional second argument, PARAMS, is a HASH ref containing attribute names and values for the new tag; the names (keys) are case-insensitive.  Any attribute values which are ARRAY refs are flattened, and the number of tags made is determined by the length of the longest one.  The optional third argument, TEXT, is a HASH ref (or scalar) containing the text that goes between the tag pairs; it is not a tag attribute, but if its an ARRAY ref then its length will influence the number of tags that are made as the length of tag attribute arrays do.  The optional fourth argument, LIST, is a boolean/scalar which indicates whether this method returns the new tags in an ARRAY

This method is used internally to do the actual construction of html tag groups.  You can call it directly when you want faster code and/or more control over how tags are made.  The first argument, NAME, is a scalar that defines the actual name of the tag we are making (eg: ’br’); it is case-insensitive.  The optional second argument, PARAMS, is a HASH ref containing attribute names and values for the new tag; the names (keys) are case-insensitive.  Any attribute values which are ARRAY refs are flattened, and the number of tags made is determined by the length of the longest one.  The optional third argument, TEXT, is a HASH ref (or scalar) containing the text that goes between the tag pairs; it is not a tag attribute, but if its an ARRAY ref then its length will influence the number of tags that are made as the length of tag attribute arrays do.  The optional fourth argument, LIST, is a boolean/scalar which indicates whether this method returns the new tags in an ARRAY ref (one tag per element) or as a scalar (tags are concatenated together); a true value forces an ARRAY ref, scalar is the default.  This method knows which HTML tags are normally paired or not, which tag attributes take specified values or not, and acts accordingly.

      ref (one tag per element) or as a scalar (tags are concatenated together); a true value forces an ARRAY ref, scalar is the default.  This method knows which HTML tags are normally paired or not, which tag attributes take specified values or not, and acts accordingly.

 

=== COMPATABILITY WITH OTHER MODULES ===

=== COMPATABILITY WITH OTHER MODULES ===

The methods of this class and their parameters are designed to be compatible with any same-named methods in the popular CGI.pm class.  This class will produce identical or browser-compatible HTML from such methods, and this class can accept all the same argument formats.  Exceptions to this include:

The methods of this class and their parameters are designed to be compatible with any same-named methods in the popular CGI.pm class.  This class will produce identical or browser-compatible HTML from such methods, and this class can accept all the same argument formats.  Exceptions to this include:

* None of our methods are exported and must be called using indirect notation, whereas CGI.pm can export any of it’s methods.

* None of our methods are exported and must be called using indirect notation, whereas CGI.pm can export any of it’s methods.

* start_html() doesn’t support all the same arguments, but those that do have the same names.  However, the effects of the missing arguments can be easily replicated by making the appropriate tags

* start_html() doesn’t support all the same arguments, but those that do have the same names.  However, the effects of the missing arguments can be easily replicated by making the appropriate tags explicitly and handing them in via either the "head" or "body" arguments, where appropriate.  The common arguments are [’title’, ’author’, ’meta’, ’style’, ’head’, ’body’], in that order.

          explicitely and handing them in via either the "head" or "body" arguments, where appropriate.  The common arguments are [’title’, ’author’, ’meta’, ’style’, ’head’, ’body’], in that order.

* Our textarea() method is autoloaded, and doesn’t have the special symantecs that CGI.pm’s textarea() does.  However, any module who subclasses from this one can override textarea() with one that

* Our textarea() method is autoloaded, and doesn’t have the special symantecs that CGI.pm’s textarea() does.  However, any module who subclasses from this one can override textarea() with one that matches CGI.pm’s symantecs.  The "HTML::FormMaker" module does this.

          matches CGI.pm’s symantecs.  The "HTML::FormMaker" module does this.

* Autoloaded methods do not use the presence or absense of arguments to decide whether to make the new tag as a pair or as "start only".

* Autoloaded methods do not use the presence or absense of arguments to decide whether to make the new tag as a pair or as "start only".

* Autoloaded methods that make html tags won’t concatenate their arguments into a single argument under any circumstances, but in some cases the "shortcuts" of CGI.pm will do so.

* Autoloaded methods that make html tags won’t concatenate their arguments into a single argument under any circumstances, but in some cases the "shortcuts" of CGI.pm will do so.

* Currently we don’t html-escape any argument values passed to our tag making functions, whereas CGI.pm sometimes does.  While we expect our caller to do the escaping themselves where necessary,

* Currently we don’t html-escape any argument values passed to our tag making functions, whereas CGI.pm sometimes does.  While we expect our caller to do the escaping themselves where necessary, we may do it later in an update.

          we may do it later in an update.

* We go further to make the generated HTML human-readable by: 1. having each new tag start on a new line; 2. making all tag and attribute names uppercase; 3.  ensuring that about 20 often-used tag

* We go further to make the generated HTML human-readable by: 1. having each new tag start on a new line; 2. making all tag and attribute names uppercase; 3.  ensuring that about 20 often-used tag attributes always appear in the same order (eg: ’type’ is before ’name’ is before ’value’), and before any others.

          attributes always appear in the same order (eg: ’type’ is before ’name’ is before ’value’), and before any others.

=== COPYING ===

=== COPYING ===