<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The JavaScript Blog &#187; Tutorials</title>
	<atom:link href="http://thejavascriptblog.com/category/tutorials/feed/" rel="self" type="application/rss+xml" />
	<link>http://thejavascriptblog.com</link>
	<description>Everything JavaScript</description>
	<lastBuildDate>Sat, 09 Jul 2011 19:16:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Remove jQuery From Your WordPress Theme</title>
		<link>http://thejavascriptblog.com/remove-jquery-from-your-wordpress-theme/</link>
		<comments>http://thejavascriptblog.com/remove-jquery-from-your-wordpress-theme/#comments</comments>
		<pubDate>Sat, 27 Nov 2010 20:44:00 +0000</pubDate>
		<dc:creator>Merrick Christensen</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://thejavascriptblog.com/?p=99</guid>
		<description><![CDATA[WordPress will generally inject jQuery into your front-end theme which in my opinion is a huge fail. Often times plugins will do it, fortunately there is a simple fix...]]></description>
			<content:encoded><![CDATA[<p>WordPress will generally inject jQuery into your front-end theme which in my opinion is a huge fail. Often times plugins will do it, fortunately there is a simple fix, just above wp_head() or inside of an init callback put:</p>
<pre>
&lt;?php
    	if ( !is_admin() ) wp_deregister_script('jquery');
?&gt;
</pre>
<p>jQuery won&#8217;t be linked anymore. Writing this post has made me start wondering if I should write a more detailed post about WP_Scripts to show how to create dependancies and registering your own scripts. Any interest?</p>
]]></content:encoded>
			<wfw:commentRss>http://thejavascriptblog.com/remove-jquery-from-your-wordpress-theme/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Developer Tools In Safari</title>
		<link>http://thejavascriptblog.com/developer-tools-in-safari/</link>
		<comments>http://thejavascriptblog.com/developer-tools-in-safari/#comments</comments>
		<pubDate>Sun, 07 Feb 2010 00:15:35 +0000</pubDate>
		<dc:creator>Merrick Christensen</dc:creator>
				<category><![CDATA[Reviews]]></category>
		<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://thejavascriptblog.com/?p=76</guid>
		<description><![CDATA[For a long time I was using Firefox just for Firebug. You know, sort of like when two people stay married for the kid. I was sick and tired of how Firefox rendering looked, hard to explain just not quite as smooth. When Chrome for Mac was released in the beta phases I was stoked&#8230; [...]]]></description>
			<content:encoded><![CDATA[<p>For a long time I was using Firefox just for Firebug. You know, sort of like when two people stay married for the kid. I was sick and tired of how Firefox rendering looked, hard to explain just not quite as smooth. When Chrome for Mac was released in the beta phases I was stoked&#8230; Until I saw the UI, now this is debatable but I would much rather have the looks of Safari then Chrome any day. All I really wanted was a good inspector and some nice things from the web developer toolbar.</p>
<h2>Enter Safari Developer Tools</h2>
<p>Why did no one tell me about this soon? Everyone needs to know safari comes with a beautiful inspector (just like chromes &#8211; webkit) and some handy disabling tools. The thing is they aren&#8217;t on by default. To turn them on all you need to do is go to :</p>
<p><strong>Safari -> Preferences -> Advanced -> Show develop menu in menu bar</strong></p>
<div id="attachment_77" class="wp-caption aligncenter" style="width: 310px"><a href="http://thejavascriptblog.com/wp-content/uploads/2010/02/Screen-shot-2010-02-06-at-5.12.41-PM.png"><img src="http://thejavascriptblog.com/wp-content/uploads/2010/02/Screen-shot-2010-02-06-at-5.12.41-PM-300x175.png" alt="" title="Screen shot 2010-02-06 at 5.12.41 PM" width="300" height="175" class="size-medium wp-image-77" /></a><p class="wp-caption-text">You get some nice things like User-Agent changing, Snippet Editors, Console Logging, Inspector, and much more.</p></div>
<p>Goodbye Firefox. It was good while it lasted, but we both know this relationship has been over for a long time.</p>
]]></content:encoded>
			<wfw:commentRss>http://thejavascriptblog.com/developer-tools-in-safari/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>WTFramework &#8211; Detect Which Framework A Site Is Using, The Easy Way</title>
		<link>http://thejavascriptblog.com/wtframework-detect-which-framework-a-site-is-using-the-easy-way/</link>
		<comments>http://thejavascriptblog.com/wtframework-detect-which-framework-a-site-is-using-the-easy-way/#comments</comments>
		<pubDate>Sun, 27 Dec 2009 20:20:02 +0000</pubDate>
		<dc:creator>Merrick Christensen</dc:creator>
				<category><![CDATA[Reviews]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://thejavascriptblog.com/?p=71</guid>
		<description><![CDATA[WTFramework Summary WTFramework is a dead simple, and well designed way to detect which framework a site is using as well as version. Being primarily a JavaScript developer I was always looking through the source to find which framework a certain site was using. Or to see if the developer had done something particularly cool [...]]]></description>
			<content:encoded><![CDATA[<h2>WTFramework Summary</h2>
<p>WTFramework is a dead simple, and well designed way to detect which framework a site is using as well as version. Being primarily a JavaScript developer I was always looking through the source to find which framework a certain site was using. Or to see if the developer had done something particularly cool with my favorite framework <a href="http://mootools.net" target="_blank">MooTools</a>. </p>
<p>It was developed by <a href="http://twitter.com/oskar">Oskar Krawczyk</a> and is implemented as a bookmark for any A grade browser. You simply drag it into your bookmarks bar and its installed. You can now use it on any site you visit. The notifications are &#8220;Growl&#8221; like and are very well designed. </p>
<p>Kudos to Oskar on this one, a dead simple, but time saving tool.</p>
<h2>Installation</h2>
<ol>
<li><a href="http://nouincolor.com/wtframework/2.0/">Visit The Site</a></li>
<li>Drag the big red icon into your bookmarks.</li>
<li>It is now installed.</li>
</ol>
<h2>Fortunately For Us</h2>
<p>Oskar has a public Git Hub repository for this. So if needs be you can change it to suit your needs.</p>
<h2>Gallery</h2>

<a href='http://thejavascriptblog.com/wtframework-detect-which-framework-a-site-is-using-the-easy-way/screen-shot-2009-12-29-at-7-15-25-pm/' title='Screen shot 2009-12-29 at 7.15.25 PM'><img width="150" height="150" src="http://thejavascriptblog.com/wp-content/uploads/2009/12/Screen-shot-2009-12-29-at-7.15.25-PM-150x150.png" class="attachment-thumbnail" alt="Screen shot 2009-12-29 at 7.15.25 PM" title="Screen shot 2009-12-29 at 7.15.25 PM" /></a>
<a href='http://thejavascriptblog.com/wtframework-detect-which-framework-a-site-is-using-the-easy-way/screen-shot-2009-12-29-at-7-16-01-pm/' title='Screen shot 2009-12-29 at 7.16.01 PM'><img width="150" height="150" src="http://thejavascriptblog.com/wp-content/uploads/2009/12/Screen-shot-2009-12-29-at-7.16.01-PM-150x150.png" class="attachment-thumbnail" alt="Screen shot 2009-12-29 at 7.16.01 PM" title="Screen shot 2009-12-29 at 7.16.01 PM" /></a>

]]></content:encoded>
			<wfw:commentRss>http://thejavascriptblog.com/wtframework-detect-which-framework-a-site-is-using-the-easy-way/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Making Every Specified Link Send Via Ajax Using MooTools</title>
		<link>http://thejavascriptblog.com/making-every-specified-link-send-via-ajax-using-mootools/</link>
		<comments>http://thejavascriptblog.com/making-every-specified-link-send-via-ajax-using-mootools/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 05:44:24 +0000</pubDate>
		<dc:creator>Merrick Christensen</dc:creator>
				<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://thejavascriptblog.com/?p=67</guid>
		<description><![CDATA[This is a relatively simple concept and is nothing to elaborate but I wanted to share a small piece of code that will take every link with the class of &#8220;ajax&#8221; and access it using AJAX instead of actually going to that page. This using the same Request instance which will keep it optimized and [...]]]></description>
			<content:encoded><![CDATA[<p>This is a relatively simple concept and is nothing to elaborate but I wanted to share a small piece of code that will take every link with the class of &#8220;ajax&#8221; and access it using AJAX instead of actually going to that page. This using the same Request instance which will keep it optimized and manageable. MooTools is going to make this nice and easy on us&#8230;</p>
<h2>Usage</h2>
<h3>JavaScript</h3>
<pre>
var ajax_request = new Request(
{
	onSuccess: function(responseText, responseXML)
	{
		$('message').set('html', responseText);
	}
});

$$('.ajax').each(function(item){
	var url = item.get('href');
	item.addEvent('click', function(event){
		ajax_request.options.url = url;
		ajax_request.send();
		return false;
	});
});
</pre>
<h3>HTML</h3>
<pre>
<a href="ajax.php" class="ajax">Sent Via AJAX</a>
<a href="ajax_alternative.php" class="ajax">Also Sent Via AJAX</a>
<div id="message">I am filled with the results of our AJAX requests.</div>
</pre>
<p>Its incredibly simple so no demo for this. The important concept here is that we are using the same request and pulling the href attribute base on a class selection. So changing something from AJAX to regular is as easy as adding or removing the class &#8220;ajax&#8221;. Pretty cool eh?</p>
]]></content:encoded>
			<wfw:commentRss>http://thejavascriptblog.com/making-every-specified-link-send-via-ajax-using-mootools/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

