Apache-Wyrd

 view release on metacpan or  search on metacpan

BUGS  view on Meta::CPAN

List of known problems:

-   Apache2 incompatible.  An Apache2::Wyrd framework is in the works, though
    it may be released as a context-sensitive wrapper class.

-   Concurrent access modes (CDB_<FOO>)of the BerkeleyDB module have
    not been widely tested, and the BerkeleyDB Index is scheduled for
    demolition before the 1.0 release.

List of known problems which will not be fixed, and why:

-   Until there's a good reason to do so, Apache::Wyrd will continue to
    use the "old-style" file semantics, since they are slightly more

BUGS  view on Meta::CPAN

    namespace:  Guilty as charged.

-   It should work more like PHP or Mason: No need to duplicate effort. If
    PHP or Mason works for you, use it!

-   The _self_parse method which is integral to the Wyrd object is
    functionally incompatible with the idea of a "non-parsed-header"
    document:  It makes more sense to use something else hand-coded if you
    need to do that.

-   The labor cost of converting the framework to D.C.'s spiffy new "Best
    Practices" at this point outweigh the benefits.  Even the Apache2 port
    will not need sufficient rewriting.  Current style is consistent where
    required, and many of the more important best practices are already used.

Wyrd.pm  view on Meta::CPAN

modules that allow the rapid object-oriented development of web sites in
Apache's mod_perl environment (LAMP).  This collection includes a very
flexible, HTML-friendly method of defining dynamic items on a web page,
and interfacing directly to perl objects with them.  It comes with many
pre-built objects to support a web site such as an authentication
module, an reverse-lookup database, granular debugging, and smart
forms/inputs and their interfaces to a DBI-compliant SQL application.

The collection is not meant to be a drop-in replacement for PHP,
ColdFusion, or other server-side parsed content creation systems, but to
provide a more flexible framework for organic custom perl development
for an experienced perl programmer who favors an object-oriented
approach.  It has been designed to simplify the transition from static
to dynamic web content by allowing the design of objects that can be
operated by a non-perl programmer through the modification of the HTML
page on which the content is to be delivered.

The Apache::Wyrd module itself is an abstract class used to create
HTML-embeddable perl objects (I<Wyrds>).  The embedded objects are
interpreted from HTML files by an instance of the abstract class
C<Apache::Wyrd::Handler>. Most Wyrds also require an instance of an

Wyrd/Interfaces/GetUser.pm  view on Meta::CPAN

	}
	$user_info = $self->null_user_spec($user_object);
	eval('$user=' . $user_object . '->new($user_info)');
	return $user;
}

=pod

=item (hashref) C<null_user_spec> (scalar)

Because the Apache::Wyrd:Services::Auth framework requires that there must
be a user object defined even when no user has logged in, this is a "hook"
method for providing minimum initialization of the non-user user object.  It
is passed the class name of the type of user object being created.  Return
value is a hashref, defaulting to the empty hash. When there is no login,
this method's return value will be passed directly to the C<new> method of
the user object as if it were a new login.

=cut

sub null_user_spec {

Wyrd/Site/SearchResults.pm  view on Meta::CPAN

To allow the individual items of the "search results" block to be related to
each other.  Additionally, if a previous search result is given in the CGI
variable "previous" and the CGI variable "within" is a non-null value (as would
be returned by a hidden INPUT tag named "previous" and a checkbox named "within",
The searcstring will be limited to the previous results.

Additionally, the CGI variable "max" is used to limit the search results to
"max" number of items or less, and the "next" and "beginning" CGI variables are
used to define a window of "max" number of of search results within a search
set, which is to say that as the frame moves to the window defined by "next",
the C<Apache::Wyrd::Intefaces::Setter> elements will set C<$:next> in the list
template to the current value of the CGI variable "next" + the value of "max".
This allows the webmaster to easily construct a moving-window search result.

=head2 HTML ATTRIBUTES

=over

=item decimals