Hi John
I don't envy you the task :-( I am working from scratch and that is
hard enough!
My main problem is maintainability of the code. I can write something
that works, however it becomes exceedingly difficult to debug and modify
as the number of pages gets beyond three or four.
The Redirect After Post article and the Struts example have put me on
the right path though I think. Breaking the problem into two steps and
handling them separately makes things clearer at the very least, even if
it doesn't reduce the total amount of code much.
Interested to hear how you go.
Regards,
Langdon
John Zimmerman [gmail] wrote:
> Thanks for the articles. They look like they might be helpful. I will
> read through them tonight.
>
> I inherited a web application development project and am trying to move
> away from the filearts framework. I have hacked on it as much as I can
> but it just isn't very good at a lot of things.
>
> Currently I am using the old framework, PEAR's QuickForm, and a messy
> controller that I wrote to keep the two in line. In general I am doing
> the following
>
> 1. display step 1
> 2. validate posted data
> 3. if validate fails redisplay step 1
> 4. if validate passes go to step 2
>
> The number of steps are pre-defined. Moving forward to the next step is
> being done through the php header('Location: url'); function.
>
> This method is getting very messy and since I am migrating to cake I am
> very interested in avoiding the same kind of shenanigans.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---
