<?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>Orangeninja &#187; Projects</title>
	<atom:link href="http://www.orangeninja.com/tag/projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.orangeninja.com</link>
	<description>Life, the Universe, and Everything In It</description>
	<lastBuildDate>Mon, 22 Dec 2008 12:50:22 +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>WordPress Dynamic Links</title>
		<link>http://www.orangeninja.com/2007/07/04/wordpress-dynamic-links/</link>
		<comments>http://www.orangeninja.com/2007/07/04/wordpress-dynamic-links/#comments</comments>
		<pubDate>Wed, 04 Jul 2007 23:09:43 +0000</pubDate>
		<dc:creator>Frosty</dc:creator>
				<category><![CDATA[Projects]]></category>
		<category><![CDATA[Web Dev]]></category>
		<category><![CDATA[web dev]]></category>

		<guid isPermaLink="false">http://www.orangeninja.com/2007/07/04/wordpress-dynamic-links/</guid>
		<description><![CDATA[One of the problems I&#8217;ve found with WordPress (especially when creating a simplified setup for less techy people) is that there&#8217;s no separation between internal and external site links. Sure, you can make a link relative to the site root with a leading slash, but what happens when you change the structure of the site [...]]]></description>
			<content:encoded><![CDATA[<p>One of the problems I&#8217;ve found with WordPress (especially when creating a simplified setup for less techy people) is that there&#8217;s no separation between internal and external site links. Sure, you can make a link relative to the site root with a leading slash, but what happens when you change the structure of the site or move a page? Suddenly, all your links are dead. Surely a content management system should handle things like this?</p>
<p><span id="more-61"></span>Having hit this problem for a client site I&#8217;m working on, I decided to come up with a solution for it. In its current unpolished form, the Dynalinks plugin parses link tags as the page is constructed, so links will always be up to date. As for the unpolished part, it currently requires text to be inserted manually as so:</p>
<ol class="code">
<li><code>[link:14"]click here[/link]</code></li>
</ol>
<p>This format will always provide a current link to the page with ID 14, no matter where it&#8217;s moved to in the site.</p>
<p>The plan is to extend this with a TinyMCE button to make inserting links easier without having to look up a page ID. Possibly down the line it may include dependency tracking, so a page can&#8217;t be deleted when it&#8217;s linked to, but maybe this is a bit overkill.</p>
<h2>Update:</h2>
<p>The script&#8217;s had a bit of an update so it now works with the URL &#8216;link:[page_id]&#8216;, to fit in more with the editor and ease of use for non-techies. This also means it doesn&#8217;t need its own TinyMCE button.</p>
<p>Grab the plugin over at its <a href="http://www.orangeninja.com/projects/dynalinks/">project page</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.orangeninja.com/2007/07/04/wordpress-dynamic-links/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Gallery Development</title>
		<link>http://www.orangeninja.com/2007/06/19/gallery-development/</link>
		<comments>http://www.orangeninja.com/2007/06/19/gallery-development/#comments</comments>
		<pubDate>Tue, 19 Jun 2007 00:21:08 +0000</pubDate>
		<dc:creator>Frosty</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[Web Dev]]></category>
		<category><![CDATA[web dev]]></category>

		<guid isPermaLink="false">http://www.orangeninja.com/2007/06/19/gallery-development/</guid>
		<description><![CDATA[Being exasperated by the available offerings for photo gallery management within WordPress, I decided to do what every self respecting geek should do, and write my own from scratch. This way I can incorporate all the features I want, but at the same time keep it easy to use so it can be used by [...]]]></description>
			<content:encoded><![CDATA[<p>Being exasperated by the available offerings for photo gallery management within WordPress, I decided to do what every self respecting geek should do, and write my own from scratch. This way I can incorporate all the features I want, but at the same time keep it easy to use so it can be used by anyone.</p>
<p>I&#8217;ve spent far too long on this so far, but it&#8217;s been a learning experience, being my first delve into WordPress plugin development.<span id="more-60"></span></p>
<p>The planned feature list is: (probably a bit ambitious)</p>
<ul>
<li>Images grouped into albums</li>
<li>Automatic retrieval of EXIF information</li>
<li>Tagging and comments system separate from main WordPress data</li>
<li>View tracking</li>
<li>Bulk uploading with zip files</li>
<li>Online image editing, including rotation and cropping. Possibly other features, once I look into GD&#8217;s capabilities</li>
<li>Full integration into WordPress frontend, with template tags and content tags</li>
<li>Added buttons in TinyMCE for inserting tags</li>
<li>Optional use of mod_rewrite for tidy URLs</li>
</ul>
<p>How many of these features will make it into the v1.0 release is debatable, but I intend to get them all working over time.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.orangeninja.com/2007/06/19/gallery-development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
