My take on the two terms: generate: make something I'm allowed/encouraged to edit later. generate:crud, generate:app, generate:project, etc. build: rebuild something that's required to run the app but isn't supposed to be directly edited.
the build tasks are really kind of a hybrid since they make both editable and non-editable code. at least with propel. i don't have experience with doctrine. for what it's worth, I'd like to see doctrine:build (and propel) default to building models, sql, and forms and add --no-model, --no- sql, --no-form options. you have to run all three tasks after updating the schema. why make it harder for the normal case? On Jul 23, 2009, at 2:34 PM, Kris Wallsmith wrote: > Hello, > > In an effort to reduce the number of tasks in the ORM plugins I've > come up with a new, flexible "build" task. Its usage in the Doctrine > plugin would look something like this: > > php symfony doctrine:build --model --sql --forms > > This would be the same as running these three tasks in symfony 1.2: > > php symfony doctrine:build-model > php symfony doctrine:build-sql > php symfony doctrine:build-forms > > My question to the group is a semantic one. Tasks currently use the > terms "generate" and "build" interchangeably, without any sort of > reason that I can deduce. Can we just choose one and get rid of the > other, or am I missing something? > > Thanks, > Kris > > -- > > Kris Wallsmith | Web Developer > [email protected] > 503.734.5700 > > http://twitter.com/kriswallsmith > > > > -- Jacob Coby --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
