[Catalyst-commits] r12131 - trunk/examples/CatalystAdvent/root/2009/pen

alexn_org at dev.catalyst.perl.org alexn_org at dev.catalyst.perl.org
Tue Dec 1 21:06:14 GMT 2009


Author: alexn_org
Date: 2009-12-01 21:06:14 +0000 (Tue, 01 Dec 2009)
New Revision: 12131

Modified:
   trunk/examples/CatalystAdvent/root/2009/pen/formhandler.pod
Log:

added reasons for using FormHandler instead of FormFu

Modified: trunk/examples/CatalystAdvent/root/2009/pen/formhandler.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2009/pen/formhandler.pod	2009-12-01 21:05:33 UTC (rev 12130)
+++ trunk/examples/CatalystAdvent/root/2009/pen/formhandler.pod	2009-12-01 21:06:14 UTC (rev 12131)
@@ -9,6 +9,41 @@
 I like HTML::FormHandler because of its simplicity, extendability
 and Moose integration provided.
 
+I prefer it over FormFu mostly because of subjective reasons, but most
+importantly ...
+
+=over 
+
+=item *
+
+The validation logic is done with validators written in Perl, and you
+can use already defined Moose constraints
+
+=item *
+
+I don't like it in FormFu that the standard way of defining a form is
+within an YAML file ... I know that many people use that form
+definition for the response rendering but validation rules are
+contract of the request and should be decoupled from the response
+
+=item *
+
+I don't like it that the standard way to initialize a FormFu object is
+done with a Catalyst plugin ... many times I prefer to initialize
+different forms in the same controller action.
+
+=item *
+
+HTML::FormHandler gives me the confidence that it's flexible enough
+for any challenge.
+
+=item *
+
+In HTML::FormHandler you can place all the saving logic, taking it out
+of the controller.
+
+=back
+
 This tutorial includes a fairly simple example ...
 
 =over




More information about the Catalyst-commits mailing list