Seadragon Ajax on the iPhone
Hi guys, I had a couple questions/ideas regarding Seadragon Ajax running on the iPhone.
1) Will you guys publish the recent modifications you've added to seadragon.com for the iPhone to the js library available on the live labs site (which IIRC wasn't up to date to the recent modifications either), and also to the open-source project on codeplex (like the touch controller, etc) ?
2) What about using the HTML5 client db storage as a tile cache ? (eg drawing a tile into a canvas, and storing what canvas.toDataURL() returns)
3) Last time I checked you were using active rendering, with a timer running at 60fps. I was wondering whether you think it'd be a good idea to also have passive rendering in order to have more resources available for the rest of the page/app embedding seadragon ?
Thanks
1) Will you guys publish the recent modifications you've added to seadragon.com for the iPhone to the js library available on the live labs site (which IIRC wasn't up to date to the recent modifications either), and also to the open-source project on codeplex (like the touch controller, etc) ?
2) What about using the HTML5 client db storage as a tile cache ? (eg drawing a tile into a canvas, and storing what canvas.toDataURL() returns)
3) Last time I checked you were using active rendering, with a timer running at 60fps. I was wondering whether you think it'd be a good idea to also have passive rendering in order to have more resources available for the rest of the page/app embedding seadragon ?
Thanks
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?Hey John,
I don't have an answer to #1 at the moment; we'll get back to you on that.
To #2, can you tell us what benefits that would have over the regular browser cache? I'll tell you that canvas.toDataURL() is unfortunately too slow for real-time use. It's also a synchronous API that blocks the main UI thread while the image is encoded, which is unacceptable to us.
To #3, we're actually a mix of the two. We actively render (trying to achieve as close to 60 fps as we can get) during animation and while new tiles are being blended in, but once an animation is finished and we're done resolving, we don't do any major work until the next animation begins. So while the user isn't interacting with Seadragon, we use up minimal resources. Is there a specific reason you ask, though?
Thanks for your interest!
Aseem
1 person says
this answers the question
-
Inappropriate?Hi John,
To #1:
We're a labs organization; lots of stuff we do is just an experiment; other things get integrated into products or we share them (via www.seadragon.com or other channels) to gather feedback, or enable and inspire new ideas.
We gave the Seadragon Ajax code to the team at Microsoft delivering the ASP.net Ajax Control Toolkit open source project. They've integrated Seadragon into the toolkit and it's framework. They're managing this open source project, and anyone can contribute enhancements.
Recently, we've been experimenting with some improved mobile support on the www.seadragon.com website. There's no immediate plans to incorporate these experiments into our hosted Seadragon Ajax library or contribute to the open source version in the Ajax Control Toolkit. For our small team this is really just an issue of time, resources and priorities. Our current priority is continued experiments for forward looking features.
The iPhone touchscreen enhancements are using the documented Safari Javascript interfaces. Anyone is free to contribute enhancements to the open source project based on these platform specific browser extensions.
Bill Crow
Seadragon Group Manager
Microsoft Live Labs
The company and 1 other person say
this answers the question
-
Thanks Bill for addressing this question.
–Daniel
Loading Profile...



EMPLOYEE