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 the finer details and more custom features being requested.
It is super alpha and we just needed it working before working well - there is no editing because it was just as fast to add the value/label you were going to change to and click the delete on the pre-existing one. That being said - now planning on converting to formsets with ajax, which will allow the editing of all at once. 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. Currently the app supports: BigIntegerField, PositiveIntegerField, DecimalField, BooleanField, RadioButton, CharField, TextField, DateField, TimeField, DateTimeField, EmailField. We use javascript to control the display of appropriate additional information fields (eg. max_length) when creating variables in the form, which is backed up by a bunch of custom validation in the modelform. JD On Sunday, September 9, 2012 5:16:54 PM UTC-6, Timothy Clemans wrote: > > Jondy: > > Is your code online? > > Attached is screenshot of adding choices. After you add a choice in > your implementation, can you change its value and label? > Do/will you support most of the field and model options? > > On Sun, Sep 9, 2012 at 7:46 AM, jondykeman <jondy...@gmail.com<javascript:>> > wrote: > > ....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 options and allows > for > >> creation and deletion of options for that field on the fly. > >> > >> JD > >> > >> On Sunday, September 9, 2012 8:37:48 AM UTC-6, jondykeman wrote: > >>> > >>> 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 > >>> great to be able to use non-programmers to basically build the first > 70% of > >>> apps I work on. > >>> > >>> Also, fyi - Mezzanine comes with something similar (also attached), > but > >>> more dynamic in the sense that the models are never actually written > out - > >>> they are stored in a table, the forms are rendered off the table, and > the > >>> information is saved FK to the field in a separate table. > >>> > >>> Let me know if you want to discuss what we each have done a little > more > >>> to see if we can learn anything from each other's experiences. > >>> > >>> JD > >>> > >>> > >>> On Saturday, September 8, 2012 8:31:00 PM UTC-6, Alec Taylor wrote: > >>>> > >>>> 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 + > >>>> skilled enough team to build such a system. > >>>> > >>>> On Sun, Sep 9, 2012 at 6:41 AM, Kurtis Mullins <kurtis....@gmail.com> > > >>>> wrote: > >>>> > 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 > >>>> > <jav...@guerrag.com> > >>>> > wrote: > >>>> >> > >>>> >> On Fri, Sep 7, 2012 at 9:42 PM, Timothy Clemans > >>>> >> <timothy...@gmail.com> 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? What features would you like to see added? > >>>> >> > >>>> >> personally, i much prefer the reverse approach: i write the > models, > >>>> >> and a tool (ie. django-extensions) generates a graphical > >>>> >> representation. > >>>> >> > >>>> >> pros: > >>>> >> - the final models are exactly what i want them to be. even if > the > >>>> >> graphical tool doesn't support some obscure Django feature, i can > >>>> >> still use it; it's just not shown graphically. > >>>> >> > >>>> >> - i don't have to learn a different (graphical) language > >>>> >> > >>>> >> - i keep fluent in the real Django language, so i don't have to > >>>> >> relearn it when for any reason i don't have to use that tool. > >>>> >> > >>>> >> cons: > >>>> >> - less sexy than not writing code > >>>> >> > >>>> >> -- > >>>> >> Javier > >>>> >> > >>>> >> -- > >>>> >> You received this message because you are subscribed to the Google > >>>> >> Groups > >>>> >> "Django users" group. > >>>> >> To post to this group, send email to django...@googlegroups.com. > >>>> >> To unsubscribe from this group, send email to > >>>> >> django-users...@googlegroups.com. > >>>> >> For more options, visit this group at > >>>> >> http://groups.google.com/group/django-users?hl=en. > >>>> >> > >>>> > > >>>> > -- > >>>> > You received this message because you are subscribed to the Google > >>>> > Groups > >>>> > "Django users" group. > >>>> > To post to this group, send email to django...@googlegroups.com. > >>>> > To unsubscribe from this group, send email to > >>>> > django-users...@googlegroups.com. > >>>> > For more options, visit this group at > >>>> > http://groups.google.com/group/django-users?hl=en. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Django users" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/django-users/-/B_asYx8DCAUJ. > > > > To post to this group, send email to > > django...@googlegroups.com<javascript:>. > > > To unsubscribe from this group, send email to > > django-users...@googlegroups.com <javascript:>. > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/hBsYJPvZnrMJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
