Re: [PHPLIB] adding structure to the chaos From: Arno A. Karner (karner <email protected>)
Date: 03/09/00

On Thu, 9 Mar 2000, Kristian Koehntopp wrote:

> On Wed, Mar 08, 2000 at 02:53:40PM -0600, Arno A. Karner wrote:
> > I was thinking of implamenting some kind of return stack as a session
> > variable, but not sure how to get the page i called to do a return
> > function upong compleation, then i would have to use some session variable
> > for a return value.
>
> You could view a set of web pages as a state machine, and keep
> the state as a session variable. Depending on the current page,
> current state and the name of the submit button the user pressed
> you would determine the next function/operation that being
> executed. Unless you are doing relocations (which I think is
> ugly), you'd have to run your application under a single URL,
> though. Instead of relocation to the next page based on state,
> you would include() that page instead - for the user the URL
> does never change.
>
> Kristian
>
i thought of doing that way too. one big page with a lot of include files
that seems as ugly to me as a go to statment, and doesnt realy alow reuse
of any logic thats in the big ugly page unless it too is made up of include file

the big single page application just has too many draw backs, first it all
has to be parsed every time, second unless u realy get sneeky with your
state stuff, the same forms are going to be included multiple times, but
only one form will be viewed or worked on at a time.

any body else got 2 cents to chip in?

-
PHP3 Base Library Mailing List. Send messages to <phplib <email protected>>.
To unsubscribe, send "unsubscribe" to <phplib-request <email protected>> in
the body, not the subject, of your message.