Hmm, but the another solution could be to create complete 'form' environment e.g. like a Django has http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#topics-forms-modelforms . Using this approach, we can obtain potentialy deeper solution, that will cover other aspects of the problem. Such Form object could be able to render himself to HTML, can make aditional validation like 'onValidate method' and many other things(e.g. contribution can then extends it to form wizards ...) We can find a huge inspiration in Django for example. If you imagine the model with 20-30 fields, it can be a bit messy to use annotations for diffrerent presentation cases in one model file. Separate Form objects would be much more elegant and we can separate form logic from model.
(from JAVA world I had a very positive experience with Click Framework and their form implementation http://click.sourceforge.net/docs/click-api/net/sf/click/control/Form.html)
But I guess, you guys will have many nice ideas.
David
Hmm, but the another solution could be to create complete 'form' environment e.g. like a Django has http:// docs.djangoproj ect.com/ en/dev/ topics/ forms/modelform s/#topics- forms-modelform s . Using this approach, we can obtain potentialy deeper solution, that will cover other aspects of the problem. Such Form object could be able to render himself to HTML, can make aditional validation like 'onValidate method' and many other things(e.g. contribution can then extends it to form wizards ...) We can find a huge inspiration in Django for example. If you imagine the model with 20-30 fields, it can be a bit messy to use annotations for diffrerent presentation cases in one model file. Separate Form objects would be much more elegant and we can separate form logic from model. click.sourcefor ge.net/ docs/click- api/net/ sf/click/ control/ Form.html)
(from JAVA world I had a very positive experience with Click Framework and their form implementation http://
But I guess, you guys will have many nice ideas.
David