|
|
Posted by J.O. Aho on 11/06/06 15:50
kenoli wrote:
> I understand that an IDE is supposed to help with this.
Yes, an IDE can keep track of files you are using in a project and the more
advanced it is, the more features it has, some can keep track of all your new
functions you created in your scripts. Myself I have been mostly used Emacs,
but begun to use KDevelop more and more.
> Otherwise, I'm wondering if people have ideas for things like naming
> scripts in progress or organizing directories.
I try to keep a name that tells a bit about what the script does, say you have
made your own login engine, then those functions could be stored in
login_engine.php.
Directories I don't have that many, usually libs, conf, admin and so, where I
store files which has to do with those things.
> I end up with a variety
> of scripts I am working on for various parts of a project and often
> have trouble remembering which is which or which is at what stage of
> development or how they relate to each other.
Why not make comments? That makes it easier for you to follow what you have
done and what you wanted to do, and the same applies if someone else would
take a look at your scripts, say to find a bug you don't fix yourself.
> Also, I often create short scripts for testing a specific function of
> piece of a larger script or just trying out and understanding some php
> function or operator. These all get mixed up.
Why not place those under a subdirectory called test? Then you can easilly
just ignore those scripts when you are finished with the testing.
> 4. Creating one directory for "trial" scripts where I isolate scripts
> to try to understand how to make them work or what is wrong.
I'm not much for renaming and change include paths, so I make a copy of the
project directory if I will try something big, that way I can always get back
to the same state if the test fails.
//Aho
Navigation:
[Reply to this message]
|