On Thu, 26 Jun 2003 22:50:38 -0400, "Albert Ahtenberg"
I have pretty much the same problem, which I solve by dividing the>Hello,
> I had some bad experience with code organization and script
>functionality in writing my php based applications. And as the applications
>get bigger in scale it gets even worse. Therefore, I am trying to build a
>general schema for data flow in a php/mysql application.
> What I has in mind is to design a three major units. To handle the
>input, processing and data access. Plus another unit to generate the output.
> What I have now is one script that resolves the operation to be done
>according to the parameters send to it and the call the processing unit to
>do the rest of the job. However, as I add more functionality to the system
>this dispatcher script gets bigger and bigger...
> 1. How can I arrange my program/data flow in an efficient and easily
dispatch script into smaller logical portions. But thats not nice.
I thought you would want to model it in a database or an array, so
that a script could output the program flow as well. You could capsule
that with a class, so that the dispatch script can ask for the
appropriate task for this input.
Isn't the output dependent on the action? In my scripts the output> 2. And how should I implement the output generation unit to be
>completely seperate from the others (I have lots of forms and outputs I have
>to show the user when necessary)?
pretty much follows the structure ofthe code.
Jochen Daum - CANS Ltd.
PHP DB Edit Toolkit -- PHP scripts for building
database editing interfaces.