<?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 for Hacking at 0300</title>
	<atom:link href="http://bililite.nfshost.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://bililite.nfshost.com/blog</link>
	<description>Thoughts on web design and programming from a very occasional volunteer webmaster</description>
	<lastBuildDate>Fri, 03 Feb 2012 05:24:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Cross-Browser Text Ranges and Selections by Danny</title>
		<link>http://bililite.nfshost.com/blog/2011/01/17/cross-browser-text-ranges-and-selections/comment-page-1/#comment-14529</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Fri, 03 Feb 2012 05:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?p=1404#comment-14529</guid>
		<description>@Hadar:
I&#039;m not sure what you mean. I&#039;m getting the text inserted correctly with the code as is. What browser are you using?
--Danny</description>
		<content:encoded><![CDATA[<p>@Hadar:<br />
I&#8217;m not sure what you mean. I&#8217;m getting the text inserted correctly with the code as is. What browser are you using?<br />
&#8211;Danny</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cross-Browser Text Ranges and Selections by Hadar</title>
		<link>http://bililite.nfshost.com/blog/2011/01/17/cross-browser-text-ranges-and-selections/comment-page-1/#comment-14480</link>
		<dc:creator>Hadar</dc:creator>
		<pubDate>Thu, 02 Feb 2012 12:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?p=1404#comment-14480</guid>
		<description>thanks for the great plugin.
I found a bug though, where it was inserting the text only to the begining of the contenteditable div.
the textProp function should have the line &quot;el.text&quot; removed, since el.text is not related to the content but rather to the color.
removing the line solved the issue.</description>
		<content:encoded><![CDATA[<p>thanks for the great plugin.<br />
I found a bug though, where it was inserting the text only to the begining of the contenteditable div.<br />
the textProp function should have the line &#8220;el.text&#8221; removed, since el.text is not related to the content but rather to the color.<br />
removing the line solved the issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hacking My Way to an Amazon Wishlist Widget by Searching your Amazon.com Wish List &#171; Code In Chinese</title>
		<link>http://bililite.nfshost.com/blog/2010/10/31/hacking-my-way-to-an-amazon-wishlist-widget/comment-page-1/#comment-14201</link>
		<dc:creator>Searching your Amazon.com Wish List &#171; Code In Chinese</dc:creator>
		<pubDate>Wed, 25 Jan 2012 18:52:47 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?p=1227#comment-14201</guid>
		<description>[...] recently removed wish list querying methods from their API. Bummer. Then I came upon this post. http://bililite.nfshost.com/blog/2010/10/31/hacking-my-way-to-an-amazon-wishlist-widget/ . The solution is the layout=compact URL [...]</description>
		<content:encoded><![CDATA[<p>[...] recently removed wish list querying methods from their API. Bummer. Then I came upon this post. <a href="http://bililite.nfshost.com/blog/2010/10/31/hacking-my-way-to-an-amazon-wishlist-widget/" rel="nofollow">http://bililite.nfshost.com/blog/2010/10/31/hacking-my-way-to-an-amazon-wishlist-widget/</a> . The solution is the layout=compact URL [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on jQuery CSS parser by Hacking at 0300 : jQuery CSS parser - EtondeGroup Blog of Web Applications &#124; EtondeGroup Blog of Web Applications</title>
		<link>http://bililite.nfshost.com/blog/2009/01/16/jquery-css-parser/comment-page-1/#comment-13720</link>
		<dc:creator>Hacking at 0300 : jQuery CSS parser - EtondeGroup Blog of Web Applications &#124; EtondeGroup Blog of Web Applications</dc:creator>
		<pubDate>Fri, 13 Jan 2012 12:39:50 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?p=251#comment-13720</guid>
		<description>[...] more here: Hacking at 0300 : jQuery CSS parser  Bookmark on Delicious Digg this post Recommend on Facebook share via Reddit Share with Stumblers [...]</description>
		<content:encoded><![CDATA[<p>[...] more here: Hacking at 0300 : jQuery CSS parser  Bookmark on Delicious Digg this post Recommend on Facebook share via Reddit Share with Stumblers [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Back to a Simple Google Search Form by Nick Lachey</title>
		<link>http://bililite.nfshost.com/blog/2011/02/23/back-to-a-simple-google-search-form/comment-page-1/#comment-13614</link>
		<dc:creator>Nick Lachey</dc:creator>
		<pubDate>Wed, 11 Jan 2012 13:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?p=1607#comment-13614</guid>
		<description>Nice post. I found this blog with with best practices for creating a search form that is quick and easy to use      http://blog.caspio.com/web-database/7-tips-for-creating-user-friendly-search-forms/</description>
		<content:encoded><![CDATA[<p>Nice post. I found this blog with with best practices for creating a search form that is quick and easy to use      <a href="http://blog.caspio.com/web-database/7-tips-for-creating-user-friendly-search-forms/" rel="nofollow">http://blog.caspio.com/web-database/7-tips-for-creating-user-friendly-search-forms/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Parsing the HTTP Accept: header by Parsing the HTTP Accept: header</title>
		<link>http://bililite.nfshost.com/blog/2010/01/06/parsing-the-http-accept-header/comment-page-1/#comment-13243</link>
		<dc:creator>Parsing the HTTP Accept: header</dc:creator>
		<pubDate>Sat, 31 Dec 2011 05:53:30 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?p=1126#comment-13243</guid>
		<description>[...] http://bililite.nfshost.com/blog/2010/01/06/parsing-the-http-accept-header/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://bililite.nfshost.com/blog/2010/01/06/parsing-the-http-accept-header/" rel="nofollow">http://bililite.nfshost.com/blog/2010/01/06/parsing-the-http-accept-header/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Understanding jQuery UI widgets: A tutorial by Danny</title>
		<link>http://bililite.nfshost.com/blog/understanding-jquery-ui-widgets-a-tutorial/comment-page-2/#comment-12008</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Fri, 09 Dec 2011 18:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?page_id=286#comment-12008</guid>
		<description>@Rafi:
Your comment is just an advertisement for your own set of widgets, which as far as I can tell to not even use jQuery UI. But they look cool and may give people ideas for their own widgets, so I&#039;ll let it slide.</description>
		<content:encoded><![CDATA[<p>@Rafi:<br />
Your comment is just an advertisement for your own set of widgets, which as far as I can tell to not even use jQuery UI. But they look cool and may give people ideas for their own widgets, so I&#8217;ll let it slide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Understanding jQuery UI widgets: A tutorial by Rafi</title>
		<link>http://bililite.nfshost.com/blog/understanding-jquery-ui-widgets-a-tutorial/comment-page-2/#comment-11970</link>
		<dc:creator>Rafi</dc:creator>
		<pubDate>Fri, 09 Dec 2011 03:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?page_id=286#comment-11970</guid>
		<description>Professionally developed and ready to use jQuery widgets.</description>
		<content:encoded><![CDATA[<p>Professionally developed and ready to use jQuery widgets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Understanding jQuery UI widgets: A tutorial by Danny</title>
		<link>http://bililite.nfshost.com/blog/understanding-jquery-ui-widgets-a-tutorial/comment-page-2/#comment-11965</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Fri, 09 Dec 2011 00:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?page_id=286#comment-11965</guid>
		<description>@Chemises homme (I assume you are a real person who designed that site):
Yes, for turning the color off and on in real life you would use a simple toggle. That was simply an example of how to create a widget; the example needed to be simple enough to not &quot;get in the way&quot; of the explanation. Actual widgets would be far more complex and need to store state and respond to events.
--Danny</description>
		<content:encoded><![CDATA[<p>@Chemises homme (I assume you are a real person who designed that site):<br />
Yes, for turning the color off and on in real life you would use a simple toggle. That was simply an example of how to create a widget; the example needed to be simple enough to not &#8220;get in the way&#8221; of the explanation. Actual widgets would be far more complex and need to store state and respond to events.<br />
&#8211;Danny</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Understanding jQuery UI widgets: A tutorial by Chemises homme</title>
		<link>http://bililite.nfshost.com/blog/understanding-jquery-ui-widgets-a-tutorial/comment-page-2/#comment-11929</link>
		<dc:creator>Chemises homme</dc:creator>
		<pubDate>Thu, 08 Dec 2011 10:25:30 +0000</pubDate>
		<guid isPermaLink="false">http://bililite.nfshost.com/blog/?page_id=286#comment-11929</guid>
		<description>Thank dany but, 
why you don&#039;t use the toggle function ?</description>
		<content:encoded><![CDATA[<p>Thank dany but,<br />
why you don&#8217;t use the toggle function ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

