Re: Idea/Suggestion for PHP App
| From: | Robert Cummings | Date: | Thu, 05 Apr 2007 20:23:10 +0000 |
| Subject: | Re: Idea/Suggestion for PHP App | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-252111@lists.php.net to get a copy of this message | ||
On Thu, 2007-04-05 at 21:59 +0200, afan@afan.net wrote:
> > On Thu, 2007-04-05 at 21:36 +0200, afan@afan.net wrote:
> >> first step is: take a paper and pen and start drawing your app structure
> >> in blocks.
> >> once you "finished your app" on the paper start drawing db structure.
> >>
> >> start coding after you have the solution for every situation.
> >
> > You're kidding aren't you? Poor trees!
> >
> > BTW You will NEVER have the solution for every situation.
> >
>
> nope. not at all. I always tried to draw/build whole app's structure
> first. or, at least closer I can get. it's also true, I never covered ALL
> situations, but to me is much easier to code after I have AS MUCH AS I CAN
> HAVE answers than start coding and then re-coding few days later because
> "oops! I forgot that user can have two homes, not only one..." :D
>
> and yes, I (still) use paper and pencil because never find good app for
> it. if you can recommend - I'll be more than happy to use it and stop
> wasting paper (agree with you on "poor tree" :D)
I use two things... my brain for the overall idea. A notes.txt file for
specific remarks that are too complicated to keep up top :)
Cheers,
Rob.
--
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com
|
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting |
| a powerful, scalable system for accessing system services |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for |
| creating re-usable components quickly and easily. |
`------------------------------------------------------------'