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<javascript:>> > 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 <javascript:>> > > wrote: > >> > >> On Fri, Sep 7, 2012 at 9:42 PM, Timothy Clemans > >> <timothy...@gmail.com <javascript:>> 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<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 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/-/M6DSZabzv9QJ. 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.
<<attachment: Mezzanine Example.png>>
<<attachment: Model GUI.png>>
