Well I think since we are using django anyway (and bottle on the API side)
I'm not sure why we would use flask forms for this..
Anyway the main question is probably, is it worth to try to define a DSL or
not?
The problem I see is that we have a lot and very complex requirements,
trying to define
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
We are re-designing a part of our codebase, which should in short be
able to generate forms with custom fields.
We use django for the frontend and bottle for the backend (using CouchDB
as database), and at the moment we simply plug extra fields on normal
django forms.
This is not really
