Re: JQAjax>>#script: in GemStone 3.3.1 with Seaside 3.2.1 works differently than in pharo

I'm still having a problem with this and would be interested in learning if
others are able to use JQAjax>>#script: on GemStone.


For me it does the request, the server is updated, but the response is the
entire page and not just the contents of the script block.


Is there a way to work around this?

I could come up with an example pretty easily if ir would be helpful.


Thanks.



Paul DeBruicker wrote
> In Pharo I can use a #script: send like this
> 
>  html jQuery ajax
>         callback: [ :json | self setMapBoundsFrom: json ]
>           json: (JSStream on: 'map.getBounds()');
>         script: [ :s | s << ((s jQuery id: #'results') html: [ :r | self
> renderResultsOn: r ]) ]
> 
> 
> And the #results id has its content set to the value of the
> #renderResultsOn: method.  
> 
> 
> In GemStone it seems like a page refresh is happening instead.
> 
> 
> Has anyone else seen this?  I think it was happening in older versions too
> but I am not sure of what version combination.
> _______________________________________________
> seaside mailing list

> [email protected]

> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside





--
View this message in context: http://forum.world.st/JQAjax-script-in-GemStone-3-3-1-with-Seaside-3-2-1-works-differently-than-in-pharo-tp4925035p4939880.html
Sent from the Seaside General mailing list archive at Nabble.com.
_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside