<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>jquery on TBNL</title>
    <link>https://www.tibobeijen.nl/tags/jquery/</link>
    <description>Recent content in jquery on TBNL</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Mar 2011 11:32:39 +0000</lastBuildDate>
    
	<atom:link href="https://www.tibobeijen.nl/tags/jquery/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Usability: Autofocus and not breaking the backspace-button</title>
      <link>https://www.tibobeijen.nl/blog/2011/03/14/usability-autofocus-and-not-breaking-the-backspace-button/</link>
      <pubDate>Mon, 14 Mar 2011 11:32:39 +0000</pubDate>
      
      <guid>https://www.tibobeijen.nl/blog/2011/03/14/usability-autofocus-and-not-breaking-the-backspace-button/</guid>
      <description>A while ago during a project we were asked to implement autofocus on the generic search field that every page in the application has. At a first glance a pretty straightforward task, from a technical perspective that is. Not from a user perspective, as indicated by a colleague mentioning his dislike of such autofocus fields “because they prevent backspace going to the previous page”. In this post I will outline some usability considerations and conclude with a jQuery plugin that will take away some of the possible hindrance of autofocusing a field.</description>
    </item>
    
    <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>
    
    <item>
      <title>Jumping in and out of jQuery land</title>
      <link>https://www.tibobeijen.nl/blog/2009/04/02/jumping-in-and-out-of-jquery-land/</link>
      <pubDate>Thu, 02 Apr 2009 21:34:59 +0000</pubDate>
      
      <guid>https://www.tibobeijen.nl/blog/2009/04/02/jumping-in-and-out-of-jquery-land/</guid>
      <description>Recently I started using jQuery in some projects. In past projects I have mainly been using Prototype and the fact that jQuery also has a $() function made me feel at home right away. That same fact put me a bit off-guard as both functions are in fact quite different:
 Prototype extends the selected HTML node with added functionality and returns it. Argument should be a HTML node or element id.</description>
    </item>
    
    <item>
      <title>Fronteers: Meeting march 10th</title>
      <link>https://www.tibobeijen.nl/blog/2009/03/15/fronteers-meeting-march-10th/</link>
      <pubDate>Sun, 15 Mar 2009 10:04:20 +0000</pubDate>
      
      <guid>https://www.tibobeijen.nl/blog/2009/03/15/fronteers-meeting-march-10th/</guid>
      <description>At the PHPgg Frontend Special I first heard of Fronteers, an association of dutch front-end developers. Past tuesday they had a meeting at Media College in Amsterdam. As meetings are open for non(yet)-members it was a nice opportunity to get to know more about Fronteers. Two topics were scheduled: jQuery and SUAVE.
jQuery Until now I have mainly used the Prototype framework for Javascript projects. As the prototype library, escpecially when bundled with scriptaculous, is quite ‘big’ I was interested in hearing some more about the ‘lean and mean’ jQuery.</description>
    </item>
    
  </channel>
</rss>