<?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"
	>
<channel>
	<title>Comments on: CoughPHP 1.3.5 Released</title>
	<atom:link href="http://coughphp.com/blog/2008/12/19/coughphp-135-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://coughphp.com/blog/2008/12/19/coughphp-135-released/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Fri, 18 May 2012 19:11:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Anthony Bush</title>
		<link>http://coughphp.com/blog/2008/12/19/coughphp-135-released/#comment-61</link>
		<dc:creator>Anthony Bush</dc:creator>
		<pubDate>Fri, 30 Jan 2009 01:12:38 +0000</pubDate>
		<guid isPermaLink="false">http://coughphp.com/blog/?p=25#comment-61</guid>
		<description>Careful in your comparison of CoughPHP, an ORM, to a full framework.  pk-framework would be better compared to LightVC (no models), or LightVC+CoughPHP (with models).

Some things to note, however, are:

- LightVC and CoughPHP follow best practices, use OOP, are PHP5 strict compatible, notice free, etc.  pk-framework has some work to do in this regard.

- CoughPHP provides the ability to insert an extension class to the two core classes, CoughObject and CoughCollection, providing more customization opportunities than a plugin system.

- The current state of pk-framework's trunk does not even work.

- pk-framework has already strayed from the objective of being a lightweight framework.  There is a lot of fluff, e.g. the assumptions about the data model, the PHP4 compatibility, etc.  It may be time to re-evaluate the objectives.</description>
		<content:encoded><![CDATA[<p>Careful in your comparison of CoughPHP, an ORM, to a full framework.  pk-framework would be better compared to LightVC (no models), or LightVC+CoughPHP (with models).</p>
<p>Some things to note, however, are:</p>
<p>- LightVC and CoughPHP follow best practices, use OOP, are PHP5 strict compatible, notice free, etc.  pk-framework has some work to do in this regard.</p>
<p>- CoughPHP provides the ability to insert an extension class to the two core classes, CoughObject and CoughCollection, providing more customization opportunities than a plugin system.</p>
<p>- The current state of pk-framework&#8217;s trunk does not even work.</p>
<p>- pk-framework has already strayed from the objective of being a lightweight framework.  There is a lot of fluff, e.g. the assumptions about the data model, the PHP4 compatibility, etc.  It may be time to re-evaluate the objectives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: norman784</title>
		<link>http://coughphp.com/blog/2008/12/19/coughphp-135-released/#comment-60</link>
		<dc:creator>norman784</dc:creator>
		<pubDate>Thu, 29 Jan 2009 17:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://coughphp.com/blog/?p=25#comment-60</guid>
		<description>It's very cool the idea of a ligthweight framework, I'm working on my own lightweight framework (http://code.google.com/p/pk-framework) and I have 2 objetives:

- Build a lightweight framework with the most common features for small projects
- Easy to learn and fast to deploy a webproject

I think you need to put more code in your files so you can have less files. Write a plugin system to personalize some of the features of your framework, so the end user developer that use this will no need to modifi your framework.</description>
		<content:encoded><![CDATA[<p>It&#8217;s very cool the idea of a ligthweight framework, I&#8217;m working on my own lightweight framework (http://code.google.com/p/pk-framework) and I have 2 objetives:</p>
<p>- Build a lightweight framework with the most common features for small projects<br />
- Easy to learn and fast to deploy a webproject</p>
<p>I think you need to put more code in your files so you can have less files. Write a plugin system to personalize some of the features of your framework, so the end user developer that use this will no need to modifi your framework.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

