These are chat archives for openseadragon/openseadragon

9th
Aug 2016
Flexflexible
@Flexflexible_twitter
Aug 09 2016 06:25

@iangilman The zooming works for me. Its just that the images were really small that I used for testing.
I updated the files so that the flipbook now loads huge .dzi files (~40mb as a png each). Need to improve the performance later on, flipbook loads 3-4 images at the same time. This means that when I zoom in, it loads the tiles for 3-4 images which results in huge lags.

Working on the zoom effect atm. Like I already said I'm really new to javascript and jquery. Right now I simply enhance the width on mouseWheelEvent. Going to make this more smooth in the next step.

VoidVolker
@VoidVolker
Aug 09 2016 06:42
@Flexflexible_twitter you do wrong things, just slice your big image to small tiles 256x256 and then you'll have good result with isd
*osd
Chris Engberg
@chris-engberg
Aug 09 2016 07:35
blob
@VoidVolker : They are doing that. @Flexflexible_twitter Part of the performance problem is the fact that Flipbook is creating canvases that are massive on its own zooming, and four of them as you said. The beauty of OSD is that it never makes a canvas other then it designated size, zooming just loads diffferent resources. OSD in flipbook is doing that properly, but flipbook is increasing the page size, thus increasing the canvas, well outside of the scope of your current window.
VoidVolker
@VoidVolker
Aug 09 2016 07:44
also, canvas can be only maximum ~32700 pixels size (because for it size is used 2 bytes signed vars)
Ian Gilman
@iangilman
Aug 09 2016 16:32
@Flexflexible_twitter One thing you could do is not open the images from other pages until the user flips to them
... but yes, as @chris-engberg says, to really get the performance right, you'll need to somehow coordinate between your zoom and the OSD zoom so OSD is only loading the pixels you actually need
Otherwise, if the OSD canvas is gigantic, you're not really getting the benefit of OSD