<?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>Softcore software development &#187; hugs</title>
	<atom:link href="http://tea.cesaroliveira.net/archives/tag/hugs/feed" rel="self" type="application/rss+xml" />
	<link>http://tea.cesaroliveira.net</link>
	<description>It&#039;s all about the cycles</description>
	<lastBuildDate>Sun, 01 Aug 2010 02:04:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Reordering the tab key &#8211; tabcomplete</title>
		<link>http://tea.cesaroliveira.net/archives/220</link>
		<comments>http://tea.cesaroliveira.net/archives/220#comments</comments>
		<pubDate>Sun, 01 Aug 2010 02:04:06 +0000</pubDate>
		<dc:creator>Cesar</dc:creator>
				<category><![CDATA[addons]]></category>
		<category><![CDATA[extension]]></category>
		<category><![CDATA[hugs]]></category>
		<category><![CDATA[keyboard]]></category>
		<category><![CDATA[tab]]></category>
		<category><![CDATA[tabcomplete]]></category>

		<guid isPermaLink="false">http://tea.cesaroliveira.net/?p=220</guid>
		<description><![CDATA[I am in the process of creating a new Firefox add-on that will hopefully change a bit how we navigate some sites. Until now, keyboard navigation for the vast majority of sites has been simply unusable. Even though websites have a layout that can easily use a keyboard, it often relies on either remembering shortcuts [...]]]></description>
			<content:encoded><![CDATA[<p>I am in the process of creating a new Firefox add-on that will hopefully change a bit how we navigate some sites. Until now, keyboard navigation for the vast majority of sites has been simply unusable. Even though websites have a layout that can easily use a keyboard, it often relies on either remembering shortcuts or tabbing through. You are almost exclusively limited to a mouse when using a full-featured browser such as Firefox, Chrome, and IE.</p>
<p>Personally, I hate using the trackpad on my laptop. After extended use, the heat and the friction take a toll on my fingers. I have an external USB mouse, but that often becomes a bother as the laptop is moved around from one location to another. Yes, wireless mice, but again we&#8217;re not really fixing the problem.</p>
<p>For simple navigation, it&#8217;s almost a crime that I cannot tab between links and major components of a web site&#8217;s navigation.</p>
<p>The <a href="http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex" onclick="pageTracker._trackPageview('/outgoing/www.w3.org/TR/html401/interact/forms.html_adef-tabindex?referer=');">tabindex</a> HTML attribute has gone largely unused when browsing the web. Perhaps for a myriad of reasons &#8211; it&#8217;s hard to re-order manually, and for many web developers it&#8217;s not worth the time or effort.</p>
<p>Even for everyday use, it becomes ridiculous how crappy it the tab key can be. Think about this:</p>
<ul>
<li>For a Google search result, the tab key must be hit <em>12 time</em>s before it focuses on your search text. Another 3 tab strikes before it takes you to the first result. Another <em>5 times or more to get to the second result</em> &#8211; not counting Google&#8217;s quick links.</li>
<li>For planet.mozilla.org, each tab key will go through every anchor link in each person&#8217;s blog post. Oh, and it takes 6 tab keystrokes to go to the first article.</li>
<li>For reddit, it can be a little better. If you just use tab, you&#8217;ll go through each &#8220;share&#8221; link first. Which is stupid. If you activate &#8220;jump to content&#8221; it will go through image->link->domain->usersubreddit->comments. Which is still a lot for one result.</li>
</ul>
<p>This is how I would order the tab key on a Google search result:<br />
<div id="attachment_221" class="wp-caption aligncenter" style="width: 286px"><a href="http://tea.cesaroliveira.net/wp-content/uploads/2010/07/google-taborder.png"><img src="http://tea.cesaroliveira.net/wp-content/uploads/2010/07/google-taborder-276x300.png" alt="Possible tab order on google" title="google-taborder" width="276" height="300" class="size-medium wp-image-221" /></a><p class="wp-caption-text">Possible tab order on google</p></div></p>
<p>I would probably use the top Google bar the least when doing a google search. Each time you hit tab, it will cycle through the search box, 1st result, 2nd result, etc. until you hit n-th result.</p>
<p>This would be great in an ideal world. A Firefox extension could do this, but for my purposes my extension does not do this. It doesn&#8217;t map the tab key. It instead uses the key right above it. Like tab, CTRL+` will cycle forward and SHIFT+~ will cycle backwards.</p>
<p>I call it <a href="https://addons.mozilla.org/firefox/addon/210516/" onclick="pageTracker._trackPageview('/outgoing/addons.mozilla.org/firefox/addon/210516/?referer=');">tabcomplete</a>. It&#8217;s not as pretty as <a href="http://azarask.in/projects/tabcandy/" onclick="pageTracker._trackPageview('/outgoing/azarask.in/projects/tabcandy/?referer=');">tabcandy</a>. I think a large part of my user-base wouldn&#8217;t be most users. Users seem content on using the mouse, and that&#8217;s fine. But for a guy who works in vim, this is a nice to have extension.</p>
]]></content:encoded>
			<wfw:commentRss>http://tea.cesaroliveira.net/archives/220/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Successfully Getting your Addon Reviewed</title>
		<link>http://tea.cesaroliveira.net/archives/52</link>
		<comments>http://tea.cesaroliveira.net/archives/52#comments</comments>
		<pubDate>Tue, 13 Jan 2009 11:49:02 +0000</pubDate>
		<dc:creator>Cesar</dc:creator>
				<category><![CDATA[addons]]></category>
		<category><![CDATA[editor]]></category>
		<category><![CDATA[extension]]></category>
		<category><![CDATA[hugs]]></category>
		<category><![CDATA[mozilla]]></category>

		<guid isPermaLink="false">http://www.cesaroliveira.net/?p=51</guid>
		<description><![CDATA[As the addon review queue grows beyond 600 nominated and updated addons, it is more important than ever to make sure your extension passes review the first time around. Editors have a review guide, and a well hidden but publicly viewable set of policies. But here is a quick list of the most cited reasons [...]]]></description>
			<content:encoded><![CDATA[<p>As the addon review queue grows beyond 600 nominated and updated addons, it is more important than ever to make sure your extension passes review the first time around. Editors have a <a href="https://wiki.mozilla.org/Update:Editors/ReviewingGuide" onclick="pageTracker._trackPageview('/outgoing/wiki.mozilla.org/Update_Editors/ReviewingGuide?referer=');">review</a> guide, and a well hidden but publicly <a href="https://addons.mozilla.org/en-US/firefox/pages/policy" onclick="pageTracker._trackPageview('/outgoing/addons.mozilla.org/en-US/firefox/pages/policy?referer=');">viewable set of policies</a>. But here is a quick list of the most cited reasons for addon refusal :</p>
<ol>
<li>Addon should have at least 3 user reviews before being nominated. External reviews count too, but you have to mention them in your nomination message. Softpedia reviews do not count.</li>
<li>Wrap your <a href="http://blogger.ziesemer.com/2007/10/respecting-javascript-global-namespace.html" onclick="pageTracker._trackPageview('/outgoing/blogger.ziesemer.com/2007/10/respecting-javascript-global-namespace.html?referer=');">loose variables</a>. All objects, variables, and anything that your addon makes global should be wrapped to avoid conflicts with other addons.</li>
<li>Look at the error console. Is your extension throwing up javascript errors? Fix it. There are some <a href="https://developer.mozilla.org/en/Setting_up_extension_development_environment" onclick="pageTracker._trackPageview('/outgoing/developer.mozilla.org/en/Setting_up_extension_development_environment?referer=');">options</a> you can set in about:config to help you with this.</li>
<li>You break functionality in the host application (Firefox, Thunderbird, etc.).</li>
<li>Your extension doesn&#8217;t work properly, or showing unexpected results. This is what user reviews are expected to catch, but you really should get someone who wasn&#8217;t involved to test and report bugs.</li>
</ol>
<p>There are other less common things that can get you busted too. I&#8217;ll just list them here for completeness sake :</p>
<ol start="5">
<li>Including remote javascript/css or other files, anywhere. Include them in your xpi file instead.</li>
<li>CSS warnings on the error console if your submitting a theme.</li>
</ol>
<p>If you have any doubts, check the public policies page linked above.</p>
<p>And don&#8217;t ask when your extension will be reviewed in the comments. Because every answer will be the same : When someone gets around to it. It could be sooner if you&#8217;d help!</p>
]]></content:encoded>
			<wfw:commentRss>http://tea.cesaroliveira.net/archives/52/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
