|
|
Posted by kenoli on 11/06/06 15:30
I'm sure there are as many solutions to this as there are programmers,
but I am interested in how people organize their scripts during
development. I'm working alone on this so there is no issue with
communicating with others working on the saem project.
I understand that an IDE is supposed to help with this. I have never
used an IDE but am looking into PHPEcllipse (I can't quite figure out
how to use it effectively on my own and have ordered the recent book on
the subject) and Zend studio (not sure if it is worth the investment-I
am trying to understand the beta version that they provide free access
to for a month-the price is a bit steep for me). I'd be interested in
opinions on these or other php software (I'm on a Mac).
Otherwise, I'm wondering if people have ideas for things like naming
scripts in progress or organizing directories. 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. This is exaercbated by
the fact that sometimes a script gets left in a state where it won't
run and that gives me even more trouble figuring out what I was working
on or where I was in it.
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.
These are some of the things I've been doing (I'm only working with
procedural coding at this point, not objects):
1. Trying to keep input screens mostly in files that can be read by
Dreamweaver to make form design and CSS formatting easier and separate
formatting from content. Keeping these in their own directory.
2. Making as many operations as possible into functions and grouping
them by some logical arrangement in "include" files.
3. Naming scripts I'm working on while in progress by names that more
or less describe their functions. Putting these in a "test_include"
directory until they are complete and go into their final destination
file.
4. Creating one directory for "trial" scripts where I isolate scripts
to try to understand how to make them work or what is wrong.
Any good ideas?
Thanks,
--Kenoli
Navigation:
[Reply to this message]
|