<?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 for Ashevile Web Design and Computer Networking :: Applied Solutions Group</title>
	<atom:link href="http://www.appliedtns.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.appliedtns.com/blog</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>Comment on Silverstripe CCK or Silverstripe for Drupal Users 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>Comment on Parsing out links from the Twitter API Response with Regular Expressions by Jeremy Lockhart</title>
		<link>http://www.appliedtns.com/blog/2009/04/parsing-out-links-from-the-twitter-api-response-with-regular-expressions/comment-page-1/#comment-89</link>
		<dc:creator>Jeremy Lockhart</dc:creator>
		<pubDate>Thu, 06 May 2010 00:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/?p=131#comment-89</guid>
		<description>Very nice! I&#039;m surprised there isn&#039;t at least some level of support for this in the Twitter API, but your post saved me a bunch of trouble with pesky regular expressions. Thanks!</description>
		<content:encoded><![CDATA[<p>Very nice! I&#8217;m surprised there isn&#8217;t at least some level of support for this in the Twitter API, but your post saved me a bunch of trouble with pesky regular expressions. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gmail Mobile on the Motorola i776 for Boost Mobile by Mandy</title>
		<link>http://www.appliedtns.com/blog/2009/07/gmail-mobile-on-the-motorola-i776-for-boost-mobile/comment-page-1/#comment-70</link>
		<dc:creator>Mandy</dc:creator>
		<pubDate>Wed, 28 Apr 2010 23:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/?p=134#comment-70</guid>
		<description>I still cannot get mine loaded can someone walk me step by step?</description>
		<content:encoded><![CDATA[<p>I still cannot get mine loaded can someone walk me step by step?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Safari 4 Beta CSS Hacks by admin</title>
		<link>http://www.appliedtns.com/blog/2009/02/safari-4-beta-css-hacks/comment-page-1/#comment-56</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 21 Apr 2010 17:57:45 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/?p=124#comment-56</guid>
		<description>Not sure if Chrome was really even out in Beta when this was posted. Either way, yes it does target WebKit browsers.</description>
		<content:encoded><![CDATA[<p>Not sure if Chrome was really even out in Beta when this was posted. Either way, yes it does target WebKit browsers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Safari 4 Beta CSS Hacks by William</title>
		<link>http://www.appliedtns.com/blog/2009/02/safari-4-beta-css-hacks/comment-page-1/#comment-55</link>
		<dc:creator>William</dc:creator>
		<pubDate>Wed, 21 Apr 2010 16:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/?p=124#comment-55</guid>
		<description>This does not target ONLY Safari, as it targets all of webkit browsers, so Chrome is affected as well.</description>
		<content:encoded><![CDATA[<p>This does not target ONLY Safari, as it targets all of webkit browsers, so Chrome is affected as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Safari 4 Beta CSS Hacks by San Francisco web design</title>
		<link>http://www.appliedtns.com/blog/2009/02/safari-4-beta-css-hacks/comment-page-1/#comment-54</link>
		<dc:creator>San Francisco web design</dc:creator>
		<pubDate>Wed, 14 Apr 2010 10:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/?p=124#comment-54</guid>
		<description>thanks for the helpful tips Tom..</description>
		<content:encoded><![CDATA[<p>thanks for the helpful tips Tom..</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Posting to Wordpress using XMLRPC and Textmate by Krysten Ascol</title>
		<link>http://www.appliedtns.com/blog/2009/01/posting-to-wordpress-using-xmlrpc-and-textmate/comment-page-1/#comment-42</link>
		<dc:creator>Krysten Ascol</dc:creator>
		<pubDate>Mon, 12 Apr 2010 15:55:09 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/tom/2009/01/posting-to-wordpress-using-xmlrpc-and-textmate/#comment-42</guid>
		<description>Excellent article, I am a big fan of this blog, keep on posting that great content, and I will be a regular for a long time.</description>
		<content:encoded><![CDATA[<p>Excellent article, I am a big fan of this blog, keep on posting that great content, and I will be a regular for a long time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Safari 4 Beta CSS Hacks by STUDIO -ひねもす- &#124; ひねもすブログ Safari 4.0 のみに効果がある CSSハック</title>
		<link>http://www.appliedtns.com/blog/2009/02/safari-4-beta-css-hacks/comment-page-1/#comment-53</link>
		<dc:creator>STUDIO -ひねもす- &#124; ひねもすブログ Safari 4.0 のみに効果がある CSSハック</dc:creator>
		<pubDate>Sun, 11 Apr 2010 15:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/?p=124#comment-53</guid>
		<description>[...] 海外のブログ [...]</description>
		<content:encoded><![CDATA[<p>[...] 海外のブログ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Safari 4 Beta CSS Hacks by Steve Dossett</title>
		<link>http://www.appliedtns.com/blog/2009/02/safari-4-beta-css-hacks/comment-page-1/#comment-52</link>
		<dc:creator>Steve Dossett</dc:creator>
		<pubDate>Tue, 30 Mar 2010 03:00:21 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/?p=124#comment-52</guid>
		<description>Thanks for this. Worked well. Usually Safari is well behaved, but I was off by a single pixel that was crucial to the design.</description>
		<content:encoded><![CDATA[<p>Thanks for this. Worked well. Usually Safari is well behaved, but I was off by a single pixel that was crucial to the design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Safari 4 Beta CSS Hacks by Chris M</title>
		<link>http://www.appliedtns.com/blog/2009/02/safari-4-beta-css-hacks/comment-page-1/#comment-51</link>
		<dc:creator>Chris M</dc:creator>
		<pubDate>Mon, 29 Mar 2010 18:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://ashevillewebblog.com/?p=124#comment-51</guid>
		<description>This is a good solution if the issue is with webkit based browsers globally (Safari, Chrome etc). If you have a Safari-only issue, this will not always work. This could be because the release versions of these browsers use slightly different versions of webkit, so the potential for slight rendering differences exist. I am having an issue now in which I need to target Safari 4 only. Since I am already targeting Chrome using the method above, I must decide in which browser it is more important to have pixel perfect rendering and which to sacrifice...</description>
		<content:encoded><![CDATA[<p>This is a good solution if the issue is with webkit based browsers globally (Safari, Chrome etc). If you have a Safari-only issue, this will not always work. This could be because the release versions of these browsers use slightly different versions of webkit, so the potential for slight rendering differences exist. I am having an issue now in which I need to target Safari 4 only. Since I am already targeting Chrome using the method above, I must decide in which browser it is more important to have pixel perfect rendering and which to sacrifice&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
