Task #4026 (reopened)
Opened 13 years ago
Last modified 13 years ago
Technology overview — at Version 14
Reported by: | atarkowska | Owned by: | atarkowska |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-Beta4.3 |
Component: | Web | Version: | n.a. |
Keywords: | n.a. | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 2.0d |
Sprint: | 2011-02-24 (6) |
Description (last modified by atarkowska)
How image zoom technology works?
The most efficient way to provide high resolution image on the web can be achieved by making an "image pyramid" out of the source image and cut it into small tiles. Whenever the user requests a portion of the image only the needed tiles of a level are sent to the client's browser. However, since this tiles are loaded by the client's browser or can be accessed over http, they can be easily reassembled (stitched back together), thus restoring the entire original image.
Instead of sending the tiles directly to the browser it could put them first together on the server side and only then send the requested portion as one picture to the client. Neither the tiles nor the original image are ever loaded by the client. Optionally could crop from the original image without making the tiles.
- http://www.ajax-zoom.com/
- http://lab.gianiaz.com/jquery/gzoom/
- http://www.tripwiremagazine.com/2010/02/15-jquery-plugins-to-create-stunning-image-zoom-effects.html
Chris:
The now defunct Microsoft Seadragon project ( http://www.seadragon.com/) whose technology has now ended up in part of Silverlight core as part of Deep Zoom ( http://www.microsoft.com/silverlight/deep-zoom/) is also a good example of server side pyramid use with extended browser functionality.
https://github.com/fajran/kasuari -- This one is also quite cool.
http://kasuari.dahsy.at/demo/bluemarble/[[BR]]
http://www.mojavelinux.com/cooker/demos/gsv/
Josh:
Change History (14)
comment:1 Changed 13 years ago by atarkowska
- Description modified (diff)
comment:2 Changed 13 years ago by atarkowska
- Owner set to atarkowska
comment:3 Changed 13 years ago by atarkowska
- Status changed from new to accepted
comment:4 Changed 13 years ago by atarkowska
- Description modified (diff)
- Sprint changed from 2011-01-27 (4) to 2011-02-10 (5)
comment:5 Changed 13 years ago by atarkowska
- Description modified (diff)
comment:6 Changed 13 years ago by cxallan
comment:7 Changed 13 years ago by atarkowska
- Description modified (diff)
comment:8 Changed 13 years ago by atarkowska
- Remaining Time changed from 2 to 0
- Resolution set to fixed
- Status changed from accepted to closed
comment:9 Changed 13 years ago by atarkowska
- Description modified (diff)
comment:10 Changed 13 years ago by atarkowska
- Description modified (diff)
comment:11 Changed 13 years ago by atarkowska
- Description modified (diff)
comment:12 Changed 13 years ago by atarkowska
- Milestone changed from OMERO-Beta4.3 to OMERO-Beta4.2
- Remaining Time changed from 0 to 2
- Resolution fixed deleted
- Sprint changed from 2011-02-10 (5) to 2010-04-02 (6)
- Status changed from closed to reopened
comment:13 Changed 13 years ago by atarkowska
- Milestone changed from OMERO-Beta4.2 to OMERO-Beta4.3
- Sprint changed from 2010-04-02 (6) to 2011-02-24 (6)
comment:14 Changed 13 years ago by atarkowska
- Description modified (diff)
The now defunct Microsoft Seadragon project (http://www.seadragon.com/) whose technology has now ended up in part of Silverlight core as part of Deep Zoom (http://www.microsoft.com/silverlight/deep-zoom/) is also a good example of server side pyramid use with extended browser functionality.