Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Date: Thu, 18 Apr 2013 07:53:54 -0500 (CDT)
From: Wayne Werner <wayne@waynewerner.com>
To: andrea crotti <andrea.crotti.0@gmail.com>
Subject: Re: dynamic forms generation
In-Reply-To: <CAF_E5Ja93v_6-AcTc=T2EVOUPufYk12zmiv24QRTPKFetfAfcg@mail.gmail.com>
References: <CAF_E5Ja93v_6-AcTc=T2EVOUPufYk12zmiv24QRTPKFetfAfcg@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-47601280-1366289634=:3322"
Cc: python-list <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.765.1366289645.3114.python-list@python.org>
Lines: 73
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:43822

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-47601280-1366289634=:3322
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT

On Tue, 16 Apr 2013, andrea crotti wrote:

> This is not really scalable, and we want to make the whole thing more
> generic.
> 
> So ideally there could be a DSL (YAML or something else) that we could
> define to then generate the forms, but the problem is that I'm quite
> sure that this DSL would soon become too complex and inadeguate, so I'm
> not sure if it's worth since noone should write forms by hands anyway.
> 
> Between the things that we should be able to do there are:
> - dependent fields
> - validation (both server and client side, better if client-side
>   auto-generated)
> - following DRY as much as possible
> 
> Any suggestions of possible designs or things I can look at?

I would highly recommend a look at Flask, and Flask-WTF in particular. 
It's fairly easy to write forms, and with only a bit of setup you can end 
out with some fairly generic systems.

I don't think that by default it does any client-side validation 
generation, but as the HTML for the forms are completely generated, 
extending the form and adding validation logic to the output wouldn't be 
too difficult.

Example:

# form.py

from flask.ext.wtf import Form, TextField, Required

class MyBasicForm(Form):
     some_text = TextField("Put some text here:", validators=[Required()])


# View/HTML

{% extends 'base.html' %}
{{ form.some_text.label() }}{{ form.some_text(size=40) }}


# Server code

@app.route("/basic_form", methods=['GET', 'POST'])
def basic():
     form = MyBasicForm()
     if form.validate_on_submit():
         do_the_needful(form.some_text.data)
 	return redirect(url_for('main'))

     return render_template('basic_form.html', form=form)



Obviously a really basic example. Check out Flask here:
http://flask.pocoo.org/

And Flask WTF here:
http://pythonhosted.org/Flask-WTF/


HTH,
Wayne
--8323329-47601280-1366289634=:3322--