<?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 on: Another thing I hate about Web application frameworks</title>
	<atom:link href="http://www.snell-pym.org.uk/archives/2007/06/17/another-thing-i-hate-about-web-application-frameworks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.snell-pym.org.uk/archives/2007/06/17/another-thing-i-hate-about-web-application-frameworks/</link>
	<description>Sarah and Alaric Snell-Pym living in interesting times</description>
	<pubDate>Thu, 09 Feb 2012 03:57:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: werutzb</title>
		<link>http://www.snell-pym.org.uk/archives/2007/06/17/another-thing-i-hate-about-web-application-frameworks/comment-page-1/#comment-80408</link>
		<dc:creator>werutzb</dc:creator>
		<pubDate>Wed, 08 Oct 2008 01:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.snell-pym.org.uk/archives/2007/06/17/another-thing-i-hate-about-web-application-frameworks/#comment-80408</guid>
		<description>&lt;p&gt;Hi!&lt;/p&gt;

&lt;p&gt;I want to improve my SQL knowledge.
 I red so many SQL books and would like to
read more about SQL for my occupation as mysql database manager.&lt;/p&gt;

&lt;p&gt;What would you recommend?&lt;/p&gt;

&lt;p&gt;Thanks,
Werutz&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi!</p>

<p>I want to improve my SQL knowledge.
 I red so many SQL books and would like to
read more about SQL for my occupation as mysql database manager.</p>

<p>What would you recommend?</p>

<p>Thanks,
Werutz</p>]]></content:encoded>
	</item>
	<item>
		<title>By: alaric</title>
		<link>http://www.snell-pym.org.uk/archives/2007/06/17/another-thing-i-hate-about-web-application-frameworks/comment-page-1/#comment-44198</link>
		<dc:creator>alaric</dc:creator>
		<pubDate>Sun, 17 Jun 2007 22:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.snell-pym.org.uk/archives/2007/06/17/another-thing-i-hate-about-web-application-frameworks/#comment-44198</guid>
		<description>&lt;p&gt;Yeah, but look at what I was doing in the post - it's not much fun
ripping out an existing part of the .rhtml, and the associated
controller logic, and making it into a reusable component. Under
Swing, it would be.&lt;/p&gt;

&lt;p&gt;What I'm really moaning about is that existing WAFs are very much
oriented towards producing pages; under Swing (or, indeed, many other
such toolkits) you'd be hard pressed &lt;em&gt;not&lt;/em&gt; to do things in a
component-like way.&lt;/p&gt;

&lt;p&gt;I want to make it so easy to throw together your own components that
it's the logical thing to do. The system shouldn't provide
controllers and views; just views that can use components, and an
easy to use framework for creating components, so the natural way of
making a special form page is to throw together a component for it,
which is then instantly malleable and reusable. Or, at least, that turning a page (or part thereof) into a component is just a matter of extracing the desired bit of template, shoving it into a 'compound component definition' file along with a bit of metadata, and then referring to it by name wherever required.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Yeah, but look at what I was doing in the post - it's not much fun
ripping out an existing part of the .rhtml, and the associated
controller logic, and making it into a reusable component. Under
Swing, it would be.</p>

<p>What I'm really moaning about is that existing WAFs are very much
oriented towards producing pages; under Swing (or, indeed, many other
such toolkits) you'd be hard pressed <em>not</em> to do things in a
component-like way.</p>

<p>I want to make it so easy to throw together your own components that
it's the logical thing to do. The system shouldn't provide
controllers and views; just views that can use components, and an
easy to use framework for creating components, so the natural way of
making a special form page is to throw together a component for it,
which is then instantly malleable and reusable. Or, at least, that turning a page (or part thereof) into a component is just a matter of extracing the desired bit of template, shoving it into a 'compound component definition' file along with a bit of metadata, and then referring to it by name wherever required.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.snell-pym.org.uk/archives/2007/06/17/another-thing-i-hate-about-web-application-frameworks/comment-page-1/#comment-44048</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sun, 17 Jun 2007 07:25:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.snell-pym.org.uk/archives/2007/06/17/another-thing-i-hate-about-web-application-frameworks/#comment-44048</guid>
		<description>&lt;p&gt;Rails, which I believe you're using, has a couple of ways of supporting this. The first is 'components', which are a bit heavyweight and you're not encouraged to use them.&lt;/p&gt;

&lt;p&gt;The second is partials, little bits of templates you can include in more than one view in more than one controller.&lt;/p&gt;

&lt;p&gt;With the partials route, there's no explicit support for the business logic, but an acceptable pattern is to put the logic in ApplicationController (in a separate file of course), in a Module you include or a separate class you instantiate and use. All depending on the visibility you need of the other parts of the framework.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Rails, which I believe you're using, has a couple of ways of supporting this. The first is 'components', which are a bit heavyweight and you're not encouraged to use them.</p>

<p>The second is partials, little bits of templates you can include in more than one view in more than one controller.</p>

<p>With the partials route, there's no explicit support for the business logic, but an acceptable pattern is to put the logic in ApplicationController (in a separate file of course), in a Module you include or a separate class you instantiate and use. All depending on the visibility you need of the other parts of the framework.</p>]]></content:encoded>
	</item>
</channel>
</rss>

