<?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: JavaRef: Ajaxified JavaDoc</title>
	<atom:link href="http://ajaxian.com/archives/javaref-ajaxified-javadoc/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc</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: iface thoughts &#187; Blog Archive &#187; Javaref</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-92789</link>
		<dc:creator>iface thoughts &#187; Blog Archive &#187; Javaref</dc:creator>
		<pubDate>Thu, 14 Sep 2006 18:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-92789</guid>
		<description>[...] I think Javaref (via Ajaxian) displays one of the best uses of AJAX. It has injected usability and ease in refering to the Java documentation.   So welcome to the Web 2.0 JavaDoc. The default way of looking up is searching. This is made easier with features like autocomplete.  Java API documentation are displayed in a style that is radically different from the classic javadoc style that ships with the JDK. The documentation includes class source code (where available), ability to leave user notes and ability to transparently navigate between APIs by following code references. [...]</description>
		<content:encoded><![CDATA[<p>[...] I think Javaref (via Ajaxian) displays one of the best uses of AJAX. It has injected usability and ease in refering to the Java documentation.   So welcome to the Web 2.0 JavaDoc. The default way of looking up is searching. This is made easier with features like autocomplete.  Java API documentation are displayed in a style that is radically different from the classic javadoc style that ships with the JDK. The documentation includes class source code (where available), ability to leave user notes and ability to transparently navigate between APIs by following code references. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WorldTechLogic</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-46720</link>
		<dc:creator>WorldTechLogic</dc:creator>
		<pubDate>Sat, 15 Jul 2006 07:33:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-46720</guid>
		<description>We have replied Angsuman&#039;s request to remove his articles from our website :)</description>
		<content:encoded><![CDATA[<p>We have replied Angsuman&#8217;s request to remove his articles from our website :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angsuman Chakraborty</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-42472</link>
		<dc:creator>Angsuman Chakraborty</dc:creator>
		<pubDate>Fri, 07 Jul 2006 21:38:12 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-42472</guid>
		<description>Your full content is being plagiarized by worldtechlogic.com. For example this article has been copied in ditto at:
http://worldtechlogic.com/2006/06/29/javaref-ajaxified-javadoc/

He has also copied several of my articles and of several other people.
You can see the articles he has copied from my blog here -
http://worldtechlogic.com/index.php?s=angsuman&amp;submit=

This is a sample of the article he copied from your :)
http://worldtechlogic.com/index.php?s=ajaxian&amp;submit=

Frankly I don&#039;t know what to do with him. It is surely not nice to copy our articles. What do you suggest? I tried contacting him but be doesn&#039;t reply.</description>
		<content:encoded><![CDATA[<p>Your full content is being plagiarized by worldtechlogic.com. For example this article has been copied in ditto at:<br />
<a href="http://worldtechlogic.com/2006/06/29/javaref-ajaxified-javadoc/" rel="nofollow">http://worldtechlogic.com/2006/06/29/javaref-ajaxified-javadoc/</a></p>
<p>He has also copied several of my articles and of several other people.<br />
You can see the articles he has copied from my blog here -<br />
<a href="http://worldtechlogic.com/index.php?s=angsuman&#038;submit" rel="nofollow">http://worldtechlogic.com/index.php?s=angsuman&#038;submit</a>=</p>
<p>This is a sample of the article he copied from your :)<br />
<a href="http://worldtechlogic.com/index.php?s=ajaxian&#038;submit" rel="nofollow">http://worldtechlogic.com/index.php?s=ajaxian&#038;submit</a>=</p>
<p>Frankly I don&#8217;t know what to do with him. It is surely not nice to copy our articles. What do you suggest? I tried contacting him but be doesn&#8217;t reply.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: webthreads.de &#187; Javaref - browse JavaDoc the Ajax way</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-38789</link>
		<dc:creator>webthreads.de &#187; Javaref - browse JavaDoc the Ajax way</dc:creator>
		<pubDate>Fri, 30 Jun 2006 08:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-38789</guid>
		<description>[...] (via Ajaxian) [...]</description>
		<content:encoded><![CDATA[<p>[...] (via Ajaxian) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-38627</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Thu, 29 Jun 2006 20:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-38627</guid>
		<description>There&#039;s no need for something like this. The standard javadocs work fine off the web, and even better if you download them.</description>
		<content:encoded><![CDATA[<p>There&#8217;s no need for something like this. The standard javadocs work fine off the web, and even better if you download them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie Hubbard</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-38617</link>
		<dc:creator>Charlie Hubbard</dc:creator>
		<pubDate>Thu, 29 Jun 2006 20:03:50 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-38617</guid>
		<description>Really good idea, but I think the old javadoc is probably more usable.  I don&#039;t like the advertising mixed so closely with the docs.  It&#039;s just too noisy for small APIs.  I&#039;d rather see it moved over to the right like Google does it.  Also let the frame fill the entire screen.  800x600 or 1024x768 is too limiting.  Let it flow.  I like the source code tab in there that&#039;s really nice.</description>
		<content:encoded><![CDATA[<p>Really good idea, but I think the old javadoc is probably more usable.  I don&#8217;t like the advertising mixed so closely with the docs.  It&#8217;s just too noisy for small APIs.  I&#8217;d rather see it moved over to the right like Google does it.  Also let the frame fill the entire screen.  800&#215;600 or 1024&#215;768 is too limiting.  Let it flow.  I like the source code tab in there that&#8217;s really nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john Parker</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-38486</link>
		<dc:creator>john Parker</dc:creator>
		<pubDate>Thu, 29 Jun 2006 16:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-38486</guid>
		<description>Most people don&#039;t realize that the standard Sun JDK and JEE javadocs are copyrighted and Sun does not allow other sites to host them.

Full marks to Javaref.com for abiding by that and not creating a jdoc.com like fiasco!</description>
		<content:encoded><![CDATA[<p>Most people don&#8217;t realize that the standard Sun JDK and JEE javadocs are copyrighted and Sun does not allow other sites to host them.</p>
<p>Full marks to Javaref.com for abiding by that and not creating a jdoc.com like fiasco!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-38463</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Thu, 29 Jun 2006 14:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-38463</guid>
		<description>How could they not even include the standard java and jsp/servlet javadocs?</description>
		<content:encoded><![CDATA[<p>How could they not even include the standard java and jsp/servlet javadocs?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: code::gallery :: Javaref :: June :: 2006</title>
		<link>http://ajaxian.com/archives/javaref-ajaxified-javadoc/comment-page-1#comment-38449</link>
		<dc:creator>code::gallery :: Javaref :: June :: 2006</dc:creator>
		<pubDate>Thu, 29 Jun 2006 14:10:34 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1315#comment-38449</guid>
		<description>[...] I think Javaref (via Ajaxian)shows one of the most perfect use of AJAX. It has injected usability and ease in refering to the Java documentation. [...]</description>
		<content:encoded><![CDATA[<p>[...] I think Javaref (via Ajaxian)shows one of the most perfect use of AJAX. It has injected usability and ease in refering to the Java documentation. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

