<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for phup &#039;n stuff</title>
	<atom:link href="http://blog.kristopherwilson.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kristopherwilson.com</link>
	<description>Another Blog About Being a Developer</description>
	<lastBuildDate>Tue, 31 Aug 2010 23:02:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Droid Doesn&#8217;t? Pros and Cons of the Droid X by Kristopher</title>
		<link>http://blog.kristopherwilson.com/2010/06/23/droid-doesnt-pros-and-cons-of-the-droid-x/comment-page-1/#comment-365</link>
		<dc:creator>Kristopher</dc:creator>
		<pubDate>Tue, 31 Aug 2010 23:02:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=238#comment-365</guid>
		<description>You have your opinion; I have mine. Thanks for the articulate, run-on comment!</description>
		<content:encoded><![CDATA[<p>You have your opinion; I have mine. Thanks for the articulate, run-on comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Droid Doesn&#8217;t? Pros and Cons of the Droid X by gilbert</title>
		<link>http://blog.kristopherwilson.com/2010/06/23/droid-doesnt-pros-and-cons-of-the-droid-x/comment-page-1/#comment-274</link>
		<dc:creator>gilbert</dc:creator>
		<pubDate>Wed, 11 Aug 2010 20:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=238#comment-274</guid>
		<description>Your a complete jackass,this phone is great I love it nothing wrong with it I love te design stop writing stupid blogs like this</description>
		<content:encoded><![CDATA[<p>Your a complete jackass,this phone is great I love it nothing wrong with it I love te design stop writing stupid blogs like this</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Ditz to Track Issues by Matt Katz</title>
		<link>http://blog.kristopherwilson.com/2010/05/01/using-ditz-to-track-issues/comment-page-1/#comment-263</link>
		<dc:creator>Matt Katz</dc:creator>
		<pubDate>Wed, 11 Aug 2010 02:57:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=227#comment-263</guid>
		<description>I started using ditz when I discovered it recently. It stores all issues as a guid/hash, so there isn&#039;t much problem with how long you wait before comitting - issue collision is very unlikely. 

The main developer isn&#039;t active on the project, but their appear to be plenty of folks still interested and some are considering a fork.</description>
		<content:encoded><![CDATA[<p>I started using ditz when I discovered it recently. It stores all issues as a guid/hash, so there isn&#8217;t much problem with how long you wait before comitting &#8211; issue collision is very unlikely. </p>
<p>The main developer isn&#8217;t active on the project, but their appear to be plenty of folks still interested and some are considering a fork.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Zend Framework Sucks: One Validate Callback per Form Field by A.J. Brown</title>
		<link>http://blog.kristopherwilson.com/2010/06/10/zend-framework-sucks-one-validate-callback-per-form-field/comment-page-1/#comment-144</link>
		<dc:creator>A.J. Brown</dc:creator>
		<pubDate>Fri, 02 Jul 2010 03:28:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=234#comment-144</guid>
		<description>What complex and highly unique validations are you doing that you would not be able to re-factor into reusable Validator classes, or be done with Validator chains?

It sounds like you might be using validators in the wrong way.  Validators should be used to ensure the integrity of the input (validation), and to ensure a desired output (filtering).  Think of them as a firewall between the user and your application, with some basic rules built in.  

You business/domain logic should not reside within the form.

With that said, perhaps Zend Framework &quot;sucks&quot; because it forces design decisions onto you.  But that&#039;s a whole other conversation.  And remember, you&#039;re not forced to use Zend Form :)</description>
		<content:encoded><![CDATA[<p>What complex and highly unique validations are you doing that you would not be able to re-factor into reusable Validator classes, or be done with Validator chains?</p>
<p>It sounds like you might be using validators in the wrong way.  Validators should be used to ensure the integrity of the input (validation), and to ensure a desired output (filtering).  Think of them as a firewall between the user and your application, with some basic rules built in.  </p>
<p>You business/domain logic should not reside within the form.</p>
<p>With that said, perhaps Zend Framework &#8220;sucks&#8221; because it forces design decisions onto you.  But that&#8217;s a whole other conversation.  And remember, you&#8217;re not forced to use Zend Form <img src='http://blog.kristopherwilson.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Zend Framework Sucks: One Validate Callback per Form Field by Patrick Barroca</title>
		<link>http://blog.kristopherwilson.com/2010/06/10/zend-framework-sucks-one-validate-callback-per-form-field/comment-page-1/#comment-140</link>
		<dc:creator>Patrick Barroca</dc:creator>
		<pubDate>Wed, 30 Jun 2010 08:32:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=234#comment-140</guid>
		<description>@ Kristopher,
Now with your comment I see that you want to bring model / form and validation code closer.
This is a compromise between reusability / readability and in this balance your form&#039;s validation complexity is what matters.
I only have a dozen of specific validators which I think is still «light» but I might have to follow the same path as you in the future.</description>
		<content:encoded><![CDATA[<p>@ Kristopher,<br />
Now with your comment I see that you want to bring model / form and validation code closer.<br />
This is a compromise between reusability / readability and in this balance your form&#8217;s validation complexity is what matters.<br />
I only have a dozen of specific validators which I think is still «light» but I might have to follow the same path as you in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Zend Framework Sucks: One Validate Callback per Form Field by Lysender</title>
		<link>http://blog.kristopherwilson.com/2010/06/10/zend-framework-sucks-one-validate-callback-per-form-field/comment-page-1/#comment-124</link>
		<dc:creator>Lysender</dc:creator>
		<pubDate>Thu, 24 Jun 2010 04:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=234#comment-124</guid>
		<description>So what did you do?

I have same issue with Zend Form and the Validation system especially default validation messages are never useful.

I  stop using zend form since zf 1.7.x and now I create my own modeling system.</description>
		<content:encoded><![CDATA[<p>So what did you do?</p>
<p>I have same issue with Zend Form and the Validation system especially default validation messages are never useful.</p>
<p>I  stop using zend form since zf 1.7.x and now I create my own modeling system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MySQL and the Most Useless Feature Ever by Kristopher</title>
		<link>http://blog.kristopherwilson.com/2010/02/24/mysql-and-the-most-useless-feature-ever/comment-page-1/#comment-123</link>
		<dc:creator>Kristopher</dc:creator>
		<pubDate>Wed, 23 Jun 2010 17:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=207#comment-123</guid>
		<description>Well, hopefully Oracle will either fix it, or break it so bad that everyone stops using it.</description>
		<content:encoded><![CDATA[<p>Well, hopefully Oracle will either fix it, or break it so bad that everyone stops using it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Zend Framework Sucks: One Validate Callback per Form Field by Kristopher</title>
		<link>http://blog.kristopherwilson.com/2010/06/10/zend-framework-sucks-one-validate-callback-per-form-field/comment-page-1/#comment-122</link>
		<dc:creator>Kristopher</dc:creator>
		<pubDate>Wed, 23 Jun 2010 17:10:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=234#comment-122</guid>
		<description>Patrick, thanks for your comment. My issue is that I have a large amount of forms, with a large amount of fields, many of them requiring complex validations that don&#039;t work with the provided Validate classes. 

I could follow your method and actually create a subclass of Zend_Validate_Interface (which I do do quite frequently for reusable validations), but I would literally have dozens of these classes tucked away in some library folder, separate from both my forms and my models. And that just doesn&#039;t make sense to me. 

I&#039;d rather have this validation all on the form, rather than have to open and reference dozens of other classes when I want to see/tweak the validation for a particular form. 

But if that works for you, more power to ya.</description>
		<content:encoded><![CDATA[<p>Patrick, thanks for your comment. My issue is that I have a large amount of forms, with a large amount of fields, many of them requiring complex validations that don&#8217;t work with the provided Validate classes. </p>
<p>I could follow your method and actually create a subclass of Zend_Validate_Interface (which I do do quite frequently for reusable validations), but I would literally have dozens of these classes tucked away in some library folder, separate from both my forms and my models. And that just doesn&#8217;t make sense to me. </p>
<p>I&#8217;d rather have this validation all on the form, rather than have to open and reference dozens of other classes when I want to see/tweak the validation for a particular form. </p>
<p>But if that works for you, more power to ya.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostgreSQL arrays and PHP&#8217;s str_getcsv() by Kristopher</title>
		<link>http://blog.kristopherwilson.com/2010/03/05/postgresql-arrays-and-phps-str_getcsv/comment-page-1/#comment-121</link>
		<dc:creator>Kristopher</dc:creator>
		<pubDate>Wed, 23 Jun 2010 16:44:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=213#comment-121</guid>
		<description>Gregory, great points. And yeah, if you know your data doesn&#039;t have commas in it, then it&#039;s a no brainer. I don&#039;t remember my specific use case for this anymore (it was a crazy database schema someone else setup), but it definitely involved commas.</description>
		<content:encoded><![CDATA[<p>Gregory, great points. And yeah, if you know your data doesn&#8217;t have commas in it, then it&#8217;s a no brainer. I don&#8217;t remember my specific use case for this anymore (it was a crazy database schema someone else setup), but it definitely involved commas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Zend Framework Sucks: One Validate Callback per Form Field by Patrick Barroca</title>
		<link>http://blog.kristopherwilson.com/2010/06/10/zend-framework-sucks-one-validate-callback-per-form-field/comment-page-1/#comment-120</link>
		<dc:creator>Patrick Barroca</dc:creator>
		<pubDate>Tue, 22 Jun 2010 09:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=234#comment-120</guid>
		<description>Hello,

I don&#039;t get your point.
I see validating via a callback as a gateway to objects / functions not following Zend_Validate_Interface.

Why don&#039;t you create your validators following this interface if you want the validation/messages mechanics ?

Then you could add them as any other validators.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I don&#8217;t get your point.<br />
I see validating via a callback as a gateway to objects / functions not following Zend_Validate_Interface.</p>
<p>Why don&#8217;t you create your validators following this interface if you want the validation/messages mechanics ?</p>
<p>Then you could add them as any other validators.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
