<?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: Prototype Changes</title>
	<atom:link href="http://ajaxian.com/archives/prototype-changes/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/prototype-changes</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: StarBoy</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-257781</link>
		<dc:creator>StarBoy</dc:creator>
		<pubDate>Fri, 26 Oct 2007 14:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-257781</guid>
		<description>I&#039;ve solved the same problem,  in an application which uses Prototype and jQuerry at same time (this if the case for the UI TABS Library used in conjunction with SCRIPT.ACULO.US portal Boxes). The Solutions is very simple

In the JQUERRY SIDE
1) First you need call the jQuery.noConflict() method
and replace all the $ by jQuery, example

If we have something  like this:

	$( function(){
		$(&#039;#container-0 ul&#039;).tabs({ disabled: [] });
	});

Replace it by this:

        jQuery.noConflict(); 
	jQuery( function(){
		jQuery(&#039;#container-0 ul&#039;).tabs({ disabled: [] });
	}); 

Do this for ALL function files which use JQUERY

IN THE PROTOTYPE SIDE:

2) Replace the &quot;function $(&quot; definition in the prototype.js file
and in all parts in that file which uses $(, by said, $X

then the line 1249 of the prototype.js file which looked:

    function $(element) {

will look now:

    function $X(element) {

do the same in all function-calls &quot;$(&quot; in prototype.js

3) Do the same in all function-calls &quot;$(&quot; in all JavaScript files which uses Prototype.
 
It should work fine ;)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve solved the same problem,  in an application which uses Prototype and jQuerry at same time (this if the case for the UI TABS Library used in conjunction with SCRIPT.ACULO.US portal Boxes). The Solutions is very simple</p>
<p>In the JQUERRY SIDE<br />
1) First you need call the jQuery.noConflict() method<br />
and replace all the $ by jQuery, example</p>
<p>If we have something  like this:</p>
<p>	$( function(){<br />
		$(&#8216;#container-0 ul&#8217;).tabs({ disabled: [] });<br />
	});</p>
<p>Replace it by this:</p>
<p>        jQuery.noConflict();<br />
	jQuery( function(){<br />
		jQuery(&#8216;#container-0 ul&#8217;).tabs({ disabled: [] });<br />
	}); </p>
<p>Do this for ALL function files which use JQUERY</p>
<p>IN THE PROTOTYPE SIDE:</p>
<p>2) Replace the &#8220;function $(&#8221; definition in the prototype.js file<br />
and in all parts in that file which uses $(, by said, $X</p>
<p>then the line 1249 of the prototype.js file which looked:</p>
<p>    function $(element) {</p>
<p>will look now:</p>
<p>    function $X(element) {</p>
<p>do the same in all function-calls &#8220;$(&#8221; in prototype.js</p>
<p>3) Do the same in all function-calls &#8220;$(&#8221; in all JavaScript files which uses Prototype.</p>
<p>It should work fine ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kingsley Joseph</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78985</link>
		<dc:creator>Kingsley Joseph</dc:creator>
		<pubDate>Thu, 31 Aug 2006 18:04:17 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78985</guid>
		<description>@Sad Developer: Real coders read code ;) I agree, Prototype&#039;s trailing jQuery on documentation - but that&#039;s also because it&#039;s far more capable. But for the average SOB like me who doesn&#039;t need that much jQuery&#039;s where it&#039;s at.</description>
		<content:encoded><![CDATA[<p>@Sad Developer: Real coders read code ;) I agree, Prototype&#8217;s trailing jQuery on documentation &#8211; but that&#8217;s also because it&#8217;s far more capable. But for the average SOB like me who doesn&#8217;t need that much jQuery&#8217;s where it&#8217;s at.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BorkWeb &#187; Prototype Changes</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78889</link>
		<dc:creator>BorkWeb &#187; Prototype Changes</dc:creator>
		<pubDate>Thu, 31 Aug 2006 13:47:33 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78889</guid>
		<description>[...] I found this article via Ajaxian regarding a nice block of Prototype updates. [...]</description>
		<content:encoded><![CDATA[<p>[...] I found this article via Ajaxian regarding a nice block of Prototype updates. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mejoras en Prototype - aNieto2K</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78794</link>
		<dc:creator>Mejoras en Prototype - aNieto2K</dc:creator>
		<pubDate>Thu, 31 Aug 2006 09:22:21 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78794</guid>
		<description>[...] Prototype ha realizado una serie de mejoras en su cÃ³digo para conseguir la posibilidad de encadenamiento de funciones entre otras mejoras. [...]</description>
		<content:encoded><![CDATA[<p>[...] Prototype ha realizado una serie de mejoras en su cÃ³digo para conseguir la posibilidad de encadenamiento de funciones entre otras mejoras. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sad developer</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78775</link>
		<dc:creator>Sad developer</dc:creator>
		<pubDate>Thu, 31 Aug 2006 08:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78775</guid>
		<description>Unfortunately, what these people still don&#039;t get is that at some point, we need proper documentation... are you all too wet2.0 when you have to read the actual library to find out what you can do with it?</description>
		<content:encoded><![CDATA[<p>Unfortunately, what these people still don&#8217;t get is that at some point, we need proper documentation&#8230; are you all too wet2.0 when you have to read the actual library to find out what you can do with it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gonzalo</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78774</link>
		<dc:creator>Gonzalo</dc:creator>
		<pubDate>Thu, 31 Aug 2006 08:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78774</guid>
		<description>Chainability is nice, but it can get abused too easily.

Is that code, with observe and setStyle chained, really clearer than having it in two lines? Are both actions related somehow so that conceptually it makes more sense chaining them together?</description>
		<content:encoded><![CDATA[<p>Chainability is nice, but it can get abused too easily.</p>
<p>Is that code, with observe and setStyle chained, really clearer than having it in two lines? Are both actions related somehow so that conceptually it makes more sense chaining them together?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Logs</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78761</link>
		<dc:creator>Google Logs</dc:creator>
		<pubDate>Thu, 31 Aug 2006 06:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78761</guid>
		<description>better option is  to use Prototype and jQuery along... 
but, you just need to replace prototype $() function by some other name to prevent conflict with jQuery $() function...
its fun and max problems are solved.</description>
		<content:encoded><![CDATA[<p>better option is  to use Prototype and jQuery along&#8230;<br />
but, you just need to replace prototype $() function by some other name to prevent conflict with jQuery $() function&#8230;<br />
its fun and max problems are solved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Haley</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78667</link>
		<dc:creator>Jason Haley</dc:creator>
		<pubDate>Thu, 31 Aug 2006 02:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78667</guid>
		<description>&lt;strong&gt;Interesting Finds: August 30, 2006&lt;/strong&gt;

</description>
		<content:encoded><![CDATA[<p><strong>Interesting Finds: August 30, 2006</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: henrah</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78652</link>
		<dc:creator>henrah</dc:creator>
		<pubDate>Thu, 31 Aug 2006 02:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78652</guid>
		<description>&lt;blockquote&gt;My first reaction also, chainability, table elements, all part of jquery pre 1.0&lt;/blockquote&gt;
Well pack it up guys, I guess jQuery wins the internet.

Seriously, what is your point?</description>
		<content:encoded><![CDATA[<blockquote><p>My first reaction also, chainability, table elements, all part of jquery pre 1.0</p></blockquote>
<p>Well pack it up guys, I guess jQuery wins the internet.</p>
<p>Seriously, what is your point?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gilles</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78253</link>
		<dc:creator>Gilles</dc:creator>
		<pubDate>Wed, 30 Aug 2006 20:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78253</guid>
		<description>My first reaction also, chainability, table elements, all part of jquery pre 1.0</description>
		<content:encoded><![CDATA[<p>My first reaction also, chainability, table elements, all part of jquery pre 1.0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78235</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 30 Aug 2006 19:20:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78235</guid>
		<description>Woot!

Prototype has been lagging lately, finally some activity!  It&#039;s still the king as far as I&#039;m concerned, there are lots of good alternatives now.</description>
		<content:encoded><![CDATA[<p>Woot!</p>
<p>Prototype has been lagging lately, finally some activity!  It&#8217;s still the king as far as I&#8217;m concerned, there are lots of good alternatives now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .mario</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-78231</link>
		<dc:creator>.mario</dc:creator>
		<pubDate>Wed, 30 Aug 2006 19:11:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-78231</guid>
		<description>Yep - and that&#039;s prototype&#039;s only chance to catch up with jQuery. I hope development in this direction will continue - always in scope to be more lightweight and performant.</description>
		<content:encoded><![CDATA[<p>Yep &#8211; and that&#8217;s prototype&#8217;s only chance to catch up with jQuery. I hope development in this direction will continue &#8211; always in scope to be more lightweight and performant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kingsley Joseph</title>
		<link>http://ajaxian.com/archives/prototype-changes/comment-page-1#comment-77989</link>
		<dc:creator>Kingsley Joseph</dc:creator>
		<pubDate>Wed, 30 Aug 2006 18:33:41 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/prototype-changes#comment-77989</guid>
		<description>Finally, looks almost as easy as jQuery now.</description>
		<content:encoded><![CDATA[<p>Finally, looks almost as easy as jQuery now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

