Loading Profile...
OpenZoom Nano Viewer Cannot Be Referenced from Central Location
How can I place the OpenZoomViewer.swf at an arbitrary point on my host? I notice in all of the documentation for OpenZoom Endo, you state to put the viewer in the same directory as the page. I'm currently developing a Ruby on Rails app that uses this viewer, and would like to put the viewer in a central directory, say /swf/OpenZoomViewer.swf or /assets/ or something. I changed the defaults[viewer] parameter in jquery.openzoom.js to be "/path/to/Viewer", and it gave the sad face. I then moved the viewer to the root of my webhost, and changed the defaults[viewer] to match ("/OpenZoomViewer.swf") and it worked. However, it only worked for Firefox and IE, not Safari or Chrome (both webkit browsers).
So, first, is there a supported way to put the viewer in a central location? Second, is there a way to override the defaults hash in jquery.openzoom.js without changing the source file? Preferrably, an option to the jQuery.openzoom.run(blah)?
Sorry for the long rambling, but I'm at my wit's end. For the record, your examples (with everything in the same folder) work on chrome and safari.
Thanks in advance,
Nathan
So, first, is there a supported way to put the viewer in a central location? Second, is there a way to override the defaults hash in jquery.openzoom.js without changing the source file? Preferrably, an option to the jQuery.openzoom.run(blah)?
Sorry for the long rambling, but I'm at my wit's end. For the record, your examples (with everything in the same folder) work on chrome and safari.
Thanks in advance,
Nathan
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has acknowledged this problem.
The best solution from the company
-
Derek,
I love your work & progess on this and the very educational videos you've produced! One suggestion I have is instead of defining new metadata on the image, I suggest extending the run method of the plugin and let users define the path to the viewer per page instead of per image.
Keep up the good work.
–Daniel
I’m happy
The company says
this solves the problem
-
Inappropriate?Nathan,
I am sorry you had to go through this and I can totally understand your frustration. You're right, I've never completely implemented the feature to centrally store the viewer and reference it by a path. I am not quite sure about the best way to go forward with this. Obviously, it's missing but frankly there's only so much time I have and I am currently working on features that will make many more people happy.
There are two ways we can handle this, either you stick with the recommended setup and store your viewer centrally or we could possibly coordinate a community effort to complete this feature.
What do you think?
–Daniel
I’m sorry
-
Inappropriate?Is the code in question in the fla file? If so, I'll dig into it and see what I can come up with. :) I can email or post any patches necessary. I'll be sure to pull the latest open-zoom-read-only from svn...
I’m confident
-
This reply was removed on 06/16/09.
see the change log -
Inappropriate?Nathan,
Thanks for giving this a spin! :)
Actually, there's no FLA file, it's all pure ActionScript. Be sure to get the latest revision from the OpenZoom repository and you'll find the viewer at
http://code.google.com/p/open-zoom/so...
Though I am not sure why the referencing doesn't work it's probably best to get started with the OpenZoom Endo jQuery plug-in:
http://code.google.com/p/open-zoom/so...
If you find out what's wrong, let me know and I'll try to fix it! :)
Thanks,
Daniel
I’m happy
-
Inappropriate?Ok, finally getting back to this. One question I have is this. If I do find the fix, how do I go about re-generating the OpenZoomViewer.swf file?
I’m undecided
-
Inappropriate?Nathan,
Awesome! For building the OpenZoom Nano viewer, I recomend you to download Adobe Flex Builder, get the latest OpenZoom Nano & OpenZoom SDK source code from GitHub, import the project and compile it:
OpenZoom Nano
http://github.com/openzoom/nano
OpenZoom SDK
http://github.com/openzoom/sdk
Let me know if you have further questions.
Cheers,
Daniel
-
Inappropriate?Hi, I am building an openzoom plugin for Chisimba, and did not realise that this was a limitation until I got here. Nathan, (or Daniel) is anyone working on this? If not, I can get someone in the Chisimba team to take a look at it. Would be very useful for building wrappers for use in other systems. -
Inappropriate?Derek,
No, I'm currently not working on it. As I've described in the following blog post, I've stepped back from active development for a while: http://gasi.ch/blog/joining-microsoft/
Nonetheless, if you decide to work on this and have any questions, I'm happy to help. If I remember correctly, one of the problems was that the path from the JS file has to be relative to the path of the HTML document in which it's included. As a first step it would be great to specify a path as an option when including the OpenZoom Endo jQuery plugin. I suggest you fork the project on GitHub:
http://github.com/openzoom/endo
Let me know if you have questions.
Cheers,
Daniel
I’m happy
-
Inappropriate?It was actually quite simple. With some help from one of the developers on the Chisimba mailing list, I managed the following hack:
Just change the openzoom run function as follows to add a viewer path to the image
appletFile = $(this).attr("openzoom:viewerpath") + "OpenZoomViewer.swf",
$.openzoom.run = function () {
$("img").each(function() {
var width = $(this).attr("width"),
height = $(this).attr("height"),
source = $(this).attr("openzoom:source"),
appletFile = $(this).attr("openzoom:viewerpath") + "OpenZoomViewer.swf",
alternate = "
That seems to do it. I will try testing it as a chisimba plugin now. But I am not really knowledgeable about git. So I will just leave it here for now in case someone comes looking for it.
P.S. I know nothing really about Javascript. The clue was given by [private information removed] on the Chisimba developer list. -
Inappropriate?sorry, some bits got chopped off...cannot seem to paste code into this interface. I will blog it tomorrow and send the link
-
Inappropriate?OK, not a perfect solution but blogged my solution at http://www.dkeats.com (permalink: http://tinyurl.com/nc5ust). You can download a modified version of the simple example there.
-
Inappropriate?Derek,
I love your work & progess on this and the very educational videos you've produced! One suggestion I have is instead of defining new metadata on the image, I suggest extending the run method of the plugin and let users define the path to the viewer per page instead of per image.
Keep up the good work.
–Daniel
I’m happy
The company says
this solves the problem
EMPLOYEE
