Hello community,
here is the log from the commit of package perl-HTML-FormHandler for
openSUSE:Factory
checked in at Wed Jul 27 15:58:50 CEST 2011.
--------
New Changes file:
--- /dev/null 2010-08-26 16:28:41.000000000 +0200
+++
/mounts/work_src_done/STABLE/perl-HTML-FormHandler/perl-HTML-FormHandler.changes
2011-04-22 09:29:20.000000000 +0200
@@ -0,0 +1,42 @@
+-------------------------------------------------------------------
+Fri Apr 22 07:26:04 UTC 2011 - [email protected]
+
+- updated to 0.33002
+ Accidentally left off compatibility for 'required_message' attribute
+ messages => { required => '...' } is new style and worked
+
+ Remove unnecessary with of HFH::Validate::Actions
+
+ bug - empty_select check defined
+ Add button field, widget, template
+ Check html attributes for definedness not truth
+ Add ability to set field inactive on new & process
+ in addition to setting active
+ Move 'no_render_label' into Field
+ Use form's language_handle in fields
+ Improve PrimaryKey doc
+ Return empty hashref from $form->value instead of undef
+ Merge experimental Wizard into master
+ Render disabled select options
+ Repeatable contains rendering incorrectly, skipping empty elements
+ Add rendering of form_errors to widgets and Render::Simple
+ *** If you were using form_errors (there are none by default)
+ and were using HFH rendering, check for compatibility
+ Allow specifying full class for widget with '+'
+ Document removing wrapper div from Simple wrapper
+ Re-do how field messages are stored and accessed. Use messages => {...}
+ instead of various _message attributes
+ Add utilities in util to pull out class messages and check I18N
+ Update I18N messages files (those that were provided by translators)
+ Change render_filter Coderef setting because of leak;
+ *** Possible incompatibility: if you have a form render_filter,
+ change to function instead of method
+ Change _localize to a Coderef to allow easier changing.
+ *** If you have a custom _localize method, check for compatibility
+
+-------------------------------------------------------------------
+Wed Jan 19 13:38:50 UTC 2011 - [email protected]
+
+- initial package 0.32005
+ * created by cpanspec 1.78.03
+
calling whatdependson for head-i586
New:
----
HTML-FormHandler-0.33002.tar.gz
perl-HTML-FormHandler.changes
perl-HTML-FormHandler.spec
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ perl-HTML-FormHandler.spec ++++++
#
# spec file for package perl-HTML-FormHandler
#
# Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
Name: perl-HTML-FormHandler
Version: 0.33002
Release: 1
License: GPL+ or Artistic
%define cpan_name HTML-FormHandler
Summary: HTML forms using Moose
Url: http://search.cpan.org/dist/HTML-FormHandler/
Group: Development/Libraries/Perl
Source:
http://www.cpan.org/authors/id/G/GS/GSHANK/%{cpan_name}-%{version}.tar.gz
BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
BuildRequires: perl
BuildRequires: perl-macros
BuildRequires: perl(aliased)
BuildRequires: perl(Carp)
BuildRequires: perl(DateTime)
BuildRequires: perl(DateTime::Format::Strptime)
BuildRequires: perl(Email::Valid)
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(File::ShareDir)
BuildRequires: perl(File::ShareDir::Install) >= 0.03
BuildRequires: perl(File::Spec)
BuildRequires: perl(Locale::Maketext) >= 1.09
BuildRequires: perl(Moose) >= 0.90
BuildRequires: perl(MooseX::Getopt) >= 0.16
BuildRequires: perl(MooseX::Types) >= 0.20
BuildRequires: perl(MooseX::Types::Common)
BuildRequires: perl(namespace::autoclean) >= 0.09
BuildRequires: perl(Test::Differences)
BuildRequires: perl(Test::Exception)
BuildRequires: perl(Test::More) >= 0.94
BuildRequires: perl(Try::Tiny)
Requires: perl(aliased)
Requires: perl(Carp)
Requires: perl(DateTime)
Requires: perl(DateTime::Format::Strptime)
Requires: perl(Email::Valid)
Requires: perl(File::ShareDir)
Requires: perl(File::Spec)
Requires: perl(Locale::Maketext) >= 1.09
Requires: perl(Moose) >= 0.90
Requires: perl(MooseX::Getopt) >= 0.16
Requires: perl(MooseX::Types) >= 0.20
Requires: perl(MooseX::Types::Common)
Requires: perl(namespace::autoclean) >= 0.09
Requires: perl(Try::Tiny)
%{perl_requires}
%description
*** Although documentation in this file provides some overview, it is
mainly intended for API documentation. See the
HTML::FormHandler::Manual::Intro manpage for a more detailed introduction.
HTML::FormHandler maintains a clean separation between form construction
and form rendering. It allows you to define your forms and fields in a
number of flexible ways. Although it provides renderers for HTML, you can
define custom renderers for any kind of presentation.
HTML::FormHandler allows you to define form fields and validators. It can
be used for both database and non-database forms, and will automatically
update or create rows in a database. It can be used to process structured
data that doesn't come from an HTML form.
One of its goals is to keep the controller/application program interface as
simple as possible, and to minimize the duplication of code. In most cases,
interfacing your controller to your form is only a few lines of code.
With FormHandler you'll never spend hours trying to figure out how to make
a simple HTML change that would take one minute by hand. Because you CAN do
it by hand. Or you can automate HTML generation as much as you want, with
template widgets or pure Perl rendering classes, and stay completely in
control of what, where, and how much is done automatically. You can define
custom renderers and display your rendered forms however you want.
You can split the pieces of your forms up into logical parts and compose
complete forms from FormHandler classes, roles, fields, collections of
validations, transformations and Moose type constraints. You can write
custom methods to process forms, add any attribute you like, use Moose
method modifiers. FormHandler forms are Perl classes, so there's a lot of
flexibility in what you can do.
HTML::FormHandler provides rendering through roles which are applied to
form and field classes (although there's no reason you couldn't write a
renderer as an external object either). There are currently two flavors:
all-in-one solutions like the HTML::FormHandler::Render::Simple manpage and
the HTML::FormHandler::Render::Table manpage that contain methods for
rendering field widget classes, and the the HTML::FormHandler::Widget
manpage roles, which are more atomic roles which are automatically applied
to fields and form if a 'render' method does not already exist. See the
HTML::FormHandler::Manual::Rendering manpage for more details. (And you can
easily use hand-build forms - FormHandler doesn't care.)
The typical application for FormHandler would be in a Catalyst,
DBIx::Class, Template Toolkit web application, but use is not limited to
that. FormHandler can be used in any Perl application.
More Formhandler documentation and a tutorial can be found in the manual at
the HTML::FormHandler::Manual manpage.
%prep
%setup -q -n %{cpan_name}-%{version}
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
%{__make} %{?_smp_mflags}
%check
%{__make} test
%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist
%clean
%{__rm} -rf %{buildroot}
%files -f %{name}.files
%defattr(-,root,root,755)
%doc Changes LICENSE README TODO util xt
%changelog
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Remember to have fun...
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
