On Wed, 24 Aug 2016, Lee Hinde wrote:
> So, no one is going to grade it. You're making this for yourself, so I
> wouldn't over think it. I'm working on a project now that only has two
> apps, one with all the core models and one for utility models (like choice
> lists).(I'm using several packages, so the database has more to it than
> that.)
> It sounds like something like that would work for you and still be 'right'.
> Especially as a first time out of the gate project, keep it simple. IMHO.
Lee,
Now this is a valuable lesson: core models and utility models. Many of my
classes have choice lists (select from a list of industries, or campaign
types) so I'll put those in the models.py of a separate app.
> While it will certainly evolve as you use it, you're not gong to suddenly
> wake up and need 18 more apps to meet your needs. And if that does happen,
> you can rearrange.
No, not on this project. But the next one will require more apps because
it has more functional groupings.
Many thanks again,
Rich
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment