<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:planet="http://planet.intertwingly.net/" xmlns:indexing="urn:atom-extension:indexing" indexing:index="no"><access:restriction xmlns:access="http://www.bloglines.com/about/specs/fac-1.0" relationship="deny"/>
  <title>Camino Planet</title>
  <updated>2010-03-11T04:00:21Z</updated>
  <generator uri="http://intertwingly.net/code/venus/">Venus</generator>
  <author>
    <name>Samuel Sidler</name>
    <email>info@caminoplanet.org</email>
  </author>
  <id>http://caminoplanet.org/atom.xml</id>
  <link href="http://caminoplanet.org/atom.xml" rel="self" type="application/atom+xml"/>
  <link href="http://caminoplanet.org/" rel="alternate"/>

  <entry xml:lang="en-us">
    <id>http://weblogs.mozillazine.org/pinkerton/archives/020468.html</id>
    <link href="http://weblogs.mozillazine.org/pinkerton/archives/020468.html" rel="alternate" type="text/html"/>
    <title>Why I'm still crazy, an update</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I wanted to post an update on my quest for replacing my paper-based planner with something electronic. After all, now that everyone knows that I'm crazy, I had to make sure everyone knows exactly how crazy.</p>

<p>I started off, very successfully, with Things on the desktop. I was in love. Data entry was quick and easy. The streamlined user interface, the general organization, flexible (hierarchical) tags, and project creation aligned perfectly with what I wanted. I spent about 2-3 weeks with Things, but ultimately I had some problems.</p>

<p>As I've said before, multi-machine sync is non-existant. I hacked a solution with DropBox, but every now and then I forgot to quit the app before I shut down my machine and had to go back and do it before I could run it anywhere else without possible database conflicts. Annoying. While I didn't buy the accompanying iPhone app, having to sync it on the local network while the app was running was a non-starter. When running out the door, I would never, ever, be able to do that, and that negates the entire purpose of having a portable app. The Things folks are still promising this is coming, but they have yet to ship it, so I can't rely on it.</p>

<p>As my free trial was winding down, I thought about taking some time and just writing my own based on Google's AppEngine. I wrote a long white paper of all the features I wanted (basically summarizing why I really liked Things), and just as I was starting to find other Googlers to help me in 20% time, I found Get It Done. It's a web-based version of Things, everything but the color scheme. Spot on. As a web app, my data is always available in the cloud. As a well-written AJAXy web app, I can use native-like gestures such as drag and drop to organize tasks and move items around.</p>

<p>One problem with Get It Done is that it's subscription ($40/yr). Cheaper than buying planner refills each year, but still a lot. I took advantage of the 15day trial and ended up making a lot of suggestions and reporting bugs. To my surprise, the developer responded, usually within an hour or two. Sometimes he even made minor changes I asked for on the website the same day. That's in direct contrast to the Things developers who rarely respond to the forums and don't seem to update the app that often. I figure if the developer is going to listen and be responsive, that's worth the subscription to fund future development.</p>

<p>I've been using GID for about a month now and while I like it, there are problems. I don't really like how projects are done. They're nothing more than tags, so to create a new project you have to add even more tags. There's no such thing as completing a project or being able to mark it as complete because it's not a real entity. Makes it hard to track completed projects. Speaking of tags, I didn't know how much I appreciated Things' concept of hierarchical tags until it was gone. In order to simulate it, I'm tagging each item with multiple tags which gets tedious and clutters the UI. There's also no way to filter on multiple tags. Finally, one of GID's greatest benefits - being a web app - is its biggest drawback. It's a web app. It's slower. It's clunky. Sometimes it feels really clunky. Entering data isn't as streamlined as a native app. While it does a really good job of emulating the native UI, it's got a long way to go to actually replicate it.</p>

<p>Things would be a slam dunk if only the data could be sync'd somewhere easily. I'll use GID for the time being, but I'll still be keeping an eye out to switch. Have I mentioned now nice the Things UI is?</p></div>
    </summary>
    <updated>2010-03-10T00:52:27Z</updated>
    <category term="Things you wish you didn't know about me"/>
    <author>
      <name>pinkerton</name>
    </author>
    <source>
      <id>http://weblogs.mozillazine.org/pinkerton/</id>
      <link href="http://weblogs.mozillazine.org/pinkerton/" rel="alternate" type="text/html"/>
      <link href="http://weblogs.mozillazine.org/pinkerton/indexf.rdf" rel="self" type="application/rdf+xml"/>
      <subtitle>I try so hard to make things suck less...And miles to go before I sleep.</subtitle>
      <title>Sucking less, on a budget</title>
      <updated>2010-03-10T00:52:27Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://cl10n.rwx.it/135 at http://cl10n.rwx.it</id>
    <link href="http://cl10n.rwx.it/node/135" rel="alternate" type="text/html"/>
    <title>Camino 1.6.11 l10n status</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Release notes can be found at <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=549370" title="Link to a Bugzilla bug">Bug 549370</a>; there are also small edits in the software update descriptions, since this will be the last Camino 1.6.x release (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=549374" title="Link to a Bugzilla bug">Bug 549374</a>). See the full article for the usual status matrix.</p>
<p><strong>Please note that there will be one and only one release of any localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.</strong></p>
<p>The translations are expected to be sent by Tue, Mar 9</p>
<div class="og_rss_groups"/><p><a href="http://cl10n.rwx.it/node/135" target="_blank">read more</a></p></div>
    </summary>
    <updated>2010-03-09T00:24:31Z</updated>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/55" term="To do"/>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/80" term="1.6.11"/>
    <author>
      <name>Marcello</name>
    </author>
    <source>
      <id>http://cl10n.rwx.it</id>
      <link href="http://cl10n.rwx.it" rel="alternate" type="text/html"/>
      <link href="http://cl10n.rwx.it/rss.xml" rel="self" type="application/rss+xml"/>
      <subtitle>The Caminol10n (Camino Localization) project is developed by people from every corner of the world contributing Camino translations, in order to make it even easier to adopt for international users. In case you're wondering, Camino is a fast, secure, easy to use browser built only for Mac OS X.
All published translations are packaged into a single distribution (Camino Multilingual), shipped at the same time when the original (English US) versions are released. Therefore, coordination and a strong common knowledge base among localization contributors is essential. If you want to help with translations and reviews, please read the information on the welcome page, register to this website, browse our tutorials (see menu on the left sidebar) and contact people who speak your language, to make your work more productive and more fun!

If you're looking for Camino end-user technical support, please consider these more specific destinations: Camino's official documentation and FAQ, Camino forum @mozillazine, your local Mozilla community.</subtitle>
      <title>Camino Localization Community (CaminoL10n)</title>
      <updated>2010-03-11T04:00:05Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>tag:vox.com,2008-12-12:asset-6a00c225234bee8e1d0109d0738c88000e</id>
    <link href="http://wevah.vox.com/library/post/better-late.html?_c=feed-atom" rel="alternate" type="text/html"/>
    <title xml:lang="en">Better late…</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><div>
         Leopard-compatible beta this weekend.   <p style="clear: both;"> 
    <a href="http://wevah.vox.com/library/post/better-late.html?_c=feed-atom#comments">Read and post comments</a>   |   
    <a href="http://www.vox.com/share/6a00c225234bee8e1d0109d0738c88000e?_c=feed-atom">Send to a friend</a> 
</p>

                </div></div>
    </content>
    <updated>2010-02-27T22:56:52Z</updated>
    <published>2008-12-12T21:09:29Z</published>
    <category label="programming" scheme="http://wevah.vox.com/tags/programming/" term="programming"/>
    <category label="mac" scheme="http://wevah.vox.com/tags/mac/" term="mac"/>
    <category label="cocoa" scheme="http://wevah.vox.com/tags/cocoa/" term="cocoa"/>
    <category label="paparazzi!" scheme="http://wevah.vox.com/tags/paparazzi!/" term="paparazzi!"/>
    <author>
      <name>Wevah</name>
      <uri>http://wevah.vox.com/?_c=feed-atom</uri>
    </author>
    <source>
      <id>tag:vox.com,2006:6p00c225234bee8e1d/</id>
      <author>
        <name>Wevah</name>
        <uri>http://wevah.vox.com/?_c=feed-atom</uri>
      </author>
      <link href="http://wevah.vox.com/library/posts/page/1/atom.xml" rel="self" type="application/atom+xml"/>
      <link href="http://wevah.vox.com/library/posts/page/1/" rel="alternate" type="text/html"/>
      <link href="http://wevah.vox.com/library/posts/atom.xml" rel="service.subscribe" type="application/atom+xml"/>
      <link href="http://wevah.vox.com/library/posts/page/2/atom.xml" rel="next" type="application/atom+xml"/>
      <link href="http://wevah.vox.com/library/posts/page/5/atom.xml" rel="last" type="application/atom+xml"/>
      <subtitle xml:lang="en">Delicious Meaty Devblog!</subtitle>
      <title xml:lang="en">Wevahschnitzel</title>
      <updated>2010-02-27T22:56:31Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>tag:vox.com,2009-02-03:asset-6a00c225234bee8e1d01101665d9be860d</id>
    <link href="http://wevah.vox.com/library/post/paparazzi-and-flash-capture.html?_c=feed-atom" rel="alternate" type="text/html"/>
    <title xml:lang="en">Paparazzi! and Flash capture</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><div>
         I’m still getting a handful of reports of people not being able to capture Flash using Paparazzi!, and I’d like to try to fix that. If you use Paparazzi! and can’t seem to capture Flash (and don’t have a delay set (this is important as the Flash l...   <p style="clear: both;"> 
    <a href="http://wevah.vox.com/library/post/paparazzi-and-flash-capture.html?_c=feed-atom#comments">Read and post comments</a>   |   
    <a href="http://www.vox.com/share/6a00c225234bee8e1d01101665d9be860d?_c=feed-atom">Send to a friend</a> 
</p>

                </div></div>
    </content>
    <updated>2010-02-27T22:56:31Z</updated>
    <published>2009-02-03T00:17:05Z</published>
    <category label="programming" scheme="http://wevah.vox.com/tags/programming/" term="programming"/>
    <category label="cocoa" scheme="http://wevah.vox.com/tags/cocoa/" term="cocoa"/>
    <category label="paparazzi!" scheme="http://wevah.vox.com/tags/paparazzi!/" term="paparazzi!"/>
    <author>
      <name>Wevah</name>
      <uri>http://wevah.vox.com/?_c=feed-atom</uri>
    </author>
    <source>
      <id>tag:vox.com,2006:6p00c225234bee8e1d/</id>
      <author>
        <name>Wevah</name>
        <uri>http://wevah.vox.com/?_c=feed-atom</uri>
      </author>
      <link href="http://wevah.vox.com/library/posts/page/1/atom.xml" rel="self" type="application/atom+xml"/>
      <link href="http://wevah.vox.com/library/posts/page/1/" rel="alternate" type="text/html"/>
      <link href="http://wevah.vox.com/library/posts/atom.xml" rel="service.subscribe" type="application/atom+xml"/>
      <link href="http://wevah.vox.com/library/posts/page/2/atom.xml" rel="next" type="application/atom+xml"/>
      <link href="http://wevah.vox.com/library/posts/page/5/atom.xml" rel="last" type="application/atom+xml"/>
      <subtitle xml:lang="en">Delicious Meaty Devblog!</subtitle>
      <title xml:lang="en">Wevahschnitzel</title>
      <updated>2010-02-27T22:56:31Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://cl10n.rwx.it/130 at http://cl10n.rwx.it</id>
    <link href="http://cl10n.rwx.it/node/130" rel="alternate" type="text/html"/>
    <title>Current release: Camino 2.0.2</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The most recent Camino release is version 2.0.2 (Universal Binary, for Intel, PowerPC, needs <strong>Mac OS X 10.4 or higher</strong>).
<a href="http://caminobrowser.org/download/releases/2.0.2-MultiLang/">Camino 2.0.2 multilingual</a> contains: Chinese (Simplified), Danish, Dutch, English (US), French, German,  Italian, Japanese, Norwegian, Polish, Russian, Slovenian, Spanish, Swedish, Turkish.
Camino 2.0 users should receive notice of the new version by way of the internal software update engine. If you have not set up Camino to check automatically for new versions, use the "Check for updates..." item in the Application menu.

<div class="og_rss_groups"/></div>
    </summary>
    <updated>2010-02-26T00:26:15Z</updated>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/27" term="10.4.x"/>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/28" term="10.5.x"/>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/86" term="10.6.x"/>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/29" term="Project status"/>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/84" term="2.0.2"/>
    <author>
      <name>Marcello</name>
    </author>
    <source>
      <id>http://cl10n.rwx.it</id>
      <link href="http://cl10n.rwx.it" rel="alternate" type="text/html"/>
      <link href="http://cl10n.rwx.it/rss.xml" rel="self" type="application/rss+xml"/>
      <subtitle>The Caminol10n (Camino Localization) project is developed by people from every corner of the world contributing Camino translations, in order to make it even easier to adopt for international users. In case you're wondering, Camino is a fast, secure, easy to use browser built only for Mac OS X.
All published translations are packaged into a single distribution (Camino Multilingual), shipped at the same time when the original (English US) versions are released. Therefore, coordination and a strong common knowledge base among localization contributors is essential. If you want to help with translations and reviews, please read the information on the welcome page, register to this website, browse our tutorials (see menu on the left sidebar) and contact people who speak your language, to make your work more productive and more fun!

If you're looking for Camino end-user technical support, please consider these more specific destinations: Camino's official documentation and FAQ, Camino forum @mozillazine, your local Mozilla community.</subtitle>
      <title>Camino Localization Community (CaminoL10n)</title>
      <updated>2010-03-11T04:00:05Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>http://caminobrowser.org/blog/2386428923794812423231098286</id>
    <link href="http://caminobrowser.org/blog/2010/#camino2.0.2" rel="alternate" type="text/html"/>
    <title xml:lang="en-US">Camino 2.0.2 Released!</title>
    <content type="xhtml" xml:lang="en-US"><div xmlns="http://www.w3.org/1999/xhtml"><div>
<p>We’ve just released Camino 2.0.2, a maintenance release which <a href="http://caminobrowser.org/releases/2.0.2/">contains various security and stability updates</a> to Camino 2.0.x. All users are urged to update.</p>
<p>In addition, Camino 2.0.2 is available in the following languages:</p>
<ul class="req">
  <li>Chinese (Simplified)</li>
  <li>Danish</li>
  <li>Dutch</li>
  <li>English (US)</li>
  <li>French</li>
  <li>German</li>
  <li>Italian</li>
  <li>Japanese</li>
  <li>Norwegian (Bokmål)</li>
  <li>Polish</li>
  <li>Russian</li>
  <li>Slovenian</li>
  <li>Spanish (Castellano)</li>
  <li>Swedish</li>
  <li>Turkish</li>
</ul>
<p>As always, you can download <a href="http://caminobrowser.org/download/releases/2.0.2/">Camino 2.0.2 in English</a> (or the <a href="http://caminobrowser.org/download/releases/2.0.2-MultiLang/">multilingual version</a>) from our website, and existing Camino users will receive this release via software update.</p>
</div></div>
    </content>
    <updated>2010-02-23T21:00:00Z</updated>
    <published>2010-02-23T21:00:00Z</published>
    <author>
      <name>Samuel Sidler</name>
    </author>
    <source>
      <id>http://caminobrowser.org/blog/</id>
      <link href="http://caminobrowser.org/blog/" rel="alternate" type="text/html"/>
      <link href="http://www.caminobrowser.org/blog/atom.xml" rel="self" type="application/atom+xml"/>
      <title xml:lang="en-US">Camino. Blog</title>
      <updated>2010-02-23T21:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=565</id>
    <link href="http://www.ardisson.org/afkar/2010/02/22/last-chances-to-vote-for-camino-in-the-2010-about-com-readers-choice-awards/" rel="alternate" type="text/html"/>
    <title>Last Chances to Vote for Camino in the 2010 About.com Reader’s Choice Awards</title>
    <summary>Just a brief reminder that there are only two days of voting left for the 2010 About.com Reader’s Choice Awards.
Camino is a finalist in the Best Independent Browser category (as announced on the Camino Blog earlier this month), as well as in the Best Mac Browser category (which we didn’t know about until recently).  [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Just a brief reminder that there are only two days of voting left for the <a href="http://awards.about.com/od/webdesign/a/awards_FAQ.htm">2010 About.com Reader’s Choice Awards</a>.</p>
<p>Camino is a finalist in the Best Independent Browser category (as announced on the Camino Blog <a href="http://caminobrowser.org/blog/2010/#aboutawards">earlier this month</a>), as well as in the Best Mac Browser category (which we didn’t know about until recently).  In the Best Independent Browser category Camino is the sole Mac-only browser, while competitors in the Best Mac Browser category include most of the usual suspects.</p>
<p>Voting runs through February 24 (or perhaps midnight on February 25—in an unspecified time zone; all of the documentation is unclear!), so if you’re a Camino fan, you can vote in the <a href="http://browsers.about.com/od/allaboutwebbrowsers/ss/2010-readers-choice-awards-web-browsers-voting_6.htm">Best Independent Browser</a> and <a href="http://macs.about.com/od/readertoreader/ss/readers-choice-2010-vote_8.htm">Best Mac Browser</a> polls.  (You can find all of the categories in the awards <a href="http://webdesign.about.com/od/awards/qt/readers-choice-2010-all-participants.htm">here</a> and vote for your favorite websites and programs in other categories.)</p></div>
    </content>
    <updated>2010-02-23T02:50:04Z</updated>
    <category term="Camino"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://www.bbc.co.uk/blogs/bbcinternet/2010/02/a_new_global_visual_language_f.html</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/0_V0RWkd5SE/a_new_global_visual_language_f.html" rel="alternate" type="text/html"/>
    <title>A new global visual language for the BBC's digital services</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="" src="http://www.bbc.co.uk/blogs/bbcinternet/img/23-colour.jpg"/></p>

	<p>A fascinating post detailing the creation of a consistent visual identity of the <span class="caps">BBC</span>’s online presence. Also, worth reading is the response from <a href="http://paulrobertlloyd.com/2010/02/bbc_online_gvl">Paul Robert Lloyd</a>. The use of big clunky Verdana for headings seems to have been phased out – hurrah!</p>
<p><a href="http://hicksdesign.co.uk/journal/a-new-global-visual-language-for-the-bbc-s-digital-services" rel="bookmark">Comment on this</a></p></div>
    </summary>
    <updated>2010-02-18T04:50:03Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://www.bbc.co.uk/blogs/bbcinternet/2010/02/a_new_global_visual_language_f.html</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/moving-on</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/MZ1aF_pR7ys/moving-on" rel="alternate" type="text/html"/>
    <title>Moving on</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>This just in: I’m leaving Opera.</p>

	<p>Before I go any further, I need to make this very clear. I’m <strong>not</strong> leaving because I unhappy working for them, or any such rubbish. Neither did we come to blows over 42 different shades of red. Opera as company, and as individuals, have bent backwards to accommodate my remote working ways, and it’s been nothing but a fruitful and joyous time. I’ve made many friends, and it’s been everything I hoped it would be and more. I could very easily carry on for as long as they would have me. </p>

	<p>But, I’ve got that itch. I’m sure a lot of designers feel the same way when they work on long term projects, and that itch is the desire simply to ‘do something different’. That is the sole reason. In fact, I’m hoping that we will still be working together in the future, it’s just that my work for Opera won’t be full-time as it is now.</p>

	<p>I ‘finish’ full-time at Opera in late April. The reason for publishing this post now, rather than then, is that I need to get word around. I’ve been ‘off the market’ for a rather long time (looong before I started at Opera), and I’m now looking at an empty diary for the rest of the year. I have a few ideas, but very few plans at this stage, other than speaking at <a href="http://futureofwebdesign.com/">Future of Web Design London</a> in May.</p>

	<p>So if you’re looking for a icon/interface/logo/website designer or even character illustrator (the Mailchimp mascot has become the new ‘animal on fire round a globe’ request!) from May onwards, then please <a href="http://feeds.feedburner.com/contact/">drop me an email</a>. Thanks!</p></div>
    </summary>
    <updated>2010-02-17T19:29:33Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/moving-on</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://cl10n.rwx.it/134 at http://cl10n.rwx.it</id>
    <link href="http://cl10n.rwx.it/node/134" rel="alternate" type="text/html"/>
    <title>Camino 2.0.2 l10n status</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Release notes can be found at <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=545347" title="Link to a Bugzilla bug">Bug 545347</a>. See the full article for the usual status matrix.</p>
<p><strong>Please note that there will be one and only one release of any localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.</strong></p>
<p>The translations are expected to be sent by Sun, Feb 21</p>
<!-- <p><strong>As of Mon. March 30th, I have received all the needed files from the l10n teams.</strong></p> -->
<div class="og_rss_groups"/><p><a href="http://cl10n.rwx.it/node/134" target="_blank">read more</a></p></div>
    </summary>
    <updated>2010-02-16T23:49:39Z</updated>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/55" term="To do"/>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/84" term="2.0.2"/>
    <author>
      <name>Marcello</name>
    </author>
    <source>
      <id>http://cl10n.rwx.it</id>
      <link href="http://cl10n.rwx.it" rel="alternate" type="text/html"/>
      <link href="http://cl10n.rwx.it/rss.xml" rel="self" type="application/rss+xml"/>
      <subtitle>The Caminol10n (Camino Localization) project is developed by people from every corner of the world contributing Camino translations, in order to make it even easier to adopt for international users. In case you're wondering, Camino is a fast, secure, easy to use browser built only for Mac OS X.
All published translations are packaged into a single distribution (Camino Multilingual), shipped at the same time when the original (English US) versions are released. Therefore, coordination and a strong common knowledge base among localization contributors is essential. If you want to help with translations and reviews, please read the information on the welcome page, register to this website, browse our tutorials (see menu on the left sidebar) and contact people who speak your language, to make your work more productive and more fun!

If you're looking for Camino end-user technical support, please consider these more specific destinations: Camino's official documentation and FAQ, Camino forum @mozillazine, your local Mozilla community.</subtitle>
      <title>Camino Localization Community (CaminoL10n)</title>
      <updated>2010-03-11T04:00:05Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=563</id>
    <link href="http://www.ardisson.org/afkar/2010/02/16/another-week-another-branch/" rel="alternate" type="text/html"/>
    <title>Another week, another branch</title>
    <summary>Just a quick update from the trenches on the “newer Gecko” project: I’m writing this post from a Camino 2.1a1pre based on Gecko 1.9.2.2pre (the same Gecko version used in Firefox 3.6.2pre nightly builds).  
Last Monday, shortly after Christopher Henderson and I had produced working Gecko 1.9.1-based builds, he posted the first screenshots of [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Just a quick update from the trenches on the “newer Gecko” project: I’m writing this post from a Camino 2.1a1pre based on Gecko 1.9.2.2pre (the same Gecko version used in Firefox 3.6.2pre nightly builds).  </p>
<p>Last Monday, shortly after <a href="http://inspiral.co.nz/">Christopher Henderson</a> and I had produced <a href="http://www.ardisson.org/afkar/2010/02/08/standing-on-the-shoulders-of-kiwis/">working Gecko 1.9.1-based builds</a>, he posted the <a href="http://inspiral.s3.amazonaws.com/camino/useragent.png">first</a> <a href="http://inspiral.s3.amazonaws.com/camino192/gradients.png">screenshots</a> of a 1.9.2-based Camino.  Over the following week, Christopher has debugged a couple of crashes, as well as the history-not-saving-across-sessions bug <a href="http://www.ardisson.org/afkar/2010/02/08/standing-on-the-shoulders-of-kiwis/#comment-7140">mentioned in the comments</a> of the previous announcement.  I fixed a few other build-related issues and hacked around a couple of smaller Gecko bugs, and <a href="http://emps.l-c-n.com/">Philippe Wittenbergh</a> started working on polishing our custom <abbr title="Cascading Style Sheets">CSS</abbr> to handle the newer Gecko versions.</p>
<p>As a result of the week’s work, we now have available a <a href="http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/experimental/Camino-2.1a1pre-1.9.2.2pre.dmg">Gecko 1.9.2-based Camino 2.1a1pre Universal build</a> (with all the best warts of both) for further testing.  Those of you who want to play along at home can build with <a href="http://www.ardisson.org/smokey/moz/1_9_2-full.diff">this large patch</a> (the CSS fixes are in additional patches in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=545353">bug 545353</a>). <strong>N.B.</strong> You should treat this build as highly experimental.  It might eat all of the cheese in your house.  Be sure to <strong>make a backup copy</strong> of your profile first.</p>
<p>We’d like nightly build users and other interested people to hammer on this build for a while to help us gauge the degree of bugginess; if the bugs we hear about seem manageable, we’ll focus our attention here.  For the time being, please comment about specific problems on <a href="http://forums.mozillazine.org/viewtopic.php?f=12&amp;t=1754775">this thread in the forums</a>.</p></div>
    </content>
    <updated>2010-02-16T06:24:15Z</updated>
    <category term="Camino"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/zootool</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/jpMCnvUn_bI/zootool" rel="alternate" type="text/html"/>
    <title>Zootool</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Main Zootool Window" src="http://hicksdesign.co.uk/else/images/Zoo_%7C_Zootool-20100211-205415.png"/></p>

	<p>The last thing I needed was more choice in apps for keeping a ‘Design Scrapbook’, but that’s what’s happened with <a href="http://zootool.com">Zootool</a>. At first glance, it looked like just another <a href="http://ffffound.com/"><span class="caps">FFFF</span>ound</a>, <a href="http://emberapp.com/">Ember</a> or <a href="http://imgspark.com/">Img Spark</a>, but it turns out it’s much more than that. The developer, Bastian, told me to think of it as more of a visual Delicious. Once I got into that mindset it made more sense.</p>

	<p><img alt="Using Lasso to round up content on the page" src="http://hicksdesign.co.uk/else/images/Psychedelic_London_newspapers_%C2%AB_Cakehead_Loves_Evil-20100211-205806.png"/></p>

	<p><img alt="Organise content into packs" class="fr" src="http://hicksdesign.co.uk/else/images/Zoo_%7C_Zootool-20100211-205952.png"/>Zootool ‘lassos’ not only images, but documents (like <span class="caps">PDF</span>s), videos, and pages (not complete pages yet) and stores them in your ‘zoo’. Content can be organised into ‘packs’ (folders) and as you would expect, it stores the original <span class="caps">URL</span>, and offers fields to change the title, and add tags or a description. It also provides integration with services like Twitter, Tumblr and Facebook, along with short urls, for sharing what you’ve found.</p>

	<p>So, rather than having favourites being stored on different sites like Delicious, Vimeo, YouTube etc, they’re all in one place. In some ways I think of it as a huffduffer for anything that isn’t audio. </p>

	<p>What’s particularly interesting is how well it’s been engineered to act like a Mac desktop app. Double clicking or pressing space bar on the thumbnails, takes you to the detail view, just as you would expect. Multiple thumbnails can be shift-selected, and to put content into a pack, you can drag and drop it. I’ve been using it for a couple of weeks now, and I think it’s rather spiffing! It works so well it feels like it’s been a part of my workflow for long time.</p>

	<p><img alt="Zootool includes an iPhone optimised view, but an app is in development" src="http://hicksdesign.co.uk/else/images/IMG_1001-20100211-204912.png"/></p>

	<p>I do have a couple of concerns however. With any system that has tags, I never feel it’s worth the effort of tagging unless I can be sure that the tags are portable in some way. I can download a bookmark file from Zootool (with delicious tags), but should the service ever go down, all that data and effort is lost. This is where desktop apps like Leap that support OpenMeta win. I feel this especially in tools like Evernote and Littlesnapper – is it really worth tagging if I then change system in a few months? The answer is no – I’m tagging less and less for this very reason.</p>

	<p>It also exists online only. Part of what I love about Evernote (which isn’t really a comparable service <span class="caps">BTW</span>), is that it’s everywhere, even when I don’t have a connection. However, Zootool still has a place in my life, even if it isn’t used as a design scrapbook.</p>

	<p>If you haven’t tried Zootool yet, I recommend you give it at least a few minutes of your life. While you’re there, <a href="http://zootool.com/user/hicksdesign/">here’s my zoo</a></p></div>
    </summary>
    <updated>2010-02-12T03:31:08Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/zootool</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=549</id>
    <link href="http://www.ardisson.org/afkar/2010/02/08/standing-on-the-shoulders-of-kiwis/" rel="alternate" type="text/html"/>
    <title>Standing on the shoulders of Kiwis</title>
    <summary>It has been some time since the last regular Camino development status update, but that doesn’t mean we haven’t been hard at work—it just means that I’ve been pretty busy with all sorts of things, and the status updates have been fairly low on my to-do list.
As I said, though, we’ve been working on all [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>It has been some time since the last regular Camino development status update, but that doesn’t mean we haven’t been hard at work—it just means that I’ve been pretty busy with all sorts of things, and the status updates have been fairly low on my to-do list.</p>
<p>As I said, though, we’ve been working on all sorts of things so far this year.  <a href="http://summerofcamino.com/">Dan Weber</a> has been hard at work on patches for some of the most visible issues with the new autocomplete experience, and I landed the fix for the magically-reappearing autocomplete window tonight.  Dan is also still working on improving the speed of autocomplete for large histories, though that patch is not yet ready.  Chris Lawson has also been working on various and sundry other bugs, including changes to the Flashblock exceptions list so that pasting <abbr title="Uniform Resource Locator">URL</abbr>s into the field will work as users expect.  <a href="http://emps.l-c-n.com/">Philippe Wittenbergh</a> is hard at work polishing some of our toolbar icons.  </p>
<p><a href="http://inspiral.co.nz/">Christopher Henderson</a> has been working on a patch that moves our history off of <a href="http://en.wikipedia.org/wiki/Mork_(file_format)">Mork</a>, which is both the sane thing to do and critical for moving forward to the new Mork-less world. As usual, I have been chasing down bugs here and there and wrangling patches to get ready for the upcoming 2.0.2 and 1.6.11 releases.  We’ve also seen Alex Jones, who has been working off-and-on on supporting Mobile Me sync, again recently, though it sounds like Sync Services wants to do things in a manner that is not easily compatible with Camino’s bookmarks implementation.  All in all, we’ve been fairly productive since the new year began.</p>
<p>Which brings us back to the title of this post and to this weekend’s developments.  Late Saturday afternoon, I got a debug version of Camino to build, launch, and run using Gecko 1.9.1, and early Sunday evening I was able to make a static (i.e., distributable) build do the same thing.  (Even better, Christopher Henderson was able to replicate my success.) This feat would not have been possible without all the hard work that Christopher put in for the aforementioned history migration, as well as a good bit of debugging and patching he did this weekend as we hit some unexpected code-change-related build failures.  After applying those patches, I mostly deleted and added things to the project and waited for the next build failure.  At the end of the day, though, Camino launches and runs, plays <code>&lt;audio&gt;</code> and <code>&lt;video&gt;</code> (with Ogg), and displays pages with <code>@font-face</code> (with raw TrueType fonts).</p>
<p style="text-align: center;"><a href="http://www.ardisson.org/afkar/wp-content/uploads/2010/02/camino-font-face.png"><img alt="Camino displaying an @font-face demo" class="size-full wp-image-556" height="477" src="http://www.ardisson.org/afkar/wp-content/uploads/2010/02/camino-font-face.png" title="Camino displaying an @font-face demo" width="485"/></a></p>
<p>This doesn’t mean that we can turn around and release a version of Camino based on Gecko 1.9.1 (and there’s a very strong possibility we may not); for starters, there are a number of known regressions (including the loss of Find-As-You-Type), as well as possibly hundreds of other serious problems we haven’t discovered in our limited test browsing.  Beyond that, the “build system” is not yet a system at all; it involves pulling mozilla-1.9.1 from hg, checking out Camino from cvs into <code>mozilla/camino</code>, and applying a <a href="http://www.ardisson.org/smokey/moz/1_9_1-full.diff">large patch</a>.  But if you’re brave or crazy, you <em>can</em> try this at home now (and for those less brave or more sane, there’s an Intel-only build <a href="http://www.ardisson.org/smokey/moz/Camino-2.1a1pre-1.9.1.8-i386.dmg">here</a> that you can use to help us find other broken things.  <strong>N.B.</strong> You should treat this build as highly experimental.  It might eat all of the cheese in your house.  It <strong>will</strong> eat your profile, so <strong>make a backup copy</strong> first).</p>
<p>(<strong>Update 9 Feb:</strong> The patch above now has all of the required parts of the history migration, which had been missing from the earlier patch.)</p>
<p>We also know (thanks to earlier attempts by Philippe Wittenbergh and <a href="http://web.me.com/krmathis/">Kai Rune Mathisen</a> to build mozilla-central) that there are more serious code breakages in newer versions of Gecko, so this is only the beginning.  In between other things the last few weeks, I’ve also been working on a new repository and fleshing out issues and solutions for the build system.  There’s a long road ahead, and Camino 2.1 might be ready before we’ve gotten to the end of the road; we’ll have to see.  However, as Christopher said on Saturday night, “it’s been a great day in Camino Land.”</p></div>
    </content>
    <updated>2010-02-08T06:49:45Z</updated>
    <category term="Camino"/>
    <category term="History"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=546</id>
    <link href="http://www.ardisson.org/afkar/2010/02/07/and-the-winner-is%e2%80%a6-2/" rel="alternate" type="text/html"/>
    <title>And the winner is…</title>
    <summary>FCKEditor!
This news is a bit old now (since it appeared briefly on Planet Mozilla the other day half-buried in a PR round-up, and since reader James reported it in a comment on January 21), but FCKEditor is the winner of the 2010 edition of the annual “we break our site for your browser when the [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>FCKEditor!</p>
<p>This news is a bit old now (since it appeared briefly on Planet Mozilla the other day half-buried in a PR round-up, and since reader James reported it in <a href="http://www.ardisson.org/afkar/2009/12/31/reminder-year-2010-bug-contest/#comment-7122">a comment</a> on January 21), but FCKEditor is the winner of the 2010 edition of the annual “we break our site for your browser when the new year rolls around” broken browser-sniffing contest.</p>
<p>If you use FCKEditor on a site and it doesn’t work with Firefox 3.6 or nightly builds of any Gecko browser built since January 1, you’re probably seeing <a href="http://www.petefreitag.com/item/737.cfm">the bug</a> that won FCKEditor this year’s prize with a stunning upset of <a href="http://www.ardisson.org/afkar/2009/01/01/and-the-winner-is&#x2026;/">two-time defending champion</a> Yahoo!</p>
<p>My gut feeling is that this new type of contest winner is much worse than the old “major site is broken” type, since there is no single point of contact for the fix (everyone who uses the affected versions of FCKEditor will have to patch or upgrade their install), since unpatched instances of FCKEditor could break functionality on websites far and wide for years to come, and since in some ways the distributed nature of the problem means there is less visibility than when a major website suddenly ceases to work correctly.</p>
<p>I think this also highlights the importance of web “library” or “component” authors doing things correctly from the beginning—not browser sniffing at all, but instead testing for features—because their code will be used widely and, as I understand it, they have little control over getting consumers to update when there are fixes for broken things like this.  </p>
<p>If you’re going to write something for wider consumption, or that you think may one day be useful to large audiences, please take the time to get things right from the beginning, especially if your code doesn’t have a dead-simple upgrade experience.  Your users, and their users, and even other unrelated software vendors, will thank you for it later.</p>
<p>(And remember: only you can prevent broken browser sniffing! <img alt=":P" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_razz.gif"/>  )</p></div>
    </content>
    <updated>2010-02-08T04:21:47Z</updated>
    <category term="Camino"/>
    <category term="History"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>http://caminobrowser.org/blog/2386428923794812423231098285</id>
    <link href="http://caminobrowser.org/blog/2010/#aboutawards" rel="alternate" type="text/html"/>
    <title xml:lang="en-US">Camino is an About.com Best Independent Browser Finalist!</title>
    <content type="xhtml" xml:lang="en-US"><div xmlns="http://www.w3.org/1999/xhtml"><div>
<p>About.com has just released the list of finalists in the 2010 <a href="http://awards.about.com/od/webdesign/a/awards_FAQ.htm">About.com Reader’s Choice Awards</a>, and Camino is one of the five finalists in the “Best Independent Browser” category.  We’re excited to be recognized, especially as the sole Mac-only browser in the category.</p>

<p>Voting runs through February 24, so if you’re a Camino fan, you can vote <a href="http://browsers.about.com/od/allaboutwebbrowsers/ss/2010-readers-choice-awards-web-browsers-voting_6.htm">on this page</a>.  (You can access all the About.com Reader’s Choice Awards categories <a href="http://webdesign.about.com/od/awards/qt/readers-choice-2010-all-participants.htm">here</a> and vote for your favorite sites and programs in other categories.)</p>
</div></div>
    </content>
    <updated>2010-02-04T21:00:00Z</updated>
    <published>2010-02-04T21:00:00Z</published>
    <author>
      <name>Smokey Ardisson</name>
    </author>
    <source>
      <id>http://caminobrowser.org/blog/</id>
      <link href="http://caminobrowser.org/blog/" rel="alternate" type="text/html"/>
      <link href="http://www.caminobrowser.org/blog/atom.xml" rel="self" type="application/atom+xml"/>
      <title xml:lang="en-US">Camino. Blog</title>
      <updated>2010-02-23T21:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>http://weblogs.mozillazine.org/pinkerton/archives/020408.html</id>
    <link href="http://weblogs.mozillazine.org/pinkerton/archives/020408.html" rel="alternate" type="text/html"/>
    <title>DropBox</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>In the spirit of the title of this blog, I wanted to pass along my experience with some software that is really awesome (and free). If you need a way to share data between machines and do some simple syncing, check out Dropbox. It blows iDisk out of the water. With a nuclear bomb. If you've ever been frustrated with iDisk's performance, frequent file copy errors, and just general malaise, try Dropbox right now. It "just works" and it's so easy use.</p>

<p>Yesterday, their servers were down for a bit while I was in the middle of trying to copy some files around. If I was using my iDisk, I would have gotten hangs and failures and dead files. The Finder probably would have locked up and I would have had to Force Quit it. However, Dropbox recovered transparently and when the servers came back up, everything finished copying without a hiccup. Proper error handling. Imagine that. The icons in the Finder are even badged to let you know what's been synced and what hasn't.</p>

<p>Go try it.</p></div>
    </summary>
    <updated>2010-01-30T18:20:17Z</updated>
    <author>
      <name>pinkerton</name>
    </author>
    <source>
      <id>http://weblogs.mozillazine.org/pinkerton/</id>
      <link href="http://weblogs.mozillazine.org/pinkerton/" rel="alternate" type="text/html"/>
      <link href="http://weblogs.mozillazine.org/pinkerton/indexf.rdf" rel="self" type="application/rdf+xml"/>
      <subtitle>I try so hard to make things suck less...And miles to go before I sleep.</subtitle>
      <title>Sucking less, on a budget</title>
      <updated>2010-03-10T00:52:27Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/the-handbag-has-been-raised</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/BQtwlREq4vw/the-handbag-has-been-raised" rel="alternate" type="text/html"/>
    <title>The Handbag has been raised!</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>How often have you read a snide, bumptious or haughty comment where you feel the only reaction could be a raised handbag, accompanied by the high-pitched mocking call of “oooOOOooooh!”?</p>

	<p>If you’re not familiar with the work of <a href="http://en.wikipedia.org/wiki/Vic_and_Bob">Vic and Bob</a>, the chances are that it’s <strong>never</strong>. Well, hopefully that will soon change, as Hicksdesign has launched a site to fulfill that need you never knew you had to “oooOOooooh!”:</p>

	<p><img alt="screenshot" src="http://hicksdesign.co.uk/else/images/ooh-20100125-170513.jpg"/></p>

	<p>Now whenever you see such a comment, you point them in the right direction: <a href="http://oo00.eu/">oo00.eu</a> (2 oh’s, 2 zeros and a european union). Obviously, feel free to use it on me if say some deserving! ;)</p>

	<p>If you’re still confused, this video might help explain the origins of the raised handbag as a retort, (before going on to become a surreal contest):</p>

	<p/>

	<h3>Playing catch-up</h3>

	<p>This little side-project was the perfect opportunity to play with new CSS3 toys and HTML5 tags that I haven’t had time to experiment with yet:</p>

	<p><strong><span class="caps">CSS</span> Animations</strong>: In any webkit browser (Safari, Omniweb, Chrome), the handbag will actually be raised, waved at you, and then lowered. There is a separate animation for the shadow underneath the bag. It’s a little clunky, but that suits the context.<br/>
<strong><span class="caps">CSS</span> Media Queries</strong>: Just as this blog does, the layout changes when the viewport  is reduced smaller than 700px. These style rules also govern layout on mobiles (only tested on iPhone so far though). Not currently supported in Camino or IE, but work in everything else.<br/>
<strong>HTML5 structural tags</strong>: Added footer, header and section, with simple javascript to allow their use in IE. Not forgetting to add display:block to each to compensate for lack of browser default styles.<br/>
<strong>HTML5 audio</strong>: In Opera 10.5 (Win), Chrome and Firefox, you should get the .ogg file, and in Safari, the mp3. It won’t be in time with the animation sadly, but I’m hoping that’s something that will be possible in the future. Thanks to the Webble Millers for providing their oooohs.<br/>
<strong>Web Fonts</strong>: Type goodness is supplied via <a href="http://typekit.com/">Typekit</a>, namely the gorgeous slab-serif <a href="http://typekit.com/fonts/650">Adelle</a>. Currently a no-show in Opera, but hopefully once 10.5 final is out, Typekit will update their sniffing.</p>

	<p>So depending on which browser you use, you’ll get a slightly different experience, but the same content. </p></div>
    </summary>
    <updated>2010-01-26T19:52:39Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/the-handbag-has-been-raised</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>http://weblogs.mozillazine.org/pinkerton/archives/020398.html</id>
    <link href="http://weblogs.mozillazine.org/pinkerton/archives/020398.html" rel="alternate" type="text/html"/>
    <title>Task Management, or "Why I'm Neurotic And Inches From The Loony Bin"</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I'm directly over the city of Columbus, Ohio, amidst a large amount of turbulence that would have spilled any drink I had, if only they had come around and brought me something. I'm also very frustrated, and I'll explain why over the course of this blog post, which is about my inability to find a task management system that has a foothold in even the 20th century. This will turn into something that most will skip with "too long, didn't read", but it's as much for my benefit as for yours. Who are we kidding, it's entirely for mine, I don't care about you.</p>

<p>I'm a list person. I need to write things down and capture them outside of my head or they simply won't happen. At one point in my life, I had a really great memory. It's still not so bad, but I can tell it's gotten a little worse as I've gotten older. Regardless, I have to write things down in order to organize them. This is the only way I'm able to execute on anything. It's also the act of writing things down that helps me remember them. I'm one of those people that learns best by taking notes, even if I never look at those notes again. None of this is up for debate, it's been proven time and time again to me through years and years and years of school, followed by work.</p>

<p>As an aside, I can barely read this as I type it because the screen is bouncing so much. Why? Because the plain is bouncing all over the sky, just north of Dayton, Ohio.</p>

<p>I used some task management software through college, but it was in grad school where I was really introduced to the joys electronic planning with my association with some research going on in the Graphics and Visualization Lab at Georgia Tech. They were doing work with the Apple Newton and I was able to procure one for daily use. That day my life changed.</p>

<p>Let me take a step back and introduce you to one of my neurosis and idiosyncrasies. I love office supplies: pens, highlighters, post-its, flags, folders, mechanical pencils, notebooks. If it's in an Office Depot, I love it. I can wander around a Staples for days and not get bored. I love them so much that I can't bear to see them spoiled by, well, using them. What if I mess up and have to scribble something out? What if I use too many and they're all gone? I have to force myself to unwrap post-it notes, let alone write on them. You can see this might make it difficult to organize my life with such supplies because doing so would mean I had to soil them.</p>

<p>Oh look, they turned off the fasten seatbelt sign.</p>

<p>With the Newton, everything was electronic. I could scribble out any mistakes, move things around on the fly, and never ever have to worry about unwrapping my precious stickies. It was as if a weight had been lifted from me. Most importantly, it was portable. Sure, my Mac had a stickies app, but I couldn't lug a PowerMac 6100/66 around to class in order to take down my homework or set up a study group. It was the best of both worlds in that I could write with my own handwriting (yes, it worked perfectly, regardless of what the press said) and I could take it anywhere. Life was good.</p>

<p>Right about the time I started working, Steve Jobs came back to Apple and decided that things had to change. Out went the Newton division and along with it my hopes and dreams. There was a new sheriff in town anyway, one that was taking over the PDA landscape: Palm. Sure you had to write with some arcane squiggles. Sure, it was tiny and you had to squint to see just about everything. But it was supported by everyone and had great desktop integration. That means I could use a desktop app at work and at home, but still be able to access and enter tasks/events on the road. For the most part, I was happy, but there was still something that left me wanting.</p>

<p>Remember that part about how I like to write things down in order to commit them to memory? The Newton allowed that, because I was really writing as if I was writing on paper. Doing any serious data entry on the Palm was a joke, so you just typed everything. In addition, the Mac desktop software was a joke, so I had to do most of it on my spare PeeCee at work and that made it difficult to do things at home. Also around that time, I was looking for something a bit more holistic in my life, something that would help organize not just remembering to do my TPS reports, but also help me make myself a better person.</p>

<p>About this time, I discovered Franklin Covey products. For those unaware, it's a methodology crafted around Stephen Covey's book about some habits and traits shared by highly effective people. He makes a lot of money on seminars and training, but that doesn't mean it's all schlock. There's some good stuff there, and it was the method I was after, not the religion. I was drawn to the "life-planning" aspect of FC, helping me to identify what and who was important to me, to set life-long goals and values, and to think about more than just TPS reports. It helped me evaluate who I was versus who I wanted to be and find a plan to unify the two. The approach of long-term and short-term planning, with frequent reviews, made a lot of sense to me and clicked very nicely. Day-to-day, it was a good system, and as part of a larger whole, it helped me to balance myself (or at least identify where I was out of balance so I could correct it). </p>

<p>There was some desktop software (PC only, of course) and accompanying Palm software (remember, everyone supported it). I used this for a while, but while the system was great, the desktop software was shit. Unadulterated shit. It did about half of the system very well, but the other half barely worked. It's as if the FC developers didn't even understand the system for which they were building software. The poor customer support people on the forums were overrun with complaints and eventually stopped responding. Updates were slow to nonexistent and didn't address the obvious bugs people would routinely complain about. After all this, I started to doubt what I could get out of this system. I made a temporary switch over to LifeBalance because it had a Mac client, but it never really worked right either.</p>

<p>Then one day I decided to take the software out of the equation entirely. If it was the software that was the barrier, the solution seemed obvious. I invested a couple hundred dollars in a nice leather binder, a year's worth of planner pages, all the inserts, pages, goal planners, etc and started my journey down the path people had been traveling for centuries: pen and paper. With pen and paper, I was free to organize myself exactly how I wanted and could adapt the system to my needs. There were no rules to follow because I controlled the horizontal and the vertical. What could go wrong?</p>

<p>I've lived with a paper planner for close to 10 years now and clearly it wasn't a bad solution. It allows me the tactile learning which I require by writing in my own hand, and it's portable. There are some problems though, which should be obvious. Remember my neurosis about not wanting to mess up? Yeah, well, I still have that. Crossing things out still makes me bleed internally. It's distracting, and always seems to happen right after a 3-day weekend when I write everything off by a day. In order to use the system properly, I need to write goals and assign them tasks. That means opening up my package of goal sheets and scribbling on them. This too makes me bleed internally because I know that once I put pen to virgin paper, the magic is gone.  What if I write things in the wrong order? What if I make any number of mistakes? It's too much, and so I don't do it. There's also the problem that my paper-based system isn't on the Interwebs anywhere. If I don't have my planner, I can't capture anything. I generally have my planner, but not always. The last annoyance is the cost. The pretty pages aren't cheap, and you have to keep buying them year in and year out. At $65 a year (that's just for the yearly pages, there may be other pages I need to get too), you can see how much money I've spent in the last decade on this stuff. I could argue that being this organized has allowed me to be in the position I'm in and the system has clearly paid for itself in that regard, but it's still a bitter pill to have to swallow every year.</p>

<p>So come this New Years, I thought to myself I would try to find a solution that was up to the standards of the 21st century in which I'm a citizen. There are a few requirements to head back into the digital domain. First off, it has to run on a Mac (duh, but this means no iPhone-only solutions) and have a way to access it from my iPhone via something other than the built-in calendar app. Second, I must be able to have first-class viewing/editing from both home and work machines without resorting to lugging around a laptop or requiring the use of my iPhone at one or the other. As I split my time about equally working at home and the office, I need something that syncs between both sets of work machines. I do not want to have to have a separate laptop open at all times that I must carry to work in order to access my life. This much is firm. Finally, it's gotta cost less than the paper planner pages I already use, though this isn't really a problem.</p>

<p>Scanning the Mac desktop landscape, there are really only two players: Things and OmniFocus, and thankfully each comes with a 14-day trial. I downloaded both and played around with them, as well as took the temperature of their online communities in the forums (support is important). Here's the gist of what I came away with.</p>

<p>Things is a beautiful application. It's a lot like an iApp in that it doesn't have complicated inspectors for everything, nor is it cluttered with buttons and UI thingamabobs that probably serve some purpose if only I could figure out what it was supposed to be. A lot of time was spent on the visual design, as well as the work flow, and it shows. It's a very good example of a well-designed, user-centric application. The ability to put multiple tags on items harkens back to the planner software I used in college that's long gone the way of the dodo. It's very flexible and comes with lots of awards for both it and its iPhone app.</p>

<p>There are some downsides, however. Multi-machine sync is something you have to hack with Dropbox and seems easy to mess up if I forget to quit the app before I go to work or come back home. The developers have promised it for forever, but it's still not here (they're a pretty small shop). Being a small shop, new features and bug fix releases are few and far between. Now, I run a rag-tag open-source project with limited to no resources so I understand what they're going through, except my app is free. We don't get paid. I don't make real dollars (or euros) on every user, money they could theoretically use to hire some more developers. I've also seen complaints that the software doesn't scale particularly well (performance of single-file database, no nested projects, etc) and If I'm going to invest in a system, I'm not going to invest in another one in 6mo because it can't keep up with me. That would be unfortunate, and it gives me pause.</p>

<p>So I decided to check out the 800-pound gorilla, OmniFocus. If Things is simple and clean like Camino, OF is like Opera. Sure, you can do tons and tons with it, but, um, do I really want to? The inspector dialog for editing tasks is daunting. I feel a large learning curve coming on, and I'm not sure I want that, as I'll get to below. OF does a great job of multi-machine sync without any hackery and that's a huge benefit for me. Clearly OmniGroup is supportive of this software, they make good and solid products, and they have the resources to continue developing it for a long time to come. It seems we have the requirements met, thus I popped over to their forums where I found them full of happy users and OmniGroup employees answering questions and providing support. Upon further reading, however, I found something I wasn't actually expecting. The forums are chock full of Getting Things Done (GTD) zealots whose beliefs about how the software should be used are clear.</p>

<p>GTD, for those who don't know, is a different system for managing your life. There's nothing wrong with it, I have nothing against people who use it. However, I don't really care to follow GTD (I have my own system, thanks), and it seems that OF was built specifically for GTD. If you want a feature or behavior that's not part of core GTD, don't even bother asking about it, as you'll be met with stiff resistance from the community who will not so gently point out that you're doing it all wrong. I don't need this stress in my life, nor do I want to set out using software in a manner at odds with its design philosophies. Down that road lies madness, and I'd rather avoid it altogether. OF may be awesome, but I just don't want to use it.</p>

<p>Then someone at work suggested a cloud-based solution such as Remember The Milk. I hadn't even though about a web-based alternative, but the benefits were suddenly obvious. Multi-machine sync was entirely a non-issue, and I always have a web browser open for Gmail. After some searching around, I found Toodledo which, astoundingly, was free (let me say that again, free!) for just about all of its functionality. Not only that, it did more than just about every other cloud-based task manager (who, again, demanded yearly payments). It followed GTD, but didn't force anything down your throat and even had several non-GTD features that appealed to me (tags, priorities, etc). It also has a 3rd party API so there are multiple iPhone apps to choose from. Being able to open any laptop in my house, or any computer I come across and see my tasks is liberating, even in just the one night I've been playing with it (laptop batteries kept dying). Perfection, right? What could be wrong now?</p>

<p>For starters, the web site's UI is ugly and mildly confusing. Yes, it's powerful, but it takes a lot of getting used to and navigating to get what I want. There's also a bigger problem. In theory sending any of my daily work tasks up to a 3rd party server is bad bad bad. In practice, I work on an open source project and the majority of my tasks are for things in my home life. However, now I'm concerned about any strategy that isn't pen and paper since every multi-machine sync solution requires a third-party server. That said, my binder could get stolen on a trip, and it's clearly not encrypted, so it could leak just as much. The only truly safe solution would be to use a single work laptop with disk encryption and lug it everywhere, which violates requirement number two. This has my stomach in knots, enough so that I'm thinking about going back to Things and manually copying around folders.</p>

<p>One thing that I'm still searching for is a solution for calendaring. Tasks are just one aspect of organization. I still have to get to my appointments on time. It would be nice to have one program to be able to check calendar and tasks, especially on the iPhone where context switching is expensive. There's a phone app called Pocket Informant that duplicates/replaces the calendaring functionality of the built-in calendar app. It sync with Google Calendar as well as Toodledo. In that respect, it's perfect. However, it's really really complicated and clunky. It also doesn't support Toodledo's tags, and in a day of using it it's already corrupted itself once. That's fine, i just reset and did a re-sync (this is really why life in the cloud is awesome) and it's fixed, but makes me hesitant to spend the money on the software. Toodledo has its own iPhone app, but it lacks calendar, so I'd have to get the built-in calendar to behave with calDav, something it only wants to do begrudgingly. For example, I got it to see my work calendar, but only the first calendar. I guess when I get off the plane I'll try some hacks I've found to get it to see others. These are things I don't have to do with PI.</p>

<p>Congratulations if you made it this far. You're one of probably four (one of them is my beautiful wife, I love her dearly and have no clue why she puts up with me; that leaves you and two others). Where am I in all this task nonsense? I'm still not sure, though I don't have my binder with me this week on travel. I guess I'll have to find make something work, sink or swim.</p>

<p>Update from somewhere over Nevada: I decided to play some more with Things while I had my laptop and some time to kill. I went and entered all the tasks and projects that I had put into Toodledo just to ensure that Things could fit my workflow and something surprised me. It was so much easier using Things than the clunky Toodledo web UI that I'm almost ready to plop down my credit card. I'll be stuck with the poor sync hackery, but it might almost be worth it. I want to live in the cloud, I want to believe that there is no need for desktop software and that everything can be done on the web, but I don't think I can in this instance. At least the calendar side can mostly be online.<br/>
 </p></div>
    </summary>
    <updated>2010-01-26T00:23:18Z</updated>
    <category term="Things you wish you didn't know about me"/>
    <author>
      <name>pinkerton</name>
    </author>
    <source>
      <id>http://weblogs.mozillazine.org/pinkerton/</id>
      <link href="http://weblogs.mozillazine.org/pinkerton/" rel="alternate" type="text/html"/>
      <link href="http://weblogs.mozillazine.org/pinkerton/indexf.rdf" rel="self" type="application/rdf+xml"/>
      <subtitle>I try so hard to make things suck less...And miles to go before I sleep.</subtitle>
      <title>Sucking less, on a budget</title>
      <updated>2010-03-10T00:52:27Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/guide-to-the-internet-2000</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/Og5_0t6l-7c/guide-to-the-internet-2000" rel="alternate" type="text/html"/>
    <title>Guide to the Internet (2000)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Jabba approves of the internet" src="http://hicksdesign.co.uk/else/images/Mobile_Photo_22_Jan_2010_12_50_01-20100122-125200.jpg"/></p>

	<p>Leigh picked up a little gem from an antiques and curios shop in Burford, titled “The Internet A to Z”. This little tome was published in the year of our Lord 2000 (so possibly written in 1999), and it was interesting to see what difference 10 years makes.</p>

	<p>In particular, there were 2 very relevant entries:</p>

	<h3>Opera</h3>

	<p><img alt="IMG_0977" src="http://hicksdesign.co.uk/else/images/IMG_0977-20100121-161648.jpg"/></p>

	<h3>…and then iCab…</h3>

	<p><img alt="IMG_0976" src="http://hicksdesign.co.uk/else/images/IMG_0976-20100121-161628.jpg"/></p>

	<p>…ouch!</p></div>
    </summary>
    <updated>2010-01-22T18:54:17Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/guide-to-the-internet-2000</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://sam.brown.tc/entry/416/the-importance-of-teaching-your-clients-and-being-the-boss</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/_OLBMJ1WzT4/the-importance-of-teaching-your-clients-and-being-the-boss" rel="alternate" type="text/html"/>
    <title>Designer, not a construction worker</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><blockquote>
		<p>“I want my sites to look Safari in Safari, and IE6 in IE6. I most definitely do not want my sites to look like IE6 in Safari”</p>
	</blockquote>

	<p><cite>Sam Brown</cite></p>
<p><a href="http://hicksdesign.co.uk/journal/designer-not-a-construction-worker" rel="bookmark">Comment on this</a></p></div>
    </summary>
    <updated>2010-01-21T03:31:04Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://sam.brown.tc/entry/416/the-importance-of-teaching-your-clients-and-being-the-boss</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/why-you-can-never-work-full-time-</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/9aNcvY5VoME/why-you-can-never-work-full-time-" rel="alternate" type="text/html"/>
    <title>Why you can never work 'full time'</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><blockquote>
		<p>“Someone asked me the other day what percentage of my day was spent doing what. Yesterday it was approximately one third general admin type stuff, one third client liaison type stuff and one third designing type stuff. If we ignore the fact that there isn’t really such a thing as a typical day – that is a pretty much a typical day.”</p>
	</blockquote>

	<p><cite>Ben Terrett (<a href="http://noisydecentgraphics.typepad.com/design/2007/08/interesting-min.html">Interesting Mini <span class="caps">CEO</span> Half Thoughts</a>)</cite></p>

	<p>When I started working freelance, I worked out my rates and estimated earnings based on a ‘typical’ eight hour day. What I didn’t really comprehend at the time was the fallacy of an eight hour day of solid work. There are so many factors that eat into that supposed ‘billable time’. </p>

	<ul>
		<li><strong>Admin</strong>. The obvious one. I hire a bookkeeper and an accountant to look after this side, but you still need to do a certain amount of admin yourself. Becoming a Limited Company brought with it more forms than I could ever imagine.</li>
		<li><strong>Illness</strong>. Your choice of lifestyle and diet can affect this, but even the fittest get the flu.</li>
		<li><strong>Hardware/software failures</strong>. Kernel panics, hard drive failures, crashy software.</li>
		<li><strong>Meetings</strong>. Not so much with clients (which are billable), but with accountants, bookkeepers, solicitors, financial advisors…</li>
		<li><strong>Enquiries</strong>. This has been a big problem for me, as before I worked for Opera, the level of enquiries was such that I could spend half of most days simply replying to them.</li>
		<li><strong>Phone calls</strong>. The ones unrelated to active projects. “I’ve lost my login details…” or “Can you just send me…”.</li>
		<li><strong>Lack of motivation</strong>. It sounds lame, but you will get days where no matter how hard you try, you can’t produce anything. Usually a sign of needing a break.</li>
		<li><strong>Power cuts</strong>, or lack of internets (something I see happen a lot with Twitter friends cut off by poor service from their <span class="caps">ISP</span>).</li>
		<li><strong>Children!</strong>. We love them, but every working parent surely dreads the call from school or nursery, asking them to collect their poorly child.</li>
	</ul>

	<p>No doubt there are many more.</p>

	<p>The problem with setting such an unrealistic expectation is two-fold. The first is that you often feel like a failure for not achieving those core hours (sometimes you do far, far more of course, but that doesn’t always help the guilt!). Secondly, it leads to underestimating project times, where your belief of how much you can achieve is sadly mistaken. </p>

	<p>There’s no easy way around this, it’s just one of the things I’ve got used to. Correction – <em>still</em> getting used to. I’m better than I was, but I still get this wrong.</p></div>
    </summary>
    <updated>2010-01-20T03:58:39Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/why-you-can-never-work-full-time-</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/dream-report-look-at-the-hygiene</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/lDVroc4hpok/dream-report-look-at-the-hygiene" rel="alternate" type="text/html"/>
    <title>Dream Report: Look at the Hygiene!</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>There’s not a lot left of last night’s dream, but here’s what there is:</p>

	<p>I was at a carvery, that looked like the kind of cafe you get inside a department store, but the layout was a little odd. After picking up a plate you then had to go around taking your vegetables off other people’s plates. Bizarrely, no one minded about this, but every table I went to I heard diners exclaim “Look at the hygiene! It’s so hygienic!”. </p>

	<p>I finally saw what everyone was getting excited about. In order to get the meat, you had to queue up to go past an airport security style desk, where you were checked for condiments, through a shower (with your plate of veg) and then put on hospital scrubs before joining the final queue for the meat. After that you simply exited via a little white swinging gate, with a plate of roast beef and soggy but sterilised vegetables.</p></div>
    </summary>
    <updated>2010-01-16T16:20:25Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/dream-report-look-at-the-hygiene</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/my-evernote-workflow</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/43SCNL2axyk/my-evernote-workflow" rel="alternate" type="text/html"/>
    <title>My Evernote Workflow</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="evernote" class="fr" src="http://hicksdesign.co.uk/else/images/evernote-20080929-210700.jpg"/>Shared notebooks are one of the many selling points of Evernote. Being able to automatically share content easily (no manual upload), with additional benefit of an <span class="caps">RSS</span> feed is genius – it almost becomes a blogging platform. As well notebooks shared with individuals (such as moodboards for clients) I have two public notebooks:</p>

	<p><a href="http://www.evernote.com/pub/hicksdesign/Scrapbook">Design Scrapbook</a> – where I keep any inspiration, be they images, <span class="caps">PDF</span>s or type samples. When clippings have come from webpages. the original <span class="caps">URL</span> is saved too.<br/>
<a href="http://www.evernote.com/pub/hicksdesign/CheeseDiaries">Cheese Diaries</a>) – where I take snaps of cheese labels to remember what I ate.</p>

	<p>Some notebooks are private, but synced, (such Opera work) and I’ve got used to a system to help ensure confidential information doesn’t appear where it shouldn’t.</p>

	<p>Simply, I have a default notebook called ‘Inbox’ where all clippings arrive. Every 3-5 days I go through and tag the content (type, * rating out of 5, colour palette etc) and then drag the clipping into it’s proper notebook. </p>

	<p>Often, I’ll combine various images and text by copying and pasting into a single note, to create a kind of simplistic moodboard. To do this, I often have to resize and crop images, but that can be done by right clicking the image, opening it in a graphics editor (Preview does the job quickly) and saving it. When I get back to the note, the image is altered.</p></div>
    </summary>
    <updated>2010-01-15T04:02:19Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/my-evernote-workflow</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/add-to-queue-in-boxee</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/uetLgavgJcE/add-to-queue-in-boxee" rel="alternate" type="text/html"/>
    <title>Add to Queue in Boxee</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>One of my favourite features in the new <a href="http://boxee.tv/">Boxee Beta</a> is a bookmarklet to add internet videos to a queue to watch in Boxee later. Once you’re logged into <a href="http://boxee.tv/">boxee.tv</a>, the bookmarklet is found bottom right. Clicking it on a page with supported video type sends it to Boxee with a confirmation message:</p>

	<p><img alt="Once the bookmarklet is clicked a confirmation message appears" src="http://hicksdesign.co.uk/else/images/OVERTURE_%28for_OTHER_HALFS%29_-_Brian_McBride_on_Vimeo-20100114-155816.png"/></p>

	<p>(The video in the screenshot was <a href="http://vimeo.com/2082920" title="for other halfs">live visuals for Overture</a> by Brian McBride, he of Stars of the Lid fame)</p>

	<p><img alt="Boxee homepage with queue" src="http://hicksdesign.co.uk/else/images/Screen_shot_2010-01-14_at_15.56.04-20100114-160019.png"/></p>

	<p>This is even more useful to me than all the various video apps that come with Boxee, is an example of what sets Boxee apart from just using <span class="caps">XBMC</span>. However, if you’re using <a href="http://rentzsch.github.com/clicktoflash/">ClicktoFlash</a>, with Youtube set to use H.264 video where possible, it will interfere with the magic, and Boxee can’t find the video. You just need to make sure it’s unchecked if you want to use the bookmarklet: </p>

	<p><img alt="ClickToFlash Settings" src="http://hicksdesign.co.uk/else/images/ClickToFlash_%E2%80%94_Settings-20100114-161307.png"/></p></div>
    </summary>
    <updated>2010-01-14T21:46:19Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/add-to-queue-in-boxee</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/the-ps3-hub</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/4CCjfkES5XU/the-ps3-hub" rel="alternate" type="text/html"/>
    <title>The PS3 Hub</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="http://ps3hub.tumblr.com/"><img alt="The PS3 Hub" class="wide" src="http://hicksdesign.co.uk/else/images/The_PS3_Hub-20100113-121336.png"/></a></p>

	<p>Almost a year ago, <a href="http://studiolift.com/">Matt Carey</a> and I set up a Tumblr blog  called “The PS3 Hub”, focussing on using the Playstation 3 as a media centre. We kept coming across handy tit bits and links, and a Tumblr account was the obvious, and easiest, choice. I love <a href="http://www.tumblr.com/">Tumblr</a>. It’s fab, not to mention <a href="http://www.metalabdesign.com/">MetaLab</a> who created the Tumblr theme that we use.</p>

	<p>Strangely, I seem to have forgotten to link to it from here in all that time. So, here’s the link to <a href="http://ps3hub.tumblr.com/">PS3 Hub</a>. </p>

	<p>P.S – a <a href="http://hicksdesign.co.uk/journal/playstation-3-media-centre">year later</a> and I’m still glad I went for the PS3 solution. It’s been a brilliant all in one solution. Now if we can just get a bit more codec support and sub-folders in the XMB…</p></div>
    </summary>
    <updated>2010-01-13T19:06:20Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/the-ps3-hub</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>http://weblogs.mozillazine.org/pinkerton/archives/020367.html</id>
    <link href="http://weblogs.mozillazine.org/pinkerton/archives/020367.html" rel="alternate" type="text/html"/>
    <title>I hate having to repeat myself</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I know we've had this conversation before, but I would like to request, beg, plead, persuade, demand, buy flowers and chocolate for, whatever it takes. I'm this close to getting down on my hands and knees and taking up religion. I'm bringing this up again because it's serious and I want to continue our relationship.</p>

<p>Please, Food Network. Please stop stretching the non-HD content on Food Network HD. Bobby Flay and Ted Allen are not really fat. Panning across a kitchen should not make me want to vomit from motion sickness. It really takes away from the viewing experience. How can you focus on the food when everything is stretched and warped beyond proportion? I don't like watching your channel when it's a non-HD show, and that means most of them because very few of your productions are. If I (and others) don't want to watch your channel, I'd bet your advertisers will eventually catch on.</p>

<p>Maybe I am in the minority. I wish I could start a Facebook group or whatever the kids these days do. Twelve people might even agree with me. Bravo gets it right, and their cooking shows are getting better and better. Cooking Academy is delightful. If you're not watching it, you really should, even though I think there's only 1 episode left. Maybe catch a marathon.</p></div>
    </summary>
    <updated>2010-01-10T21:31:33Z</updated>
    <author>
      <name>pinkerton</name>
    </author>
    <source>
      <id>http://weblogs.mozillazine.org/pinkerton/</id>
      <link href="http://weblogs.mozillazine.org/pinkerton/" rel="alternate" type="text/html"/>
      <link href="http://weblogs.mozillazine.org/pinkerton/indexf.rdf" rel="self" type="application/rdf+xml"/>
      <subtitle>I try so hard to make things suck less...And miles to go before I sleep.</subtitle>
      <title>Sucking less, on a budget</title>
      <updated>2010-03-10T00:52:27Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/radiohead-puppet-show-6th-january-2010</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/_kaZ4x_asCQ/radiohead-puppet-show-6th-january-2010" rel="alternate" type="text/html"/>
    <title>Dream Report: Radiohead Puppet Show</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>(As part of a drive to vary the content on this blog from either Dr Who, Media Centres or Apps, I’m going to start documenting the snippets of dreams that I still remember in the morning).</p>

	<p>The first part of the dream was too hazy, but I know it involved a school, and was probably another one of my ‘back being a youth leader on summer camp’ nightmares. It’s starts properly with Glenda the Goodwitch flirting with a centaur in one of the school rooms. I think the Centaur looked a bit like her husband Scott, so that was OK. </p>

	<p>Leaving them to do whatever they were going to do, I was suddenly in the car, driving some kids from the camp into town. The town looked decidedly Belgian, like the historic architecture of Bruges, but the car park was a boring modern affair. It then cuts to returning to the car, but the kids have gone and so has my car. </p>

	<p>After what felt like half an hour of panicking, I suddenly noticed something happening in one corner of the car park. On closer inspection, it was none other than Thom and Ed from Radiohead, performing a small puppet show set to music from Kid A. It was small but quite spectacular, and was obvious that they’d practiced a lot.</p>

	<p>When the show was over, I realised that the chap standing next to me in the ankle length red corduroy coat (!) was in fact Jeremy Keith. He looked up thoughtfully, stroking his chin and exclaiming “Yes, that was really rather excellent”. I knew it was all going to be OK.</p>

	<p>Then I woke up.</p></div>
    </summary>
    <updated>2010-01-09T03:50:38Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/radiohead-puppet-show-6th-january-2010</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://dashnote.resenmedia.com/</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/zzkSARHQsFk/" rel="alternate" type="text/html"/>
    <title>Dashnote</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="image-notes" src="http://hicksdesign.co.uk/else/images/image-notes-20100106-125359.png"/></p>

	<p>Dashnote is a well-thought-out dashboard widget interface for <a href="http://simplenoteapp.com/">Simplenote</a>, and my favourite of all desktop client/syncing solutions. </p>
<p><a href="http://hicksdesign.co.uk/journal/dashnote" rel="bookmark">Comment on this</a></p></div>
    </summary>
    <updated>2010-01-06T18:53:38Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://dashnote.resenmedia.com/</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>http://weblogs.mozillazine.org/pinkerton/archives/020361.html</id>
    <link href="http://weblogs.mozillazine.org/pinkerton/archives/020361.html" rel="alternate" type="text/html"/>
    <title>Some phone I heard about</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I've now spent the last few weeks messing around with my Nexus One and I've got a few things to say about it. Note that I am speaking for myself only, not my company of employment.</p>

<p>What's good:</p>

<p>- Fast, though I haven't used an iPhone 3GS. I hear it's fast too.<br/>
- Pretty screen. I'm a sucker for those things.<br/>
- Nice 5mp camera with flash!<br/>
- Voice input on all text fields. I didn't know that, except I watched Gizmodo's liveblog.<br/>
- Nice Google Maps, Gmail, and gTalk support, but that's nothing new to the N1.<br/>
- Weather app is pretty cool. It has a neat display of high/low temps over time.</p>

<p>What isn't:</p>

<p>- Scrolling feels wrong. It's jerky sometimes. When you get to the start/end, there's no indication that you are there. The iPhone lets you drag just past the end and then it springs back, giving you really great feedback that there's nothing more. When you get to the end on the N1, it just stops and nothing happens when you move your finger. It feels broken. The "app wheel" has this feature, but none of the apps themselves do.</p>

<p>- Managing background applications feels like Windows 3.1. If you install anything useful (Twitter, SportsTap, Facebook, etc etc), you will be installing an app that wants to be online 24/7, and on Android these apps can be as long as the phone has juice. And they will continue to do so until they run the phone out of juice. Don't want them to kill your battery? You have to go to the settings of every single app, individually, and tweak the 5+ different settings (per app) on update frequency, etc. It's also very confusing when certain apps run in the background. I have a SportsTap widget that will update me with sports scores, but it didn't start working until I interacted with its widget. Now it's telling me about things from last night (shouldn't it already have?), and now I don't know if I can stop it until it kills my battery (yes yes, there is a screen for that, but it's buried and non-techies would never ever find it). Yes, it sucks having to switch apps and not be able to run background processes on the iPhone, but if this is the alternative, I'll take the iPhone any day. Thanks Steve.</p>

<p>- Want to know what background app killed your battery? Too bad. Once the battery is drained and you reboot, the helpful screen that tells you what ate the battery gets reset.</p>

<p>- Out of the box with a Google account, you're on Gtalk as long as the phone has power, even if the display is off (you're marked as away). Yes, you can change this, but it's a setting, buried two levels deep in a menu. Where'd that battery go, again?</p>

<p>- If you can't tell, I left my phone on overnight and came back and the battery was drained. What did it? Beats me, the info was lost when the phone rebooted!</p>

<p>- Pressing the hard home button takes you to a fixed screen, not the last screen you were on when you launched the app.</p>

<p>- The hard back button is offset from where the actual sensor is, meaning you have to hit the button 3 or 4 times just right to get it to register and take you back.</p>

<p>- On AT&amp;T, it's EDGE/Wifi only. No 3G for that carrier. Most may not care about that, but if you're on AT&amp;T, you sure would.</p>

<p>- Want to silence your phone w/out unlocking it? There's no hard switch to flick. You have to unlock it and interact with it.</p>

<p>- Want all your music sync'd from iTunes? Bzzzt. You need a 3rd party application to do that, or you can manually copy all your music there. Endless fun for all ages!</p>

<p>- When I hold it in my hand for an extended period of time, my hand really cramps up. I can hold my iPhone for hours with no strain at all. I'm not sure what the difference is, but I mostly feel it in my thumb and across the breadth of my palm.</p>

<p>- No multi-touch to zoom. It seems like the obvious default gesture to zoom in and out, yet the N1 makes you double-tap to zoom. It doesn't feel very "direct manipulation", and after years with an iPhone, feels clunky.</p>

<p>With full disclosure that I'm an Apple fanboi, I'm impressed with the phone, but bothered enough by it that I don't have any reason to switch from my 1st gen iPhone. I'm sure this is a really impressive phone if you're upgrading from a 5 year old RAZR. If my iPhone suddenly up and died, I'd use this, but I would still be grumbly about it.</p></div>
    </summary>
    <updated>2010-01-05T19:23:12Z</updated>
    <author>
      <name>pinkerton</name>
    </author>
    <source>
      <id>http://weblogs.mozillazine.org/pinkerton/</id>
      <link href="http://weblogs.mozillazine.org/pinkerton/" rel="alternate" type="text/html"/>
      <link href="http://weblogs.mozillazine.org/pinkerton/indexf.rdf" rel="self" type="application/rdf+xml"/>
      <subtitle>I try so hard to make things suck less...And miles to go before I sleep.</subtitle>
      <title>Sucking less, on a budget</title>
      <updated>2010-03-10T00:52:27Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>http://weblogs.mozillazine.org/pinkerton/archives/020357.html</id>
    <link href="http://weblogs.mozillazine.org/pinkerton/archives/020357.html" rel="alternate" type="text/html"/>
    <title>Because</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I fast-forwarded (because, face it, nobody actually watches commercials anymore) through a Jim Beam commercial yesterday, on New Years Day. Isn't that an odd time to advertise? I mean, whose New Years resolution is to start drinking bourbon?</p>

<p>My Jersey Shore name is either Bones or Mikey Mortadella, though we're not actually watching it. We are completely hooked on True Blood, and if you've been following my tweets, you know we've now exhausted Season One which is all that's been released on DVD. Anyone work at HBO? I'll trade you a nightly build of Chromium for the second season!</p>

<p>One of my resolutions is to blog more this year. Hopefully I'll have enough to say about both Camino and Chrome/Chromium such that I'll need more than 140 characters.</p></div>
    </summary>
    <updated>2010-01-02T16:33:59Z</updated>
    <author>
      <name>pinkerton</name>
    </author>
    <source>
      <id>http://weblogs.mozillazine.org/pinkerton/</id>
      <link href="http://weblogs.mozillazine.org/pinkerton/" rel="alternate" type="text/html"/>
      <link href="http://weblogs.mozillazine.org/pinkerton/indexf.rdf" rel="self" type="application/rdf+xml"/>
      <subtitle>I try so hard to make things suck less...And miles to go before I sleep.</subtitle>
      <title>Sucking less, on a budget</title>
      <updated>2010-03-10T00:52:27Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=535</id>
    <link href="http://www.ardisson.org/afkar/2009/12/31/camino-2009-in-review/" rel="alternate" type="text/html"/>
    <title>Camino 2009 in Review</title>
    <summary>Sitting at this end of the calendar, 2009 seems like quite a long year; I’m exhausted, and I hope 2010 will be less of a marathon.  2009 was, however, still a good year for Camino, and that is what my annual look back is all about.

First and foremost, we released Camino 2, a significant [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Sitting at this end of the calendar, 2009 seems like quite a long year; I’m exhausted, and I hope 2010 will be less of a marathon.  2009 was, however, still a good year for Camino, and that is what my <a href="http://www.ardisson.org/afkar/2008/12/31/camino-2008-in-review/">annual</a> <a href="http://www.ardisson.org/afkar/2007/12/31/camino-2007-in-review/">look</a> <a href="http://www.ardisson.org/afkar/2006/12/30/camino-2006-in-review/">back</a> is all about.</p>
<ol>
<li>First and foremost, we released <a href="http://caminobrowser.org/blog/2009/#camino2.0">Camino 2</a>, a significant new release with lots of great new <a href="http://caminobrowser.org/features/">features</a> like Tab Overview, phishing and malware protection, drag-and-drop rearranging of tabs, Growl support, and new AppleScript features. As with all community projects, it took longer than anticipated, but based on the very positive reaction, it was well worth the wait.
<ul>
<li><a href="http://escapedthoughts.com/weblog/">Stuart Morgan</a> fixed the most bugs, while <a href="http://seanmurph.com/">Sean Murphy</a> wrote three major new features; <a href="http://jeffd.org/">Jeff Dlouhy</a>, <a href="http://www.inspiral.co.nz/">Christopher Henderson</a>, and Ilya Sherman also contributed major features to Camino 2.</li>
<li>Our localization teams stayed busy, so the Multilingual edition of Camino 2.0.x currently ships with 15 languages.</li>
</ul>
</li>
<li>In conjunction with the Camino 2 release, we rolled out a redesign of <a href="http://caminobrowser.org/">caminobrowser.org</a>.  Thanks to our friends at <a href="http://clearleft.com/">Clearleft</a> for the design work, <a href="http://samuelsidler.com/">Samuel Sidler</a> for implementing the redesign, and <a href="http://emps.l-c-n.com/">Philippe Wittenbergh</a> for helping to polish the rough edges afterwards.</li>
<li>While our focus was on Camino 2, we continued to release security and stability updates for Camino 1.6 throughout the year, and beginning in the summer we started landing code for what will become Camino 2.1.</li>
<li><a href="http://summerofcamino.com/">Dan Weber</a> was our Google Summer of Code student in 2009, working on enhancing the location bar.  Over the course of the summer, Dan implemented a new look for the autocomplete window as well as extending autocompletion to include <abbr title="Uniform Resource Locator">URL</abbr>s and titles of both bookmarks and history items (fixing a couple of the oldest remaining Camino bugs in the process).  Check out a <a href="http://caminobrowser.org/contribute/#nightly">nightly build</a> to see his work in action.</li>
<li>Our hard-working <a href="http://cl10n.rwx.it/active-contributors">localization teams</a> added two new languages this year, Slovenian and Turkish, and revived two translations, Chinese (Simplified) and Danish that have been missing for several major releases. Sadly, a few languages didn’t make the jump to Camino 2, so if Camino is not currently available in your language, drop by the <a href="http://cl10n.rwx.it/">caminol10n project website</a>, join the <a href="http://cl10n.rwx.it/mailing-list">mailing list</a>, and learn how you can help!</li>
</ol>
<p>I think that about wraps up the high points of the year, in a little briefer fashion than years past. <img alt=";)" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_wink.gif"/>   Thanks to everyone who was a part of the Camino community in 2009—developers, testers, localizers, and users—for a great year!  We’re always looking for new contributors, so if you’d like to help make Camino even better, there are <a href="http://caminobrowser.org/blog/2009/#helpmake">many ways</a> you can help out in the coming year.  In the meantime, enjoy Camino 2, Happy New Year, and welcome to 2010!</p></div>
    </content>
    <updated>2010-01-01T01:05:23Z</updated>
    <category term="Camino"/>
    <category term="Life"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:22Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=532</id>
    <link href="http://www.ardisson.org/afkar/2009/12/31/reminder-year-2010-bug-contest/" rel="alternate" type="text/html"/>
    <title>Reminder: Year 2010 Bug Contest</title>
    <summary>This is a rather late reminder of the “pool” for the 2010 installment of the annual “we break our site for your browser when the new year rolls around” broken browser-sniffing contest (2010 Gecko browsers will be available in about 28 hours from now).
As I noted in January, the “three-peat” is  Yahoo!’s to lose, [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>This is a rather late reminder of the “pool” for the 2010 installment of the annual “we break our site for your browser when the new year rolls around” broken browser-sniffing contest (2010 Gecko browsers will be available in about 28 hours from now).</p>
<p>As I <a href="http://www.ardisson.org/afkar/2009/01/01/and-the-winner-is%e2%80%a6/">noted in January</a>, the “three-peat” is  Yahoo!’s to lose, although there was <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=471816#c21">some talk</a> last January of Yahoo! actually doing away with their date checking. </p>
<p>Get your picks in now for both the site/company that will break and the reporter of the <a href="http://www.mozilla.org/projects/tech-evangelism/site/about.html">Tech Evangelism bug</a> who notices said site/company.  (For the record, my picks are Yahoo! <img alt=":P" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_razz.gif"/>  and <a href="http://emps.l-c-n.com/">Philippe Wittenbergh</a>.)  No actual prizes will be awarded, but both winners will be recognized in a future entry in this journal.</p>
<p>And remember: only you can prevent bad browser-sniffing! <img alt=":P" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_razz.gif"/> </p></div>
    </content>
    <updated>2009-12-31T05:24:00Z</updated>
    <category term="Camino"/>
    <category term="History"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/loo-copywriting</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/5kBQB2v8rmY/loo-copywriting" rel="alternate" type="text/html"/>
    <title>Loo Copywriting</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>While travelling this Christmas, I came upon some copywriting in a loo that I took umbridge with:</p>

	<p><img alt="Cant find the hand towels? Meet the new hand-dryer. It'll dry your hands completely in 10-15 seconds, using 80% less energy than traditional dryers. Still missing the hand towels? Well now, theres always your jeans" src="http://hicksdesign.co.uk/else/images/Mobile_Photo_30_Dec_2009_09_06_10-20091230-090935.jpg"/></p>

	<p>10-15 seconds and 80% less energy? Rather than 2 seconds and 0% energy? It’s really that last sarcastic last line that got to me though. It’s like the signs you get in hotels, claiming that they don’t want to wash your towels every day because they’re very concerned about the ‘environment’. ‘Well now’, I <span class="caps">DID</span> use my jeans, so that taught them! Fools!</p>

	<p><img alt="When constructing this bathroom we simply focused on you and the environment. So wherever possible we've used environmentally friendly materials to make your experience a little greener just as nature intended" src="http://hicksdesign.co.uk/else/images/Mobile_Photo_30_Dec_2009_08_53_40-20091230-090856.jpg"/></p>

	<p>Since when did we become Americans and start calling the toilet a ‘bathroom’? And surely ‘as nature intended’ would be actually be a large bush? </p></div>
    </summary>
    <updated>2009-12-30T15:09:05Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/loo-copywriting</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-18T04:50:03Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/opera-105-pre-alpha-next-week</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/lLNPpCcv2zc/opera-105-pre-alpha-next-week" rel="alternate" type="text/html"/>
    <title>Opera 10.5 pre-alpha next week</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="http://my.opera.com/chooseopera/blog/2009/12/17/jul-comes-early-this-year"><img alt="Christmas Gift" src="http://hicksdesign.co.uk/else/images/ill-O10.5labs2-20091217-165551.jpg"/></a></p>

	<p>Things have been a bit quieter around here lately, and here’s why. Everyone at Opera has been gearing up to release a sneaky peek of Opera 10.5 before Christmas comes! This isn’t even at an Alpha stage but it will show off, not necessarily new features (there are some though), but some rather big improvements in various areas. One of which has already been hinted at in the post on <a href="http://my.opera.com/chooseopera/blog/2009/12/17/jul-comes-early-this-year">Choose Opera</a> – <strong>speed</strong>.</p>

	<p>Can’t say anymore yet, but it will out on Tuesday 22nd December so you’ll soon be able to play with it, and find out.</p></div>
    </summary>
    <updated>2009-12-17T22:55:12Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/opera-105-pre-alpha-next-week</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-17T19:29:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/and-mary-and-joseph-had-</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/8Fu--h4qmAI/and-mary-and-joseph-had-" rel="alternate" type="text/html"/>
    <title>And Mary and Joseph had…</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Christmas Clip Art" src="http://hicksdesign.co.uk/else/images/IMG_0886-20091214-210447.jpg"/></p>

	<p>…a giant woodlouse by the look of it! Quality clip art used on the programme cover of my daughter’s school Christmas play.</p></div>
    </summary>
    <updated>2009-12-15T03:05:09Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/and-mary-and-joseph-had-</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-02-12T03:31:08Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/boxee-box</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/8w7qzvFUvzY/boxee-box" rel="alternate" type="text/html"/>
    <title>Boxee Box</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Front View" src="http://hicksdesign.co.uk/else/images/Front-SMALL-20091212-211445.png"/></p>

	<p>I’m more than just a few days late with this one, but I couldn’t let this pass without a mention! On Monday, Boxee unveiled their <a href="http://boxee.tv/box/">Boxee Box</a>, a collaboration with D-Link to provide their own hardware solution. My initial reaction was that it looked like an award, and something that wouldn’t fit snugly into existing setups:</p>

	<p><img alt="Back view" src="http://hicksdesign.co.uk/else/images/Back-SMALL-20091212-211757.png"/></p>

	<p>However, once I saw just how small it is…</p>

	<p><img alt="Size of a Coke Can" src="http://hicksdesign.co.uk/else/images/IMG_3755-300x225-20091212-211556.png"/></p>

	<p>…I changed my mind somewhat. In fact, the shape has very quickly grown on me, and in short, <strong>I really want one</strong>, despite already running Boxee via an Apple TV. (the restrictive supported formats, and size of, the PS3 are starting to get to me).</p>

	<p>It’ll be interesting to see if it get’s a UK release and what the cost will be. I seem to recall the US price being $200, which <em>should</em> translate into roughly £120. That would be a price point that would beat the recently released <a href="http://westerndigital.com/en/products/Products.asp?DriveID=735">WD TV Live</a> into a cocked hat. A substantially better interface experience, and built in Wifi and SD card slot to boot. </p>

	<p>I’m also rather interested in another new small solution that I recently discovered. Namely, the Acer Aspire Revo – a little nettop wonder that looks ideal as a Boxee Box:</p>

	<p><img alt="revo" src="http://hicksdesign.co.uk/else/images/revo-20091212-215451.png"/></p>

	<p>If you go for the Linux version of these, they can be had for around £170, a complete bargain. It doesn’t have the industrial design finesse of a Jonathan Ive designed product, but I actually rather like it for that. </p>

	<p>It’s funny, 3 years ago, I wouldn’t have considered a non-Apple solution for watching media on TV, but that’s changed a lot these days. </p></div>
    </summary>
    <updated>2009-12-13T04:08:59Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/boxee-box</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-26T19:52:39Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=526</id>
    <link href="http://www.ardisson.org/afkar/2009/12/08/camino-2009-fall-catch-up/" rel="alternate" type="text/html"/>
    <title>Camino 2009 Fall Catch-Up</title>
    <summary>Looking back, it appears that the last regular Camino update was in early August, nearly four months ago!  As you’ve no doubt noticed, Camino work did proceed, and if for some reason you hadn’t noticed, I’ll let you know that we shipped three security and stability updates (Camino 1.6.9,  1.6.10, and 2.0.1), one [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Looking back, it appears that the last regular Camino update was in early August, nearly four months ago!  As you’ve no doubt noticed, Camino work did proceed, and if for some reason you hadn’t noticed, I’ll let you know that we shipped three security and stability updates (Camino <a href="http://caminobrowser.org/blog/2009/#camino1.6.9">1.6.9</a>,  <a href="http://caminobrowser.org/blog/2009/#camino1.6.10">1.6.10</a>, and <a href="http://caminobrowser.org/blog/2009/#camino2.0.1">2.0.1</a>), one milestone (<a href="http://caminobrowser.org/blog/2009/#camino2.0b4">Camino 2.0 Beta 4</a>), and one major release (<a href="http://caminobrowser.org/blog/2009/#camino2.0">Camino 2</a>) since the last update.  We also launched a new <a href="http://caminobrowser.org/">website redesign</a>, brought the total number of languages in the multilingual edition of Camino 2.0.1 to 15 with the return of Polish, and have attempted to keep up with all the comments (overwhelmingly positive; thank you!) and bug reports we’ve gotten since the release of Camino 2—all the while battling illnesses and holidays.  Herewith a brief update on the smaller details of the past week or so.</p>
<ul>
<li id="smorgan"><a href="http://escapedthoughts.com/weblog/">Stuart Morgan</a> handled the major Camino code changes for 2.0.1. He got Mac OS X 10.6 and the Help menu talking again in non-English localizations, and he hooked up support for collecting emails in the Camino Crash Reporter (once email addresses are available for authorized users of crash-stats, we’ll be able to contact you for more information about your crashes when we need your help).</li>
<li id="hendy"><a href="http://inspiral.co.nz/">Christopher Henderson</a> wrote a patch to make the <a href="about:config">about:config</a> context menu start working, which is handy now that we officially acknowledge that about:config exists. <img alt=";-)" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_wink.gif"/>   He has also been working on some history-related changes and on implementing some missing bits in <code>CocoaPromptService</code> that the about:config context menu wants to use.</li>
<li id="cl"><a href="http://chrislawson.net/">Chris Lawson</a> gave Christopher’s patch a review, and he also began working through our backlog of unconfirmed bugs, following up on those that haven’t seen activity for a while.</li>
<li id="ss-phiw"><a href="http://samuelsidler.com/">Samuel Sidler</a> and <a href="http://emps.l-c-n.com/">Philippe Wittenbergh</a> have been polishing some of the slightly-rough edges of the new website design and doing their usual parts to help with bug triage.</li>
<li id="me">With the release work for 2.0.1 out of the way, I’ve also joined in on the website polishing and bug triaging.  Mostly, though, I feel like the sprint to 2.0 and then 2.0.1 is finally done, so I can take a moment and breathe. <img alt=";-)" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_wink.gif"/> </li>
</ul>
<p>That’s it for now; we’re slowly getting back in gear for the road to Camino 2.1, but the number of exciting changes will probably be light until after the new year.</p></div>
    </content>
    <updated>2009-12-08T06:40:27Z</updated>
    <category term="Camino"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>http://caminobrowser.org/blog/2386428923794812423231098284</id>
    <link href="http://caminobrowser.org/blog/2009/#camino2.0.1" rel="alternate" type="text/html"/>
    <title xml:lang="en-US">Camino 2.0.1 Released!</title>
    <content type="xhtml" xml:lang="en-US"><div xmlns="http://www.w3.org/1999/xhtml"><div>
<p>We’ve just released Camino 2.0.1, a maintenance release which <a href="http://caminobrowser.org/releases/2.0.1/">contains various security and stability updates</a> to Camino 2.0. All users are urged to update.</p>
<p>In addition, Camino 2.0.1 is available in the following languages:</p>
<ul class="req">
  <li>Chinese (Simplified)</li>
  <li>Danish</li>
  <li>Dutch</li>
  <li>English (US)</li>
  <li>French</li>
  <li>German</li>
  <li>Italian</li>
  <li>Japanese</li>
  <li>Norwegian (Bokmål)</li>
  <li>Polish</li>
  <li>Russian</li>
  <li>Slovenian</li>
  <li>Spanish (Castellano)</li>
  <li>Swedish</li>
  <li>Turkish</li>
</ul>
<p>As always, you can download <a href="http://caminobrowser.org/download/releases/2.0.1/">Camino 2.0.1 in English</a> (or the <a href="http://caminobrowser.org/download/releases/2.0.1-MultiLang/">multilingual version</a>) from our website, and existing Camino users will receive this release via software update.</p>
</div></div>
    </content>
    <updated>2009-12-04T21:00:00Z</updated>
    <published>2009-12-04T21:00:00Z</published>
    <author>
      <name>Samuel Sidler</name>
    </author>
    <source>
      <id>http://caminobrowser.org/blog/</id>
      <link href="http://caminobrowser.org/blog/" rel="alternate" type="text/html"/>
      <link href="http://www.caminobrowser.org/blog/atom.xml" rel="self" type="application/atom+xml"/>
      <title xml:lang="en-US">Camino. Blog</title>
      <updated>2010-02-23T21:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://cl10n.rwx.it/133 at http://cl10n.rwx.it</id>
    <link href="http://cl10n.rwx.it/node/133" rel="alternate" type="text/html"/>
    <title>Camino 2.0.1 l10n status</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Release notes can be found at <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=530177" title="Link to a Bugzilla bug">Bug 530177</a> (not finalized, but can be worked on). See the full article for the usual status matrix. There is an additional string to translate in <em>Frameworks/Breakpad.framework/Versions/A/Resources/crash_report_sender.app/Contents/Resources/[lang].lproj/Localizable.strings</em>: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=529989" title="Link to a Bugzilla bug">Bug 529989</a> comment #3.</p>
<p><strong>Please note that there will be one and only one release of any localized version of Camino. Therefore, it's very important that release notes translations are produced and sent as soon as possible.</strong></p>
<!-- <p>The final multilingual package is expected to be complete by Sat, June 20</p>
<p><strong>As of Mon. March 30th, I have received all the needed files from the l10n teams.</strong></p> -->
<div class="og_rss_groups"/><p><a href="http://cl10n.rwx.it/node/133" target="_blank">read more</a></p></div>
    </summary>
    <updated>2009-11-29T22:18:49Z</updated>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/55" term="To do"/>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/83" term="2.0.1"/>
    <author>
      <name>Marcello</name>
    </author>
    <source>
      <id>http://cl10n.rwx.it</id>
      <link href="http://cl10n.rwx.it" rel="alternate" type="text/html"/>
      <link href="http://cl10n.rwx.it/rss.xml" rel="self" type="application/rss+xml"/>
      <subtitle>The Caminol10n (Camino Localization) project is developed by people from every corner of the world contributing Camino translations, in order to make it even easier to adopt for international users. In case you're wondering, Camino is a fast, secure, easy to use browser built only for Mac OS X.
All published translations are packaged into a single distribution (Camino Multilingual), shipped at the same time when the original (English US) versions are released. Therefore, coordination and a strong common knowledge base among localization contributors is essential. If you want to help with translations and reviews, please read the information on the welcome page, register to this website, browse our tutorials (see menu on the left sidebar) and contact people who speak your language, to make your work more productive and more fun!

If you're looking for Camino end-user technical support, please consider these more specific destinations: Camino's official documentation and FAQ, Camino forum @mozillazine, your local Mozilla community.</subtitle>
      <title>Camino Localization Community (CaminoL10n)</title>
      <updated>2010-03-11T04:00:05Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/netmag-article-on-icon-design</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/VQ_rL9aVObU/netmag-article-on-icon-design" rel="alternate" type="text/html"/>
    <title>Netmag article on Icon Design</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>This month’s .net magazine (#196 December) features my article ‘Design the perfect icon’. focussing on icon design for websites, rather than for software. It expands on the talk I gave at @media earlier this year <a href="http://hicksdesign.co.uk/journal/icons-for-interaction">Icons for Interaction</a></p>

	<p><img alt="netmag front cover" src="http://hicksdesign.co.uk/else/images/IMG_0437-20091125-102725.jpg"/></p>

	<p>This is my first really big magazine article that I’ve written, and found 5500 words much harder than I thought, and probably won’t be writing another one in a hurry! However, I’m really pleased with result, and it’s given me an idea of how much harder it would be to write a book. </p>

	<p><img alt="first spread" src="http://hicksdesign.co.uk/else/images/spread1-20091125-103343.jpg"/></p>

	<p><img alt="second spread" src="http://hicksdesign.co.uk/else/images/skitched-20091125-103506.jpg"/></p></div>
    </summary>
    <updated>2009-11-25T16:27:25Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/netmag-article-on-icon-design</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-22T18:54:17Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>http://caminobrowser.org/blog/2386428923794812423231098283</id>
    <link href="http://caminobrowser.org/blog/2009/#helpmake" rel="alternate" type="text/html"/>
    <title xml:lang="en-US">Help make a great Mac browser!</title>
    <content type="xhtml" xml:lang="en-US"><div xmlns="http://www.w3.org/1999/xhtml"><div>
<p>In the days since the release of Camino 2, we’ve been thrilled by the positive response it has received.  We love making a great Mac web browser, and we’re very happy that you like to use it.  One of the most common criticisms we’ve heard is one we often make of ourselves: we don’t move fast enough. Part of this is our reputation for the high bar of quality we set for releases, but most of this is due to available manpower.  We’re a small, all-volunteer, open source project, not some skunkworks arm of a major corporation.</p>
<h3>Clearing up persistent misconceptions about Camino</h3>
<p>Contrary to what you may have read in some misinformed news coverage of the Camino 2 release, Camino is not a project of “the same people who make Firefox.”  Camino is an all-volunteer project, and while the Mozilla Foundation generously serves as the legal organization representing the Camino Project and provides ancillary support services (build machines, version control and bug tracking systems, and release mirrors), as the Foundation does for other “community projects,” that’s where the connection begins and ends. No one is earning a salary to work on Camino, there are no Mozilla Foundation or Corporation employees whose job descriptions include caring for Camino, and, incidentally, Camino is in no way “draining resources from Firefox.”  Camino does usually benefit from work Mozilla Corporation employees do on the Gecko rendering engine, but that’s only an added bonus all around; the Mozilla Corporation employees are doing that work to make Firefox better.</p>
<h3>How you can help</h3>
<p>The Camino Project is made up of a small, diverse group of volunteers who work on Camino on nights, weekends, and other bits of spare time.  Our developers range from pilots to students and software developers.  Unlike browsers produced by companies with dozens of full-time employes assigned to develop, test, and release the product, Camino has less than one full-time person worth of developer time, spread out over approximately five people. Because we’re a small team, everyone has a chance to make an impact, and having more people can make a noticeable difference in our progress.  How can you help your favorite browser?</p>
<ul>
<li>If you know some Cocoa and Objective-C, there are plenty of opportunities to help out without having to go near C++ or Gecko/XPCOM.  You don’t have to be an Objective-C rockstar, either; we can help take Objective-C beginners and turn them into <a href="http://www.ardisson.org/afkar/2006/12/30/camino-2006-in-review/#froodian">developers with 100 bugfixes in a year</a>.  We have a <a href="http://wiki.caminobrowser.org/Development:Home_Page">development</a> section on our wiki with overviews, build instructions, and other helpful information, and you can also talk with us on <a href="http://caminobrowser.org/contact/#development">IRC</a>.</li>
<li>If you also know C++ and aren’t afraid to get your hands a bit dirty with Mozilla’s XPCOM, we have some bigger projects that require some plumbing in Gecko and our embedding layer.  (If you like working at even lower levels, there are also <a href="http://code.google.com/p/google-breakpad/issues/detail?id=321">some bugs</a> in the Breakpad crash reporting library we’d like fixed.)</li>
<li>If you’re bilingual or a polyglot, our <a href="http://cl10n.rwx.it/">localization teams</a> are always looking for new members to help out existing teams and to localize Camino into new languages.</li>
<li>Even if you just consider yourself a “normal user,” there are things you can do to help, too.  Stop by the <a href="http://forums.mozillazine.org/viewforum.php?f=12">Camino forum</a> on mozillaZine and see if you can help answer questions; maybe you’re a web developer and can look into why a website might be acting strangely for another user.  Tell your friends about Camino; we also have a number of <a href="http://wiki.caminobrowser.org/Promotion:Home_Page">badges</a> you can display on your website, blog, or profile page.</li>
<li>If we didn’t mention your skillset and you want to help out, <a href="http://caminobrowser.org/contact/">let us know</a>; there’s likely something you can do, too.</li>
</ul>
<p>In short, there are opportunities for just about everyone to contribute to help make Camino even better.  You don’t have to produce 100 patches to make a difference, either; every bit of code contributed is one more feature for Camino users to enjoy (or one less bug to annoy them).  Thank you again for being Camino users; we appreciate your support, and we hope some of you will consider helping make Camino an ever better Mac browser.</p>
</div></div>
    </content>
    <updated>2009-11-22T23:15:00Z</updated>
    <published>2009-11-18T23:15:00Z</published>
    <author>
      <name>Smokey Ardisson</name>
    </author>
    <source>
      <id>http://caminobrowser.org/blog/</id>
      <link href="http://caminobrowser.org/blog/" rel="alternate" type="text/html"/>
      <link href="http://www.caminobrowser.org/blog/atom.xml" rel="self" type="application/atom+xml"/>
      <title xml:lang="en-US">Camino. Blog</title>
      <updated>2010-02-23T21:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>http://caminobrowser.org/blog/2386428923794812423231098282</id>
    <link href="http://caminobrowser.org/blog/2009/#camino2update" rel="alternate" type="text/html"/>
    <title xml:lang="en-US">Update on Camino 2 crashes</title>
    <content type="xhtml" xml:lang="en-US"><div xmlns="http://www.w3.org/1999/xhtml"><div>
<p>Since Camino 2 was released on Wednesday afternoon, we’ve been analyzing the early crash reports, looking for patterns and filing bugs.  Since this is the first time since the release of Camino 0.8 that all Camino users have been able to report crashes automatically, we weren’t quite sure what to expect. Besides the usual plug-in crashes (especially Flash Player), we’ve identified some common crashes that we can either help alleviate already or crashes where we’d like more information from those of you who are, unfortunately, experiencing them.</p>
<h3>Crashes on startup</h3>
<p>Most frustrating are the crashes that occur on startup because, if they are persistent crashes, they prevent you from using Camino at all (and they also prevent you from using the <code>about:crashes</code> feature to learn more about your crashes).  Early indications are that there are three common startup crashes: one caused by corrupt fonts on Mac OS X 10.6, one caused by internet plug-ins, and one that seems related to color management.</p>
<h4>Corrupt fonts</h4>
<p>The good news is that the most common of these startup crashes, a crash in <code>MacOSFontEntry::GetFontID</code> caused by corrupt fonts on Mac OS X 10.6, is already fixed in <a href="http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-2.0-M1.9/">Camino 2.0.1pre nightly builds</a>.  If you’re using Mac OS X 10.6 and crashing on startup, this is probably the crash you’re seeing, and using the nightly build of what will very soon become Camino 2.0.1 should fix the crashes.  We also recommend that you use Font Book to <a href="http://docs.info.apple.com/article.html?path=FontBook/2.2/en/5285.html">validate your fonts</a> and remove any corrupt ones (as well as to <a href="http://docs.info.apple.com/article.html?path=FontBook/2.0/en/fb1799.html">check for duplicate fonts</a>), since corrupt and duplicate fonts can cause problems for other applications and the system.</p>
<h4>Internet Plug-ins</h4>
<p>A second common startup crash is a crash in <code>dlopen</code> related to detecting installed plug-ins.  If you have plug-ins installed other than the common <code>QuickTime Plugin.plugin</code>, <code>Flash Player.plugin</code>, and the <code>JavaPluginCocoa.bundle</code>, try removing the other plug-ins from <strong>Internet Plug-Ins</strong> folder inside the <strong>Library</strong> folder in your user’s <strong>Home</strong> folder and in the <strong>Internet Plug-Ins</strong> folder inside the <strong>Library</strong> folder at the root of your hard disk.  If Camino launches successfully, you can quit Camino, add plug-ins back one by one, and relaunch Camino until you find the plug-in that is triggering the crash.  When you figure out which plug-in is causing the crash, please let us know, either by <a href="http://forums.mozillazine.org/viewforum.php?f=12">posting in the forum</a> or by <a href="http://caminobrowser.org/documentation/bugzilla/#crash">filing a bug</a>, so that we can try to stop the crash in the future.</p>
<h4>Color Management</h4>
<p>The final common startup crash is in <code>gfxPlatform::GetCMSOutputProfile</code>, which is code related to the (off-by-default) color management feature.  If you have enabled the <a href="http://caminobrowser.org/documentation/hiddenprefs/#EnableColorManagement">color management hidden preference</a> and are crashing on startup, try launching Camino with a fresh profile using the <a href="http://pimpmycamino.com/parts/troubleshoot-camino">Troubleshoot Camino</a> utility.  If Camino launches successfully, you can remove the color management preference from the <code>prefs.js</code> (and possibly <code>user.js</code>, if it exists) file in your Camino profile (the <strong>Camino</strong> inside the <strong>Application Support</strong> folder inside the <strong>Library</strong> folder in your user’s <strong>Home</strong> folder).  At this time we don’t know much about this crash, so if you are experiencing it, please let us know so that we can obtain more information and try to stop the crash in the future.</p>
<h3>Crashes customizing the toolbar</h3>
<p>If you crash when trying to customize the toolbar, make sure that you do not have the third-party 1Password software installed.  1Password does not currently support Camino 2, and all current versions of the 1Password software are incompatible with Camino 2.  If you have 1Password installed and crash when customizing the toolbar, you should uninstall 1Password’s Camino integration and contact 1Password support.</p>
<h3>Crashes with Google Desktop installed</h3>
<p>Google Desktop’s Camino integration is a common way of triggering a crash in Gecko’s code for drawing form controls.  If you have Google Desktop installed and frequently crash randomly while browsing, visit <code>about:crashes</code> to look up the crash reports you have sent.  If the “signature” in one or more of your crash reports contains <code>nsNativeThemeCocoa::DrawPushButton</code>, you are experiencing this crash, and you should uncheck “Web History” in the “Indexing” tab of Google Desktop’s preferences.</p>
<p>If you’re having trouble figuring out why you are crashing (for instance, if you are crashing at startup and don’t know whether your crashes are the ones described above), stop by the <a href="http://forums.mozillazine.org/viewforum.php?f=12">Camino forum</a> on mozillaZine and ask for help.  In addition, if you are experiencing persistent crashes, please let us know, either by <a href="http://forums.mozillazine.org/viewforum.php?f=12">posting in the forum</a> or by <a href="http://caminobrowser.org/documentation/bugzilla/#crash">filing a bug</a>.  If we’ve already learned about your crash, there’s a good chance that we can point you to a version of Camino containing a fix for the crash or at least supply a work-around in the interim.  If we haven’t heard of your crash before, letting us know about it is the first step to making it go away.  As always, thank you for using Camino.</p>
</div></div>
    </content>
    <updated>2009-11-22T23:15:00Z</updated>
    <published>2009-11-18T23:15:00Z</published>
    <author>
      <name>Smokey Ardisson</name>
    </author>
    <source>
      <id>http://caminobrowser.org/blog/</id>
      <link href="http://caminobrowser.org/blog/" rel="alternate" type="text/html"/>
      <link href="http://www.caminobrowser.org/blog/atom.xml" rel="self" type="application/atom+xml"/>
      <title xml:lang="en-US">Camino. Blog</title>
      <updated>2010-02-23T21:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>http://weblogs.mozillazine.org/pinkerton/archives/020307.html</id>
    <link href="http://weblogs.mozillazine.org/pinkerton/archives/020307.html" rel="alternate" type="text/html"/>
    <title>Camino 2.0 Released!</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I am very proud to announce today's release of Camino 2.0, <a href="http://caminobrowser.org">available for download from our website</a>. This release represents the culmination of over a year of hard work by our developers, testers, and localizers and easily surpasses the high quality bar we have set in past releases.</p>

<p>I want to stress that this is a product of our community, including our users, who provided valuable bug reports and feedback along the way. I am constantly impressed with the community's enthusiasm for the project and the care and thought put into every feature. They should be proud of this product and their contributions to it. I think it says a lot about the community that an open source project can have such high quality and attention to detail. Remember, none of these folks are getting paid. This is solely a labor of love.</p>

<p>I won't spend a lot of time listing features, since you can easily see them on the website, but many of the changes are under the hood. We're using a much more up to date version of Gecko (though not the latest for various reasons), and that will improve web page rendering and compatibility significantly from previous versions. If you find no other reason to upgrade, do it for the new Gecko.</p>

<p>Give it a spin, I'm sure you'll enjoy it!</p></div>
    </summary>
    <updated>2009-11-19T00:15:17Z</updated>
    <author>
      <name>pinkerton</name>
    </author>
    <source>
      <id>http://weblogs.mozillazine.org/pinkerton/</id>
      <link href="http://weblogs.mozillazine.org/pinkerton/" rel="alternate" type="text/html"/>
      <link href="http://weblogs.mozillazine.org/pinkerton/indexf.rdf" rel="self" type="application/rdf+xml"/>
      <subtitle>I try so hard to make things suck less...And miles to go before I sleep.</subtitle>
      <title>Sucking less, on a budget</title>
      <updated>2010-03-10T00:52:27Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=519</id>
    <link href="http://www.ardisson.org/afkar/2009/11/18/%e2%98%a2-alert/" rel="alternate" type="text/html"/>
    <title>☢ alert</title>
    <summary>If you’re reading this, it means that yet another major version of Camino is now in the wild.  Today we released Camino 2 (codenamed ☢, because our first choice of “kittens” didn’t have a Unicode glyph) after over a year in development. There are a number of major architectural changes under the hood that [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>If you’re reading this, it means that yet another major version of Camino is now in the wild.  Today we released Camino 2 (codenamed ☢, because our first choice of “kittens” didn’t have a Unicode glyph) after over a year in development. There are a number of major architectural changes under the hood that should make your overall browsing experience much better, and on top of that we’ve added a number of <a href="http://caminobrowser.org/features/">exciting new features</a>.  It has, once again, been a long(er-than-expected) journey, but we’re very proud of all the work we’ve put into Camino 2 and are pleased to offer you a new stable release.</p>
<p>The road to Camino 2 began in April of 2008 when we wrapped up work on Camino 1.6, although we had been performing architectural maintenance and related work to keep up with Gecko 1.9 changes since late 2007 (and some of the changes in Gecko itself were made all the way back in 2005, after the <code>MOZILLA_1_8_BRANCH</code> was cut on August 12, 2005).  Over the last year and a half, we’ve fixed more than 450 “bugs” (problems or new features), and 16 different people contributed patches for this release (<a href="http://escapedthoughts.com/weblog/">Stuart Morgan</a> again led the way with 119 fixes). Sean Murphy implemented three major features this release (tab dragging, phishing and malware protection, and rewritten Full Keyboard Access support in the browser window), and Christopher Henderson and Ilya Sherman showed up to implement full content zoom and Growl notifications for downloads, respectively, and stuck around to fix over four dozen other bugs between them.  Big thanks also to the one-third of that list of patch contributors who aren’t regular Camino developers; every little fix helps make Camino a better browser.</p>
<p>In some ways Camino 2 isn’t the revolutionary release we hoped it would be when we <a href="http://www.ardisson.org/afkar/2008/04/17/this-airplane-has-reached-its-cruising-altitude/">wrapped up Camino 1.6</a>, but it’s still a vast improvement over Camino 1.6 and a triumph for an all-volunteer, all-free-time development team in today’s world of corporate-sponsored browsers.</p>
<p>Thanks to our hard-working <a href="http://cl10n.rwx.it/">localization teams</a>, Camino 2 is available today in US English and <a href="http://caminobrowser.org/releases/2.0/">13 other languages</a>, with Polish expected to join that list as soon as our Polish localizer’s Mac is repaired.  Sadly, we had a few languages that shipped in Camino 1.6 disappear on us, so if your language is missing, please stop by the <a href="http://cl10n.rwx.it/mailing-list">caminol10n mailing list</a> and see how you can help bring these localizations back. (As I mentioned <a href="http://www.ardisson.org/afkar/2009/10/29/danish-is-coming-turkish-too/">earlier this year</a>, the work doesn’t require much specialized computer/software knowledge; you and a friend can bring Camino to thousands of users in your language!  For Camino 2, new contributors successfully revived the Danish localization, which was in Camino 1.0 but disappeared from Camino 1.5.)</p>
<p>This year I again went to bed the night before release while fearless webmaster <a href="http://samuelsidler.com/">Samuel Sidler</a> stayed up putting the finishing touches on the <a href="http://caminobrowser.org/">home page</a>, the <a href="http://caminobrowser.org/features/">Features page</a>, and implementing the new website design from the folks at <a href="http://clearleft.com/">Clearleft</a>.  One of these years <em>both</em> Sam and I are going to get a full night’s sleep before a major release, but this was not to be that year.  Aside from a few things here and there, it seems like the website and webserver bits went more smoothly this release than with 1.6.</p>
<p>What’s next?  Those of us who have been working on the website and release details for the past month or so are going to take a little rest.  Parts of the development team, which wrapped up development with a late-October push, are already starting to work on new features for Camino 2.1.  <a href="http://caminobrowser.org/download/releases/nightly/">Nightly builds</a> already include <a href="http://summerofcamino.com/">Dan Weber</a>’s 2009 Summer of Code work on location bar autocomplete, and we have some early plans for other features in Camino 2.1 (we’re always looking for contributors, so if you’re interested in helping make a great Mac browser, stop by the <a href="http://caminobrowser.org/contribute/">Contribute page</a> or find us on <a href="http://caminobrowser.org/contact/#development">irc</a>).</p>
<p>In the meantime, enjoy Camino 2.0 and let us know what you think!</p></div>
    </content>
    <updated>2009-11-19T00:05:19Z</updated>
    <category term="Camino"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>http://caminobrowser.org/blog/2386428923794812423231098281</id>
    <link href="http://caminobrowser.org/blog/2009/#camino2.0" rel="alternate" type="text/html"/>
    <title xml:lang="en-US">Camino 2.0 Released!</title>
    <content type="xhtml" xml:lang="en-US"><div xmlns="http://www.w3.org/1999/xhtml"><div>
<p>After over a year of hard work, the Camino Project is proud announce Camino 2.0, a major new update to the Camino web browser.</p>
<p>Camino 2.0 includes a number of new features and enhancements, including rearranging tabs by drag-and-drop, a new Tab Overview feature, phishing and malware protection, full content zoom, Growl notifications for downloads, improved support for Full Keyboard Access in the browser window, and displays web content using Mozilla’s Gecko 1.9 rendering engine. For a list of features in Camino, visit our <a href="http://caminobrowser.org/features/">features page</a>. Also, see the <a href="http://caminobrowser.org/releases/2.0/">release notes</a> for more detailed information about changes in Camino 2.0.</p>
<p>Camino 2.0 is available today in 14 languages:</p>
<ul class="req">
  <li>Chinese (Simplified)</li>
  <li>Danish</li>
  <li>Dutch</li>
  <li>English (US)</li>
  <li>French</li>
  <li>German</li>
  <li>Italian</li>
  <li>Japanese</li>
  <li>Norwegian (Bokmål)</li>
  <li>Russian</li>
  <li>Slovenian</li>
  <li>Spanish (Castellano)</li>
  <li>Swedish</li>
  <li>Turkish</li>
</ul>
<p>One other language, Polish, is expected to be available in the near future.</p>
<p>As always, you can download <a href="http://caminobrowser.org/download/releases/2.0/">Camino 2.0 in English</a> (or the <a href="http://caminobrowser.org/download/releases/2.0-MultiLang/">multilingual version</a>) from our website, and existing Camino users will receive this release via software update. Camino 2.0 is available for users of Mac OS X 10.4 or later.</p>
</div></div>
    </content>
    <updated>2009-11-18T22:00:00Z</updated>
    <published>2009-11-18T22:00:00Z</published>
    <author>
      <name>Samuel Sidler</name>
    </author>
    <source>
      <id>http://caminobrowser.org/blog/</id>
      <link href="http://caminobrowser.org/blog/" rel="alternate" type="text/html"/>
      <link href="http://www.caminobrowser.org/blog/atom.xml" rel="self" type="application/atom+xml"/>
      <title xml:lang="en-US">Camino. Blog</title>
      <updated>2010-02-23T21:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://cl10n.rwx.it/132 at http://cl10n.rwx.it</id>
    <link href="http://cl10n.rwx.it/node/132" rel="alternate" type="text/html"/>
    <title>Camino 2.0 is here!</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I'd like all the people active on this website and on the <a href="http://cl10n.rwx.it/mailing-list">CaminoL10n mailing-list</a> to raise a glass and toast to <strong>Camino 2</strong>!<br/>
You can find all the release details at <a href="http://caminobrowser.org" title="http://caminobrowser.org">http://caminobrowser.org</a> but here I want to praise the CaminoL10n contributors, who did a terrific job in handling this major release.</p>
<div class="og_rss_groups"/><p><a href="http://cl10n.rwx.it/node/132" target="_blank">read more</a></p></div>
    </summary>
    <updated>2009-11-18T01:39:02Z</updated>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/82" term="2.0"/>
    <category scheme="http://cl10n.rwx.it/taxonomy/term/1" term="Announcement"/>
    <author>
      <name>Marcello</name>
    </author>
    <source>
      <id>http://cl10n.rwx.it</id>
      <link href="http://cl10n.rwx.it" rel="alternate" type="text/html"/>
      <link href="http://cl10n.rwx.it/rss.xml" rel="self" type="application/rss+xml"/>
      <subtitle>The Caminol10n (Camino Localization) project is developed by people from every corner of the world contributing Camino translations, in order to make it even easier to adopt for international users. In case you're wondering, Camino is a fast, secure, easy to use browser built only for Mac OS X.
All published translations are packaged into a single distribution (Camino Multilingual), shipped at the same time when the original (English US) versions are released. Therefore, coordination and a strong common knowledge base among localization contributors is essential. If you want to help with translations and reviews, please read the information on the welcome page, register to this website, browse our tutorials (see menu on the left sidebar) and contact people who speak your language, to make your work more productive and more fun!

If you're looking for Camino end-user technical support, please consider these more specific destinations: Camino's official documentation and FAQ, Camino forum @mozillazine, your local Mozilla community.</subtitle>
      <title>Camino Localization Community (CaminoL10n)</title>
      <updated>2010-03-11T04:00:05Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=514</id>
    <link href="http://www.ardisson.org/afkar/2009/11/17/mac-os-x-10-6-2-your-fonts-and-launching-camino-2/" rel="alternate" type="text/html"/>
    <title>Mac OS X 10.6.2, your fonts, and launching Camino 2</title>
    <summary>Many of you might have noticed that, after upgrading to Mac OS X 10.6.2, Camino 2.0b4, Camino 2.0rc1, or Camino 2.0.1pre/2.1a1pre nightly builds have started crashing on launch or shortly after launch, perhaps as the first page was loading. (Some of you may have noticed these crashes ever since Mac OS X 10.6 arrived, but [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Many of you might have noticed that, after upgrading to Mac OS X 10.6.2, Camino 2.0b4, Camino 2.0rc1, or Camino 2.0.1pre/2.1a1pre nightly builds have started crashing on launch or shortly after launch, perhaps as the first page was loading. (Some of you may have noticed these crashes ever since Mac OS X 10.6 arrived, but the font changes in Mac OS X 10.6.2 seem to have made the crashes much more widespread.)  You might even be one of the people who have submitted one of <a href="http://crash-stats.mozilla.com/report/list?product=Camino&amp;platform=mac&amp;query_search=signature&amp;query_type=exact&amp;query=&amp;date=&amp;range_value=4&amp;range_unit=weeks&amp;do_query=1&amp;signature=MacOSFontEntry%3A%3AGetFontID()">these crash reports</a>.  </p>
<p>I have some good news and some bad news about these crashes.  The good news is that we’ve been looking at the problem for a while now, and Mozilla’s font gurus, <a href="http://blog.mozilla.com/nattokirai/">John Daggett</a> and Jonathan Kew have a couple of theories about the cause of the crashes (probably Mac OS X font cache corruption, yay! <img alt=":P" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_razz.gif"/>  ).  In addition, we generally know how individuals can “fix” the cause of the crashes on their own Macs.  </p>
<p>The bad news is that the individual “fix” so effective that we aren’t currently in contact with anyone who is still experiencing this problem, and reversing the “fix” doesn’t cause the crash to reappear. This makes it much more difficult to determine what exactly is wrong and to find the best way to fix the Mozilla code to make whatever the underlying problem is not crash Camino, now or in the future, for everyone.</p>
<p>If you’re currently experiencing this crash, we could use your help.  There are questions in need of some answers, and we’ll probably be able to generate some test builds (to log additional information and eventually to test proposed fixes) soon.  Please comment in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=514114">bug 514114</a> if you’re seeing this crash. (If you can’t get Camino to launch in order to check <a href="about:crashes">about:crashes</a> for your crash ids, you can open the <strong>Camino</strong> inside the <strong>Breakpad</strong> folder inside the <strong>Library</strong> folder in your users’s <strong>Home</strong> folder and look for files with names in the format of <code>CrashID=bp-0c24401b-93b6-4f7e-bcf7-8e4062091108.dmp</code>; paste the <code>bp-0c24401b-93b6-4f7e-bcf7-8e4062091108</code> part into the search field on <a href="http://crash-stats.mozilla.com/">crash-stats</a> to find your report.)</p>
<p>Finally, if you just want to make the problem go away and can’t help us track down the cause of the crash, you should open <strong>Font Book</strong>, check for and resolve any duplicate fonts (in the <kbd class="menu">Edit</kbd> menu), and validate all of your fonts, removing any ones that Font Book flags as having problems (in the <kbd class="menu">File</kbd> menu). You may also need to restart your Mac after removing duplicate and corrupted fonts.</p>
<p>Thanks for your help investigating this crash; we hope we’ll soon be able to make Camino stop crashing for everyone who is, or will be, experiencing this problem on Mac OS X 10.6.</p>
<p><strong>Update (2009-11-17):</strong> John came up with a patch that should fix the crash, and it was reviewed and approved this evening.  The fix should appear in tomorrow’s (2009-11-18) Camino 2.0.1pre, 2.1a1pre, and Firefox 3.0.16pre nightly builds.</p></div>
    </content>
    <updated>2009-11-17T05:34:55Z</updated>
    <category term="Camino"/>
    <category term="Software"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=504</id>
    <link href="http://www.ardisson.org/afkar/2009/11/09/crash-reporting-redux/" rel="alternate" type="text/html"/>
    <title>Crash Reporting Redux</title>
    <summary>As we move ever-closer to the release of Camino 2, I wanted to revisit the subject of crash reporting.  A few years ago, I wrote about crash reporting and how to help fight crashes with Talkback, our decrepit crash-reporting system from the early years of this century.  I realized a few months ago [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>As we move ever-closer to the release of Camino 2, I wanted to revisit the subject of crash reporting.  A few years ago, I <a href="http://www.ardisson.org/afkar/2007/03/04/talking-back-with-talkback/">wrote</a> about crash reporting and how to help fight crashes with Talkback, our decrepit crash-reporting system from the early years of this century.  I realized <a href="http://www.ardisson.org/afkar/2009/05/02/camino-2009-week-17-18/#comments">a few months ago</a> that if you started using Camino around or after the release of Camino 1.0, there’s a good chance you’ve never seen Talkback, since part of its decrepit nature was its <abbr title="PowerPC">PPC</abbr>-only binary, and Camino 1.0 coincided with the beginning of the transition to Intel-based Macs.  Now that Camino 2 includes modern crash reporting based on <a href="http://code.google.com/p/google-breakpad/">Google Breakpad</a> (tip o’ the hat to <em>mento</em> for bootstrapping modern open-source crash reporting), users with Intel Macs may be experiencing Camino crash reporting for the first time, so it’s a good time to revisit what you should do to help us find and fix crashing bugs.</p>
<p>Like Talkback before it, the Breakpad-based Camino Crash Reporter collects data about your crash and, when you agree, sends the data to Mozilla servers, where we (the Camino team) get to see the information in aggregate (and non-personal information in individual crash incidents).  </p>
<h3 id="how_work">How crash reporting works in Camino 2</h3>
<p>If Camino crashes, the Camino Crash Reporter pops up and asks you to add a comment and then to report the crash:</p>
<p id="reporter" style="text-align: center;"><a href="http://www.ardisson.org/afkar/wp-content/uploads/2009/11/Reporter.png"><img alt="Camino Crash Reporter" class="size-full wp-image-508" height="283" src="http://www.ardisson.org/afkar/wp-content/uploads/2009/11/Reporter.png" title="Camino Crash Reporter; we hope you never see this!" width="425"/></a></p>
<p>When you restart Camino, you can visit <a href="about:crashes">about:crashes</a> to find the report ID for the crash you just experienced and even see the processed report.</p>
<p id="aboutCrashes" style="text-align: center;"><a href="http://www.ardisson.org/afkar/wp-content/uploads/2009/11/aboutCrashes.png"><img alt="about:crashes" class="size-full wp-image-507" height="207" src="http://www.ardisson.org/afkar/wp-content/uploads/2009/11/aboutCrashes.png" title="about:crashes listing submitted crash reports" width="425"/></a></p>
<p>The about:crashes page contains a list of report IDs for crash reports you’ve submitted successfully to Mozilla’s crash collection servers.  If you click on the report ID, you can see the processed report for your crash.  Not all reports are processed immediately, so you may see a “processing” screen at first:</p>
<p id="processing" style="text-align: center;"><a href="http://www.ardisson.org/afkar/wp-content/uploads/2009/11/Processing.png"><img alt="The report is being processed" class="size-full wp-image-505" height="248" src="http://www.ardisson.org/afkar/wp-content/uploads/2009/11/Processing.png" title="Processing&#x2026;" width="425"/></a></p>
<p>Once processing is complete, you can see the <a href="http://crash-stats.mozilla.com/report/index/0c24401b-93b6-4f7e-bcf7-8e4062091108">full report</a> for your incident on <a href="http://crash-stats.mozilla.com/">crash-stats</a>:
</p><p id="incident" style="text-align: center;"><a href="http://www.ardisson.org/afkar/wp-content/uploads/2009/11/Incident.png"><img alt="Incident Report" class="size-large wp-image-506" height="370" src="http://www.ardisson.org/afkar/wp-content/uploads/2009/11/Incident-1024x892.png" title="Incident Report" width="425"/></a></p>
<h3 id="how_help">How you can improve the chances of your crash being fixed (and how to improve your crash report)</h3>
<p>We hope that you’ll never have to use the new crash reporting in Camino 2, but if you do, following these simple steps will make your report as useful as possible and improve the chances of the crash you experienced getting fixed.</p>
<p>When you experience a crash, <strong>the most important thing you can do is to allow the Camino Crash Reporter to submit your report to us</strong>.  If we don’t know a crash is happening, there is a zero percent chance that we will be able to fix it (if you’re happy seeing the same crash over and over, then don’t feel the need to submit a crash report <img alt=";-)" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_wink.gif"/>  ).  Many times we’re able to discover and fix crashes just from the aggregate data generated from users submitting crash reports to us.</p>
<p>Second, when you submit your report, <strong>please add a comment</strong>!  We know that crashing is frustrating and disrupting, and it is tempting to just press <span class="prefName">Submit</span> (or even <span class="prefName">Cancel</span>) and get back to what you were doing.  However, while the computer-generated data that is submitted in the crash report tells us “what” is happening, it often is insufficient to allow us to fix the problem, and comments can help bridge that gap.  When you add a comment, please be reasonably descriptive when telling us what actions you might have performed just before Camino crashed.  As you can see in the sample crash <a href="http://www.ardisson.org/afkar/category/camino/feed/#reporter">above</a>, I listed a number of specific steps that I performed just before Camino crashed.  </p>
<p>In addition to providing a comment, if you are comfortable providing the <abbr title="Uniform Resource Locator">URL</abbr> you were viewing when Camino crashed (and you know, or can look up in History, what that URL was), include it in your comment, too.  While Camino attempts to collect the URL you were on when Camino crashed, the URL is not displayed with your crash report for privacy reasons and is not readily available to anyone.  As I mentioned <a href="http://www.ardisson.org/afkar/2007/03/04/talking-back-with-talkback/#fn1">several years ago</a>, a good comment and a URL can be the difference between a frustrating crash and a fix.  Unfortunately, only a few reports out of every hundred currently include a comment, so there are many opportunities to understand and fix crashes that are currently being lost.</p>
<p>Finally, if you experience what you think might be the same crash, over and over—either whenever you visit a certain site you crash, or performing the same series of actions on a variety of sites leads to a crash—please <a href="http://caminobrowser.org/documentation/bugzilla/#found">file a bug</a>. While aggregate crash data can help us discover crashes, especially those that don’t otherwise seem to have a pattern, <strong>this data is no substitute for a bug report from someone who is actually seeing the crash frequently</strong>.  Sometimes specific crashes can still get lost in aggregate data, and filing a bug report on a crash that’s plaguing you can bring it to our attention.</p>
<p>When you file your bug report, please be sure to include the report IDs of incidents of this crash.  To get the report ID, type <kbd class="code">about:crashes</kbd> in Camino’s location bar and press <kbd class="shortcut" title="Return">Return</kbd>. Camino will display a list of crash reports you have submitted and their corresponding report IDs (a long string of letters and numbers). Copy the crash report ID corresponding to the crash you are reporting and paste the ID into your bug report, adding <kbd class="code">bp-</kbd> to the beginning of the pasted string. For example, a crash report id of <code>0c24401b-93b6-4f7e-bcf7-8e4062091108</code> should become <code>bp-0c24401b-93b6-4f7e-bcf7-8e4062091108</code> in your bug report, and Bugzilla will then link that string to your crash report. (<strong>Please do not paste entire crash reports into the “Comments” field of the bug report.</strong>)  Then, please be willing to answer questions and perform some tests as we work to understand and fix the crash you’ve reported in the bug.</p>
<p>Finally, when filing a bug or making a comment in a crash report, please don’t berate us.  We know you’re upset that Camino crashed on you, and we’re just as upset, but yelling at us doesn’t help.  Also, since at least one-third of crashes we see are caused by third-party software (for example, browser plug-ins, third-party hacks, or even fragile parts of Mac OS X itself), you might be yelling at the wrong party anyway.</p>
<h4>In summary:</h4>
<ol>
<li>Any crash report you submit is better than no report at all, so please always allow Camino Crash Reporter to do its job.</li>
<li>The more information you provide in your crash report (comment or URL), the more useful your report is to the developers.</li>
<li>For crashes you can reproduce or see over and over, reports filed with Camino Crash Reporter are no substitute for an actual bug report (with <!--a href="http://www.caminobrowser.org/support/bugzilla/#crash" title="Camino : Support : Bugzilla FAQ"-->crash report IDs<!--/a-->).</li>
<li>Please be polite and civil in your comments and bug reports; we’re all working towards the same goal here (Camino not crashing on you).</li>
</ol>
<p>All of which is a long way of saying “you could be the key to fixing the crash that is annoying you.” <img alt=";-)" class="wp-smiley" src="http://www.ardisson.org/afkar/wp-includes/images/smilies/icon_wink.gif"/> </p>
<p>Please enjoy Camino 2 (due out “real soon now”), and don’t fear the Camino Crash Reporter; it’s only trying to help.</p></div>
    </content>
    <updated>2009-11-09T06:58:51Z</updated>
    <category term="Camino"/>
    <category term="Software"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-23T03:00:21Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/icons-of-the-screen-icon-wired-uk</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/1YALVT1bgiU/icons-of-the-screen-icon-wired-uk" rel="alternate" type="text/html"/>
    <title>Icons of the screen icon - Wired UK</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Wired magazine article" src="http://hicksdesign.co.uk/else/images/IMG_0834-20091106-101603.jpg"/></p>

	<p>I got a wee mention in Decembers’ UK Edition of <span class="caps">WIRED</span> magazine, in a section called ‘Icons of the Screen Icon’. Nice!</p></div>
    </summary>
    <updated>2009-11-06T16:16:20Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/icons-of-the-screen-icon-wired-uk</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-21T03:31:04Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://www.thedieline.com/blog/2009/11/the-kraken-media-kit.html</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/U_F0CJKa6g0/the-kraken-media-kit.html" rel="alternate" type="text/html"/>
    <title>The Kraken Media Kit</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Kraken Rum Lable" src="http://hicksdesign.co.uk/else/images/6a00d8345250f069e20120a62905dc970b-550wi-20091103-224023.png"/></p>

	<p>TheDieline.com (a packaging blog you really should subscribe to) have lustworthy photos of the special media kit sent to promote Kraken black spiced rum.</p>
<p><a href="http://hicksdesign.co.uk/journal/the-kraken-media-kit" rel="bookmark">Comment on this</a></p></div>
    </summary>
    <updated>2009-11-04T04:41:25Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://www.thedieline.com/blog/2009/11/the-kraken-media-kit.html</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-20T03:58:39Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/using-evernote-as-a-design-scrapbook</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/3QSVJvz30Og/using-evernote-as-a-design-scrapbook" rel="alternate" type="text/html"/>
    <title>Using Evernote as a Design Scrapbook</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I’ve used iPhoto, Littlesnapper, a combination of Leap and Dropbox, but of late, I’ve reverted to using <a href="http://www.evernote.com/">Evernote</a> as my collection point for design scraps. </p>

	<p><img alt="Evernote" class="wide" src="http://hicksdesign.co.uk/else/images/Screen_shot_2009-10-30_at_20.36.09-20091030-203636.jpg"/></p>

	<p>The Desktop &gt; Web &gt; iPhone ecosystem is lovely. I have my design collection everywhere I go (also possible with the dropbox method I used to use, but there’s no way of tagging on the iPhone). The desktop client collects images and websites (as <span class="caps">PDF</span>s), and the iPhone client collects snapshots of sketches, camera photos and images saved from mobile Safari. Then the two ‘collectors’ get synced together to become one big collection:</p>

	<p><img alt="Diagram of using Evernote as a collector" src="http://hicksdesign.co.uk/else/images/Creative_Sponge.043-20091030-211220.png"/></p>

	<p>Some more reasons why Evernote has struck a chord with me are:</p>

	<ul>
		<li>I’m not restricted to single images, I can add <span class="caps">PDF</span>s, group images together (as a note), and add text notes.</li>
		<li>I love the widescreen layout (above) where I can view thumbnails, followed a large preview of the selected item on the right – no need for anymore clicks or different screens to view it</li>
		<li>Importing content is so easy. The context menu in Safari offers ‘Add Image to Evernote’ and ‘Add Page to Evernote as <span class="caps">PDF</span>’. The latter gives me a complete web page (not a print stylesheet version), and any links are still active (not so with a  <span class="caps">PNG</span>). The former works so nicely compared to some apps that get confused by links around images (cough, Littlesnapper).</li>
		<li>I’ve been experimenting with using a shared notebook to show moodboards/collected reference, and collaborate with clients, and this has so far gone OK. Would be even better if it was possible to layout images in a less linear way, and resize them, but that’s pushing the remit of Evernote.</li>
		<li>I find that I can often remember text within an image (especially as I often save a lot of found typography). Evernote’s <span class="caps">OCR</span> technology means I can find these images very quickly, and is often faster than tagging:</li>
	</ul>

	<p><img alt="searching image text evernote" src="http://hicksdesign.co.uk/else/images/Screen_shot_2009-10-30_at_20.45.52-20091030-204653.jpg"/></p>

	<p>I do tag as well, usually marking content type, dominant colours and sometimes a possible project reference and a star rating. I’ve also started using it for things like a Cheese Diary, where I take a snap of the the cheese label, to store it for later reference:</p>

	<p><img alt="Cheese Diary screenshot" src="http://hicksdesign.co.uk/else/images/Evernote-20091030-205135.jpg"/></p>

	<p>There are still some negative points about Evernote:</p>

	<ul>
		<li>My main bugbear from last year still stands: Evernote makes it really easy to get all sorts of content in, but it still makes it tricky to get it out again in it’s original form. In particular multiple images can’t be exported easily – at least not without an Evernote branded border. It’s my data Evernote, not yours, and I resent the enforced advertising, especially with premium account. The ‘best’ way to do this is to export as <span class="caps">HTML</span>, and then fish out the images from the various ‘resources’ folders. Or drag and drop them individually.</li>
		<li>You can’t select multiple items and add new tags. The only way currently is to drag them to an existing tag in the sidebar, which isn’t intuitive, or easy (depending on how many tags you have).</li>
		<li>I would love to be able to restrict my view on the iPhone to a particular notebook.</li>
	</ul>

	<p>Still, I love and use it despite these niggles, mainly because a lot of the things that niggled me last year (like thumbnails of images with loads of whitespace) have been fixed. Evernote development is ongoing and always improving, and I feel it’s a system I can put my trust in.</p></div>
    </summary>
    <updated>2009-10-31T03:18:40Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/using-evernote-as-a-design-scrapbook</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-16T16:20:25Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=501</id>
    <link href="http://www.ardisson.org/afkar/2009/10/29/danish-is-coming-turkish-too/" rel="alternate" type="text/html"/>
    <title>Danish is coming (Turkish, too)</title>
    <summary>Taking another break from working on tasks for the Camino 2 release, I wanted to write a little bit about our amazing team of localizers tonight.  As if someone was reading my mind, Christopher Henderson showed us this tweet he came across tonight.
Camino 2 is likely going to ship in English and 13 other [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Taking another break from working on tasks for the Camino 2 release, I wanted to write a little bit about our amazing team of localizers tonight.  As if someone was reading my mind, <a href="http://inspiral.co.nz/">Christopher Henderson</a> showed us <a href="http://twitter.com/alexpysaryuk/statuses/5249573703">this tweet</a> he came across tonight.</p>
<p>Camino 2 is likely going to ship in English and 13 other languages (attentive readers will note that this is down by two from the number of languages in Camino 1.6.10, but still three more than shipped in the initial Camino 1.6 release), all translated by our volunteer localizers from the <a href="http://cl10n.rwx.it/">caminol10n project</a>.  New to Camino 2 will be Danish (which last appeared in the Camino 1.0 series) and Turkish, making its debut as a Camino localization.</p>
<p>The story of Danish in Camino 2 is particularly worth telling.  At the end of September, about two weeks after we released Camino 2.0 Beta 4, Danish Camino user Allan Nyholm Nielsen <a href="http://forums.mozillazine.org/viewtopic.php?f=12&amp;t=1509675">posted a message</a> in the Camino discussion forum asking why Camino 1.6 was localized in Swedish and Norwegian but not Danish, and whether Camino 2 would include a Danish translation.  A member of the Camino development team replied that our localizations are all produced by volunteers and that while there had been a Danish localization in Camino 1.0.x and some work had been done for Camino 1.5, the leader of that team disappeared and the translation for 1.5 was never finished.  We also pointed Allan to the caminol10n project (and to another Danish Camino user on the forum, David Munch, who could possibly help) and urged him to think about reviving the Danish translation.</p>
<p>The very next day, Allan had posted to the caminol10n mailing list (and back in the Camino discussion forum) stating that he had signed up and had gotten started.  Two weeks after that, Allan <a href="http://mozdev.org/pipermail/caminol10n/2009-October/002789.html">posted a message</a> stating that he had essentially completed the translation of Camino 2 into Danish, and, after a week of polishing the translation, he <a href="http://mozdev.org/pipermail/caminol10n/2009-October/002820.html">reported</a> he had the complete translation ready.</p>
<p>In three weeks, we went from having no Danish translation and only an interested user who had never done any Mac OS X application localization to having a complete, peer-reviewed Danish localization for Camino 2.0!  Congratulations to Allan and David on this achievement.</p>
<p>If you would like to see Camino in your language, you too can make it a reality.  While not every language has a localization of an older version of Camino available to jump-start the process (there are a dozen languages that have shipped in past Camino versions that will not be in Camino 2.0, however), and while some teams take longer to complete a translation than others, you can still get started today and perhaps be ready to include your language in Camino 2.0.1 or 2.0.2.  There are a few, relatively simple, specialized tools to learn, but for the most part all you need to know is English and your own language.  There might even be other speakers of your language already <a href="http://cl10n.rwx.it/teams">interested in helping</a>, and the existing Camino translators are knowledgeable and can help you get started with the tools.</p>
<p>The Danish experience is not an isolated case, either; during the Camino 1.6.x series, we added three new languages, and one of them was complete in a matter of weeks (one took a month or so, and the third we learned about only when it was already complete).</p>
<p>If your language is already included in Camino, be sure to thank the <a href="http://cl10n.rwx.it/active-contributors">members of your language’s translation team</a> and ask them if there is any way you can help; existing teams are usually looking for new members, too, to help spread the workload.</p>
<p>Finally, it is with sadness that I report that Catalan, Czech, Polish, and Portuguese (pt-BR) will be missing from Camino 2.0, so if you are a Camino user who speaks one of those languages, now is the time for you to get involved.  Register with the <a href="http://cl10n.rwx.it/">caminol10n project</a>, join the <a href="http://cl10n.rwx.it/mailing-list">mailing list</a>, and bring your language back to Camino.</p></div>
    </content>
    <updated>2009-10-29T06:17:14Z</updated>
    <category term="Camino"/>
    <category term="Open Source"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-16T06:30:15Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://www.ardisson.org/afkar/?p=496</id>
    <link href="http://www.ardisson.org/afkar/2009/10/27/the-big-2/" rel="alternate" type="text/html"/>
    <title>The Big 2</title>
    <summary>Just a very brief post here tonight, to come up for air and to mark an occasion; I have a large backlog of things to write about in the near future, and also a lot more work to do.
I realized tonight that in the year that I have been handling the “build” side of Camino’s [...]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Just a very brief post here tonight, to come up for air and to mark an occasion; I have a large backlog of things to write about in the near future, and also a lot more work to do.</p>
<p>I realized tonight that in the <a href="http://www.ardisson.org/afkar/2008/10/19/camino-20a1-minibranch-bread-truck-factor-of-2/">year</a> that I have been handling the “build” side of Camino’s build and release process (at first sharing duties with the illustrious Mark Mentovai, and then on my own), I’ve produced builds for a bunch of releases: five Camino 2 milestones and five Camino 1.6.x security and stability releases (with at least one respin in the mix).  However, I had never been responsible for the build process for a major release, for the new version that’s all shiny, the culmination of the entire team’s hard work, and the build that’s tested and reviewed by the world.  Since 2006 (and Camino 1.0), Mark had always handled that.  Tonight, though, I felt the weight of tagging on my shoulders.</p>
<p>Which is a long, rambling, nostalgic way of saying that we now have a Camino 2 release candidate (note to the press and other interested parties: <em>release candidate</em>; Camino 2 <em>is not out yet</em>) for our community to hammer on, with special thanks to <a href="http://escapedthoughts.com/weblog/">Stuart Morgan</a> for fixing a dozen or so of our blockers and wanted/pseudo-blockers in the past two weeks and to Mark for the ninetieth-minute superreview on the very last patch. </p>
<p>I’ll have more to say about Camino 2 in the coming days, and the release will be here before you know it, but for now I’m just going to mark this milestone, point everyone to the <a href="http://forums.mozillazine.org/viewtopic.php?f=12&amp;t=1557035">usual places</a>, take off my build engineer’s cap, and go to sleep.</p></div>
    </content>
    <updated>2009-10-27T07:34:03Z</updated>
    <category term="Camino"/>
    <category term="Life"/>
    <author>
      <name>Smokey</name>
    </author>
    <source>
      <id>http://www.ardisson.org/afkar</id>
      <link href="http://www.ardisson.org/afkar/category/camino/feed/" rel="self" type="application/atom+xml"/>
      <link href="http://www.ardisson.org/afkar" rel="alternate" type="text/html"/>
      <subtitle>A journal at al-Qâhira fî Amrîkâ</subtitle>
      <title>افكار و احلام » Camino</title>
      <updated>2010-02-08T07:00:22Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://www.flickr.com/photos/36844288@N00/sets/72157620733079997/</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/tS6zKESKjc8/" rel="alternate" type="text/html"/>
    <title>Lettering - a set on Flickr</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="" src="http://hicksdesign.co.uk/else/images/Lettering_-_a_set_on_Flickr-20091026-155805.jpg"/></p>

	<p>A tasty Flickr set of found typography – focussing on British/London Underground/Transport styles., which of course is right up my street.</p>
<p><a href="http://hicksdesign.co.uk/journal/lettering-a-set-on-flickr" rel="bookmark">Comment on this</a></p></div>
    </summary>
    <updated>2009-10-26T21:58:28Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://www.flickr.com/photos/36844288@N00/sets/72157620733079997/</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-15T04:02:19Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/how-to-be-a-creative-sponge-2</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/wg82UqWQqFg/how-to-be-a-creative-sponge-2" rel="alternate" type="text/html"/>
    <title>How to be a Creative Sponge 2</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Creative%20Sponge" src="http://hicksdesign.co.uk/else/images/Creative_Sponge-20091024-100336.jpg"/></p>

	<p>This week I had the great pleasure of speaking at the 3rd Web Developer Conference in Bristol, along with <a href="http://elliotjaystocks.com/">Elliot Jay Stocks</a>, <a href="http://www.sazzy.co.uk/">Sarah Parmenter</a> and <a href="http://hereinthehive.com/">Dan Donald</a>. </p>

	<p>It was only a one-day conference, but I had a whale of time, meeting new folks like <a href="http://elliottkember.com/">Elliot Kember</a> (who shone on the 2 panels he attended), <a href="http://www.oliverker.co.uk/">Oliver Ker</a> and the legendary <a href="http://jontangerine.com/">Jon Tan</a>, with whom I’ve had emails and chat but never met in person. I also got to catch up with Ben Hostler, the creative director of Bristol-based agency <a href="http://www.wearebeef.co.uk/">Beef</a>, who I haven’t seen since I was at Middle School with him… 24 years ago!</p>

	<p>The talk I gave was an update of one I gave at @media 2007, ‘How to be a Creative Sponge’. Back then, Flickr was really the only option for sharing design collections online, but a lot has changed since then. We’re now spoilt for choice, but I explained my current system of choice – <a href="http://www.evernote.com/">Evernote</a>. Like Fireworks, I have a bit of a love/hate relationship with it in the past, but earlier criticisms have been fixed in recent updates. In particular, I’m finding that I can ofter remember text in an image that I’ve saved, so the <span class="caps">OCR</span> technology in Evernote makes it easy for me to find items I’ve collected. I would even say it was more effective than a tag.</p>

	<p><a href="http://dl.getdropbox.com/u/23369/Creative%20Sponge.pdf">Download the slides as <span class="caps">PDF</span></a> (27.8mb). I don’t tend to write presenters notes, so I’ve added these afterwards to try and help it make sense. All links mentioned in my talk are available <a href="http://delicious.com/jonhicks/sponge">on Delicious under the sponge tag</a>.</p>

	<p>I came away with a really good feeling about Bristol – it has a great developer/designer community, in a city that feels friendly and very un-intimidating. </p>

	<p>I also came away with a realisation that there is a whole book’s worth of material in ‘Malarkey’s Prank Calls’. Everyone I met seemed to have at least one experience of that delight to share ;)</p></div>
    </summary>
    <updated>2009-10-24T15:15:37Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/how-to-be-a-creative-sponge-2</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-14T21:46:19Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://my.opera.com/community/blog/2009/10/22/hicks-halloween-challenge</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/Sb6sOIKNd7E/hicks-halloween-challenge" rel="alternate" type="text/html"/>
    <title>Hicks' Halloween Challenge</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="" src="http://files.myopera.com/EspenAO/halloween/ill-HicksHalloweenChallenge-101-post.jpg"/></p>

	<p>Create a spooky Speed Dial background (1200×600 pixels and save it as <span class="caps">JPG</span> or <span class="caps">PNG</span>), and I’ll pick my favourite for a special Halloween edition of Opera! <a href="http://my.opera.com/community/blog/2009/10/22/hicks-halloween-challenge">See this post on My Opera</a> for details of how to enter!</p>
<p><a href="http://hicksdesign.co.uk/journal/hicks-halloween-challenge" rel="bookmark">Comment on this</a></p></div>
    </summary>
    <updated>2009-10-22T19:03:16Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://my.opera.com/community/blog/2009/10/22/hicks-halloween-challenge</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-13T19:06:20Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/whitelines-behance-dot-grid-book</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/qoTPuOb9L-A/whitelines-behance-dot-grid-book" rel="alternate" type="text/html"/>
    <title>Whitelines + Behance Dot Grid Book</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="" src="http://farm3.static.flickr.com/2436/4013363775_762e6fc058.jpg"/></p>

	<p>In <a href="http://hicksdesign.co.uk/journal/squared">Squared</a> I mentioned that I’d ordered both a <a href="http://www.whitelines.se/">Whitelines</a> pad, and the <a href="http://www.creativesoutfitter.com/Products/Dot-Grid-Book/9">Behance Dot Grid book</a> to try out. After trying them both for a few days, I thought I’d just post a few words about them.</p>

	<p>First of all, the Dot Grid Book. The packaging was sublime (see my <a href="http://www.flickr.com/photos/hicksdesign/sets/72157622465487601">photoset</a> on Flickr), and the book itself has a rubberised card cover, wiro-bound, with good strong stock inside. The rubbery cover freaked some people out that I showed it to, and has the habit of collecting fluff!</p>

	<p>There’s no show-through using black ink (maybe just the very, very slightest hint, but not enough to be a problem). The dots work quite well, and provide a lot of freedom. It’s also US letter sized, which is a change from A4. The only downsides are the that the wiro-bound spine gets snarled up (I’ve heard this from others, and experienced it already) and they felt the need to slap their logo on every page, which is a shame. Overall, a good idea, but really rather expensive for what it is (don’t faint -£14!). The more costly and elite a notebook is, the less I feel like using it. Too much pressure! I’ll enjoy using it, but I probably won’t be back for another one.</p>

	<p>I found I preferred the Whitelines layout the most. The grid lines are still there, but the use of negative-space whitelines is just enough to draw by, without being too noticeable. The tinting drops out when copying, and every page is logo free! The binding was very good, but the only drawback was the weight of the paper. It’s fairly light compared the Dot Grid Book, and you definitely get show-through. On the A4 perfect bound pad that I bought that’s not a huge problem. It’s not nearly as expensive as the Grid Book, and feels OK to leave one side blank. </p>

	<p>Looking over their product lines, my ideal Whitelines notebook doesn’t exist yet. I need one with a heavier no-show-through-paper, perfect bound with similar dimensions as my Moleskine sketchbook (21 × 13.2 × 2 cm). If by any chance the Swedish gods of negative space are listening -any chance of it?</p></div>
    </summary>
    <updated>2009-10-19T01:44:00Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/whitelines-behance-dot-grid-book</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-09T03:50:38Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://www.marshallalexander.net/</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/7O_6eYYxC2M/" rel="alternate" type="text/html"/>
    <title>Marshall Alexander - Paper Engineer</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Paper " src="http://hicksdesign.co.uk/else/images/skitched-20091017-190830.png"/></p>

	<p><img alt="Max" class="fr" src="http://hicksdesign.co.uk/else/images/skitched-20091017-191226.png"/>Marshall Alexander creates wonderful one-piece paper toys, available as free <span class="caps">PDF</span> downloads for you to make, including the Max figure (right) having a wild rumpus!</p>

	<blockquote>
		<p>Growing up in the seventies and eighties, my personal work is heavily inspired by retro design, videogames, movies, bright plastic toys and TV cartoons. Most of this work can be downloaded for free from my site. So get your knives and glue out, download some of the models and start building. Enjoy! </p>
	</blockquote>
<p><a href="http://hicksdesign.co.uk/journal/marshall-alexander-paper-engineer" rel="bookmark">Comment on this</a></p></div>
    </summary>
    <updated>2009-10-18T00:08:45Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://www.marshallalexander.net/</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2010-01-06T18:53:38Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://ow.ly/uEzv</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/cUHWL9jHRF4/uEzv" rel="alternate" type="text/html"/>
    <title>Holey Moley! Culture Vulture Interview</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Culture Vulture, who instigated the Moleskine Project <a href="http://hicksdesign.co.uk/journal/my-world">I participated in a few months ago</a>, have published a short interview with me. I get asked a question I’ve been waiting for -“What’s your favourite building?” </p>
<p><a href="http://hicksdesign.co.uk/journal/holey-moley-culture-vulture-interview" rel="bookmark">Comment on this</a></p></div>
    </summary>
    <updated>2009-10-17T23:59:40Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://ow.ly/uEzv</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2009-01-04T03:44:43Z</updated>
    </source>
  </entry>

  <entry>
    <id>http://hicksdesign.co.uk/journal/squared</id>
    <link href="http://feedproxy.google.com/~r/hicksdesign/~3/hRFy4ApPN60/squared" rel="alternate" type="text/html"/>
    <title>Squared</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Saddle-Stitch-heart" src="http://hicksdesign.co.uk/else/images/Saddle-Stitch-heart-20091013-161028.png"/></p>

	<p>My name is Jon Hicks, and I’m a stationery fetishist. I’m sure many of you are too. I love the design, feel, and most of all, smell of it. Some of my earliest and  happiest memories are of walking into <span class="caps">WHS</span>miths and smelling the pencils and paper, looking at the pads and notebooks (and being allowed to buy a new one!). Even in an age when my work is solely screen-based, I still lust after the senses-satisfying joy of new stationery.</p>

	<p>Just recently, I’ve started using graph paper pads again, particularly for sketching interface wireframes. I’ve tried plain paper, but I’m one of those people that can’t draw a freehand straight line to save their life. Then the wonkiness of the line just becomes a distraction.</p>

	<p>I’d been using a Paperchase notebook, which had a very faint dotted line squared paper, but it was only a few sheets amongst a variety of other types. It was ideal, but Paperchase don’t make a pad or notebook of just this type anymore, so after fruitless local searching and googling, I asked for Twitter feedback on a suitable alternative. The response was fantastic, and here are the three best options.</p>

	<p>The <a href="http://www.originaldesignersworkbook.com/">Original Designers Workbook</a> (Available from the <a href="http://designmuseumshop.com/catalogue/desktop-stationery/original-designers-workbook">Design Museum Shop</a>, although mostly out of stock at the moment) fits the criteria, as subtle graph paper pad:</p>

	<p><img alt="background1" src="http://hicksdesign.co.uk/else/images/background1-20091013-122135.png"/></p>

	<p>Here’s a sample of it’s grid:</p>

	<p><img alt="" src="http://www.formfiftyfive.com/wp-content/uploads/2009/04/grid.jpg"/></p>

	<p>The most-suggested option by far was the <a href="http://www.creativesoutfitter.com/Products/Dot-Grid-Book/9">Behance dot grid book</a> (available in the UK from <a href="http://www.strawberryandcream.com/brands/behance/behance-dot-grid-book.html">Strawberry and Cream</a>):</p>

	<p><img alt="Behance grid book close up" src="http://hicksdesign.co.uk/else/images/skitched-20091013-122529.png"/></p>

	<p><img alt="" src="http://hicksdesign.co.uk/else/images/skitched-20091013-122655.png"/></p>

	<p>Best of all though looks like the Swedish <a href="http://www.whitelines.se/">Whitelines</a> series, as suggested by <a href="http://www.davidhughes.org/">David Hughes</a> (available from Foyles in London, Amazon and <a href="http://www.papernation.co.uk/catalog/notebooks-whitelines-notebooks-c-74_135.html">Papernation</a> in the UK). </p>

	<p><img alt="Hard-bound-all-sizes-lying" src="http://hicksdesign.co.uk/else/images/Hard-bound-all-sizes-lying-20091013-154620.png"/></p>

	<p>Rather than use the traditional lined approach, it uses the negative space, creating a less destructive white lined grid:</p>

	<p><img alt="flowersCompare" src="http://hicksdesign.co.uk/else/images/flowersCompare-20091013-154421.png"/></p>

	<p>I should also mention the lovely <a href="http://konigi.com/store/product/wireframe-notepad">Konigi Wireframe Pad</a>, which also looked ideal, but sadly is US delivery only. Yes, I can always get someone in the US to send it on for me, but on principle I prefer not to. They offer a great range of free <span class="caps">PDF</span> templates that you print off, but that’s not a economical solution in the long term. Fine for the odd sheet here and there. Also, Inkjet prints just don’t have that lustfulness about them in the way new stationery does. </p>

	<p>So, I’ve ordered both the Behance Dot book and a Whitelines notebook to try them both out!</p></div>
    </summary>
    <updated>2009-10-13T21:14:19Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://hicksdesign.co.uk/journal/squared</feedburner:origLink>
    <author>
      <name>Jon Hicks</name>
    </author>
    <source>
      <id>http://hicksdesign.co.uk//journal/</id>
      <link href="http://hicksdesign.co.uk//journal/" rel="alternate" type="text/html"/>
      <link href="http://feeds.feedburner.com/hicksdesign" rel="self" type="application/rss+xml"/>
      <link href="http://pubsubhubbub.appspot.com" rel="hub" type="text/html"/>
      <subtitle>The journal of Hicksdesign, a creative partnership working with new and old-fangled media</subtitle>
      <title>The Hickensian</title>
      <updated>2009-12-30T15:09:05Z</updated>
    </source>
  </entry>
</feed>
