<?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>fordie's Blog &#187; tutorial</title>
	<atom:link href="http://fordie.co.uk/category/technical/tutorial/feed/" rel="self" type="application/rss+xml" />
	<link>http://fordie.co.uk</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 10 May 2011 17:58:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>jQuery intellisense in Visual Studio 2008 &amp; Dreamweaver</title>
		<link>http://fordie.co.uk/2008/11/13/jquery-intellisense-in-visual-studio-2008-dreamweaver/</link>
		<comments>http://fordie.co.uk/2008/11/13/jquery-intellisense-in-visual-studio-2008-dreamweaver/#comments</comments>
		<pubDate>Thu, 13 Nov 2008 20:00:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.net]]></category>
		<category><![CDATA[Dreamweaver]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[jQuery]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[technical]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[visual studio]]></category>
		<category><![CDATA[work]]></category>
		<category><![CDATA[code hints]]></category>
		<category><![CDATA[intellisense]]></category>

		<guid isPermaLink="false">http://fordie.co.uk/?p=136</guid>
		<description><![CDATA[jQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML it&#8217;s my weapon of choice when it comes to adding client side interactions to a site. It has rapidly gained popularity with web developers and designers &#8211; now software manufacturers are starting to take note with industry leaders like Adobe &#38; Microsoft [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://jquery.com/">jQuery</a> is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML it&#8217;s my weapon of choice when it comes to adding client side interactions to a site.</p>
<p>It has rapidly gained popularity with web developers and designers &#8211; now software manufacturers are starting to take note with industry leaders like Adobe &amp; Microsoft adding tools to their web development environments to help make jQuery development even quicker.</p>
<h2>Microsoft Visual Studio 2008</h2>
<p>I spoke previously about getting <a href="/index.php/2008/03/18/jquery-intellisense-in-visual-studio-2008/">Jquery intellisense in Visual Studio</a> 2008. Since then Scott Guthrie announced that <a href="http://weblogs.asp.net/scottgu/archive/2008/09/28/jquery-and-microsoft.aspx"><q>that Microsoft will be shipping jQuery with Visual Studio going forward</q></a> and then just yesterday I spotted <a href="http://blogs.msdn.com/webdevtools/archive/2008/10/28/rich-intellisense-for-jquery.aspx">this article</a> on the Visual Web Developer Team Blog with interesting updates to VS2008&#8242;s jQuery intellisense. The best development from my point of view is the ability to get code hints in your aspx &amp; master pages, not just your .js files.</p>
<p>In order to take advantage of these improvements you&#8217;ll first need to install <a href="http://msdn.microsoft.com/en-gb/vstudio/cc533448.aspx">Visual Studio 2008 Service Pack 1</a>and this <a href="http://code.msdn.microsoft.com/KB958502/Release/ProjectReleases.aspx?ReleaseId=1736">hot fix</a>.</p>
<p>Next download the <a href="http://code.jquery.com/jquery-1.2.6-vsdoc.js">jQuery IntelliSense documentation file</a> and save it in to your website in (probably a good idea to put it in the same folder as your jQuery file).</p>
<p>To add jQuery intellisense to a javascript file simply add this line to the top of the file:</p>
<pre name="code" class="xhtml:firstline[1]">
  /// &lt;reference path="jquery-1.2.6-vsdoc.js"/&gt;
</pre>
<p>To add it to aspx &amp; master pages do add the following lines to the head of your document.</p>
<pre name="code" class="xhtml:firstline[1]">
    &lt;% if (false)
       { %&gt;
        &lt;script src="~/[PATH_TO_REFERENCE_FILE]/jquery-1.2.6-vsdoc.js" type="text/javascript"&gt;
        &lt;/script&gt;
    &lt;%} %&gt;
</pre>
<h3>Points to note:</h3>
<ul>
<li>The &#8220;if (false)&#8221; statement will prevent the link to the reference file being rendered at runtime.  Microsoft are planning to release a hotfix to automatically search for the vsdoc file if the javascript file has a reference path in it meaning that these links in the head will become redundant.</li>
<li>If you are using aspnet&#8217;s MVC framework you need to ensure that your path to the reference file starts with a tilde otherwise VS will not find the reference file.</li>
<li>dding a link to the reference to a master page means all aspx pages that inherit that master page will have intellisense enabled.</li>
</ul>
<h2>Adobe Dreamweaver</h2>
<h3>CS4</h3>
<p>Adobe have just released <a href="http://www.adobe.com/products/dreamweaver/">Dreamweaver CS4</a> which also has support for jQuery code hinting. Adobe have taken a different approach to Microsoft, they use &#8220;introspection&#8221; to parse any javaScript files you have linked to your page and provide code hints.</p>
<p>This seems to work pretty well, and even handles chaining. However, I do have a couple of minor gripes. Firstly as soon as I typed &#8220;$(&#8221; dreamweaver told me I had a syntax error which really confused me, in the end I realised that just had to keep typing and DW would eventually figure out what I was doing. The other thing is, as a VS user I&#8217;m used to to code hits appearing strait away, in DW you have to press Ctrl + [space]. It&#8217;s not a big deal but would take some getting used to.</p>
<h3>Older Vesions</h3>
<p>Users of older versions of Dreamweaver <a href="http://xtnd.us/dreamweaver/jquery">this extension</a> from Chris Charlton adds excellent code hints for jQuery &amp;<a href="http://ui.jquery.com/"> jQuery UI</a> and what&#8217;s more it prompts you as soon as you hit &#8220;.&#8221; good work Chris!</p>
]]></content:encoded>
			<wfw:commentRss>http://fordie.co.uk/2008/11/13/jquery-intellisense-in-visual-studio-2008-dreamweaver/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>jQuery Intellisense in Visual Studio 2008</title>
		<link>http://fordie.co.uk/2008/03/18/jquery-intellisense-in-visual-studio-2008/</link>
		<comments>http://fordie.co.uk/2008/03/18/jquery-intellisense-in-visual-studio-2008/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 17:16:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.net]]></category>
		<category><![CDATA[annoyances]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[jQuery]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[visual studio]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[intellisense]]></category>

		<guid isPermaLink="false">http://fordie.co.uk/index.php/2008/03/18/jquery-intellisense-in-visual-studio-2008/</guid>
		<description><![CDATA[We&#8217;ve started using jQuery quite heavily to power our javascript widgets &#8211; without exception everyone who&#8217;s used it here has had their own little jQuery epiphany. It&#8217;s quite funny to watch, people tend to resist it to start with (particularly the hardcore coders) &#8211; but when they use it for a while and see how [...]]]></description>
			<content:encoded><![CDATA[<p><img src="/images/blog/intel.jpg" alt="intellisense in action" style="margin: 0pt 0.5em 0.5em 0pt; float: left" height="207" width="300" />We&#8217;ve started using <a href="http://jquery.com/">jQuery</a> quite heavily to power our javascript widgets &#8211; without exception everyone who&#8217;s used it here has had their own little jQuery epiphany. It&#8217;s quite funny to watch, people tend to resist it to start with (particularly the hardcore coders) &#8211; but when they use it for a while and see how much pain it can save you they soon come round.</p>
<p>One thing that was missing until now though was a way of getting jQuery intellisense in VS2008.  <a href="http://icanhaz.com/intellisense">Yesterday I spotted this article by  James Hart</a> which describes how this missing functionality can be be added. You need to make sure that you have this <a href="http://tinyurl.com/38vn68">Visual Studio 2008 Hotfix</a> installed then follow the instructions in James&#8217; article and as if by magic you&#8217;ll have intellisense for your jQuery code! This has gone down a treat here and looks set to make life an awful lot easier.</p>
]]></content:encoded>
			<wfw:commentRss>http://fordie.co.uk/2008/03/18/jquery-intellisense-in-visual-studio-2008/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using lists as an alternative to image maps</title>
		<link>http://fordie.co.uk/2007/06/26/using-lists-as-an-alternative-to-image-maps-2/</link>
		<comments>http://fordie.co.uk/2007/06/26/using-lists-as-an-alternative-to-image-maps-2/#comments</comments>
		<pubDate>Tue, 26 Jun 2007 14:38:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[css]]></category>
		<category><![CDATA[semantic markup]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[web standards]]></category>
		<category><![CDATA[xhtml]]></category>
		<category><![CDATA[lists]]></category>

		<guid isPermaLink="false">http://fordie.co.uk/index.php/2007/06/26/using-lists-as-an-alternative-to-image-maps-2/</guid>
		<description><![CDATA[eyes ears mouth oh my! Some time ago I got asked how to produce an &#8220;accessible alternative to an image map&#8220;. As long as Image Maps are implemented correctly there&#8217;s no reason why the shouldn&#8217;t be accessible however they may not always be the most appropriate or semantic way to mark up your content. In [...]]]></description>
			<content:encoded><![CDATA[<ul id="map">
<li id="eyes"><a href="#">eyes</a></li>
<li id="ear"><a href="#">ears</a></li>
<li id="mouth"><a href="#">mouth</a></li>
<li id="ilb"><a href="#">oh my!</a></li>
</ul>
<p>Some time ago I got asked how to produce an &#8220;<a href="http://www.dotdragnet.com/oldforum/index.php?act=ST&amp;f=4&amp;t=32322&amp;hl=image+map&amp;s=869a48eea4a1b2fb78a5379fe1c265ba">accessible alternative to an image map</a>&#8220;.</p>
<p>As long as Image Maps are <a href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#image-maps">implemented correctly</a> there&#8217;s no reason why the shouldn&#8217;t be accessible however they may not always be the most appropriate or semantic way to mark up your content.</p>
<p>In this example I&#8217;ve used a simple unordered list to describe some of the features of the young lady on the left, and positioned the list items over the top of her photo using CSS. The list is set to display:block and the height &amp; width are set to match the background image you want to use; position:relative is used to allow you to absolutely position the list items within the list. Each list item is given a unique id and absolutely positioned within the list, their height and width are also set in the CSS. At it&#8217;s most basic that&#8217;s all there is to it.</p>
<p>In this example I added borders round the list items highlight the active areas, you probably wouldn&#8217;t want to display them as they probably detract from the aesthetics of your image. I also used text-indent on the anchors to hide the text until you hover over them and then set the text-indent to 0 using the :hover pseudo class.<br />
<!-- more --></p>
<h2>Here is the XHTML used to mark this list up:</h2>
<pre name="code" class="xhtml">
     &lt;ul id="map"&gt;

         &lt;li id="eyes"&gt;&lt;a href="#"&gt;eyes&lt;/a&gt;&lt;/li&gt;

         &lt;li id="ear"&gt;&lt;a href="#"&gt;ears&lt;/a&gt;&lt;/li&gt;

         &lt;li id="mouth"&gt;&lt;a href="#"&gt;mouth&lt;/a&gt;&lt;/li&gt;

         &lt;li id="ilb"&gt;&lt;a href="#"&gt;oh my!&lt;/a&gt;&lt;/li&gt;

     &lt;/ul&gt;
</pre>
<h2>And here is the CSS:</h2>
<pre name="code" class="css">
#map {
 display:block;
 height:298px;
 width:200px;
 float:left;
 border:1px solid #FFA200;
 margin:0 10px 10px 0;
 background: url(/images/blog/girl.jpg) no-repeat;
 position: relative;
}

#map li {
position:absolute;
display:block;
list-style:none;
border:1px solid #ffcc00;

 }
#map li a {
 display:block;
 height:100%;
 width:100%;
 text-indent:-2000px;
 color:#ffcc00;
 font-weight:bold;
}

#map li a:hover {
 text-indent:0;
 text-decoration:none;
}

#eyes	{
 top:46px;
 left:71px;
 height:18px;
 width:44px;
}

