<?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: The broken link paradox</title>
	<atom:link href="http://www.iacons.net/writing/2007/03/04/the-broken-link-paradox/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iacons.net/writing/2007/03/04/the-broken-link-paradox/</link>
	<description></description>
	<lastBuildDate>Fri, 09 Apr 2010 01:26:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Iacovos</title>
		<link>http://www.iacons.net/writing/2007/03/04/the-broken-link-paradox/comment-page-1/#comment-2075</link>
		<dc:creator>Iacovos</dc:creator>
		<pubDate>Sat, 31 Mar 2007 09:52:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.iacons.net/writing/2007/03/04/the-broken-link-paradox/#comment-2075</guid>
		<description>&lt;p&gt;Thanks for your reply George. I found your suggestion so easy and straightforward that I am wondering how I could not come up with it in the first place. Well, I guess this is the point where experience makes the difference, huh? :)&lt;/p&gt;
&lt;p&gt;P.S: I am sorry it took me so long to reply to your comment -- I have been quite busy the last few weeks trying to sort out both work and studies.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for your reply George. I found your suggestion so easy and straightforward that I am wondering how I could not come up with it in the first place. Well, I guess this is the point where experience makes the difference, huh? <img src='http://www.iacons.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>P.S: I am sorry it took me so long to reply to your comment &#8212; I have been quite busy the last few weeks trying to sort out both work and studies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://www.iacons.net/writing/2007/03/04/the-broken-link-paradox/comment-page-1/#comment-1300</link>
		<dc:creator>George</dc:creator>
		<pubDate>Fri, 09 Mar 2007 13:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.iacons.net/writing/2007/03/04/the-broken-link-paradox/#comment-1300</guid>
		<description>&lt;p&gt;It&#039;s been my experience that this happens with more than broken links. In fact, it&#039;s something that happens with all GUI control elements.&lt;/p&gt;
&lt;p&gt;Lets say you have a flash element with a button whose actions you haven&#039;t implemented yet, so the button is there but clicking it does absolutely nothing. Clients and even colleagues will inevitably come back to you and report that the button doesn&#039;t work. If you make it pop-up an alert which reads something like &#039;This is still under construction&#039;, people will come back and report that the button is popping-up a message instead of working and it needs to be implemented.&lt;/p&gt;
&lt;p&gt;What I&#039;m getting at, is that anything you present to clients, or even higher levels of management withing the development environment, should be skinned down to whatever actually works. Put place holders where stuff isn&#039;t ready yet, but don&#039;t put interface controls unless they are usable. Interface controls are irresistible, and if they don&#039;t behave properly they cause frustration. Links, buttons, selectors, scroll bars, get them out until they&#039;re done.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It&#8217;s been my experience that this happens with more than broken links. In fact, it&#8217;s something that happens with all GUI control elements.</p>
<p>Lets say you have a flash element with a button whose actions you haven&#8217;t implemented yet, so the button is there but clicking it does absolutely nothing. Clients and even colleagues will inevitably come back to you and report that the button doesn&#8217;t work. If you make it pop-up an alert which reads something like &#8216;This is still under construction&#8217;, people will come back and report that the button is popping-up a message instead of working and it needs to be implemented.</p>
<p>What I&#8217;m getting at, is that anything you present to clients, or even higher levels of management withing the development environment, should be skinned down to whatever actually works. Put place holders where stuff isn&#8217;t ready yet, but don&#8217;t put interface controls unless they are usable. Interface controls are irresistible, and if they don&#8217;t behave properly they cause frustration. Links, buttons, selectors, scroll bars, get them out until they&#8217;re done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
