Loading Profile...
EMPLOYEE
Seadragon Ajax updated to 0.8.4!
After many months of being super busy on other projects, we're happy to announce that we've updated Seadragon Ajax from 0.8.3 to 0.8.4! If you're pulling Seadragon Ajax from seadragon.com (as shown in our get started page), you're already updated.
Chief on the list of changes is experimental wrapping support! AKA "360 mode", this lets you pan infinitely on panoramas, maps, etc. that are meant to be connected on the edges. To learn more, check out the thread that started the idea: Is there a way to view an image in 360 mode?
In addition, Seadragon Ajax now has better default pan and zoom constraints. For example, the way we specify minimum zoom now has been changed from "the image should never be smaller than 64 pixels" to "the image should never be smaller than 80% of the viewer". This aligns with our goal of resolution independence. You can see these improved constraints in action in our seadragon.com viewers.
As part of that, we deprecated two things: Seadragon.Config's minZoomDimension in favor of the new minZoomImageRatio, and Seadragon.Viewport's ensureVisible() in favor of the new applyConstraints(). Neither is a breaking change. The documentation explains both if you're interested.
Finally, we have a variety of bug fixes and subtle improvements. For example, we now use <canvas> in Chrome 2+ and Safari 4+, as both now render <canvas> with subpixel precision. This makes it noticeably better visually. Sweet!
We hope you find the update useful! As always, we're open to feedback, so let us know if you find any other bugs or have any other ideas. Enjoy!
Chief on the list of changes is experimental wrapping support! AKA "360 mode", this lets you pan infinitely on panoramas, maps, etc. that are meant to be connected on the edges. To learn more, check out the thread that started the idea: Is there a way to view an image in 360 mode?
In addition, Seadragon Ajax now has better default pan and zoom constraints. For example, the way we specify minimum zoom now has been changed from "the image should never be smaller than 64 pixels" to "the image should never be smaller than 80% of the viewer". This aligns with our goal of resolution independence. You can see these improved constraints in action in our seadragon.com viewers.
As part of that, we deprecated two things: Seadragon.Config's minZoomDimension in favor of the new minZoomImageRatio, and Seadragon.Viewport's ensureVisible() in favor of the new applyConstraints(). Neither is a breaking change. The documentation explains both if you're interested.
Finally, we have a variety of bug fixes and subtle improvements. For example, we now use <canvas> in Chrome 2+ and Safari 4+, as both now render <canvas> with subpixel precision. This makes it noticeably better visually. Sweet!
We hope you find the update useful! As always, we're open to feedback, so let us know if you find any other bugs or have any other ideas. Enjoy!
I’m happy
Follow this update to get notifications on your dashboard.
-
Inappropriate?Congrats on shipping the new version! Unbelievable, now I'm a couple offices down the hall and wasn't even aware of this new update ;)
Cheers,
Daniel
I’m excited
-
Inappropriate?Great news, Aseem!
Perhaps this isn't quite the right place for this, but the timing seems more than coincidental - I've been admiring the improved experience on the iPhone. Granted, it's an update to Seadragon.com, perhaps more than Seadragon Ajax per se, but I noticed that multi-touch now works on the iPhone in Seajax and the new option to launch Seadragon Mobile is insanely great. =]
In any case, the wrapping support is fantastic, as is further canvas support. Keep up the excellent work!
1 Comment
Add a comment
-
Nathanael,
Glad you like the updated Seadragon.com. Improving the mobile experience, e.g. multitouch on iPhone/iPod touch, was the first thing I worked on at Live Labs. Aseem came up with the brilliant View in Seadragon Mobile button that automatically downloads the app if the user doesn't have it. Lots more goodies coming...
Cheers,
Daniel -
Inappropriate?So, how might we use this new update? It appears the API docs haven't been updated to reflect the update, and the basic API script include isn't updated. :)
Just curious gentlemen.
I’m curious.
-
Inappropriate?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.
-
-
-
Inappropriate?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!
EMPLOYEE
