Aseem Kishore's dashboard

Aseem Kishore set one of Aseem Kishore's replies as an official response to "Seadragon to visualize office documents?" in Microsoft Live Labs

Aseem Kishore replied on November 20, 2009 18:57 to the idea "Seadragon to visualize office documents?" in Microsoft Live Labs:

I think the idea of being able to give Seadragon.com your documents is a great one. It's on our list of possible future directions.

For the time being, you do have to convert them to images first. If you put those images on the web, you can import them into Seadragon.com.

Aseem Kishore replied on November 19, 2009 05:01 to the idea "How can I add several pictures once?" in Microsoft Live Labs:

We'd definitely love to easily enable that kind of scenario, though. Thanks for your feedback -- we're listening!

Aseem Kishore replied on November 17, 2009 07:30 to the update "Seadragon.com: Flickr, Developer & Showcase" in Microsoft Live Labs:

Big props to Daniel -- the Flickr work was all him, as part of his internship here on the Seadragon team. Great work, Daniel!

To add on a couple of points to the above:

Snapdragon was indeed mentioned in a CNET article today! And while it wasn't mentioned in the Live Labs blog, it was in our unofficial Dragonosticism blog.

As for updating the Chris Jordan showcase to be more mobile-friendly, maybe at some point in the future, but for now that's fairly low priority. It's tough because mobile solutions have to be tailored at the application level and can't be fully solved at the platform level, so we're forced to go about it on a case-by-case basis.

Glad you like the changes though! I'm happy that we're expanding Seadragon.com the way we are. Look for more in the future.

Aseem Kishore set one of Aseem Kishore's replies as an official response to "title and description for image in seadragon" in Microsoft Live Labs

Aseem Kishore replied on November 17, 2009 07:19 to the idea "title and description for image in seadragon" in Microsoft Live Labs:

Tof,

We took your idea and applied it for Flickr images! When you give us a Flickr image now, our page title includes the title of the Flickr image.

So thanks for the suggestion! As Daniel said, we're looking at ways to derive this automatically for other images as well.

Aseem Kishore replied on November 17, 2009 07:17 to the idea "Hosting seadragon images on my own server" in Microsoft Live Labs:

And if you want to automate any of it, DeepZoomTools.dll might be perfect for you! It's in fact what Deep Zoom Composer uses under the hood. (As well as Seadragon.com!)

http://seadragon.com/developer/creati...

Aseem Kishore replied on November 17, 2009 07:15 to the update "Seadragon Ajax updated to 0.8.4!" in Microsoft Live Labs:

No updates yet. It's a tough problem to fix at the platform level and still allow the flexibility of zooming that we have currently. But we have some ideas that we'll hopefully get a chance to play with pretty soon!

Aseem Kishore replied on November 17, 2009 07:06 to the question "How to disable panning beyond the image boundaries?" in Microsoft Live Labs:

When you pan, we still do let you move the image/viewport until you let go of the mouse. That is indeed the default behavior; it feels more direct of a mapping to physical behavior.

What you're talking about with the aligning/pushing towards the margin is exactly what I meant with "flip-flop"; it'll keep aligning to the left or right margin, alternating, instead of staying centered. The quick fix I recommended was to disallow zooming out past home. You can do this by setting Config.minZoomImageRatio to 1. That should work; does it not?

Aseem Kishore started following the update "Seadragon.com: Flickr, Developer & Showcase" in Microsoft Live Labs.

Aseem Kishore replied on November 13, 2009 16:19 to the question "How to disable panning beyond the image boundaries?" in Microsoft Live Labs:

Yes, it's very easy -- just set Seadragon.Config.visibilityRatio to 1! That means that the entire viewer must be filled with image content at all times.

But a couple of things to keep in mind:

One is that we have a known issue where having a visibilityRatio > 0.5 can cause the image to switch back and forth if the image is zoomed out too far (such that the ratio of image to viewer is less than visibilityRatio).

So in your case, if you go with visibilityRatio of 1, you should also set minZoomImageRatio to 1 as well. This way, the image won't be able to zoom out beyond home, and you (hopefully) shouldn't run into the flip-flop behavior.

The second is that we haven't really tested much with a non-default visibilityRatio, so we apologize in advance if something doesn't work right. Do let us know if you run into any problems, and we'll try our best to help.

Aseem Kishore replied on November 08, 2009 03:37 to the idea "Gallery buttons (prev/next) or thumbnails visible in full-page mode" in Microsoft Live Labs:

That's a really good idea. We'll consider this when we have some time and resources to devote. Thanks!

Aseem Kishore replied on November 06, 2009 05:14 to the problem "Chrome support?" in Microsoft Live Labs:

Thanks for reporting this. Are you running Chrome 4? We don't see this in Chrome 3 (the officially public one currently), but we heard of the same bug from a fellow team member running Chrome 4.

Aseem Kishore replied on November 04, 2009 16:40 to the praise "I'm quite excited" in Microsoft Live Labs:

That's great to hear. We'd love to check it out, so feel free to share a link here when you're ready!

Aseem Kishore replied on November 04, 2009 00:51 to the update "Seadragon Ajax updated to 0.8.4!" in Microsoft Live Labs:

Both the documentation and the script include are referenced by just the first two numbers, i.e. 0.8. The idea is that:

0 - platform version, i.e. incremented for major architectural changes
8 - major version, i.e. incremented for breaking API changes
4 - minor version, silently incremented for bugfixes and non-breaking new features

So if you're using the script via:


<script src="http://seadragon.com/ajax/0.8/seadragon-min.js"></script>


Then you will always get the latest version of 0.8, in this case currently 0.8.4.

Aseem Kishore set one of Dan Cory's replies as an official response to "Does the Deep Zoom Composer retain ICC Color Profiles?" in Microsoft Live Labs

Aseem Kishore set one of Daniel Gasienica's replies as an official response to "title and description for image in seadragon" in Microsoft Live Labs

A comment on the problem "Seadragon conversion error for large file" in Microsoft Live Labs:

No, we didn't modify the JPEG quality. I'm not 100% knowledgeable about the details, but I believe the fix was a "striping" technique that reads only portions of the JPEG file into memory at any given time. This shouldn't affect the quality; the same artifacts would have been there.

I'm also not 100% sure about the second question, but I'm pretty certain they're derived from the original image and not from subsequent scaled-down versions.

Btw, the image you link to would probably be better off as a PNG, since it's more of a vector-type image than a photographic one. That would also prevent any artifacting you see. – Aseem Kishore, on October 30, 2009 22:12

Aseem Kishore set one of Aseem Kishore's replies as an official response to "Why zoom to more than 100%?" in Microsoft Live Labs

Aseem Kishore replied on October 29, 2009 20:54 to the question "Why zoom to more than 100%?" in Microsoft Live Labs:

Hi Malcolm,

That's a good question. We let you go past 100% by default because it's not uncommon for people to be on high-DPI displays. For them, zooming in past 100% doesn't really make it blurry -- it in fact makes details more visible.

As Anthony pointed out, this limit is configurable in Seadragon Ajax. But it's actually easier than changing the source directly -- it's exposed via an API. Simply add this line to your app:


Seadragon.Config.maxZoomPixelRatio = 1;


You can check out the documentation for that and other "knobs" inside Seadragon.Config.

By the way, our default used to let you zoom into 400% (as Anthony's code snippet shows), but we recently changed the default to 200%. You might like that default better.

Let us know if you have any other questions!