| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Pkgsrc changes:
o Add a BUILD_DEPENDS for the tests
Upstream changes:
0.601 (01.09.2009) - John Siracusa <siracusa@gmail.com>
* Fixed an uninitialized value warning in Rose::HTML::Text.
|
|
|
|
Pkgsrc changes:
o Canonicalize HOMEPAGE
o Adjust dependencies according to new requirements
Upstream changes:
0.600 (12.13.2008) - John Siracusa <siracusa@gmail.com>
* Added localization support.
* Added private library support.
* Rose::HTML::Form::Field::PopUpMenu's internal_value() is now
unconditionally singular, and undef when no items are selected.
* Fixed a bug in Rose::HTML::Image that made detection of image
sizes dependent on method call order. (Reported by Sean Allen)
* Added mod_perl 2.x support to Rose::HTML::Image. (Reported by
Sean Allen)
0.555 (10.22.2008) - John Siracusa <siracusa@gmail.com>
* Fixed a memory leak in group fields (RT #38837)
* Corrected documentation and implementation of init_with_objects().
|
|
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
|
|
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.
|
