<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>I am Ad Taylor &#187; features</title>
	<atom:link href="http://www.iamadtaylor.com/blog/features/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iamadtaylor.com</link>
	<description>The portfolio and blog of Ad Taylor</description>
	<lastBuildDate>Thu, 20 May 2010 22:49:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Helvetical</title>
		<link>http://www.iamadtaylor.com/helvetical/</link>
		<comments>http://www.iamadtaylor.com/helvetical/#comments</comments>
		<pubDate>Tue, 01 Sep 2009 16:13:17 +0000</pubDate>
		<dc:creator>Ad Taylor</dc:creator>
				<category><![CDATA[features]]></category>
		<category><![CDATA[Fluid]]></category>
		<category><![CDATA[Helvetical]]></category>
		<category><![CDATA[Helvetireader]]></category>
		<category><![CDATA[userstyle]]></category>

		<guid isPermaLink="false">http://www.iamadtaylor.com/?p=228</guid>
		<description><![CDATA[Pimping up Google Calendar, Helvetical is an extension of Helvetireader.]]></description>
			<content:encoded><![CDATA[<div style="padding:5px;border:1px solid #800000;background-color:#FFB3B4;color:#800000;margin: 10px 100px;">
<h2 style="color:#800000;text-shadow:none;">SMALL Helvetical update.</h2>
<p>Hi all. The new UI refresh of Google Cal is great, they have really done a brilliant job. Yet it hasn&#8217;t been too kind on Helvetical, making it unbearable to use. I set about trying to patch up the holes but the nature of a userstyle has made this an ugly and unproductive task. So I feel it is best to <strong>start from scratch</strong> again and build in some of the feature requests.</p>
<p>In the mean time, I have created a <a href="http://userstyles.org/styles/20669">patched up version</a> that makes the userstyle <strong>usable</strong> yet far from pretty. Download from <a href="http://userstyles.org/styles/20669">http://userstyles.org/styles/20669</a>. Obviously the alternative is to disable it for a while. </p>
<p>It would be great if we could use this time to build up a feature list for Helvetical 2. So leave a comment or <a href="mailto:hi@iamadtaylor.com?subject=Helvetical" >mail me</a>. BTW, this isn&#8217;t some excuse to put the project on the back-burner — I have penciled in the end of the month to complete.</p>
<p>Cheers, Ad</p>
</div>
<div class="container top">
<div id="image-holder" class="maincontent">
		<img src="/wp-content/themes/iamadtaylor/images/features/2009/helvetical_screenshot.png" title="Screen shot of Helvetical"/>
	</div>
<p><!-- #image-holder --></p>
<div id="heading" class="sidecontent">
<h1><span>Helvetical</span> pimping up Google Calendar.</h1>
<p>I know I am not alone in my love/hate relationship for Google&#8217;s apps, the functionality is brilliant but the UI is <strong>ugly</strong>. <a href="http://www.google.com/calendar" title="Google Calendar">Google Calendar</a> is most definitely not the exception to the rule, it hurts my eyes.</p>
<p><a href="http://www.iamadtaylor.com/helvetical" title="Helvetical">Helvetical</a> extends the work done by <span class="vcard"><a href="http://hicksdesign.co.uk/" title="Jon Hicks" class="fn url">Jon Hicks</a></span> on <a href="http://helvetireader.com/" title="Helvetireader">Helvetireader</a>, turning the mayhem of the Google interface into something that doesn&#8217;t offend. It was created for use with Fluid.app but I&#8217;m sure you can hack the CSS to work for your needs.</p>
<p>Please note that this is an on-going project so things are a bit rough around the edges. I hope to update soon.</p>
</p></div>
<p><!-- #heading --></p>
<div class="clear"></div>
</div>
<p><!-- .container --></p>
<div class="container bottom">
<div  class="maincontent">
<h2>Usage</h2>
<p>Thanks to the help of <span class="vcard"><a href="http://desandro.com/" class="fn url">David DeSandro</a></span>, Helvetical now works in Greasemonkey, Stylish, Fluid and others.</p>
<p>First of all you either need to have <a href="https://addons.mozilla.org/en-US/firefox/addon/748">Greasemonkey</a>, <a href="http://hetima.com/safari/stand-e.html">Stand</a>, <a href="http://fluidapp.com/">Fluid</a> or <a href="https://addons.mozilla.org/en-US/firefox/addon/2108">Stylish</a> installed. Relevant instructions can be found if you follow the links, the easiest option seems to be Greasemonkey for either Safari 4 or Firefox.</p>
<ul>
<li>Install the <a href="/userscripts/helveticalRELEASE/helvetical.user.js" title="Helvetical userscript">user <strong>script</strong></a> here.</li>
<li>Install the <a href="http://userstyles.org/styles/20669" title="Helvetical user style">user <strong>style</strong></a> from <a href="http://userstyles.org">userstyles.org</a>.</li>
</ul>
<h2>New icon</h2>
<p>I love using <a href="http://www.flickr.com/photos/joshuabrewer/3064355028/sizes/o/in/set-72157610267728694/">the icon</a> that <span class="vcard"><a href="http://www.flickr.com/photos/joshuabrewer/" class="fn url">Joshua Brewer</a></span>made for Helvetireader, it&#8217;s clean, Swiss and still sits nicely in the, oh so glossy, dock. I knocked up a quick version for you <a href="http://fluidapp.com/">Fluid.app</a> and <a href="http://prism.mozilla.com/">Prism</a> users out there so that HelvetiCal and Helvetireader can sit better on your dock.<br />
<a href="http://www.flickr.com/photos/adhoc01/4372688338/sizes/o/">Find it here.</a></p>
<p><img src="/wp-content/themes/iamadtaylor/images/features/2009/helvetical_icon_in_dock.png" class="h-icon" title="HelvetiCal icon in the dock next to the Helvetireader icon"/></p></div>
<div  class="sidecontent clearfix">
<h2>Updates</h2>
<p>I shall post all updates here but if you want to know about them as they happen follow <a href="http://twitter.com/HelveticalNews">@HelveticalNews</a></p>
<ul>
<li>Version 1.1 &#8211; Now with coloured &#8216;Other Calendars&#8217; and support for https:// hosted calendars.</li>
<li>Version 1.2 &#8211; Cleaned up for use with Google Gears [Help from <span class="vcard"><a href="http://twitter.com/martijnvdven" class="fn url">Martijn van der Ven</a></span>].</li>
<li>Version 1.3 &#8211; Fixed Firefox specific bugs (tasks, labs items,hover states etc)</li>
<li>Version 1.4 — Events are now colour coded in the &#8216;Months&#8217; section.</li>
<li>Version 1.5 — <strong>Maintenance</strong>. Moving elements back to their original position and filling in the new found blanks. Recommended.</li>
<li>Version 1.6 — Added RSVP colouring and line-throughs. Thanks to <span class="vcard"><a href="http://infoneer.net/" class="fn url">Chris Barth</a></span> for his help.</li>
</ul>
<h2>Useful links</h2>
<ul>
<li><a href="http://fluidapp.com/" title="Fluid">Fluid</a></li>
<li><a href="http://www.josefrichter.com/blog/offline-gmail-google-docs-helvetireader-etc-using-fluid/" title="Offline Gmail, Google Docs, Helvetireader, etc. using Fluid">Offline Gmail, Google Docs, Helvetireader, etc. using Fluid</a> by Josef Richter</li>
<li><a href="http://www.flickr.com/groups/fluid_icons/" title="Fluid Icons">Fluid Icons</a> – Though I do plan to have one for Helvetical soon.</li>
<li><a href="http://www.helvetireader.com/" title="Helvetireader">Helvetireader</a></li>
</ul></div>
<div class="clear"></div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.iamadtaylor.com/helvetical/feed/</wfw:commentRss>
		<slash:comments>81</slash:comments>
		</item>
		<item>
		<title>Archive Extractor &#8211; A Perch Hack / Plugin</title>
		<link>http://www.iamadtaylor.com/archive-extractor-a-perch-plugin/</link>
		<comments>http://www.iamadtaylor.com/archive-extractor-a-perch-plugin/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 10:29:57 +0000</pubDate>
		<dc:creator>Ad Taylor</dc:creator>
				<category><![CDATA[features]]></category>
		<category><![CDATA[Perch]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[plugin]]></category>

		<guid isPermaLink="false">http://www.iamadtaylor.com/?p=148</guid>
		<description><![CDATA[A plugin to help with the extraction of content itmes from the Perch database.]]></description>
			<content:encoded><![CDATA[<h1>Archive Extractor &#8211; A Perch Hack / Plugin</h1>
<div id="text-wrap">
<p class="edit note"><strong>Edit :</strong> Changes made as per Drew&#8217;s advice. Now deals with &#8217;shared&#8217; content and custom table prefix.</p>
<p>For sometime now I have been meaning to post this little hack I came up with — however I completely forgot. This is a hack for the <strong>brilliant</strong> &#8216;little&#8217; <abbr  title="Content managment system">CMS </abbr>, <a href="http://grabaperch.com/" title="Perch CMS">Perch</a> .<br/> It was made through necessity as I <strong>wanted</strong> to use Perch but I <strong>needed</strong> to be able to have news items from other pages on the front page. To my surprise it was nice and easy, and although I&#8217;m sure it will be inefficient, it seems pretty fast.</p>
<p>It is an incredibly simple plugin that pulls the JSON out of the Perch database and returns it. It doesn&#8217;t try to do anything else — no formatting, no nothing — just the way I like it.</p>
<p class="note"><strong>Standard disclaimer :</strong> I am not a server-side kinda guy, I can not take responsibility for anything this plugin does to your installation of Perch, server security or general happiness. That said, I can&#8217;t see how these lazy few lines of code could screw up much.</p>
<h2 class="installation">Installation</h2>
<p>Download the file and put it in your Perch &#8220;plugins&#8221; folder. This isn&#8217;t mandatory for it to work but just seems like a logical place to put it. Watch out when you next need to update Perch — Back up!!</p>
<h2 class="usage">Usage</h2>
<p>You must include the file at the top of the page you wish to use Archive Extractor. If your Perch directory is called &#8220;perch&#8221; then the include could be something like this:
</p>
<pre name="code" class="php">
	 include('perch/plugins/archiveExtractor/archiveExtractor.php');
</pre>
<p>To use just call the function with the 2 variables, the Perch Content name (e.g &#8220;News Item&#8221;) and the path to the page it is on (e.g &#8220;/news/index.php&#8221;). With the data returned you can iterate through the items and pull from it the data you want. <br/> Maybe best seen as an example:</p>
<pre name="code" class="php">
	// Call function with variables.
	$newsArchive = archiveExtractor('News Item','/news/index.php');
	// Check to see if there are any results
	if($newsArchive) {
		$limit = count($newsArchive);
		// Loop through all results
		for ($i=0; $i < $limit; $i++) {
			// In the example the word 'title' refers to the id of a content type
			// from the 'News Item' content template
			echo '
<li>
<h5>'.$newsArchive[$i]->title.' Trip</h5>

 on '.$newsArchive[$i]->information.'.</li>

';
		}
	}
</pre>
<p>If you want to extract data from shared regions, simply leave out the content path. It took me a while to understand the point of this (as this was recommended by <a href="http://grabaperch.com" class="vcard fn url">Drew</a>) but obviously it would be handy if you only wanted to extract part of the data (i.e. title and date).</p>
<pre name="code" class="php">
$newsArchive = archiveExtractor('News Item');
</pre>
<p><a href="/resources/archiveExtractor.zip" title="Download Archive Extrator" ><span class="download">Download</span></a><br />
<a href="#" title="Click to see plugin code" class="show-code">Click to view code</a></p>
<div class="clear"></div>
<div class="code-hide">
<pre name="code" class="php">
/*
	Archive Extractor - A Perch Hack
	By Ad Taylor - http://www.iamadtaylor.com
	For usage see :
	Creative Commons Attribution-Share Alike 2.0 UK: England &#038; Wales Licence
*/

function archiveExtractor($contentKey,$contentPage = '*')
{
	$query = queryDB($contentKey,$contentPage,$limit);
	if ($query) {
		foreach ($query as $key => $value) {
			$json = $value;
		}

		return PerchUtil::json_safe_decode($json);
	} else {
		return NULL;
	}

}

function queryDB($contentKey,$contentPage) {

	require_once $_SERVER['DOCUMENT_ROOT'].'/edit/config/config.php';

	$link = @mysql_connect(PERCH_DB_SERVER, PERCH_DB_USERNAME, PERCH_DB_PASSWORD);

	if (!$link) {
		return NULL;
	}
	else {
		mysql_select_db(PERCH_DB_DATABASE,$link);
		$sql = "SELECT `contentJSON` FROM `".PERCH_DB_PREFIX."contentItems` WHERE `contentKey` LIKE '$contentKey' AND `contentPage` LIKE CONVERT(_utf8 '$contentPage' USING latin1) OR '*' COLLATE latin1_swedish_ci";
		$result = mysql_query($sql, $link);
		return mysql_fetch_assoc($result);
		mysql_close($link);

	}
}</pre>
</div>
</div>
<p><!-- #text-wrap --></p>
]]></content:encoded>
			<wfw:commentRss>http://www.iamadtaylor.com/archive-extractor-a-perch-plugin/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Wet behind the ears</title>
		<link>http://www.iamadtaylor.com/wet-behind-the-ears/</link>
		<comments>http://www.iamadtaylor.com/wet-behind-the-ears/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 23:00:00 +0000</pubDate>
		<dc:creator>Ad Taylor</dc:creator>
				<category><![CDATA[features]]></category>
		<category><![CDATA[wet behind the ears]]></category>

		<guid isPermaLink="false">http://www.iamadtaylor.com/?p=113</guid>
		<description><![CDATA[The starting of a blog for web designers still wet behind the ears by a web designer wet behind the ears.]]></description>
			<content:encoded><![CDATA[<div id="wet">
<h1>Wet behind the ears.</h1>
<div>
<p>
										So the journey begins here and is signified by the start of this blog. <em>The journey?</em> Well I am in the process of (as in waiting for results) graduating from my degree in Multimedia Computing, therefore I am starting the arduous task of finding an agency to hire me. I <strong>really</strong> want to join an agency as I think it will further me as a creative, much more than going at it freelance like I am now.</p>
<p>
											With this said I am really enjoying my time — post uni — working on freelance work, and with every job I complete I find I become a considerably better designer/front-end developer. <em>[note — I have no idea what it is I am. Tried to work it out but can't find an answer]</em>
										</p>
</p></div>
</p></div>
<p><!-- #wet --></p>
<div id="behind">
<div>
<p>
										Though none of this is what I intended to post about. What I mean to ramble on about is the intended purpose of this blog and more importantly answer the question I kept on asking myself … <strong>What&#8217;s the point?</strong>
										</p>
<p>
											I have been wanting to start a blog for some time now but have been putting it off as I figured it would be, as the saying goes, teaching your grandmother how to suck eggs. I am still yet to graduate and have only been taking commercial projects for a year or two — to use yet another saying — I am a bit wet behind the ears.
										</p>
</p></div>
</p></div>
<p><!-- #behind --></p>
<div id="the">
<div>
<p>
											Recently I reached a conclusion on the matter; No matter how wet my ears are there will be someone out there with slightly damper ones. So this is my attempt to give back to the community the knowledge and resources&#8217; it gave (and still gives) me when I was starting out.
										</p>
<p>
											In a way this is my pre-emptive apology to those who may read something on this blog and think &#8216;this is horse sh**e&#8217;. The posts might be technically crude, they maybe even lean on the side of incorrect <strong>but</strong> hopefully they will be enough for some other WBTE designer to get on the right tracks.
										</p>
</p></div>
</p></div>
<p><!-- #the --></p>
<div id="ears">
<div>
<p>
										I plan to post hints, tips and code snippets in the &#8217;shorts&#8217; section of this blog. My aim is to make them the kind of thing that can be helpful off the back of a quick google search (and a boost in traffic wouldn&#8217;t hurt too). It is in this section, &#8216;features&#8217;, that I shall be posting tutorials, how-to&#8217;s and reviews that need the extra space and design this section can offer.
									</p>
<p>
										The first post is going to be the wet-behind-the-ears designers guide to git and github. I have spent a while searching for the perfect version control system for the non-techy and I think git and github are just that. Anyway, that&#8217;s for later on next week.
									</p>
</p></div>
</p></div>
<p><!-- #ears --></p>
]]></content:encoded>
			<wfw:commentRss>http://www.iamadtaylor.com/wet-behind-the-ears/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
