<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Doug Seven</title>
	<atom:link href="http://dougseven.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://dougseven.com</link>
	<description>Something can be learned in the course of observing things</description>
	<lastBuildDate>Thu, 23 May 2013 10:08:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on What About Windows Phone? by joeriks</title>
		<link>http://dougseven.com/2012/10/24/what-about-windows-phone/#comment-1827</link>
		<dc:creator><![CDATA[joeriks]]></dc:creator>
		<pubDate>Thu, 23 May 2013 10:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://dougseven.com/2012/10/23/what-about-windows-phone/#comment-1827</guid>
		<description><![CDATA[Happy to see Telerik KendoUI supports Windows8 phones. I get back to Icenium when it does too :)]]></description>
		<content:encoded><![CDATA[<p>Happy to see Telerik KendoUI supports Windows8 phones. I get back to Icenium when it does too <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Overcoming the New Visual Studio UI by farmerbuzz</title>
		<link>http://dougseven.com/2012/02/27/overcoming-the-new-visual-studio-ui/#comment-1817</link>
		<dc:creator><![CDATA[farmerbuzz]]></dc:creator>
		<pubDate>Fri, 17 May 2013 20:16:26 +0000</pubDate>
		<guid isPermaLink="false">https://dougseven.wordpress.com/?p=186#comment-1817</guid>
		<description><![CDATA[When I&#039;m navigating a tree in VS2012 and I can&#039;t tell which icons are files and which icons are folders because they are all inscrutable black lines I have a lot of trouble. 

This is not me being afraid of change, this is me being afraid of the morons that have taken over Microsoft.]]></description>
		<content:encoded><![CDATA[<p>When I&#8217;m navigating a tree in VS2012 and I can&#8217;t tell which icons are files and which icons are folders because they are all inscrutable black lines I have a lot of trouble. </p>
<p>This is not me being afraid of change, this is me being afraid of the morons that have taken over Microsoft.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on My New Life in the Cloud &#8211; Day 0 by Eddie S Jackson</title>
		<link>http://dougseven.com/2012/09/04/my-new-life-in-the-cloud-day-0/#comment-1790</link>
		<dc:creator><![CDATA[Eddie S Jackson]]></dc:creator>
		<pubDate>Wed, 08 May 2013 22:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://dougseven.com/?p=223#comment-1790</guid>
		<description><![CDATA[Nice setup!  A pic of my old desk: http://eddiejackson.net/web_images/workpic2.jpg]]></description>
		<content:encoded><![CDATA[<p>Nice setup!  A pic of my old desk: <a href="http://eddiejackson.net/web_images/workpic2.jpg" rel="nofollow">http://eddiejackson.net/web_images/workpic2.jpg</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Overcoming the New Visual Studio UI by Adam</title>
		<link>http://dougseven.com/2012/02/27/overcoming-the-new-visual-studio-ui/#comment-1774</link>
		<dc:creator><![CDATA[Adam]]></dc:creator>
		<pubDate>Fri, 26 Apr 2013 12:08:02 +0000</pubDate>
		<guid isPermaLink="false">https://dougseven.wordpress.com/?p=186#comment-1774</guid>
		<description><![CDATA[OW--My Eyes!

Ergonomics anyone? Does Microsoft have some hidden angle in forcing developers to visit their local optometrist? I don&#039;t mind the look--if I jumped out of my skin every time Microsoft did something ridiculous...(well, I don&#039;t know what I&#039;d do.)]]></description>
		<content:encoded><![CDATA[<p>OW&#8211;My Eyes!</p>
<p>Ergonomics anyone? Does Microsoft have some hidden angle in forcing developers to visit their local optometrist? I don&#8217;t mind the look&#8211;if I jumped out of my skin every time Microsoft did something ridiculous&#8230;(well, I don&#8217;t know what I&#8217;d do.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Overcoming the New Visual Studio UI by Xen</title>
		<link>http://dougseven.com/2012/02/27/overcoming-the-new-visual-studio-ui/#comment-1759</link>
		<dc:creator><![CDATA[Xen]]></dc:creator>
		<pubDate>Tue, 23 Apr 2013 07:06:56 +0000</pubDate>
		<guid isPermaLink="false">https://dougseven.wordpress.com/?p=186#comment-1759</guid>
		<description><![CDATA[Visual Styles.]]></description>
		<content:encoded><![CDATA[<p>Visual Styles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Overcoming the New Visual Studio UI by Xen</title>
		<link>http://dougseven.com/2012/02/27/overcoming-the-new-visual-studio-ui/#comment-1758</link>
		<dc:creator><![CDATA[Xen]]></dc:creator>
		<pubDate>Tue, 23 Apr 2013 07:05:31 +0000</pubDate>
		<guid isPermaLink="false">https://dougseven.wordpress.com/?p=186#comment-1758</guid>
		<description><![CDATA[Allow the developers to change the UI. VS2008 / VS2010 or VS2012 or change it to suit your own requirements. Provide a few themes and allow developers to share themes that they have created. When designing the UI (Microsoft!!) did you guys not think a little further in case those developers that did not like the theme could change it. Come on, MS!!! You have so many supporters out there.]]></description>
		<content:encoded><![CDATA[<p>Allow the developers to change the UI. VS2008 / VS2010 or VS2012 or change it to suit your own requirements. Provide a few themes and allow developers to share themes that they have created. When designing the UI (Microsoft!!) did you guys not think a little further in case those developers that did not like the theme could change it. Come on, MS!!! You have so many supporters out there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Overcoming the New Visual Studio UI by Tim</title>
		<link>http://dougseven.com/2012/02/27/overcoming-the-new-visual-studio-ui/#comment-1756</link>
		<dc:creator><![CDATA[Tim]]></dc:creator>
		<pubDate>Tue, 23 Apr 2013 00:35:32 +0000</pubDate>
		<guid isPermaLink="false">https://dougseven.wordpress.com/?p=186#comment-1756</guid>
		<description><![CDATA[I would liken it to a car manufacturer deciding to replace all of the rotary dials with a group of nondescript vertical bar gauges in the middle of the dash.  Gauges for speed, temperature, oil pressure, engine RPMs, etc. are all just sitting next to each other, evenly spaced, and uniform in color.

You can tell which one is which because there is a small bit of capitalized text below each telling you what it does.  For example, you can tell apart speed and outside temperature because the speed gauge has &quot;SPD&quot; below it, while the temperature gauge sitting next to it says &quot;TEMP&quot;.  The temperature gauge also starts at -20 and goes to +120, while the speed gauge goes from 0 to +140.

Eventually it would become second nature where exactly the speed gauge is located, and you would no longer make the mistake of mixing it up with the temperature gauge next to it.  But why should you have to go through that learning process when the speedometer was better than the speed gauge in every way as far as usability and aesthetics are concerned?]]></description>
		<content:encoded><![CDATA[<p>I would liken it to a car manufacturer deciding to replace all of the rotary dials with a group of nondescript vertical bar gauges in the middle of the dash.  Gauges for speed, temperature, oil pressure, engine RPMs, etc. are all just sitting next to each other, evenly spaced, and uniform in color.</p>
<p>You can tell which one is which because there is a small bit of capitalized text below each telling you what it does.  For example, you can tell apart speed and outside temperature because the speed gauge has &#8220;SPD&#8221; below it, while the temperature gauge sitting next to it says &#8220;TEMP&#8221;.  The temperature gauge also starts at -20 and goes to +120, while the speed gauge goes from 0 to +140.</p>
<p>Eventually it would become second nature where exactly the speed gauge is located, and you would no longer make the mistake of mixing it up with the temperature gauge next to it.  But why should you have to go through that learning process when the speedometer was better than the speed gauge in every way as far as usability and aesthetics are concerned?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Overcoming the New Visual Studio UI by Tim</title>
		<link>http://dougseven.com/2012/02/27/overcoming-the-new-visual-studio-ui/#comment-1755</link>
		<dc:creator><![CDATA[Tim]]></dc:creator>
		<pubDate>Tue, 23 Apr 2013 00:06:49 +0000</pubDate>
		<guid isPermaLink="false">https://dougseven.wordpress.com/?p=186#comment-1755</guid>
		<description><![CDATA[The default VS2012 color scheme is pretty bad.  The reason why it&#039;s bad is not because it&#039;s different, but because it requires a lot more effort than it should to differentiate between different UI elements.  

With no easily distinguishable lines to separate different areas of the screen, it may require several seconds of scrutiny to determine whether, for example, the last line of visible text in a pane is actually the last line, or if the text is cut off by the bottom of the pane, and you should scroll to see more.  With the old UI, such things were obvious, and therefore much easier to read and use.  It was also much easier to tell the difference between buttons, tabs, and plain text, and to identify groupings of UI elements that probably apply to similar things.

Fortunately, the theme editor is fairly robust, and it was not too difficult for me to create a color theme that acceptably rectifies the problem.  I can add contrast, and the UI becomes relatively easy to read again.

Now the main problems I&#039;m facing are the crashing and slow find-in-files  Unfortunately I don&#039;t know of such easy workarounds for those.]]></description>
		<content:encoded><![CDATA[<p>The default VS2012 color scheme is pretty bad.  The reason why it&#8217;s bad is not because it&#8217;s different, but because it requires a lot more effort than it should to differentiate between different UI elements.  </p>
<p>With no easily distinguishable lines to separate different areas of the screen, it may require several seconds of scrutiny to determine whether, for example, the last line of visible text in a pane is actually the last line, or if the text is cut off by the bottom of the pane, and you should scroll to see more.  With the old UI, such things were obvious, and therefore much easier to read and use.  It was also much easier to tell the difference between buttons, tabs, and plain text, and to identify groupings of UI elements that probably apply to similar things.</p>
<p>Fortunately, the theme editor is fairly robust, and it was not too difficult for me to create a color theme that acceptably rectifies the problem.  I can add contrast, and the UI becomes relatively easy to read again.</p>
<p>Now the main problems I&#8217;m facing are the crashing and slow find-in-files  Unfortunately I don&#8217;t know of such easy workarounds for those.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What About Windows Phone? by tim</title>
		<link>http://dougseven.com/2012/10/24/what-about-windows-phone/#comment-1737</link>
		<dc:creator><![CDATA[tim]]></dc:creator>
		<pubDate>Sun, 14 Apr 2013 11:22:40 +0000</pubDate>
		<guid isPermaLink="false">http://dougseven.com/2012/10/23/what-about-windows-phone/#comment-1737</guid>
		<description><![CDATA[You should have a type of crowd source &quot;thing&quot; On your website you should ask the developers if they will pledge a certain amount of money to the development of the windows side of this awesome product. If the response is good then you have a bit of the capital and the dev base to use it. We have clients right now that want apps on all devices and we explain to them that it is possible but we will more money to do this. If we can bring out price point down with the ability to develop once for all devices ... man, that will be a very good day.

You have a seriously cool product. One that is making everyone wonder how the bigger players ( not that telerik is small ;) did not get this right. I do not know one developer that enjoys developing the same thing for every type of device, it sucks so much. And with windows you could essentially develop one app for every device type , phone , tablet, desktop. Actually you should get microsoft to sponsor it . It would only be good for them.

I know i would throw money at you for this.]]></description>
		<content:encoded><![CDATA[<p>You should have a type of crowd source &#8220;thing&#8221; On your website you should ask the developers if they will pledge a certain amount of money to the development of the windows side of this awesome product. If the response is good then you have a bit of the capital and the dev base to use it. We have clients right now that want apps on all devices and we explain to them that it is possible but we will more money to do this. If we can bring out price point down with the ability to develop once for all devices &#8230; man, that will be a very good day.</p>
<p>You have a seriously cool product. One that is making everyone wonder how the bigger players ( not that telerik is small <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  did not get this right. I do not know one developer that enjoys developing the same thing for every type of device, it sucks so much. And with windows you could essentially develop one app for every device type , phone , tablet, desktop. Actually you should get microsoft to sponsor it . It would only be good for them.</p>
<p>I know i would throw money at you for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Overcoming the New Visual Studio UI by rextimmy</title>
		<link>http://dougseven.com/2012/02/27/overcoming-the-new-visual-studio-ui/#comment-1736</link>
		<dc:creator><![CDATA[rextimmy]]></dc:creator>
		<pubDate>Sun, 14 Apr 2013 05:00:28 +0000</pubDate>
		<guid isPermaLink="false">https://dougseven.wordpress.com/?p=186#comment-1736</guid>
		<description><![CDATA[If you had any involvement as a reviewer you have failed miserably or just told them what they wanted to hear. This is the most hideous UI i have used, words can&#039;t describe how badly Microsoft have failed with VS 2012. Honestly, how could you look at that 9-5 at work all day?There is no way in hell i will use it and luckily my work place agreed with me too.

Personally I loved VS 2010 and will continue to use it, it has a extremely nice UI design. Such a shame, i always looked forward to new releases of VS as the interface always got better and better. Until some absolute moron/s decided a bland looking Windows 3.11 interface would look great.]]></description>
		<content:encoded><![CDATA[<p>If you had any involvement as a reviewer you have failed miserably or just told them what they wanted to hear. This is the most hideous UI i have used, words can&#8217;t describe how badly Microsoft have failed with VS 2012. Honestly, how could you look at that 9-5 at work all day?There is no way in hell i will use it and luckily my work place agreed with me too.</p>
<p>Personally I loved VS 2010 and will continue to use it, it has a extremely nice UI design. Such a shame, i always looked forward to new releases of VS as the interface always got better and better. Until some absolute moron/s decided a bland looking Windows 3.11 interface would look great.</p>
]]></content:encoded>
	</item>
</channel>
</rss>