<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>michael-mccracken.net &#187; programming</title>
	<atom:link href="http://michael-mccracken.net/tag/programming/feed/" rel="self" type="application/rss+xml" />
	<link>http://michael-mccracken.net</link>
	<description>This is a weblog</description>
	<lastBuildDate>Wed, 17 Feb 2010 04:52:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>App History</title>
		<link>http://michael-mccracken.net/2009/11/app-history/</link>
		<comments>http://michael-mccracken.net/2009/11/app-history/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 18:02:06 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[programming]]></category>

		<guid isPermaLink="false">http://michael-mccracken.net/?p=237</guid>
		<description><![CDATA[I just saw Brent&#8217;s post from a couple weeks ago about an App History App &#8211; I think that&#8217;d be really cool. I especially like the screen shot idea, since I love seeing posts from a developer showing what an app looked like along the progression. It&#8217;s too easy to forget to document that kind [...]]]></description>
			<content:encoded><![CDATA[<p>I just saw Brent&#8217;s post from a couple weeks ago about an <a href="http://inessential.com/2009/11/08/apphistory_app_idea">App History App</a> &#8211; I think that&#8217;d be really cool. I especially like the screen shot idea, since I love seeing posts from a developer showing what an app looked like along the progression. It&#8217;s too easy to forget to document that kind of thing, and I&#8217;d love it if we saw more of these behind-the-scenes posts.</p>]]></content:encoded>
			<wfw:commentRss>http://michael-mccracken.net/2009/11/app-history/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iCal&#039;s Text Field Jumble</title>
		<link>http://michael-mccracken.net/2008/11/text-field-jumble/</link>
		<comments>http://michael-mccracken.net/2008/11/text-field-jumble/#comments</comments>
		<pubDate>Sun, 02 Nov 2008 21:38:46 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[mac]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[cocoa]]></category>
		<category><![CDATA[ui]]></category>

		<guid isPermaLink="false">http://michael-mccracken.net/wp/?p=121</guid>
		<description><![CDATA[Discussing some quirks of dialog design in iCal's event edit window.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve written here before about text fields, particularly the problem of having a good-looking &#8216;display&#8217; mode and a separate &#8216;edit&#8217; mode for data you don&#8217;t edit so often, like in AddressBook.</p>

<p>The most recent version of iCal decided that events are write-once-read-many as well. You now have to use cmd-E to get into edit mode, while cmd-I just gives you a small display mode.</p>

<p>I&#8217;m mostly OK with that, although I find I edit events about as often as I look at their info windows &#8211; after editing I usually just deal with alarms, not the events themselves. The casual glance at the time and title is always enough &#8211; I think either you&#8217;re looking at the time and title or you&#8217;re editing. I don&#8217;t see the appeal in the new &#8216;info-only&#8217; mode (if it&#8217;s actually new &#8211; it seems new.)</p>

<p>However, the change does highlight the jumble of editable text fields and text-like fields in the edit window:
<a href="http://michael-mccracken.net/wp2/wp-content/uploads/2008/11/pastedgraphic-1.tiff"><img src="http://michael-mccracken.net/wp2/wp-content/uploads/2008/11/pastedgraphic-1.tiff" alt="" title="Info window in iCal, 2008" class="alignnone size-full wp-image-125" /></a></p>

<p><a href="http://michael-mccracken.net/wp2/wp-content/uploads/2008/11/pastedgraphic.tiff"><img src="http://michael-mccracken.net/wp2/wp-content/uploads/2008/11/pastedgraphic.tiff" alt="" title="iCal info window, 2008" class="alignnone size-full wp-image-126" /></a></p>

<p>The &#8220;Add Attendees&#8221; link and the &#8220;None&#8221; placeholder for url act the same &#8211; you click on them, and enter text.
One&#8217;s a link and one&#8217;s mute gray text. Why?
For my part, I think the gray text is too understated, and the link is too garish.</p>

<p>There are other differences: you can tab to the &#8220;url&#8221; field, but you can&#8217;t tab to &#8220;attendees&#8221;&#8230; until you add one, then you can. Once you click on either of them, the url field pops up a plain white raised NSTextField, but the attendees field is sunken and translucent, apparently an NSTokenField?</p>

<p>Both of the blue links could also be buttons. I&#8217;m still not completely sold on replacing buttons with links, but I can understand the trend. I think a small plus-sign button would be fine for &#8220;Add File&#8221;, though, and &#8220;Attendees&#8221; ought to be a text field. Why force the user to use the mouse when adding data to an event?</p>

<p>All in all, I think the &#8220;Add Attendees&#8221; link/field is pretty strange. I&#8217;m curious if I missing a precedent somewhere.</p>]]></content:encoded>
			<wfw:commentRss>http://michael-mccracken.net/2008/11/text-field-jumble/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
