Comments on: Lightroom Plugin Development: Adding a URL Handler to a Lightroom Plugin http://regex.info/blog/2012-01-17/1926 Not a photo blog. A personal blog with photos. Wed, 23 May 2012 20:38:13 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Rob Cole http://regex.info/blog/2012-01-17/1926#comment-45992 Rob Cole Fri, 13 Apr 2012 13:47:51 +0000 http://regex.info/blog/2012-01-17/1926#comment-45992 For those wanting an example of a working plugin which uses a url handler: http://www.robcole.com/Rob/ProductsAndServices/CookmarksLrPlugin PS - I haven't had any problems using the links via IE - I'd be curious if anybody else has success or failure. Rob For those wanting an example of a working plugin which uses a url handler:

http://www.robcole.com/Rob/ProductsAndServices/CookmarksLrPlugin

PS – I haven’t had any problems using the links via IE – I’d be curious if anybody else has success or failure.

Rob

]]> By: Don McKee http://regex.info/blog/2012-01-17/1926#comment-45987 Don McKee Thu, 12 Apr 2012 23:01:59 +0000 http://regex.info/blog/2012-01-17/1926#comment-45987 Just to follow up for anyone else happening by, I've worked around the problems I was having with IE. I had been having the external site that I was authenticating with respond directly with my "lightroom://..." callback URL (via HTTP 302 redirect). IE didn't like this and displayed an error page. I discovered that IE <em>would</em> work correctly if I first directed it to a web page containing a "meta refresh" tag with my "lightroom://..." URL (or a user-clickable link). So, I changed things up to have the external site redirect to a web page on my site containing, among other stuff, one line of PHP script to dynamically build my Lightroom callback URL with the parameters passed from the external site. Discounting the fact that my plug-in is no longer completely self-contained, this workaround is sort of a Good Thing because my intermediate web page has verbiage and screen shots about dealing with the various application launch dialogs that may be encountered. -Don Just to follow up for anyone else happening by, I’ve worked around the problems I was having with IE. I had been having the external site that I was authenticating with respond directly with my “lightroom://…” callback URL (via HTTP 302 redirect). IE didn’t like this and displayed an error page.

I discovered that IE would work correctly if I first directed it to a web page containing a “meta refresh” tag with my “lightroom://…” URL (or a user-clickable link). So, I changed things up to have the external site redirect to a web page on my site containing, among other stuff, one line of PHP script to dynamically build my Lightroom callback URL with the parameters passed from the external site.

Discounting the fact that my plug-in is no longer completely self-contained, this workaround is sort of a Good Thing because my intermediate web page has verbiage and screen shots about dealing with the various application launch dialogs that may be encountered.

-Don

]]> By: Don McKee http://regex.info/blog/2012-01-17/1926#comment-45931 Don McKee Fri, 06 Apr 2012 17:11:02 +0000 http://regex.info/blog/2012-01-17/1926#comment-45931 Thanks for posting this how-to, Jeffrey! The process worked fine on my Win XP box running Firefox as my default browser. However, when I tried it with Internet Explorer 8, IE complained "Internet Explorer cannot display the webpage". Do you have any insight into how Lightroom defines itself as a handler for "lightroom://..." URLs so I can see about making this work across-the-board? Is this one of those "...rare OS/browser combinations" you're talking about (doesn't seem that rare to me, though ;-) )? Again, thanks a bunch for documenting this! -Don <span class='jfriedl'>Unfortunately, my "insight" in this area extends to "try reinstalling Lightroom, and I bet it'll work". I'd <i>think</i> it should work even after switching default browsers, but perhaps that requires a Lr reinstall. —Jeffrey</span> Thanks for posting this how-to, Jeffrey! The process worked fine on my Win XP box running Firefox as my default browser. However, when I tried it with Internet Explorer 8, IE complained “Internet Explorer cannot display the webpage”. Do you have any insight into how Lightroom defines itself as a handler for “lightroom://…” URLs so I can see about making this work across-the-board? Is this one of those “…rare OS/browser combinations” you’re talking about (doesn’t seem that rare to me, though ;-) )?

Again, thanks a bunch for documenting this!

-Don

