a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"


";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:65:"
	
	
	
	
	
	
	
	
	
		
		
		
		
		
		
		
		
		
		
		
		
		
		
		
	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:8:"MooTools";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:24:"http://mootools.net/blog";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8:"The Blog";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Dec 2011 21:30:16 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:2:"en";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:29:"http://wordpress.org/?v=3.0.1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:15:{i:0;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"MooTools 1.4.2 Released";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/45J-BZc5yB0/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:69:"http://mootools.net/blog/2011/12/02/mootools-1-4-2-released/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Dec 2011 21:03:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1508";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:354:"Today we release MooTools Core 1.4.2 which is a small maintenance release. Upgrading from 1.4.1 should not cause any backward incompatibilities. We recommend all users upgrade to 1.4.2 as soon as possible. Fixes #2073: Reduced redundant call to onTimeout if async option is true. #2083: Fixes Element.clone in IE. #2085: All specs are green across. [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"ibolmo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3841:"<p>Today we release MooTools Core 1.4.2 which is a small maintenance release. Upgrading from 1.4.1 should not cause any backward incompatibilities. We recommend all users upgrade to 1.4.2 as soon as possible.</p>

<h3>Fixes</h3>

<ul>
<li><a href="https://github.com/mootools/mootools-core/issues/2073">#2073</a>: Reduced redundant call to <code>onTimeout</code> if <code>async</code> option is <code>true</code>.</li>
<li><a href="https://github.com/mootools/mootools-core/pull/2083">#2083</a>: Fixes <code>Element.clone</code> in IE. </li>
<li><a href="https://github.com/mootools/mootools-core/issues/2085">#2085</a>: All specs are green across.</li>
<li><a href="https://github.com/mootools/mootools-core/issues/2100">#2110</a>: <code>Element.erase('class')</code> did not clear the class.</li>
<li><a href="https://github.com/mootools/mootools-core/issues/2113">#2113</a>: <code>button.set('type', 'button')</code> is now fixed for <a href="https://bugs.webkit.org/show_bug.cgi?id=14439">webkit bug</a>.</li>
<li><a href="https://github.com/mootools/mootools-core/issues/2116">#2116</a>: Fixes <code>Element.fade</code> chain.</li>
<li><a href="https://github.com/mootools/mootools-core/issues/2118">#2118</a>: <code>$uid</code> method is no longer exposed</li>
</ul>

<h3>Improvements</h3>

<ul>
<li><a href="https://github.com/mootools/mootools-core/issues/2089">#2089</a>: Added support for native <code>mouseenter</code> and <code>mouseleave</code>. </li>
<li><a href="https://github.com/mootools/mootools-core/issues/2134">#2134</a>: Deprecates the <a href="http://github.com/mootools/mootools-core-specs">MooTools Core Specs</a> repository in favor of including the specs in the Core repo. Due to ease of development.</li>
<li>Series of new specs and refactoring of old specs. Specs are all passing and much faster.</li>
<li><a href="https://github.com/mootools/mootools-core/pull/2138">#2138</a>: Native <code>Element.fireEvent</code> in IE is now accessible in via <code>Element._fireEvent</code>.</li>
</ul>

<h3><a href="https://github.com/mootools/mootools-core/issues?milestone=&amp;page=1&amp;state=open">Known Issues</a></h3>

<ul>
<li>Documentation fixes/additions for <code>Element.NativeEvents</code>, <code>Fx</code>, <code>Request.JSON</code>, and conflicts between <code>Array</code> and <code>Elements</code> methods.</li>
<li><code>Object.each</code> enumeration</li>
<li>Possible leak with <code>Element.adopt</code></li>
<li>IE returns methods for some Element attributes.</li>
<li><code>Element.Delegation</code> problem with non-elements.</li>
</ul>

<p>These issues will be fixed subsequently prior to release of the next maintenance release.</p>

<h3>Get it!</h3>

<ul>
<li><a href="http://mootools.net/download">Download MooTools Core 1.4.2</a>; <a href="http://mootools.net/core/">Build MooTools Core 1.4.2</a></li>
<li>Fork / clone <a href="http://github.com/mootools/mootools-core/tree/1.4.2">MooTools Core 1.4.2 from GitHub</a>, and build it yourself with <a href="http://github.com/kamicane/packager">Packager</a>.</li>
<li><a href="http://code.google.com/apis/ajaxlibs/documentation/index.html#mootools">Google CDN</a> (will be updated soon)</li>
<li><a href="http://mootools.net/docs">Browse the Documentation for Core &amp; More.</a></li>
</ul>

<h3>Contribute</h3>

<p>These fixes and improvements would not have happened if you didn&#8217;t submit an issue (ticket) to the <a href="https://github.com/mootools/mootools-core/issues">MooTools Core Issues</a>, or reporting your problems in the <a href="https://groups.google.com/forum/#!forum/mootools-users">MooTools User Group</a>. Send us your (MooTools) issues (or feature requests) so that your favorite JavaScript framework keeps getting better.</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/45J-BZc5yB0" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:65:"http://mootools.net/blog/2011/12/02/mootools-1-4-2-released/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:60:"http://mootools.net/blog/2011/12/02/mootools-1-4-2-released/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:34:"MooTools Forge - Now with comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/pxKjahfnZoE/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:78:"http://mootools.net/blog/2011/10/18/mootools-forge-now-with-comments/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 18 Oct 2011 22:55:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1493";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:322:"Just a quick update to let you know we&#8217;ve added comments through Disqus to all Forge plugins. If you&#8217;re a plugin owner, you can subscribe by going to your plugin page and clicking &#8216;subscribe by email&#8217; at the bottom. Remember, if you find a bug in a plugin, you should always report it in that [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"fakedarren";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:835:"<p>Just a quick update to let you know we&#8217;ve added comments through Disqus to all Forge plugins.</p>

<p>If you&#8217;re a plugin owner, you can subscribe by going to your plugin page and clicking &#8216;subscribe by email&#8217; at the bottom.</p>

<p>Remember, if you find a bug in a plugin, you should always report it in that repository&#8217;s Github Issues.</p>

<p>As it stands, all comments will need to be moderated before they appear, just to make sure we don&#8217;t get trolled / spammed and we&#8217;re really looking forward to adding the ability to comment to the other parts of the website - particularly in documentation.</p>

<p>Thanks to <a href="https://twitter.com/#!/anutron">Aaron</a> for making this happen!</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/pxKjahfnZoE" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:74:"http://mootools.net/blog/2011/10/18/mootools-forge-now-with-comments/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"4";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:69:"http://mootools.net/blog/2011/10/18/mootools-forge-now-with-comments/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"MooTools Core 1.4.1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/FLi333YUkqU/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:65:"http://mootools.net/blog/2011/10/06/mootools-core-1-4-1/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 06 Oct 2011 19:01:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1484";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:351:"Today we release MooTools Core 1.4.1 which is a small maintenance release and as such only fixes bugs that were introduced in previous releases. We have fixed the mousewheel event in Firefox, Element.fade sets the visibility CSS-property again, Event.Delegation now behaves properly if you use fireEvent and we have fixed a couple of issues with [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"cpojer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1321:"<p>Today we release MooTools Core 1.4.1 which is a small maintenance release and as such only fixes bugs that were introduced in previous releases. We have fixed the <code>mousewheel</code> event in Firefox, <code>Element.fade</code> sets the <code>visibility</code> CSS-property again, Event.Delegation now behaves properly if you use <code>fireEvent</code> and we have fixed a couple of issues with <code>Element.setProperty</code> and <code>Element.removeProperty</code>.</p>

<p>Upgrading from 1.4.0 should not cause any backward incompatibilities. We recommend all users to update to 1.4.1 as soon as possible.</p>

<h3>Get it!</h3>

<ul>
<li><a href="http://mootools.net/download">Download MooTools Core 1.4.1</a>; <a href="http://mootools.net/core/">Build MooTools Core 1.4.1</a></li>
<li>Fork / clone <a href="http://github.com/mootools/mootools-core/tree/1.4.1">MooTools Core 1.4.1 from GitHub</a>, and build it yourself with <a href="http://github.com/kamicane/packager">Packager</a>.</li>
<li><a href="http://code.google.com/apis/ajaxlibs/documentation/index.html#mootools">Google CDN</a> (will be updated soon)</li>
<li><a href="http://mootools.net/docs">Browse the Documentation for Core &amp; More.</a></li>
</ul>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/FLi333YUkqU" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:61:"http://mootools.net/blog/2011/10/06/mootools-core-1-4-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"7";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:56:"http://mootools.net/blog/2011/10/06/mootools-core-1-4-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"MooTools 1.4.0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/XMD5J0lWrdo/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:60:"http://mootools.net/blog/2011/09/10/mootools-1-4-0/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 10 Sep 2011 14:16:16 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1468";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:317:"As of today a new version of MooTools is available. This includes MooTools Core and MooTools More. We&#8217;ve communicated a lot about changes for 2.0 but we also felt we had some good stuff that would benefit you directly which we wanted to add to the 1.x releases. This good stuff contains of course numerous [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"Arian";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:6179:"<p>As of today a new version of MooTools is available. This includes MooTools Core and MooTools More. We&#8217;ve communicated a lot about changes for 2.0 but we also felt we had some good stuff that would benefit you directly which we wanted to add to the 1.x releases. This good stuff contains of course numerous bugfixes but mostly one important new feature for MooTools Core: Delegation. This 1.4 release should be fully <em>backward compatible</em> with the MooTools 1.2 and 1.3 series&#8217;.</p>

<h3>So all changes for 1.4.0:</h3>

<ul>
<li>Move <a href="http://mootools.net/docs/core/Element/Element.Delegation">Delegation</a> into Core.</li>
<li>ECMAScript 5 compatibility fixes. Among them are Function.bind, Array.map and String.trim</li>
<li>Deprecate <code>Element.setOpacity()</code> and <code>Element.set('opacity')</code>. <code>Element.setStyle('opacity')</code> is the only correct way now (the same applies for getters).</li>
<li>Disable the 1.2 compat layer by default in the builder.</li>
<li>Revamp <code>Element.getProperty</code>, <code>Element.setProperty</code>. <code>Element.getProperty</code> uses <code>Slick.getAttribute</code> now to share this code and save some bytes.</li>
<li>IE7 doesn&#8217;t crash anymore when cloning an element twice.</li>
<li>The <a href="http://mootools.net/docs/core/Slick/Slick">Selectors documentation</a> is back and updated for Slick.</li>
<li>Update Slick to 1.1.6</li>
<li>Unified <code>change</code> event behavior across browsers.</li>
<li>Renamed <code>Event</code> to <code>DOMEvent</code> so it will not <a href="http://trac.webkit.org/changeset/93951">conflict</a> with the native <code>Event</code> object.</li>
</ul>

<h3>Event Delegation</h3>

<p>Event delegation is a common practice where an event listener is attached to a parent element to monitor its children rather than attach events to every single child element. It&#8217;s more efficient for dynamic content or highly interactive pages with a lot of DOM elements.</p>

<p><strong>Example</strong></p>

<pre><code>var myElement = $('myElement');
var request = new Request({
    // other options
    onSuccess: function(text){
        myElement.set('html', text); // No need to attach more click events.
    }
});
// Adding the event, notice the :relay syntax with the selector that matches the target element inside of myElement.
// Every click on an anchor-tag inside of myElement executes this function.
myElement.addEvent('click:relay(a)', function(event, target){
    event.preventDefault();
    request.send({
        url: target.get('href')
    });
});
</code></pre>

<h4>MooTools More</h4>

<ul>
<li>Removed Delegation. It&#8217;s now in Core obviously.</li>
<li>Added the <code>length</code> validator to Form.Validator</li>
<li>Added the <code>update</code> method to HtmlTable which let you update rows</li>
<li>Added ARIA accessibility to Tips.</li>
</ul>

<p>If you&#8217;d like to know what exactly changed, checkout the <a href="https://github.com/mootools/mootools-core/compare/1.3.2...1.4.0">compare view</a>.</p>

