<?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>EyeStorm Blog</title>
	<atom:link href="http://www.eyestormstudio.com/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.eyestormstudio.com/blog</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 30 Oct 2009 22:54:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>ForumMonkeys looking for phpBB3 developers</title>
		<link>http://www.eyestormstudio.com/blog/?p=16</link>
		<comments>http://www.eyestormstudio.com/blog/?p=16#comments</comments>
		<pubDate>Thu, 05 Feb 2009 00:24:27 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.eyestormstudio.com/blog/?p=16</guid>
		<description><![CDATA[Our sister site, ForumMonkeys, is now looking for able bodied men or women with extensive familiarity with phpBB. For more information check out the Help Wanted page.
]]></description>
			<content:encoded><![CDATA[<p>Our sister site, ForumMonkeys, is now looking for able bodied men or women with extensive familiarity with phpBB. For more information check out the <a href="http://www.forummonkeys.com/nowhiring.html" target="_blank">Help Wanted page</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eyestormstudio.com/blog/?feed=rss2&amp;p=16</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wordpress Loop on Non-Wordpress Pages</title>
		<link>http://www.eyestormstudio.com/blog/?p=11</link>
		<comments>http://www.eyestormstudio.com/blog/?p=11#comments</comments>
		<pubDate>Sat, 20 Oct 2007 01:22:40 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Articles]]></category>

		<guid isPermaLink="false">http://www.eyestormstudio.com/blog/?p=11</guid>
		<description><![CDATA[I was looking for an easy code snippet to put the latest blog posts on the EyeStorm index page using the Wordpress loop. I remember it took me quite a bit of searching, that I had to keep trying different keyword combinations until I finally found something to help me. Today, I wanted to change [...]]]></description>
			<content:encoded><![CDATA[<p>I was looking for an easy code snippet to put the latest blog posts on the EyeStorm index page using the Wordpress loop. I remember it took me quite a bit of searching, that I had to keep trying different keyword combinations until I finally found something to help me. Today, I wanted to change the sort order of the posts and no matter if I changed it from ASC to DESC, nothing happened. I realized the code I had pilfered had some syntax errors. Having some PHP/MySQL knowledge, I fixed them and spent another ten minutes looking for that post again so I could add a comment with the syntax fix to no avail. So, I decided I would post this in case other people are looking for the same thing and having problems finding it.</p>
<p>Now that I&#8217;ve bored you with the short story, here&#8217;s the code.</p>
<p><span id="more-11"></span></p>
<pre style="width:400px;">&lt;?php
        $how_many=3; //How many posts do you want to show
        require_once(&quot;blog/wp-config.php&quot;); // Change this for your path to wp-config.php file ?&gt;

        &lt;ol id=&quot;whats-new&quot;&gt;
        &lt;?php
        // if post state is published and the post type is a post (and not a page), display it. You can remove the  AND 'post_type' = \&quot;post\&quot;  line to grab both posts and pages. Sort ASC or DESC (Descending).
        $news=$wpdb-&gt;get_results(&quot;SELECT `ID`,`post_title` FROM $wpdb-&gt;posts
        WHERE `post_status`= \&quot;publish\&quot; AND `post_type` = \&quot;post\&quot; ORDER BY POST_DATE DESC LIMIT &quot;.$how_many);
        foreach($news as $np){
        printf (&quot;&lt;li style='padding-bottom:7px;'&gt;&lt;a href=\&quot;blog/index.php?p=%s\&quot;&gt;%s&lt;/a&gt;&lt;/li&gt;&quot;, $np-&gt;ID,$np-&gt;post_title);
        }?&gt;
        &lt;/ol&gt;</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.eyestormstudio.com/blog/?feed=rss2&amp;p=11</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>How To: Animated Favicon</title>
		<link>http://www.eyestormstudio.com/blog/?p=8</link>
		<comments>http://www.eyestormstudio.com/blog/?p=8#comments</comments>
		<pubDate>Fri, 06 Jul 2007 02:50:50 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Articles]]></category>

		<guid isPermaLink="false">http://www.eyestormstudio.com/blog/?p=8</guid>
		<description><![CDATA[Firefox allows webmasters to use animated favicons and it is likely more browsers will eventually follow suit. While Internet Explorer does not support animated icons in any way, there is an easy way to code things so that you can display an animated favicon in supported browsers and a standard icon for all others.

Normally, one [...]]]></description>
			<content:encoded><![CDATA[<p>Firefox allows webmasters to use animated favicons and it is likely more browsers will eventually follow suit. While Internet Explorer does not support animated icons in any way, there is an easy way to code things so that you can display an animated favicon in supported browsers and a standard icon for all others.</p>
<p><span id="more-8"></span></p>
<p>Normally, one could just plop the favicon.ico image in a website&#8217;s root directory and it would show up without even the need to add a link to it. To get both icons showing in all browsers, we&#8217;ll need to add not just the link to the normal favicon, but also to the animated one.</p>
<p>Create your animated icon 16 pixels high and wide. I recommend calling it favicon.gif and uploading it to your website&#8217;s root directory, which should be where your regular favicon.ico file is. Put the code beneath this paragraph anywhere between the &lt;head&gt; tags of your website, making sure the paths are accurate, and you&#8217;re good to go. Firefox will show the animated .gif as the favicon, even when the user bookmarks the page, and Internet Explorer and other browsers that do not support it will continue to use the boring non-animated version. <em>Note, if you have a cached bookmark image, it will show it until you clear your cache.</em></p>
<pre>
&lt;link rel="shortcut icon" href="favicon.ico"&gt;
&lt;link rel="shortcut icon" href="favico.gif"&gt;</pre>
<p>As you can see, the first link is the regular favicon and the second is the animated version. If you want to see for yourself, I recently added an animated favicon to <a href="http://www.forummonkeys.com" title="vBulletin, phpBB, Invision skins and styles">ForumMonkeys</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eyestormstudio.com/blog/?feed=rss2&amp;p=8</wfw:commentRss>
		<slash:comments>23</slash:comments>
		</item>
		<item>
		<title>The Anatomy of the vBulletin Animal</title>
		<link>http://www.eyestormstudio.com/blog/?p=6</link>
		<comments>http://www.eyestormstudio.com/blog/?p=6#comments</comments>
		<pubDate>Fri, 15 Jun 2007 03:45:23 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Articles]]></category>

		<guid isPermaLink="false">http://www.eyestormstudio.com/blog/?p=6</guid>
		<description><![CDATA[Part One
The Forumhome (a.k.a homepage, a.k.a index page)
Even despite years of study in its natural habitat, even though we have picked apart its scat and know what it eats (mysql queries), the vBulletin Animal  nevertheless easily irritates newcomers with its ponderous template hierarchy. Over the next few weeks, I am going to try and [...]]]></description>
			<content:encoded><![CDATA[<h3>Part One</h3>
<p><em>The Forumhome (a.k.a homepage, a.k.a index page)</em></p>
<p>Even despite years of study in its natural habitat, even though we have picked apart its scat and know what it eats (mysql queries), the vBulletin Animal  nevertheless easily irritates newcomers with its ponderous template hierarchy. Over the next few weeks, I am going to try and manifest what I have learned after years of taming and grooming, and do it in color, so we all can at least get a fundamental understanding of  vBulletin modification.<span id="more-6"></span></p>
<p style="margin-right: 15px; width: 300px; height: 400px; float: left"><img src="http://www.eyestormstudio.com/materials/forumhome.gif" alt="The Forumhome" /></p>
<p><em>Here, you see a snapshot of the internals of the index page, commonly referred to in the vBulletin skinning circles as the forumhome.</em></p>
<p>So, looking at the <strong>forumhome</strong> template, we see that at the top it calls the <strong>header</strong> and <strong>navbar</strong>, and below it, the <strong>footer</strong>. The out-of-the-box vBulletin style begins the first element, the column headings (i.e. forum, last post, posts, threads) in the <strong>forumhome</strong> template; most skinners will tuck this code into the <strong>level1_nopost</strong> in a way that makes every forum begin with the category instead, followed by these column headings.  Then, all that&#8217;s really left of the major organs is the <strong>level2_post</strong> which is where all the actual forum data can be found.</p>
<p>I often get questions about sidebars, those left or right hand columns you often see on forums where users plug random stuff (usually advertising) and how to get them to show up on just the index page, or to change them so they show up on every page. If you are coding a new skin or need to change the visibility of an existing column, the three choices of location, in order of popularity, are the <strong>forumhome</strong>, the <strong>header</strong>, and the <strong>navbar</strong>.  Putting the code for your column in the <strong>forumhome</strong> template guarantees it will only be seen on the index page. You obviously, in every case, need to make sure that you planned the placement of your code correctly, so that when the user navigates to the actual post, and the column disappears, you didn&#8217;t leave an unterminated DIV or TD tag (thereby probably messing up the entire forum on every page <em>but</em> the index page).</p>
<p>If you want the column to appear on every page within your forum, the best way to implement this modification is to put it in the <strong>header</strong> template. The <strong>navbar</strong> template is another place you could put it, but there are a few pages that do not call the <strong>navbar</strong> and thus will not plug in the column, like the redirects, the error pages, and a few others. I often recommend using the <strong>navbar</strong> template for situations such as when you are running a CMS/Portal like VbAdvanced, which uses its own columns &#8211; that way you can turn the <strong>navbar</strong> off in the CMS/Portal, and not have to worry about juggling your own column around; you can keep the easy default three column layout of the CMS/Portal software and still have your custom column show up on the forum index and below. Another reason to use the <strong>navbar</strong> for your column is that it parses the statistics and other variables normally found under the What&#8217;s Going On table; the <strong>header</strong> does not.</p>
<h3>Part Two</h3>
<p><em>The Forumdisplay</em></p>
<p>The <strong>forumdisplay</strong> has two major functions. The first is apparent when you click on a category link or if you click on a forum link that has subforums attached to it. Clicking on the category link, for example, will show all the forums attached to the category (controlled by <strong>forumhome_level1_post</strong>), any subforums (controlled by <strong>forumhome_level2_post</strong>), and, if there are any threads, will also display the <strong>threadbit</strong>.<!--more--></p>
<p style="margin-left: 15px; width: 300px; height: 400px; float: right"><img src="http://www.eyestormstudio.com/materials/forumdisplay.gif" alt="vBulletin forumdisplay" /></p>
<p>The more obvious function is just to display the <strong>threadbit</strong>, the actual threads people have posted. While all the controls and buttons are in the parent container and main template, the <strong>forumdisplay</strong>, if you are looking to maybe change the thread status icon background, change the order of the alt1 and alt2 classes in the thread rows, and so on, the <strong>threadbit</strong> is the place to go.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eyestormstudio.com/blog/?feed=rss2&amp;p=6</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EyeStorm Blog Online</title>
		<link>http://www.eyestormstudio.com/blog/?p=5</link>
		<comments>http://www.eyestormstudio.com/blog/?p=5#comments</comments>
		<pubDate>Tue, 05 Jun 2007 23:28:07 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Internal News]]></category>

		<guid isPermaLink="false">http://www.eyestormstudio.com/blog/?p=5</guid>
		<description><![CDATA[EyeStorm was running on Joomla, a decent Content Management System, but after a while it just seemed constrictive and, well, overkill. Besides some light blogging, the vast majority of our content is static and easily updated and a CMS was just too much bloat.
To that end, the static content has been separated from the blog. [...]]]></description>
			<content:encoded><![CDATA[<p>EyeStorm was running on Joomla, a decent Content Management System, but after a while it just seemed constrictive and, well, overkill. Besides some light blogging, the vast majority of our content is static and easily updated and a CMS was just too much bloat.</p>
<p>To that end, the static content has been separated from the blog. Although there&#8217;s some code cleanup and some aesthetics to put down later, everything is presentable enough now to open the doors to the public. We hope to be showcasing content in the near future that is appealing to not just our clients or prospective clients, but the web savvy as well.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eyestormstudio.com/blog/?feed=rss2&amp;p=5</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
