Isn't it easier to:
ShellExecute(NULL, "open", "http://scripting.net", NULL, NULL,
SW_SHOWNORMAL);
Just as on OS X I'd use [NSWorkspace openURL: ].
I'm just wondering, is there some other major use for DDE when Frontier is
interacting with the browser? (Frankly, this is the first time I heard
about DDE, but from what the book of knowledge says, it's similar to Apple
Events, right?)
On Sat, Jun 9, 2012 at 8:35 PM, Dave Winer <dave.wi...@gmail.com> wrote:
> When you choose Preferences or Tool Catalog from the Misc menu, we fire
> off a DDE message to the current browser.
> Apparently Chrome does not support this. That's why these commands don't
> work with Chrome on Windows.
The reason why DDE is easier is that al the other browsers work that way
and if Chrome did I would have to do *nothing* to make it work with the
OPML Editor. :-)
It's why we bother using standards whenever possible.
On Sat, Jun 9, 2012 at 2:55 PM, Ivan Vučica <ivuc...@gmail.com> wrote:
> You use DDE to open a web page?
> Isn't it easier to:
> ShellExecute(NULL, "open", "http://scripting.net", NULL, NULL,
> SW_SHOWNORMAL);
> Just as on OS X I'd use [NSWorkspace openURL: ].
> I'm just wondering, is there some other major use for DDE when Frontier is
> interacting with the browser? (Frankly, this is the first time I heard
> about DDE, but from what the book of knowledge says, it's similar to Apple
> Events, right?)
> On Sat, Jun 9, 2012 at 8:35 PM, Dave Winer <dave.wi...@gmail.com> wrote:
>> When you choose Preferences or Tool Catalog from the Misc menu, we fire
>> off a DDE message to the current browser.
>> Apparently Chrome does not support this. That's why these commands don't
>> work with Chrome on Windows.
Sorry, that's, of course, a line in C using a Win32 API for launching a
process. :-)
I agree that Chrome should definitely support it. But based on my
experience with them fixing reported bugs, you're probably looking at
several months of response time.
Simpler solutions are often better, and IPC of this kind may not be needed
here if ShellExecute() will do the trick.
> The reason why DDE is easier is that al the other browsers work that way
> and if Chrome did I would have to do *nothing* to make it work with the
> OPML Editor. :-)
> It's why we bother using standards whenever possible.
> Dave
> On Sat, Jun 9, 2012 at 2:55 PM, Ivan Vučica <ivuc...@gmail.com> wrote:
>> You use DDE to open a web page?
>> Isn't it easier to:
>> ShellExecute(NULL, "open", "http://scripting.net", NULL, NULL,
>> SW_SHOWNORMAL);
>> Just as on OS X I'd use [NSWorkspace openURL: ].
>> I'm just wondering, is there some other major use for DDE when Frontier
>> is interacting with the browser? (Frankly, this is the first time I heard
>> about DDE, but from what the book of knowledge says, it's similar to Apple
>> Events, right?)
>> On Sat, Jun 9, 2012 at 8:35 PM, Dave Winer <dave.wi...@gmail.com> wrote:
>>> When you choose Preferences or Tool Catalog from the Misc menu, we fire
>>> off a DDE message to the current browser.
>>> Apparently Chrome does not support this. That's why these commands don't
>>> work with Chrome on Windows.
On Sat, Jun 9, 2012 at 3:37 PM, Ivan Vučica <ivuc...@gmail.com> wrote:
> Sorry, that's, of course, a line in C using a Win32 API for launching a
> process. :-)
> I agree that Chrome should definitely support it. But based on my
> experience with them fixing reported bugs, you're probably looking at
> several months of response time.
> Simpler solutions are often better, and IPC of this kind may not be needed
> here if ShellExecute() will do the trick.
> On Sat, Jun 9, 2012 at 9:25 PM, Dave Winer <dave.wi...@gmail.com> wrote:
>> My memory is bad so I tried running your one-liner on the server.
>> The reason why DDE is easier is that al the other browsers work that way
>> and if Chrome did I would have to do *nothing* to make it work with the
>> OPML Editor. :-)
>> It's why we bother using standards whenever possible.
>> Dave
>> On Sat, Jun 9, 2012 at 2:55 PM, Ivan Vučica <ivuc...@gmail.com> wrote:
>>> You use DDE to open a web page?
>>> Isn't it easier to:
>>> ShellExecute(NULL, "open", "http://scripting.net", NULL, NULL,
>>> SW_SHOWNORMAL);
>>> Just as on OS X I'd use [NSWorkspace openURL: ].
>>> I'm just wondering, is there some other major use for DDE when Frontier
>>> is interacting with the browser? (Frankly, this is the first time I heard
>>> about DDE, but from what the book of knowledge says, it's similar to Apple
>>> Events, right?)
>>> On Sat, Jun 9, 2012 at 8:35 PM, Dave Winer <dave.wi...@gmail.com> wrote:
>>>> When you choose Preferences or Tool Catalog from the Misc menu, we fire
>>>> off a DDE message to the current browser.
>>>> Apparently Chrome does not support this. That's why these commands
>>>> don't work with Chrome on Windows.
> Isn't it easier to:
> ShellExecute(NULL, "open", "http://scripting.net", NULL, NULL,
> SW_SHOWNORMAL);
> Just as on OS X I'd use [NSWorkspace openURL: ].
> I'm just wondering, is there some other major use for DDE when Frontier is
> interacting with the browser? (Frankly, this is the first time I heard
> about DDE, but from what the book of knowledge says, it's similar to Apple
> Events, right?)
> On Sat, Jun 9, 2012 at 8:35 PM, Dave Winer <dave.wi...@gmail.com> wrote:
> > When you choose Preferences or Tool Catalog from the Misc menu, we fire
> > off a DDE message to the current browser.
> > Apparently Chrome does not support this. That's why these commands don't
> > work with Chrome on Windows.
> I think we now have a working connection betw the OPML Editor and
> Chrome on Windows. :-)
> Dave
> On Jun 9, 2:55 pm, Ivan Vučica <ivuc...@gmail.com> wrote:
>> You use DDE to open a web page?
>> Isn't it easier to:
>> ShellExecute(NULL, "open", "http://scripting.net", NULL, NULL,
>> SW_SHOWNORMAL);
>> Just as on OS X I'd use [NSWorkspace openURL: ].
>> I'm just wondering, is there some other major use for DDE when Frontier
>> is
>> interacting with the browser? (Frankly, this is the first time I heard
>> about DDE, but from what the book of knowledge says, it's similar to
>> Apple
>> Events, right?)
>> On Sat, Jun 9, 2012 at 8:35 PM, Dave Winer <dave.wi...@gmail.com> wrote:
>> > When you choose Preferences or Tool Catalog from the Misc menu, we fire
>> > off a DDE message to the current browser.
>> > Apparently Chrome does not support this. That's why these commands
>> > don't
>> > work with Chrome on Windows.
You don't need to create that temp file. Windows protocol handler will
execute a url directly in the default browser from ShellExecute. So all you
need is this:
> I think we now have a working connection betw the OPML Editor and
> Chrome on Windows. :-)
> Dave
> On Jun 9, 2:55 pm, Ivan Vučica <ivuc...@gmail.com> wrote:
> > You use DDE to open a web page?
> > Isn't it easier to:
> > ShellExecute(NULL, "open", "http://scripting.net", NULL, NULL,
> > SW_SHOWNORMAL);
> > Just as on OS X I'd use [NSWorkspace openURL: ].
> > I'm just wondering, is there some other major use for DDE when Frontier
> is
> > interacting with the browser? (Frankly, this is the first time I heard
> > about DDE, but from what the book of knowledge says, it's similar to
> Apple
> > Events, right?)
> > On Sat, Jun 9, 2012 at 8:35 PM, Dave Winer <dave.wi...@gmail.com> wrote:
> > > When you choose Preferences or Tool Catalog from the Misc menu, we fire
> > > off a DDE message to the current browser.
> > > Apparently Chrome does not support this. That's why these commands
> don't
> > > work with Chrome on Windows.
> You don't need to create that temp file. Windows protocol handler will
> execute a url directly in the default browser from ShellExecute. So all you
> need is this:
Updated parts, created an empty outline, did Add Link...
http://www.harvard.edu . Right-clicked and did Open in Browser. Firefox
opened fine to the correct url. Switched to Chrome as default browser and
did the same thing. Opened fine. (Windows 7)
> On Jun 11, 1:12 am, Dave Jones <sec...@gmail.com> wrote:
> > You don't need to create that temp file. Windows protocol handler will
> > execute a url directly in the default browser from ShellExecute. So all
> you
> > need is this:
On Monday, June 11, 2012 4:34:16 PM UTC-4, Dave Jones wrote:
> Updated parts, created an empty outline, did Add Link... > http://www.harvard.edu . Right-clicked and did Open in Browser. Firefox > opened fine to the correct url. Switched to Chrome as default browser and > did the same thing. Opened fine. (Windows 7)
> DJ
> On Mon, Jun 11, 2012 at 7:44 AM, Dave Winer <dave.wi...@gmail.com> wrote:
>> On Jun 11, 1:12 am, Dave Jones <sec...@gmail.com> wrote: >> > You don't need to create that temp file. Windows protocol handler will >> > execute a url directly in the default browser from ShellExecute. So all >> you >> > need is this:
> The second call works, per these suggestions, but it still tries to bring
> Firefox to the front.
> Thanks in advance for any help.
> Dave
> On Monday, June 11, 2012 4:34:16 PM UTC-4, Dave Jones wrote:
>> Updated parts, created an empty outline, did Add Link...
>> http://www.harvard.edu . Right-clicked and did Open in Browser.
>> Firefox opened fine to the correct url. Switched to Chrome as default
>> browser and did the same thing. Opened fine. (Windows 7)
>> DJ
>> On Mon, Jun 11, 2012 at 7:44 AM, Dave Winer <dave.wi...@gmail.com> wrote:
>>> On Jun 11, 1:12 am, Dave Jones <sec...@gmail.com> wrote:
>>> > You don't need to create that temp file. Windows protocol handler will
>>> > execute a url directly in the default browser from ShellExecute. So
>>> all you
>>> > need is this:
On Thu, Jul 12, 2012 at 2:28 PM, Dave Jones <sec...@gmail.com> wrote:
> Just running launch.application(opmlEditor.data.urls.toolCatalogPage)
> brings chrome to the front for me when i set it as my default browser.
> DJ
> On Thu, Jul 12, 2012 at 12:23 PM, Dave Winer <dave.wi...@gmail.com> wrote:
>> Dave, following up on this --
>> Is there a way to bring the default web browser to the front using the
>> same mechanism?
>> For example, in the Tool Catalog command, we do this:
>> The second call works, per these suggestions, but it still tries to bring
>> Firefox to the front.
>> Thanks in advance for any help.
>> Dave
>> On Monday, June 11, 2012 4:34:16 PM UTC-4, Dave Jones wrote:
>>> Updated parts, created an empty outline, did Add Link...
>>> http://www.harvard.edu . Right-clicked and did Open in Browser.
>>> Firefox opened fine to the correct url. Switched to Chrome as default
>>> browser and did the same thing. Opened fine. (Windows 7)
>>> DJ
>>> On Mon, Jun 11, 2012 at 7:44 AM, Dave Winer <dave.wi...@gmail.com>wrote:
>>>> On Jun 11, 1:12 am, Dave Jones <sec...@gmail.com> wrote:
>>>> > You don't need to create that temp file. Windows protocol handler
>>>> will
>>>> > execute a url directly in the default browser from ShellExecute. So
>>>> all you
>>>> > need is this:
