[Seaside] trouble with callbacks
rleon at insario.com
Mon Aug 1 21:25:07 CEST 2005
I have a feeling that your renderContentOn is somehow changing state,
that call to the criteriaComponent at the top concerns me, seems that if
you're building up the list each time, that you can't page next because
each render builds up a whole new list of items, destroying the last
list that was rendered.
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf
> Of Jason Rogers
> Sent: Monday, August 01, 2005 11:59 AM
> To: The Squeak Enterprise Aubergines Server - general discussion.
> Subject: Re: [Seaside] trouble with callbacks
> On 7/29/05, Ramon Leon <rleon at insario.com> wrote:
> > Show code.
> renderMyContentOn: html
> | itemView |
> viewFilter := self getViewFilterFor: (self call: self
> itemView := self viewFilter view.
> itemView isEmptyOrNil
> [html divClass: #content with: [html
> text: 'None']]
> tableHeaders: (self gatherHeadersFrom: itemView).
> [bacthedListTableComponent data: itemView.
> html render: [bacthedListTableComponent].
> "answer a ShoreComponent that will be used to set my
> ifNil: [criteriaComponent := self
> criteriaComponentClass parent: self;
> label: self filterName;
> ^ criteriaComponent
> Jason Rogers
> "I am crucified with Christ: nevertheless I live; yet not I,
> but Christ liveth in me: and the life which I now live in the
> flesh I live by the faith of the Son of God, who loved me,
> and gave himself for me."
> Galatians 2:20
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside