<?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: How to make your app&#8217;s Dock tile highlight</title>
	<atom:link href="http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight/feed" rel="self" type="application/rss+xml" />
	<link>http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight</link>
	<description>The personal weblog of Peter Hosey.</description>
	<pubDate>Fri, 05 Dec 2008 13:29:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Jeff Johnson</title>
		<link>http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108983</link>
		<dc:creator>Jeff Johnson</dc:creator>
		<pubDate>Tue, 24 Jul 2007 15:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108983</guid>
		<description>Hi. Just wanted to let you know that there seem to be typos in http://feeds.feedburner.com/domainofthebored where it's referring to http://boredzo.org/blog/archives/2007-07-24/configure-application-dock-tile, which doesn't exist, rather than to http://boredzo.org/blog/archives/2007-07-23/configure-application-dock-tile.</description>
		<content:encoded><![CDATA[<p>Hi. Just wanted to let you know that there seem to be typos in <a href="http://feeds.feedburner.com/domainofthebored" rel="nofollow">http://feeds.feedburner.com/domainofthebored</a> where it's referring to <a href="http://boredzo.org/blog/archives/2007-07-24/configure-application-dock-tile" rel="nofollow">http://boredzo.org/blog/archives/2007-07-24/configure-application-dock-tile</a>, which doesn't exist, rather than to <a href="http://boredzo.org/blog/archives/2007-07-23/configure-application-dock-tile" rel="nofollow">http://boredzo.org/blog/archives/2007-07-23/configure-application-dock-tile</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Hosey</title>
		<link>http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108689</link>
		<dc:creator>Peter Hosey</dc:creator>
		<pubDate>Mon, 23 Jul 2007 17:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108689</guid>
		<description>Actually, I had resigned the problem yesterday, but came back to it while working on an application of my own that I'm going to release later today.</description>
		<content:encoded><![CDATA[<p>Actually, I had resigned the problem yesterday, but came back to it while working on an application of my own that I'm going to release later today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper</title>
		<link>http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108686</link>
		<dc:creator>Jesper</dc:creator>
		<pubDate>Mon, 23 Jul 2007 16:56:42 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108686</guid>
		<description>I feel I should add that 10.5 ("Leopard") will improve on this by adopting UTIs everywhere, but it doesn't mean you can add them to your existing apps because 10.4 will still fuck this up.

And Peter started looking into this because I was having trouble supporting a feature in an upcoming ThisService release, where you should be able to drag any script file to its dock icon to trigger opening it (but implementing the opening behavior as simply placing it in the script file picker). Right now, I think I'll either stick to one entry containing all extensions for common scripts (+ AppleScript's OS types) or to one catch-all entry (which would be bad since it'll show up in Open With in the Finder.

Command+Option is a clear workaround but I should be able to do this using just two UTIs, in my opinion: `com.apple.mach-o-binary` (for compiled UNIX pass-through filters) and `public.script` (underlying both AppleScripts and command-line style scripts like shell scripts and PHP/Perl/Ruby/Python/etc.).</description>
		<content:encoded><![CDATA[<p>I feel I should add that 10.5 ("Leopard") will improve on this by adopting UTIs everywhere, but it doesn't mean you can add them to your existing apps because 10.4 will still fuck this up.</p>
<p>And Peter started looking into this because I was having trouble supporting a feature in an upcoming ThisService release, where you should be able to drag any script file to its dock icon to trigger opening it (but implementing the opening behavior as simply placing it in the script file picker). Right now, I think I'll either stick to one entry containing all extensions for common scripts (+ AppleScript's OS types) or to one catch-all entry (which would be bad since it'll show up in Open With in the Finder.</p>
<p>Command+Option is a clear workaround but I should be able to do this using just two UTIs, in my opinion: `com.apple.mach-o-binary` (for compiled UNIX pass-through filters) and `public.script` (underlying both AppleScripts and command-line style scripts like shell scripts and PHP/Perl/Ruby/Python/etc.).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Hosey</title>
		<link>http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108678</link>
		<dc:creator>Peter Hosey</dc:creator>
		<pubDate>Mon, 23 Jul 2007 15:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108678</guid>
		<description>launch actually works in circumstances where mdls doesn't. For example, I performed the above example on a RAM disk. Here's what mdls says:

&lt;pre&gt;% mdls -name kMDItemContentType Foo.app
Foo.app -------------&lt;/pre&gt;

For those who haven't seen it before, here's the normal output, as determined by cding into my /Applications folder and mdlsing one of the applications there:

&lt;pre&gt;% mdls -name kMDItemContentType Adium.app
Adium.app -------------
kMDItemContentType = "com.apple.application-bundle"&lt;/pre&gt;

So mdls doesn't work on volumes without a Spotlight index. launch works anywhere.</description>
		<content:encoded><![CDATA[<p>launch actually works in circumstances where mdls doesn't. For example, I performed the above example on a RAM disk. Here's what mdls says:</p>
<pre>% mdls -name kMDItemContentType Foo.app
Foo.app -------------</pre>
<p>For those who haven't seen it before, here's the normal output, as determined by cding into my /Applications folder and mdlsing one of the applications there:</p>
<pre>% mdls -name kMDItemContentType Adium.app
Adium.app -------------
kMDItemContentType = "com.apple.application-bundle"</pre>
<p>So mdls doesn't work on volumes without a Spotlight index. launch works anywhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ssp</title>
		<link>http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108675</link>
		<dc:creator>ssp</dc:creator>
		<pubDate>Mon, 23 Jul 2007 15:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2007-07-23/how-to-make-your-apps-dock-tile-highlight#comment-108675</guid>
		<description>If it's not an application you are developing but just one you want to use, Command-Option dragging may help as well.

Perhaps just using the mdls command is an even easier way to learn a file's UTI, btw. 

'mdls -name kMDItemContentType PATHTOFILE'</description>
		<content:encoded><![CDATA[<p>If it's not an application you are developing but just one you want to use, Command-Option dragging may help as well.</p>
<p>Perhaps just using the mdls command is an even easier way to learn a file's UTI, btw. </p>
<p>'mdls -name kMDItemContentType PATHTOFILE'</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.197 seconds -->