#ear	{
top:46px;
left:132px;
height:26px;
width:21px;
}

#mouth	{
top:81px;
left:82px;
height:16px;
width:33px;
}

#ilb	{
top:177px;
left:80px;
height:63px;
width:81px;
}</pre>
<p>This article is an extended version of the example I originally published <a href="http://markford.me.uk/tutorials/listmap.html">here</a> on 30/01/2007</p>
]]></content:encoded>
			<wfw:commentRss>http://fordie.co.uk/2007/06/26/using-lists-as-an-alternative-to-image-maps-2/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Fordie&#8217;s Form System &#8211; a POSH way to mark up forms</title>
		<link>http://fordie.co.uk/2007/05/29/fordies-form-system-a-posh-way-to-mark-up-forms/</link>
		<comments>http://fordie.co.uk/2007/05/29/fordies-form-system-a-posh-way-to-mark-up-forms/#comments</comments>
		<pubDate>Tue, 29 May 2007 21:12:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[css]]></category>
		<category><![CDATA[semantic markup]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[web standards]]></category>
		<category><![CDATA[xhtml]]></category>
		<category><![CDATA[forms]]></category>
		<category><![CDATA[POSH]]></category>

		<guid isPermaLink="false">http://fordie.co.uk/index.php/2007/05/29/fordies-form-system-a-posh-way-to-mark-up-forms/</guid>
		<description><![CDATA[Form layout is one area where designers have struggled to find a sensible way to replace tables with nice clean semantic xhtml + CSS. In 2005 Andy Clarke demonstrated his approach to form layout at CSS for designers, He wraps the label around the input field, then put the actual label text in a span. [...]]]></description>
			<content:encoded><![CDATA[<p>Form layout is one area where designers have struggled to find a sensible way to replace tables with nice clean semantic xhtml + CSS.</p>
<p>In 2005 <a rel="acquaintance met" href="http://www.stuffandnonsense.co.uk/">Andy Clarke</a> demonstrated his approach to form layout at <a href="http://www.carsonworkshops.com/design-dev/holzschlag_clarke/17_18NOV2005_photos.html">CSS for designers</a>, He wraps the label around the input field, then put the actual label text in a span.</p>
<pre>&lt;label&gt; label text&lt;input type="text" /&gt;&lt;/label&gt;</pre>
<p>In the CSS he then sets the label to &#8220;display:block&#8221; and puts width on the spans. The list items effectively create rows spans columns.</p>
<p>This approach is fine when you only have two elements you want to appear on a line, however, when you start throwing other things into the mix (like required field markers or &#8220;help&#8221; links) you need a system that can handle more than two elements. This got me thinking…</p>
<p>In late 2005 I came up with a solution I call Fordie’s Form System (FFS).</p>
<p>FFS is based on the premise that a form is essentially a list of questions to which we need an answer, with label being the question and the input being the place for the user to answer it. That being the case, the obvious way to mark up the form (in my mind) is with lists.</p>
<p>I believe that as well as well as providing the structure to hold the form together, the lists add meaning to the markup – making FFS a POSH way to markup forms.</p>
<p><span id="more-89"></span></p>
<h2>FFS Structure</h2>
<p>Each group of label, input and related controls (for example help and validation) within the form is referred to as a &#8220;question&#8221;.</p>
<ol>
<li>The Form tag goes around the whole form</li>
<li>Related questions are grouped using fieldsets</li>
<li>Lists hold the questions within the fieldset (you can use ordered on unordered lists)</li>
<li>Each question is contained in a list item (li) containing:
<ul>
<li>A label</li>
<li>An input</li>
<li>Usually one or more of the following:
<ul>
<li>A required field marker</li>
<li>A &#8220;help&#8221; link</li>
<li>Validation Errors indicator</li>
</ul>
</li>
</ul>
</li>
</ol>
<h3>Basic FFS mark-up</h3>
<p>Here is an example of a form marked up in FFS</p>
<pre class="html">		&lt;form action="/" method="post" name="ffsExample" id="ffsExample"&gt;
			&lt;fieldset&gt;
				&lt;legend&gt;Your Details&lt;/legend&gt;
				&lt;ul&gt;
					&lt;li class="alt"&gt;
						&lt;label for="title"&gt;Title&lt;/label&gt;
						&lt;select name="title" id="title"&gt;
							&lt;option value="1"&gt;Mr&lt;/option&gt;
							&lt;option value="2"&gt;Mrs&lt;/option&gt;
							&lt;option value="3"&gt;Miss&lt;/option&gt;
							&lt;option value="4"&gt;Ms&lt;/option&gt;
						&lt;/select&gt;
					&lt;/li&gt;
					&lt;li&gt;
						&lt;label for="firstName"&gt;First name&lt;/label&gt;
						&lt;input name="firstName" id="firstName" type="text" /&gt;
						&lt;a href="/help/" class="help"&gt;help&lt;/a&gt;
					&lt;/li&gt;
					&lt;li&gt;
						&lt;label for="surName"&gt;Surname&lt;/label&gt;
						&lt;input name="surName" id="surName" type="text" /&gt;
					&lt;/li&gt;
					&lt;li&gt;
						&lt;label for="contactTel"&gt;Contact Telephone Number&lt;/label&gt;
						&lt;input name="contactTel" id="contactTel" type="text" /&gt;
						&lt;a href="/help/" class="help"&gt;help&lt;/a&gt;
					&lt;/li&gt;
					&lt;li&gt;
						&lt;label for="eMailAddress"&gt;Email Address&lt;/label&gt;
						&lt;input name="eMailAddress" id="eMailAddress" type="text" /&gt;
					&lt;/li&gt;
				&lt;/ul&gt;
			&lt;/fieldset&gt;
		&lt;/form&gt;</pre>
<h3>And here&#8217;s the CSS for the layout</h3>
<p>I&#8217;ve added comments to the CSS the explain what each rule does</p>
<pre class="css">		fieldset
		{	/* contains a list of related questions, you can have multiple fieldsets in a form */
			border:0;
			margin:0;
			width:100%;
			padding:0;
			clear:both;
		}
		fieldset ul
		{
			display:block;
			border:0;
			margin:0;
			padding:0;
		}
		fieldset li
		{	/* removes the bullet from &amp; adds vertical space in between list items  */
			display:block;
			list-style-type:none;
			clear:both;
			margin:0.2em 0 0.2em 0;
			line-height:2em;
		}
		fieldset li label
		{	/* Sets the width of the labels */
			display:block;
			width:33%;
			padding:0.2em 0 0.2em 0;
			float:left;
		}
		fieldset li input, fieldset li select
		{	/* floats the inputs left to sit next to the labels */
			float:left;
		}
		fieldset li a.help
		{	/* positions your "help" links, you may also have required field markers or
			   validation messages that you need position within the li*/
			float:right;
		}</pre>
<h3>Variations on a theme</h3>
<p>There are a couple of input types that need special treatment: radio &amp; check boxes tend to have their labels wrapped round them. This means that we need to introduce a new element to contain &#8220;question text&#8221; and change the width of the labels. By adding a class to the li we can change the attributes off all the elements contained within</p>
<pre class="html">		&lt;li class="radio"&gt;
			&lt;span&gt;Gender&lt;/span&gt;
			&lt;label&gt;&lt;input name="gender" type="radio" value="Male" /&gt;Male&lt;/label&gt;
			&lt;label&gt;&lt;input name="gender" type="radio" value="Female" /&gt;Female&lt;/label&gt;
		&lt;/li&gt;</pre>
<p>The CSS for the radio class looks like this</p>
<pre class="css">		li.radio span
			{
			/* This span is only required if you want to put additional descriptive text in the first column*/
				display:block;
				width:33%;
				float:left;
			}
		li.radio label
		{
			width:auto;
		}</pre>
<p>FFS is flexible and can handle many elements with in a list item. It can also display the form in a number of different ways simply by changing the CSS, for example:</p>
<ul>
<li>One question per row (using the CSS above will give this result)</li>
<li>Two questions per row (set the width of the li to 50% and float left)</li>
<li>One question per row, question above the input (set the label to 100% of the width of the li)</li>
</ul>
<p>You can see implementations of FFS here*:</p>
<ul>
<li><span style="font-size: 10pt; font-family: Arial"><a href="https://quoteandbuy.morethanbusiness.com/QuoteAndBuy/vans/YouAndYourVan.aspx">Moreth&gt;n</a></span></li>
<li><a href="https://rsa.ssp-uk.com/YORKSHIREBS/DataCapture/ContactInformation.aspx">Yorkshire Building Society</a></li>
</ul>
<p>*These are not particularly clean implementations, they need a lot of extra classes thrown at them to accommodate the asp.net generated html that the application produced.</p>
<hr />I have been planning this article for a long time, I’ve had it in draft form for over a year but I’ve only recently discovered a way to get it into the blog with the markup intact.I hope you find it useful.</p>
]]></content:encoded>
			<wfw:commentRss>http://fordie.co.uk/2007/05/29/fordies-form-system-a-posh-way-to-mark-up-forms/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Creating your own wordpress theme</title>
		<link>http://fordie.co.uk/2007/01/22/creating-your-own-wordpress-theme/</link>
		<comments>http://fordie.co.uk/2007/01/22/creating-your-own-wordpress-theme/#comments</comments>
		<pubDate>Mon, 22 Jan 2007 11:19:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[web standards]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://fordie.co.uk/index.php/2007/01/22/creating-your-own-wordpress-theme/</guid>
		<description><![CDATA[It was never my intention to use an existing wordpress theme for this blog. My original plan was to build a theme myself, however a combination of time pressure &#38; a creative mental block meant that I ended up with a theme that I&#8217;d downloaded (albeit slightly modified). My biggest stumbling block was that all [...]]]></description>
			<content:encoded><![CDATA[<p>It was never my intention to use an existing wordpress theme for this blog. My original plan was to build a theme myself, however a combination of time pressure &amp; a creative mental block meant that I ended up with a <a href="http://www.kaushalsheth.com/themes">theme that I&#8217;d downloaded</a> (albeit slightly modified).</p>
<p>My biggest stumbling block was that all the WP themes I looked at were pretty bloated and it was very difficult for me with my limited php knowledge to sus out what I needed to keep and what I could throw away. I searched in vain for &#8220;blank&#8221; wordpress theme after a couple of weeks I gave up.</p>
<p>A few days ago I <a href="http://www.stumbleupon.com/">stumbled upon</a> an <a href="http://ryanarrowsmith.com/2007/01/13/creating-a-wordpress-theme-part-i/">article by Ryan Arrowsmith</a> which has a link to that <a href="http://www.visual-assault.org/wpTheme_basic/index.html">elusive blank theme</a> and step by step instructions for creating your own theme! (Thanks Ryan)<br />
So now I have a blank theme sitting in the background on the server. Now all I have to do is decide how I want this site to look.</p>
]]></content:encoded>
			<wfw:commentRss>http://fordie.co.uk/2007/01/22/creating-your-own-wordpress-theme/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to create or edit a Firefox quick search</title>
		<link>http://fordie.co.uk/2006/10/31/how-to-create-or-edit-a-firefox-quick-search/</link>
		<comments>http://fordie.co.uk/2006/10/31/how-to-create-or-edit-a-firefox-quick-search/#comments</comments>
		<pubDate>Tue, 31 Oct 2006 12:04:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[browsers]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://fordie.co.uk/index.php/2006/10/31/how-to-create-or-edit-a-firefox-quick-search/</guid>
		<description><![CDATA[I like the quick search facility in firefox; the dictionary search is particularly useful. by typing &#8220;dict search-term&#8221; into the address bar you get a dictionary definition. The definitions used to be provided by dictionary.reference.com but for some reason in the last couple of versions it&#8217;s been the Merriam-Webster website. I just don&#8217;t think the [...]]]></description>
			<content:encoded><![CDATA[<p>I like the quick search facility in firefox; the dictionary search is particularly useful. by typing &#8220;dict search-term&#8221; into the address bar you get a dictionary definition.</p>
<p>The definitions used to be provided by dictionary.reference.com but for some reason in the last couple of versions it&#8217;s been the <font size="-1">Merriam-Webster website. I just don&#8217;t think the results are as good. I had a look at the <a href="https://addons.mozilla.org/firefox/search-engines/">search engines available as firefox add ons</a> but dictionary.reference.com wasn&#8217;t there so I set about finding a way to change firefox&#8217;s behaviour.</font> Here&#8217;s what to do&#8230;</p>
<ol>
<li>Click on &#8220;Bookmarks&#8221; in Firefox&#8217;s menu</li>
<li>Click &#8220;Organise Bookmarks&#8230;&#8221;</li>
<li>Expand the &#8220;Quick Searches&#8221; folder</li>
<li>Right click on the search you want to change (in this case I changed the dictionary search)</li>
<li>click &#8220;Properties&#8221;</li>
<li>Change the name of the bookmark to reflect the new site you are going to use</li>
<li>If you want to use dictionary.reference.com for your dictionary search change the location to &#8220;http://dictionary.reference.com/browse/%s&#8221;</li>
<li>Change the keyword if you want to use something other than &#8220;dict&#8221; to use this search from the address bar</li>
<li>Change the description to reflect your other changes</li>
<li>Click OK</li>
</ol>
<p>You can also use this method to create your own quick search for almost any site with a search facility.</p>
<ol>
<li>Go to the site you want to add and carry out a search using the usual search method.</li>
<li>Copy the URL (including query string) of the search results page. For example here is a search for &#8220;test&#8221; on theregister.com &#8220;http://search.theregister.co.uk/?q=test&#038;mode=site&#8221;.</li>
<li>Replace the search term in the query string with &#8220;%s&#8221;, so for the register we use &#8220;http://search.theregister.co.uk/?q=<strong>%s</strong>&#038;mode=site&#8221;.</li>
<li>Click on &#8220;Bookmarks&#8221; in Firefox&#8217;s menu</li>
<li>Click &#8220;Organise Bookmarks&#8230;&#8221;</li>
<li>Expand the &#8220;Quick Searches&#8221; folder</li>
<li>Right click, choose &#8220;New Book mark&#8221;</li>
<li>Enter the details for your new search. My Register search looks like this:</li>
</ol>
<p>Name:       El Reg Search<br />
Location:   http://search.theregister.co.uk/?q=%s&#038;mode=site<br />
Keyword:   reg<br />
Descrition: Search the register, Type &#8220;reg &#8221; into the address bar</p>
]]></content:encoded>
			<wfw:commentRss>http://fordie.co.uk/2006/10/31/how-to-create-or-edit-a-firefox-quick-search/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Share Adobe Photoshop Album data</title>
		<link>http://fordie.co.uk/2006/10/04/share-adobe-photoshop-album-data/</link>
		<comments>http://fordie.co.uk/2006/10/04/share-adobe-photoshop-album-data/#comments</comments>
		<pubDate>Wed, 04 Oct 2006 12:39:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[networking]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://fordie.co.uk/index.php/2006/10/04/share-adobe-photoshop-album-data/</guid>
		<description><![CDATA[Having spent many hours adding tags to Photoshop Album I was keen not to loose that information when I moved my photos to my new network hard drive, so I set about finding a way to keep it, and better yet share the tags across the network.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been using Adobe Photoshop Album for quite some time now; I have somewhere in the region of four or five thousand photos &#8220;tagged&#8221;. If you haven&#8217;t used tried it it&#8217;s worth a look you can <a href="http://www.adobe.com/products/photoshopalbum/starter.html">download the &#8220;starter edition&#8221; free from the Adobe site</a>.</p>
<p>Photoshop Album has a <a href="http://www.adobe.com/products/photoshopalbum/startercompare.html">number of features</a> but the main thing I use it for is keeping my photos organised. You create your own &#8220;Tags&#8221; within PSA these are a short description that you apply to your photos. The tags can be anything you want, but PSA ships with a number of categories that the suggest you use for your tags, People and Places for example.</p>
<p>You can add multiple tags to your pictures and then search through your photos based on the tags you have added; so if I want to find all the photos of Laura and Isla together I click on the Laura and Isla tags and PSA displays all the photos of the two women in my life.</p>
<p>Having spent many hours adding tags to Photoshop Album I was keen not to loose that information when I moved my photos to my new <a href="http://fordie.co.uk/index.php/2006/10/04/freecom-network-hard-drive/">network hard drive</a>, so I set about finding a way to keep it, and better yet share the tags across the network.</p>
<p>First I copied the photos from my computer&#8217;s hard drive onto the network hard drive. I copied everything under &#8220;My Pictures&#8221; to &#8220;E:/Photos&#8221;.<br />
The next thing to do was to find where PSA was storing the Catalogue, to do this open PSA and click on &#8220;help > system info&#8221; You should see this screen: <img src="/images/blog/PSA-systeminfo.jpg" /></p>
<p>Note the location and name of the catalog. I copied the Catalog file and renamed the copy My Catalog.mdb. This allows you to edit the file with <a href="http://office.microsoft.com/en-gb/FX010857911033.aspx">Microsoft Access</a>.</p>
<p>Open the database and look for the table called &#8220;ImageTable&#8221;; do a find and replace on &#8220;fImageOriginalFilePath&#8221; and &#8220;fMediaFullPath&#8221; replace the files original location with the new location, e.g. Find &#8220;C:\Documents and Settings\[user name]\My Documents\My Pictures&#8221; replace with &#8220;E:\photos&#8221;.</p>
<p>Close the database and change the extension back to .psa then copy your altered catalog onto the network drive. I copied mine to  &#8220;E:\Adobe\PSA\&#8221;.</p>
<p>Next we need to change where PSA looks for it&#8217;s catalog. Click on the start button then &#8220;run&#8221; in the text box type &#8220;regedit&#8221; and press enter. The registry editor will open. Press F3 in the &#8220;Find what:&#8221; box type the old path to your catalog (C:\Documents and Settings\All Users\Application Data\Adobe\Photoshop Album\Catalogs\).<br />
Under &#8220;Look At&#8221; uncheck &#8220;keys&#8221; then click on find. The registry editor will find two or three entries with this value; when you find one double click on it and change the value to the new location of your .psa file. Press F3 to search again until all entries in the registry are replaced.</p>
<p>If you are planning to install PSA on more than one machine you will need to repeat the registry editing on each machine once you have installed PSA.</p>
<p>You can now open Photoshop Album, it will now be looking at the shared area on your network.</p>
<p>Note: This method does have limitations you will *probably* only be able to access PSA from one machine at a time.</p>
]]></content:encoded>
			<wfw:commentRss>http://fordie.co.uk/2006/10/04/share-adobe-photoshop-album-data/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
	</channel>
</rss>

