Re: acrobat doesn't close
Thomas 'PointedEars' Lahn
> Thomas 'PointedEars' Lahn wrote:
>> Andrew Poulos wrote:
>>> Thomas 'PointedEars' Lahn wrote:
>>>> Andrew Poulos wrote:
>>>>> Is there a way to "force" acrobat reader to close?
>>>> Is there a way for you to post on-topic?
>>> Sorry I was kind of hoping there was something javascript could do to
>>> release whatever acrobat reader was holding onto.
>> You have not been thinking this through. If what you describe would be
>> generally possible with client-side HTML-UA-based scripting, any Web site
>> could close any application you are running, except if you had script
>> support disabled.
>
> I thought (wrongly) that as some HTML is causing the reader to launch
> then perhaps...
*The browser* is causing the reader (plugin) to launch. HTML is not a
programming language.
>> That Adobe Reader keeps running in the background is not a bug, it's a
>> feature. A bad one at that, but such happens frequently with monopolist's
>> software. Try Foxit Reader instead; it won't give you a plugin for Firefox
>> (yet), but it will also not keep system resources reserved when not needed.
>
> I have enough trouble with plugins without asking my users to install
> some small player's plugin (even though it may indeed be vastly superior
^^^^^^^^^^^^^^^^^^^^^^^^^^
> software).
Apparently you have not been paying attention. Foxit Reader is an
alternative free *PDF viewer*, and as I said, it does _not_ provide a plugin
_for Firefox_ yet, so it runs as a standalone application then. But there
is a plugin for IE that is considerably faster and less resource-consuming
than the Adobe Reader equivalent. (Therefore, on Windows you can use the
IE Tab extension for Firefox to trigger IE and its Foxit plugin with
/\.pdf$/ and the like.)
Anyhow, Foxit Reader exits when you don't need it anymore, while Adobe
Reader does not do that (as you have observed).
>> BTW, your markup is unnecessarily invalid. <http://validator.w3.org/>
>
> This is something I've been struggling with: do I strive for 100%
> standards compliance or should I take a more pragmatic approach. With
> some media I'm finding that going for a 100% standards compliant
> solution actually results in other issues that I've not been able to solve.
Trying to embed a PDF document in a Web document is a pointless exercise
anyway, as not everybody has or wants to use a PDF plugin. You will be much
better off setting a hyperlink to the PDF document instead, and properly
mark it as such.
X-Post & F'up2 comp.infosystems.www.authoring.misc
PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
-- Richard Cornford, cljs, <f806at$ail$1$8300...@news.demon.co.uk>