<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atomfull.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://purl.org/atom/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" version="0.3" xml:lang="en">
	<title>Punctilious</title>
	<link rel="alternate" type="text/html" href="http://pun.ctilio.us" />
	<tagline>Articles and ramblings (and maybe some podcasts) on PHP, MySQL, and life developing websites.</tagline>
	<modified>2008-03-08T03:42:38Z</modified>
	<copyright>Copyright 2007</copyright>
	<generator url="http://wordpress.org/" version="2.0.7">WordPress</generator>
		<!-- podcast_generator="podPress/8.2" -->
	<icon>http://pun.ctilio.us/wp-content/plugins/podpress/images/powered_by_podpress.jpg</icon>
		<link rel="start" href="http://feeds.feedburner.com/punctilious" type="application/atom+xml" /><entry>
	  	<author>
			<name>mike</name>
		</author>
		<title type="text/html" mode="escaped"><![CDATA[Using PHP For Modular Design - Introduction]]></title>
		<link rel="alternate" type="text/html" href="http://pun.ctilio.us/2007/10/07/using-php-for-modular-design-introduction/" />
		<id>http://pun.ctilio.us/2008/03/07/using-php-for-modular-design-introduction/</id>
		<modified>2007-10-07T14:23:44Z</modified>
		<issued>2007-10-07T14:23:44Z</issued>
		
		<dc:subject>Web Development</dc:subject>
 
		<summary type="text/plain" mode="escaped"><![CDATA[This may be old news, but Dreamweaver&#8217;s templating system has some serious drawbacks. To begin with, even if you&#8217;ve gone through a great deal of trouble to nest templates, you have to be very confident that the pages you intend to change are still in fact associated with the template. What if you move between [...]]]></summary>
		<content type="text/html" mode="escaped" xml:base="http://pun.ctilio.us/2007/10/07/using-php-for-modular-design-introduction/"><![CDATA[<p>This may be old news, but Dreamweaver&#8217;s templating system has some serious drawbacks. To begin with, even if you&#8217;ve gone through a great deal of trouble to nest templates, you have to be very confident that the pages you intend to change are still in fact associated with the template. What if you move between your laptop and your desktop system pretty regularly? What if you have several dozen (or hundreds of) pages that will all be affected by a template change? That&#8217;s right, you&#8217;ll be re-uploading all those pages.</p>
<p>I propose that you work smart, not hard, next time you set up a site. If you get used to a system like I&#8217;m proposing, you&#8217;ll get to reuse code over and over again, making your future worktime more efficient, and thereby driving more profits your way. I&#8217;m sure many designers out there are doing this already, but this series of articles is intended to help those designers out there who are struggling with the learning curve. I hope this helps a little.</p>
<p>In a nutshell: We&#8217;ll be using PHP to perform server-side includes for the header, navigation, and footer of all pages on the site. We&#8217;ll set up some associative arrays for the header information, and if you choose to use a database, I&#8217;ll throw in some tips for that method as well. The beauty of this system is that when you need to update the an individual piece of your site, all you&#8217;ll need to do is update one PHP script and upload it.
</p>
]]></content>
	</entry>
		<entry>
	  	<author>
			<name>mike</name>
		</author>
		<title type="text/html" mode="escaped"><![CDATA[Turing Tests And Sacrificing Accessibility]]></title>
		<link rel="alternate" type="text/html" href="http://pun.ctilio.us/2007/09/11/turing-tests-and-sacrificing-accessibility/" />
		<id>http://pun.ctilio.us/2007/09/11/turing-tests-and-sacrificing-accessibility/</id>
		<modified>2007-09-12T03:08:17Z</modified>
		<issued>2007-09-12T03:08:17Z</issued>
		
		<dc:subject>Web Design</dc:subject>
 
		<summary type="text/plain" mode="escaped"><![CDATA[I&#8217;ve been using Turing tests (CAPTCHA images) for quite a while now, but a huge drawback is that making a CAPTCHA image more accessible also compromises its inherent security.  None of us like spam, but I&#8217;m sure we also don&#8217;t like the idea of refusing to accept forms from (even a small percentage) of [...]]]></summary>
		<content type="text/html" mode="escaped" xml:base="http://pun.ctilio.us/2007/09/11/turing-tests-and-sacrificing-accessibility/"><![CDATA[<p>I&#8217;ve been using <a href="http://en.wikipedia.org/wiki/Turing_test">Turing tests</a> (<acronym title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHA</acronym> images) for quite a while now, but a huge drawback is that making a <acronym title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHA</acronym> image more accessible also compromises its inherent security.  None of us like spam, but I&#8217;m sure we also don&#8217;t like the idea of refusing to accept forms from (even a small percentage) of our users.</p>
<p>So with that, I&#8217;ve recently turned away from <acronym title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHA</acronym> images and started using a simple math problem.  It&#8217;s no big deal to create a random one-digit addition problem and ask the user to solve it, and if you incorporate server-side and client-side validation, you&#8217;ll have a very user-friendly and accessible form on your site.</p>
<p>Can a script figure out the math problem?  Sure.  But so far I&#8217;ve been using my script on every site I&#8217;ve developed, and I haven&#8217;t had one report of spam through an online form.  Is it perfect?  No, far from it.  But it seems to work well for now, and it&#8217;s very simple to implement.</p>
<p>Want to see an example?  Check out my firm&#8217;s <a href="http://www.107designs.com/contact.php">contact form at 107 Designs</a>.
</p>
]]></content>
	</entry>
		<entry>
	  	<author>
			<name>mike</name>
		</author>
		<title type="text/html" mode="escaped"><![CDATA[Hello World!]]></title>
		<link rel="alternate" type="text/html" href="http://pun.ctilio.us/2007/08/03/hello-world/" />
		<id>http://pun.ctilio.us/2007/08/03/hello-world/</id>
		<modified>2007-08-03T20:59:22Z</modified>
		<issued>2007-08-03T20:59:22Z</issued>
		
		<dc:subject>Ramblings</dc:subject>
 
		<summary type="text/plain" mode="escaped"><![CDATA[Well, after spending years on the sidelines of the weblog playing field, I&#8217;ve decided to launch Punctilious.  Although there are a lot of great  PHP/MySQL developers out there on the Interweb, I feel that loads of the tutorials, scripts, and how-tos are sorely out-of-date.  Specifically, I&#8217;d like to address development and design [...]]]></summary>
		<content type="text/html" mode="escaped" xml:base="http://pun.ctilio.us/2007/08/03/hello-world/"><![CDATA[<p>Well, after spending years on the sidelines of the weblog playing field, I&#8217;ve decided to launch Punctilious.  Although there are a lot of great  PHP/MySQL developers out there on the Interweb, I feel that loads of the tutorials, scripts, and how-tos are sorely out-of-date.  Specifically, I&#8217;d like to address development and design in one blog, focusing on web standards, usability, accessibility, and modular code.  Since I do it all, I feel like I&#8217;m in an interesting position to write about it.<br />
So with that, I begin my journey into the great blogosphere, boldly going where <strike>no man has</strike> many men have gone before.
</p>
]]></content>
	</entry>
	</feed>
