Iván Sánchez Ortega wrote:
> Mo wrote:
>
> [...]
>> The reason I avoided using colspan is because I've seen it cause
>> problems when it comes to trying to export the data to a .CSV format.
>
> Uh, what?
>
> How (on earth) are you doing the html -> csv conversion?
>
> It's much easier, IMHO, to use a MVC pattern to output either HTML or CSV.
>
>> As for making the spaghetti code more modular, do you have any
>> suggestions?
>
> Not really: how the code is structured depends on the design, not on the
> coding itself. I do think that reading about design patterns would
> enlighten you.

I'm a new PHP programmer, but not new at programming. I'm unfamiliar
with this. Could you throw an example or a link my way? What I've just
googled up makes this look like a RAD. When I look at PHP Cake examples,
it looks like a collection of classes. I'm really confused.

My own style is to use a template and call a class depending on what
the page instructions are. The end result is to have reusable bits that
can be customized and reconfigured. Instructions could be sent on the
query string or be related to the page path. I'm not sure how that fits
in with this.

Jeff

>
>> Also, are you referring breaking up the code into multiple pages and
>> using INCLUDE function? (I do plan to do this with the DB connection
>> parts of the code.)
>
> Yes, but you really need to plan that in advance, and for planning it
> *right*, you'll just need some experience.
>
> Cheers,