On Monday, Dec 16, 2002, at 08:55 US/Pacific, Christopher Oliver wrote:
Ovidiu Predescu wrote:
On Sunday, Dec 15, 2002, at 23:59 US/Pacific, Ugo Cei wrote:
Ovidiu Predescu wrote:
One solution would be to define a pseudo-continuation, just after
you finish the function initialization code
Ovidiu Predescu wrote:
On Sunday, Dec 15, 2002, at 23:59 US/Pacific, Ugo Cei wrote:
Ovidiu Predescu wrote:
One solution would be to define a pseudo-continuation, just after
you finish the function initialization code, which could be referred
from the View page template. Something like:
fun
On Sunday, Dec 15, 2002, at 23:59 US/Pacific, Ugo Cei wrote:
Ovidiu Predescu wrote:
One solution would be to define a pseudo-continuation, just after you
finish the function initialization code, which could be referred from
the View page template. Something like:
function myFunc()
{
var a;
Ovidiu Predescu wrote:
One solution would be to define a pseudo-continuation, just after you
finish the function initialization code, which could be referred from
the View page template. Something like:
function myFunc()
{
var a;
// Long initialization code here
startForm(); // Creates a
On Saturday, Dec 14, 2002, at 12:33 US/Pacific, Ugo Cei wrote:
Christopher Oliver wrote:
In this case to go back to the beginning you don't need a
continuation. You can just call the function again.
Which wouldn't work if you have some code at the beginning of the
function that is to be exe
Ovidiu Predescu wrote:
The value "2" for the "select" attribute is because it looks like
using "1" actually refers to the "current" continuation and not the
"previous" one as I thought initially. Am I correct and is this a
"feature" or a "bug"?
I don't see how "1" could refer to the current c
Christopher Oliver wrote:
In this case to go back to the beginning you don't need a continuation.
You can just call the function again.
Which wouldn't work if you have some code at the beginning of the
function that is to be executed only once.
Ugo
---
On Friday, Dec 13, 2002, at 21:46 US/Pacific, Christopher Oliver wrote:
Ugo Cei wrote:
I've tried to implement this use case in a flowscript like the
following:
function foobar() {
// Note the use of the "new style" function names
sendPageAndWait("showform", {});
// Collect request par
Hi Ugo,
On Friday, Dec 13, 2002, at 08:18 US/Pacific, Ugo Cei wrote:
Dear flow gurus,
suppose I have an application that implements the following workflow:
1. Present the user a form to be filled.
2. When the user submits the form, present him a confirmation page,
with two buttons: "Confirm"
Konstantin Piroumian wrote:
From: "Ugo Cei" <[EMAIL PROTECTED]>
It seems to me that Christian's version is more correct conceptually, it
allows to perform additional actions when user clicks "Go back", while in
your version the flow engine will automatically return the flow to the
pervious st
Ugo Cei wrote:
I've tried to implement this use case in a flowscript like the following:
function foobar() {
// Note the use of the "new style" function names
sendPageAndWait("showform", {});
// Collect request parameters here
sendPageAndWait("askforconfirmation", { /* ... field values .
From: "Ugo Cei" <[EMAIL PROTECTED]>
> Christian Haul wrote:
> > Interesting. Why not:
> >
> > function foobar() {
> >// Note the use of the "new style" function names
> >var response = null;
> >do {
> >sendPageAndWait("showform", {});
> >// Collect request parameters he
Christian Haul wrote:
Interesting. Why not:
function foobar() {
// Note the use of the "new style" function names
var response = null;
do {
sendPageAndWait("showform", {});
// Collect request parameters here
sendPageAndWait("askforconfirmation", { /* ... field value
On 13.Dec.2002 -- 05:18 PM, Ugo Cei wrote:
> Dear flow gurus,
>
> suppose I have an application that implements the following workflow:
>
> 1. Present the user a form to be filled.
>
> 2. When the user submits the form, present him a confirmation page, with
> two buttons: "Confirm" and "Go back
Dear flow gurus,
suppose I have an application that implements the following workflow:
1. Present the user a form to be filled.
2. When the user submits the form, present him a confirmation page, with
two buttons: "Confirm" and "Go back"
3a. If the user presses "Confirm", perform some job (e.g
15 matches
Mail list logo
