<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: JavaScript Madness?</title>
	<atom:link href="http://routecafe.com/posts/javascript-madness.moccha/feed" rel="self" type="application/rss+xml" />
	<link>http://routecafe.com/posts/javascript-madness.moccha</link>
	<description>It's all about David's Blog!</description>
	<lastBuildDate>Thu, 08 Jul 2010 03:27:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: David</title>
		<link>http://routecafe.com/posts/javascript-madness.moccha/comment-page-1#comment-2394</link>
		<dc:creator>David</dc:creator>
		<pubDate>Wed, 13 Jan 2010 00:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://routecafe.com/?p=201#comment-2394</guid>
		<description>&quot;The biggest problem that you’ll probably face is the DOM and it’s API&quot;, yes... I doubt I&#039;ll run into any problems with the syntax itself but with the scarce DOM API documentation it seems impossible not running into any problems. 

One thing I noticed, I don&#039;t know if I&#039;m right or wrong but everything is an object, I grab a node or node list and it returns the node with a list of methods like attaching events etc etc. 

Quirksmode is great, checking a few things I came with a conclusion that I&#039;m still missing out more things. Like &quot;how do I know the methods available once I get an object?&quot; or &quot;how do I test in javascript?&quot; (so far I&#039;ve relied on Google Chrome&#039;s JavaScript Console), &quot;how does animation work in JavaScript?&quot; and so on. Not to mention what other objects are available like for instance there is &quot;window&quot;, &quot;document&quot;, and what else.


To be honest, I hated JavaScript myself, mostly ignorance and immature thoughts back then when I was toying with HTML and CSS and didn&#039;t know anything about PHP programming or programming at all. JavaScript for me was the devil, it had this weird complex syntax that didn&#039;t made sense with so many brackets, numbers. 

I agree with you on this one though, MDC is the most useful. It made new readers think of the DOM as a tree before introducing them to the syntax. I couldn&#039;t have done all my exercises without any visualization in my mind.</description>
		<content:encoded><![CDATA[<p>&#8220;The biggest problem that you’ll probably face is the DOM and it’s API&#8221;, yes&#8230; I doubt I&#8217;ll run into any problems with the syntax itself but with the scarce DOM API documentation it seems impossible not running into any problems. </p>
<p>One thing I noticed, I don&#8217;t know if I&#8217;m right or wrong but everything is an object, I grab a node or node list and it returns the node with a list of methods like attaching events etc etc. </p>
<p>Quirksmode is great, checking a few things I came with a conclusion that I&#8217;m still missing out more things. Like &#8220;how do I know the methods available once I get an object?&#8221; or &#8220;how do I test in javascript?&#8221; (so far I&#8217;ve relied on Google Chrome&#8217;s JavaScript Console), &#8220;how does animation work in JavaScript?&#8221; and so on. Not to mention what other objects are available like for instance there is &#8220;window&#8221;, &#8220;document&#8221;, and what else.</p>
<p>To be honest, I hated JavaScript myself, mostly ignorance and immature thoughts back then when I was toying with HTML and CSS and didn&#8217;t know anything about PHP programming or programming at all. JavaScript for me was the devil, it had this weird complex syntax that didn&#8217;t made sense with so many brackets, numbers. </p>
<p>I agree with you on this one though, MDC is the most useful. It made new readers think of the DOM as a tree before introducing them to the syntax. I couldn&#8217;t have done all my exercises without any visualization in my mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Johnson</title>
		<link>http://routecafe.com/posts/javascript-madness.moccha/comment-page-1#comment-2393</link>
		<dc:creator>Justin Johnson</dc:creator>
		<pubDate>Tue, 12 Jan 2010 23:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://routecafe.com/?p=201#comment-2393</guid>
		<description>Glad I could help mate.  

As for reference resources, you&#039;re right, they&#039;re all spread out.  I find that MDC is the most useful in general.  I believe they mark which features belong to which versions of JavaScript, which is something that you&#039;ll have to watch out for since FF now implements JavaScript 1.6 and IE is still at 1.5.  It&#039;s not a big deal, it just means that you can&#039;t reliably use the new features yet until all the browsers are on the band wagon.  In the meantime, we just have to use libraries to get around this.

The biggest problem that you&#039;ll probably face is the DOM and it&#039;s API.  Most people run up with some crap here and for good reason: it&#039;s a horrible API to begin with plus the fact that different browsers implement it differently.  For this problem, you&#039;ll want to check out quirksmode.org, specifically http://www.quirksmode.org/compatibility.html This lists off the major areas of JavaScript compared to their implementation/support in all the major browsers.  The areas are further broken down in to property/component/method which is really helpful when working without a library or when you want to do something that your library doesn&#039;t support.</description>
		<content:encoded><![CDATA[<p>Glad I could help mate.  </p>
<p>As for reference resources, you&#8217;re right, they&#8217;re all spread out.  I find that MDC is the most useful in general.  I believe they mark which features belong to which versions of JavaScript, which is something that you&#8217;ll have to watch out for since FF now implements JavaScript 1.6 and IE is still at 1.5.  It&#8217;s not a big deal, it just means that you can&#8217;t reliably use the new features yet until all the browsers are on the band wagon.  In the meantime, we just have to use libraries to get around this.</p>
<p>The biggest problem that you&#8217;ll probably face is the DOM and it&#8217;s API.  Most people run up with some crap here and for good reason: it&#8217;s a horrible API to begin with plus the fact that different browsers implement it differently.  For this problem, you&#8217;ll want to check out quirksmode.org, specifically <a href="http://www.quirksmode.org/compatibility.html" rel="nofollow">http://www.quirksmode.org/compatibility.html</a> This lists off the major areas of JavaScript compared to their implementation/support in all the major browsers.  The areas are further broken down in to property/component/method which is really helpful when working without a library or when you want to do something that your library doesn&#8217;t support.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
