> I need help managing my project files. I've got over 120 class files
> each that have their own specific validation routines. Most of which
> are pretty tame, but some are pretty nasty. Anyways, I took a stab at a
> creating one .py file for each class, but it's turning out to be a mess
> of include statements. Going back to a single file makes for a HUGE
> file which is manageable, but annoying when searching for particular code.
>
> Anyways - I though I'd ask to see if there were any examples or
> resources out there that I could look at that would help me clean this up.
Why not put around 10-20 classes that are closely related into one
file? This is what I do too, then you have around 10-15 files which is
manageable all right. Surely your classes can be grouped according to
some criteria.
Search and jumping around in source code is quite easy in vim which is
what I use, but I bet other good editors make it simple too. So
normally you don't have to search for strings but the function names,
class names, etc, are stored structurally in a 'tags' file which is
then used by the editor.
Cheers,
Daniel
--
Psss, psss, put it down! - http://www.cafepress.com/putitdown
|
