[Seaside] Problem getting render methods to be functional

[Derek Brans]

Yes, it's inside a container and it needs to be because all my top-level 
components reside within a template-like component.

Actually, I think I got around it by calling Session>>start when the 
user changes.  That way the entry point is re-initialized.

Thanks again,
Derek


On Tuesday, February 4, 2003, at 06:48 PM, Avi Bryant wrote:

>
> On Tue, 4 Feb 2003, Derek Brans wrote:
>
>> Avi, Julian,
>>
>> I'm wondering what can or should not be done in a render method.
>> Creation of components I gather are out.  What other sorts of things
>> constitute "important side effects"?
>
> Anything that affects the value of a StateHolder.  The problem is that
> currently the StateHolders are snapshotted before the rendering starts, 
> so
> any changes made during the rendering will get lost.
>
> This is not an ideal restriction, and I'd like to just get rid of it, 
> but
> that'll take a fair amount of reworking, so don't expect to see it fixed
> right away.
>
>> The change in user happens somewhere else in the application so my
>> component couldn't know about it until render time.  At the beginning 
>> of
>> my render method in the main component, I detect a change in user and
>> create a fresh tabComp (based on the user's permissions).  That's 
>> giving
>> me problems related to lazy initialization as before.
>
> Is the tab component inside a Container?  I wouldn't expect it to be...
> and if it's not this shouldn't actually break anything.
>
> Avi
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>
>
Nerd on a Wire: Web and Information Solutions
Website Design - Database Systems - Site Hosting
604.874.6463
mailto:info at nerdonawire.com
For more information, visit http://nerdonawire.com