Short description
Although WCAG 2 does not prohibit the use of layout tables, CSS-based layouts are recommended in order to retain the defined semantic meaning of the HTML table elements and to conform to the coding practice of separating presentation from content (see, http://www.w3.org/TR/WCAG-TECHS/F46.html). However, Moin uses heavily layout tables for forms. But there are nice CSS frameworks ready for the creation of forms with CSS only, see e.g. http://code.google.com/p/formy-css-framework/.
The idea is to implement one of these frameworks in Moin and extend moinmoin.widget.dialog to a real dialog class which helps bulding forms with CSS only. So maybe the idea of looking at a form as a table is a good way to interact with the moinmoin.widget.dialog class, i.e. to define / step by step built a form through repeatedly calling some moinmoin.widget.dialog class function. However, the new moinmoin.widget.dialog class turns this with the help of the css framework in html which use CSS for positioning only and not tables.
For a start, it is maybe enough to concentrate on simple forms only (I think most forms in Moin are quite simple) and to leave out such complex stuff like the xapian-extended-search-form.
Discussion
moin-2.0 is based on !Jinja2 see ToDo MoinMoin2.0 and yeah small defined tasks as workpackage is a good idea. Currently we don't know if we will be invited for ghop but anyway it is a good idea to prepare small tasks.
Sorry, don't know much about !Jinja2. Can you elaborate a bit more on how templates could help to avoid layout-tables for froms in a generic way? -- OliverSiemoneit 2009-09-09 13:45:47
Forms in moin-2.0 are done by flatland and jinja2.