[Seaside] initialRequest: / updateRoot: / updateUrl:
Sebastian Sastre
sebastian at flowingconcept.com
Thu May 19 18:39:27 UTC 2011
the lazy init is ok?
is #resetVisibleComponent doing something like this:
^ visibleComponent := VisibleComponent new
??
On May 19, 2011, at 3:31 PM, Francois Stephany wrote:
> Hi list,
>
> I probably forget something stupid but I have some trouble with initialRequest:/updateRoot:/updateUrl:
>
> WAComponent
> subclass: #WPRootComponent
> instanceVariableNames: 'visibleComponent'
>
> WPRootComponent>>children
> ^Array with: self visibleComponent.
>
> WPRootComponent>>renderContentOn: html
> html render: self visibleComponent.
>
> WPRootComponent>>visibleComponent
> visibleComponent isNil ifTrue: [ self resetVisibleComponent ].
> ^visibleComponent.
>
> visibleComponent is an instance of sublass of a subclass of WAComponent.
>
> WPAVisibleComponent>>updateUrl: anUrl
> self halt.
>
>
> initialRequest:, updateRoot: and updateUrl: are never called on visibleComponent (halt never occurs).
>
> Are there common mistakes that introduce this behaviour ?
>
> Cheers,
> Francois
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
More information about the seaside
mailing list