I guess that's where passengers: come handy. Because what you pass can be the result of a jQuery.
TBH sometimes it is easier to do a JSStream on: 'some js code that does what you want' instead of wondering for ages how to do the same with the Javascript classes, subclasses and methods. Look into the test packages for lots of examples. That helped me. Phil On Fri, Dec 9, 2016 at 2:20 PM, Siemen Baader <siemenbaa...@gmail.com> wrote: > Hi all, > > I'm confused about the limitations and intended use of Seaside's javascript > builders. I can follow that we can do eg: "(html jQuery: 'div') remove" or > "html javascript alert: 'hello'" within the "renderContentOn: html" > methods, > but how do I deal with logic and variables? How do I eg. install an event > listener and provide a browser-side function that extracts data from the > event and then passes it to the server via "html jQuery ajax"? > > Is this something to be done in pure JS returned from the #script method? > > Thanks for any enlightenment! > > Siemen > > > > -- > View this message in context: http://forum.world.st/seaside- > javascript-builders-tp4926336.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >
