Skip to main content

How to access the jQuery event object in a Seaside callback


Basically, I want to translate the following into Seaside Smalltalk:




$(".myDiv").bind('click', function(e) {
console.log(e);
});



Besides that I don't want to console.log the event, but access it in my ajax callback.



The most promising approach seemed to be something like




html div
onClick: (html jQuery ajax callback: [:v | self halt] value: (???);
with: 'Foo'.



But I couldn't find any way to access the event that caused the callback. Intuitively, I would try




html jQuery this event



for the ??? part, but the Seaside jQuery wrapper doesn't know any message that comes close to event .



Any help is appreciated. There has to be away to access the event data...


Source: Tips4allCCNA FINAL EXAM

Comments

  1. To serialize the x mouse coordinate of the event use the following code:

    html div
    onClick: (html jQuery ajax
    callback: [ :x | x inspect ]
    value: JQEvent new pageX);
    with: 'Click'.


    There are other properties in the event object that you might be interested in, just serialize them with the same AJAX request by adding multiple callback:value: constructs in a cascade.

    In the very latest JQuery code you can use html jQuery event to create the event object. This was missing up to now.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex