<?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>indiWiz.com &#187; web</title>
	<atom:link href="http://indiwiz.com/tag/web/feed/" rel="self" type="application/rss+xml" />
	<link>http://indiwiz.com</link>
	<description>Subhash&#039;s Tech Log</description>
	<lastBuildDate>Sun, 29 Apr 2012 15:11:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>URL Shortners</title>
		<link>http://indiwiz.com/2009/12/15/url-shortners/</link>
		<comments>http://indiwiz.com/2009/12/15/url-shortners/#comments</comments>
		<pubDate>Tue, 15 Dec 2009 06:27:26 +0000</pubDate>
		<dc:creator>Subhash Chandran</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[urlshortening]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://indiwiz.com/?p=594</guid>
		<description><![CDATA[Got two news on this topic today: bit.ly starts offering premium services. Google launched a URL shortening service.]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop --><!-- End Shareaholic LikeButtonSetTop --><p>Got two news on this topic today:</p>
<ol>
<li><a href="http://bit.ly/">bit.ly</a> starts offering <a href="http://blog.bit.ly/post/284009728/announcing-bit-ly-pro">premium services</a>.</li>
<li>Google <a href="http://googleblog.blogspot.com/2009/12/making-urls-shorter-for-google-toolbar.html">launched a URL shortening service</a>.</li>
</ol>
<div class="shr-publisher-594"></div><!-- Start Shareaholic LikeButtonSetBottom --><!-- End Shareaholic LikeButtonSetBottom -->]]></content:encoded>
			<wfw:commentRss>http://indiwiz.com/2009/12/15/url-shortners/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OpenSearch search providers and browsers</title>
		<link>http://indiwiz.com/2009/11/25/opensearch-search-providers-and-browsers/</link>
		<comments>http://indiwiz.com/2009/11/25/opensearch-search-providers-and-browsers/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 05:06:10 +0000</pubDate>
		<dc:creator>Subhash Chandran</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[opensearch]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[webbrowser]]></category>

		<guid isPermaLink="false">http://indiwiz.com/?p=587</guid>
		<description><![CDATA[All the major browser vendors support the OpenSearch format (yes, this means including Microsoft IE8) for registering a search provider in your browser. Writing a OpenSearch provider Recently I wrote a search provider for my favorite book-buying site, Pustak.co.in: Hosting your search provider To let people use your search provider, you need to host it [...]]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop --><!-- End Shareaholic LikeButtonSetTop --><p>All the major browser vendors support the OpenSearch format (yes, this means including Microsoft IE8) for registering a search provider in your browser.</p>
<h4>Writing a OpenSearch provider</h4>
<p>Recently I wrote a search provider for my favorite book-buying site, <a href="http://pustak.co.in/">Pustak.co.in</a>:</p>
<pre class="brush: xml; title: ; notranslate">
&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;OpenSearchDescription xmlns=&quot;http://a9.com/-/spec/opensearch/1.1/&quot;&gt;
	&lt;ShortName&gt;Pustak.co.in&lt;/ShortName&gt;
	&lt;Description&gt;Pustak.co.in provider&lt;/Description&gt;
	&lt;InputEncoding&gt;UTF-8&lt;/InputEncoding&gt;
	&lt;Url type=&quot;text/html&quot;
		template=&quot;http://pustak.co.in/pustak/books/search?q={searchTerms}&amp;amp;type=book&amp;amp;page=1&quot;/&gt;
&lt;/OpenSearchDescription&gt;
</pre>
<h4>Hosting your search provider</h4>
<p>To let people use your search provider, you need to host it in the web. For our example, let us assume that you host it here: <em>http://yourhost/your_opensearch.xml</em>.</p>
<p>The MIME type of this document can be left to its default <em>application/xml</em>, or can be made OpenSearch specific: <em>application/opensearchdescription+xml</em>.</p>
<h4>Using JavaScript to register a provider</h4>
<p>After deploying the OpenSearch XML in your host, we need to write a JavaScript function to register the provider with your browser:</p>
<pre class="brush: jscript; title: ; notranslate">
&lt;script type=&quot;text/javascript&quot;&gt;
function registerYourSearchProvider(){
  window.external.AddSearchProvider(&quot;http://yourhost/your_opensearch.xml&quot;);
}
&lt;/script&gt;
</pre>
<p>This JavaScript worked with Firefox, IE8 and Google Chrome. Opera 10 was not able to understand it.</p>
<h4>Auto-discovering OpenSearch providers</h4>
<p>Recently when I saw my Google Chrome search providers, I saw this list:</p>
<p><a href="http://www.flickr.com/photos/subwiz/4132146183/" title="Chrome Search Providers by subWiz, on Flickr"><img src="http://farm3.static.flickr.com/2784/4132146183_4b96fbc9b2_o.png" width="485" height="394" alt="Chrome Search Providers" /></a></p>
<p>I was surprised to see this list because there are providers that I have not added specifically. How was Google Chrome &#8220;discovering&#8221; these providers?</p>
<p>A look into the HTML source of one of the auto-registering search provider, I found the following info (in the &lt;head&gt; section):</p>
<pre class="brush: xml; title: ; notranslate">
&lt;link rel=&quot;search&quot;
       href=&quot;/mavensearch.xml&quot;
       type=&quot;application/opensearchdescription+xml&quot;
       title=&quot;mavensearch.net&quot; /&gt;
</pre>
<p>To let browsers auto-discover you as a search-provider, add the above in your sites!</p>
<div class="shr-publisher-587"></div><!-- Start Shareaholic LikeButtonSetBottom --><!-- End Shareaholic LikeButtonSetBottom -->]]></content:encoded>
			<wfw:commentRss>http://indiwiz.com/2009/11/25/opensearch-search-providers-and-browsers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Most despicable web browser: IE</title>
		<link>http://indiwiz.com/2009/05/25/most-despicable-web-browser-ie/</link>
		<comments>http://indiwiz.com/2009/05/25/most-despicable-web-browser-ie/#comments</comments>
		<pubDate>Mon, 25 May 2009 04:42:54 +0000</pubDate>
		<dc:creator>Subhash Chandran</dc:creator>
				<category><![CDATA[Software Dev]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://indiwiz.com/?p=301</guid>
		<description><![CDATA[I know I am not the first person to say this. I know I am neither the last. But I am using this post to ease my indignation about a pathetic piece of engineering called IE. Recently I have been working on portlet development in Liferay. We developed a fancy portlet with Ajax and stuff [...]]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop --><!-- End Shareaholic LikeButtonSetTop --><p>I know I am not the first person to say this. I know I am neither the last. But I am using this post to ease my indignation about a pathetic piece of engineering called <a href="http://www.microsoft.com/windows/internet-explorer/">IE</a>.</p>
<p>Recently I have been working on portlet development in Liferay. We developed a fancy portlet with Ajax and stuff showing content from a Alfresco deployment. While styling the portlet, I experienced nightmare. The HTML, CSS and JavaScript we developed worked in all browsers, except IE 7. And the reasons for not working are so pathetic: nested divs, nested styling components, menu generation using lists.</p>
<p>I am wondering what kind of coding and engineering effort would have gone into making this crap of a browser called IE. As I am imagining how to write code for parsing and rendering CSS display components, I can feel the awkward code that is inside IE parsing my CSS. Something like graceful degradation and granularity of CSS styles are simple to achieve by &#8220;a little thought&#8221; while coding. But the crap inside IE makes it so complicated!</p>
<p>I wish there never was a browser called IE.</p>
<div class="shr-publisher-301"></div><!-- Start Shareaholic LikeButtonSetBottom --><!-- End Shareaholic LikeButtonSetBottom -->]]></content:encoded>
			<wfw:commentRss>http://indiwiz.com/2009/05/25/most-despicable-web-browser-ie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

