<?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: Silverstripe CCK or Silverstripe for Drupal Users</title>
	<atom:link href="http://www.appliedtns.com/blog/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.appliedtns.com/blog/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 17 May 2010 18:02:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Web</title>
		<link>http://www.appliedtns.com/blog/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/comment-page-1/#comment-103</link>
		<dc:creator>Web</dc:creator>
		<pubDate>Mon, 17 May 2010 18:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/tom/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/#comment-103</guid>
		<description>&lt;i&gt;Wondering though, why with SS, Django, etc. must one define formfields at the code level?? If you create your database tables (id, field1, field2, etc.) the model definitions are already in place.  On the CMS level one would simply import those already created DB table fields via GUI vs. typing it all out by hand.&lt;/i&gt;
+1</description>
		<content:encoded><![CDATA[<p><i>Wondering though, why with SS, Django, etc. must one define formfields at the code level?? If you create your database tables (id, field1, field2, etc.) the model definitions are already in place.  On the CMS level one would simply import those already created DB table fields via GUI vs. typing it all out by hand.</i><br />
+1</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why not this</title>
		<link>http://www.appliedtns.com/blog/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/comment-page-1/#comment-66</link>
		<dc:creator>Why not this</dc:creator>
		<pubDate>Thu, 25 Mar 2010 22:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/tom/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/#comment-66</guid>
		<description>Silverstripe does indeed look like an ideal CMS given that unlike Drupal it is actually PHP5 OO driven.

Wondering though, why with SS, Django, etc. must one define formfields at the code level?? If you create your database tables (id, field1, field2, etc.) the model definitions are already in place.  On the CMS level one would simply import those already created DB table fields via GUI vs. typing it all out by hand.

I do this with my roll-my-own CMS -- form presentation, reports and data storage are literally button clicks, drag and drop ordering of fields (and modules on the view level).  The only time you have to code is coding to the exception vs. defining everything at code level.

Anyway, must be a reason the big CM platforms are setup as they are.  Django is indeed awesome, if SS comes close, I&#039;ll consider making the dive, just downloaded it and am sooooo pleased to see actual objects vs. Drupal local &quot;hook&quot; functions, what a zoo.</description>
		<content:encoded><![CDATA[<p>Silverstripe does indeed look like an ideal CMS given that unlike Drupal it is actually PHP5 OO driven.</p>
<p>Wondering though, why with SS, Django, etc. must one define formfields at the code level?? If you create your database tables (id, field1, field2, etc.) the model definitions are already in place.  On the CMS level one would simply import those already created DB table fields via GUI vs. typing it all out by hand.</p>
<p>I do this with my roll-my-own CMS &#8212; form presentation, reports and data storage are literally button clicks, drag and drop ordering of fields (and modules on the view level).  The only time you have to code is coding to the exception vs. defining everything at code level.</p>
<p>Anyway, must be a reason the big CM platforms are setup as they are.  Django is indeed awesome, if SS comes close, I&#8217;ll consider making the dive, just downloaded it and am sooooo pleased to see actual objects vs. Drupal local &#8220;hook&#8221; functions, what a zoo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rezeptfreie Potenzmittel</title>
		<link>http://www.appliedtns.com/blog/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/comment-page-1/#comment-65</link>
		<dc:creator>Rezeptfreie Potenzmittel</dc:creator>
		<pubDate>Sun, 21 Mar 2010 02:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/tom/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/#comment-65</guid>
		<description>I am completly Agree with you! Great Article!</description>
		<content:encoded><![CDATA[<p>I am completly Agree with you! Great Article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silverstripe CCK or Silverstripe for Drupal Users &#124; Asheville Web &#8230; &#124; developer</title>
		<link>http://www.appliedtns.com/blog/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/comment-page-1/#comment-64</link>
		<dc:creator>Silverstripe CCK or Silverstripe for Drupal Users &#124; Asheville Web &#8230; &#124; developer</dc:creator>
		<pubDate>Mon, 03 Aug 2009 20:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/tom/2009/08/silverstripe-cck-or-silverstripe-for-drupal-users/#comment-64</guid>
		<description>[...] Continue reading here: Silverstripe CCK or Silverstripe for Drupal Users &#124; Asheville Web ... [...]</description>
		<content:encoded><![CDATA[<p>[...] Continue reading here: Silverstripe CCK or Silverstripe for Drupal Users | Asheville Web &#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
