<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: MVC and PHP Fusebox</title>
	<link>http://www.derekscruggs.com/mvc-and-php-fusebox.html</link>
	<description>Answering questions about entrepreneurship,  internet marketing, PHP/MySQL and doing business with China. (How's that for diversity?)</description>
	<pubDate>Tue, 06 Jan 2009 09:57:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Marcin Staniszczak</title>
		<link>http://www.derekscruggs.com/mvc-and-php-fusebox.html#comment-4829</link>
		<pubDate>Mon, 02 Jan 2006 18:21:01 +0000</pubDate>
		<guid>http://www.derekscruggs.com/mvc-and-php-fusebox.html#comment-4829</guid>
					<description>So you web.framework - new MVC framework for PHP 5. In this framework you can write Views as PHP scripts or as templates. Samo of features of this framework:
- action and action-chains
- call to another actions/action-chains from action-chain 
- pre- and post- actions with exceptions (i.e. you can exclude some actions/action-chains from pre- or post- actions)
- validators for simple check forms
- client-side validators
- AJAX
- support for DB configuration in framework configuration
- support for DB connections (PDO, ADOdb and web.db)
- support for template systems (by default drivers for web.template and Smarty)
- router – for simple support for nice URL and generate proper URL addresses
- token
- authorization frame
- DB Session’s handler
and more...

http://webframework.sourceforge.net/</description>
		<content:encoded><![CDATA[<p>So you web.framework - new MVC framework for PHP 5. In this framework you can write Views as PHP scripts or as templates. Samo of features of this framework:<br />
- action and action-chains<br />
- call to another actions/action-chains from action-chain<br />
- pre- and post- actions with exceptions (i.e. you can exclude some actions/action-chains from pre- or post- actions)<br />
- validators for simple check forms<br />
- client-side validators<br />
- AJAX<br />
- support for DB configuration in framework configuration<br />
- support for DB connections (PDO, ADOdb and web.db)<br />
- support for template systems (by default drivers for web.template and Smarty)<br />
- router – for simple support for nice URL and generate proper URL addresses<br />
- token<br />
- authorization frame<br />
- DB Session’s handler<br />
and more&#8230;</p>
<p><a href='http://webframework.sourceforge.net/' rel='nofollow'>http://webframework.sourceforge.net/</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Sparr</title>
		<link>http://www.derekscruggs.com/mvc-and-php-fusebox.html#comment-7</link>
		<pubDate>Mon, 10 Jan 2005 15:59:33 +0000</pubDate>
		<guid>http://www.derekscruggs.com/mvc-and-php-fusebox.html#comment-7</guid>
					<description>I appreciate the input.  We are considering various options for a rearchitecture of Goomzee's storefronts.  I liked smarty due to it's template and caching but like yourself, we already have custom classes and functions for display.</description>
		<content:encoded><![CDATA[<p>I appreciate the input.  We are considering various options for a rearchitecture of Goomzee&#8217;s storefronts.  I liked smarty due to it&#8217;s template and caching but like yourself, we already have custom classes and functions for display.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anonymous</title>
		<link>http://www.derekscruggs.com/mvc-and-php-fusebox.html#comment-6</link>
		<pubDate>Mon, 10 Jan 2005 15:50:41 +0000</pubDate>
		<guid>http://www.derekscruggs.com/mvc-and-php-fusebox.html#comment-6</guid>
					<description>Mike - I haven't worked much with J2EE and STRUTS, so I don't know how closely they compare. But I'm not a big fan of Smarty because it seems redundant to me. *PHP* is the templating engine. Why reinvent the wheel? You could argue that it's easier for non-PHP programmers, but IMO it's not much easier. You still have to understand if/then, loops, arrays etc.  Why not just teach them basic PHP?</description>
		<content:encoded><![CDATA[<p>Mike - I haven&#8217;t worked much with J2EE and STRUTS, so I don&#8217;t know how closely they compare. But I&#8217;m not a big fan of Smarty because it seems redundant to me. *PHP* is the templating engine. Why reinvent the wheel? You could argue that it&#8217;s easier for non-PHP programmers, but IMO it&#8217;s not much easier. You still have to understand if/then, loops, arrays etc.  Why not just teach them basic PHP?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Sparr</title>
		<link>http://www.derekscruggs.com/mvc-and-php-fusebox.html#comment-5</link>
		<pubDate>Mon, 10 Jan 2005 06:08:59 +0000</pubDate>
		<guid>http://www.derekscruggs.com/mvc-and-php-fusebox.html#comment-5</guid>
					<description>Curious on your thoughts about the Smarty library set, perhaps coupled with PEAR lib?  As a former J2EE architect, specializing in MVC and design patterns, most Java-based platforms are moving towards a STRUTS (Apache project) style architecture.  I see Smarty/Pear as perhaps the PHP equivilent but given your research am curious on your thoughts?</description>
		<content:encoded><![CDATA[<p>Curious on your thoughts about the Smarty library set, perhaps coupled with PEAR lib?  As a former J2EE architect, specializing in MVC and design patterns, most Java-based platforms are moving towards a STRUTS (Apache project) style architecture.  I see Smarty/Pear as perhaps the PHP equivilent but given your research am curious on your thoughts?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
