Seaside 3.0 status

[bnemec]

I'm spending a lot of time in Seaside on VW (and a bit on Pharo). Our shop also supports a VA app that I'd like to add a Seaside interface to. I have a simple navigation working, but I'm limited by the inability to use call: and lightbox: in VA, due to continuation errors.

Loading GemBuilder with Seaside & Grease requires some code changes. To make sure I was not causing my own problems, I tried a base VA image, loaded Seaside from the list of features, and ran some Seaside tests. WAFlowFunctionalTest fails with...

a ContextEmulator
WAActionCallback>>#evaluateWithArgument:
arg1 = nil
not found while capturing continuation.

Executing in: WARequestContext>>#push:while:

...should I expect this work in VA 8.0.2? If not, will issues like this be resolved when the Seaside 3.0 RC is ported to VA? Is there something else to load or initialize? There a number of posts on this (using #show: vs. #call: because of continuation errors), but I have not seen a solution or work-around (sorry if I missed it).

BTW: the VA / GS app uses jpg images stored in GS to provide a graphic drill down navigation. Making that same interface work in Seaside has been straight forward, and looks very cool. Users really seem to like having a browser interface to a legacy app.

Thanks for any help,
Bob Nemec

[bnemec]

Anyone... anyone?

[wembley]

Bob -

Seaside 3.0RC will be available in the first V8.0.3 development build.

No, you shouldn't expect that to work in V8.0.2 since Seaside Flow depends on continuations and continuations don't work in V8.0.2.

[wembley]

Bob -

And, as to the workaround, it is to use #show:

Code: Select all

<some code>.
r := self call: aComponent. “NO, does self wait:”
<more code using r>.

<some code>.
self show: aComponent onAnswer: [ :r |
  <more code using r ]. “YES”