Paul,
I don't know if I can explain exactly what is going on, but basically, I
believe that 'javascript:' is registered to the windows shell as a URL
prefix, so it sends the entire string to a browser. Once the browser
receives the string, it recognizes it as script to be executed. 'window' is
a first class javascript object that refers to the browser window, and it
has a method called 'navigate' that takes one argument, a URL.
Alas, I just tried invoking two consecutive browse-urls with the javascript:
URL and unfortunately they opened two browser windows. So, for now it looks
like we're back to the temp HTML file with the <META HTTP-EQUIV="refresh"
... > tag solution that Don pointed out.
/Nick
-----Original Message-----
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 07, 2001 10:22 AM
To: Nick Sieger; 'Javier Lopez'; '[EMAIL PROTECTED]'
Subject: RE: Browsing to an anchor
At 10:01 AM 8/7/2001 -0500, Nick Sieger wrote:
>How about this - I just tried
>
>M-x browse-url
>javascript:window.navigate("file:///C:/java/jdk1.3.1/docs/api/java/lang/Str
i
>ng.html#hashCode()")
>
>and it worked. Don't know if it will work with Netscape/Mozilla, though
>(don't have it installed) - can anyone confirm?
>
Hi Nick,
Great! Care to explain what is going on with your solution? It's totally
mysterious to me. I'm fairly confident that (browse-url filename) should
work on other platforms. So if your solution works for Windows, all I need
to do is include it as a special calse. Then I can finish my extension of
API help from the class to the method and field level.
- Paul
