[cgiapp] Run-Modes and events question

[Lyle Brooks <suppressed>]

1) 

I tried to locate an archive for this list, but was unable to.

If there is one, can someone point me to it?



2)

I've read over the documentation for CGI::Application.  One thing I 
really like it is the state transition model it uses to map "run-modes"
to methods.

If I understand the docs, the run-mode corresponds to the "current state"
or form being displayed in your application  (As opposed to the the "next
state" or state that you get to from a transition).

What I don't see illustrated in the examples in the events that cause a
transition from one state(run-mode) to another.

The state or run-mode is encoded in a hidden form field (typically "rm"),
but what about the events.

In the examples I saw there seemed to be only one possible event generated
per form.  This is fine for an example, but most forms have a number of
events that could be generated (hyperlinks, form buttons, image buttons, etc.)

What are some of the way events are modeled within a CGI::Application program,
with the emphasis on having one out of many possible events being generated
from the same run-mode?





---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed