Skip to main content

Class Pointers in CoffeeScript?



trying to figure out how to write the following in CoffeeScript:







var foo = new function()

{



var $this = this;



$("#foo").click( this.clicked );



this.clicked = function()

{

$this.alert( $(this).text() );

};



this.alert = function(message)

{

alert(message);

};



};







Unfortunately I can't figure out for the life of me how in CoffeeScript I access the class pointer, "this" is obviously not context aware and will often just point to the variable passed by the callee. So there's no way for me to write the above script in CoffeeScript.





Any advice? I can't find anything useful in the documentation, you have the @ pointers but they also just use the "this" pointer from the current context, making it useless..


Comments

  1. You can add methods directly to @ in the constructor to achieve the same effect:

    class C
    constructor: ->
    $this = @
    @clicked = ->
    console.log @
    $this.alert 'pancakes'
    alert: (m) ->
    console.log m

    c = new C
    c.clicked()
    c.clicked.call window​​​​​


    Demo: http://jsfiddle.net/ambiguous/Y8ZBe/

    You'd usually be able to use a bound method and an "event" argument in situations like this though:

    class C
    clicked: (ev) =>
    @alert(ev.target.value)
    alert: (m) ->
    console.log m

    c = new C
    c.clicked(target: { value: 'pancakes' })
    c.clicked.call window, target: { value: 'pancakes' }


    This sort of thing usually turns up in jQuery (or similar) callbacks and they usually have an event argument which explicitly identifies the target "this" so that you can use bound functions.

    Demo: http://jsfiddle.net/ambiguous/LafV2/

    ReplyDelete
  2. CoffeeScript is still javascript. The limitations of this still apply. You can obviously write a straight translation:

    foo = ->
    self = this
    @clicked = ->
    self.alert $(this).text()
    @alert = (message) ->
    alert message
    $('#foo').click @clicked


    Yet you should be using prototypes (even in javascript). With the fat arrow => you can bind the function to it's current context (but then you lose the element reference):

    foo = ->
    $('#foo').click (e) =>
    @clicked(e.target)

    foo::clicked = (el) ->
    @alert $(el).text()

    foo::alert = (message) ->
    alert message


    Or using the class abstraction (nothing more than prototype usage wrapped up in a prettier package) and jQuery.proxy:

    class Foo
    constructor: ->
    $('#foo').click $.proxy @clicked, this
    clicked: (e) ->
    @alert $(e.target).text()
    alert: (message) ->
    alert message


    $.proxy @clicked, this could be replaced with @clicked.bind @ on modern browsers/engines (see Function.prototype.bind).

    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