Comments for The next 10,000 hours http://www.trouble.net.au/blog/korny Korny's tech blog Thu, 08 Apr 2010 00:34:10 +0000 http://wordpress.org/?v=2.9.2 hourly 1 Comment on Simple ruby wrapper for Delcom build lights on Linux by korny http://www.trouble.net.au/blog/korny/2010/02/12/simple-ruby-wrapper-for-delcom-build-lights-on-linux/comment-page-1/#comment-35 korny Thu, 08 Apr 2010 00:34:10 +0000 http://www.trouble.net.au/blog/korny/?p=138#comment-35 Just a note - if using a recent Delcom light, you should check out the ruby driver at http://github.com/ileitch/delcom_904008_driver - apparently the linux kernel doesn't support new lights (yet!) Just a note – if using a recent Delcom light, you should check out the ruby driver at http://github.com/ileitch/delcom_904008_driver – apparently the linux kernel doesn’t support new lights (yet!)

]]> Comment on Playing with CoffeeScript by jashkenas http://www.trouble.net.au/blog/korny/2010/02/25/playing-with-coffeescript/comment-page-1/#comment-34 jashkenas Fri, 26 Feb 2010 20:04:20 +0000 http://www.trouble.net.au/blog/korny/?p=148#comment-34 Right -- when you pass the "app.init" function into jQuery (binding it to document.ready), you're pulling the function off of the "app" object, and it loses its sense of "this". So, another way to go is to keep your single init, and replace the final line with this: $(-> app.init()) Right — when you pass the “app.init” function into jQuery (binding it to document.ready), you’re pulling the function off of the “app” object, and it loses its sense of “this”. So, another way to go is to keep your single init, and replace the final line with this:

$(-> app.init())

]]> Comment on Playing with CoffeeScript by korny http://www.trouble.net.au/blog/korny/2010/02/25/playing-with-coffeescript/comment-page-1/#comment-33 korny Fri, 26 Feb 2010 00:06:39 +0000 http://www.trouble.net.au/blog/korny/?p=148#comment-33 In fact, I can clean everything up by putting in a second init, and then I can use '@' (which is an alias for 'this.' <code> app: { init: -> app.__init() __init: @paper: Raphael('playspace',320,200) @draw_circle() @draw_square() </code> Nice! In fact, I can clean everything up by putting in a second init, and then I can use ‘@’ (which is an alias for ‘this.’

app: {
init: -> app.__init()
__init:
@paper: Raphael('playspace',320,200)
@draw_circle()
@draw_square()

Nice!

]]> Comment on Playing with CoffeeScript by korny http://www.trouble.net.au/blog/korny/2010/02/25/playing-with-coffeescript/comment-page-1/#comment-32 korny Fri, 26 Feb 2010 00:02:20 +0000 http://www.trouble.net.au/blog/korny/?p=148#comment-32 Thanks - that works! I'm still confused around how 'this' works - it's not really a Coffeescript thing, more of a Javascript thing. For example, in my code above, I can change references in 'app.draw_circle' to use 'this' and they get 'app'. Which makes sense, as they are called as 'app.draw_circle()' But I can't change references in 'app.init' to use 'this', for some reason the JQuery call '$(app.init)' doesn't set 'this' to 'app'... I think that's where a lot of my confusion started, as I'd change something in 'draw_circle' and it would work, then I'd change it in 'init' and it wouldn't! Thanks – that works!
I’m still confused around how ‘this’ works – it’s not really a Coffeescript thing, more of a Javascript thing.
For example, in my code above, I can change references in ‘app.draw_circle’ to use ‘this’ and they get ‘app’. Which makes sense, as they are called as ‘app.draw_circle()’
But I can’t change references in ‘app.init’ to use ‘this’, for some reason the JQuery call ‘$(app.init)’ doesn’t set ‘this’ to ‘app’… I think that’s where a lot of my confusion started, as I’d change something in ‘draw_circle’ and it would work, then I’d change it in ‘init’ and it wouldn’t!

]]> Comment on Playing with CoffeeScript by jashkenas http://www.trouble.net.au/blog/korny/2010/02/25/playing-with-coffeescript/comment-page-1/#comment-31 jashkenas Thu, 25 Feb 2010 12:59:29 +0000 http://www.trouble.net.au/blog/korny/?p=148#comment-31 Nice writeup. It's very cool to see an example of using Raphael from CoffeeScript. The problem that you had with "this" is one of my least favorite parts of JavaScript. Unlike everything else in JS (which has proper lexical scope), the value of "this" within a function is the object that the function has been attached to. The benefit is that you can pull a function off one object and attach it to another, and it'll work seamlessly. The downside is that if you pull a function off an object, say, to hand it to a click handler, it loses its notion of identity and it's former value for "this". The common way to address it is to set a local variable to "this" from the outside, and reference it through the closure, instead of "this". So, your original: $(circle.node).click (e) -> this.kick e Becomes: me: this $(circle.node).click (e) -> me.kick e Which will work properly. However, CoffeeScript provides a convenience for defining functions that are bound to the current value of "this", right on the spot where they're declared, for use in cases like these. http://jashkenas.github.com/coffee-script/#fat_arrow Using the fat arrow, the example becomes: $(circle.node).click (e) => this.kick e Hope that helps. Nice writeup. It’s very cool to see an example of using Raphael from CoffeeScript.

The problem that you had with “this” is one of my least favorite parts of JavaScript. Unlike everything else in JS (which has proper lexical scope), the value of “this” within a function is the object that the function has been attached to.

The benefit is that you can pull a function off one object and attach it to another, and it’ll work seamlessly. The downside is that if you pull a function off an object, say, to hand it to a click handler, it loses its notion of identity and it’s former value for “this”.

The common way to address it is to set a local variable to “this” from the outside, and reference it through the closure, instead of “this”. So, your original:

$(circle.node).click (e) -> this.kick e

Becomes:

me: this
$(circle.node).click (e) -> me.kick e

Which will work properly. However, CoffeeScript provides a convenience for defining functions that are bound to the current value of “this”, right on the spot where they’re declared, for use in cases like these.

http://jashkenas.github.com/coffee-script/#fat_arrow

Using the fat arrow, the example becomes:

$(circle.node).click (e) => this.kick e

Hope that helps.

]]> Comment on Behaviour Driven Development with Cucumber and Selenium by mat kelcey http://www.trouble.net.au/blog/korny/2009/11/03/behaviour-driven-development-with-cucumber-and-selenium/comment-page-1/#comment-27 mat kelcey Tue, 03 Nov 2009 10:38:23 +0000 http://www.trouble.net.au/blog/korny/?p=102#comment-27 good stuff korny, i'm definitely lacking in the cucumber knowledge good stuff korny, i’m definitely lacking in the cucumber knowledge

]]> Comment on Refactoring my blogs by korny http://www.trouble.net.au/blog/korny/2009/10/04/refactoring-my-blogs/comment-page-1/#comment-19 korny Sun, 04 Oct 2009 11:46:25 +0000 http://www.trouble.net.au/blog/korny/2009/10/04/refactoring-my-blogs/#comment-19 hmm - this theme doesn't do bullet points very well. Might have to fiddle with this further tomorrow... hmm – this theme doesn’t do bullet points very well. Might have to fiddle with this further tomorrow…

]]> Comment on Faking DNS with Ruby and Sinatra by Korny http://www.trouble.net.au/blog/korny/2008/03/07/faking-dns-with-ruby-and-sinatra/comment-page-1/#comment-18 Korny Fri, 07 Mar 2008 05:41:38 +0000 http://blog.sietsma.com/2008/03/07/faking-dns-with-ruby-and-sinatra/#comment-18 oops, looks like wordpress didn't like my inline html in the code. I might need to make these files into attachments... oops, looks like wordpress didn’t like my inline html in the code. I might need to make these files into attachments…

]]> Comment on Mobile blogging still needs work, also Pythons on a Phone! by Korny http://www.trouble.net.au/blog/korny/2007/06/14/mobile-blogging-still-needs-work-also-pythons-on-a-phone/comment-page-1/#comment-3 Korny Wed, 20 Jun 2007 01:34:24 +0000 https://www.trouble.net.au/blog/korny/2007/06/14/mobile-blogging-still-needs-work-also-pythons-on-a-phone/#comment-3 Hmm - I'm actually thinking of giving up on Trouble - the way the web is moving, it's less pain to have a blog on a big hosting service than on a friend's machine... sorry Thorne! Hmm – I’m actually thinking of giving up on Trouble – the way the web is moving, it’s less pain to have a blog on a big hosting service than on a friend’s machine… sorry Thorne!

]]> Comment on Mobile blogging still needs work, also Pythons on a Phone! by Jennie http://www.trouble.net.au/blog/korny/2007/06/14/mobile-blogging-still-needs-work-also-pythons-on-a-phone/comment-page-1/#comment-2 Jennie Thu, 14 Jun 2007 12:19:06 +0000 https://www.trouble.net.au/blog/korny/2007/06/14/mobile-blogging-still-needs-work-also-pythons-on-a-phone/#comment-2 you can email your post to a special email address to flickr and it will post it to your blog automatically. I think you set it up under accounts/blogging. you can even set default post settings, code and image handling. it's pretty kewl. you can email your post to a special email address to flickr and it will post it to your blog automatically. I think you set it up under accounts/blogging. you can even set default post settings, code and image handling. it’s pretty kewl.

]]>