An open-source, web-based viewer for zoomable images, implemented in pure JavaScript.
avandecreme
This message was deleted
@avandecreme I could show you the problem on the website. The problem is, i can't offer a direct link yet so you have to do some clicks before: Steps to reproduce: 1) visit https://gp3.mpg.de 2) Search for "BA10" 3) Add the set to the cart/selection, 4) Click on selection in the menu 5) Click on the small image icon on the first image.
zoom
ok, so the issue is with the tiles in the borders, right?
@foobarable ^
I think you should make a simple example outside of angular. I can't see your source code right now.
@msalsbery I'd love event improvement contributions to svg-overlay as well!
@dwrogers OSD's built-in overlays don't scale their content as you zoom (giving the effect @sickrandir is looking for) whereas svg-overlay scales everything, so it's like the overlays are part of the image. The fabric overlay is good for interactive drawing as @altert says, and his canvas overlay would be probably the most low level, where you want fine control over every pixel drawn in your overlay
@msalsbery "grunt doc" was what I was looking for. Thanks!
@dwrogers Just keep in mind that it's in the site-build repository; if you're working with the openseadragon repository, you'll have to
grunt publish it into the site-build before doing grunt doc
Grunt responded: "Eh <crunch><crunch>.... Whats doc, doc."
Yup, if you did it in the openseadragon repository
Never mind. It's a different repo. Gotta read the whole message...
Just to verify: do you just want the docs for the latest release? If so, those are online. You only need to build if you are writing new docs and want to test them
@iangilman I need to learn how to use jsdocs so I can understand and contribute.
Cool, just making sure :)
One approach is to just edit openseadragon.js in site-build directly and experiment there
@msalsbery @altert @iangilman Thanks for the comments on the various overlays!
@msalsbery @altert @iangilman Thanks for the comments on the various overlays!
:)
@iangilman So would I... ;)
:P
:squirrel:
hmm that ZoomTo("OverlayId") seems like an nice function to have. It would need to be dependant on overlay size though, I guess?
referring to #838
@altert Absolutely
I think it would be more generally useful to be able to get the bounds of an overlay in viewport coordinates. You could then pass that directly into fitBounds or manipulate it somehow (like zooming out a little) before passing it
It looks like overlays already have a .bounds property (though it might be good to provide a
getBounds method), so I think the big piece that's missing is being able to get an overlay by passing its ID
Something like Viewer.getOverlayById(id)
yes, I've created such function in one application using fabricoverlay, to be able to get overlay and connected fabric objects by id
but that was external to osd, could be nice to have it inside it as well of course
Agreed! Would you be up for making a patch?
I'll experiment at least, and see where it's going)
Excellent :)
small question: as navigator is just somewhat specialized viewer, I guess making two syncronized (or kind of semi-syncronized, i.e. map and book) viewers shouldn't be too hard?
@altert Yes, that's exactly what the navigator is, for instance
(more or less)