Seaside 2.9 WARenderloop Replacement

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Seaside 2.9 WARenderloop Replacement

Karsten Kusche
Hi,

i've noticed that WARenderLoop has been removed in Seaside 2.9. The docs
on Seaside.st don't mention what class should be used instead, so i'm
asking here.
When I try to open a new window with a new component the WARenderLoop
should have been used in Seaside 2.8. What can I call now to open a new
component in a new window?

Kind Regards
Karsten


--
Karsten Kusche - Dipl.Inf. - [hidden email]
Tel: +49 3496 21 43 29
Georg Heeg eK - Köthen
Handelsregister: Amtsgericht Dortmund A 12812
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 2.9 WARenderloop Replacement

Julian Fitzell-2
Hi Karsten,

I'm trying to remember the details of this. I think that we discovered
that creating a new RenderLoop was only working because of a
coincidence caused by the way we were using exceptions and full
continuations. When we switched to partial continuations, which gave
us a more accurate model of what was actually happening, that
functionality stopped working.

I believe (but don't have an image with me to check), that we decided
the same thing could be more simply accomplished by simply doing a
call or show from the root component (which is now stored in a
property on Session by the render loop). I kind of think we added a
method to Session to easily support this but it's all a bit fuzzy. Let
me know if you can't find it and I'll check again when i'm back on my
own computer.

It could still be made possible to "start a new renderloop" but I
think a new exception would need to be created and you would have to
define what the semantics are of that. Does #initialRequest: get
called again, for example? The WARenderLoop class itself was removed
because it didn't represent a loop and didn't really do anything. The
"loop" is simply the Action continuation and Render continuation
calling each other. You can start a new loop by creating a new
continuation of whichever type and running it, but that's where i
think a new exception is needed because I think you need (this is
where I can't quite remember the details anymore) to drop back out of
the callback code before going to the new continuation.

Let me know if you need more help here and I'll take a look next week.

Julian

On 9/18/09, Karsten <[hidden email]> wrote:

> Hi,
>
> i've noticed that WARenderLoop has been removed in Seaside 2.9. The docs on
> Seaside.st don't mention what class should be used instead, so i'm asking
> here.
> When I try to open a new window with a new component the WARenderLoop should
> have been used in Seaside 2.8. What can I call now to open a new component
> in a new window?
>
> Kind Regards
> Karsten
>
>
> --
> Karsten Kusche - Dipl.Inf. - [hidden email]
> Tel: +49 3496 21 43 29
> Georg Heeg eK - Köthen
> Handelsregister: Amtsgericht Dortmund A 12812
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 2.9 WARenderloop Replacement

Philippe Marschall
2009/9/20, Julian Fitzell <[hidden email]>:

> Hi Karsten,
>
> I'm trying to remember the details of this. I think that we discovered
> that creating a new RenderLoop was only working because of a
> coincidence caused by the way we were using exceptions and full
> continuations. When we switched to partial continuations, which gave
> us a more accurate model of what was actually happening, that
> functionality stopped working.
>
> I believe (but don't have an image with me to check), that we decided
> the same thing could be more simply accomplished by simply doing a
> call or show from the root component (which is now stored in a
> property on Session by the render loop). I kind of think we added a
> method to Session to easily support this but it's all a bit fuzzy. Let
> me know if you can't find it and I'll check again when i'm back on my
> own computer.

WAPopupFunctionalTest as always.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 2.9 WARenderloop Replacement

Karsten Kusche
Hi Julien and Philippe,

thanks a lot for the help, just using #show:onAnswer: does the trick :-)

Kind Regards
Karsten




Philippe Marschall wrote:
2009/9/20, Julian Fitzell [hidden email]:
  
Hi Karsten,

I'm trying to remember the details of this. I think that we discovered
that creating a new RenderLoop was only working because of a
coincidence caused by the way we were using exceptions and full
continuations. When we switched to partial continuations, which gave
us a more accurate model of what was actually happening, that
functionality stopped working.

I believe (but don't have an image with me to check), that we decided
the same thing could be more simply accomplished by simply doing a
call or show from the root component (which is now stored in a
property on Session by the render loop). I kind of think we added a
method to Session to easily support this but it's all a bit fuzzy. Let
me know if you can't find it and I'll check again when i'm back on my
own computer.
    

WAPopupFunctionalTest as always.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


  

--
Karsten Kusche - Dipl.Inf. - [hidden email]
Tel: +49 3496 21 43 29
Georg Heeg eK - Köthen
Handelsregister: Amtsgericht Dortmund A 12812

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside