<?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"
	>
<channel>
	<title>Comments on: Improving Mac OS X: #8 - Zoom</title>
	<atom:link href="http://curmi.com/blog/2007/09/23/improving-mac-os-x-zoom/feed/" rel="self" type="application/rss+xml" />
	<link>http://curmi.com/blog/2007/09/23/improving-mac-os-x-zoom/</link>
	<description>Mac stuff, Tech stuff, Weird stuff</description>
	<pubDate>Thu, 20 Nov 2008 00:01:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: curmi</title>
		<link>http://curmi.com/blog/2007/09/23/improving-mac-os-x-zoom/#comment-7609</link>
		<dc:creator>curmi</dc:creator>
		<pubDate>Mon, 05 Nov 2007 11:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://curmi.com/blog/2007/09/23/improving-mac-os-x-zoom/#comment-7609</guid>
		<description>For any developers wanting to make zoom work correctly in their OS X applications, here's an interesting article that might help.

http://www.oreillynet.com/pub/a/mac/2002/05/16/cocoa.html</description>
		<content:encoded><![CDATA[<p>For any developers wanting to make zoom work correctly in their OS X applications, here&#8217;s an interesting article that might help.</p>
<p><a href="http://www.oreillynet.com/pub/a/mac/2002/05/16/cocoa.html" rel="nofollow">http://www.oreillynet.com/pub/a/mac/2002/05/16/cocoa.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: curmi</title>
		<link>http://curmi.com/blog/2007/09/23/improving-mac-os-x-zoom/#comment-5592</link>
		<dc:creator>curmi</dc:creator>
		<pubDate>Sun, 23 Sep 2007 21:52:41 +0000</pubDate>
		<guid isPermaLink="false">http://curmi.com/blog/2007/09/23/improving-mac-os-x-zoom/#comment-5592</guid>
		<description>Hey Sebastian.

Whether you disagree or not, the fact remains that the action is confusing.  If the effect of clicking a button is  inconsistent people will shy away from ever touching the button.

Reading some of the forums, that is exactly what happens - people stop clicking the button because they never know what to expect.  That suggests that the button is being overloaded with too many features.

I'm not saying that the functionality of the calculator isn't good - just that overloading the button to use that functionality isn't good.</description>
		<content:encoded><![CDATA[<p>Hey Sebastian.</p>
<p>Whether you disagree or not, the fact remains that the action is confusing.  If the effect of clicking a button is  inconsistent people will shy away from ever touching the button.</p>
<p>Reading some of the forums, that is exactly what happens - people stop clicking the button because they never know what to expect.  That suggests that the button is being overloaded with too many features.</p>
<p>I&#8217;m not saying that the functionality of the calculator isn&#8217;t good - just that overloading the button to use that functionality isn&#8217;t good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian Lewis</title>
		<link>http://curmi.com/blog/2007/09/23/improving-mac-os-x-zoom/#comment-5591</link>
		<dc:creator>Sebastian Lewis</dc:creator>
		<pubDate>Sun, 23 Sep 2007 21:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://curmi.com/blog/2007/09/23/improving-mac-os-x-zoom/#comment-5591</guid>
		<description>I disagree with some of that actually, more specifically, the part about Apple or any developer following the guidelines to the letter without question.  For one thing, they're guidelines, not law, and for another, sometimes the guidelines don't make sense for a specific application.

iTunes for example, when you "Zoom" it, it becomes a mini player.  I like this mini player because with the iLike sidebar installed, iTunes eats up almost all screen space on my Macbook.  This may not be the case on a 30" display, but on a 13.3" display it makes a difference and the mini player can stay in the top left corner out of the way.

Calculator is another example, hitting the Zoom button takes it between Standard, Scientific, and Programmer modes.  Now expanding the Calculator to be larger then it is obviously makes no sense because it doesn't need to be any larger, but it can change states since it has 3 different modes and it's much faster than going to the menu and while it does have keyboard shortcuts, I don't use it often enough to remember what those are.

The HIG are just that: Guidelines.

guideline &#124;ˈgīdˌlīn&#124;
noun
a general rule, principle, or piece of advice.

Sebastian</description>
		<content:encoded><![CDATA[<p>I disagree with some of that actually, more specifically, the part about Apple or any developer following the guidelines to the letter without question.  For one thing, they&#8217;re guidelines, not law, and for another, sometimes the guidelines don&#8217;t make sense for a specific application.</p>
<p>iTunes for example, when you &#8220;Zoom&#8221; it, it becomes a mini player.  I like this mini player because with the iLike sidebar installed, iTunes eats up almost all screen space on my Macbook.  This may not be the case on a 30&#8243; display, but on a 13.3&#8243; display it makes a difference and the mini player can stay in the top left corner out of the way.</p>
<p>Calculator is another example, hitting the Zoom button takes it between Standard, Scientific, and Programmer modes.  Now expanding the Calculator to be larger then it is obviously makes no sense because it doesn&#8217;t need to be any larger, but it can change states since it has 3 different modes and it&#8217;s much faster than going to the menu and while it does have keyboard shortcuts, I don&#8217;t use it often enough to remember what those are.</p>
<p>The HIG are just that: Guidelines.</p>
<p>guideline |ˈgīdˌlīn|<br />
noun<br />
a general rule, principle, or piece of advice.</p>
<p>Sebastian</p>
]]></content:encoded>
	</item>
</channel>
</rss>
