<?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: UI Control Naming Conventions</title>
	<atom:link href="http://www.owenpellegrin.com/blog/net/ui-control-naming-conventions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.owenpellegrin.com/blog/net/ui-control-naming-conventions/</link>
	<description>I write stuff here</description>
	<lastBuildDate>Wed, 07 Jul 2010 09:26:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Bill Bartmann</title>
		<link>http://www.owenpellegrin.com/blog/net/ui-control-naming-conventions/comment-page-1/#comment-1783</link>
		<dc:creator>Bill Bartmann</dc:creator>
		<pubDate>Thu, 17 Sep 2009 15:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.owenpellegrin.com/blog/net/ui-control-naming-conventions-a-boondoggle/#comment-1783</guid>
		<description>I&#039;m so glad I found this site...Keep up the good work I read a lot of blogs on a daily basis and for the most part, people lack substance but, I just wanted to make a quick comment to say GREAT blog.  Thanks,

A definite great read...:)

&lt;a href=&quot;http://forum.dotnetpanel.com/members/Bill-Bartmann.aspx&quot; rel=&quot;nofollow&quot;&gt;-Bill-Bartmann&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I&#8217;m so glad I found this site&#8230;Keep up the good work I read a lot of blogs on a daily basis and for the most part, people lack substance but, I just wanted to make a quick comment to say GREAT blog.  Thanks,</p>
<p>A definite great read&#8230;:)</p>
<p><a href="http://forum.dotnetpanel.com/members/Bill-Bartmann.aspx" rel="nofollow">-Bill-Bartmann</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AZ</title>
		<link>http://www.owenpellegrin.com/blog/net/ui-control-naming-conventions/comment-page-1/#comment-1726</link>
		<dc:creator>AZ</dc:creator>
		<pubDate>Thu, 03 Sep 2009 20:25:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.owenpellegrin.com/blog/net/ui-control-naming-conventions-a-boondoggle/#comment-1726</guid>
		<description>This made me remember what we once used for a school project that had like zillion controls and the requirements were changing every period.

We decided to prefix each control with one of the following:
ic for input control, oc for output control and dc for display control. Of course, this ends up to be Hungarian notation too. Tho, one can always suffix InputControl, OutputControl and DisplayControl.</description>
		<content:encoded><![CDATA[<p>This made me remember what we once used for a school project that had like zillion controls and the requirements were changing every period.</p>
<p>We decided to prefix each control with one of the following:<br />
ic for input control, oc for output control and dc for display control. Of course, this ends up to be Hungarian notation too. Tho, one can always suffix InputControl, OutputControl and DisplayControl.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Westness</title>
		<link>http://www.owenpellegrin.com/blog/net/ui-control-naming-conventions/comment-page-1/#comment-1725</link>
		<dc:creator>Brad Westness</dc:creator>
		<pubDate>Thu, 03 Sep 2009 19:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.owenpellegrin.com/blog/net/ui-control-naming-conventions-a-boondoggle/#comment-1725</guid>
		<description>I usually stick with the suffix notation with camel casing. The result is that a lot of my control names are pretty unwieldy, but I think it&#039;s the most self-commenting method of naming controls. 

However, it is brittle, as you said, changing from stateTextBox to stateComboBox requires searching for every instance of the control. 

Maybe naming it something like stateInput or stateInputControl (or whatever) would eliminate the confusion inherent in just calling it &quot;state&quot; but still allow the control type to be changed without breaking everything.</description>
		<content:encoded><![CDATA[<p>I usually stick with the suffix notation with camel casing. The result is that a lot of my control names are pretty unwieldy, but I think it&#8217;s the most self-commenting method of naming controls. </p>
<p>However, it is brittle, as you said, changing from stateTextBox to stateComboBox requires searching for every instance of the control. </p>
<p>Maybe naming it something like stateInput or stateInputControl (or whatever) would eliminate the confusion inherent in just calling it &#8220;state&#8221; but still allow the control type to be changed without breaking everything.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