<p>We would like to thank everybody who has contributed code, documentation fixes and ideas to make this release possible. Among them are <a href="https://github.com/arieh">arieh</a>, <a href="https://github.com/Delapouite">Delapouite</a>, <a href="https://github.com/madisvain">madisvain</a>, <a href="https://github.com/adamnbowen">adamnbowen</a>, <a href="https://github.com/mooyah">mooyah</a>, <a href="https://github.com/GCheung55">GCheung55</a>, <a href="https://github.com/amadeus">amadeus</a>, <a href="https://github.com/rasmusfl0e">rasmusfl0e</a>, <a href="https://github.com/jasonwaters">jasonwaters</a>, <a href="https://github.com/realityking">realityking</a>, <a href="https://github.com/Nico-B">Nico-B</a>, <a href="https://github.com/mcfedr">mcfedr</a>, <a href="https://github.com/donatj">donatj</a>, <a href="https://github.com/csuwldcat">csuwldcat</a>, <a href="https://github.com/ibolmo">ibolmo</a>, <a href="https://github.com/cpojer">cpojer</a>, <a href="https://github.com/kamicane">kamicane</a>, <a href="https://github.com/timwienk">timwienk</a>, <a href="https://github.com/fakedarren">fakedarren</a>, <a href="https://github.com/anutron">anutron</a>, <a href="https://github.com/subtlegradient">subtlegradient</a> and myself <a href="https://github.com/arian">arian</a>.</p>

<h3>Bugs</h3>

<p>Thanks to GitHub <a href="https://github.com/blog/712-pull-requests-2-0">contributing</a> is easier <a href="https://github.com/blog/905-edit-like-an-ace">than ever</a>. It&#8217;s very easy to fix them or to report them, especially since we <a href="http://mootools.net/blog/2011/08/01/moving-to-github-issues/">moved to GitHub</a> for our issues. Bugs can reported on the <a href="https://github.com/mootools/mootools-core/issues">MooTools Core Bug Tracker</a> and for MooTools More you can go to the <a href="https://github.com/mootools/mootools-more/issues">More Bug Tracker</a>.</p>

