[Seaside] JQAjax>>#script: in GemStone 3.3.1 with Seaside 3.2.1 works differently than in pharo
Mariano Martinez Peck
marianopeck at gmail.com
Sat Mar 25 01:14:46 UTC 2017
On Fri, Mar 24, 2017 at 6:44 PM, Paul DeBruicker <pdebruic at gmail.com> wrote:
> 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.
My app has become 90% AJAX requests and in 99% of them I use #script:
I can tell you that both on Pharo 5.0 and GemStone 3.3.3 (Seaside from
'github://GsDevKit/Seaside31:3.1.?/repository' ) it works correct (the
response is the script response and not whole page).
If you give me an reproducible example I can try in my stone.
> 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
> > but I am not sure of what version combination.
> > _______________________________________________
> > seaside mailing list
> > seaside at .squeakfoundation
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> View this message in context: http://forum.world.st/JQAjax-
> Sent from the Seaside General mailing list archive at Nabble.com.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside