<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>closure on TBNL</title>
    <link>https://www.tibobeijen.nl/tags/closure/</link>
    <description>Recent content in closure on TBNL</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 27 Jul 2009 13:52:44 +0000</lastBuildDate>
    
	<atom:link href="https://www.tibobeijen.nl/tags/closure/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Taming the Javascript event scope: Closures</title>
      <link>https://www.tibobeijen.nl/blog/2009/07/27/taming-the-javascript-event-scope-closures/</link>
      <pubDate>Mon, 27 Jul 2009 13:52:44 +0000</pubDate>
      
      <guid>https://www.tibobeijen.nl/blog/2009/07/27/taming-the-javascript-event-scope-closures/</guid>
      <description>&lt;p&gt;When doing client-side developing there are times that jQuery’s get-this-do-that nature doesn’t provide all that is needed. For more complex applications I usually find myself creating javascript objects that ‘control’ a specific part of the page’s interaction. In the objects the application’s state is tracked, references to other objects (could be relevant DOM nodes) are stored and event handlers are set.&lt;/p&gt;
&lt;p&gt;One of the problems typically encountered when dealing with javascript event handlers is that they have their own take on the ‘this’ keyword. Closures to the rescue.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>