These are chat archives for openseadragon/openseadragon

25th
Feb 2016
foobarable
@foobarable
Feb 25 2016 07:24 UTC
@iangilman https://gist.github.com/foobarable/89b3317ed705b0ade756 This is the function that creates my options object for creating the osd viewer
foobarable
@foobarable
Feb 25 2016 07:31 UTC
@iangilman But I found a way collection mode works for me as well
Im just filling the gaps i have with default images
foobarable
@foobarable
Feb 25 2016 07:52 UTC
@sickrandir I was not able yet to look into your code. Will do next week probably
sickrandir
@sickrandir
Feb 25 2016 09:27 UTC
@foobarable no worries. I should tell you that at the moment I'm looking into another way. I just changed the definition of scope in the directive to avoid the creation of a separate scope, like this:
   restrict: "E",
   scope: false,
and now I have shared scope and so shared objects between the directive and the controller. Probably not the best, but it works for me for now.
@iangilman thank you for your pointer on MouseTracker, I made it work for mobile clicking.
@iangilman another question. How the setFullPage(true) function is supposed to work? I tried to set it on a viewer that has hardcoded sizes in px in style and the effect is just that the viewer disappear completely. It seems to be very very small and not spanning the whole page as I thought.
Antoine Vandecreme
@avandecreme
Feb 25 2016 14:19 UTC
@sickrandir it should work just like that. Is the full screen mode working? (full screen is using full page)
sickrandir
@sickrandir
Feb 25 2016 14:29 UTC
@avandecreme full screen it's working
can you point me to an example of full page in action so I'll check if I'm missing something obvious?
@sickrandir ^
sickrandir
@sickrandir
Feb 25 2016 15:33 UTC
thank you. it's quite straightforward. but it's not working for me. Maybe that has something to do with the angularjs wrapper. I'll look into it. Fullscreen however it's working as expected.
@avandecreme is there any way to make the osd area fully responsive?
Antoine Vandecreme
@avandecreme
Feb 25 2016 15:44 UTC
do you mean have it size adjust depending on the available space?
sickrandir
@sickrandir
Feb 25 2016 15:56 UTC
yes
Ian Gilman
@iangilman
Feb 25 2016 17:16 UTC
@foobarable In order to get the x and y to work you need to do it like this:
var tilesource = {
    x: 2 * i,
    y: 0,
    tileSource: {
        type: "zoomifytileservice",
        width: images[i].dimx,
        height: images[i].dimy,
        tileSize: 256,
        tilesUrl: images[i].zoom        
    }
};
i.e. the positioning info needs to be outside of the tileSource definition
@sickrandir To make the viewer responsive you just need to style its contain div so it resizes with the page; the viewer will automatically resize itself to fill as needed
Grant Echols
@gechols
Feb 25 2016 17:18 UTC
@iangilman - I have my overlay drawing example updated and running on https://familysearch.org/reference/frontier/controls/OpenSDPOJO. There's a bit of debug information displaying in the javascript console. To get the multi-image issue running you need to copy/paste the list of URLs in the page into the entry field before hitting 'open' button.
https://familysearch.org/reference/frontier/controls/OpenSDPOJO?debug=true would probably be better as the code loads uncompressed this way
Ian Gilman
@iangilman
Feb 25 2016 17:19 UTC
Cool...once I have it opened with those images, what do I do next?
Grant Echols
@gechols
Feb 25 2016 17:20 UTC
'turn on' the overlay drawing - the image gets a yellow translucent layer. You can then 'draw' overlays on the image using the mouse. You can turn off the overlay drawing after you've drawn an overlay and navigate to the next image
That's when we lose the overlay because we get a position that doesn't make sense
Ian Gilman
@iangilman
Feb 25 2016 17:22 UTC
Got it
If I wanted to look at the viewer in the console, what variable do I find it in?
Grant Echols
@gechols
Feb 25 2016 17:23 UTC
I figured you'd want something like that. I should have done my homework. let me poke around and see where we have it burried. I know its available...hang on
Ian Gilman
@iangilman
Feb 25 2016 17:24 UTC
Btw, I'm using the arrow buttons in the top strip of the viewer to go to the next image...is that the right thing? It seems the effect is to replace the previous image with the new one, rather than panning/zooming to the new one. If that's the effect you're trying to achieve, maybe you should stack the images on top of each other instead of laying them out in space?
Alexey Tikhonov
@altert
Feb 25 2016 17:27 UTC
heh. Spend quite some time to battle legacytiles caching, due to filtering out images with parameters, solved it using mime type, then wrote an issue suggesting regex change, and only after all that found that it's already fixed in latest version. btw, thanks @gechols )
Ian Gilman
@iangilman
Feb 25 2016 17:29 UTC
I suppose it might be time to start thinking about another official release
Alexey Tikhonov
@altert
Feb 25 2016 17:30 UTC
btw I think that OpenSeadragonImagingHelper will get broken by it
Ian Gilman
@iangilman
Feb 25 2016 17:31 UTC
By the regex change?
Alexey Tikhonov
@altert
Feb 25 2016 17:31 UTC
no, I mena by latest version of OSD
it uses Viewport.contentSize
Ian Gilman
@iangilman
Feb 25 2016 17:31 UTC
Gotcha
Grant Echols
@gechols
Feb 25 2016 17:35 UTC
The arrow buttons effectively pan the image in. If you hit the grid button (it looks like a bunch of boxes in the 'zoomer') it switches to view the 'world' as we have it arranged. All we really do is make the other images 'hidden' and set the viewer bounds to focus on the individual image. My belief is that we are just setting the viewer bounds to the 'next' or 'previous' image and then OSD kicks in and loads the image into the viewport.
Ian Gilman
@iangilman
Feb 25 2016 17:40 UTC
@altert msalsbery/OpenSeadragonImagingHelper#9
@gechols Fair enough...having the grid button makes laying them out in space make sense
...though of course you could still stack them while in "one up" mode and then rearrange them when you go to "grid"
If you do that though, make sure you get the latest from master, because of #859
Anyway, I'm sure we can sort out the overlay issue
Grant Echols
@gechols
Feb 25 2016 17:42 UTC
I'm deploying a new version of the code that will have window.osdViewer set for you to get to the viewer you need to see
Ian Gilman
@iangilman
Feb 25 2016 17:42 UTC
Thank you!
Grant Echols
@gechols
Feb 25 2016 17:43 UTC
Its just a few minutes until the build server finishes
Ian Gilman
@iangilman
Feb 25 2016 17:43 UTC
Cool, just let me know
Grant Echols
@gechols
Feb 25 2016 17:59 UTC
@iangilman You should be able to open the image list and then the window.osdViewer variable will be set
Antoine Vandecreme
@avandecreme
Feb 25 2016 18:13 UTC
Regarding the next release, I would like to fix the overlays rotation before it. It might take some time though. There is that too: https://github.com/openseadragon/openseadragon/milestones/2.1.1
only #555 seems important in that list though
Ian Gilman
@iangilman
Feb 25 2016 18:26 UTC
@gechols Responded in a private channel
@avandecreme Good point...I'll update the list
What's the issue number for overlay rotation?
Also I'm going to bump it up to 2.2.0 because of the breaking changes (even though they're minor)
Antoine Vandecreme
@avandecreme
Feb 25 2016 18:35 UTC
agree for 2.2.0
#852 for rotation (among other duplicates)
Ian Gilman
@iangilman
Feb 25 2016 18:46 UTC
Cool, I'll add it :)