<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: UIEtips: Components Versus Patterns</title>
	<atom:link href="http://www.uie.com/brainsparks/2009/01/09/uietips-components-vs-patterns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2009/01/09/uietips-components-vs-patterns/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 20 Mar 2010 06:08:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Brockington</title>
		<link>http://www.uie.com/brainsparks/2009/01/09/uietips-components-vs-patterns/comment-page-1/#comment-145189</link>
		<dc:creator>Mike Brockington</dc:creator>
		<pubDate>Mon, 12 Jan 2009 11:48:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=776#comment-145189</guid>
		<description>I suspect that part of the problem here is the over-simplification of the terminology. Again and again we see a single (pre-existing) word being over-loaded with a new meaning in a specific context. 
So: &quot;Design Patterns&quot; is normally referred to as just &quot;Patterns&quot;  and similarly with &quot;Components&quot;. The latter is especially bad, as it has meaning in every industry - the web site in question may well be for the manufacturer of components for some industry, for which each product may itself have numerous components. To a software developer, a component is a very specific amount of code, and very different from a page component (visual block), which may be built from beans, procedures, DLL&#039;s etc.

If the headline had been: should I build a &quot;Design Pattern Library&quot; or a &quot;Page Component Library&quot; the conversation would surely have been much shorter.</description>
		<content:encoded><![CDATA[<p>I suspect that part of the problem here is the over-simplification of the terminology. Again and again we see a single (pre-existing) word being over-loaded with a new meaning in a specific context.<br />
So: &#8220;Design Patterns&#8221; is normally referred to as just &#8220;Patterns&#8221;  and similarly with &#8220;Components&#8221;. The latter is especially bad, as it has meaning in every industry &#8211; the web site in question may well be for the manufacturer of components for some industry, for which each product may itself have numerous components. To a software developer, a component is a very specific amount of code, and very different from a page component (visual block), which may be built from beans, procedures, DLL&#8217;s etc.</p>
<p>If the headline had been: should I build a &#8220;Design Pattern Library&#8221; or a &#8220;Page Component Library&#8221; the conversation would surely have been much shorter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bookmarks for January 9th to January 11th &#124; BlobFisk.com</title>
		<link>http://www.uie.com/brainsparks/2009/01/09/uietips-components-vs-patterns/comment-page-1/#comment-145137</link>
		<dc:creator>Bookmarks for January 9th to January 11th &#124; BlobFisk.com</dc:creator>
		<pubDate>Sun, 11 Jan 2009 17:54:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=776#comment-145137</guid>
		<description>[...] UIEtips: Components Versus Patterns &#187; UIE Brain Sparks - [...]</description>
		<content:encoded><![CDATA[<p>[...] UIEtips: Components Versus Patterns &raquo; UIE Brain Sparks &#8211; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
