It might only come up in the context of my work, but we do a lot of data
collection, and so when using the GUI all of the variables we create as
destined to be part a of specific modelform. As such, we way want to end up
with two forms (eg. Baseline, Purchase History) each of which will be
If you could open source it I would appreciate it.
> Do you have a way of setting which fields will be associated with which of
> the models? I am moving onto this aspect next and was thinking of maybe
> doing draggable divs in a list to make it more interactive.
I don't understand this. Could
Nothing is up yet - we have just been using internally where I work. It
came up because we were getting too much work and couldn't find the
programmers. A model (and other things) GUI really helped with getting
other staff to be able to effectively contribute to app development, and
left us to
with attachment.
On Sunday, September 9, 2012 8:46:10 AM UTC-6, jondykeman wrote:
>
> Also, I saw on your github that you are looking for choices support.
>
> Just to give my insight I have implemented the attached for adding choices.
>
> It is ajax via a modal that pre-populates existing
Also, I saw on your github that you are looking for choices support.
Just to give my insight I have implemented the attached for adding choices.
It is ajax via a modal that pre-populates existing options and allows for
creation and deletion of options for that field on the fly.
JD
On
Timothy - I am implementing something similar (Model GUI.png attached) that
is within a larger structure that not only generates models.py, but
registers them to the admin, builds the modelforms, and generates JS logic
etc.
Rather than such a thing being useful for developers I have found it
Kurtis: That looks very interesting; just finished reading it.
I wouldn't recommend this for Timothy though; it looks like something
which will require a large team to develop.
Maybe submit it as a project proposal to Canonical?
Or post on Django-Dev [and here] to see if you can get a large +
Thank you for the feedback.
I implemented the simple_mode suggestion. I'll use it personally so I
don't have to click two checkboxes.
I have simple ungrouped choices almost implemented. Unfortunately I'm
getting weird undefined errors in my javascript. Most other field
options are enabled now.
You could take it a few steps farther and reproduce some work done by a
doctor(now) I used to go to school with.
http://knoesis.wright.edu/research/srl/projects/mobicloud/
On Sat, Sep 8, 2012 at 2:50 PM, Javier Guerra Giraldez
wrote:
> On Fri, Sep 7, 2012 at 9:42 PM, Timothy
On Fri, Sep 7, 2012 at 9:42 PM, Timothy Clemans
wrote:
> I've developed a GUI for creating models, see
> https://github.com/timothyclemans/django-admin-models-editor
>
> Would this be helpful for developers? Would it be useful for you? Should I
> keep developing it?
This could be very useful for generating dynamic forms. You create the
model and then just have some views that generate and process a ModelForm
that uses the created model with this interface.
Also having a "simple" mode for the client who will actually use this would
be helpful. For example,
On Saturday, September 8, 2012 8:16:18 AM UTC+5:30, Alec Taylor wrote:
>
> Suggestion: go visual
>
> E.g.: fork this - http://gaesql.appspot.com/
>
This already seems to do that:
http://code.google.com/p/uml-to-django/
I have not tried it: I am put off by the way it splits models.py and
Suggestion: go visual
E.g.: fork this - http://gaesql.appspot.com/
On Sat, Sep 8, 2012 at 12:42 PM, Timothy Clemans
wrote:
> I've developed a GUI for creating models, see
> https://github.com/timothyclemans/django-admin-models-editor
>
> Would this be helpful for
13 matches
Mail list logo