[cvs] [Wiki] changed: Project/HordeForm

[Chuck Hagenbuch]

chuck  Thu, 03 Apr 2008 18:30:51 -0400

Modified page: http://wiki.horde.org/Project/HordeForm
New Revision:  17.4
Change log:  add Rdo integration/autogeneration

@@ -3,9 +3,18 @@
 This page is a proposal for the implementation of new package to replace
Horde_Form_Type:: and Horde_Form_Variable::.

 I'm refactoring this page into topics.  I had a major wiki breakthrough
when doing this for work (as I receive e-mail, enter meeting notes, etc., I
now factor into topics which could be different pages or different headings
on a page).  A really good overview emerges fairly quickly and it works
extremely well with something like a project's needs analysis.  So let's
call it a pattern. -- JasonFelice

-++ Proposed Requirements
+++ Proposed Paths/Requirements
+
++++ Autogeneration
+
+Extend Rdo (http://cvs.horde.org/framework/Rdo) and Horde_Form to
autogenerate basic CRUD forms (create, read, update, delete) based on the
metadata already available in Rdo.
+
++++ Ajax Functionality
+
+Follow up on the Summer of Code Horde_Form project (currently available in
the incubator - http://cvs.horde.org/incubator/Horde_Form/). Update the code
to use Prototype and
+Scriptaculous for the scripting basis, sync with the current Horde_Form
code, and go from there. The ability to have any form switch between active
and inactive rendered mode - optionally on a field-by-field basis - using
in-place-edit functionality would be very slick.

 +++ Useable Without Horde_Form::

 There are currently still some interdependencies with
Horde_UI_VarRenderer:: and Horde_Form:: which really suck.  When working on
Horde_UI_Table::, I need to render fields in display mode and I have no
form. -- JasonFelice
@@ -40,13 +49,8 @@
         Text/Wiki/Render/DocBook/Wikilink.php
 </code>

 -- ChuckHagenbuch (from e-mail on May 26, 2004)
-
-+++ Ajax Functionality
-
-Follow up on the Summer of Code Horde_Form project (currently available in
the incubator - http://cvs.horde.org/incubator/Horde_Form/). Update the code
to use Prototype and
-Scriptaculous for the scripting basis, sync with the current Horde_Form
code, and go from there. The ability to have any form switch between active
and inactive rendered mode - optionally on a field-by-field basis - using
in-place-edit functionality would be very slick.

 +++ Multiple Output Formats

 In our old framework, we can render a field to plain text, HTML, or !TeX
(since that is how we produce PDFs).