I usually start with defining goals, actors and use cases, continue
with UML class diagrams and UI mockups on paper, and then transfer all
that to Python in this order: models, urls, views, templates. Then I
manually populate the DB with some data, dump a fixture and
periodically reset the app dat
On Monday 19 October 2009 18:11:38 Sam Lai wrote:
> I am tempted to ask a related question though - what do people use to
> plan out their projects (for those that do :)? Large sheets of paper,
> diagramming software (e.g. Visio), mindmaps, plain old text files...
>
> (Feel free to tell me to lo
2009/10/20 Shakefu :
> So ... I feel slightly guilty about asking this, because I might as
> well be throwing napalm on the stove but which editors/IDEs/whatever
> do people prefer for their Djangoing?
Don't mean to rain on your parade, but this topic's been done to
death, even recently - here'
Definitely +1 to Mike's post. Lots of great advice.
I'm ashamed to admit that I'm usually the sort who goes about projects
without any written planning what so ever. Generally I spend some time
forming an idea in my head as to what I'd like and what I want to
implement, but often that gets twiste
I really like Mike's post and I think it all boils down to what he's
said. There's not much to add except other personal preferences and
delicacies you take onto a new project.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Saturday 17 October 2009 21:55:39 Shakefu wrote:
> So my questions are simple:
>
> What are your opinions on the best methodologies and practices for
> developing django apps and projects?
>
> What sort of planning do you do for an application or project?
I've been thinking about this and fi
On 19 Paź, 12:00, bruno desthuilliers
wrote:
> On 18 oct, 23:15, Mike Ramirez wrote:
>
> Or write a custom migration script, or just fire your favorite db
> client and issue a couple SQL queries.
>
> > I tend to start with the models first and when I add a field, I just use
> > alter
> > to u
On 18 oct, 23:15, Mike Ramirez wrote:
> On Sunday 18 October 2009 13:57:58 Shakefu wrote:
>
> > > > a first working implementation of my models (remember you can test
> > > > your models from the interactive shell and/or python scripts).
>
> > > Or write unit tests, which are more suited for te
HI,
=>> I tend to start with the models first and when I add a field, I
just use alter
>> to update the table in place. This has a gotcha with NOT NULL though, if you
>> don't specify a default you'll end up with an error. To bypass this error, I
>> usually don't add the NOT NULL constraint till
>
> > Is there any downside to starting with the models first?
>
> The biggest one is that if you decide later to add a field to the model that
> isn't there and you've filled in some data to the db.
I agree 100%. On this project (and some I've worked on before) I know
I'll be adding fields as it
On Sunday 18 October 2009 13:57:58 Shakefu wrote:
> > > a first working implementation of my models (remember you can test
> > > your models from the interactive shell and/or python scripts).
> >
> > Or write unit tests, which are more suited for testing than loose
> > bunch of scripts
>
> Well, I
>
> > a first working implementation of my models (remember you can test
> > your models from the interactive shell and/or python scripts).
>
> Or write unit tests, which are more suited for testing than loose
> bunch of scripts
>
Well, I certainly have noticed that a lot of guides/tutorials/snipp
On 18 oct, 17:04, Tomasz Zieliński
wrote:
> On 18 Paź, 15:48, bruno desthuilliers
> wrote:
>
> > a first working implementation of my models (remember you can test
> > your models from the interactive shell and/or python scripts).
>
> Or write unit tests, which are more suited for testing than
On 18 Paź, 15:48, bruno desthuilliers
wrote:
>
> a first working implementation of my models (remember you can test
> your models from the interactive shell and/or python scripts).
Or write unit tests, which are more suited for testing than loose
bunch of scripts
--
Tomasz Zielinski,
http://py
On 18 oct, 06:55, Shakefu wrote:
> So my questions are simple:
>
> What are your opinions on the best methodologies and practices for
> developing django apps and projects?
>
> What sort of planning do you do for an application or project?
>
> What development techniques do you use to help conc
Ah, thanks for the input. In this case I'm just developing an app for
my own gratification.
Unfortunately, I have rough idea as to what I'd like it to do
eventually, but since the details aren't set in stone or even pencil
I'm looking for some ideas to get started.
Plus it never hurts to learn a
Ah, thanks for the input. In this case I'm just developing an app for
my own gratification.
Unfortunately, I have rough idea as to what I'd like it to do
eventually, but since the details aren't set in stone or even pencil
I'm looking for some ideas to get started.
Plus it never hurts to learn a
It surely depends on your input. If you have detailed specification
of user interface, then writing URLconfs is probably more or less no-
brainer,
and also the design can often be quite obvious.
On the other hand, if you're starting in 'fluid' environment
and project doesn't have a direction, the
So my questions are simple:
What are your opinions on the best methodologies and practices for
developing django apps and projects?
What sort of planning do you do for an application or project?
What development techniques do you use to help conceptualize an
evolving project/app?
For example:
19 matches
Mail list logo
