I am doing something a little similar, although actually the site is about what you would call 'scale development', so the resulting forms aren't used for data collection. But maybe it's of interest?
I use xml to define a template, composed of elements and groups. The xml is just stored in a text field in a model. On loading the template, the xml is passed to a generic page template, and the xml is processed using some very simple templatetags which wrap ElementTree code- most are just a line or 2. The template is then built through recursive calls to widgets, which are just little fragments of template code. (The NewForms stuff might support this better now) For your application, you could have a simple Scale model, with a field for the xml definition, to give you complete flexibility, then build the forms using the scales, and just save a generic data-point with the scale id and a value. Derek --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
