[Seaside-dev] WAError: You can no longer call #addLoadScript: on WASession

Sebastian Sastre ssastre at seaswork.com
Wed Mar 18 10:29:21 UTC 2009


ah yes, it's a fresh pharo core 248 with 2.9a3 
I'm seeing: 

WATagBrush>>script: aPrototype
	aPrototype isNil
		ifTrue: [ ^ self ].
	(aPrototype respondsTo: #id:)
		ifTrue: [ aPrototype id: self ensureId ].

	aPrototype session addLoadScript: aPrototype


sebastian

> -----Mensaje original-----
> De: seaside-dev-bounces at lists.squeakfoundation.org 
> [mailto:seaside-dev-bounces at lists.squeakfoundation.org] En 
> nombre de Julian Fitzell
> Enviado el: Wednesday, March 18, 2009 07:22
> Para: Seaside - developer list
> Asunto: Re: [Seaside-dev] WAError: You can no longer call 
> #addLoadScript: on WASession
> 
> This is 2.9a3? I don't see any senders in my image calling
> #addLoadScript: on Session. You'll need to give a stack trace...
> 
> Julian
> 
> On Wed, Mar 18, 2009 at 11:05 AM, Sebastian Sastre 
> <ssastre at seaswork.com> wrote:
> > hi there,
> > I'm seeing this for in place editor and friends. Not only 
> in my app but in
> > seaside tests.
> > should I have to add this as an issue in google code?
> > sebastian
> >
> > _______________________________________________
> > seaside-dev mailing list
> > seaside-dev at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
> >
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev



More information about the seaside-dev mailing list