<?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>Jeff Linse &#187; PHP</title>
	<atom:link href="http://jefflinse.com/tag/php/feed/" rel="self" type="application/rss+xml" />
	<link>http://jefflinse.com</link>
	<description></description>
	<lastBuildDate>Thu, 17 Jun 2010 00:43:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to Maintain Simple, Static Pages in CakePHP</title>
		<link>http://jefflinse.com/2009/how-to-maintain-simple-static-pages-in-a-cakephp-application/</link>
		<comments>http://jefflinse.com/2009/how-to-maintain-simple-static-pages-in-a-cakephp-application/#comments</comments>
		<pubDate>Sat, 09 May 2009 18:30:17 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[cake]]></category>
		<category><![CDATA[cakephp]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[routing]]></category>
		<category><![CDATA[static pages]]></category>

		<guid isPermaLink="false">http://jefflinse.com/?p=60</guid>
		<description><![CDATA[Cake&#8217;s default way of handling simple static content is to use the built-in PagesController to serve up .tpl files from /app/views/pages. This is a simple and straightforward approach and works for very small websites, but comes with some obvious drawbacks:

Making changes to the content of the pages requires editing template files;
There&#8217;s no easy way (generally) ]]></description>
		<wfw:commentRss>http://jefflinse.com/2009/how-to-maintain-simple-static-pages-in-a-cakephp-application/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Passing A Variable Number of Arguments to a Function at Run-time</title>
		<link>http://jefflinse.com/2009/passing-variable-number-arguments-function-runtime/</link>
		<comments>http://jefflinse.com/2009/passing-variable-number-arguments-function-runtime/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 02:49:07 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[C/C++]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[arguments]]></category>
		<category><![CDATA[c]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://jefflinse.com/?p=39</guid>
		<description><![CDATA[At the request of an Ozzu member last night, I wrote up two new quick tutorials outlining how to write functions that can accept a variable-length argument list at run-time.  I wrote the original tutorial for C programmers and later adapted it for PHP.  I&#8217;ll likely adapt it for a few other languages in the ]]></description>
		<wfw:commentRss>http://jefflinse.com/2009/passing-variable-number-arguments-function-runtime/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Calendar Element for CakePHP</title>
		<link>http://jefflinse.com/2009/a-calendar-element-for-cakephp/</link>
		<comments>http://jefflinse.com/2009/a-calendar-element-for-cakephp/#comments</comments>
		<pubDate>Wed, 28 Jan 2009 00:43:27 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[cake]]></category>
		<category><![CDATA[cakephp]]></category>
		<category><![CDATA[calendar]]></category>
		<category><![CDATA[element]]></category>

		<guid isPermaLink="false">http://jefflinse.com/?p=26</guid>
		<description><![CDATA[Here&#8217;s a quick calendar element I whipped up for a CakePHP application I&#8217;m writing.  I needed to use the calendar in a number of different places, so creating a view element for it in Cake made the most sense.

&#60;&#60;&#60; March 2009 &#62;&#62;&#62;



Su
Mo
Tu
We
Th
Fr
Sa


1
2
3
4
5
6
7


8
9
10
11
12
13
14


15
16
17
18
19
20
21


22
23
24
25
26
27
28


29
30
31








Download the source (zipped .ctp file) here: 
The code is pretty simple.  Pass the ]]></description>
		<wfw:commentRss>http://jefflinse.com/2009/a-calendar-element-for-cakephp/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Creating a Tree Structure within a CakePHP Model</title>
		<link>http://jefflinse.com/2008/creating-a-tree-structure-within-a-cakephp-model/</link>
		<comments>http://jefflinse.com/2008/creating-a-tree-structure-within-a-cakephp-model/#comments</comments>
		<pubDate>Mon, 06 Oct 2008 02:50:45 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[association]]></category>
		<category><![CDATA[cake]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[tree]]></category>

		<guid isPermaLink="false">http://jefflinse.com/?p=24</guid>
		<description><![CDATA[My assumption going into this was that creating a tree-like relationship within one of my models would be fairly straightforward with Cake&#8217;s model relationships.  As it turns out, I was absolutely correct.
Let&#8217;s say we want to create a model called &#8220;Category&#8221;, and each category can belong to a parent category.  In other words, we want ]]></description>
		<wfw:commentRss>http://jefflinse.com/2008/creating-a-tree-structure-within-a-cakephp-model/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>10 Useful PHP Functions You May Not Have Known About</title>
		<link>http://jefflinse.com/2008/10-useful-php-functions-you-may-not-have-known-about/</link>
		<comments>http://jefflinse.com/2008/10-useful-php-functions-you-may-not-have-known-about/#comments</comments>
		<pubDate>Mon, 15 Sep 2008 05:23:13 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[functions]]></category>

		<guid isPermaLink="false">http://jefflinse.com/?p=22</guid>
		<description><![CDATA[10. get_browser()
This function comes in handy when collecting information about a user&#8217;s browser to determine the content capabilities for that user.  It returns an associative array containing information such as the browser type, version, whether or not it is capable of handling frames, cookies, and javascript, and the platform on which the browser is running.
This ]]></description>
		<wfw:commentRss>http://jefflinse.com/2008/10-useful-php-functions-you-may-not-have-known-about/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Creating Custom printf() Wrappers</title>
		<link>http://jefflinse.com/2008/creating-custom-printf-wrappers/</link>
		<comments>http://jefflinse.com/2008/creating-custom-printf-wrappers/#comments</comments>
		<pubDate>Tue, 24 Jun 2008 14:40:27 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[C/C++]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[c]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[printf]]></category>
		<category><![CDATA[wrapper]]></category>

		<guid isPermaLink="false">http://jefflinse.com/?p=15</guid>
		<description><![CDATA[After some brief searching, I found a way to create my own custom printf() wrapper functions.

The technique is rather simple.  Declare a function that accepts a format string and a varying number of further arguments.  Pass said string and arguments to fprintf.  Do anything else desired before and after]]></description>
		<wfw:commentRss>http://jefflinse.com/2008/creating-custom-printf-wrappers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
