<?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>BoltPress &#187; phi</title>
	<atom:link href="http://blog.novalistic.com/tag/phi/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.novalistic.com</link>
	<description>Also the official blog.NOVALISTIC</description>
	<lastBuildDate>Mon, 02 Aug 2010 09:45:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>How I&#8217;m preparing for WordPress 2.7</title>
		<link>http://blog.novalistic.com/archives/2008/11/how-im-preparing-for-wordpress-2-7/</link>
		<comments>http://blog.novalistic.com/archives/2008/11/how-im-preparing-for-wordpress-2-7/#comments</comments>
		<pubDate>Fri, 14 Nov 2008 17:33:58 +0000</pubDate>
		<dc:creator>BoltClock</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog.novalistic]]></category>
		<category><![CDATA[phi]]></category>
		<category><![CDATA[potassium]]></category>
		<category><![CDATA[thistle]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://blog.dev.novalistic.com/?p=199</guid>
		<description><![CDATA[In this post I summarize the steps I'm taking in preparation for WordPress 2.7's release, in terms of my themes and plugins.]]></description>
			<content:encoded><![CDATA[<p>WordPress 2.7 is coming soon. My two blogs at WordPress.com (<a href="http://boltclock.wordpress.com">BoltClock @ WordPress.com</a> and <a href="http://ofchrist.wordpress.com">Of Christ in Me</a>) will be well taken care of, but I&#8217;m going to have to update certain other things. I&#8217;ll summarize my plans in getting my work WordPress 2.7-ready.</p>
<h3>blog.NOVALISTIC</h3>
<p>No, there will be no revamp of the current design because I simply find it too awesome to be replaced (as yet). However, to harness WordPress 2.7&#8242;s new theming features, especially threaded comments, which I myself will take a while to adjust to, I will be substantially refactoring the theme and release blog.NOVALISTIC 2.1 as soon as WordPress 2.7 RC1 is out the door.</p>
<p>I have a feeling this design will live through the launch of NOVALISTIC 4.0 &#8220;Sarathos&#8221;.</p>
<h3>dev.NOVALISTIC and Thistle</h3>
<p>Like what will become blog.NOVALISTIC 2.1, <a href="http://blog.novalistic.com/downloads/wordpress-themes/thistle">Thistle</a> 1.1 will also be worked on to welcome WordPress 2.7 and I suspect Thistle should be out at around the same time frame as when RC1 arrives. Don&#8217;t worry though: rest assured that Thistle 1.1 will remain backward compatible with WordPress &le; 2.6, and you can upgrade painlessly. Of course, dev.NOVALISTIC&#8217;s WordPress setup will be upgraded to the release candidate, and the theme will be updated.</p>
<h3>Potassium</h3>
<p><a href="http://blog.novalistic.com/downloads/wordpress-themes/sandbox-potassium">Potassium</a> will be updated, as Potassium 1.0.6, to go with <a href="http://plaintxt.org/themes/sandbox">Sandbox</a> 1.7, the version of Sandbox that should be made for WordPress 2.7.</p>
<h3>Phi</h3>
<p><a href="http://blog.novalistic.com/downloads/wordpress-plugins/phi">Phi</a> is not affected in any way by WordPress 2.7. Although that means Phi is already WordPress 2.7-ready, that doesn&#8217;t mean I&#8217;ll only support use of it on WordPress 2.7 when I release it. All versions from 2.0 onwards are supported. I believe Phi will be ready for release shortly after 2.7 rolls out.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.novalistic.com/archives/2008/11/how-im-preparing-for-wordpress-2-7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My first WordPress plugin: Phi &#966;</title>
		<link>http://blog.novalistic.com/archives/2008/09/my-first-wordpress-plugin-phi/</link>
		<comments>http://blog.novalistic.com/archives/2008/09/my-first-wordpress-plugin-phi/#comments</comments>
		<pubDate>Fri, 19 Sep 2008 17:23:33 +0000</pubDate>
		<dc:creator>BoltClock</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Web Development & Design]]></category>
		<category><![CDATA[phi]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wordpress plugin]]></category>

		<guid isPermaLink="false">http://blog.dev.novalistic.com/?p=193</guid>
		<description><![CDATA[On Thursday, I hacked together my very first WordPress plugin, called <strong>Phi</strong> (for <strong>P</strong>HP <strong>Hi</strong>ghlight). See it in action here. I plan to release its source code soon once I deem it worthy of release...]]></description>
			<content:encoded><![CDATA[<p>I spent Thursday whipping up my very first WordPress plugin (and yesterday plus today fixing its first bugs). It&#8217;s called <strong>Phi</strong> (as in the Greek letter &phi;), which stands for <strong>P</strong>HP <strong>Hi</strong>ghlight. It&#8217;s currently running in this blog, and so far it&#8217;s been working really well for me. I don&#8217;t enjoy syntax highlighting for anything but PHP, but I&#8217;m happy.</p>
<p><span id="more-193"></span></p>
<p>I tried a few plugins like <a href="http://wordpress.org/extend/plugins/wp-syntax">WP-Syntax</a> and <a href="http://wordpress.org/extend/plugins/syntaxhighlighter-plus">SyntaxHighlighter Plus</a>, however they were too complicated and feature-rich for my needs, and recent versions of WP-Syntax, which I&#8217;d been using for the past year, were beginning to mess with my styles. That annoyed me real good. Plus, GeSHi colors were getting a little boring for me.</p>
<p>There was <a href="http://wordpress.org/extend/plugins/wp-syntax-colorizer">WP-Syntax Colorizer</a>, but it didn&#8217;t quite satisfy me.</p>
<p><em>That does it</em>, I thought. So I set out to put together a simple plugin which would fulfill my needs, using PHP&#8217;s humble <code>highlight_string()</code> function (<a href="http://www.php.net/manual/en/function.highlight-string.php">PHP manual page</a>).</p>
<p>And Phi was born.</p>
<p>I might release Phi soon. I believe there are others out there who share my opinion about the bigger syntax highlighting plugins. Besides, this is my first, so for additional kicks I&#8217;d like to see what it&#8217;s like to be a proud developer of my very own WordPress plugin (heh).</p>
<p>Here&#8217;s an excerpt of Phi&#8217;s source code, highlighted using Phi itself of course:</p>
<p><small>Example 1: Phi&#8217;s source code, highlighted using Phi</small></p>
<pre class="phi php">
<span style="color: #fff"><span style="color: #138dd7">&lt;?php
&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #952d13">//&nbsp;PHP&nbsp;4&nbsp;coughs&nbsp;up&nbsp;&lt;font&gt;&nbsp;tags&nbsp;-&nbsp;clearly&nbsp;highly&nbsp;undesirable&nbsp;behavior
&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #df0">if&nbsp;(&nbsp;</span><span style="color: #138dd7">version_compare</span><span style="color: #df0">(</span><span style="color: #138dd7">phpversion</span><span style="color: #df0">(),&nbsp;</span><span style="color: #64e6a5">'5.0.0'</span><span style="color: #df0">,&nbsp;</span><span style="color: #64e6a5">'&lt;'</span><span style="color: #df0">)&nbsp;)&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #138dd7">$php&nbsp;</span><span style="color: #df0">=&nbsp;</span><span style="color: #138dd7">preg_replace</span><span style="color: #df0">(
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;array(</span><span style="color: #64e6a5">'@&lt;font&nbsp;color="(.+?)"&gt;@'</span><span style="color: #df0">,&nbsp;</span><span style="color: #64e6a5">'@&lt;/font&gt;@'</span><span style="color: #df0">),&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;array(</span><span style="color: #64e6a5">'&lt;span&nbsp;style="color:&nbsp;$1"&gt;'</span><span style="color: #df0">,&nbsp;</span><span style="color: #64e6a5">'&lt;/span&gt;'</span><span style="color: #df0">),&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #138dd7">$php
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #df0">);
&nbsp;&nbsp;&nbsp;&nbsp;}
&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style="color: #138dd7">?&gt;</span></span>
</pre>
<p>See also, at dev.NOVALISTIC, <a href="http://dev.NOVALISTIC.com/wordpress/2007/12/10/two-code-snippets">Phi in action</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.novalistic.com/archives/2008/09/my-first-wordpress-plugin-phi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
