[development] Awesome form building UI

[Gary (Lists)]

"Nedjo Rogers" wrote:

> The approach would be similar to what is done on formassembly, except that we
> would use an XML encoding of our $forms arrays: * serialize our $forms arrays
> as XML
> * write XSL to render the form XML into wForms format * build forms using
> wForms, updating XML dataset, which is then unserialized into a $form array.

I personally refuse any more "XYZ format"  (wForms, etc.) of anything.

There are __standards based__ forms formats for the web, and those are what
__we all__ should be using.

The W3C is what we need to honor, collectively, to have any traction on the
web and to stop this endless cycle of re-naming everything...twice.

Xforms is the W3C next-gen standard, and that is what we all need to
struggle toward.


> 2006-03-14: XForms 1.0 Second Edition Is a W3C Recommendation. The World Wide
> Web Consortium today released XForms 1.0 Second Edition as a W3C
> Recommendation. The new generation of Web forms, XForms separate presentation
> and content, minimize round-trips to the server, offer device independence,
> and reduce the need for scripting. This second edition adds clarifications and
> corrects errors as reported in the first edition errata. Second edition
> publications include the following documents.
> 
>   * XForms 1.0 Second Edition
>   * XForms for HTML Authors: Part 2
>   * XForms Quick Reference
>   * XHTML to XForms Converter (XSLT)
>   * Revised XForms Test Suite

<http://www.w3.org/MarkUp/Forms/>
--
Gary


And Nedjo, while I have your eyes, I've been wondering about this, which
involves you...


You wrote this about two bug fixes for the Projects module. Note the date.

> #7 submitted by nedjo on October 3, 2005 - 15:48
> Status:    patch (code needs review)    » fixed
> 
> Both patches applied.


Yet the latest downloadable version [dated this month, 2006] of that
Projects module does _not_ have these patches applied.  That was a real
waste of a whole work day.

Is there anything you can do about that?