Unfortunately, my “insight” in this area extends to “try reinstalling Lightroom, and I bet it’ll work”. I’d think it should work even after switching default browsers, but perhaps that requires a Lr reinstall. —Jeffrey

]]> By: Kyle http://regex.info/blog/2012-01-17/1926#comment-45151 Kyle Sat, 21 Jan 2012 05:08:13 +0000 http://regex.info/blog/2012-01-17/1926#comment-45151 This is the kind of thing that I wish Adobe would touch on/include in their SDK. Hopefully it's included in Lr4 SDK. It's a small thing, but makes things a <i>lot</i> easier for end users. Thanks, Jeffrey! This is the kind of thing that I wish Adobe would touch on/include in their SDK. Hopefully it’s included in Lr4 SDK.

It’s a small thing, but makes things a lot easier for end users.

Thanks, Jeffrey!

]]> By: Rob Cole http://regex.info/blog/2012-01-17/1926#comment-45137 Rob Cole Wed, 18 Jan 2012 22:29:07 +0000 http://regex.info/blog/2012-01-17/1926#comment-45137 Well, if you issue an http "get", then you can read a response. So, if a web-app issued a lightroom://... url, would it possible to know if the plugin is disabled, and hence the url fell on deaf ears? Would it be possible for a web-app to issue a lightroom url that requests a bunch of info from a plugin for use in the web-app? From SF, CA, USA <span class='jfriedl'>Ah, I see, sorry, I was looking at it from the wrong point of view. No, I don't see any way for the issuer of the <b>lightroom://</b> url to get any follow-on information (including even whether Lightroom is installed) without going through all kinds of hoops of passing something like a session ID one way, then waiting for a response on some other avenue agreed upon in advance by the issuer and the plugin. —Jeffrey</span> Well, if you issue an http “get”, then you can read a response. So, if a web-app issued a lightroom://… url, would it possible to know if the plugin is disabled, and hence the url fell on deaf ears? Would it be possible for a web-app to issue a lightroom url that requests a bunch of info from a plugin for use in the web-app?

From SF, CA, USA

Ah, I see, sorry, I was looking at it from the wrong point of view. No, I don’t see any way for the issuer of the lightroom:// url to get any follow-on information (including even whether Lightroom is installed) without going through all kinds of hoops of passing something like a session ID one way, then waiting for a response on some other avenue agreed upon in advance by the issuer and the plugin. —Jeffrey

]]> By: Rob Cole http://regex.info/blog/2012-01-17/1926#comment-45135 Rob Cole Wed, 18 Jan 2012 19:49:37 +0000 http://regex.info/blog/2012-01-17/1926#comment-45135 I take it this is for one-way communication only, right? i.e. no way for plugin to respond and have it be heard(?) <span class='jfriedl'>I'm not quite sure what you mean... a plugin can open dialogs, launch applications, and cause web pages to load, so that's one way to be heard... —Jeffrey</span> I take it this is for one-way communication only, right? i.e. no way for plugin to respond and have it be heard(?)

I’m not quite sure what you mean… a plugin can open dialogs, launch applications, and cause web pages to load, so that’s one way to be heard… —Jeffrey

]]> By: Matt Dawson http://regex.info/blog/2012-01-17/1926#comment-45130 Matt Dawson Wed, 18 Jan 2012 10:02:42 +0000 http://regex.info/blog/2012-01-17/1926#comment-45130 For those trying this out, you will need to check whether the URL supplied to your handler is surrounded in double quotes. I don't think it always is so its worth explicitly checking before you try to process the URL received. <span class='jfriedl'>Good point, Matt, thanks, I should have mentioned that. I'll go back and update the post to include it. —Jeffrey</span> For those trying this out, you will need to check whether the URL supplied to your handler is surrounded in double quotes. I don’t think it always is so its worth explicitly checking before you try to process the URL received.

Good point, Matt, thanks, I should have mentioned that. I’ll go back and update the post to include it. —Jeffrey

]]> By: Rob Cole http://regex.info/blog/2012-01-17/1926#comment-45120 Rob Cole Tue, 17 Jan 2012 08:37:44 +0000 http://regex.info/blog/2012-01-17/1926#comment-45120 Hot tip - many possibilities... Hot tip – many possibilities…

]]>