<p>If you have any questions, either about how to do something or about contributing you can ask, or something to share, just join the <a href="https://groups.google.com/forum/#!forum/mootools-users">MooTools Mailing list</a> or IRC (#mootools on freenode.net). We have an <a href="http://mootools.net/blog/2011/06/09/open-irc-office-hours/">office hour</a> each Tuesday but you can hang out there whenever you want.</p>

<h3>Get it!</h3>

<ul>
<li><a href="http://mootools.net/download">Download MooTools Core 1.4.0</a>; <a href="http://mootools.net/core/">Build MooTools Core 1.4.0</a></li>
<li><a href="http://mootools.net/more/">Build MooTools More 1.4.0.1</a></li>
<li>Fork / clone <a href="http://github.com/mootools/mootools-core/tree/1.4.0">MooTools 1.4.0 from GitHub</a>, and build it yourself with <a href="http://github.com/kamicane/packager">Packager</a>.</li>
<li><a href="http://code.google.com/apis/ajaxlibs/documentation/index.html#mootools">Google CDN</a>  (which should be updated soon)</li>
<li><a href="http://mootools.net/docs">Browse the Documentation for Core &amp; More.</a></li>
</ul>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/XMD5J0lWrdo" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:56:"http://mootools.net/blog/2011/09/10/mootools-1-4-0/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:2:"16";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:51:"http://mootools.net/blog/2011/09/10/mootools-1-4-0/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"Moving to GitHub Issues";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/HSC1Z_A0rYA/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:69:"http://mootools.net/blog/2011/08/01/moving-to-github-issues/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 02 Aug 2011 00:14:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1456";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:317:"We at the MooTools headquarters love GitHub for all its features which makes contributing and managing our code much easier than say, five years ago. GitHub is the place to be for all cool JavaScript projects which makes following your projects of interest a lot easier. When we moved to GitHub a long time ago, [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"Arian";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1853:"<p>We at the MooTools headquarters love GitHub for all its features which makes contributing and managing our code much easier than say, five years ago. GitHub is the place to be for all cool JavaScript projects which makes following your projects of interest a lot easier. When we moved to GitHub a long time ago, the ticket system was too basic to be a real solution. Fortunately this has <a href="https://github.com/blog/831-issues-2-0-the-next-generation">since</a> improved.</p>

<p>Especially the additions for milestones and assignees were important for us. With this in place GitHub issues can finally replace Lighthouse.</p>

<p>The main advantages are:</p>

<ul>
<li>Everything at one place, one login</li>
<li>Easier to follow MooTools</li>
<li>Similar to pull requests</li>
</ul>

<p>A disadvantage is that most of the current issues are in <a href="https://mootools.lighthouseapp.com/projects/2706-mootools/tickets">Lighthouse</a>. Darren did an awesome job going through a lot of them but there are still some open or not fixed. A proposed option was to move all tickets to GithHub, but we decided to try to address as many as we can and just move on to GitHub.</p>

<p>Now every <a href="https://github.com/mootools">MooTools project</a> has its issues on GitHub:</p>

<ul>
<li><a href="https://github.com/mootools/mootools-core/issues">MooTools Core</a></li>
<li><a href="https://github.com/mootools/mootools-more/issues">MooTools More</a></li>
<li><a href="https://github.com/mootools/slick/issues">Slick</a></li>
<li><a href="https://github.com/mootools/mootools-demos/issues">Demos</a></li>
</ul>

<p>So if you know anything about any of the issues at GitHub or some old Tickets at Lighthouse, comments and fixes are highly appreciated!</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/HSC1Z_A0rYA" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:65:"http://mootools.net/blog/2011/08/01/moving-to-github-issues/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:60:"http://mootools.net/blog/2011/08/01/moving-to-github-issues/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:32:"July 12th Dev Hour Recap/Summary";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/CpJLVVNkuIA/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:77:"http://mootools.net/blog/2011/07/19/july-12th-dev-hour-recapsummary/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Jul 2011 14:28:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1442";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:352:"Every week the MooTools developers host an IRC OfficeDeveloper Hour where they work together to listen to your feedback, answer your questions, and develop MooTools. We do this every Tuesday at 11am EST at #mootools Freenode IRC Channel. Everyone’s welcomed to join us. This recap includes: Mentions Answers to: Where do you guys think MooTools [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"ibolmo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:11101:"<p>Every week the MooTools developers host an IRC <del>Office</del>Developer Hour where they work together to listen to your feedback, answer your questions, and develop MooTools. We do this every Tuesday at 11am EST at <a href="irc://irc.freenode.net/mootools">#mootools Freenode IRC Channel</a>. Everyone’s welcomed to join us.</p>

<p>This recap includes:</p>

<ul>
<li>Mentions</li>
<li>Answers to: Where do you guys think MooTools can improve?</li>
<li>Sneak Peak to Improved Docs</li>
<li>Agenda for July 19th Dev Hour</li>
</ul>

<p><span id="more-1442"></span></p>

<h3>Mentions</h3>

<p><a href="http://seanmonstar.com/">Sean McArthur (seanmonstar)</a> is working on a MooTools-based MVC Framework called <a href="https://github.com/seanmonstar/Shipyard">Shipyard</a>. The framework is made for working on the browser, but it can run on <a href="http://nodejs.org">Node.JS</a>. He’s been testing Shipyard and we mentioned that he should try the <a href="https://github.com/mootools/mootools-runner">mootools-runner</a> which runs the specs for Core and More. The Runner can be run via the browser, node.js, or CLI (via <a href="http://code.google.com/p/js-test-driver/">JsTestDriver</a>). It’s lightning fast and easy to contribute to. All specs are written in <a href="http://github.com/pivotal/jasmine">Jasmine</a> and mocked by <a href="https://github.com/cjohansen/Sinon.JS">Sinon.JS</a>.</p>

<p>Another user talked to us that he’s in high school in Colorado, and that he’s trying to convert his church to use MooTools instead of jQuery. We recommended that he should try to ween the church off of jQuery by using Ryan Florence’s <a href="https://github.com/rpflorence/moo4q">moo4q</a>, a helper to bring Object Oriented programming to jQuery.</p>

<p>Another user had asked if anyone had worked on HTML5’s pushState, and we’ve pointed him to MooTools’ own Christoph Pojer’s <a href="http://cpojer.net/PowerTools/#!">PowerTools</a>. In particular, if you’re looking for a history plugin I highly recommend <a href="https://github.com/cpojer/mootools-history">mootools-history</a>.</p>

<h3>Questionaire</h3>

<p>Last week we asked the channel: <strong>Where do you guys think MooTools can improve?</strong> We’re always glad to hear from our users and here are a few notable mentions from last week’s questionaire.</p>

<p><strong>Lighter weight</strong>: <code>alpha123</code> had mentioned that there are some utility methods that he never uses and could go. Likewise, <code>xandros</code> pointed out that between 1.2 and 1.3 the same build with specific dependencies had grown in size. I couldn’t agree more. We’ve always been careful with the size of your builds by giving you the power to build the smallest build possible with the <a href="http://mootools.net/core/">online web builder</a> or with <a href="https://github.com/kamicane/packager">Packager</a>. Undoubtedly the 1.y.x branch has grown in size due to maturity and contributions from the team and our users. I’d like to personally try to arrange a “Dependency Cops” team that tries to monitor and reduce the baggage in some of the dependencies. We’d like for you to help us, though. In spare time (if any) read the source code and try to find sections of code that can be moved or refactored into its own file. This way we can reduce the bytes in the dependency chain. Send us a pull request.</p>

<p><strong>Marketing and Evangelism</strong>: <code>jazzman</code> had mentioned that MooTools marketing and evangelism could definitely improve. Historically, MooTools core developers have shied away from marketing MooTools as a product. We’ve done this to reduce distractions and instead we’d focus strictly on the code. (If you build it, they will come.) I think that as a team we’re shifting our beliefs towards being more vocal and open about our philosophies and code. We love MooTools and think that others would be surprised with MooTools and how easy our principles help to code better. Not just for MooTools, but JavaScript. And so, we are warming up to the idea to be proactive with spreading the Moo. And so should you. Just be courteous and qualitative. MooTools is not infallible and it’s not always the best <strong>tool</strong> for the job. We need responsible and honest people whose interests lies in improving code, coming to a solution, and moving forward.</p>

<p><strong>More UI Goodness</strong>: UI components have been around since the beginning of MooTools (see: Accordion madness). We understand that many of you are looking for the team to build a UI framework, and we’d like to serve your needs. At the moment, however, we have bigger fish to fry (MooTools 2.0). Instead, please see this blog post for some mentions of <a href="http://mootools.net/blog/2011/06/27/june-21st-office-hour-recapsummary/">UI libraries</a> that are built on top of MooTools, or to use other libraries/frameworks (we’re all friends here). If you’re interested in championing this cause, then the best way to get an official (sanctioned) MooTools repo is to: do it™ and to keep us in the loop (ask us to review your commits).</p>

<p><strong>More sourced content</strong>: We’d like to work on more screencasts, slideshows, presentations, demonstrations and other content that would help you understand MooTools as well as show it off to your friends, nemesis, or colleagues. We understand that it’s hard to convince your team members or employer to adopt MooTools. We are working to improve this area, but we need your help. Leave us a comment on how we can help you understand or overcome hurdles when speaking with people. I’ve had a few ideas: providing you with introduction presentations that you can give to your peers, for example.</p>

<p>Any other areas that you think we need to improve?</p>

<h3>Sneak Peak to Improved Docs</h3>

<p><a href="http://mootools.net/developers">Darren Waddell</a> has been working on your suggestions from past <a href="http://mootools.net/blog/2011/06/27/june-21st-office-hour-recapsummary/">Office (Dev) Hours</a>. In this sneak preview: each method has its own page and its own comment section (ala PHP). We’ve only shared this sneak peak with a few people and we’re already <a href="http://mootools.net/docs/core/Element/Element/Element:constructor#comment-253004492">seeing contribution</a>. To see the improved docs you’ll have to create a new cookie <code>newdocs</code>. Confused? Here’s the instructions on how to use the new docs:</p>

<ol>
<li>Go to the <a href=”http://mootools.net/docs/core” target=”_new”>Core Docs</a>.</li>
<li>Copy and paste this: <code>javascript:Cookie.write('newdocs', true, {path: '/'})</code> into your address bar (or into a console).</li>
<li>Refresh the page.</li>
</ol>

<p>If you did the above correctly, you should see that the <a href="http://mootools.net/docs/core/Element/Element">Element</a> Docs have been split into individual pages.</p>

<p>Darren has done a great job so far. If you’d like to help please leave your suggestions or <strong>fork</strong> the <a href="https://github.com/fakedarren/mootools-docs">mootools-docs</a> repository.</p>

<h3>Agenda for July 19th Dev Hour</h3>

<ul>
<li><strong>Features and Roadmap of 1.4.0</strong>. Believe it or not, we’re still working on the release of 1.4.x. Word has it that <strong>Delegation</strong> will finally move to Core. Plus a bunch of bug fixes.</li>
<li><strong>Improved Docs Feedback and Work</strong>.  We’d like for you to join us to talk about the improvements that we’re making on the documentation.</li>
<li><strong>Bug Hunting in <a href="https://mootools.lighthouseapp.com/dashboard">Lighthouse Tickets</a> and <a href="https://github.com/mootools/mootools-core/issues">Github Issues</a></strong>. To release 1.4 we’re going to need to fix a lot of bugs and to have our users report any issues. Please report your issues to Github, as Lighthouse is now deprecated (blog post coming soon).</li>
<li><strong>Open Forum</strong>. As always, we’d love to meet you and talk about all things Moo. </li>
</ul>

<h3>Next Office Hour</h3>

<p>Remember that we’re having the next office hour this:</p>

<h4>Tuesday, July 19th at</h4>

<p>05:01 - <strong>Honolulu</strong> (Hast UTC-10)<br />
08:01 - <strong>San Francisco</strong> (PDT UTC-7)<br />
10:01 - <strong>Chicago</strong> (CDT UTC-5)<br />
11:01 - <strong>New York</strong> (EDT UTC-4)<br />
12:01 - <strong>Rio de Janeiro</strong> (BRT UTC-3)<br />
16:01 - <strong>London</strong> (BST UTC+1)<br />
17:01 - <strong>Vienna</strong> (CEST UTC+2)<br />
18:01 - <strong>Kyiv</strong> (EEST UTC+3)<br />
20:31 - <strong>Mumbai</strong> (IST UTC+5:30)<br />
23:01 - <strong>Hong Kong</strong> (HKT UTC+8)<br />
00:01 - <strong>Tokyo</strong> (JST UTC+9)<br />
01:01 - <strong>Sydney</strong> (EST UTC+10)<br />
03:01 - <strong>Auckland</strong> (NZST UTC+12)</p>

<p>We&#8217;ll be in the <a href="irc://irc.freenode.net/mootools">#mootools</a> freenode.net channel.</p>

<h3>Guidelines</h3>

<p>We did very well last week in following the guidelines. I’ve included them in this post as a reminder.</p>

<ol>
<li><strong>Please use <a href="http://jsfiddle.net">jsfiddle.net</a></strong> and keep your code with minimal boilerplate &#8212; get to the essence of your question</li>
<li><strong>Stay on topic.</strong> Let&#8217;s keep the chat around MooTools and how it interacts with your code and the rest of the JavaScript ecosystem.</li>
<li><strong>Be courteous and helpful with others.</strong> We are not guaranteeing that all of us will give you our undivided attention during the hour (we are also working!). If you can answer a question (as best as you can) it will really be helpful.</li>
<li>Sharing is caring. Share the room, but also share the event. Post to twitter, Facebook, your blog, and tell your parents. We want to foster growth in our community. This is the chance to participate and to help.</li>
</ol>

<h3>Tips</h3>

<p>Use this button to add the open office hour to your Google Calendar. <strong>You’ll need to setup the event so that it repeats weekly.</strong><br />
<a href="http://www.google.com/calendar/event?action=TEMPLATE&#038;text=MooTools%20IRC%20Office%20Hours&#038;dates=20110719T150000Z/20110719T160000Z&#038;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&#038;location=%23motools%20on%20irc.freenode.net&#038;trp=true&#038;sprop=http%3A%2F%2Fmootools.net%2F&#038;sprop=name:MooTools" target="_blank"><img src="http://www.google.com/calendar/images/ext/gc_button6.gif" border=0></a>
<br style="clear: both" />
If you don’t have an IRC client you can use <a href="http://webchat.freenode.net/">http://webchat.freenode.net/</a>.</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/CpJLVVNkuIA" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:73:"http://mootools.net/blog/2011/07/19/july-12th-dev-hour-recapsummary/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"6";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:68:"http://mootools.net/blog/2011/07/19/july-12th-dev-hour-recapsummary/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:38:"July 5th IRC Office Hour Recap/Summary";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/7jAPQ674i3Y/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:83:"http://mootools.net/blog/2011/07/11/july-5th-irc-office-hour-recapsummary/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Jul 2011 19:11:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1432";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:350:"Every week the MooTools developers have an IRC office hour meeting where they work together to listen to your feedback, answer your questions, and develop on MooTools. We do this every Tuesday at 11am EST at #mootools Freenode IRC Channel. Everyone’s welcome so join us tomorrow. This recap includes: Compare 1.3.x and Experimental 2.y.x Code [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"ibolmo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:7806:"<p>Every week the MooTools developers have an IRC office hour meeting where they work together to listen to your feedback, answer your questions, and develop on MooTools. We do this every Tuesday at 11am EST at <a href="irc://irc.freenode.net/mootools">#mootools Freenode IRC Channel</a>. Everyone’s welcome so join us tomorrow.</p>

<p>This recap includes:</p>

<ul>
<li>Compare 1.3.x and Experimental 2.y.x Code Diffs</li>
<li>Things to Come (Agenda’ed Office Hour, Dedicated “Hackathon” Office Hours)</li>
</ul>

<p><span id="more-1432"></span></p>

<p>Last week we had a small conversation of the <a href="http://github.com/kamicane/mootools-core/tree/define-2">experimental branch that Valerio has for MooTools 2.0</a>. The conversation covered most of the comments in <a href="http://mootools.net/blog/2011/07/04/june-28th-irc-office-hour-recapsummary/#comments">last week’s post comments</a>. Instead of going over them again, please take a look at last week’s post.</p>

<h3>Compare 1.3.x and Experimental 2.y.x Code Diffs</h3>

<p>Like I had promised last week, I did want to start a repository for helping you understand what are the main differences (in code) between 1.3.x and the experimental 2.y.x. Last week the <a href="https://github.com/ibolmo/mootools-1-vs-2">mootools-1-vs-2 repository</a> to do just that. You can use Github’s <strong>awesome</strong> Compare View to <a href="https://github.com/ibolmo/mootools-1-vs-2/compare/1.3.x...2.y.x">view the differences between 1.3.x and 2.y.x</a> (Valerio’s experimental branch).</p>

<p>The files included in the repo are meant to compare Core code, Plugin code, and Application code:</p>

<p><strong>Core Code</strong></p>

<ul>
<li><strong>Request.js</strong> is from the MooTools <a href="https://github.com/mootools/mootools-core/blob/master/Source/Request/Request.js">Core/Request</a>.</li>
</ul>

<p><strong>Plugin Code</strong></p>

<ul>
<li><p><strong>Database.js</strong> (by <a href="http://github.com/csuwldcat">Daniel Buchner</a>). You can find the original Database.js in the repo as well as in his <a href="https://github.com/csuwldcat/mootools-htmlx">csuwldcat/mootools-htmlx</a>.</p></li>
<li><p><strong>ScrollSpy.js</strong> (by <a href="https://github.com/darkwing">David Walsh</a>). You can find the original ScrollSpy.js in the <a href="http://mootools.net/forge/p/scrollspy">MooTools Forge</a>.</p></li>
</ul>

<p><strong>Application Code</strong></p>

<ul>
<li><strong>Examples/001.js</strong> and <strong>Examples/002.js</strong> are examples from the <a href="http://mootools.net/docs/core/Request/Request">Request.js</a> documentation. </li>
</ul>

<h4>Caveats</h4>

<p><strong>The examples are not all encompassing of user behavior and usage.</strong> I did select the scripts, but I tried to be fair. You can fork the repository and add your files to the <a href="https://github.com/ibolmo/mootools-1-vs-2">1.3.x branch</a> (the base branch) and send me a <a href="https://github.com/ibolmo/mootools-1-vs-2/pulls">pull request</a> and I’ll try to port your code. Please be considerate, and send me at most one file with recommended maximum of 500 lines.</p>

<p><strong>The code will change as 2.0 is further defined</strong>. The 2.0 API is not final. Valerio is kicking butt everyday on his experimental branch. This compare 1.3.x vs. 2.y.x repo. is meant to assuage some of the concerns from the <a href="http://mootools.net/blog/2011/07/04/june-28th-irc-office-hour-recapsummary/">previous blog post</a> about Valerio’s experimental 2.0 branch.</p>

<p><strong>This repo is not a definitive guide to 2.0</strong>. We’re still working on that definitive guide for 2.0, but since the API is not strictly defined it’s premature to give you this. For now, leave your comments or join us tomorrow with your questions.</p>

<p><strong>The repo doesn’t show <code>Host.Install</code></strong>. The intention of the repo. is to show the default behavior of 2.0. I’m likely to create another branch and call it <code>2.y.x-installed</code> so that you’ll see the differences between 1.3.x and 2.0.x with native extensions installed.</p>

<h3>Things to Come.</h3>

<h4>Agenda for the Office Hours</h4>

<p>We were asked that Office Hours should have an agenda so that we can have a more directed conversation. I didn’t have a chance to inquire the team for items, but we should have some items for next week.</p>

<p>Any suggestions? Leave a comment below.</p>

<h4>Mini Hackathons or “Dedicated” Office Hours</h4>

<p>Similar to the above, it’s been suggested by <a href="http://github.com/fakedarren">Darren Wadell</a> and <a href="http://github.com/arian">Arian Stolwijk</a> that we could dedicated actionable work hours. We could have demos office hour, documentation, bugfix or test office hours for example.</p>

<p>What do you think? Would you participate?</p>

<h3>Next Office Hour</h3>

<p>Remember that we’re having the next office hour this:</p>

<h4>Tuesday, July 12th at</h4>

<p>05:01 - <strong>Honolulu</strong> (Hast UTC-10)<br />
08:01 - <strong>San Francisco</strong> (PDT UTC-7)<br />
10:01 - <strong>Chicago</strong> (CDT UTC-5)<br />
11:01 - <strong>New York</strong> (EDT UTC-4)<br />
12:01 - <strong>Rio de Janeiro</strong> (BRT UTC-3)<br />
16:01 - <strong>London</strong> (BST UTC+1)<br />
17:01 - <strong>Vienna</strong> (CEST UTC+2)<br />
20:31 - <strong>Mumbai</strong> (IST UTC+5:30)<br />
23:01 - <strong>Hong Kong</strong> (HKT UTC+8)<br />
00:01 - <strong>Tokyo</strong> (JST UTC+9)<br />
01:01 - <strong>Sydney</strong> (EST UTC+10)<br />
03:01 - <strong>Auckland</strong> (NZST UTC+12)</p>

<p>We&#8217;ll be in the <a href="irc://irc.freenode.net/mootools">#mootools</a> freenode.net channel.</p>

<h3>Guidelines</h3>

<p>We did very well last week in following the guidelines. I’ve included them in this post as a reminder.</p>

<ol>
<li><strong>Please use <a href="http://jsfiddle.net">jsfiddle.net</a></strong> and keep your code with minimal boilerplate &#8212; get to the essence of your question</li>
<li><strong>Stay on topic.</strong> Let&#8217;s keep the chat around MooTools and how it interacts with your code and the rest of the JavaScript ecosystem.</li>
<li><strong>Be courteous and helpful with others.</strong> We are not guaranteeing that all of us will give you our undivided attention during the hour (we are also working!). If you can answer a question (as best as you can) it will really be helpful.</li>
<li>Sharing is caring. Share the room, but also share the event. Post to twitter, Facebook, your blog, and tell your parents. We want to foster growth in our community. This is the chance to participate and to help.</li>
</ol>

<h3>Tips</h3>

<p>Use this button to add the open office hour to your Google Calendar. <strong>You’ll need to setup the event so that it repeats weekly.</strong><br />
<a href="http://www.google.com/calendar/event?action=TEMPLATE&#038;text=MooTools%20IRC%20Office%20Hours&#038;dates=20110712T150000Z/20110712T160000Z&#038;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&#038;location=%23motools%20on%20irc.freenode.net&#038;trp=true&#038;sprop=http%3A%2F%2Fmootools.net%2F&#038;sprop=name:MooTools" target="_blank"><img src="http://www.google.com/calendar/images/ext/gc_button6.gif" border=0></a>
<br style="clear: both" />
If you don’t have an IRC client you can use <a href="http://webchat.freenode.net/">http://webchat.freenode.net/</a>.</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/7jAPQ674i3Y" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:79:"http://mootools.net/blog/2011/07/11/july-5th-irc-office-hour-recapsummary/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"3";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:74:"http://mootools.net/blog/2011/07/11/july-5th-irc-office-hour-recapsummary/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:44:"
		
		
		
		
		
				
		

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:39:"June 28th IRC Office Hour Recap/Summary";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/wbN66Jr6Jag/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:84:"http://mootools.net/blog/2011/07/04/june-28th-irc-office-hour-recapsummary/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 05 Jul 2011 01:37:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:6:"Events";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1424";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:340:"Every week the MooTools developers have an IRC office hour meeting where they work together to listen to your feedback, answer your questions, and develop on MooTools. We do this every Tuesday at 11am EST at #mootools Freenode IRC Channel. Everyone’s welcome so join us tomorrow. Recap Last week’s office hour was dominated by the [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"ibolmo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:6398:"<p>Every week the MooTools developers have an IRC office hour meeting where they work together to listen to your feedback, answer your questions, and develop on MooTools. We do this every Tuesday at 11am EST at <a href="irc://irc.freenode.net/mootools">#mootools Freenode IRC Channel</a>. Everyone’s welcome so join us tomorrow.</p>

<h3>Recap</h3>

<p><span id="more-1424"></span>
Last week’s office hour was dominated by the experimental <a href="http://github.com/kamicane/mootools-core/tree/define-2">define-2</a> branch by <a href="http://mootools.net/developers">Valerio</a>. This branch has the experimental support of <a href="http://wiki.commonjs.org/wiki/Modules/AsynchronousDefinition">Asynchronous Module Definition (AMD)</a> and also has the proposed direction of MooTools 2.0 as mentioned in the <a href="http://mootools.net/blog/2011/06/27/june-21st-office-hour-recapsummary/">previous blog post</a>.</p>

<p>From the discussion in last week’s office hour, it seemed that there was confusion on the implications of adopting Valerio’s 2.0 branch. In particular there were concerns for: compatibility, native extensions (and minimum ES5 polyfills), chainability, and style.</p>

<p>At first, 2.0 will likely not be compatible with 1.3 without a builder and an upgrade script. Since we’ve yet to cross this road, please be vigilant of the changes and discussion that are underway. As always, rest assured that we would like to make your transition into 2.0 as easy and immediate as possible.</p>

<p>Without a dedicated blog post, I’d like to recap that there is a divide between the community and even the MooTools developers about the possible decision to <strong>not</strong> extend native objects (e.g. Array, Number, String, …) by default. One side of the argument is that this is a 180 degree shift in MooTools style and philosophy and that it ruins competitive differentiation (a <a href="http://www.gobignetwork.com/information/go-big-dictionary/competitive-differentiation-definition">marketing term</a>). On the other side of the argument is that this is necessary to stay <strong>relevant</strong> in the discussion, that we’ve cornered ourselves between a rock and a hard place and that we just need to be better. Valerio had even quoted <a href="http://www.youtube.com/watch?v=3LEXae1j6EY#t=09m20s">Steve Jobs as a perfect explanation</a> on his position.</p>

<p>Instead of going further and making points for either argument, it’d be more appropriate if we make a definitive post on the matter.</p>

<h3>Next Office Hour</h3>

<p>The discussion is still not done. If you’d like to give us your $0.02 on the matter, we welcome your thoughts and concerns. If you’d like to contribute to the <a href="https://docs.google.com/document/d/1tnT5nrPSaNL2GfaaXlN0Q61NjqQoOJddjgsIjqwmhGo/edit?hl=en_US">2.0 Wish List</a>, add your suggestion or talk to us on IRC. Remember that we’re having the next office hour this:</p>

<h4>Tuesday, July 5th at</h4>

<p>05:01 - <strong>Honolulu</strong> (Hast UTC-10)<br />
08:01 - <strong>San Francisco</strong> (PDT UTC-7)<br />
10:01 - <strong>Chicago</strong> (CDT UTC-5)<br />
11:01 - <strong>New York</strong> (EDT UTC-4)<br />
12:01 - <strong>Rio de Janeiro</strong> (BRT UTC-3)<br />
16:01 - <strong>London</strong> (BST UTC+1)<br />
17:01 - <strong>Vienna</strong> (CEST UTC+2)<br />
20:31 - <strong>Mumbai</strong> (IST UTC+5:30)<br />
23:01 - <strong>Hong Kong</strong> (HKT UTC+8)<br />
00:01 - <strong>Tokyo</strong> (JST UTC+9)<br />
01:01 - <strong>Sydney</strong> (EST UTC+10)<br />
03:01 - <strong>Auckland</strong> (NZST UTC+12)</p>

<p><a href="http://www.google.com/calendar/event?action=TEMPLATE&amp;text=MooTools%20IRC%20Office%20Hours&amp;dates=20110705T150000Z/20110705T160000Z&amp;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&amp;location=%23motools%20on%20irc.freenode.net&amp;trp=true&amp;sprop=http%3A%2F%2Fmootools.net%2F&amp;sprop=name:MooTools">Add it to your Google Calendar</a>.</p>

<p>We&#8217;ll be in the <a href="irc://irc.freenode.net/mootools">#mootools</a> freenode.net channel.</p>

<h3>Guidelines</h3>

<p>We did very well last week in following the guidelines. I’ve included them in this post as a reminder.</p>

<ol>
<li><strong>Please use <a href="http://jsfiddle.net">jsfiddle.net</a></strong> and keep your code with minimal boilerplate &#8212; get to the essence of your question</li>
<li><strong>Stay on topic.</strong> Let&#8217;s keep the chat around MooTools and how it interacts with your code and the rest of the JavaScript ecosystem.</li>
<li><strong>Be courteous and helpful with others.</strong> We are not guaranteeing that all of us will give you our undivided attention during the hour (we are also working!). If you can answer a question (as best as you can) it will really be helpful.</li>
<li>Sharing is caring. Share the room, but also share the event. Post to twitter, Facebook, your blog, and tell your parents. We want to foster growth in our community. This is the chance to participate and to help.</li>
</ol>

<h3>Tips</h3>

<p>Use this button to add the open office hour to your Google Calendar. <strong>You’ll need to setup the event so that it repeats weekly.</strong><br />
<a href="http://www.google.com/calendar/event?action=TEMPLATE&#038;text=MooTools%20IRC%20Office%20Hours&#038;dates=20110705T150000Z/20110705T160000Z&#038;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&#038;location=%23motools%20on%20irc.freenode.net&#038;trp=true&#038;sprop=http%3A%2F%2Fmootools.net%2F&#038;sprop=name:MooTools" target="_blank"><img src="http://www.google.com/calendar/images/ext/gc_button6.gif" border=0></a>
<br style="clear: both" />
If you don’t have an IRC client you can use <a href="http://webchat.freenode.net/">http://webchat.freenode.net/</a>.</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/wbN66Jr6Jag" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:80:"http://mootools.net/blog/2011/07/04/june-28th-irc-office-hour-recapsummary/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:2:"18";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:75:"http://mootools.net/blog/2011/07/04/june-28th-irc-office-hour-recapsummary/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:35:"June 21st Office Hour Recap/Summary";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/LvtoZ7bCDxA/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:80:"http://mootools.net/blog/2011/06/27/june-21st-office-hour-recapsummary/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 27 Jun 2011 12:46:11 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:6:"Events";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1412";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:299:"As suggested by our community, we’re going to release a recap, or summary, of the IRC Office Hour after every session. We want to encourage you to join us on Tuesday’s at 11am EST in the #mootools IRC channel, but if need be let this be your medium to discuss your perspective and your own [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"ibolmo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:12307:"<p>As <a href="http://mootools.net/blog/2011/06/20/reminder-next-office-hour-is-tomorrow-june-21st/#comment-2020">suggested by our community</a>, we’re going to release a recap, or summary, of the IRC Office Hour after every session. We want to encourage you to join us on Tuesday’s at 11am EST in the <a href="irc://irc.freenode.net/mootools">#mootools IRC channel</a>, but if need be let this be your medium to discuss your perspective and your own ideas (you can also discuss in the <a href="https://groups.google.com/forum/#!forum/mootools-users">Google Group</a>).</p>

<h3>Topics Covered</h3>

<ul>
<li>MooTools 2.0 Community “Wish List”</li>
<li>MooTools Documentation</li>
<li>Flex Box Model</li>
<li>Require.JS and Namespacing</li>
<li>MooTools Roadmap</li>
<li>MooTools Feature: Accessors</li>
<li>Model Change Events</li>
<li>MooTools 2.0 Site</li>
<li>MooTools UI and Mobile</li>
<li>Event Delegation in Core</li>
<li>Github Issues</li>
</ul>

<p><span id="more-1412"></span></p>

<h4>MooTools 2.0 Community “Wish List”</h4>

<p>We created a document and shared with the IRC channel a “wish list” to add requests of what MooTools 2.0 should include. You can find the <a href="https://docs.google.com/document/d/1tnT5nrPSaNL2GfaaXlN0Q61NjqQoOJddjgsIjqwmhGo/edit?hl=en_US">wish list here</a>. Please add your own requests. Periodically we’ll check the list and approve items for 2.0.</p>

<h4>MooTools Documentation</h4>

<p>We talked about our efforts to improve the documentation. We were suggested in the channel to improve the argument list in the docs and include inherited properties and methods (plus link to the parent class).</p>

<p>We also want to make the experience more viral and social and we’d like to include social plugins (Facebook and Twitter). A comments section akin to PHP’s plus heavy moderation to have quality comments and shared experiences.</p>

<p>Analytics will also play a major role as we’d like to improve feedback. We’d like to know which methods and classes are most viewed, liked, and commented. Likewise, we want to make it easier for you to find what you’re looking for. Better SEO as well as navigation and search inside of the docs.</p>

<p>While you are in the documentation, we are also adding inlined <a href="http://jsfiddle.net/">jsfiddle</a> so that you can run the examples/demos and modify them on the fly. This also means that you can contribute your own examples/demos.</p>

<p>Of course, the above is a lot of work and we welcome your participation. <a href="http://mootools.net/developers">Darren Waddell</a> has stepped up and already started working on this. Take a look at his repository (<a href="https://github.com/fakedarren/mootools-docs">fakedarren/mootools-docs</a>) and <strong>please fork</strong>. User, kpobococ, is already working with Darren thanks to the office hour.</p>

<h4>Flex box module</h4>

<p>A user had a question about the “wrapping” of the UI so that it extends to the complete window. It’s not built-in to MooTools, but we gave him a few suggestions on how to accomplish this. Ryan Florence mentioned his <a href="https://github.com/rpflorence/mootools-wallpaper">mootools-wallpaper</a> and a <a href="http://jsfiddle.net/rpflorence/A7VNN/embedded/result,resources,js,html,css/">jsfiddle example</a>.</p>

<h4>AMD, requirejs, namespacing</h4>

<p>First, some context. <a href="http://requirejs.org/">require.js</a> is a “file and module loader” which implements the <a href="http://wiki.commonjs.org/wiki/Modules/AsynchronousDefinition">Asynchronous Module Definition</a> (AMD) CommonJS specification. This means that you can <code>define</code> modules and <code>require</code> (load) them only if they’re necessary. The philosophy is aligned to ours. We’ve never wanted our users to download the complete repository and load it <em>blindly</em> into a page. We’ve supported modularity, and speed, since day 1. Rest assured that MooTools 2.0 will be require.js ready out of the box.</p>

<p>Namespacing, is a loaded term. It may mean to “sandbox” MooTools so that it doesn’t mess with prototypes. Namespacing may also mean that you can apply, or install, methods into any given object. We’ll make a separate blog post about this, but it’s time to let the cat out of the bag.</p>

<p>We would like for MooTools 2.0 to play nice with <strong>everyone</strong>. This is a huge departure from 1.x days, but we’d like to position MooTools 2.0 so that you can drop it in <strong>any</strong> environment (that JavaScript can be run) and it will <strong>Just Work™</strong>.</p>

<p>Valerio Proietti has started to work on this in his own <a href="https://github.com/kamicane/mootools-core/tree/define-2">define-2</a> branch and we’re looking to you for feedback and opinions. Please fork and send feedback. Now is the time to make your voice heard. Once we release 2.0, there’s no going back.</p>

<h4>MooTools Roadmap</h4>

<p>And this brings us to the roadmap. Again, well deserving of its own blog post. Here’s the official word from Valerio, himself. <strong>We’re going straight to 2.0.</strong> There’s no date, yet, on when this will happen but a lot of <a href="https://github.com/kamicane/mootools-core/commits/define-2">work and time</a> is being put to get it out the door.</p>

<p>This would be the time, for you to volunteer your time.</p>

<p>Oh and don’t run around frantically. 1.3.x will continued being developed but released as bug fixes and any improvements provided by the community or downgraded from 2.0.</p>

<h4>MooTools 2.0 Feature: Accessor</h4>

<p>Still in its infancy this pattern is very powerful. It’s deserving of its own blog post, but here’s the summary: with this pattern you can define and lookup functions and properties that are usually Objects now, like Class.Mutators or Element.Properties. Besides simple lookup, it can also do a match so a &#8216;protected&#8217; Class Mutator can be defined so a Class method can be defined as <code>’protected foo’: function(){</code> so that the method cannot be run outside of the class. Have a look at the <a href="https://github.com/kamicane/mootools-core/blob/define-2/Source/Data/Accessor.js">source</a>.</p>

<h4>Model Change Events</h4>

<p>Someone had asked to support events for when properties change in the form of <code>change:foo</code>. It’s doubtful we’ll have this, but developer, verylastminute, has already worked on something that might serve in the mean time: <a href="http://jsfiddle.net/sixtyseconds/eRqxF/">ElementSpy</a>.</p>

<h4>MooTools 2.0 Site</h4>

<p>As you might have expected, there will be a new site for the launch of 2.0. We’re not yet in implementation stage, but we have <a href="http://mootools.fakedarren.com/moo2.png">screenshot of what it might look like</a>. If you’d like to get involved in the design (for some street cred) join us in the IRC channel to get in touch with Nathan Querido, from <a href="http://www.queridodesign.net/">QueridoDesign</a>, since he’s leading that project.</p>

<h3>MooTools UI and Mobile</h3>

<p>There’s a strong request for an official UI and Mobile projects. Although we are not promising that we will get around to the UI and Mobile prior to 2.0 release, we do agree on having them. For now we’re supporting projects that fill this need.</p>

<p>For the mobile, we’re interested in <a href="https://github.com/jpdery/moobile-core">jpdery/moobile-core</a> and <a href="https://github.com/cpojer/mootools-mobile">cpojer/mootools-mobile</a>. Add your projects in the comment section.</p>

<p>For UI we have our own <a href="https://github.com/kamicane/art">ART project</a> which is almost ready to be released. Missing documentation and testing. There’s also projects we’re interested in: <a href="https://github.com/Inviz/lsd">inviz/lsd</a>, <a href="https://github.com/anutron/behavior">anutron/behavior</a>, <a href="http://jxlib.org/">JxLib</a>, and <a href="https://github.com/sixtyseconds/mootools-interface">sixtyseconds/mootools-interface</a>. Add your projects in the comment section.</p>

<h4>Event Delegation in Core</h4>

<p>We’re also promising that Event Delegation will be in Core before 2.0 is out the door. Still unknown if the API will change between 1.3.x and 2.0, but let’s revel in the news!</p>

<h4>Github Issues</h4>

<p>Again one of those, “deserving of its own blog post” we’re moving from Lighthouse Tickets to Github Issues. This means that we will accept any new issues in <a href="https://github.com/mootools/mootools-core/issues">Github</a> and discourage the use of Lighthouse. We will disable Lighthouse after we’ve migrated.</p>

<h3>Next Office Hour</h3>

<p>As you’re now aware, the MooTools Office Hours are very fun and informative. Remember that we’re having another this:</p>

<h4>Tuesday, June 28th at</h4>

<p>05:01 - <strong>Honolulu</strong> (Hast UTC-10)<br />
08:01 - <strong>San Francisco</strong> (PDT UTC-7)<br />
10:01 - <strong>Chicago</strong> (CDT UTC-5)<br />
11:01 - <strong>New York</strong> (EDT UTC-4)<br />
12:01 - <strong>Rio de Janeiro</strong> (BRT UTC-3)<br />
16:01 - <strong>London</strong> (BST UTC+1)<br />
17:01 - <strong>Vienna</strong> (CEST UTC+2)<br />
20:31 - <strong>Mumbai</strong> (IST UTC+5:30)<br />
23:01 - <strong>Hong Kong</strong> (HKT UTC+8)<br />
00:01 - <strong>Tokyo</strong> (JST UTC+9)<br />
01:01 - <strong>Sydney</strong> (EST UTC+10)<br />
03:01 - <strong>Auckland</strong> (NZST UTC+12)</p>

<p><a href="http://www.google.com/calendar/event?action=TEMPLATE&amp;text=MooTools%20IRC%20Office%20Hours&amp;dates=20110628T150000Z/20110628T160000Z&amp;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&amp;location=%23motools%20on%20irc.freenode.net&amp;trp=true&amp;sprop=http%3A%2F%2Fmootools.net%2F&amp;sprop=name:MooTools">Add it to your Google Calendar</a>.</p>

<p>We&#8217;ll be in the <a href="irc://irc.freenode.net/mootools">#mootools</a> freenode.net channel.</p>

<h3>Guidelines</h3>

<p>We did very well last week in following the guidelines. I’ve included them in this post as a reminder.</p>

<ol>
<li><strong>Please use <a href="http://jsfiddle.net">jsfiddle.net</a></strong> and keep your code with minimal boilerplate &#8212; get to the essence of your question</li>
<li><strong>Stay on topic.</strong> Let&#8217;s keep the chat around MooTools and how it interacts with your code and the rest of the JavaScript ecosystem.</li>
<li><strong>Be courteous and helpful with others.</strong> We are not guaranteeing that all of us will give you our undivided attention during the hour (we are also working!). If you can answer a question (as best as you can) it will really be helpful.</li>
<li>Sharing is caring. Share the room, but also share the event. Post to twitter, Facebook, your blog, and tell your parents. We want to foster growth in our community. This is the chance to participate and to help.</li>
</ol>

<h3>Tips</h3>

<p>Use this button to add the open office hour to your Google Calendar. <strong>You’ll need to setup the event so that it repeats weekly.</strong><br />
<a href="http://www.google.com/calendar/event?action=TEMPLATE&#038;text=MooTools%20IRC%20Office%20Hours&#038;dates=20110628T150000Z/20110628T160000Z&#038;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&#038;location=%23motools%20on%20irc.freenode.net&#038;trp=true&#038;sprop=http%3A%2F%2Fmootools.net%2F&#038;sprop=name:MooTools" target="_blank"><img src="http://www.google.com/calendar/images/ext/gc_button6.gif" border=0></a>
<br style="clear: both" />
If you don’t have an IRC client you can use <a href="http://webchat.freenode.net/">http://webchat.freenode.net/</a>.</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/LvtoZ7bCDxA" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:76:"http://mootools.net/blog/2011/06/27/june-21st-office-hour-recapsummary/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"9";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:71:"http://mootools.net/blog/2011/06/27/june-21st-office-hour-recapsummary/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:44:"
		
		
		
		
		
				
		

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:51:"Reminder: Next Office Hour is Tomorrow (June 21st)!";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/q6Y7ndCnEY0/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:93:"http://mootools.net/blog/2011/06/20/reminder-next-office-hour-is-tomorrow-june-21st/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Jun 2011 17:09:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:6:"Events";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1398";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:331:"Last week we held our first IRC office hours in the #mootools channel on irc.freenode.net. Fifteen (15) MooTools team members were in attendance and we got a lot of responses from our community. We covered: sandboxing natives, namespacing, packaging, roadmap, MVC, and that I look like Sam from the Lord of the Rings. This is [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"ibolmo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:5052:"<p>Last week we held our first IRC office hours in the #mootools channel on irc.freenode.net.  Fifteen (15) MooTools team members were in attendance and we got a lot of responses from our community. We covered: sandboxing natives, namespacing, packaging, roadmap, MVC, and that I look like <a href="https://park-204.wikispaces.com/file/view/sam5.jpg/33426961/sam5.jpg">Sam from the Lord of the Rings</a>.</p>

<p>This is a reminder that <strong>tomorrow</strong> (June 21st) we’re having another office hour and you’re cordially invited to join us.</p>

<p>Unlike last week, this week we’ll have a couple of questions ready to steer the conversation. This week we’ll talk about MooTools 2.0 and what you guys need to love MooTools even more. We’ll be taking names down as well, for those that would like to contribute.</p>

<p>Keep reading to learn the details.</p>

<p><span id="more-1398"></span></p>

<h3>When &amp; Where</h3>

<p>If you’re familiar with last week’s office hour, you probably realize that I made a boo boo with the offset in different timezones. This is now fixed thanks to EveryTimeZone. Here’s a complete list of timezones just so that we’re all on the same page.</p>

<h4>Tuesday, June 21st at</h4>

<p>05:01 - <strong>Honolulu</strong> (Hast UTC-10)<br />
08:01 - <strong>San Francisco</strong> (PDT UTC-7)<br />
10:01 - <strong>Chicago</strong> (CDT UTC-5)<br />
11:01 - <strong>New York</strong> (EDT UTC-4)<br />
12:01 - <strong>Rio de Janeiro</strong> (BRT UTC-3)<br />
16:01 - <strong>London</strong> (BST UTC+1)<br />
17:01 - <strong>Vienna</strong> (CEST UTC+2)<br />
20:31 - <strong>Mumbai</strong> (IST UTC+5:30)<br />
23:01 - <strong>Hong Kong</strong> (HKT UTC+8)<br />
00:01 - <strong>Tokyo</strong> (JST UTC+9)<br />
01:01 - <strong>Sydney</strong> (EST UTC+10)<br />
03:01 - <strong>Auckland</strong> (NZST UTC+12)</p>

<p><a href="http://www.google.com/calendar/event?action=TEMPLATE&amp;text=MooTools%20IRC%20Office%20Hours&amp;dates=20110621T150000Z/20110621T160000Z&amp;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&amp;location=%23motools%20on%20irc.freenode.net&amp;trp=true&amp;sprop=http%3A%2F%2Fmootools.net%2F&amp;sprop=name:MooTools">Add it to your Google Calendar</a>.</p>

<p>We&#8217;ll be in the <a href="irc://irc.freenode.net/mootools">#mootools</a> freenode.net channel.</p>

<h3>Guidelines</h3>

<p>We did very well last week in following the guidelines. I’ve included them in this post as a reminder.</p>

<ol>
<li><strong>Please use <a href="http://jsfiddle.net">jsfiddle.net</a></strong> and keep your code with minimal boilerplate &#8212; get to the essence of your question</li>
<li><strong>Stay on topic.</strong> Let&#8217;s keep the chat around MooTools and how it interacts with your code and the rest of the JavaScript ecosystem.</li>
<li><strong>Be courteous and helpful with others.</strong> We are not guaranteeing that all of us will give you our undivided attention during the hour (we are also working!). If you can answer a question (as best as you can) it will really be helpful.</li>
<li>Sharing is caring. Share the room, but also share the event. Post to twitter, Facebook, your blog, and tell your parents. We want to foster growth in our community. This is the chance to participate and to help.</li>
</ol>

<h3>Tips</h3>

<p>Use this button to add the open office hour to your Google Calendar. <strong>You’ll need to setup the event so that it repeats weekly.</strong><br />
<a href="http://www.google.com/calendar/event?action=TEMPLATE&#038;text=MooTools%20IRC%20Office%20Hours&#038;dates=20110621T150000Z/20110621T160000Z&#038;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&#038;location=%23motools%20on%20irc.freenode.net&#038;trp=true&#038;sprop=http%3A%2F%2Fmootools.net%2F&#038;sprop=name:MooTools" target="_blank"><img src="http://www.google.com/calendar/images/ext/gc_button6.gif" border=0></a>
<br style="clear: both" />
If you don’t have an IRC client you can use <a href="http://webchat.freenode.net/">http://webchat.freenode.net/</a>.</p>

<h3>In Closing</h3>

<p>Remember that we’re doing this because we love to meet our community leaders. Bring your colleagues or even your boss if you have questions that you’re concerned with or would like solutions for.</p>

<p>Last week we had a lot of fun bringing a lot of MooTools developers together which spurred some development. Looking forward to tomorrow for a great hour.</p>

<p>Cheers.</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/q6Y7ndCnEY0" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:89:"http://mootools.net/blog/2011/06/20/reminder-next-office-hour-is-tomorrow-june-21st/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:84:"http://mootools.net/blog/2011/06/20/reminder-next-office-hour-is-tomorrow-june-21st/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:10;a:6:{s:4:"data";s:44:"
		
		
		
		
		
				
		

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:22:"Open IRC Office Hours!";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/ZS9KFitjPfk/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:67:"http://mootools.net/blog/2011/06/09/open-irc-office-hours/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 10 Jun 2011 02:00:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:6:"Events";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:4:"News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1372";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:364:"Starting next week, we’re going to be holding regular IRC office hours for MooTools developers in the #mootools channel on irc.freenode.net. Members of the MooTools team will be on hand to answer your technical questions. We’re following the footsteps of many successful office hours from other Open Source projects (Android, Mongo DB, Google App Engine, [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"ibolmo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4155:"<p>Starting next week, we’re going to be holding regular IRC office hours for MooTools developers in the <a href="irc://irc.freenode.net/mootools">#mootools</a> channel on irc.freenode.net. Members of the MooTools team will be on hand to answer your technical questions.</p>

<p><span id="more-1372"></span></p>

<p>We’re following the footsteps of many successful office hours from other Open Source projects (Android, Mongo DB, Google App Engine, and Node.JS) because we think it’s the best way to help, meet, and listen to our community.</p>

<p>In fact, without IRC I wouldn’t have become a MooTools developer in the first place. Like many of the other MooTools developers. Maybe you will too.</p>

<h3>When</h3>

<p>We’re going to start with a single weekly meeting on Tuesday’s at 5pm - 6pm (CEST <del datetime="2011-06-14T15:00:00+00:00">GMT</del>) (11am - 12pm EDT <del datetime="2011-06-14T15:00:00+00:00">EST</del>). We chose this time since it best fits our schedule, but depending on response and returns (more development, more team members, etc.) we can have a dedicated time for Western and for Eastern hemispheres.</p>

<p>Our <strong>first</strong> meeting is <em>next</em> <a href="http://www.google.com/calendar/event?action=TEMPLATE&#038;text=MooTools%20IRC%20Office%20Hours&#038;dates=20110614T150000Z/20110614T160000Z&#038;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&#038;location=%23motools%20on%20irc.freenode.net&#038;trp=true&#038;sprop=http%3A%2F%2Fmootools.net%2F&#038;sprop=name:MooTools" target="_blank">Tuesday, June 14th at 11am EDT <del datetime="2011-06-14T15:00:00+00:00">EST</del> (5pm CEST <del datetime="2011-06-14T15:00:00+00:00">GMT</del>)</a>.</p>

<h3>Guidelines</h3>

<p>With any endeavor there are some ground rules for efficacy.</p>

<ol>
<li><strong>Please use <a href="http://jsfiddle.net">jsfiddle.net</a></strong> and keep your code with minimal boilerplate &#8212; get to the essence of your question</li>
<li><strong>Stay on topic.</strong> Let&#8217;s keep the chat around MooTools and how it interacts with your code and the rest of the JavaScript ecosystem.</li>
<li><strong>Be courteous and helpful with others.</strong> We are not guaranteeing that all of us will give you our undivided attention during the hour (we are also working!). If you can answer a question (as best as you can) it will really be helpful.</li>
<li>Sharing is caring. Share the room, but also share the event. Post to twitter, Facebook, your blog, and tell your parents. We want to foster growth in our community. This is the chance to participate and to help.</li>
</ol>

<h3>Tips</h3>

<p>Use this button to add the open office hour to your Google Calendar. <strong>You’ll need to setup the event so that it repeats weekly.</strong><br />
<a href="http://www.google.com/calendar/event?action=TEMPLATE&#038;text=MooTools%20IRC%20Office%20Hours&#038;dates=20110614T150000Z/20110614T160000Z&#038;details=Join%20us%20and%20ask%20away%20technical%20questions%2C%20open%20(what's%20new%2C%20what's%20coming)%20questions%2C%20or%20just%20participate%20in%20the%20party.%20MooTools%20developers%20will%20be%20in%20the%20%23mootools%20channel%20ready%20to%20answer%20and%20get%20to%20meet%20you.&#038;location=%23motools%20on%20irc.freenode.net&#038;trp=true&#038;sprop=http%3A%2F%2Fmootools.net%2F&#038;sprop=name:MooTools" target="_blank"><img src="http://www.google.com/calendar/images/ext/gc_button6.gif" border=0></a>
<br style="clear: both" />
If you don’t have an IRC client you can use <a href="http://webchat.freenode.net/">http://webchat.freenode.net/</a>.</p>

<h3>In Closing</h3>

<p>I expect this will be a lot of fun and a great learning experience to find out how our community has been prospering and using MooTools. Hope to see you in the IRC channel!</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/ZS9KFitjPfk" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:63:"http://mootools.net/blog/2011/06/09/open-irc-office-hours/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"5";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:58:"http://mootools.net/blog/2011/06/09/open-irc-office-hours/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:11;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:36:"MooTools Core 1.3.2 and More 1.3.2.1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/OAdj1CW6zbs/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:82:"http://mootools.net/blog/2011/04/28/mootools-core-1-3-2-and-more-1-3-2-1/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 28 Apr 2011 20:23:28 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1352";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:329:"Today we announce the simultaneous release of MooTools Core 1.3.2 and More 1.3.2.1. This is mostly a bugfix release and does not contain many new features. The most important fix is within our selector engine, Slick, which failed in some cases where the selectors began with an operator (ex. ~div). A new component has been [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"Arian";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3025:"<p>Today we announce the simultaneous release of MooTools Core 1.3.2 and More 1.3.2.1. This is mostly a bugfix release and does not contain many new features. The most important fix is within our selector engine, Slick, which failed in some cases where the selectors began with an operator (ex. <code>~div</code>).</p>

<p>A new component has been added to MooTools More: Table. Table was slated to be added in MooTools Core 2.0, but we&#8217;re making it available in MooTools More now. Table is similar to the JavaScript object literal, but where an object can only have a scalar value (string or number) as a key, Table can have any value as a key. Where the order of values in an object is not static like an array (by specification, usually browsers keep the order which they are defined), the values in Table will have a static order. These advantages come with a performance cost, where an object value is a direct look-up, Table uses <code>indexOf</code> which is less efficient, so use with care.</p>

<h3>Notable changes in MooTools Core include:</h3>

<ul>
<li>Fixed Slick bug with <code>~div</code>-like selectors</li>
<li>Fixed MooTools in the Node.js environment</li>
<li>Fixed an exception in DOMReady in Chrome when the page with MooTools was in an IFrame</li>
<li>Fixed <code>setOpacity</code> for very small numbers in IE</li>
<li>Fixed an exception in FireFox 4 when MooTools tried to overwrite <code>document.head</code></li>
<li>Added the possibility to create elements with boolean values with an selector, e.g. <code>new Element('input[checked]');</code></li>
</ul>

<h3>MooTools More:</h3>

<ul>
<li>Rewritten Element.Position which solved some issues </li>
<li>Added Table, as described above</li>
<li>Ironed out some Event Delegation issues</li>
<li>Additional fixes can be found at the <a href="https://mootools.lighthouseapp.com/projects/24057/milestones/104271-1322">Lighthouse for 1.3.2.1</a></li>
</ul>

<h3>Get it!</h3>

<ul>
<li><a href="http://mootools.net/download">Download MooTools Core 1.3.2</a>; <a href="http://mootools.net/core/">Build MooTools Core 1.3.2</a></li>
<li><a href="http://mootools.net/more/">Build MooTools More 1.3.2.1</a></li>
<li>Fork / clone <a href="http://github.com/mootools/mootools-core/tree/1.3.2">MooTools 1.3.2 from GitHub</a>, and build it yourself with <a href="http://github.com/kamicane/packager">Packager</a>.</li>
<li><a href="http://github.com/mootools/mootools-core/commits/1.3.2">Read the Core commit logs</a> to see precisely what has changed.</li>
<li><a href="http://github.com/mootools/mootools-more/commits/1.3.2.1">Read the More commit logs</a> to see precisely what has changed for More.</li>
<li><a href="http://mootools.net/docs">Browse the Documentation for Core &amp; More.</a></li>
<li>Please report any bugs you can find on <a href="https://mootools.lighthouseapp.com/projects/2706-mootools/tickets">Lighthouse</a>, our bug tracker.</li>
</ul>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/OAdj1CW6zbs" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:78:"http://mootools.net/blog/2011/04/28/mootools-core-1-3-2-and-more-1-3-2-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:2:"14";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:73:"http://mootools.net/blog/2011/04/28/mootools-core-1-3-2-and-more-1-3-2-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:12;a:6:{s:4:"data";s:41:"
		
		
		
		
		
				

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:37:"MooTools Gets a Little Closer to Home";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/zvq4nGnc69c/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:83:"http://mootools.net/blog/2011/04/01/mootools-gets-a-little-closer-to-home/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 Apr 2011 09:54:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1325";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:325:"A few months back we sent out a survey asking you where you&#8217;d like for the development team to focus its energies. Since then we&#8217;ve worked on demos and released a new version of the framework with new features based on that valuable feedback. Getting direct input from everyone who uses MooTools helps us as [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"aaron";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:5276:"<p>A few months back we <a href="http://mootools.net/blog/2010/12/05/mootools-survey">sent out a survey</a> asking you where you&#8217;d like for the development team to focus its energies. Since then we&#8217;ve <a href="http://mootools.net/blog/2011/01/04/new-demos/">worked on demos</a> and <a href="http://mootools.net/blog/2011/02/25/mootools-core-more-1-3-1/">released a new version of the framework</a> with new features based on that valuable feedback. Getting direct input from everyone who uses MooTools helps us as developers stay on target for the things you need.</p>

<p>One of the items that came up several times in the survey was a desire for more support for internationalization. MooTools More already ships with a <a href="http://mootools.net/docs/more/Locale/Locale">system for localizing plugins</a>, but this functionality isn&#8217;t baked deep into the framework. Several comments in the survey implied a desire to see this functionality available throughout MooTools Core. One respondent wrote, &#8220;It is difficult to understand MooTools as my English is not great. My website has many visitors from where I live and they need all to understand it. Thank you.&#8221;</p>

<p>You asked for a more culturally sensitive framework and we listened. Given that the MooTools development team is based all over the world from Italy to Austria to The Netherlands to Germany to Sweden we can understand the value of having MooTools available in your native tongue.</p>

<p><span id="more-1325"></span></p>

<h3>Introducing the MooTools Localized API</h3>

<p>For the past few weeks we&#8217;ve been hard at work localizing all of MooTools. That&#8217;s right, you will be able to download MooTools Core and MooTools More in any of the several languages we support. We&#8217;re are not entirely ready yet and don&#8217;t have full coverage for each API, but nevertheless wanted to give you a preview of what we&#8217;re working on.
We were able to do this because MooTools&#8217; modularity and JavaScript&#8217;s flexibility which makes it easy to add and change methods on the fly.</p>

<p>To get started with using the translated API, you need to look at <a href="https://github.com/fakedarren/mootools-locale">Github</a> for now, since we&#8217;re still early in development. However we will provide <a href="http://mootools.net/download">a download page</a> in the coming weeks so you can easily select your language and download the required components.</p>

<p>Here&#8217;s a quick example of the Italian translation in action:</p>

<pre><code>Element.impostaStile('colore', 'rosso');
</code></pre>

<p>We also support British English now as well:</p>

<pre><code>Element.setStyle('colour', 'red');
</code></pre>

<p>Or Dutch:</p>

<pre><code>venster.gebeurtenisToevoegen('domklaar', function(){
    $('kop').zet('tekst', 'MooTools!');
});
</code></pre>

<p>Everything is right were you expect it to be; it&#8217;s still just MooTools! All your users will recognize the difference of a site built using their native tongue.</p>

<p>We&#8217;ve also set up a repository on <a href="https://github.com/fakedarren/mootools-locale">Github</a> which you could use to add and improve translations. You could grab the Dutch translation (Locale.nl-NL.API.js) and translate it to your own language. We would like to add documentation for the translations as well, and are still looking how we could implement this in an efficient way in our future documenation system which is currently under development.</p>

<p>If you&#8217;re interested in helping us translate into additional languages please get in touch on the <a href="http://groups.google.com/group/mootools-users">MooTools Google Group</a> or at <a href="https://github.com/fakedarren/mootools-locale">Github</a>.</p>

<p>Here is an early demo with some working JSFiddles:</p>

<p><strong>Dutch:</strong></p>

<iframe style="width: 100%; height: 300px" src="http://jsfiddle.net/arian/sLyj8/5/embedded/"></iframe>

<p><strong>Ukrainian:</strong></p>

<iframe style="width: 100%; height: 300px" src="http://jsfiddle.net/slik/9ucfy/3/embedded/"></iframe>

<p><strong>GERMAN:</strong></p>

<iframe style="width: 100%; height: 300px; margin-bottom: 2em" src="http://jsfiddle.net/arian/Ln94J/embedded/"></iframe>

<h3>Keep the Feedback Coming!</h3>

<p>In the coming months we hope to add a lot of new features that enrich the MooTools ecosystem. We&#8217;ve gotten a lot of requests to make MooTools Core suitable for mobile devices. Our plans are to make a modular system that allows you to include only the parts you need with small, powerful, and feature rich modules for effects and AJAX as well as enhancements to native objects like strings and functions. We plan to sell this in the iTunes store for 99&cent;. What features would you like to see next in MooTools? Leave a comment!</p>

<p><strong>Update:</strong> Thanks to <a href="https://github.com/paraboul">paraboul</a> we added a beginning for French!</p>

<p><strong>Update 2:</strong> Anyone wishing to find more information on our Localized API efforts, please <a href="http://twitter.com/#!/mootools/status/53918481925668864">read this</a>.</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/zvq4nGnc69c" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:79:"http://mootools.net/blog/2011/04/01/mootools-gets-a-little-closer-to-home/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:2:"20";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:74:"http://mootools.net/blog/2011/04/01/mootools-gets-a-little-closer-to-home/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:13;a:6:{s:4:"data";s:44:"
		
		
		
		
		
				
		

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:61:"Events with MooTools - Element, Class, Delegation and Pseudos";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/sfgEJ4JKOx0/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:103:"http://mootools.net/blog/2011/03/28/events-with-mootools-element-class-delegation-and-pseudos/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 28 Mar 2011 19:18:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:13:"Tips & Tricks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1182";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:354:"One of the most useful and common part of MooTools is its Events Type. There are two Event usages: Element and Class. Element.Events is probably the most known because that&#8217;s probably one of the first things you&#8217;ve used when you started using MooTools. Furthermore, MooTools More 1.3 Events.Pseudos has been introduced to give even more [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"Arian";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:18985:"<p>One of the most useful and common part of MooTools is its Events Type. There are two Event usages:  Element and Class. Element.Events is probably the most known because that&#8217;s probably one of the first things you&#8217;ve used when you started using MooTools. Furthermore, MooTools More 1.3 Events.Pseudos has been introduced to give even more power and control over Events and with Event Delegation can give your page a massive performance boost. This blog post will give you a deeper insight into all components.</p>

<p><span id="more-1182"></span></p>

<h3>Element.Events</h3>

<p>Element.Events represents DOM node event abstraction.  The most simple example is, of course, adding a click event to a DOM Element:</p>

<iframe style="width: 100%; height: 200px" src="http://jsfiddle.net/arian/PS5kP/2/embedded/"></iframe>

<p>For the sake of completeness I&#8217;ll explain this code step by step. First we grab the <code>a</code> element with the <a href="http://mootools.net/docs/core/Element/Element#Window:document-id">document.id</a> method. Then we call the <a href="http://mootools.net/docs/core/Element/Element.Event#Element:addEvent">Element:addEvent</a> method. The <code>addEvent</code> accepts two arguments: the event name, which is a string without the &#8216;on&#8217; part (click, keydown, mouseover) and the callback, which is a function. This function will be called when the user clicks the element.</p>

<p>There are two interesting things you see there: first, the <code>event</code> argument of the callback function. This is an instance of the <a href="http://mootools.net/docs/core/Types/Event">Event</a> Type. This is a wrapper of the native event object so we do not have to worry about browser inconsistencies. In this case the <code>stop</code> method is called to stop all default behaviors, like following the link.
The second interesting thing is that we can use the <code>this</code> variable in the event callback which refers to the <code>clickme</code> element.</p>

<h4>Removing Events</h4>

<p>Once you&#8217;ve added events to an Element, you might want to remove them some time later. Removing events is pretty straightforward. We have to store a reference to the function if we only want to remove this single event.</p>

<pre><code>// store a reference to the callback
var myCallback = function(event){
    alert('hi');
};

// add the event
myElement.addEvent('click', myCallback);

// remove the event
myElement.removeEvent('click', myCallback);
</code></pre>

<p>You can remove all the click events when calling the <code>removeEvents</code> method.</p>

<pre><code>myElement.removeEvents('click');
</code></pre>

<p>This is an interesting example what you can do when you only want to click an element twice:</p>

<iframe style="width: 100%; height: 200px" src="http://jsfiddle.net/arian/cezxh/embedded/"></iframe>

<h4>Firing Events manually</h4>

<p>It is possible to fire events manually with the <code>fireEvent</code> method. This is not a very common method but can be useful.</p>

<p>The following example is how you can call events you&#8217;ve added to an element manually:</p>

<iframe style="width: 100%; height: 200px" src="http://jsfiddle.net/arian/s6y7E/embedded/"></iframe>

<p>It is important to note that the event callback of the <code>clickme</code> event checks if the <code>event.stop</code> method exists. When using <code>fireEvent</code> you&#8217;re not calling the callback through the DOM but directly with pure JavaScript. You can pass additional arguments as a second argument of the <code>fireEvent</code>, e.g:</p>

<pre><code>clickme.fireEvent('click', [{stop: function(){}}, 'MooTools'], 500);
</code></pre>

<p>What am I doing here? The second argument of the <code>fireEvent</code> accepts a single argument or an array of arguments. In this case, I pass an array of arguments, which contains an Object as the first item in the array. The Object helps get rid of the <code>if (event &amp;&amp; event.stop)</code> condition in the former example because it mimics the Event object. In the forge there is a more sophisticated <a href="http://mootools.net/forge/p/event_mock">Event.Mock</a>.</p>

<p>Additionally, I&#8217;ve passed a third argument to <code>fireEvent</code>, <code>500</code>. This third argument is used to delay the execution of the event callback.</p>

<p>You don&#8217;t necessarily have to use existing events like <code>click</code> or <code>mouseenter</code>. You can fire an event like <code>grow</code> as well. If you add an event <code>grow</code> to the element it will work fine:</p>

<pre><code>clickme.addEvent('grow', function(height){
    this.tween('height', this.getStyle('height').toInt() + height);
});
clickme.fireEvent('grow', 30);
</code></pre>

<h4>Clone Events</h4>

<p>An even lesser known method is the <code>cloneEvents</code> method. This method can be used to clone the events from the first element into the other, for example, after using the <code>clone</code> method.</p>

<h4>How Events Work Internally</h4>

<p>The methods in Element.Events: addEvent, addEvents, removeEvent, removeEvents, fireEvent and cloneEvents, which are described above, are actually wrappers to native browser methods. Unfortunately those native methods are inconsistent across browsers. Most browsers use the W3C specification <code>addEventListener</code> except IE 8 and lower which uses the <code>attachEvent</code> method. A MooTools wrapper for the <code>addEventListener</code> is called <code>addListener</code>. This is a private method that will give us a cross-browser implementation for <code>addEvent</code>.</p>

<p>Another reason why we use our own methods is garbage collection. This happens when adding events to elements and the elements are removed from the DOM later. The events are still there, but the element is not; this might cause to memory leaks. Fortunately MooTools handles this problem and you don&#8217;t need to manually fix this issue.</p>

<p>Finally MooTools stores all the event callbacks using the <code>store</code> and <code>retrieve</code> methods. You could retrieve the object with all event callbacks using <code>myElement.retrieve('events')</code>. This is private and not recommended because it could break your code sooner or later. The reason why MooTools stores all the callbacks is so you can easily remove, fire, or clone them without passing a reference to the callbacks each time.</p>

<h4>Event Bubbling</h4>

<p>An interesting thing about the DOM is that elements can be nested. So what will happen if you add events to an element and to the element&#8217;s child element? What will happen is called &#8216;Event Bubbling&#8217;.</p>

<p>This is a quick example:</p>

<iframe style="width: 100%; height: 300px" src="http://jsfiddle.net/arian/4K3ad/embedded/"></iframe>

<p>In this example there are two different elements, where the <code>a</code> element is nested into the <code>div</code> element. Each element has its own click event. Now when you click the <code>a</code> element, both events are fired, first the event of the <code>a</code> element, then the event of the <code>div</code> element. Also note that we cannot use the <code>Event:stop</code> or <code>Event:stopPropagation</code> methods anymore because this will block bubbling, we should use <code>Event.preventDefault</code> in this case.</p>

<p>This is actually nothing special of MooTools, but this is how it&#8217;s specified by the W3C. The W3C specification has a capture phase too, that will go the other way around. Unfortunately MooTools cannot support this because IE 8 and lower doesn&#8217;t support it. The three phases are clearly explained in <a href="http://www.w3.org/TR/DOM-Level-3-Events/#dom-event-architecture">this diagram</a></p>

<h4>Event Delegation</h4>

<p>Event Delegation is a technique that uses event bubbling and the <code>event.target</code> property. The target property is always the element which is clicked (or hovered when using mouse* events). What you can do is add an event to one of the parent elements, which will fire too because of the bubbling, and check of the target property satisfies your constrains, for example if it matches a CSS selector.</p>

<p>A very basic example of event delegation is:</p>

<iframe style="width: 100%; height: 300px" src="http://jsfiddle.net/arian/2CKEL/embedded/"></iframe>

<p>This example is very simple, but it can get more difficult with more complex delegates. That&#8217;s why MooTools More has the <a href="http://mootools.net/docs/more/Element/Element.Delegation">Element.Delegation</a> component. This component makes it easy to use delegation.</p>

<iframe style="width: 100%; height: 300px" src="http://jsfiddle.net/arian/Qd7fb/embedded/"></iframe>

<p>This example uses Delegation. You can see that instead of using just <code>click</code>, <code>click:relay(tr td.click)</code> is used. With the Event Pseudo (will be explained later) <code>relay</code> we tell MooTools to check if the target or one of its parents matches the passed selector <code>tr td.click</code>. If the element is matched the callback gets fired.</p>

<p>Event Delegation has some important advantages. It especially improves performance. Imagine a page with hundreds of links or table rows. Instead of adding an event to every element, you can delegate the parent element by adding only one event. 
Secondly Event Delegation is useful when working with dynamic pages. In case you have the same large table which will update regularly by XHR Requests, you don&#8217;t have to add new events to the rows because the rows are added into the table which has the event. The click event will bubble up to the table element and when the new row is matched against the given selector the callback function is fired. This can save you a serious amount of code and logic.</p>

<h3>Class Events</h3>

<p>Now we have seen how Element Events work, we&#8217;ll explore the Class Events. Class Events brings similar methods like addEvent, addEvents, removeEvent, removeEvents and fireEvent to MooTools Class.</p>

<p>First an example from the docs to illustrate how it works:</p>

<pre><code>var Widget = new Class({
    Implements: Events,
    initialize: function(element){
        // …
    },
    complete: function(){
        this.fireEvent('complete');
    }
});

var myWidget = new Widget();
myWidget.addEvent('complete', myFunction);
</code></pre>

<p>So what does this do? First it implements the <a href="http://mootools.net/docs/core/Class/Class.Extras#Events">Events</a> mixin. The Implements mutator will copy the methods of the Events mixin into the Widget Class.
In the complete method  it uses the <code>fireEvent</code> to fire all the added &#8216;complete&#8217; events. Once the Widget class is instantiated the example uses the <code>addEvent</code> method to add an event &#8216;complete&#8217; with the callback <code>myFunction</code>.</p>

<p>When you want to pass arguments to the callback function, you can use the second argument of the <code>fireEvent</code> method, which accepts any value for a single argument or an array for multiple arguments, just like <code>Element:fireEvent</code>.</p>

<h4>addEvent Internal argument</h4>

<p>This is a fairly unknown but useful feature. The third argument of the <code>addEvent</code> method is called the <code>internal</code> argument. This argument can be set to <code>true</code> when you do not want that the event can be removed.</p>

<p>Imagine you&#8217;re building a datepicker class. You split it up in two classes, a Picker class and a DatePicker class. The Picker Class is a generic picker which could be used for a ColorPicker or whatever picker too. It has an <code>open</code> method which opens the picker and fires the &#8216;open&#8217; event. Now the DatePicker has to do some extra things on open. Now it could overwrite the &#8216;open&#8217; method, but it can add an &#8216;open&#8217; event too. Though you do not want that the user can remove the event when using <code>myDatePicker.removeEvents('open')</code>. In this case you set the <code>internal</code> argument to <code>true</code>.</p>

<h4>Adding Events with Class Options</h4>

<p>If you&#8217;ve used <a href="http://mootools.net/docs/core/Fx/Fx">Fx</a> or <a href="http://mootools.net/docs/core/Request/Request">Request</a> you definitely have used this: events as options when instantiating a Class. This are functions which have property names like <code>onEventname</code> where <code>Eventname</code> (the first character should be uppercase) is the actual eventname and is prefixed by <code>on</code>.</p>

<pre><code>new Fx({
    onComplete: function(){
        // Will get fired when the Fx is complete
    },
    onPause: function(){
        // The Fx is paused
    }
});
</code></pre>

<p>The <code>setOptions</code> method of the <a href="http://mootools.net/docs/core/Class/Class.Extras#Options">Options</a> mixin will automatically detect this and use the <code>addEvent</code> method.</p>

<pre><code>var myWidget = new Class({
    Implements: Options,
    options: { // Default options and events
        onComplete: function(){
            // Will get fired when the class is complete
        },
        onPause: function(){
            // The class is paused
        }
    },
    initialize: function(options){
        // use the setOption method 
        this.setOptions(options);
    }
});
</code></pre>

<h3>Events Pseudos</h3>

<p>We&#8217;ve seen already a glimpse of <a href="http://mootools.net/docs/more/Class/Events.Pseudos">Events Pseudos</a> when using Event Delegation. This is a new component in MooTools More 1.3. It allows you to use event names as CSS Pseudo Selectors, thus <code>event:pseudo(value)</code>.</p>

<p>A quick example how to use the <code>:once</code> pseudo:</p>

<iframe style="width: 100%; height: 200px" src="http://jsfiddle.net/arian/wXFvj/embedded/"></iframe>

<h4>Behind the scenes</h4>

<p>Because the Element and Class methods are so similar, Events Pseudos is actually implemented once for both. It is totally abstracted to a single (private) function <code>Events.Pseudos</code>. It returns an object with modified <code>addEvent</code> and <code>removeEvent</code> methods. These methods are implemented into <a href="http://mootools.net/docs/more/Class/Events.Pseudos">Events</a> and <a href="http://mootools.net/docs/more/Element/Element.Event.Pseudos">Element</a>, so it monkey patches the old ones.</p>

<p>When using one of the methods it will detect if the eventname is a pseudo eventname, if that&#8217;s the case the eventname is parsed by <code>Slick.Parse</code> to an object. Finally it will add an event to the Class or Element with a custom callback. That callback fires the corresponding pseudo function. That pseudo function is actually a function in between that can do some extra stuff.</p>

<h4>Event Pseudo Functions</h4>

<p>The &#8216;function in between that can do some stuff&#8217; is actually the power of Events Pseudos. Like the <code>:once</code> pseudo function it will fire the passed callback function and remove itself, so the callback function can only be fired once. Another existing pseudo function for elements is <a href="http://mootools.net/docs/more/Element/Element.Event.Pseudos.Keys">:keys</a> which waits till all passed keys are pressed until firing the callback. These psuedo functions can be defined by <code>Events.definePseudo</code> or <code>Event.definePseudo</code>. In MooTools More 1.3.1.1 the <code>:pause</code> and <code>:throttle</code> events were added.</p>

<p>At this point we come back at Event Delegation, because the <code>:relay(selector)</code> is a Pseudo Function too! That pseudo function basically uses <code>Slick.match</code> to check if the element matches the selector and should fire the callback function.</p>

<h4>Creating your own Pseudo Functions</h4>

<p>You can define your own pseudo functions. This can be done with the <code>Events.definePseudo</code> or <code>Event.definePseudo</code> functions. The first one for Class Events, the second one for Element Events.</p>

<p>This is an example how to create a pseudo event which only allows you to click an element with the right mousebutton based on the mousedown event:</p>

<iframe style="width: 100%; height: 200px" src="http://jsfiddle.net/arian/BAKHU/embedded/"></iframe>

<p>This is a fairly simple example, but it is clear that you can do a lot of things with it while keeping your code clean and simple to read.</p>

<p>Another example that counts the number of clicks:</p>

<iframe style="width: 100%; height: 350px" src="http://jsfiddle.net/arian/v7W4M/embedded/"></iframe>

<p>You can see that <code>var event = args[0];</code> is used. The <code>args</code> argument is the argument that keeps the usual arguments passed into a normal event callback. Since we&#8217;re working with Element Events it has only one, so <code>args[0]</code> is the <a href="http://mootools.net/docs/core/Types/Event">Event</a> instance. Of course this argument can be different when working with Class events or when using the <code>fireEvent</code> method with multiple arguments.</p>

<p>The <code>split</code> argument contains an object with the parsed event name: <code>event:pseudo(value)</code>. You can use the <code>split.value</code> property for example if you use the <code>(</code> and <code>)</code> for passing an extra value (like <code>:relay(selector)</code> for Event Delegation). The <code>split.original</code> property contains the whole string, so <code>event:pseudo(value)</code> which can be used to remove the event in the pseudo function, which is actually what the <code>:once</code> pseudo function does.</p>

<p>Finally we use <code>fn.apply(this, args)</code> to call the callback function (which highligts the <code>a</code> element). We use apply to be sure that <code>this</code> refers to the element and it is called with the same arguments as usually. You can do something else of course, but in most cases you want to use <code>fn.apply(this, args)</code>.</p>

<h3>Conclusion</h3>

<p>Events are very powerful and you almost cannot write MooTools code without using Events. For the DOM, MooTools saves you a lot of pain and brings you the easy cross-browser API. Because of the nature of the DOM, it brings Event Bubbling which can be used for Event Delegation which can bring you several advantages. A unique part of MooTools is its Class, which brings the same API of DOM Events to Class. To give you even more power to Events, Events Pseudos can be used.</p>

<h4>Quick tip</h4>

<p>Also have a look at <a href="http://code.keetology.com/company/">Company</a> by Keeto or the PubSub pattern with the <a href="https://github.com/rpflorence/mootools-channels">MooTools-Channels</a> as MooTools implementation.</p>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/sfgEJ4JKOx0" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:99:"http://mootools.net/blog/2011/03/28/events-with-mootools-element-class-delegation-and-pseudos/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:2:"11";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:94:"http://mootools.net/blog/2011/03/28/events-with-mootools-element-class-delegation-and-pseudos/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:14;a:6:{s:4:"data";s:44:"
		
		
		
		
		
				
		

		
		
			
			
		
		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:6:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:26:"MooTools Core & More 1.3.1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://feedproxy.google.com/~r/mootools-blog/~3/X_T4x6_HHF0/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:70:"http://mootools.net/blog/2011/02/25/mootools-core-more-1-3-1/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 25 Feb 2011 20:05:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:3:"All";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"http://mootools.net/blog/?p=1249";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:301:"The MooTools team is very happy to announce a simultaneous update of both Core and More repositories. The past year was amazing for us. We had a great hackathon in London, we gave you MooTools 1.3, added a lot of new people to our team and improved everything around the code. The results of the [...]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:6:"cpojer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:2926:"<p>The MooTools team is very happy to announce a simultaneous update of both Core and More repositories. The past year was amazing for us. We had a great hackathon in London, we gave you MooTools 1.3, added a lot of new people to our team and improved everything around the code. The results of the MooTools survey clearly showed that we are doing the right things and we intend to make MooTools even better in 2011. We spent the past weeks fixing bugs and adding new features on both projects. This is what&#8217;s new:</p>

<h3>Changes</h3>

<ul>
<li>Lots (and by that I mean LOTS) of documentation improvements, clarifications and cleanups</li>
<li>Updated Slick to 1.1.5 and improved the speed of our Slick selector engine</li>
<li>Added delegation support for <code>submit</code>, <code>focus</code>, <code>blur</code>, <code>reset</code>, <code>change</code> and <code>select</code> events in MooTools More</li>
<li>If available the native JSON methods are now used in JSON.decode and JSON.encode</li>
<li>Multiple Pseudos click:relay(a):once <a href="http://mootools.net/demos/?demo=Element.Event.Pseudos">(demo)</a></li>
<li>Two new <a href="http://mootools.net/docs/more/Class/Events.Pseudos#Pseudos:throttle">pseudo events</a>: <code>:throttle</code> and <code>:pause</code></li>
<li>Added String.truncate to String.Extras in More</li>
<li>More than two hundred changes to increase the stability of both <a href="https://github.com/mootools/mootools-core/compare/1.3...1.3.1">Core</a> &amp; <a href="https://github.com/mootools/mootools-more/compare/1.3.0.1...1.3.1.1">More</a></li>
</ul>

<p>I am also pleased to announce our newest addition to the MooTools More team, <a href="http://twitter.com/#!/fat">Jacob Thornton</a>, who is a great developer, currently working for Twitter. He has put a substantial amount of work into making MooTools More even better.</p>

<p>Be sure to check out the updated demos in our new <a href="http://mootools.net/demos/">demos section</a>.</p>

<h3>Get it!</h3>

<ul>
<li><a href="http://mootools.net/download">Download MooTools Core 1.3.1</a>; <a href="http://mootools.net/core/">Build MooTools Core 1.3.1</a></li>
<li><a href="http://mootools.net/more/">Build MooTools More 1.3.1.1</a></li>
<li>Fork / clone <a href="http://github.com/mootools/mootools-core/tree/1.3.1">MooTools 1.3.1 from GitHub</a>, and build it yourself with <a href="http://github.com/kamicane/packager">Packager</a>.</li>
<li><a href="http://github.com/mootools/mootools-core/commits/1.3.1">Read the commit logs</a> to see precisely what has changed.</li>
<li><a href="http://mootools.net/docs">Browse the Documentation for Core &amp; More.</a></li>
<li>Please report any bugs you can find on <a href="https://mootools.lighthouseapp.com/projects/2706-mootools/tickets">Lighthouse</a>, our bug tracker.</li>
</ul>
<img src="http://feeds.feedburner.com/~r/mootools-blog/~4/X_T4x6_HHF0" height="1" width="1"/>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:66:"http://mootools.net/blog/2011/02/25/mootools-core-more-1-3-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:2:"11";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:8:"origLink";a:1:{i:0;a:5:{s:4:"data";s:61:"http://mootools.net/blog/2011/02/25/mootools-core-more-1-3-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:6:"hourly";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:2:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";s:4:"href";s:41:"http://feeds.feedburner.com/mootools-blog";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:2:{s:3:"rel";s:3:"hub";s:4:"href";s:32:"http://pubsubhubbub.appspot.com/";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:42:"http://rssnamespace.org/feedburner/ext/1.0";a:1:{s:4:"info";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:1:{s:3:"uri";s:13:"mootools-blog";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";a:11:{s:12:"content-type";s:23:"text/xml; charset=UTF-8";s:4:"etag";s:27:"VkOqS7nk3ynhNy0gv6Nx/D7Y6s8";s:13:"last-modified";s:29:"Tue, 13 Dec 2011 21:31:42 GMT";s:16:"content-encoding";s:4:"gzip";s:17:"transfer-encoding";s:7:"chunked";s:4:"date";s:29:"Tue, 13 Dec 2011 21:40:53 GMT";s:7:"expires";s:29:"Tue, 13 Dec 2011 21:40:53 GMT";s:13:"cache-control";s:18:"private, max-age=0";s:22:"x-content-type-options";s:7:"nosniff";s:16:"x-xss-protection";s:13:"1; mode=block";s:6:"server";s:3:"GSE";}s:5:"build";s:14:"20090627192103";}