OK. I have been trying it out. I have to say I like how structured everything comes out. It makes it easy to cross reference what I entered into the "Generator" site and the code it gave me. I now have a working project with some features that I can learn from. It's like having a seasoned Django programmer show me how to do it right.
I already have a better understanding of what is going on and expect this to help me get up to speed with Django very fast. I learn best by example and can now try out various things and get a working set-up each time. After a while I always just rely on memory and write code directly. Not only is it something I can learn from but it does look like a more "comprehensive" startproject / startapp utility. I can see using this to create starting points for various types of projects or applications. If "Generator" gets even more advanced it could turn into a way of stockpiling my own re-usable apps that I could quickly paste together in a web interface, download the project and let the customization begin! Imagine if you could use a "Generator" like concept to set-up Pinax, Satchmo or both into a project, taking only the pieces of each you need. The whole point of those two projects is to allow me to focus on what is unique about my project and rely on them for the boilerplate code. Why not have an application that allows me to pick and choose and create the project all at the same time? Thank you Brice for the great work on this! Appreciatively, Richard On Tue, Feb 9, 2010 at 6:02 PM, Brice Leroy <bbrriic...@gmail.com> wrote: > Thank you Richard. > > I put most of my coding convention inside and try to respect the pep8. > > A lot of work still need to be done. But I expect to reach my goal by > the next 15 days > > Brice > > 2010/2/9 Richard Shebora <sheb...@gmail.com>: >> Actually my first thought was... What a great learning tool! >> >> How many times did I want to do something but could not find a working >> example to pick apart? I would think it would make a great way to >> show proper layout and conventions for newbies (like me). I have been >> programming in python for years but am having some trouble wrapping my >> head around the "django" paradigm. >> >> Thanks, >> Richard >> >> On Tue, Feb 9, 2010 at 5:52 PM, Frank W. Samuelson >> <fr...@merrill-samuelson.com> wrote: >>> You are something of a killjoy, Mike. >>> >>> This could grow into a really great project, where people don't even have to >>> learn programming to generate a usable django web database app. They just >>> design their app with the user friendly web interface, and it runs. It >>> could even be integrated with hosting, and people might never see the code, >>> it would just run. How many people who have web pages nowadays know HTML? >>> >>> Generate on! >>> >>> >>> On Tue, 9 Feb 2010, Mike Ramirez wrote: >>> >>>> On Tuesday 09 February 2010 13:09:08 Brice Leroy wrote: >>>>> >>>>> django-admin startproject creates an empty folder... >>>>> >>>>> startproject almost = mkdir >>>>> >>>>> This will generate your models, modelForm, views, templates, urls, and >>>>> soon customized forms and permissions >>>>> >>>> >>>> That's what the web interface does? >>>> >>>> Yes startproject gives you empty files so you can add in your own code, >>>> with >>>> the minimal funs. >>>> >>>> For me, I don't see your project as a big advantage, except maybe two >>>> minutes >>>> of time where I don't need to do things like: >>>> >>>> class MyModel(models.Model): >>>> ... >>>> >>>> >>>> I don't know, thought about your approach before, but think it's >>>> reduntant. >>>> Just because each project requires it's own data and model field >>>> attributes >>>> and form funs... And I think django already does a great job of >>>> genericizing >>>> this stuff with the code i.e. ModelFoms. I don't know how much of a real >>>> timesaver this really is. Didn't even mention tests.. Which can you auto >>>> generate? >>>> >>>> Especially if your project's outputed code isn't template driven where >>>> each >>>> user of it can change the boiler plate code with minimal or no fuss, so it >>>> can >>>> be tailored to each users needs. Like I'm able to add in my most used >>>> imports, which aren't all going to be yours or anyone elses or the same in >>>> each project. >>>> >>>> I think the minimal approach of django-admin is a much better way to do >>>> these >>>> things. With either way you still have to give the fields, options and the >>>> names, then fill in the functions you need/want. Each function that can be >>>> autogenerated is like two lines of code. >>>> >>>> I don't know if your generated code can handle a lot of choices I make, >>>> like >>>> making fields not editable in the admin, setting defaults, etc... and even >>>> if >>>> you do offer these choices, the time to use your project and code it up >>>> probably isn't much different. >>>> >>>> The big thing for me in terms of tools like this, is the ability to save >>>> time, >>>> which I don't think there is a difference between what django-admin has >>>> and >>>> your project. Because either way I need to still fill in the fields, the >>>> type >>>> of field it is, etc.. and typeing IntegerField() isn't faster than >>>> selecting >>>> from a drop down box. >>>> >>>> Tho the importing of existing models maybe interesting for refactoring, >>>> Tho I >>>> just cp oldversion newversion and make the changes. >>>> >>>> I still have a large feeling I'm going to editting what your project >>>> outputs >>>> (blame this on things like UML). When I would just rather write it once >>>> and >>>> forget it. >>>> >>>> I also love building development tools, I'm just finishing up something >>>> like >>>> this for Go. Where it'll generate a project directory tree of your Go >>>> files >>>> (either a package or command, with Makefiels, readme, etc.. all template >>>> driven so you can edit the boilerplate code to be what you want) it'll be >>>> released in a few more days when I finish cleaning up the default >>>> templates >>>> and a few optimizations. If you want to see what I mean, I don't mind >>>> sending >>>> it today. Just know there are a lot of mistakes in the templates and still >>>> looking at a few tweaks and playing with usability. >>>> >>>> But in the end, I think the time saved with yours is going to be minimal I >>>> believe unless your can guess what model fields I need and what options >>>> they >>>> are it's not saving that much time (maybe 30 minutes?). Otherwise, I think >>>> that altering django-admin startporject to be template driven is a better >>>> idea >>>> than this. Sorry for being negative, but without negativity how can we be >>>> challenged and grow? >>>> >>>> Mike >>>> >>>>> I'll add a copy project so you can extend an existing model if you >>>>> have a big production pace of common project model. >>>>> >>>>> 2010/2/9 Mike Ramirez <gufym...@gmail.com>: >>>>>> >>>>>> On Tuesday 09 February 2010 12:58:32 Brice Leroy wrote: >>>>>>> >>>>>>> Hello everybody, >>>>>>> >>>>>>> I've been working for a week on this idea of a generator for django >>>>>>> project. The goal is to provide a simple architecture that can be >>>>>>> after adapted to your project. The system is in alpha stage but allows >>>>>>> you to create project, model (+1 view and 1 form) and application. >>>>>>> Once your project is created you can download a tar.gz with the >>>>>>> complete project already build for you. >>>>>>> >>>>>>> It's supposed to be used with the trunk version of django. >>>>>>> >>>>>>> I plan to add permission, forms and view during the next 15 days. Let >>>>>>> me know if you have any advice or request. >>>>>>> >>>>>>> The project can be found here: http://alpha.djangogenerator.com/ and >>>>>>> is open to registration >>>>>>> The source code is located on github: >>>>>>> http://github.com/debrice/djangogenerator >>>>>>> >>>>>>> All the best, >>>>>>> >>>>>>> -- >>>>>>> Brice Leroy >>>>>>> http://www.debrice.com >>>>>> >>>>>> how is this different than `django-admin startproject` ? >>>>>> >>>>>> Mike >>>>>> -- >>>>>> Overconfidence breeds error when we take for granted that the game will >>>>>> continue on its normal course; when we fail to provide for an unusually >>>>>> powerful resource -- a check, a sacrifice, a stalemate. Afterwards the >>>>>> victim may wail, `But who could have dreamt of such an idiotic-looking >>>>>> move?' -- Fred Reinfeld, "The Complete Chess Course" >>>>> >>>> >>>> -- >>>> After the Children of Israel had wandered for thirty-nine years >>>> in the wilderness, Ferdinand Feghoot arrived to make sure that they would >>>> finally find and enter the Promised Land. With him, he brought his >>>> favorite robot, faithful old Yewtoo Artoo, to carry his gear and do >>>> assorted camp chores. >>>> The Israelites soon got over their initial fear of the robot and, >>>> as the months passed, became very fond of him. Patriarchs took to >>>> discussing abtruse theological problems with him, and each evening the >>>> children all gathered to hear the many stories with which he was >>>> programmed. >>>> Therefore it came as a great shock to them when, just as their journey was >>>> ending, he abruptly wore out. Even Feghoot couldn't console them. >>>> "It may be true, Ferdinand Feghoot," said Moses, "that our friend >>>> Yewtoo Artoo was soulless, but we cannot believe it. He must be properly >>>> interred. We cannot embalm him as do the Egyptians. Nor have we wood for >>>> a coffin. But I do have a most splendid skin from one of Pharoah's own >>>> cattle. We shall bury him in it." >>>> Feghoot agreed. "Yes, let this be his last rusting place." >>>> "Rusting?" Moses cried. "Not in this dreadful dry desert!" >>>> "Ah!" sighed Ferdinand Feghoot, shedding a tear, "I fear you do not >>>> realize the full significance of Pharoah's oxhide!" >>>> -- Grendel Briarton "Through Time & Space With Ferdinand >>>> Feghoot!" >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Django users" group. >>> To post to this group, send email to django-us...@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. >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To post to this group, send email to django-us...@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. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@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. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
