17 Jul 00:14
Re: rebuild children - when to do it
From: Julian Fitzell <jfitzell <at> gmail.com>
Subject: Re: rebuild children - when to do it
Newsgroups: gmane.comp.lang.smalltalk.squeak.seaside
Date: 2008-07-16 22:14:14 GMT
Subject: Re: rebuild children - when to do it
Newsgroups: gmane.comp.lang.smalltalk.squeak.seaside
Date: 2008-07-16 22:14:14 GMT
It's not the normal pattern. If your children aren't persisting between requests then their state isn't being persisted (or rolled back with the back button). If you feel your code is working fine, then you may not actually need components for these "children". If your child components do not have or need state, you might consider subclassing WAPresenter instead of WAComponent. These can be created at will and used for rendering. Or of course you can create any other class that implements #renderOn: and use that. If you do want/need components, you should, as Ramon says, usually use lazy initialization or set up your children when the component is initialized. Cheers, Julian On Thu, Jul 17, 2008 at 5:55 AM, Squeaker <squeakman <at> gmail.com> wrote: > Greetings, > > In my renderContentOn: method I am making a call to my method > rebuildChildren which reconstructs my children on the fly. This is done as > the first thing in renderContentOn: > > The code appears to work. > > My question: Is it ok to rebuild my children at rendering time? > > Thanks, > Frank > > _______________________________________________ > seaside mailing list > seaside <at> lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >
RSS Feed