<?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: A (graphical) look at Final Cut Server.</title>
	<atom:link href="http://blog.cocoia.com/2007/10/21/a-graphical-look-at-final-cut-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cocoia.com/2007/10/21/a-graphical-look-at-final-cut-server/</link>
	<description>The Cocoia Blog is the website of Sebastiaan de With, a Dutch Icon and Interface designer.</description>
	<pubDate>Sat, 30 Aug 2008 03:34:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Cocoia Blog &#187; End-of-Month roundup.</title>
		<link>http://blog.cocoia.com/2007/10/21/a-graphical-look-at-final-cut-server/#comment-86647</link>
		<dc:creator>Cocoia Blog &#187; End-of-Month roundup.</dc:creator>
		<pubDate>Thu, 01 Nov 2007 00:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cocoia.com/?p=175#comment-86647</guid>
		<description>[...] graphical look at Final Cut Server was followed up by quite a few emails concerning Apple&#8217;s &#8216;icon rage&#8217; lately. It [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] graphical look at Final Cut Server was followed up by quite a few emails concerning Apple&#8217;s &#8216;icon rage&#8217; lately. It [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dbr</title>
		<link>http://blog.cocoia.com/2007/10/21/a-graphical-look-at-final-cut-server/#comment-80386</link>
		<dc:creator>dbr</dc:creator>
		<pubDate>Mon, 22 Oct 2007 15:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cocoia.com/?p=175#comment-80386</guid>
		<description>'I wish Apple and Adobe both would get back to using the system defaults'
As aesthetically horrible as the Shake UI is, it is functional. If it were to use the HIG-compatible, standard UI, it'd be unusable.

That said, there are some really annoying bugs in the shake UI (Like the "Show images only" setting that remains when you try to open/save scripts, even though there is no way to change that setting from inside the open/save script dialog..)

To someone actually using Shake, it's way way more important the interface 'works', rather than complies to the HIG, or fits in with the rest of the Apple products.

Of course your looking at the software from a purely visual point of view, but for the higher-end applications, functionality comes a long way before aesthetics. Take any high-end visual-effects/3D application as an example, like Houdini, Maya, Flame etc.

As for the dark interfaces, ignoring the fact colours other than neutral-grey will alter the perception of colour (bad for colour-correction and such - although I imagine it will only be an issue if your interface happens to be bright pink or something) - A lot of compositing happens in dark rooms... A brighter interfaces means more light coming out your monitor, and when you're looking at that screen for long hours, in the dark - it's going to hurt your eyes.</description>
		<content:encoded><![CDATA[<p>&#8216;I wish Apple and Adobe both would get back to using the system defaults&#8217;<br />
As aesthetically horrible as the Shake UI is, it is functional. If it were to use the HIG-compatible, standard UI, it&#8217;d be unusable.</p>
<p>That said, there are some really annoying bugs in the shake UI (Like the &#8220;Show images only&#8221; setting that remains when you try to open/save scripts, even though there is no way to change that setting from inside the open/save script dialog..)</p>
<p>To someone actually using Shake, it&#8217;s way way more important the interface &#8216;works&#8217;, rather than complies to the HIG, or fits in with the rest of the Apple products.</p>
<p>Of course your looking at the software from a purely visual point of view, but for the higher-end applications, functionality comes a long way before aesthetics. Take any high-end visual-effects/3D application as an example, like Houdini, Maya, Flame etc.</p>
<p>As for the dark interfaces, ignoring the fact colours other than neutral-grey will alter the perception of colour (bad for colour-correction and such - although I imagine it will only be an issue if your interface happens to be bright pink or something) - A lot of compositing happens in dark rooms&#8230; A brighter interfaces means more light coming out your monitor, and when you&#8217;re looking at that screen for long hours, in the dark - it&#8217;s going to hurt your eyes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twist</title>
		<link>http://blog.cocoia.com/2007/10/21/a-graphical-look-at-final-cut-server/#comment-79565</link>
		<dc:creator>Twist</dc:creator>
		<pubDate>Sun, 21 Oct 2007 16:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cocoia.com/?p=175#comment-79565</guid>
		<description>All these custom interfaces are really starting to get on my nerves. I wish Apple and Adobe both would get back to using the system defaults (especially Adobe since I use way more of their apps).</description>
		<content:encoded><![CDATA[<p>All these custom interfaces are really starting to get on my nerves. I wish Apple and Adobe both would get back to using the system defaults (especially Adobe since I use way more of their apps).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: capa</title>
		<link>http://blog.cocoia.com/2007/10/21/a-graphical-look-at-final-cut-server/#comment-79546</link>
		<dc:creator>capa</dc:creator>
		<pubDate>Sun, 21 Oct 2007 15:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cocoia.com/?p=175#comment-79546</guid>
		<description>"ut it almost seems derived from the overly ‘dark’ style the Adobe CS3 apps have been using. There is a complete absence of gloss in the interface, which makes it stand out a lot from all other Pro applications and general aesthetic of OS X."

I work in the film industry and the 50 percent grey to black look of interfaces is pretty much everywhere. Neutral value in the interface as to not have colour bleed when colour correcting. 

   Of course now it doesn't really have much of an impact since usually there's more light bleeding from the workspace (or from the half of dozen monitors sitting around). Still, an interface that doesn't grab attention is essential here.

 It's a convention in higher-end video apps, from shake to toxic to combustion. The next update of Nuke is shifting it's interface to a darker feel.  CS3 did the same thing, makes it look like they are playing in the same sandbox.
more of a fad, if you ask me.</description>
		<content:encoded><![CDATA[<p>&#8220;ut it almost seems derived from the overly ‘dark’ style the Adobe CS3 apps have been using. There is a complete absence of gloss in the interface, which makes it stand out a lot from all other Pro applications and general aesthetic of OS X.&#8221;</p>
<p>I work in the film industry and the 50 percent grey to black look of interfaces is pretty much everywhere. Neutral value in the interface as to not have colour bleed when colour correcting. </p>
<p>   Of course now it doesn&#8217;t really have much of an impact since usually there&#8217;s more light bleeding from the workspace (or from the half of dozen monitors sitting around). Still, an interface that doesn&#8217;t grab attention is essential here.</p>
<p> It&#8217;s a convention in higher-end video apps, from shake to toxic to combustion. The next update of Nuke is shifting it&#8217;s interface to a darker feel.  CS3 did the same thing, makes it look like they are playing in the same sandbox.<br />
more of a fad, if you ask me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
