<?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: Adobe InDesign CS3 5.0.3 Updater: Why does it require me to quit Safari?</title>
	<atom:link href="http://www.betalogue.com/2008/07/10/indesign-503-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.betalogue.com/2008/07/10/indesign-503-update/</link>
	<description>Notes from an unfinished world…</description>
	<lastBuildDate>Mon, 06 Feb 2012 13:29:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: helge</title>
		<link>http://www.betalogue.com/2008/07/10/indesign-503-update/comment-page-1/#comment-8386</link>
		<dc:creator>helge</dc:creator>
		<pubDate>Fri, 08 Aug 2008 19:28:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/?p=2389#comment-8386</guid>
		<description>Even if the InDesign update would really update the Adobe PDF plugin, it wouldn&#039;t make sense to quit Camino, because Adobe&#039;s PDF plugin is only compatible with Safari. 
That, of course, makes a lot of sense, because Safari does already come with full PDF support and all the other browsers do not. Oh wait, maybe it does not make any sense at all...</description>
		<content:encoded><![CDATA[<p>Even if the InDesign update would really update the Adobe PDF plugin, it wouldn&#8217;t make sense to quit Camino, because Adobe&#8217;s PDF plugin is only compatible with Safari.<br />
That, of course, makes a lot of sense, because Safari does already come with full PDF support and all the other browsers do not. Oh wait, maybe it does not make any sense at all&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2008/07/10/indesign-503-update/comment-page-1/#comment-8359</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Fri, 11 Jul 2008 20:45:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/?p=2389#comment-8359</guid>
		<description>Arden: Indeed I would very much like not having to remember to option-click on PDF files on web sites. And I have Default Apps on my machine. Where do I go in Default Apps to tell it to treat PDFs as Preview files automatically? It&#039;s far from clear in the Default Apps interface. I already have Preview for .PDF and .pdf extensions and for the application/pdf MIME type. What else do I need to change to achieve this behaviour?</description>
		<content:encoded><![CDATA[<p>Arden: Indeed I would very much like not having to remember to option-click on PDF files on web sites. And I have Default Apps on my machine. Where do I go in Default Apps to tell it to treat PDFs as Preview files automatically? It&#8217;s far from clear in the Default Apps interface. I already have Preview for .PDF and .pdf extensions and for the application/pdf MIME type. What else do I need to change to achieve this behaviour?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arden</title>
		<link>http://www.betalogue.com/2008/07/10/indesign-503-update/comment-page-1/#comment-8358</link>
		<dc:creator>Arden</dc:creator>
		<pubDate>Fri, 11 Jul 2008 18:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/?p=2389#comment-8358</guid>
		<description>&lt;blockquote&gt;Personally, I prefer to download PDF files separately and to open them in Preview. So I removed the Adobe PDF plug-in from my “Internet Plug-Ins” folder a long time ago, and typically I option-click on links to PDF documents to force Safari to download them as files instead of displaying them in the browser window.&lt;/blockquote&gt;

Same here... except I use Default Apps to tell the system to treat PDF&#039;s as Preview files and download them automatically, instead of having to option-click them every time. It means I don&#039;t even have to think about whether it&#039;s a PDF or not, which sounds like something you would advocate.

&lt;blockquote&gt;Who knows, maybe the Adobe updater wants to supply the browsers with code that will enable you to do a much more satisfactory job at copying complex text from those browsers and pasting that information with formatting into InDesign?&lt;/blockquote&gt;

Considering how mediocrely-at-best they actually accomplish this, I wouldn&#039;t count on it.

&lt;blockquote&gt;I’m VERY much in favor of manufacturers informing us better about what’s being installed. On the other hand, I can imagine the headaches of providing detailed information about, say, new “copy-and-paste translators” being added for browsers when InDesign is updated, if I’ve guessed correctly. Most people won’t have a clue what the technical information means, and most won’t care. There will be compulsive tekkies who will demand further information, or the capability of micromanaging the update process. That leaves a very small number of users who will actually get something useful from being informed and won’t generally cause further headaches for the manufacturers.&lt;/blockquote&gt;

I disagree. I believe it is the developers&#039; responsibility to keep track of every change they make between releases and to inform us the users of these changes. Plenty of much smaller developers than Adobe have gotten this down to an art form, listing each change made to the product in plain English (usually). Whether or not a consumer understands exactly what each change means, he will understand that, say, in your example, something has changed with copy-and-paste behavior and some improvement in its functionality may be expectable. But I think anybody who actually bothers to read the changelog will get plenty of benefit out of it, and it&#039;s the developer&#039;s headache to bear.</description>
		<content:encoded><![CDATA[<blockquote><p>Personally, I prefer to download PDF files separately and to open them in Preview. So I removed the Adobe PDF plug-in from my “Internet Plug-Ins” folder a long time ago, and typically I option-click on links to PDF documents to force Safari to download them as files instead of displaying them in the browser window.</p></blockquote>
<p>Same here&#8230; except I use Default Apps to tell the system to treat PDF&#8217;s as Preview files and download them automatically, instead of having to option-click them every time. It means I don&#8217;t even have to think about whether it&#8217;s a PDF or not, which sounds like something you would advocate.</p>
<blockquote><p>Who knows, maybe the Adobe updater wants to supply the browsers with code that will enable you to do a much more satisfactory job at copying complex text from those browsers and pasting that information with formatting into InDesign?</p></blockquote>
<p>Considering how mediocrely-at-best they actually accomplish this, I wouldn&#8217;t count on it.</p>
<blockquote><p>I’m VERY much in favor of manufacturers informing us better about what’s being installed. On the other hand, I can imagine the headaches of providing detailed information about, say, new “copy-and-paste translators” being added for browsers when InDesign is updated, if I’ve guessed correctly. Most people won’t have a clue what the technical information means, and most won’t care. There will be compulsive tekkies who will demand further information, or the capability of micromanaging the update process. That leaves a very small number of users who will actually get something useful from being informed and won’t generally cause further headaches for the manufacturers.</p></blockquote>
<p>I disagree. I believe it is the developers&#8217; responsibility to keep track of every change they make between releases and to inform us the users of these changes. Plenty of much smaller developers than Adobe have gotten this down to an art form, listing each change made to the product in plain English (usually). Whether or not a consumer understands exactly what each change means, he will understand that, say, in your example, something has changed with copy-and-paste behavior and some improvement in its functionality may be expectable. But I think anybody who actually bothers to read the changelog will get plenty of benefit out of it, and it&#8217;s the developer&#8217;s headache to bear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2008/07/10/indesign-503-update/comment-page-1/#comment-8357</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Fri, 11 Jul 2008 01:44:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/?p=2389#comment-8357</guid>
		<description>I could probably get by with a Photoshop alternative if I really had to, but I am not aware of any other software that lets me put together 300-page print-ready publications with the &quot;smart document&quot; features that InDesign provides. Sure, it has tons of features that I don&#039;t use, but it does have vital features that I use and that I could not do without in my work. (Well, I suppose I theoretically could waste countless hours trying to reproduce these features using other, less appropriate tools, but it would be rather masochistic of me.)</description>
		<content:encoded><![CDATA[<p>I could probably get by with a Photoshop alternative if I really had to, but I am not aware of any other software that lets me put together 300-page print-ready publications with the &#8220;smart document&#8221; features that InDesign provides. Sure, it has tons of features that I don&#8217;t use, but it does have vital features that I use and that I could not do without in my work. (Well, I suppose I theoretically could waste countless hours trying to reproduce these features using other, less appropriate tools, but it would be rather masochistic of me.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: skellener</title>
		<link>http://www.betalogue.com/2008/07/10/indesign-503-update/comment-page-1/#comment-8356</link>
		<dc:creator>skellener</dc:creator>
		<pubDate>Thu, 10 Jul 2008 23:05:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/?p=2389#comment-8356</guid>
		<description>Dude, you are preaching to the choir.  Adobe software expensive, bloated, buggy and slow.  I refuse to clog my brand new iMac with any Adobe software. There is tons of much better, smaller, native apps out there for Mac OS X.  MS has been irrelevant on the Mac for about a decade, now it&#039;s Adobe&#039;s turn.  They refuse to embrace anything Apple has done over the last decade with OS X.  Their days are numbered.  The jurassic age of Adobe is over. Their as dead as the dinosaurs.</description>
		<content:encoded><![CDATA[<p>Dude, you are preaching to the choir.  Adobe software expensive, bloated, buggy and slow.  I refuse to clog my brand new iMac with any Adobe software. There is tons of much better, smaller, native apps out there for Mac OS X.  MS has been irrelevant on the Mac for about a decade, now it&#8217;s Adobe&#8217;s turn.  They refuse to embrace anything Apple has done over the last decade with OS X.  Their days are numbered.  The jurassic age of Adobe is over. Their as dead as the dinosaurs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2008/07/10/indesign-503-update/comment-page-1/#comment-8353</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Thu, 10 Jul 2008 19:08:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/?p=2389#comment-8353</guid>
		<description>I have nothing against the requirement to enter an administrator&#039;s password per se. What bothers me is that the Adobe updater asks for it in a generic dialog box before anything else—whereas the regular OS X installer asks for it at a later stage, with more of a context indicating why the password is required. Adobe&#039;s approach is the equivalent of saying: &quot;Before going any further, I want your password. Don&#039;t ask me why. It is just so. Trust me.&quot;

As for the requirement to quit all browsers, I simply do not see how it is justified. Even if InDesign makes use of some parts of WebKit, the engine behind Safari, this does not justify having to quit Safari in order to update InDesign. I highly doubt that Adobe can interfere in any way with the way non-Adobe applications use the Clipboard! If they did, why would they limit the &quot;shutdown&quot; requirement only to browsers? They should ask the user to quit all applications!

No, the only &quot;reasonable&quot; explanation here is that lazy Adobe developers have an installer script that requires the user to quit all browsers for any application update, regardless of whether it is actually necessary or not.</description>
		<content:encoded><![CDATA[<p>I have nothing against the requirement to enter an administrator&#8217;s password per se. What bothers me is that the Adobe updater asks for it in a generic dialog box before anything else—whereas the regular OS X installer asks for it at a later stage, with more of a context indicating why the password is required. Adobe&#8217;s approach is the equivalent of saying: &#8220;Before going any further, I want your password. Don&#8217;t ask me why. It is just so. Trust me.&#8221;</p>
<p>As for the requirement to quit all browsers, I simply do not see how it is justified. Even if InDesign makes use of some parts of WebKit, the engine behind Safari, this does not justify having to quit Safari in order to update InDesign. I highly doubt that Adobe can interfere in any way with the way non-Adobe applications use the Clipboard! If they did, why would they limit the &#8220;shutdown&#8221; requirement only to browsers? They should ask the user to quit all applications!</p>
<p>No, the only &#8220;reasonable&#8221; explanation here is that lazy Adobe developers have an installer script that requires the user to quit all browsers for any application update, regardless of whether it is actually necessary or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: henryn</title>
		<link>http://www.betalogue.com/2008/07/10/indesign-503-update/comment-page-1/#comment-8352</link>
		<dc:creator>henryn</dc:creator>
		<pubDate>Thu, 10 Jul 2008 18:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/?p=2389#comment-8352</guid>
		<description>The necessity to enter an administrator password is designed-in by Apple and is a quite reasonable control/security  measure -- for Macs that are intentionally shared or might be accessed and abused by, say, a teenager.  On Macs in completely controlled or trusted environments, Apple might consider providing an option to relax that requirement. But doing so isn&#039;t really essential, in my opinion, and is another opportunity for breaches of machines that need more security.

It DOES seem unreasonable to shut down all (?) browsers when doing an InDesign update.   It may be reasonable, considering the amount of inter-application processing that may be going on behind the scenes.  

Here&#039;s a somewhat related example:  The clipboard &quot;just works&quot; in general, and I&#039;ve noticed it has worked better in recent years -- at the task of transferring information among very different applications, exactly what it is supposed to do  What enables this is that copying in app &#039;A&#039; puts a surprising number of differently-formatted copies of the selected items &quot;on&quot; the clipboard.  So when you try to paste in app &#039;B&#039; you have an increasingly better chance of getting what you expect pasted in.    To do this requires a lot cooperation among manufacturers.  

Who knows, maybe the Adobe updater wants to supply the browsers with code that will enable you to do a much more satisfactory job at copying complex text from those browsers and pasting that information with formatting into InDesign?

I&#039;m VERY much in favor of manufacturers informing us better about what&#039;s being installed.  On the other hand, I can imagine the headaches of providing detailed information about, say, new &quot;copy-and-paste translators&quot; being added for browsers when InDesign is updated, if I&#039;ve guessed correctly.   Most people won&#039;t have a clue what the technical information means, and most won&#039;t care.   There will be compulsive tekkies who will demand further information, or the capability of micromanaging the update process. That leaves a very small number of users who will actually get something useful from being informed and won&#039;t generally cause further headaches for the manufacturers.

Full disclosure: I&#039;ve been trying to get a bug fixed in an Adobe application that&#039;s been reported for several years now. I&#039;ve even got an inside contact ... but no progress despite 7 months of on-and-off correspondence wotj.   When I think about the kind of excellent response I generally get from small companies and even free-ware writers...   

I think are absolutely right that large software companies can become bloated and insensitive.  I&#039;m very worried about the continuing trend towards oligopoly in the industry.  Doctrine says that competition ensures sensitivity to customer needs.  Hmmm... 

That said, I try to decide for each given issue is if the the problem can be attributed to that trend, or it&#039;s just due some numb-brained individual inside who made a stupid choice.  

Henry</description>
		<content:encoded><![CDATA[<p>The necessity to enter an administrator password is designed-in by Apple and is a quite reasonable control/security  measure &#8212; for Macs that are intentionally shared or might be accessed and abused by, say, a teenager.  On Macs in completely controlled or trusted environments, Apple might consider providing an option to relax that requirement. But doing so isn&#8217;t really essential, in my opinion, and is another opportunity for breaches of machines that need more security.</p>
<p>It DOES seem unreasonable to shut down all (?) browsers when doing an InDesign update.   It may be reasonable, considering the amount of inter-application processing that may be going on behind the scenes.  </p>
<p>Here&#8217;s a somewhat related example:  The clipboard &#8220;just works&#8221; in general, and I&#8217;ve noticed it has worked better in recent years &#8212; at the task of transferring information among very different applications, exactly what it is supposed to do  What enables this is that copying in app &#8216;A&#8217; puts a surprising number of differently-formatted copies of the selected items &#8220;on&#8221; the clipboard.  So when you try to paste in app &#8216;B&#8217; you have an increasingly better chance of getting what you expect pasted in.    To do this requires a lot cooperation among manufacturers.  </p>
<p>Who knows, maybe the Adobe updater wants to supply the browsers with code that will enable you to do a much more satisfactory job at copying complex text from those browsers and pasting that information with formatting into InDesign?</p>
<p>I&#8217;m VERY much in favor of manufacturers informing us better about what&#8217;s being installed.  On the other hand, I can imagine the headaches of providing detailed information about, say, new &#8220;copy-and-paste translators&#8221; being added for browsers when InDesign is updated, if I&#8217;ve guessed correctly.   Most people won&#8217;t have a clue what the technical information means, and most won&#8217;t care.   There will be compulsive tekkies who will demand further information, or the capability of micromanaging the update process. That leaves a very small number of users who will actually get something useful from being informed and won&#8217;t generally cause further headaches for the manufacturers.</p>
<p>Full disclosure: I&#8217;ve been trying to get a bug fixed in an Adobe application that&#8217;s been reported for several years now. I&#8217;ve even got an inside contact &#8230; but no progress despite 7 months of on-and-off correspondence wotj.   When I think about the kind of excellent response I generally get from small companies and even free-ware writers&#8230;   </p>
<p>I think are absolutely right that large software companies can become bloated and insensitive.  I&#8217;m very worried about the continuing trend towards oligopoly in the industry.  Doctrine says that competition ensures sensitivity to customer needs.  Hmmm&#8230; </p>
<p>That said, I try to decide for each given issue is if the the problem can be attributed to that trend, or it&#8217;s just due some numb-brained individual inside who made a stupid choice.  </p>
<p>Henry</p>
]]></content:encoded>
	</item>
</channel>
</rss>

