[Seaside] Change component on initialRequest:

Sebastian Sastre sebastian at flowingconcept.com
Thu Feb 19 13:59:29 UTC 2015

I do not use Seaside tasks.

What I do is render a MainComponent without using #call: and teach that guy how to do things

If you do that, you can take the initial request and somehow make your app what this MainComponent should do


> On Feb 19, 2015, at 9:23 AM, Dave <lasmiste at gmail.com> wrote:
> Hi guys,
> I'm trying to display a specific component when a user go to a specific url
> (sort of bookmarkable url).
> I wanted to call a component in the initialRequest but looking at
> WAPresenter>>initialRequest: it says: "You can not use #call: in here.
> Consider using a WATask instead and sending #call: in #go."
> but it's not really clear to me how to use a task, can you point me in the
> right direction?
> Thanks
> Dave
> --
> View this message in context: http://forum.world.st/Change-component-on-initialRequest-tp4806479.html
> Sent from the Seaside General mailing list archive at Nabble.com.
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list