All Products
Zoomify Express
Zoomify Export in Photoshop
Zoomify Design
Zoomify Flash
Zoomify Enterprise
Other Products
All
Products
How big should my image be for good zoom?
There are two factors that define 'good zoom'.
The first is how much you are able to zoom in, the second
is what you end up looking at. That is, zooming for a long
time provides a certain sense of satisfaction, but ending
up looking at something interesting is important too.
How much you are able to zoom in depends on the size of the source image as compared to the size of the intended display area. An image that is 1024x768 pixels when zoomified will offer no zoom at all if displayed in a view area that is 1024x768. The image will need to be zoomed 100% just to fill the display area. (Setting zoomifyMaxZoom equal to something higher than 100% is possible but beyond 110% or so stretching will be evident.) If the same image is displayed in a postage stamp-sized view area, however, it will zoom one or two levels of magnification. Given that a view area of at least 1/2 a screen and even larger is generally preferred, a source image should best be 2000 to 3000 pixels in width and/or height at a minimum.
What you end up looking at is also important as this determines whether the experience feels useful and is therefore satisfying. Users zooming on an image of a crowd expect to be able to clearly see a face. Users zooming on an image of a face expect to clearly see blood vessels in an eye. This is simply how user expectations work, in our experience.
A note regarding capture methods: scanning a 35mm negative at 2400 dpi gives about 17.5 megabytes of data - thousands of pixels in both dimensions. This will provide considerable zoom. Most digital cameras are multi-megapixel and their images will also provide significant zoom. It is exciting to have content like our Paris satellite image (courtesy of GeoEye), however, an image 9500 pixels in each dimension - hundreds of megabytes in size when uncompressed - is much more than is needed for most subject matter.
top of section | top of page
Is there a maximum file size for Zoomify Images?
Zoomify's technologies and products have been
designed to support extreme file sizes. Zoomify's testing
as well as actual implementations by many of Zoomify's customers
have included images tens of gigabytes in size. Exact calculations
of the maximum supported file size are difficult due to the
many factors involved. These include the types of programming
variables used, the efficiency of memory and disk space usage,
potential limitations in standard codec libraries that are
leveraged in some areas, file format limitations, and potential
operating system issues.
Please note that specific editions of the Zoomify
Converter support image files of different sizes. The Zoomify
Converter included in Zoomify's standard and Developer products
can convert source images up to 256 megapixels in size. The
Converter included in our Enterprise products supports images
up to 768 megapixels in size. Additional Converters are available
which support images that are larger or even unlimited in
size (within operating system and file format constraints)
- that is, tens of gigabytes in size. If you require support
for images over 768 megapixels or support for special file
formats or Unix/Linux platforms please contact our support
team for pricing and assistance.
top of section | top of page
Do I need special hardware for
Zoomify? What is the best hardware setup?
No. Zoomify does not require special hardware. Zoomify simply requires:
- For image
conversion, sufficient memory and disk space (two and three
times the size of the image
being converted, respectively);
- For viewer customization or component use, hardware sufficient to
run a Flash editing tool (MX or later);
- And for
viewing, sufficient memory for Flash Player (v9 or newer).
top of section | top of page
What performance benchmarks can I expect
with Zoomify?
Zoomify delivers maximum efficiency for maximum performance. Every aspect of Zoomify's zoom-and-pan viewing technology has been optimized: processing is distributed, image data downloads are minimized, redundant data requests are prevented, IT costs are minimized and the end-user experience is maximized.
Most importantly, viewing images with Zoomify prevents all
unnecessary downloads. Image data is requested by the Zoomify
Viewer only for the parts of the image that the user actually
looks at and only at the zoom level they actually zoom to.
This provides a significant bandwidth savings as compared
to common implementations involving large JPEGs, wherein,
the entire image is downloaded even if two thirds of the image
won't fit on the user's screen and only the center third is
ever viewed.
Another key design efficiency in our system is that all logic
and processing occur on the viewing computer rather than the
web server - a fully distributed approach. As site visitors
navigate within an image, it is their systems and not the
server that determine what the current view is, and what image
data is needed for that view.
Note that where optional single-file (PFF) image storage is
used, the Zoomify Servlet is used to fulfill requests for
the parts (byte ranges) of the image file that the client
computer has determined are needed for the current view. Fulfilling
byte-range requests is a standard HTTP 1.1 protocol function
just like fulfilling file requests, which is what Web servers
are designed for. The two tasks, file fulfillment and partial
file fulfillment, show no discernable difference in processing
speed or scaling performance.
Additional efficiencies include the use of all possible caches
both server-side and client-side. Zoomify's solution is entirely
standards based and is therefore perfectly suited to leveraging
existing efficiencies of web servers, operating systems, browsers,
and the Flash Player. Any requested image 'tile' at any resolution,
is simply a JPEG and will therefore be automatically managed
according to the web server cache settings you have in place.
Similarly, these tiny JPEGs are stored on the client machine
by the browser for fast subsequent accesses by the Flash Player.
A common question is whether extra hardware and bandwidth
is needed to support zoomable images - it is not. The better
question is whether extra hardware needed to support image
zooming - i.e., the additional exploration of images that
naturally occurs when site visitors are given access to high-quality
images via an intuitive, interactive interface. With more
time devoted to viewing behavior, more bandwidth may be used.
Predicting end-use behavior is a challenging task and quite
specific to particular audiences and their style of use of
images. As a broad generalization, users will spend significantly
more time viewing zoomable images than low-res images - on
the order of three to five times as much time. Given this
fact, throughput analysis is useful:
On a 1 GHz Pentium 4 with at least 1 GB of RAM memory assuming
throughput of at least 2 saturated 100 mbps Fast Ethernet
connections, theoretical throughput is 2 x 100 mbps = 200
mbps. Effective real throughput (40%) is 80 mbps = 10,000
KB/s. At 9.5 KB per 256-pixel tile this represents 1053 tiles
per second. At approximately 2.5 tiles per second per user
(that is, a half screen view every 2 seconds) this supports
421 concurrent users with a 1 second response time (this assumes
125 concurrent users with only one Ethernet connection). Of
course, the above example illustrates a worst case scenario
given hardware and bandwidth available at reasonable cost.
Ultimately, it is not throughput which best informs site design
choices regarding image presentation alternatives. The critical
factor is not how much data can be passed through a system,
but how little. That is, given the limitations of any server/network
context, the opportunity lies in reducing unnecessary processing
and bandwidth impacts in order to free up resources for desirable
user behavior - efficient image viewing - which is the purpose
and proficiency of Zoomify.
top of section | top of page
My image shows up but it won't zoom at all - what's wrong?
While it is possible that a viewer problem or
incorrect parameter is at fault (such as a zoomifyMaxZoom
setting below 100%), the most likely cause of an image showing
up but failing to zoom is that the source image was simply
very small. The Zoomify converter will convert any image file
so long as it is at least 512 pixels wide or tall, however,
any file that is as small or smaller than the intended display
area will simply fill the area and will not have additional
resolution to zoom into. While it is true that the zoomifyMaxZoom
parameter can be set to a value of 120 (rather than the default
100, which represents 100%) - or even 150 or 200, this simply
forces the Flash Player to stretch the image data. All image
content will show artifacts if stretched beyond a certain
point. For most images this is point is in the range of 110%
to 120%. The only solution for this problem is higher quality
source content - details can simply not be created where they
do not exist.
top of section | top of page
I see the Zoomify logo and splash screen, but my image won't appear. Why?
For an image to be displayed and zoomable, three
steps must successfully occur:
- 1. The
HTML page must tell the browser to embed the Flash Player;
- 2. The
HTML must tell the Player to display the ZoomifyViewer.swf;
- 3. The
HTML must tell the ZoomifyViewer.swf to open a specific Zoomify
Image;
If the Zoomify logo is visible the first two
steps have succeeded and the ZoomifyViewer.swf is running.
If the image is not visible the ZoomifyViewer.swf cannot find
the Zoomify Image. This problem is typically caused by a faulty
zoomifyImagePath. A simple test is to put the Zoomify Image
folder directly next to the ZoomifyViewer.swf so that the
image path can simply be the image folder name. Once that
is working, the image folder can be moved and the path adjusted
appropriately. NOTE: the Flash Player implements a security
restriction that will prevent the Player from opening any
content on a different domain than the Flash movie (in this
case the ZoomifyViewer.swf file). To work around this a 'cross
domain policy file' is required on the target server. For
more information on this issue see the question 'How
can I use a cross domain policy file to allow content on multiple
domains?'
top of section | top of page
I see my Zoomify Image in one browser but not another. Why?
The Flash Player is a different type of client
software in different contexts. It is an 'ActiveX' on Windows
when being used in Internet Explorer. In all other contexts
it is a plugin. Because of this, all HTML embed parameters
for the Player - and thus for Zoomify viewing - must be present
twice, with slightly different formatting in each instance.
For example, the zoomifyImagePath will be present two times,
as will the name of the ZoomifyViewer.swf, as will any additional
parameters. For a simple example of how this works view the
source of any example on the Zoomify web site, or download
the Zoomify Express product and view the source of the 'template.htm'
example web page. Zoomify Express can be downloaded here: Win
| Mac.
top of section | top of page
Will
the Zoomify Viewers work in a CSS layer in a web page?
Yes, however, at the time of release of Zoomify
Design v4 and Zoomify Flash v4 the support of Flash Player
in a layer in the Safari browser on Macintosh was not deemed
reliable enough for production use. Errors are possible regardless
of the method used to create a layer and embed the Player
in it. Zoomify Design and Zoomify Flash do include a web page
example using a layer, along with information about the current
limitations. The example uses the DOM method innerHTML in
non-Internet Explorer browsers to create a layer at the time
of use. This avoids having the Flash Player active in a layer
if not in use. The example uses the Javascript method document.write
to create a layer in Internet Explorer to overcome a problem
with FlashVars support in innerHTML instantiated layers in
that browser. In spite of these and other efforts, an approach
that is compatible with all browsers has not yet been identified.
As work on this issue continues, information will be posted
on the Zoomify web site.
top of section | top of page
Should a relative image path be relative to the Viewer '.swf' file or the calling web page '.htm' file?
A relative path should always be relative to
the calling web page ('.htm' file).
top of section | top of page
I
receive an error about changing security settings when viewing
remote content from a local web page. Why?
In Flash Player versions 8 and later the Player
protects users from the possibility of unauthorized disk access
by blocking access to remote content from a Player instance
in a web page launched locally (off the local hard disk rather
than off a remote web server). The error presented permits
the authorization of access via a Settings panel. This authorization
is per SWF instance locally and per remote web domain. Additional
information can be found on the Settings
Manager page of the Adobe web site.
top of section | top of page
How can I be sure my customers can
see my Zoomify Images even if they're using AOL?
The standard setup of any Flash content should
be easily accessible even for AOL users, however, it is possible
that some AOL users may have browser settings that prevent
Flash Player from dynamically loading images. This my occur
because AOL will, in some versions, attempt to automatically
convert JPEG files to 'progressive' JPEG format, which is
intended to allow the image content to load in horizontal
strips as it is downloaded. (This is actually a function of
the AOL caching system which can modify content on the fly
and which compresses and or reformats image content to streamline
delivery to the many millions of AOL users using dial-up Internet
access.) The Flash Player may fail to load AOL-modified image
files. If this problem is encountered it can be addressed
by instructing the site visitor to modify their browser settings
to leave JPEG files in their original state and not convert
them to progressive JPEG format. The AOL browser is a modified
version of Internet Explorer and the exact steps to make the
settings change may vary. It will almost certainly be found
within the Preferences or Settings menu options and will very
likely be labeled 'Image Compression' with the option to set
it On or Off.
top of section | top of page
The Zoomify converter creates
a 'zoomifyConvertPrefs.asp' file during each conversion - can I
delete it?
The file 'zoomifyConvertPrefs.asp' is a preferences
file that is created by the Zoomify Converter during each
conversion. It is used to store settings for future conversions
and is primarily relevant to the Zoomify Enterprise product.
The prefs file will be located next to the converter (in the
same folder), or for some versions on Windows, in the directory:
Windows | Zoomify | Viewer | Cache. Note that the converter
will create a new preferences file during any subsequent conversion
if it is not already present so it can be deleted at any time
if that is preferred. Also note that it can be helpful to
delete the prefs file (along with any Converter temp files)
if any conversion attempt is interrupted for any reason. More
information about this is available in the answer to the question
'The Zoomify Converter was working,
but now I'm seeing errors. How can I fix this?'.
top of section | top of page
How can I easily convert a large number of images?
The Zoomify Converter included with Zoomify Design,
Zoomify Flash, and Zoomify Enterprise supports 'batch' image
conversion. Simply drag-drop many files onto the converter
and it will automatically convert them one by one. Or, double-click
the converter and within the standard Open File dialog that
is presented, shift-click to select multiple image file names.
Note that the Zoomify Converter included with Zoomify Enterprise
also supports scripted conversion (the use of ASP, JSP, PHP,
or other scripting languages to instruct the Converter to
process a specific image). For information on how many images
can be batch converted at once please see the question 'How
many images can I batch convert at once?'. For information
on scripting the Enterprise Converter, please see the question
'How can I script
conversion of one file after another?'.
top of section | top of page
Are
any special setup steps needed to run the Zoomify Converter
on Windows Vista?
No. Prior versions of the Zoomify Converter may,
however, need to be run in Compatibility Mode. If errors are
encountered regarding the excecutable being incompatible contact
Zoomify to receive the latest Zoomify Converter or use the
following steps to run the Converter in Compatibility Mode:
Right-click the converter and select Properties, then the
Compatibility tab, then check the box labeled "Run this
program in compatibility mode for:" and select from the
dropdown, 'Windows XP'. Note that the converter also has to
run in "Administrator mode".
top of section | top of page
How fast can Zoomify convert and display
images?
Zoomify is designed to deliver the maximum possible
efficiency in image preparation and viewing.
Image preparation is typically performed at site
authoring time though it is also possible to implement at
view-time using the scriptable Zoomify Converter included
in Zoomify Enterprise. The Zoomify Converter can process gigabytes
of image data in minutes - actual performance varies according
to processing power and memory availability. To determine
the processing performance your system will deliver simply
download our free product, Zoomify Express, and convert your
test images on the system in question. Zoomify Express can be
downloaded here: Win
| Mac.
Viewing of Zoomify images is significantly more
efficient than with any other approach. Each new view that
a site visitor zooms-and-pans to only involves the image data
essential for that view at that resolution. The user experience
is further optimized by server and client-side caching.
For additional information on Zoomify performance
please see the questions 'What
performance benchmarks can I expect with Zoomify?', and
'What are the key benefits of Zoomify?'.
top of section | top of page
How can I change the compression level of the Zoomify Converter?
The default compression of the Zoomify Converter
can be easily changed by locating the file zoomifyConvertPrefs.asp*
and changing one line. The file will be located immediately
next to the Zoomify Converter after any conversion, or for
some prior versions in the Zoomify | Cache directory. The
line that requires changing reads as follows by default:
ZOOM_COMPRESSION: 80
The number 80 can be changed to anything from 1 to 100. Note that settings below 80 may show JPEG compression artifacts.
*This file will exist AFTER you've converted at least one image
top of section | top of page
What formats does the Zoomify Converter support?
The Zoomify Converter natively supports TIF,
BMP, and JPEG formats. Numerous additional formats are supported
through the built-in Zoomify Export available in Adobe Photoshop
CS5, CS4, and CS3.
top of section | top of page
When will Zoomify offer conversion support for formats like RAW
or PSB?
In Adobe Photoshop CS5, CS4, and CS3 Zoomify
conversion is an integrated feature. Photoshop CS5, CS4, and
CS3 users can simply select File | Export | Zoomify... to
prepare their images for Zoomify viewing. While it may still
be of interest for some Zoomify customers for the Zoomify
Converter to directly support the RAW or PSB format, the built-in
support provided by Adobe delivers excellent convenience and
performance. Your input as to how direct support within the
Zoomify Converter weighs against the development or enhancement
of other Zoomify features is welcomed. (Please note that prior
to exporting from within Photoshop CS5, CS4, or CS3 users
will want to ensure their image is 8-bit (as required by the
Flash Player) and in sRGB format (in order to ensure consistent
color presentation across Windows and Macintosh platforms.)
top of section | top of page
Can Zoomify work with image tiles that are not lossy compressed?
Zoomify currently makes use of Flash Player's
longstanding support for the JPEG image format and, accordingly,
the image tiles the Zoomify Viewer loads are JPEG files. With
the release of Flash Player 8, PNG support became available,
however, customer demand for Zoomify support for lossless
tile compression was not judged to be as great as for many
other features. Since that time we have made an effort to
justify diverting development resources from other customer
requested features but have not yet been able to do so. If
you have a need for non-lossy-compressed tile support in Zoomify
please let us know.
We do our best to ensure our development is driven by customer
needs.
top of section | top of page
Can Zoomify work with image tiles that are in other formats?
Zoomify currently works with JPEG tiles, however,
Zoomify technology certainly can be modified to work with
tiles in any image format that the Flash Player supports.
With respect to viewing, such a modification would simply
require a change to expected filename extension in the Zoomify
Viewer Component inside the Zoomify Viewers (note that other
changes might also be required, though this is not expected).
With respect to image conversion, however, the Zoomify Converter
would need to be modified to save tiles in a format other
than JPEG. This would require greater effort. An alternative
would be to create a script in Photoshop that would output
tiles in the desired format, or to use a scripting language
such as ASP, JSP, or Python coupled with an image library
such as ImageMagick or PIL to create the tiles. The work involved
in either of these approaches, while not overwhelming, is
not trivial.
top of section | top of page
Can I use Zoomify with vector content?
Yes and no. Vector content in the form of a SWF
file can easily be used as a hotspot (label, overlay) within
the Zoomify Hotspot Viewer in 8 for our prior Zoomify Flash
product version (v3). Later Zoomify Hotspot Viewer versions
do not yet support hotspots in the file format '.swf' due
to complications related to Flash Player security changes.
More importantly, vector content cannot currently be converted
using the Zoomify Converter into a base image to be displayed
within the Zoomify Viewer.
The benefit of the Zoomify technology is in the
rapid, interactive viewing of bitmap (photo) files. This is
essential as bitmap images of any reasonable quality typically
make for very large files. Cutting these files into JPEG tiles
and doing so at many different tiers of resolution enables
the Zoomify Viewer to download only the small portion of the
image that is essential for the current view that has been
zoomed and panned to by the user. This ensures that each new
view will require only a download of perhaps 100k to 300k
regardless of whether the source image is 5 megabytes or 500
gigabytes in size.
Vector content, in contrast, is typically small
with respect to file size. It can be downloaded quickly and
scaled with the built-in functionality of the Flash Player.
In most cases Zoomify's tiled/tiered approach is not required.
Where one's vector content is exceptionally complex or broad
in scope - for example a street map for an entire city - tiling
and tiering would prove valuable. Zoomify has explored this
possible additional use and weighed the non-trivial vector
tiling requirement against the apparent demand and the development
has simply not been justifiable to-date. There are many other
features associated with much greater customer demand. We
are, however, interested in the value of such a feature addition
and we welcome your input about your needs and potential uses
for such a feature.
top of section | top of page
How can I easily upload Zoomify Image folders to my Web server?
Zoomify Image folders can contain numerous JPEG
'tile' files. As a result, it is often helpful to first 'zip'
or 'stuff' one or more folders prior to uploading. The uploaded
file can then be unzipped or unstuffed on the server. This
approach results in the transfer of a comparable amount of
data but only a single file transfer. The savings in client
and server communication can reduce the copy time dramatically.
This approach is also recommended due to the reduced risk
of any individual JPEG file being corrupted or lost during
the transfer process whether due to operating system or human
error. Utilities for compressing and uncompressing files as
described above can be downloaded from numerous sites including
WinZip.com
and Stuffit.com.
top of section | top of page
What
is a 'cross-domain policy file' and how do I use it for multi-domain
web site hosting?
Beginning with Flash Player 6, security restrictions
have prevented Flash movies from dynamically loading content
from domains other than the domain that the Flash movie itself
is in. This restriction can be addressed through the use of
a cross-domain policy file.
A cross-domain policy file is simply an XML (text)
file that provides a way for the server to indicate that its
data and documents are available to SWF (Flash movie) files
served from certain domains or from all domains. Any SWF file
that is served from a domain specified by the server's policy
file will be permitted to access data or assets from that
server.
When a Flash movie attempts to load data from
another domain, Flash Player automatically looks for policy
file on that domain. If one is present, the data is automatically
accessible. For complete information on creating and using
cross-domain policy files, visit the Adobe web site and read
TechNote
14213.
top of section | top of page
How can I control the Zoomify Viewer from JavaScript in my web page?
Using Javascript to talk into a 'smart client'
such as Flash Player is always enticing and always a challenge.
This is not an issue specific to Zoomify. The many browsers
and browser versions support different communication means
(both inward and outward) and each means presents different
level of control and reliability. Two starting points for
exploring the possibilities include the FSCommand
support of Flash Player 7 and earlier and the ExternalInterface
class introduced in Flash Player 8 (the former being relevant
to Zoomify Flash and earlier, the latter to later Zoomify
product versions). In each case Flash editing of Zoomify Viewer
source code will be required. For this reason the Zoomify
Flash product is needed rather than the Zoomify Design product.
top of section | top of page
How can I ensure that the Zoomify Viewer has focus when my Web page loads?
The following lines can be added to a web page
for a specific Flash movie to have focus when the page loads.
This may or may not be be effective depending on the browser,
Flash Player version, and any customizations that may have
been made to the Viewer being loaded. If effective, the keystrokes
'a', 'z', 'Ctrl', 'Shift', and the arrow keys, will cause
the Zoomify Viewer to zoom and pan as desired without a mouse-click
in the Viewer being required first.
In the following lines to function properly, 'movieName' must be the name parameter in the Flash object and embed tags.
top of section | top of page
Which Zoomify products support 'map files'?
Zoomify's 'map file' support provides for 'aliases' via an XML file. This allows many image paths to be easily managed by editing the references in one file. As this functionality has been primarily of interest to our enterprise customers, it is implemented in a manner convenient for that audience: on the server-side using our Zoomify Servlet. This servlet is included with our Zoomify Enterprise product.
Because our Zoomify components are common to all our products, the 'map file' field is present in the custom property inspector's Advanced tab regardless of whether the component is acquired with Zoomify Flash or Zoomify Enterprise. Clarification that this feature is specific to the Enterprise product will be added in an upcoming revision to the User Guide documentation.
top of section | top of page
Does Zoomify work with Akamai and other edge servers?
Zoomify's default 'folder-based storage' involves just JPEGs, HTML, and a tiny Flash movie which functions as the 'viewer'. This zoom-and-pan solution is completely standard in terms of web server hosting, caching, and other publishing considerations. Whether working with Akamai or another 'edge server' system, the small JPEG image files which make up any Zoomify view will be propagated over the network optimally and independently based on demand - just as if they were individually placed within a web page.
Zoomify's 'one-file' storage approach, in which the JPEG files that make up different views of an image are stored in a single file with a '.PFF' extension, involves the use of a small Java servlet for fulfillment of file requests during the zoom-and-pan viewing of site visitors. Due to Java security requirements, the servlet may need to be distributed to the edge servers to support image file delivery from the edge network servers.
top of section | top of page
Zoomify Express
Can I use the free Zoomify Express on a public or commercial site?
Yes. Our free product, Zoomify Express, is ideal
for web designers needing a quick and simple way to include
high-quality images in their sites and is approved for use
on web sites and CDs whether private or public, personal or
commercial. Zoomify Express can be downloaded from the Zoomify
web site: Win
| Mac.
Complete information regarding license terms can be found
in the Zoomify
License Agreement.
top of section | top of page
Are there any royalties or strings
on my Zoomify content?
No. Zoomify does not charge any royalty fees
whether per number of images, per number of times an image
is viewed, or per time period. Nor does Zoomify require any
'broadcast key' or other licensing technology. Your content
is your content. Complete information regarding license terms
can be found in the Zoomify
License Agreement.
top of section | top of page
How do I set up Zoomify Express?
Zoomify Express requires no install and no setup.
Simply download the product, unzip or unstuff the downloaded
file, and open the resulting folder.
You'll find a simple Zoomify Converter application
that you can drag-drop any image file onto. It creates a Zoomify
Image folder - right next to the source image file. The small
window that opens shows the conversion in progress - when
it closes your new Zoomify Image folder will be complete.
(Note that for a small image - 5 megabytes or less - the conversion
happens very rapidly and the progress window may only be open
for a very brief amount of time.)
The Zoomify Express product folder also includes
our Zoomify Viewer - the file ZoomifyViewer.swf - as well
as an example web page - template.htm. These are used together
to view your newly created Zoomify Image.
For quick simple steps for using Zoomify Express
see the QuickStart.htm file that is in the downloaded folder.
For complete, detailed steps on using the product see the
questions 'Where can I find step-by-step,
detailed instructions for using Zoomify Express?'.
top of section | top of page
Where can I find step-by-step, detailed instructions for using Zoomify Express?
Here are step-by-step instructions for working
with Zoomify Express. Follow these detailed steps to use Zoomify
if you are not familiar and comfortable with web page editing:
1. Download your free copy of Zoomify Express from the Zoomify
home page.
2. Unzip the download. This will create a new folder.
3. Copy the image file of your choice into that folder. Bigger
is better. Zoomify's technology does not make small images
high-quality, it makes big high-quality images fast and interactive.
Whatever you see in your image editor at 100% is what you
will see in Zoomify at 100% zoom.
4. Drag the image file onto the Zoomify Converter. You will
see it get cut into little pieces at many resolutions. After
a short wait the converter will have created a new folder.
The new folder will be directly next to the source image.
The name of the new folder will be the same as the source
image except that it will not include the filename extension
(the '.jpg' or '.tif'). For example, if your source image
is myImage.jpg then your resulting zoomable image folder will
be myImage. (Note that a file named 'zoomifyConvertPrefs.asp'
will also be created. This file is used to store settings
for future conversions and is primarily relevant to the Zoomify
Enterprise product. You can ignore this file or delete it
after conversion completes, if you prefer.)
5. Now open the template.htm file with a text editor. This
is just a web page - an HTML file. You must change one statement
in it and then save it.
6. The statement you must change is: zoomifyImagePath=ZoomifyExampleImage
You must replace the name of your zoomable image folder in
that statement. For example, if your zoomable image folder's
name is myImage, the new statement will be: zoomifyImagePath=myImage.
7. Make this change in TWO places. Look carefully and you
will see that the zoomifyImagePath statement is present twice.
Flash Player requires all such statement to be present twice.
The formatting surrounding each of the instances will differ
slightly. The need for this repetition as well as for the
slight difference in formatting is due to the fact that the
Flash Player works differently in Windows Internet Explorer
than in other browsers. Because your web page will be viewed
by people with all different sorts of browsers you need to
be sure to have the Flash Player work in all cases.
8.Save the template.htm file and close the text editor program.
9. Double-click the template.htm file and it will automatically
open in your browser. It will load Flash Player and that will
load the Zoomify Viewer which is a Flash movie. The Viewer
will, in turn, load some of the little jpeg pieces out of
the zoomable image folder. You will see your image and be
able to zoom in and out and pan left and right and up and
down. You now have a working example of your image in zoomable
form.
10. You can now make this image available for everyone to
see by copying it to your web server. If you use a hosted
web site service the company providing the service will tell
you how to copy your image to the server. You will need to
be sure to copy the zoomable image folder (myImage), the Zoomify
Viewer (ZoomifyViewer.swf), and the web page (template.htm).
After copying these files to the server you'll be able to
type an Internet address or 'URL' into your browser and view
the image over the web. You'll see that the view is quick
to display and fast to zoom-and-pan. This is because the initial
view is made up of just a few little pieces or JPEG image
files - which quickly and automatically download for viewing.
And any zoom-and-pan presents a new view which is also made
up of just a few image files. There is never any need to download
the entire image so viewing it is always simple and fast.
top of section | top of page
How big should my image be for good zoom?
There are two factors that define 'good zoom'.
The first is how much you are able to zoom in, the second
is what you end up looking at. That is, zooming for a long
time feels good, but ending up looking at something interesting
is important too.
How much you are able to zoom in depends on the size of the
source image as compared to the size of the intended display
area. An image that is 1024x768 pixels when zoomified will
offer no zoom at all if displayed in a view area that is 1024x768.
The image will need to be zoomed 100% just to fill the display
area. (Setting zoomifyMaxZoom equal to something higher than
100% is possible but beyond 110% or so stretching will be
evident.) If the same image is displayed in a postage stamp-sized
view area, however, it will zoom one or two levels of magnification.
Given that a view area of at least 1/2 a screen and even larger
is generally preferred, a source image should best be 2000
to 3000 pixels in width and/or height at a minimum.
What you end up looking at is also important as this determines
whether the experience feels useful and is therefore satisfying.
Users zooming on an image of a crowd expect to be able to
clearly see a face. Users zooming on an image of a face expect
to clearly see blood vessels in an eye. This is simply how
user expectations work, in our experience.
A note regarding capture methods: scanning a 35mm negative
at 2400 dpi gives about 17.5 megabytes of data - thousands
of pixels in both dimensions. This will provide considerable
zoom. Most digital cameras now capture many megapixels and
their images will also provide significant zoom. It is exciting
to have content like our Paris satellite image (courtesy of
GeoEye), however, an image 9500 pixels in each dimension -
hundreds of megabytes in size when uncompressed - is much
more than is needed for most subject matter.
top of section | top of page
I see my Zoomify Image in one browser but not another. Why?
The Flash Player is a different type of client
software in different contexts. It is an 'ActiveX' on Windows
when being used in Internet Explorer. In all other contexts
it is a plugin. Because of this, all HTML embed parameters
for the Player - and thus for Zoomify viewing - must be present
twice, with slightly different formatting in each instance.
For example, the zoomifyImagePath will be present two times,
as will the name of the ZoomifyViewer.swf, as will any additional
parameters. For a simple example of how this works view the
source of any example on the Zoomify web site, or download
the Zoomify Express product and view the source of the 'template.htm'
example web page. Zoomify Express can be downloaded here: Win
| Mac.
top of section | top of page
My image shows up but it won't zoom at all - what's wrong?
While it is possible that a viewer problem or
incorrect parameter is at fault (such as a zoomifyMaxZoom
setting below 100%), the most likely cause of an image showing
up but failing to zoom is that the source image was simply
very small. The Zoomify converter will convert any image file
so long as it is at least 512 pixels wide or tall, however,
any file that is as small or smaller than the intended display
area will simply fill the area and will not have additional
resolution to zoom into. While it is true that the zoomifyMaxZoom
parameter can be set to a value of 120 (rather than the default
100, which represents 100%) - or even 150 or 200, this simply
forces the Flash Player to stretch the image data. All image
content will show artifacts if stretched beyond a certain
point. For most images this is point is in the range of 110%
to 120%. The only solution for this problem is higher quality
source content - details can simply not be created where they
do not exist.
top of section | top of page
My image zooms, but I want it to zoom more. What can I do?
How much you are able to zoom depends on the
size of the source image as compared to the size of the intended
display area. An image that is 1024x768 pixels when zoomified
will offer no zoom at all if displayed in a view area that
is 1024x768. The image will need to be zoomed 100% just to
fill the display area. (Setting zoomifyMaxZoom equal to something
higher than 100% is possible but beyond 110% or so stretching
will be evident.) If the same image is displayed in a postage
stamp-sized view area, however, it will zoom one or two levels
of magnification. Given that a view area of at least 1/2 a
screen and even larger is generally preferred, a source image
should best be 2000 to 3000 pixels in width and/or height
at a minimum.
If your image does not provide the amount of
zoom that you would like it is therefore possible to decrease
the size of the view area or increase the size (quality) of
the source image. The latter solution is by far the better
choice. Note that scanning a 35mm negative at 2400 dpi gives
about 17.5 megabytes of data - thousands of pixels in both
dimensions. This will provide considerable zoom. Most digital
cameras now capture many megapixels and their images will
also provide significant zoom. It is therefore not particularly
difficult to capture sufficient image data for 'good zoom'
- assuming that recapturing or replacing the source image
is an option.
top of section | top of page
I see the Zoomify logo but I don't see my image. Why?
For an image to be displayed and zoomable, three
steps must successfuly occur:
- 1. The
HTML page must tell the browser to embed the Flash Player;
- 2. The
HTML must tell the Player to display the zoomifyViewer.swf;
- 3. The
HTML must tell the zoomifyViewer.swf to open a specific Zoomify
Image;
If the Zoomify logo is visible the first two
steps have succeeded and the zoomifyViewer.swf is running.
If the image is not visible the zoomifyViewer.swf cannot find
the Zoomify Image. This problem is typically caused by a faulty
zoomifyImagePath. A simple test is to put the Zoomify Image
folder directly next to the zoomifyViewer.swf so that the
image path can simply be the image folder name. Once that
is working, the image folder can be moved and the path adjusted
appropriately. NOTE: the Flash Player implements a security
restriction that will prevent the Player from opening any
content on a different domain than the Flash movie (in this
case the zoomifyViewer.swf file). To work around this a 'cross
domain policy file' is required on the target server. For
more information on this issue see the question 'How
can I use a cross domain policy file to allow content on multiple
domains?'
top of section | top of page
How can I ensure my initial display is sharp and
clear and not blurry?
To ensure the clearest possible initial image
view, all versions of the Zoomify Viewer released since August
2004 include ActionScript in the 'Actions' frame (frame 1
of layer 1) that carefully manages the presentation of image
data depending on how Flash Player has loaded. This is necessary
because the timing of initial image display must be different
when the Player loads for the first time in a browser session
than when it loads on any subsequent web page views or when
a web page is resized. This special handling ensures that
image data will be sized after the Player is initialized,
the Flash stage is sized, and the Zoomify Viewer component
is initialized, and will therefore be free of any distortion
(unintended scaling) and absolutely as clear as possible.
top of section | top of page
Where should my image path in my HTML point?
Your image path should point to your Zoomify
Image folder. It should not point to anything inside the image
folder. 'Relative' paths are easiest to use. For example,
if your source image is named 'myFavoriteImage.jpg' the Zoomify
Converter will create a Zoomify Image folder named 'myFavoriteImage'.
If you place this directly next to the Zoomify Viewer (zoomifyViewer.swf)
your image path will be:
zoomifyImagePath=myFavoriteImage
top of section | top of page
Do I ever need to refer to the TileGroup0 folder or the XML file?
No. Absolutely not. Your image path should point
to your Zoomify Image folder. It should not point to anything
inside the image folder. Please see the question 'Where
should my image path in my HTML point?' for a helpful
example.
top of section | top of page
What steps should I take to find out why my Zoomify Image won't display?
First, determine if your browser is correctly
loading your web page. If you can see any text or perhaps
the outline of a Flash display area you know the browser has
at least found the page and is trying to load it. If not,
you are probably receiving a 'Page not found - 404' browser
error. You may be trying to access the page using an link
that is not correct. Try entering the web page URL directly
into your browser. If testing locally on your desktop, try
double-clicking the web page.
Next, decide if the web page is loading the Zoomify
Viewer. If you see the Zoomify logo, the web page is finding
the Viewer. If not, double-check the HTML. Your Flash embed
statement may have an incorrect name and/or path for the zoomifyViewer.swf
file.
Now see if the Viewer is loading your image to
any extent. Is the image starting to show up but failing to
fully clear? Is the Flash Player or browser getting 'hung
up'? This sort of issue is very seldom encountered but when
it is it is harder to isolate but any information you can
provide will help us help you.
Two final points:
- First, don't forget that every parameter needed
for the Flash Player must be included in the web page TWICE.
This is because the Flash Player is an ActiveX client for
Windows IE users and a plugin for everyone else. The two technologies
require the same parameters but slightly different formatting.
This is not specific to Zoomify or even to Flash Player. It
is a function of how browsers support client software.
- Second, it is sometimes the case when using
web space on a hosted server or a complex ecommerce web store
package that file names, paths, or even types can be confused.
A good way to find out is to download our simple
test, try it on your local desktop, then upload it with
no modifications. If it does not work, contact your service
or software provider. If it does, compare the setup of your
web page and files with the simple example and you'll likely
find a typo or other oversight.
Additional resources: 'I
see the Zoomify logo but I don't see my image. Why?',
'My image shows up
but it won't zoom at all - what's wrong?', 'I
see my Zoomify Image in one browser but not another. Why?'
top of section | top of page
What
HTML and XML parameters do the Zoomify Viewers support?
The exact HTML and XML parameters supported by
each Zoomify Viewer differ according to the features of the
Viewer. These are described in detail in the 'READ ME FIRST.txt'
file that is included in each Viewer folder. A general listing
is also included on the Zoomify Design
product page. The parameters of the Viewers are the same whether
included in the Zoomify Design product or the Zoomify Flash
product, however, with the '.FLA' and '.AS' source files included
in the Zoomify Flash product and a Flash editor, you can add,
modify or remove HTML or XML parameters at will.
top of section | top of page
Can I add to the parameters supported by Zoomify Viewer?
Yes, of course. The parameters that the Zoomify
Viewer supports are simply a function of the naming convention
used in the web page's HTML and a few lines of ActionSript
inside each Zoomify Viewer. For example, the FlashVars parameter
must include a zoomifyImagePath=myImageFolderName string and
it may also include something like zoomifyInitialZoom=50 to
set the initial zoom at 50% (rather than the default behavior
of zooming just enough to exactly fit the image into the display
area). These two parameters are joined together to create
this FlashVars parameter:
zoomifyImagePath=myImageFolderName&zoomifyZoom=50
The Flash Player automatically reads this value
when it loads and passes it into whatever Flash movie it opens
- for example, ZoomifyViewer.swf. The values are passed in
as two variables: one is named 'zoomifyImagePath' and is set
to 'myImageFolderName', and the other is named 'zoomifyInitialZoom'
and is set to the value 50.
The Zoomify Viewer, in turn, has several lines
of ActionScript instructions in the class file 'Parameters.as'.
This file can be found in the subfolder named 'Classes | zoomify
| utils'. The ActionScript 'maps' the HTML to XML so that
it can be read internally via the Zoomify ActionScript API
calls 'getParameterAsString()' and 'getParameterAsNumber()'.
These tests the variables to make sure they are not undefined
and verify that they have useful values.
If the variable has a useful value, the ActionScript
then passes the values into the Zoomify Viewer Component by
setting its properties:
myViewerInstance.imagePath = myImagePath;
To add new parameters most simply, select and
duplicate, line by line, the support for an existing parameter.
Then add the parameter to a test web page.
top of section | top of page
How
can I remove or replace the Zoomify splashscreen and Zoomify
Toolbar logo?
The Zoomify logo is present in all Zoomify products
by default. It can be removed in all products other than our
free Zoomify Express product and and the Zoomify Viewer that
is included in the Zoomify Export feature provided in Adobe
Photoshop CS5, CS4, and CS3. It can be replaced in the Viewers
using the editable '.FLA' and '.AS' source files included
in our Zoomify Flash product using a Flash editor. Please
do not attempt to remove the logo from the Zoomify Express
viewer or the Viewer included with Zoomify Export as its presence
is what makes continued availability of our free Viewers possible.
To remove the logo in the Viewers in Zoomify Design simply
set the zoomifySplashscreen and zoomifyToolbarLogo HTML parameters
to '0'. This is also possible via the XML parameters. To replace
the logo in the Viewers using Zoomify Flash simply open the
relevant '.FLA' source file in your Flash editor, use the
Window menu to open the Library pane, right-click any folder
item in the Library and select Expand All Folders, then scroll
down to find the relevant elements. These items can be right-clicked
to place them on the stage for editing.
top of section | top of page
Zoomify Export in Photoshop
What is included in this feature?
Zoomify Export in Adobe Photoshop CS5, CS4, and
CS3 includes everything you need to use high-quality images
on any web site: fast integrated output of zoomable image
content; a small, intuitive 'viewer'; and automatically generated
web pages you can use, edit, or simply copy HTML from.
Zoomify Export provides Photoshop users with
a alternative to down-res'ing via the Save For Web or Devices
feature. Rather than throwing away high-quality image data,
you can publish it on the web for anyone to view using only
the Zoomify Viewer - a tiny Flash movie which allows web site
visitors to zoom-and-pan within your 'zoomified' image.
Zoomify is completely standard - just JPEGs,
HTML, and Flash - so no special setup is required for your
web site or your site visitors. Most importantly, no royalties
or strings are put on your content.
Zoomify's other products provide enhanced features
and functionality relevant to web designers, Flash developers,
and content managers in image-centric markets such as medicine
and the sciences, image archives and museums, defense and
security, education and entertainment, and much more.
- Zoomify Express provides free zoom-and-pan
authoring, publishing, and viewing
- Zoomify Design adds 10 enhanced Viewers for Slideshows,
Hotspots, and more and HTML and XMl parameters
- Zoomify Flash delivers complete Flash source files for total
control of look and feel in all Viewers
- Zoomify Enterprise adds intuitive web-based image annotation
and a scriptable converter
top of section | top of page
What about updates and new functionality?
Updates to the Zoomify Viewer included in Photoshop
CS5, CS4, and CS3 will be posted on our Zoomify Export in
Photoshop web page as they become available. Enhanced functionality
is provided by Zoomify's many other products:
- Zoomify Express provides free zoom-and-pan
authoring, publishing, and viewing
- Zoomify Design adds 10 enhanced Viewers for Slideshows,
Hotspots, and more and HTML and XMl parameters
- Zoomify Flash delivers complete Flash source files for complete
control of look and feel in all Viewers
- Zoomify Enterprise adds intuitive web-based image annotation
and a scriptable converter
top of section | top of page
Are
additional HTML and XML parameters available?
The HTML parameters supported by the Zoomify
Viewer included with Photoshop include only the ability to
hide or show the Zoomify Navigator ('bird's-eye-view') as
well as the standard parameters supported by Flash Player
(background color, etc.). Zoomify's other products add many
enhanced Viewers with special features such as Slideshows
and Hotspots and additional HTML and XML parameters covering
a wide range of layout and behavior choices. The Zoomify Viewers
are very flexible and provide functionality relevant to many
different audiences. In addition, you can add, modify or remove
parameters yourself using our Zoomify Flash product and a
Flash editor.
top of section | top of page
Can I change the look and functionality of the Zoomify Viewer?
Absolutely. The Zoomify Design product includes
10 additional Viewers with extensive HTML and XML parameters
for control of Viewer layout and functionality. And Zoomify
Flash includes complete '.FLA.' and '.AS' source files for
the many Zoomify Viewers as well as many examples, also with
full source code.
top of section | top of page
What compression setting is optimal for most images?
A setting of 8 : HIGH provides the optimal combination
of quality and compression for the vast majority of images
we and our customers have worked with over many versions,
many years, and many images.
top of section | top of page
Where can I see known issues with the beta version?
A list of known problems with the latest beta
version is available on our Zoomify
Export in Photoshop page on our web site. We welcome your
input regarding any issues you discover via our Support email
address.
top of section | top of page
Do I really need a zoomifyViewer.swf file in every image folder?
Absolutely not. You can put the zoomifyViewer.swf
file wherever you prefer on your server and simply change
the 'SRC' path of zoomifyViewer.swf accordingly. Be sure to
make the change in TWO places in your web page (once for Windows
IE users, once for everyone else). The SWF file in your image
folder is there only as a convenience in the export process
and can be deleted.
top of section | top of page
Can I have a single zoomifyViewer.swf file for my entire web site?
Absolutely. Simply put the zoomifyViewer.swf
file wherever you prefer on your server and change the 'SRC'
path of zoomifyViewer.swf accordingly. Be sure to make the
change in TWO places in your web page (once for Windows IE
users, once for everyone else). The SWF file in your image
folder is there only as a convenience in the export process
and can be deleted.
top of section | top of page
I don't see this feature in Photoshop. Do I install it manually?
Zoomify Export is a feature of Photoshop CS5,
CS4, and CS3. If you do not see the feature on the File menu
of your copy of Photoshop please verify that you have CS5,
CS4, or CS3. If you do not you can purchase the latest version
from the Adobe web site. If you do and the menu choice is
not present, a reinstallation of Photoshop may be the simplest
means to resolve the problem. An alternative would be to check
for the Zoomify files that should be present in the Zoomify
folder under the 'Presets' subfolder of Photoshop. If these
steps do not resolve the problem, it may be a bug and a report
to us and to Adobe will be appreciated.
top of section | top of page
How do I report a possible bug?
Please send bug reports to Zoomify
Support. If you are an Adobe Photoshop beta tester, please
be sure to also report bugs to Adobe as described in their
beta download process. Your input is greatly appreciated.
top of section | top of page
Can
I purchase this product without purchasing Photoshop CS5,
CS4, or CS3?
The Zoomify Export feature of Photoshop CS5,
CS4, and CS3 is designed as an integrated function of Photoshop
and cannot be purchased or used separately from it. The Zoomify
Viewer v4, however, will be available in the near future (weeks,
not months) as an element of a new version of each relevant
Zoomify product. (All purchases during or after December of
this year include a free upgrade. Prior purchasers may upgrade
for a small fee.)
top of section | top of page
I
got this feature in a Photoshop public beta. What are the
allowed uses?
Any Zoomify beta release includes technology
not considered ready for sale or use on production web sites,
and is provided solely to support testing to ensure a high-quality
final shipping product. With regard to the shipping products
of Zoomify, allowed uses are discussed in detail in the answer
to the question 'What
are the allowed uses of Zoomify products?'. Complete information
regarding license terms can be found in the Zoomify
License Agreement.
top of section | top of page
I
have a beta Zoomify Viewer. Can I use it on public or commercial
Web sites?
Zoomify beta software involves technology not
considered ready for sale or use on production web sites,
and is provided solely to support testing to ensure a high-quality
final shipping product.
top of section | top of page
Zoomify
Design
How do I install Zoomify Design?
Zoomify Design does not require installation.
The various features of the product are useful immediately
upon unzipping the product download. The Zoomify Converter
can be used simply by dropping any image file onto the Converter
application (exe or app) icon. Each of the eleven Zoomify
Viewers includes example web pages and Zoomify Image content.
The product User's Guide and helpful READ ME text files are
all accessible directly in the unzipped download. And publishing
your content simply requires copying a Viewers '.swf' file,
Zomify image folder, and HTML web page with appropriate image
path to your web server.
top of section | top of page
Is there a trial version available?
Our free product, Zoomify Express, substitutes for
a trial product and can be downloaded from our home page or
here: Win
| Mac.
This product demonstrates drag-and-drop image conversion and
intuitive Flash-based zoom-and-pan viewing and is ideal for
web designers needing a quick and simple way to include high-quality
images in their sites - whether private or public, personal
or commercial. Customers requiring a means to more deeply
evaluate the specific features of Zoomify Flash may
contact our Support team at the address provided below
for receipt of evaluation a copy of that product on a case-by-case
basis.
top of section | top of page
Do I need a Flash editor or any special tools to use Zoomify Design?
No special tools and no Flash editor is needed
to work with Zoomify Design. Converting images, setting Viewer
preferences via parameters, and publishing zoomable content
to your web server can all be accomplished with only a standard
text or HTML editor and a way to upload files.
top of section | top of page
Does
Zoomify Design work with Dreamweaver?
Absolutely. Dreamweaver allows web designers
to easily and productively create web pages and support for
Flash - and thus for Zoomify - is a key benefit of working
with Dreamweaver. A common frustration, however, is that Dreamweaver's
support for Flash Player is not absolutely complete.
The most important example of this incomplete
support is that Dreamweaver does not present the 'FlashVars'
parameter - which is natively supported by Flash Player -
in its properties palette for Flash objects. The FlashVars
parameter is very useful because it allows a web page to pass
a value into a Flash movie for that movie to use internally.
The FlashVars parameter is how any web page tells the Zoomify
Viewer what Zoomify Image to display.
In practice, the fact that Dreamweaver's Flash
object properties palette doesn't present the FlashVars parameter
for entry simply means that Dreamweaver users must briefly
switch from Design View to Code View and manually type in
the parameter in the page's HTML. This is not immediately
clear, however, so many Dreamweaver users add their Flash
object - the Zoomify Viewer - set its size and position, and
then are disappointed when they view the resulting page and
the Zoomify Viewer does not display their image.
This situation can be easily remedied by simply
viewing the HTML of any demo on the Zoomify web site and mimicking
the placement of the FlashVars parameter and its value in
the web page. (And be certain to include it twice - as with
all Flash Player parameters, their is one instance for Windows
IE users and a second instance for everyone else.)
top of section | top of page
How
can I remove or replace the Zoomify splash screen and Zoomify
Toolbar logo?
The Zoomify logo is present in all Zoomify products
by default. It can be removed in all products other than our
free Zoomify Express product and and the Zoomify Viewer that
is included in the Zoomify Export feature provided in Adobe
Photoshop CS5, CS4, and CS3. It can be replaced in the Viewers
using the editable '.FLA' and '.AS' source files included
in our Zoomify Flash product using a Flash editor. Please
do not attempt to remove the logo from the Zoomify Express
viewer or the Viewer included with Zoomify Export as its presence
is what makes continued availability of our free Viewers possible.
To remove the logo in the Viewers in Zoomify Design simply
set the zoomifySplashscreen and zoomifyToolbarLogo HTML parameters
to '0'. This is also possible via the XML parameters. To replace
the logo in the Viewers using Zoomify Flash simply open the
relevant '.FLA' source file in your Flash editor, use the
Window menu to open the Library pane, right-click any folder
item in the Library and select Expand All Folders, then scroll
down to find the relevant elements. These items can be right-clicked
to place them on the stage for editing.
top of section | top of page
Does
Zoomify Design include '.FLA' and '.AS' source files?
Yes. The Zoomify Flash product includes
the zoomifyViewer.fla file as well as FLA files for many examples.
Additional examples are available on request by contacting
our Support team and will be incorporated into future
revisions to the product.
top of section | top of page
What image formats does the Zoomify Converter support?
The Zoomify Converter natively supports TIF,
BMP, and JPEG formats. Numerous additional formats are supported
through the built-in Zoomify Export available in Adobe Photoshop
CS5, CS4, and CS3.
top of section | top of page
Can I batch convert images with the Zoomify Converter?
The Zoomify Converters included with Zoomify
Design, Zoomify Flash, and Zoomify Enterprise support 'batch'
image conversion. Simply drag-drop many files onto the converter
and it will automatically convert them one by one. Or, double-click
the converter and within the standard Open File dialog that
is presented, shift-click to select multiple image file names.
Note that the Zoomify Converter included with Zoomify Enterprise
also supports scripted conversion (the use of ASP, JSP, PHP,
or other scripting languages to instruct the Converter to
process a specific image). For information on how many images
can be batch converted at once please see the question 'How
many images can I batch convert at once?'. For information
on scripting the Enterprise Converter, please see the question
'How can I script
conversion of one file after another?'.
top of section | top of page
How many image files can I batch
convert at once?
The batch processing support of the Zoomify Converter allows a large number of image files to be simultaneously drag-dropped onto the converter or multi-selected within the Converter's standard file selection dialog (presented on double-click of the Converter). The exact number of image files that can constitute a batch is limited by the operating system. On both Windows and Macintosh the filenames and file paths are joined together into one long string of text that is passed into the Converter. This text can only contain a set amount of characters. To enable the largest possible batch size, use small image filenames and place all the images at the root of your system (C:\ on Windows). This typically allows batch processing of 50 to 100 images at one time.
top of section | top of page
Can I script or automate the Zoomify Converter?
Yes, however, this requires the Zoomify Converter
that is included in the Zoomify Enterprise product. This
feature is included in the Enterprise product because it is
most usefully implemented on a server as part of a scripted
image management system (as might be used by a classified
advertising web site, for example) and it therefore most commonly
requires Enterprise level (server-side) documentation and
support.
top of section | top of page
Can
I use Zoomify with vector graphics like vector map images?
Yes and no. Vector content in the form of a SWF
file can easily be used as a hotspot (label, overlay) within
the Zoomify Hotspot Viewer in 8 for our prior Zoomify Flash
product version (v3). Later Zoomify Hotspot Viewer versions
do not yet support hotspots in the file format '.swf' due
to complications related to Flash Player security changes.
More importantly, vector content cannot currently be converted
using the Zoomify Converter into a base image to be displayed
within the Zoomify Viewer.
The benefit of the Zoomify technology is in the
rapid, interactive viewing of bitmap (photo) files. This is
essential as bitmap images of any reasonable quality typically
make for very large files. Cutting these files into JPEG tiles
and doing so at many different tiers of resolution enables
the Zoomify Viewer to download only the small portion of the
image that is essential for the current view that has been
zoomed and panned to by the user. This ensures that each new
view will require only a download of perhaps 100k to 300k
regardless of whether the source image is 5 megabytes or 500
gigabytes in size.
Vector content, in contrast, is typically small
with respect to file size. It can be downloaded quickly and
scaled with the built-in functionality of the Flash Player.
In most cases Zoomify's tiled/tiered approach is not required.
Where one's vector content is exceptionally complex or broad
in scope - for example a street map for an entire city - tiling
and tiering would prove valuable. Zoomify has explored this
possible additional use and weighed the non-trivial vector
tiling requirement against the apparent demand and the development
has simply not been justifiable to-date. There are many other
features associated with much greater customer demand. We
are, however, interested in the value of such a feature addition
and we welcome your input about your needs and potential uses
for such a feature.
top of section | top of page
What steps should I take if I see errors during conversion?
First, make sure no other software programs are
running that present any opportunity for a conflict. Second
ensure sufficient memory and disk space are available (two
times the size of the image and three times the size of the
image, respectively). Third, delete all temp files (these
will have 'PFF' in the filename). Fourth, delete any copies
of zoomifyConvertPrefs.asp that are present on your system
(this file is created each time the Converter is run, and
in current versions will be directly next to the Converter
application). Fifth, test with a new image freshly created
in your image editor. Be sure it is saved in the RGB color
space, is 8-bit, and is in format like TIF, JPEG, or BMP.
Finally, if you still see errors, test on a different system
if you can. Let us know the results
of your tests, we're standing by to help.
top of section | top of page
Can
I have one Zoomify Viewer SWF file for all my Zoomify Images
on my web site?
Absolutely. Simply put the Zoomify Viewer '.swf'
file wherever you prefer on your server and change the 'SRC'
path in the Flash Player embed statement in your web page(s)
accordingly. Be sure to make the change in TWO places in your
web page (once for Windows IE users, once for everyone else).
The SWF file in your image folder is there only as a convenience
in the export process and can be deleted. Please see the demos
on the Zoomify web site as well as the eample web pages in
each Zoomify product for example HTM.
top of section | top of page
Can
I have one HTML page for all my Zoomify Images on my web site?
Yes. We even include an example in our Zoomify
Design and Zoomify Flash products. It uses a 'URL-Driven Web
Page' - that is, a page that can parse its own calling URL
to find the Zoomify Image to display. For example, your home
page might have a link:
myPopUpPage?images/myFavoriteImage
such that when that link is clicked, a special
'URL-Driven' page named 'myPopUpPage' is called. That page
contains Javascript that is able to see the pages own URL,
find the '?', capture the string that follows 'images/myFavoriteImage
and use that value to create the HTML on-the-fly that tells
the Zoomify Viewer to show that image.
This approach means you can have one web page
for displaying Zoomify Images that can be called from any
page on your site.
top of section | top of page
Can I place my Zoomify Content on more than one domain?
Yes. Placing Zoomify Images on a domain different
from the domain that your zoomifyViewer.swf file is on simply
requires using a 'cross-domain policy file'. For complete
details on how to do this, see the question 'How
can I use a cross domain policy file to allow content on multiple
domains?'.
top of section | top of page
What
features of the Zoomify Viewers can be customized with HTML
or XML parameters?
The exact HTML and XML parameters supported by
each Zoomify Viewer differ according to the features of the
Viewer. These are described in detail in the 'READ ME FIRST.txt'
file that is included in each Viewer folder. A general listing
is also included on the Zoomify Design
product page. The parameters of the Viewers are the same whether
included in the Zoomify Design product or the Zoomify Flash
product, however, with the '.FLA' and '.AS' source files included
in the Zoomify Flash product and a Flash editor, you can add,
modify or remove HTML or XML parameters at will.
top of section | top of page
Do
the Zoomify Viewers support skinning?
Yes. The Zoomify Viewers included in the Zoomify
Design and Zoomify Flash products support HTML and XML parameters
that can be used to specify the paths to image files to be
used to skin the Zoomify Toolbar. Additionally, direct replacement
of the graphic library elements of the Zoomify Components
that make up the Zoomify Viewers is possible with the '.FLA'
and '.AS' source files included in the Zoomify Flash product.
This direct approach requires a Flash editor but avoids the
need to load image files each time the Zoomify Viewer launches.
top of section | top of page
Can
I use JavaScript to control the Zoomify Viewers?
Using Javascript to talk into a 'smart client'
such as Flash Player is always enticing and always a challenge.
This is not an issue specific to Zoomify. The many browsers
and browser versions support different communication means
(both inward and outward) and each means presents different
level of control and reliability. Two starting points for
exploring the possibilities include the FSCommand
support of Flash Player 7 and earlier and the ExternalInterface
class introduced in Flash Player 8 (the former being relevant
to Zoomify Flash and earlier, the latter to later Zoomify
product versions). In each case Flash editing of Zoomify Viewer
source code will be required. For this reason the Zoomify
Flash product is needed rather than the Zoomify Design product.
top of section | top of page
Do
the customizable features include Navigator and Toolbar sizes
and placement?
Of course. All the Zoomify Components in the
Zoomify Viewer - Viewer, Toolbar, and Navigator - can be manually
sized and positioned on the stage of the Flash editor or automatically
sized and positioned using ActionScript. See the question
'How can I move the
Zoomify Toolbar or the Zoomify Navigator window off the image
display area?' for more information on automatic layout
options.
top of section | top of page
How
can I remove or replace the Zoomify splash screen and Zoomify
Toolbar logo?
The Zoomify logo is present in all Zoomify products
by default. It can be removed in all products other than our
free Zoomify Express product and and the Zoomify Viewer that
is included in the Zoomify Export feature provided in Adobe
Photoshop CS5, CS4, and CS3. It can be replaced in the Viewers
using the editable '.FLA' and '.AS' source files included
in our Zoomify Flash product using a Flash editor. Please
do not attempt to remove the logo from the Zoomify Express
viewer or the Viewer included with Zoomify Export as its presence
is what makes continued availability of our free Viewers possible.
To remove the logo in the Viewers in Zoomify Design simply
set the zoomifySplashscreen and zoomifyToolbarLogo HTML parameters
to '0'. This is also possible via the XML parameters. To replace
the logo in the Viewers using Zoomify Flash simply open the
relevant '.FLA' source file in your Flash editor, use the
Window menu to open the Library pane, right-click any folder
item in the Library and select Expand All Folders, then scroll
down to find the relevant elements. These items can be right-clicked
to place them on the stage for editing.
top of section | top of page
Can
I customize the Zoomify Toolbar?
Yes. The Zoomify Toolbar can easily be skinned
using HTML and XML parameters. These parameters are supported
by all of the many Zoomify Viewers included in the Zoomify
Design and Zoomify Flash products. Additionally, the Zoomify
Toolbar can also be edited directly using a Flash editor and
the '.FLA' and '.AS' source files included in the Zoomify
Flash product. This additional level of control allows addition
or removal of buttons, modification of the functionality of
any of the buttons, and more.
top of section | top of page
Can I change the background color of the Zoomify Viewers?
Yes. The background color is visible whenever
and image's aspect ratio does not match that of the display
area or when the image is zoomed out to a point that allows
space beyond any edge of the image to be viewed. In versions
of the Viewer Component prior to v4 it is also possible to
pan an image beyond the edge of the view area in any direction
which also causes the background color to become visible.
Two steps are required to change the background color in versions
3 and earlier of the Zoomify Viewer Component. Only the first
step is required in versions 4 and later.
First, set the background color of the Flash
Player itself using the Player's built-in support for the
BGCOLOR parameter. This and additional parameters are described
in detail in TechNote
12,701 on the Adobe web site. (Note that this step is
not necessary where the Zoomify Viewer Component does not
cover the full extent of the Flash project and the area not
covered is not intended to have a background color different
from the web page.)
Second, open the Flash project and right-click
the Zoomify Viewer Component. Select Edit In Place and then
carefully move the various layers of the Viewer to one side
to expose the background layer. This object is a movieclip,
the color of which must be changed manually at Flash authoring
time, or via ActionScript. (Note that in v4 of the Zoomify
Viewer component and later this step is not required. The
Flash Player background color will automatically display as
the background color of whatever image is displayed.)
top of section | top of page
Can
I turn off pan constraints so a view can center on an image
edge or corner?
Beginning with version 4, the default behavior
of the Zoomify Viewer is to constrain image pan to ensure
the image does not leave the view area. This behavior can
be disabled using the zoomifyPanConstrain HTML parameter which
is documented in the 'READ ME FIRST.txt' file in each Viewer
folder in the product. This property can also be set via XML
parameter. Example web page implementations are also included
with each Viewer in the 'HTML & XML Examples' subfolder.
top of section | top of page
Do
the Zoomify Viewers support localization?
All Flash projects provide some inherent degree
of localization support, however, such support has been less
relevant to Zoomify's Viewers and Components than is the case
with many other software programs. This is largely due to
the fact that the Zoomify technologies are predominantly image
content-focused, rather than text-based. As a result, very
little localization is required in most cases. Areas of greatest
relevance likely include Viewers presenting Slide or Hotspot
choicelists or those displaying captions or tooltips, which
are XML-driven with proper ActionScript escaping (management
of special characters) so projects built on these Viewer '.AS'
source files are not expected to present any significant difficulty
for implementations in other languages - or at a minimum,
those presented in horizontal aspect. To support and simplify
localization in these areas every attempt has been made to
organize error, default, and other text strings in the Resources.as
source file, as well as in the relevant slides.xml, hotspots.xml,
and other data resource text files.
top of section | top of page
Where
can I see demos of all the different Zoomify Viewers?
The Zoomify web site has demonstrations of every
Zoomify Viewer. Although the Viewers themselves are included
in both the Zoomify Design and Zoomify Flash products you
can find the demos on the Zoomify Design
web page. The Zoomify Flash web page
presents demos of the sorts of Viewer customizations that
are possible with the editable source files that are included
in that product.
top of section | top of page
Can I combine the functionality of different Zoomify Viewers?
Yes, however, this will require the Zoomify
Flash product and a Flash editor. The Zoomify Design product
is tailored to the needs of web designers who don't wish to
pursue Flash editing, but rather, prefer to customize Viewer
layout and behavior using HTML and XML parameters. These parameters
are specific to each Viewer and offer the ability to change
an individual Viewer, not move behaviors between Viewers.
The Zoomify Flash product includes complete '.FLA' and '.AS'
source files to enable this deeper level of customization
control.
top of section | top of page
How do I decide what numbers to use for hotspot coordinates?
Selecting the X and Y coordinates at which to
place a hotspot is as simple as counting the pixels from the
left edge and the top edge of the source image. This can be
accomplished most easily by opening your source image in an
image editor such as Adobe Photoshop. Most image and photo
editors include an information panel presenting the current
X and Y position of the cursor over the image. This is the
value needed for your hotspot. An alternative is to estimate
the coordinates of the desired position, edit and save the
hotspots.xml file, load the web page presenting the Zoomify
Hotspots Viewer in your browser, and then modify and resave
the hotspots.xml and reload the web page until the positioning
is as intended. When estimating simply remember that the left
edge of the image is pixel 0 and the right edge is the full
pixel width of the image - for example 1000 on a 1000 pixel-wide
image. Similarly the top edge is 0 and the bottom - of a 1000
pixel tall image - would be 1000. In this example the center
point would be X=500 and Y=500.
PRIOR VERSION NOTE: The prior version of Zoomify Flash ('Zoomifyer
for Flash v3') presented two means to specify X and Y coordinates:
'resolution independent coordinates' or pixel coordinates'.
Zoomify's hotspot component, available in the prior product
version, makes use of the former scheme, while later examples
employ the latter, more intuitive approach.
To work with the hotspot component, it is simplest
to use the custom component inspector interface of the Hotspot
Component to place hotspots. This visual interface also displays
the applied resolution independent coordinates (though manual
entry is not required). However when working with the Zoomify
Hotspot Viewer example of the prior version of Zoomify Flash,
coordinates in the hotspots.xml text file are entered as pixel
values - as with the current version of Zoomify Flash.
Lastly, note that in the prior version of Zoomify
Flash, when using ActionScript to position hotspots or otherwise
interact with an image, conversion between the two coordinate
models can be managed using conversion scripts provided in
the answer to the question 'How
can I convert from resolution independent to pixel coordinates?'
top of section | top of page
Can
I customize the Slideshow, Hotspot, and other Viewers?
Absolutely. The Zoomify Viewers included in Zoomify
Design and Zoomif Flash can be customized using extensive
HTML and XML parameters. Additionally Zoomify Flash includes
the editable '.FLA' and '.AS' source files enabling customizaion
of layout and functionality as well as creation of totally
custom viewing solutions. And Zoomify Flash is built using
Zoomify Components and a powerful ActionScript API. This makes
integration of zoom-and-pan in your own projects straightforward
and efficient.
PRIOR VERSION NOTE: The Zoomify Slideshow, Hotspot, and other
components released with the prior version of Zoomify Flash
('Zoomifyer for Flash v3') present custom component inspectors
that are implemented within the Adobe Flash editing tools
using a special Live Preview feature of Flash. This preview
capability provides an intuitive visual interface for the
Slideshow and Hotspot components. It is, unfortunately, precompiled
during creation of the Zoomify components. In short, the Slideshow
and Hotspot components provide ease of use with some limitation
of control.
More specifically, the values entered into these custom property
inspectors via the fields and other interface elements presented
are held in memory until the FLA is published and the designer's
SWF is created. At that time the values as well as the associated
functionality the relate to are automatically and transparently
incorporated into the designer's SWF. These values and their
associated ActionScript, movieclips, etc. are not exposed
in the designer's FLA and cannot be edited. The custom property
inspectors present specific functionality that allows rapid
creation of specific effects but they do not enable customization
of that functionality beyond what is made possible by the
choices presented within the custom property inspector interface.
For designers and developers requiring complete control of
their projects Zoomify now provides the Zoomify Slideshow
Viewer and Zoomify Hotspot Viewer example projects - complete
with FLA source files. These examples are based on the Zoomify
Viewer Component, Toolbar Component, and underlying Zoomify
ActionScript API. This makes these project flexible and fully
customizable. In addition, these projects are xml-driven -
the slide names, hotspot coordinates, and other data are simply
typed into a text file rather than being entered into a component
inspector. As a result, designers and developers enjoy significant
control of the slideshow and hotspot presentations without
any Flash editing and complete control of features and functionality
should they choose to customize the project FLA files.
top of section | top of page
How can I make Hotspots open in the same window?
The Zoomify Hotspots Viewer supports a simple
HTML and XML parameter to specify the target of a hotspot
click. This parameter supports standard values such as '_self'
and '_blank'. The use of this parameter is documented in the
'READ ME FIRST.txt' file in each Viewer folder in the product.
This property can also be set via XML parameter. Example web
page implementations are also included with each Viewer in
the 'HTML & XML Examples' subfolder.
PRIOR VERSION NOTE: In the prior version of Zoomify
Flash ('Zoomifyer for Flash v3') the mouse click behavior
of Zoomify hotspots makes use internally of the Flash Player's
built-in 'getURL' function. This function supports two parameters:
the URL to open, and the target window to open it into. The
second parameter is specified as '_blank' (representing a
new window) by default. This parameter's value is hardcoded
in the prior version and can only be changed by editing the
source code of the Zoomify Viewer component. The value can
be set to '_self' (representing the current window) by following
this steps:
Open zoomifyHotspotViewer.fla in a Flash editor.
On the Flash editor's menu select Window | Library.
Right-click the ZoomifyViewer Component and select Expand.
Right-click the item Label Infrastructure and select Expand.
Right-click the item LabelText_Text_mc and select Edit.
Select Layer 1, Frame 1, and from the Flash editor's menu select Window | the Actions.
Find this line (typically line 21 or line 47):
getURL(this.gZoomifyURL,"_blank");
Replace _blank with _self.
Publish a new SWF and all future mouse-clicks will open in the same (current) window.
top of section | top of page
How can I make Hotspots do something other than open a URL link?
The Zoomify Hotspot Viewer's support for hotspot
mouse clicks is implemented using the Flash Player's built-in
navigateToURL method. The method call can be replaced with
a call to any function in order to change the default mouse-click
behavior. Making this change requires the Zoomify Flash product
and a Flash editor. For additional information see the same
question, 'How can I make Hotspots
do something other than open a URL link?', under the Zoomify
Flash product listing.
top of section | top of page
What file formats can be used for Zoomify Hotspots?
Supported file formats for hotspots media include
those supported by Flash Player - PNG, GIF, and JPG in Flash
Player 9. Use PNG files if support is required for transparency.
Note that SWF files have been supported in prior versions
('Zoomifyer for Flash v3') however this support has been temporarily
removed pending review of the implications of recent Flash
Player security changes related to active media being dynamically
loaded at runtime.
top of section | top of page
How can I hide or show all hotspots?
This functionality requires custom ActionScript
development using a Flash editor and the '.FLA' and '.AS'
source files included in the Zoomify Flash product. In fact,
a pre-built example is included in that product in the 'Developer
Examples' folder titled 'Hide-Show All Hotspots'. This example
includes source code.
top of section | top of page
How can I hide or show individual hotspots?
This functionality requires custom ActionScript
development using a Flash editor and the '.FLA' and '.AS'
source files included in the Zoomify Flash product. In fact,
a pre-built example is included in that product in the 'Developer
Examples' folder titled 'Hide-Show One Hotspot'. This example
includes source code.
top of section | top of page
How
can I change properties of individual hotspots?
Property changes of individual hotspots require
custom ActionScript and thus a Flash editor and the '.FLA'
and '.AS' source files included in the Zoomify Flash product.
For more information on this topic see the same question,
'How can I change properties of individual
hotspots?' in the Zoomify Flash section below.
top of section | top of page
Why do Hotspots seem to shift position slightly at extreme zoom?
Very large images present a special challenge with respect to the accurate placement of hotspots. This is due at least in part to the fact that the coordinates for a hotspot will have to be extremely exact - and in some cases, more exact than Flash Player may allow.
The basic unit of measure for coordinates in Flash is 1/20-th of a screen pixel, or a TWIP. Coordinates with finer precision than .05 are simply rounded to the nearest .05. The fractional pixel positions are approximated using anti-aliasing. This would not normally present a problem, but with the extreme range of resolutions in the Zoomify Viewer, and the fact that the label "tier" (i.e. layer) has to correspond to the lowest resolution "tier" the coordinate calculations can result in th rounding process creating a noticable shifting effect as an image is panned slightly in one direction and then back again.
Zoomify is working to implement an alternate approach in upcoming releasese which, it is expected, will resolve this issue through forced, smooth, miniscule readjustment of image pan positions to allow exact placement of hotspots and avoidance of any need to exceed the supported degree of precision.
top of section | top of page
Can I add hotspots in Viewers other than the Zoomify Hotspot Viewer?
Adding hotspots in Viewers other than the Zoomify
Hotspot Viewer (and other Viewers that support hotspots such
as the Watermark, Tour, and Geo Viewers) requires moving ActionScript
from one Viewer to another followed by recompiling the target
Viewer. This requires a Flash editor and the '.FLA' and '.AS'
source files included in the Zoomify Flash product. For more
information on this topic see the same question, 'Can
I add hotspots in Viewers other than the Zoomify Hotspot Viewer?'
in the Zoomify Flash section below.
top of section | top of page
What are the alerts presented when switching between Normal and Full Screen viewing modes?
Two alerts are presented when switching between viewing modes.
The first is displayed by the Flash Player. It reminds the
user that the Escape key can be used to exit Full Screen mode.
This was implemented by Adobe in anticipation of the possibility
that a clear means to return to normal viewing mode might
not always be presented in projects created by Flash developers.
The second alert, presented directly below the first, notes
that an initial click is required to activate the new mode
- whether Full Screen or Normal. This is necessary because
a click-drag will cause an unintended behavior (view scaling
not under the control of the Zoomify Viewer) if not preceded
by an initial click. That is, attempting to pan prior to clicking
the view in the new mode will create unexpected consequences
and potential errors. Zoomify is monitoring reports to Adobe
related to Full Screen / Normal mode changes. As quickly as
the source of this issues is identified and addressed an update
wil be developed. Additional information will be posted to
the Zoomify web site as it becomes available.
top of section | top of page
How are the Zoomify Slideshow and Zoomify Gallery Viewers different?
Both the Zoomify Slideshow Viewer and Zoomify
Gallery Viewer provide sequential viewing of Zoomify Images.
Both present an enhanced Slideshow Toolbar and a choicelist
of Slides for easy navigation. To these features the Gallery
Viewer adds a Zoomify Gallery Scrollbar that supports navigation
just like the Slides choicelist, but with a thumbnail image
of each Slide as a preview of the Zoomify Images available
for viewing. Note that the Gallery Scrollbar can be positioned
at the bottom or top of the Gallery Viewer using an HTML or
XML parameter, and like the Slides choicelist, it can be turned
off.
top of section | top of page
Can I specify rotation values over 360 degrees in the Zoomify Rotation Viewer?
Absolutely. Values over 360 degrees will be
automatically converted internally to the appropriate value
under 360.
top of section | top of page
Can I specify negative rotation values in the Zoomify Rotation Viewer?
Yes. Values below 0 will be automatically converted
internally to the appropriate value between 0 and 360. Note
that clicking the Reset Initial View button will initiate
a zoom-to-view transition to the initial X, Y, Zoom, and rotation
values, and that the shortest path will be taken. For example,
if the current rotation is 185 degrees and the initial rotation
was 0 degrees, the view will rotate clockwise in returning
to 0. However, if the current rotation is 175 degrees, the
view will rotate counter-clockwise in returning to 0.
top of section | top of page
Can I specify rotation values radian rather than degress in the Zoomify Rotation Viewer?
Unfortunately, no. Values in degrees are expected
by the Zoomify Rotation Viewer. Customization of the underlying
ActionScript to autoconvert internally from radian parameter
inputs to degrees is certainly possible and would not be difficult.
Editing the ActionScript source code would require a Flash
Editor and the '.FLA' and '.AS' source files available in
the Zoomify Flash product.
top of section | top of page
Can the Zoomify Geo Viewer be used with coordinate systems other than latitude and longitude?
As delivered, the Zoomify Geo Viewer expects
parameter inputs in latitude and longitude. Modifying the
internal methods to support an alternative matrix or grid
system is certainly possible. This would, however, require
editing the ActionScript source code which would require a
Flash Editor and the '.FLA' and '.AS' source files available
in the Zoomify Flash product.
top of section | top of page
Zoomify
Flash
How do I install Zoomify Flash?
No install is necessary with the exception of
the Zoomify Components. Simply download the product from the
link provided during the online purchase process, unzip it,
and you're ready to use the PDF User's Guide, HTML Zoomify
API Reference, Zoomify Converter, Examples, and more. To install
the Zoomify Components (so that they will appear on the Components
list within the Adobe Flash editing environment, simply run
the appropriate installer MXP file: ZCompInstaller-CS3.mxp,
ZCompInstallHot-CS3.mxp, ZCompInstaller-CS4.mxp, or ZCompInstallHot-CS4.mxp,
ZCompInstaller-CS5.zxp, or ZCompInstallHot-CS5.zxp.
The Zoomify Component MXP installers use Adobe Extension Manager
to copy a Zoomify Components file into the an Adobe Flash
subfolder. This ensures that the Zoomify Components appear
in the Components Panel within the Adobe Flash authoring environment.
The Extension Manager is included in the Adobe Flash product
and is also available for free download from the Adobe web
site. Additional information is available in the 'READ ME
FIRST.txt' file in the Component Installers folder.
PRIOR VERSION NOTE: The prior version of Zoomify
Flash ('Zoomifyer for Flash v3') provided a greater degree
of integration into the Adobe Flash editing environment. Several
features are accessible within Flash IDE. Installers are included
for Flash MX, MX 2004, and Flash 8. While the features provided
and the related installation process do provide significant
functional convenience, the level of integration provided
is complex to support and can result in installer errors depending
on the context. Should you encounter any difficulties whatsoever
please see the questions 'I'm
using Flash MX or MX2004 and see an installation error. How
can I fix this?' or 'I'm
using Flash 8 and seeing errors during install. What can I
do?'.
top of section | top of page
Is
there an installer for Flash 8, MX 2004, or MX?
We've created a special installer for Flash 8
that corrects the difficulties caused by changes in the Flash
folder structure organization. This is included in the standard
product download. Note that this is no longer a custom installer.
Rather, it is an extension installer 'package' that automatically
runs within the Macromedia Extension Manager when double-clicked.
If you have not received this as part of your product download,
please contact Zoomify Support.
The package will place numerous elements of Zoomify Flash within the Flash 8 interface. The Zoomify Flash Components will appear on the Window | Components menu. Detailed Zoomify API information will appear on the Help Panel accessible via the Help menu. Zoomify Commands will appear on the Commands menu and Zoomify Behaviors on the Window | Behaviors menu. Zoomify Developer Examples will appear on the Window | Other Panels menu.
Additional note for Macintosh customers: A prior
release of the product for the Macintosh platform may have
included converter and file access files that will not properly
install. If you encounter errors when using the integrated
Convert and Browse buttons, the situation can be easily corrected
by manually replacing two files. Simply copy the Zoomify Converter
from the root level of the main product download as well as
the ZoomifyFileAPI.dll in the Developer Tools | Installer
Support Files folder in the same download. Paste both of these
files into your External Libraries folder under Hard Drive:Users:Library:Application
Support:Macromedia:Flash8:en:Configuration. (If the folder
External Libraries does not exist simply create it.) Replacing
these files will ensure that everything is in place intact
and the cause of the errors is removed.
top of section | top of page
Is there a trial version available?
Our free product, Zoomify Express, substitutes for
a trial product and can be downloaded from our home page or
here: Win
| Mac.
This product demonstrates drag-and-drop image conversion and
intuitive Flash-based zoom-and-pan viewing and is ideal for
web designers needing a quick and simple way to include high-quality
images in their sites - whether private or public, personal
or commercial. Customers requiring a means to more deeply
evaluate the specific features of Zoomify Flash may
contact our Support team at the address provided below
for receipt of evaluation a copy of that product on a case-by-case
basis.
top of section | top of page
What versions of the Flash editor does Zoomify Flash support?
Zoomify Flash can be used with Flash
MX, MX 2004 and Flash 8. Version 4 has been completely rewritten
for Flash 9. (All purchases during or after December of this
year include a free upgrade. Prior purchasers may upgrade
for a small fee.)
top of section | top of page
Does Zoomify Flash work with Dreamweaver?
Absolutely. Dreamweaver allows web designers
to easily and productively create web pages and support for
Flash - and thus for Zoomify - is a key benefit of working
with Dreamweaver. A common frustration, however, is that Dreamweaver's
support for Flash Player is not absolutely complete.
The most important example of this incomplete
support is that Dreamweaver does not present the 'FlashVars'
parameter - which is natively supported by Flash Player -
in its properties palette for Flash objects. The FlashVars
parameter is very useful because it allows a web page to pass
a value into a Flash movie for that movie to use internally.
The FlashVars parameter is how any web page tells the Zoomify
Viewer what Zoomify Image to display.
In practice, the fact that Dreamweaver's Flash
object properties palette doesn't present the FlashVars parameter
for entry simply means that Dreamweaver users must briefly
switch from Design View to Code View and manually type in
the parameter in the page's HTML. This is not immediately
clear, however, so many Dreamweaver users add their Flash
object - the Zoomify Viewer - set its size and position, and
then are disappointed when they view the resulting page and
the Zoomify Viewer does not display their image.
This situation can be easily remedied by simply
viewing the HTML of any demo on the Zoomify web site and mimicking
the placement of the FlashVars parameter and its value in
the web page. (And be certain to include it twice - as with
all Flash Player parameters, their is one instance for Windows
IE users and a second instance for everyone else.)
top of section | top of page
What versions of ActionScript does Zoomify Flash support?
Version 4 of Zoomify Flash has been completely
rewritten using ActionScript 3.0 and is designed for use with
Adobe Flash CS5, CS4, or CS3 and Flash Player versions 9 or
newer.
PRIOR VERSION NOTE: The prior version of Zoomify
Flash ('Zoomifyer for Flash v3') was developed for Flash 8,
MX 2004, and MX and Flash Player versions 6 and newer. The
underlying Zoomify Components were created using ActionScript
1.0.
top of section | top of page
Does
Zoomify Flash support ActionScript 1.0, 2.0, or 3.0?
Version 4 of Zoomify Flash has been completely
rewritten using ActionScript 3.0 and is designed for use with
Adobe Flash CS5, CS4, or CS3 and Flash Player versions 9 or
newer.
PRIOR VERSION NOTE: The prior version of Zoomify
Flash ('Zoomifyer for Flash v3') was developed for Flash 8,
MX 2004, and MX and Flash Player versions 6 and newer. The
underlying Zoomify Components were created using ActionScript
1.0.
top of section | top of page
How
can I remove or replace the Zoomify splash screen and Zoomify
Toolbar logo?
The Zoomify logo is present in all Zoomify products
by default. It can be removed in all products other than our
free Zoomify Express product and and the Zoomify Viewer that
is included in the Zoomify Export feature provided in Adobe
Photoshop CS5, CS4, and CS3. It can be replaced in the Viewers
using the editable '.FLA' and '.AS' source files included
in our Zoomify Flash product using a Flash editor. Please
do not attempt to remove the logo from the Zoomify Express
viewer or the Viewer included with Zoomify Export as its presence
is what makes continued availability of our free Viewers possible.
To remove the logo in the Viewers in Zoomify Design simply
set the zoomifySplashscreen and zoomifyToolbarLogo HTML parameters
to '0'. This is also possible via the XML parameters. To replace
the logo in the Viewers using Zoomify Flash simply open the
relevant '.FLA' source file in your Flash editor, use the
Window menu to open the Library pane, right-click any folder
item in the Library and select Expand All Folders, then scroll
down to find the relevant elements. These items can be right-clicked
to place them on the stage for editing.
top of section | top of page
Does
Zoomify Flash include '.FLA' and '.AS' source files?
Yes. The Zoomify Flash product includes the ZoomifyViewer.fla
file as well as FLA files for many examples. Additional examples
are available on request by contacting
our Support team and will be incorporated into future
revisions to the product.
top of section | top of page
Do Zoomify
Components use ActionScript methods or custom methods?
Both. The Zoomify Components make extensive use
of ActionScript methods. In addition, the ActionScript methods
are the basis for the Zoomify ActionScript API - a set of
methods with functions specific to loading, displaying, and
working with high-quality image content in a dynamic, interactive
way.
top of section | top of page
How do I set the properties of Zoomify Components without using ActionScript?
The Zoomify Components each include a standard
property inspector that allows key component properties to
be set within the Flash design environment. No ActionScript
is required to set the size or position of the components,
or properties such as the image to be displayed by the Zoomify
Viewer Component.
top of section | top of page
How do I set the properties of Zoomify Components using ActionScript?
The Zoomify ActionScript API lists numerous 'set'
methods, including but not limited to setViewX(), setViewY(),
setViewZoom(), setView(), setInitialX(), setInitialY(), setMinZoom(),
and setMaxZoom(). Please consult the Zoomify
ActionScript API Reference Index for a complete listing
of these methods as well as the numerous 'get' methods and
other useful functions such as zoomToView().
top of section | top of page
What support
do Zoomify components provide for accessibility?
Zoomify's Components, Viewers, and examples rely
on the built-in accessibility support of Flash Player including
combined mouse and keyboard support though not including special
audio or text-relevant features. Many enhancements are possible
given the latest capabilities of Flash.
Zoomify is actively exploring improved navigation
options that may be of use to users needing alternatives to
standard keyboard and mouse support. Additionally, we are
aware that the Zoomify Annotation System, with its text fields
and Edit mode, presents possibilities for improved accessibility.
We welcome input
about how these products can become more useful and more usable.
top of section | top of page
How much overhead do Zoomify Components add to my Flash projects?
Each of the Zoomify Components is quite small,
in fact, the most commonly used components including the Zoomify
Viewer, Toolbar, and Navigator can be added to a Flash project
as a group and contribute less than 20k to the project's total
size. The components can, of course, be reduced in size, by
removing code related to features not required for a specific
project. This should, however, only be attempted by Flash
developers reasonably comfortable with ActionScript as well
as with editing the ActionScript or other programming code
of others.
top of section | top of page
How can I make a screensaver with Zoomify?
The Zoomify Viewer includes support for a powerful
yet intuitive set of methods that make up the Zoomify ActionScript
API. Included in these is the method zoomToView(). This method
takes several parameters: an x, y, and zoom coordinate, a
number of steps to make from the current view to the new coordinates,
and an interval of time over which to spread those steps.
Using this function and the random number generation as well
as the 'interval support in ActionScript it is a simple matter
to create a function that starts a time-based process which
repeatedly repositions the view to some new are of the image
at some new level of zoom.
As an alternative, the Zoomify Slideshow Viewer
or Zoomify Tour Viewer - included in the Zoomify Design and
Zoomify Flash products - could be used to cycle through different
images or different views of the same image. As these are
ready-made Viewers they may suffice for many uses.
Each of the above approaches does involve having
a browser loaded - to avoid this a 'projector' would be needed.
This is a standalone Flash movie that can play without a web
browser. For more information on Flash projectors, please
see the 'LiveDocs' available on the Adobe web site as well
as TechNote
14,231, also on the Adobe web site.
top of section | top of page
I'm
using Flash 8 and seeing errors during install. What can I
do?
We've created a special installer for Flash 8
for our prior Zoomify Flash product version (v3) that corrects
the difficulties caused by changes in the Flash folder structure
organization. This is included in the standard product download.
Note that this is no longer a custom installer. Rather, it
is an extension installer 'package' that automatically runs
within the Macromedia Extension Manager when double-clicked.
If you have not received this as part of your product download,
please contact Zoomify Support.
The package will place numerous elements of Zoomify Flash within the Flash 8 interface. The Zoomify Flash
Components will appear on the Window | Components menu. Detailed
Zoomify API information will appear on the Help Panel accessible
via the Help menu. Zoomify Commands will appear on the Commands
menu and Zoomify Behaviors on the Window | Behaviors menu.
Zoomify Developer Examples will appear on the Window | Other
Panels menu.
Additional note for Macintosh customers: A prior
release of the product for the Macintosh platform may have
included converter and file access files that will not properly
install. If you encounter errors when using the integrated
Convert and Browse buttons, the situation can be easily corrected
by manually replacing two files. Simply copy the Zoomify Converter
from the root level of the main product download as well as
the ZoomifyFileAPI.dll in the Developer Tools | Installer
Support Files folder in the same download. Paste both of these
files into your External Libraries folder under Hard Drive:Users:Library:Application
Support:Macromedia:Flash8:en:Configuration. (If the folder
External Libraries does not exist simply create it.) Replacing
these files will ensure that everything is in place intact
and the cause of the errors is removed.
top of section | top of page
I'm
using Flash 8 and see an error using the Zoomify features.
What can I do?
We've created a special installer for Flash 8
for our prior Zoomify Flash product version (v3) that corrects
the difficulties caused by changes in the Flash folder structure
organization. This is included in the standard product download.
Note that this is no longer a custom installer. Rather, it
is an extension installer 'package' that automatically runs
within the Macromedia Extension Manager when double-clicked.
If you have not received this as part of your product download,
please contact Zoomify Support.
The package will place numerous elements of Zoomify Flash within the Flash 8 interface. The Zoomify Flash
Components will appear on the Window | Components menu. Detailed
Zoomify API information will appear on the Help Panel accessible
via the Help menu. Zoomify Commands will appear on the Commands
menu and Zoomify Behaviors on the Window | Behaviors menu.
Zoomify Developer Examples will appear on the Window | Other
Panels menu.
Additional note for Macintosh customers: A prior
release of the product for the Macintosh platform may have
included converter and file access files that will not properly
install. If you encounter errors when using the integrated
Convert and Browse buttons, the situation can be easily corrected
by manually replacing two files. Simply copy the Zoomify Converter
from the root level of the main product download as well as
the ZoomifyFileAPI.dll in the Developer Tools | Installer
Support Files folder in the same download. Paste both of these
files into your External Libraries folder under Hard Drive:Users:Library:Application
Support:Macromedia:Flash8:en:Configuration. (If the folder
External Libraries does not exist simply create it.) Replacing
these files will ensure that everything is in place intact
and the cause of the errors is removed.
top of section | top of page
I'm using Flash MX or MX2004 and see an installation error. How can I fix this?
It is possible that some installations of Flash
MX or MX 2004 may cause the Zoomify installer for our prior
Zoomify Flash product version (v3) to be unable to locate
the proper folder for certain files. In these cases the Installer
will present an error. This has been reported with some international
installations as well as with some installations involving
a custom setup such as an uncommon drive letter or name. In
spite of our efforts to conform exactly to the specifications
of the Adobe (formerly Macromedia) installation paradigm,
we have not been able to identify the exact causes for these
problems. Accordingly, a workaround has been identified which
allows manual placement of the files in the appropriate locations.
The steps required are outlined in detail in the Zoomify Flash
User's Guide in the appendix titled 'Manual Installation of
Zoomify Flash'.
The most important step is to manually place
two files. These files are the Zoomify Converter which can
be found at the root level of the product download, and the
ZoomifyFileAPI.dll which will be found in the Developer Tools
| Installer Support Files folder in the product download.
Both of these files must be copied into your External Libraries
folder. The paths below indicate the likely location of the
External Libraries folder (substitute 'MX' for 'MX 2004' is
you have that version of the Flash editor):
On Windows: C:\Program Files\Macromedia\Flash
MX 2004\en\Configuration\. (Your drive designation may not
be C:.)
On Macintosh: Hard Drive:Users:Library:Application
Support:Macromedia:Flash MX 2004:en:Configuration.
(On both platforms, if the folder External Libraries
does not exist simply create it.) Placing these two files
correctly will ensure that the cause of most errors is removed.
top of section | top of page
The Help menu mentions an online product registration page,
do I need that?
No. That reference is outdated and has been removed
in subsequent documentation revisions. The Zoomify online
store includes the contact information necessary for Zoomify
to notify you of product updates or upgrades. Please note
that Zoomify does not share or sell customer information and
holds it in the strictest confidence. Additionally, credit
card information is not retained beyond a brief processing
period, for the security of our customers.
top of section | top of page
What image formats does the Zoomify Converter support?
The Zoomify Converter natively supports TIF,
BMP, and JPEG formats. Numerous additional formats are supported
through the built-in Zoomify Export available in Adobe Photoshop
CS5, CS4, and CS3.
top of section | top of page
Can I batch convert images with the Zoomify Converter?
The Zoomify Converters included with Zoomify
Design, Zoomify Flash, and Zoomify Enterprise support 'batch'
image conversion. Simply drag-drop many files onto the converter
and it will automatically convert them one by one. Or, double-click
the converter and within the standard Open File dialog that
is presented, shift-click to select multiple image file names.
Note that the Zoomify Converter included with Zoomify Enterprise
also supports scripted conversion (the use of ASP, JSP, PHP,
or other scripting languages to instruct the Converter to
process a specific image). For information on how many images
can be batch converted at once please see the question 'How
many images can I batch convert at once?'. For information
on scripting the Enterprise Converter, please see the question
'How can I script
conversion of one file after another?'.
top of section | top of page
How many image files can I batch
convert at once?
The batch processing support of the Zoomify Converter allows a large number of image files to be simultaneously drag-dropped onto the converter or multi-selected within the Converter's standard file selection dialog (presented on double-click of the Converter). The exact number of image files that can constitute a batch is limited by the operating system. On both Windows and Macintosh the filenames and file paths are joined together into one long string of text that is passed into the Converter. This text can only contain a set amount of characters. To enable the largest possible batch size, use small image filenames and place all the images at the root of your system (C:\ on Windows). This typically allows batch processing of 50 to 100 images at one time.
top of section | top of page
Can I script or automate the Zoomify Converter?
Yes, however, this requires the Zoomify Converter
that is included in the Zoomify Enterprise product. This
feature is included in the Enterprise product because it is
most usefully implemented on a server as part of a scripted
image management system (as might be used by a classified
advertising web site, for example) and it therefore most commonly
requires Enterprise level (server-side) documentation and
support.
top of section | top of page
Can
I use Zoomify with vector graphics like vector map images?
Yes and no. Vector content in the form of a SWF
file can easily be used as a hotspot (label, overlay) within
the Zoomify Hotspot Viewer in 8 for our prior Zoomify Flash
product version (v3). Later Zoomify Hotspot Viewer versions
do not yet support hotspots in the file format '.swf' due
to complications related to Flash Player security changes.
More importantly, vector content cannot currently be converted
using the Zoomify Converter into a base image to be displayed
within the Zoomify Viewer.
The benefit of the Zoomify technology is in the
rapid, interactive viewing of bitmap (photo) files. This is
essential as bitmap images of any reasonable quality typically
make for very large files. Cutting these files into JPEG tiles
and doing so at many different tiers of resolution enables
the Zoomify Viewer to download only the small portion of the
image that is essential for the current view that has been
zoomed and panned to by the user. This ensures that each new
view will require only a download of perhaps 100k to 300k
regardless of whether the source image is 5 megabytes or 500
gigabytes in size.
Vector content, in contrast, is typically small
with respect to file size. It can be downloaded quickly and
scaled with the built-in functionality of the Flash Player.
In most cases Zoomify's tiled/tiered approach is not required.
Where one's vector content is exceptionally complex or broad
in scope - for example a street map for an entire city - tiling
and tiering would prove valuable. Zoomify has explored this
possible additional use and weighed the non-trivial vector
tiling requirement against the apparent demand and the development
has simply not been justifiable to-date. There are many other
features associated with much greater customer demand. We
are, however, interested in the value of such a feature addition
and we welcome your input about your needs and potential uses
for such a feature.
top of section | top of page
What steps should I take if I see errors during conversion?
First, make sure no other software programs are
running that present any opportunity for a conflict. Second
ensure sufficient memory and disk space are available (two
times the size of the image and three times the size of the
image, respectively). Third, delete all temp files (these
will have 'PFF' in the filename). Fourth, delete any copies
of zoomifyConvertPrefs.asp that are present on your system
(this file is created each time the Converter is run, and
in current versions will be directly next to the Converter
application). Fifth, test with a new image freshly created
in your image editor. Be sure it is saved in the RGB color
space, is 8-bit, and is in format like TIF, JPEG, or BMP.
Finally, if you still see errors, test on a different system
if you can. Let us know the results
of your tests, we're standing by to help.
top of section | top of page
Can
I have one Zoomify Viewer SWF file for all my Zoomify Images
on my web site?
Absolutely. Simply put the Zoomify Viewer '.swf'
file wherever you prefer on your server and change the 'SRC'
path in the Flash Player embed statement in your web page(s)
accordingly. Be sure to make the change in TWO places in your
web page (once for Windows IE users, once for everyone else).
The SWF file in your image folder is there only as a convenience
in the export process and can be deleted. Please see the demos
on the Zoomify web site as well as the eample web pages in
each Zoomify product for example HTML.
top of section | top of page
Can
I have one HTML page for all my Zoomify Images on my web site?
Yes. We even include an example in our Zoomify
Design and Zoomify Flash products. It uses a 'URL-Driven Web
Page' - that is, a page that can parse its own calling URL
to find the Zoomify Image to display. For example, your home
page might have a link:
myPopUpPage?images/myFavoriteImage
such that when that link is clicked, a special
'URL-Driven' page named 'myPopUpPage' is called. That page
contains Javascript that is able to see the pages own URL,
find the '?', capture the string that follows 'images/myFavoriteImage
and use that value to create the HTML on-the-fly that tells
the Zoomify Viewer to show that image.
This approach means you can have one web page
for displaying Zoomify Images that can be called from any
page on your site.
top of section | top of page
Can I place my Zoomify Content on more than one domain?
Yes. Placing Zoomify Images on a domain different
from the domain that your zoomifyViewer.swf file is on simply
requires using a 'cross-domain policy file'. For complete
details on how to do this, see the question 'How
can I use a cross domain policy file to allow content on multiple
domains?'.
top of section | top of page
Does
Zoomify include '.FLA' and '.AS' source files in its products?
Yes. Each of our products includes the '.FLA' and '.AS' source files for the viewing solutions provided including
the underlying Zoomify Components and Zoomify ActionScript
API. Source code is also included for supporting and/or optional
elements of each product such as our Zoomify Servlet for alternative
single-file 'PFF' image storage. Additional examples and sample
projects are provided as they become available and source
is provided for these as well.
top of section | top of page
What Zoomify
examples are available?
The Zoomify Design and Zoomify Flash products
include numerous examples tailored to the needs of designers
and developers including coverage of features of the various
Zoomify Viewers, alternative web page implementations, and
more.
top of section
| top of page
Where can
I get source files for the examples?
Complete '.FLA' and '.AS' source files are included
in the Zoomify Flash product.
top of section
| top of page
Can I get a copy of the Paris Concierge FLA file?
Yes. For download information contact
us with your name, product, and, preferably, purchase
date and order number.
top of section | top of page
What
features of the Zoomify Viewer can be customized with HTML
or XML parameters?
The exact HTML and XML parameters supported by
each Zoomify Viewer differ according to the features of the
Viewer. These are described in detail in the 'READ ME FIRST.txt'
file that is included in each Viewer folder. A general listing
is also included on the Zoomify Design
product page. The parameters of the Viewers are the same whether
included in the Zoomify Design product or the Zoomify Flash
product, however, with the '.FLA' and '.AS' source files included
in the Zoomify Flash product and a Flash editor, you can add,
modify or remove HTML or XML parameters at will.
top of section | top of page
What features
can be customized with the component inspector properties?
Each Zoomify component's position and size can
be set using standard property inspector fields. In addition,
the Zoomify Viewer Component includes property inspector values
for image path, initial x, y, and zoom, min and max zoom,
and more.
top of section | top of page
What features can be customized using the Flash editor's built-in tools?
The Zoomify Viewer, Zoomify Components, and Zoomify
examples are provided in both publishable SWF form and editable
source '.FLA' and '.AS' form. Flash designers and developers
therefore have complete control over every aspect of look,
feel, and functionality. All Library elements, ActionScript
classes, and external resourcs (example HTML and XML files,
example hotspots graphic files, etc.) are accessible and editable.
All features are therefore open to customization.
PRIOR VERSION NOTE: In the prior version of Zoomify
Flash ('Zoomifyer for Flash v3') an exception to the above
notes is presented by the Slideshow and Hotspot components.
These components were created with custom component inspector
'Live Preview' interfaces that are highly visual but somewhat
less open than our other components and example projects.
Live Preview interfaces involve the 'building-in' of precompiled
SWFs that serve as the visual front-end for setting properties
and preferences of the components. Because of this design
approach, they are to some degree 'black boxes'.
In order to support greater access and control
on the part of prior version customers an alternative to the
above mentioned Components was created. The Slideshow and
Hotspot example projects included in the Prior Version For
F8-to-MX | Documentation | Examples Volume 2 subfolder substitute
for these components. These projects offer similar features
in the form of SWF and fully editable FLA files. Designers
considering projects including slideshow or hotspot functionality
are encouraged to use these examples, rather than the related
components, as their starting point.
top of section | top of page
What features can be customized using ActionScript?
Flash ActionScript has grown in power to such
a degree that very little that can be done using the Flash
editing interface cannot be done using ActionScript methods.
Certainly all properties of the Zoomify Components can be
set or reset using ActionScript. Where a Zoomify ActionScript
API call is not provided, a workaround can be implemented
such as direct access of underlying variables or modification
of underlying ActionScript code - or a new API call can simply
be created. The Zoomify web site includes an index of the
Zoomify ActionScript
API.
top of section | top of page
Do the Zoomify Components support skinning?
The Zoomify Components in Zoomify Flash are designed
to support easy replacement of key graphic objects within
the Flash library of the Zoomify Viewers and other projects
containing the Zoomify Components. Versions of the Components
beginning with v4 include standardized skin elements that
conform to and support skinning as implemented in the Adobe
Flash CS5, CS4, and CS3 Components.
PRIOR VERSION NOTE: As with the current version
of Zoomify Flash (v4), the prior version of Zoomify Flash
('Zoomifyer for Flash v3') the Zoomify Components are designed
to support easy replacement of key graphic objects within
the Flash library of the Zoomify Viewers and other projects
containing the Zoomify Components. However, the skinning model
in this prior Zoomify Flash Component set conforms to the
approach common within earlier Flash Component releases.
top of section | top of page
Can
I use JavaScript to control the Zoomify Viewers?
Using Javascript to talk into a 'smart client'
such as Flash Player is always enticing and always a challenge.
This is not an issue specific to Zoomify. The many browsers
and browser versions support different communication means
(both inward and outward) and each means presents different
level of control and reliability. Two starting points for
exploring the possibilities include the FSCommand
support of Flash Player 7 and earlier and the ExternalInterface
class introduced in Flash Player 8 (the former being relevant
to Zoomify Flash and earlier, the latter to later
Zoomify product versions).
top of section | top of page
Can I change the look of the components without using ActionScript?
Yes. Each of the components is built using standard
Flash elements - movieclips, buttons, and so on - with snippets
of ActionScript strategically placed to enable automatic functionality.
Flash designers can easily edit the colors, shapes, and positions
of component elements.
Note 1: For the Zoomify Components to be manually edited the
must be dragged to the stage of a new Flash document or located
in the Library of an existing Flash document. The Zoomify
Viewers, for example, follow the Adobe standard practice of
creating instances of components at runtime using ActionScript.
The components will therefore not be found on the stage and
the elements of the components must be found within the project
library. The exception to this is the Components On Stage
example in the Developer Examples subfolder of Zoomify Flash.
This example presents a working Zoomify Viewer with the Zoomify
Viewer, Toolbar, and Navigator Components manually placed
and positioned on the stage (and the image path and other
parameters set within the Component Parameters panel).
Note 2: changing the behavior of the Components does require
editing ActionScript that implements the underlying functionality.
top of section | top of page
Do the customizable features include component sizes and placement?
Yes. All the Zoomify Components can be manually
sized and positioned on the stage of the Flash editor or automatically
sized and positioned using ActionScript.
Note: For the Zoomify Components to be manually edited the
must be dragged to the stage of a new Flash document or located
in the Library of an existing Flash document. The Zoomify
Viewers, for example, follow the Adobe standard practice of
creating instances of components at runtime using ActionScript.
The components will therefore not be found on the stage and
the elements of the components must be found within the project
library. The exception to this is the Components On Stage
example in the Developer Examples subfolder of Zoomify Flash.
This example presents a working Zoomify Viewer with the Zoomify
Viewer, Toolbar, and Navigator Components manually placed
and positioned on the stage (and the image path and other
parameters set within the Component Parameters panel).
PRIOR VERSION NOTE: In the prior version of Zoomify
Flash ('Zoomifyer for Flash v3') the Zoomify Viewer is created
with the Zoomify Components manually placed on the stage.
The Components can therefore be manually sized and placed
(as with the 'Components On Stage' example in the current
product mentioned above). To use ActionScript to customize
this prior version Viewer, see the question 'How
can I move the Zoomify Toolbar or the Zoomify Navigator window
off the image display area?' for more information on automatic
layout options.
top of section | top of page
How
can I move the Zoomify Toolbar or the Zoomify Navigator window
off the image display area?
Certainly, as noted in the answer to the prior
question 'Do the customizable features
include component sizes and placement?', the size and
position of the Zoomify Components can be customized in the
Zoomify Viewers either manually or using ActionScript, depending
upon whether they are placed on the stage at design time -
as with the 'Components On Stage' example - or at runtime
- as with all other Zoomify Viewers in the current product.
In the case of the Zoomify Viewers, the sizing and placing
of Zoomify Components is implemented in a method named 'onStageResizeHandler'
in the main class file ('ZoomifyDesignViewer.as', 'ZoomifySlideshowViewer.as',
'ZoomifyHotspotViewer.as', etc.). By modifying the values
in this method the size and position of the included Components
can be easily adjusted.
PRIOR VERSION NOTE: In the prior version of Zoomify
Flash ('Zoomifyer for Flash v3') the Zoomify Viewer is created
with the Zoomify Components manually placed on the stage.
To manually position the components simply open the FLA in
a Flash editor, drag the components to the locations you prefer,
and then be sure to comment out the lines of ActionScript
in the 'Actions' layer that automatically position the components
when the Viewer loads. This approach is simple, however, it
does present some limitations. A complete manual layout is
fixed and requires subsequent manual effort to modify the
layout.
As an alternative, the ActionScript in the 'Actions'
layer can be modified so that the automatic sizing and positioning
it implements better suits your intended design. For example,
where the ActionScript checks the width and height of the
stage and sets the width and height of the Viewer Component
to match, the code could be modified to set the height slightly
shorter. The lines of ActionScript that set the x and y coordinates
of the Viewer Component could then be modified to position
the Viewer so that some space is available below it for the
Toolbar. Similarly, the ActionScript that sets the x and y
coordinates of the Toolbar Component such that it is near
the bottom of the Viewer Component could be modified to position
it at or near the bottom of the stage instead. In this way,
the desired design is achieved while maintaining the ability
to set the view area using HTML parameters.
top of section | top of page
How
can I remove or replace the Zoomify splash screen and Zoomify
Toolbar logo?
The Zoomify logo is present in all Zoomify products
by default. It can be removed in all products other than our
free Zoomify Express product and and the Zoomify Viewer that
is included in the Zoomify Export feature provided in Adobe
Photoshop CS5, CS4, and CS3. It can be replaced in the Viewers
using the editable '.FLA' and '.AS' source files included
in our Zoomify Flash product using a Flash editor. Please
do not attempt to remove the logo from the Zoomify Express
viewer or the Viewer included with Zoomify Export as its presence
is what makes continued availability of our free Viewers possible.
To remove the logo in the Viewers in Zoomify Design simply
set the zoomifySplashscreen and zoomifyToolbarLogo HTML parameters
to '0'. This is also possible via the XML parameters. To replace
the logo in the Viewers using Zoomify Flash simply open the
relevant '.FLA' source file in your Flash editor, use the
Window menu to open the Library pane, right-click any folder
item in the Library and select Expand All Folders, then scroll
down to find the relevant elements. These items can be right-clicked
to place them on the stage for editing.
top of section | top of page
Can
I customize the Zoomify Toolbar?
Yes. The Zoomify Toolbar Component is simply
a collection of buttons and movieclips and it can easily be
modified by any Flash designer. The Toolbar Component contains
only limited ActionScript and that can easily be modified
by Flash developers. See the class ZoomifyToolbar.as for the
relevant methods (or the enhanced classes 'ZoomifySlideshowToolbar.as',
ZoomifyComparisonToolbar.as', etc.).
PRIOR VERSION NOTE: In the prior version of Zoomify
Flash ('Zoomifyer for Flash v3') the Toolbar Component in
the Zoomify Viewer is automatically sized and positioned by
ActionScript in the 'Actions' layer. Any custom sizing and
positioning performed manually will therefore be overridden
unless the relevant lines of ActionScript are modified or
commented out.
top of section | top of page
Can I change the background color of the Zoomify Viewers?
Yes. The background color is visible whenever
and image's aspect ratio does not match that of the display
area or when the image is zoomed out to a point that allows
space beyond any edge of the image to be viewed. In versions
of the Viewer Component prior to v4 it is also possible to
pan an image beyond the edge of the view area in any direction
which also causes the background color to become visible.
Two steps are required to change the background color in versions
3 and earlier of the Zoomify Viewer Component. Only the first
step is required in versions 4 and later.
First, set the background color of the Flash
Player itself using the Player's built-in support for the
BGCOLOR parameter. This and additional parameters are described
in detail in TechNote
12,701 on the Adobe web site. (Note that this step is
not necessary where the Zoomify Viewer Component does not
cover the full extent of the Flash project and the area not
covered is not intended to have a background color different
from the web page.)
Second, open the Flash project and right-click
the Zoomify Viewer Component. Select Edit In Place and then
carefully move the various layers of the Viewer to one side
to expose the background layer. This object is a movieclip,
the color of which must be changed manually at Flash authoring
time, or via ActionScript. (Note that in v4 of the Zoomify
Viewer component and later this step is not required. The
Flash Player background color will automatically display as
the background color of whatever image is displayed.)
top of section | top of page
How can I make sure my image is completely clear when first displayed?
To ensure the clearest possible initial image
view, all versions of the Zoomify Viewer released since August
2004 include ActionScript in the 'Actions' frame (frame 1
of layer 1) that carefully manages the presentation of image
data depending on how Flash Player has loaded. This is necessary
because the timing of initial image display must be different
when the Player loads for the first time in a browser session
than when it loads on any subsequent web page views or when
a web page is resized. This special handling ensures that
image data will be sized after the Player is initialized,
the Flash stage is sized, and the Zoomify Viewer component
is initialized, and will therefore be free of any distortion
(unintended scaling) and absolutely as clear as possible.
top of section | top of page
How can I provide a visual indicator that a new, clearer view is loading?
Yes. It is certainly possible to add text or
graphics to the view area to assure the user that image data
loading is in progress. Typically this is accomplished by
the visual loading effect itself, however, some designers
prefer a more explicit indicator.
In the current version of Zoomify Flash, each
of the Zoomify Viewers includes the ZoomiGrid class that,
in turn, includes the methods selectTiles(), renderLoadedTiles(),
and renderUpdatedTiles(). These methods manage the determination
of the tiles required for the latest view zoomed and/or panned
to, and place and position the tiles as they are loaded (renderLoadedTiles)or
repositioned (renderUpdatedTiles). In addition, the events
'viewLoadingProgress' and 'viewLoadingComplete' provide bounding
conditions for a progress notification method or class.
PRIOR VERSION NOTE: using the Zoomify ActionScript
API calls supported by the Zoomify Viewer Component, a simple
progress message display can be created in the form of a 'sharpening
component' using ActionScript as follows:
top of section | top of page
How
can I set focus on a Zoomify Viewer Component instance?
Use the ActionScript 'setFocus' method to set
focus on a specific instance of the Zoomify Viewer Component:
myZoomifyViewerInstance.setFocus();
Conversly, to avoid having the keystrokes 'a',
'z', 'shift', and 'control' cause an instance of the Zoomify
Viewer Component to zoom in or out during typing in a text
field in the same Flash project, use the same method to set
focus on the text field rather than on the Component.
top of section | top of page
Do the Zoomify Components include keyboard support?
Yes. The Zoomify Viewer Component includes native
support for panning using the up, down, left, and right arrow
keys, zooming using the 'a' or 'SHIFT' key to zoom in and
the 'z' or CTRL key to zoom out (Command key on Macintosh),
as well as the Escape to reset the initial image view.
top of section | top of page
How can I modify or disable Zoomify key handling?
The key handling support that is provided by
the Zoomify Viewer Component can be disabled by setting the
property keyboardEnabled:
zoomifyViewerInstance.keyboardEnabled
= false;
The set keyboardEnabled() method itself can be
found in the ZoomifyViewer.as file in the Classes | zoomify
subfolder.
top of section | top of page
Do the Zoomify Components support tabbing (focus management)?
The Zoomify Components support tabbing (focus
management) to the limited degree that it is relevant to their
functionality. For example, focus can be set on the Zoomify
Viewer Component via custom component inspector values or
using standard ActionScript calls, however, focus is not typically
set on the Zoomify Toolbar Component as built-in keystroke
support provides zoom-and-pan control and is based on an assumption
of focus being on the view. Note that the Zoomify Annotation
Viewer included in Zoomify Enterprise presents a greater need
for tabbing control due to the many data entry fields that
are available in Edit mode (Point Of Interest names, Notes
text content, etc.) Accordingly, the Annotation Viewer includes
greater built-in support for focus management.
top of section | top of page
Can
I turn off pan constraints so a view can center on an image
edge or corner?
Beginning with version 4, the default behavior
of the Zoomify Viewer is to constrain image pan to ensure
the image does not leave the view area. This behavior can
be disabled using the zoomifyPanConstrain HTML parameter which
is documented in the 'READ ME FIRST.txt' file in each Viewer
folder in the product. This property can also be set via XML
parameter. Example web page implementations are also included
with each Viewer in the 'HTML & XML Examples' subfolder.
Flash developers can also make use of the Zoomify ActionScript
API available in Zoomify Flash:
zoomifyViewerInstance.panConstrain = false;
PRIOR VERSION NOTE: In the prior version of Zoomify Flash
('Zoomifyer for Flash v3') the default behavior is to NOT
constrain pan. In fact, constraint behavior requires custom
ActionScript coding to implement. This is, however, easy to
implement in a limited way. In a limited implementation, when
a user panned an image out of view and releases it it will
pop back to a position partially in view. To implement this
approach, the following code can be placed in frame 1 of the
Flash project containing the Zoomify Viewer Component into.
(If the Zoomify Viewer Component instance is in a different
frame then the code will need to be placed in that frame.)
There will in fact be 5 occurrences of the term
"ZoomifyImageInstance" that will need to be changed to the
actual Viewer Component instance name.
Also note that the numeric value can be modified
to alter the constraint effect. For example, change the value
0.5 above to 0.9 and that will allow the user to pan the image
further out of view - almost completely - without it jumping
back. Note, however, that in this case, and image can end
up so far out toward an edge of the display that any amount
of zoom-in could still cause the image to move out of view.
A more elegant approach would prevent the image
from ever leaving view - rather than popping it partially
back into view when the user finishes panning. This is more
difficult to achieve for several reasons. It requires handling
more cases: where a current view of the image is smaller than
the display area it should be constrained by its leading edge,
bumping into the display border and never even partially leaving
view. Once the user zooms in sufficiently that the view of
the image exceeds the size of the display area the image's
leading edge should be allowed to pass beyond the display
boundary, however, the image's trailing edge should 'catch'
on the opposite display boundary, preventing it from coming
out into the middle of the view. Due to the complexity of
this more thorough implementation its development became part
of the Zoomify Flash version 4 development effort, and all
of the Viewers in that version include built-in pan constraint
support.
top of section | top of page
Do the Zoomify Components support image preloading?
The Zoomify Viewer Component is specifically
designed to load only the image data which is required for
the current view that the user has zoomed and panned to. Idle
time preloading possibilities present an obvious potential
performance boost, however, typical user behavior associated
with zoom-and-pan image viewing does not, in fact, present
significant idle time for sophisticated implementations to
leverage. Alternately, it may in some cases be desirable to
preload a specified set of image tiles representing a specific
desired initial or sequential set of views. Where designers
or developers wish to implement such functionality in their
own applications the simplest approach may be to use multiple
instances of the Zoomify Viewer Component and use the Zoomify
ActionScript API to setView() on each. These components can
then be revealed as appropriate with their content ready for
immediate viewing.
top of section | top of page
Do the Zoomify Components support localization?
All Flash projects provide some inherent degree
of localization support, however, such support has been less
relevant to Zoomify's Viewers and Components than is the case
with many other software programs. This is largely due to
the fact that the Zoomify technologies are predominantly image
content-focused, rather than text-based. As a result, very
little localization is required in most cases. Areas of greatest
relevance likely include Viewers presenting Slide or Hotspot
choicelists or those displaying captions or tooltips, which
are XML-driven with proper ActionScript escaping (management
of special characters) so projects built on these Viewer '.AS'
source files are not expected to present any significant difficulty
for implementations in other languages - or at a minimum,
those presented in horizontal aspect. To support and simplify
localization in these areas every attempt has been made to
organize error, default, and other text strings in the Resources.as
source file, as well as in the relevant slides.xml, hotspots.xml,
and other data resource text files.
top of section | top of page
How can I use ActionScript to parse XML?
Loading and parsing XML is a extremely useful
for working with image content or any content. The Flash Player
and ActionScript make all sorts of advanced data-driven functionality
possible. New features become available with every upgrade
- be sure to check the ActionScript API reference prior to
implementing anything. Some simple information follows that
may be helpful for those new to using XML data to populate
a Flash application.
Three steps are important: loading the XML, parsing
it to an array, and using the Zoomify ActionScript API to
load an image based on the data in the array. In the Zoomify
Viewers this is handled via the Parameters.as class, as well
as by specific methods within the calling classes. Some examples
from the Zoomify Hotspot Viewer follow:
PRIOR VERSION NOTE: In the prior version of Zoomify
Flash ('Zoomifyer for Flash v3') loading XML looks like this:
Parsing the xml looks like this:
And using a choicelist to set the Zoomify Viewer's image path looks like this:
Lastly, create your choice list
and set the above method as its handler.
top of section | top of page
How can I convert from resolution independent to pixel coordinates?
Early versions of the Zoomify Viewer made use
of 'resolution independent coordinates' to specify and position
hotspots within a zoomable image. This coordinate system represents
an image using a span from a value of negative 1 to positive
1 both vertically and horizontally. Accordingly, the center
of the image is represented as 0,0 while the far upper left
corner would be represented as -1,-1. All recent versions
(v3 and above) of the Zoomify Viewer make use of the simpler
and more intuitive pixel coordinate representation. Using
this approach, the position of a hotspot within a zoomable
image is simply the number of pixels from the left side of
the image and the number of pixels from the top of the image.
The center of an image that is 1000 pixels wide and tall would
therefore be 500,500 while the upper left corner would always
be 0,0.
It may be desirable under certain circumstances
to convert between these coordinate systems. The functions
below accomplish this task. Note that these functions require
information about the size of the image and are therefore
useful only after a zoomable image has loaded (that is, the
viewer has initialized).
top of section | top of page
When
does nesting the Zoomify Viewer in a MovieClip stop mouse
interaction?
Version 3 of the Zoomify Viewer Component is
known to contain several references to '_root' that will evaluate
incorrectly should the Viewer Component be nested within a
movieclip. This uses was not anticipated at the time of first
release as test and actual implementations typically (uniformly)
made use of the Component placed directly on the stage. This
problem is addressed in subsequent versions. If you encounter
it you can simply replace the _root references with _parent
(the number of such references are limited). For information
on subsequent releases please contact
us.
top of section | top of page
How do I
stop errors I see when using Zoomify in my Flash editor?
Zoomify provides custom installers for Adobe
Flash MX and Flash MX 2004. Zoomify provides MXP files for
newer versions of the Flash editor. In some cases, it is not
possible for these installers to determine where Zoomify's
files should be placed within the Flash editor file structure.
In these cases, errors may be presented when using specific
integrated features within the Flash design environment.
To correct this situation it is necessary to
manually place the needed files in the appropriate Flash subdirectories.
Please find the section titled 'manual install' in the product
User Guide and follow the steps provided. These steps specify
what files should be copied from each product folder into
each Flash subdirectory.
Please note that the features of Zoomify can
be used even without installation. Image files can be dragged
directly onto the Zoomify Converter, and the Zoomify Help
and Zoomify ActionScript API can be directly double-clicked
for viewing. This option may provide a useful alternative
to immediately pursuing the manual install steps.
top of section | top of page
When previewing in Flash MX the components do not work as expected. Why?
Flash MX does not provide the support required
to enable the Convert, Browse, and other integration features
of Zoomify Flash. The support required for these features
to work was first implemented in Flash MX 2004. The functionality
of the Zoomify solution is, however, fully accessible as thes
integration features simply provide increased convenience.
For example, conversion is possible by simply dropping any
image file on the Zoomify Converter file (exe or app) icon
which is available immediately upon downloading and unzipping/unstuffing
the Zoomify Flash product. Similarly, the Zoomify ActionScript
API is available directly within the Developer folder in the
download.
top of section | top of page
The ZoomScale component seems to ignore HTML parameters. How can I fix this?
The ZoomScale component in Zoomify Flash version
3 ('Zoomifyer for Flash') delivers a ruler graphic presenting
the current scale and zoom level (degree of magnication).
Reports of intermittent or context-specific problems with
the ZoomScale component and the HTML parameters used to set
its range and units are under investigation. Some builds may
include HTML parameter (FlashVar parameter) handling that
is based on ActionScript variable names which conflict with
the class declaration values of the component. As additional
information becomes available we will post it on the Zoomify
web site.
top of section | top of page
Where
can I see demos of all the different Zoomify Viewers?
The Zoomify web site has demonstrations of every Zoomify Viewer.
Although the Viewers themselves are included in both the Zoomify
Design and Zoomify Flash products you can find the demos on
the Zoomify Design web page. The
Zoomify Flash web page presents demos
of the sorts of Viewer customizations that are possible with
the editable source files that are included in that product.
top of section | top of page
Can I combine the functionality of different Zoomify Viewers?
Yes, the Zoomify Flash product includes complete
'.FLA' and '.AS' source files to enable total customization
control.
Note that the Zoomify Design product does NOT support this
deeper level of customization. Rather, it is tailored to the
needs of web designers who don't wish to pursue Flash editing,
but rather, prefer to customize Viewer layout and behavior
using HTML and XML parameters. These parameters are specific
to each Viewer and offer the ability to change an individual
Viewer, not move behaviors between Viewers.
top of section | top of page
How do I decide what numbers to use for hotspot coordinates?
Selecting the X and Y coordinates at which to
place a hotspot is as simple as counting the pixels from the
left edge and the top edge of the source image. This can be
accomplished most easily by opening your source image in an
image editor such as Adobe Photoshop. Most image and photo
editors include an information panel presenting the current
X and Y position of the cursor over the image. This is the
value needed for your hotspot. An alternative is to estimate
the coordinates of the desired position, edit and save the
hotspots.xml file, load the web page presenting the Zoomify
Hotspots Viewer in your browser, and then modify and resave
the hotspots.xml and reload the web page until the positioning
is as intended. When estimating simply remember that the left
edge of the image is pixel 0 and the right edge is the full
pixel width of the image - for example 1000 on a 1000 pixel-wide
image. Similarly the top edge is 0 and the bottom - of a 1000
pixel tall image - would be 1000. In this example the center
point would be X=500 and Y=500.
PRIOR VERSION NOTE: The prior version of Zoomify Flash ('Zoomifyer for Flash v3') presented two means to specify X and Y coordinates:
'resolution independent coordinates' or pixel coordinates'.
Zoomify's hotspot component, available in the prior product
version, makes use of the former scheme, while later examples
employ the latter, more intuitive approach.
To work with the hotspot component, it is simplest
to use the custom component inspector interface of the Hotspot
Component to place hotspots. This visual interface also displays
the applied resolution independent coordinates (though manual
entry is not required). However when working with the Zoomify
Hotspot Viewer example of the prior version of Zoomify Flash,
coordinates in the hotspots.xml text file are entered as pixel
values - as with the current version of Zoomify Flash.
Lastly, note that in the prior version of Zoomify
Flash, when using ActionScript to position hotspots or otherwise
interact with an image, conversion between the two coordinate
models can be managed using conversion scripts provided in
the answer to the question 'How
can I convert from resolution independent to pixel coordinates?'
top of section | top of page
Can I customize the Slideshow, Hotspot, and other components?
Absolutely. The Zoomify Viewers included in Zoomify
Design and Zoomif Flash can be customized using extensive
HTML and XML parameters. Additionally Zoomify Flash includes
the editable '.FLA' and '.AS' source files enabling customizaion
of layout and functionality as well as creation of totally
custom viewing solutions. And Zoomify Flash is built using
Zoomify Components and a powerful ActionScript API. This makes
integration of zoom-and-pan in your own projects straightforward
and efficient.
PRIOR VERSION NOTE: The Zoomify Slideshow, Hotspot, and other
components released with the prior version of Zoomify Flash
('Zoomifyer for Flash v3') present custom component inspectors
that are implemented within the Adobe Flash editing tools
using a special Live Preview feature of Flash. This preview
capability provides an intuitive visual interface for the
Slideshow and Hotspot components. It is, unfortunately, precompiled
during creation of the Zoomify components. In short, the Slideshow
and Hotspot components provide ease of use with some limitation
of control.
More specifically, the values entered into these custom property
inspectors via the fields and other interface elements presented
are held in memory until the FLA is published and the designer's
SWF is created. At that time the values as well as the associated
functionality the relate to are automatically and transparently
incorporated into the designer's SWF. These values and their
associated ActionScript, movieclips, etc. are not exposed
in the designer's FLA and cannot be edited. The custom property
inspectors present specific functionality that allows rapid
creation of specific effects but they do not enable customization
of that functionality beyond what is made possible by the
choices presented within the custom property inspector interface.
For designers and developers requiring complete control of
their projects Zoomify now provides the Zoomify Slideshow
Viewer and Zoomify Hotspot Viewer example projects - complete
with FLA source files. These examples are based on the Zoomify
Viewer Component, Toolbar Component, and underlying Zoomify
ActionScript API. This makes these project flexible and fully
customizable. In addition, these projects are xml-driven -
the slide names, hotspot coordinates, and other data are simply
typed into a text file rather than being entered into a component
inspector. As a result, designers and developers enjoy significant
control of the slideshow and hotspot presentations without
any Flash editing and complete control of features and functionality
should they choose to customize the project FLA files.
top of section | top of page
How can I make Hotspots open in the same window?
The Zoomify Hotspots Viewer supports a simple
HTML and XML parameter to specify the target of a hotspot
click. This parameter supports standard values such as '_self'
and '_blank'. The use of this parameter is documented in the
'READ ME FIRST.txt' file in each Viewer folder in the product.
This property can also be set via XML parameter. Example web
page implementations are also included with each Viewer in
the 'HTML & XML Examples' subfolder.
PRIOR VERSION NOTE: In the prior version of Zoomify
Flash ('Zoomifyer for Flash v3') the mouse click behavior
of Zoomify hotspots makes use internally of the Flash Player's
built-in 'getURL' function. This function supports two parameters:
the URL to open, and the target window to open it into. The
second parameter is specified as '_blank' (representing a
new window) by default. This parameter's value is hardcoded
in the prior version and can only be changed by editing the
source code of the Zoomify Viewer component. The value can
be set to '_self' (representing the current window) by following
this steps:
Open zoomifyHotspotViewer.fla in a Flash editor.
On the Flash editor's menu select Window | Library.
Right-click the ZoomifyViewer Component and select Expand.
Right-click the item Label Infrastructure and select Expand.
Right-click the item LabelText_Text_mc and select Edit.
Select Layer 1, Frame 1, and from the Flash editor's menu
select Window | the Actions.
Find this line (typically line 21 or line 47):
getURL(this.gZoomifyURL,"_blank");
Replace _blank with _self.
Publish a new SWF and all future mouse-clicks
will open in the same (current) window.
top of section | top of page
How can I make Hotspots do something other than open a URL link?
The Zoomify Hotspot Viewer's support for hotspot
mouse clicks is implemented using the Flash Player's built-in
navigateToURL method. The method call can be replaced with
a call to any function in order to change the default mouse-click
behavior.
Open the subfolder 'Classes | zoomify | Viewer'
and open the source file ZoomGrid.as in a text editor.
Find this line (typically line 1057):
navigateToURL(new URLRequest(hotspotData.url),
hotspotData.urlTarget);
Comment it out and insert a call to any other
function:
//navigateToURL(new URLRequest(hotspotData.url),
hotspotData.urlTarget);
myFunction(myParameter);
Note that 'this' is a useful value to pass in
as myParameter. This will return the full path and name of
the hotspot that has been called. This value can be parsed
to yield the hotspot ID which can then be used for determining
action that differs depending on which hotspot has been clicked.
For more information on using hotspot IDs and parsing hotspot
names see the TechNote 'How are
hotspots named?'.
Publish a new SWF and all future mouse-clicks
will cause the new function to be called and the preferred
new behavior to occur.
PRIOR VERSION NOTE: In the prior version of Zoomify
Flash ('Zoomifyer for Flash v3') the mouse click behavior
of Zoomify hotspots makes use internally of the Flash Player's
built-in 'getURL' method. This method call can be replaced
with a call to any function in order to change the default
mouse-click behavior.
Open zoomifyHotspotViewer.fla in a Flash editor.
On the Flash editor's menu select Window | Library.
Right-click the ZoomifyViewer Component and select Expand.
Right-click the item Label Infrastructure and select Expand.
Right-click the item LabelText_Text_mc and select Edit.
Select Layer 1, Frame 1, and from the Flash editor's menu select Window | the Actions.
Find this line (typically line 21 or line 47):
getURL(this.gZoomifyURL,"_blank");
Comment it out and insert a call to any other function:
//getURL(this.gZoomifyURL,"_blank");
_root.myFunction(myParameter);
Note that 'this' is a useful value to pass in as myParameter. This will return the full path and name of the hotspot that has been called. This value can be parsed to yield the hotspot ID which can then be used for determining action that differs depending on which hotspot has been clicked. For more information on using hotspot IDs and parsing hotspot names see the TechNote 'How are hotspots named?'.
Publish a new SWF and all future mouse-clicks will cause the new function to be called and the preferred new behavior to occur.
top of section | top of page
What file formats can be used for Zoomify Hotspots?
Supported file formats for hotspots media include those supported
by Flash Player - PNG, GIF, and JPG in Flash Player 9. Use
PNG files if support is required for transparency. Note that
SWF files have been supported in prior versions ('Zoomifyer for Flash v3') however this support has been temporarily removed
pending review of the implications of recent Flash Player
security changes related to active media being dynamically
loaded at runtime.
top of section | top of page
How
can I make my SWF Hotspots react to mouse events?
PRIOR VERSION NOTE: Prior versions of Zoomify
Flash ('Zoomifyer for Flash v3') support the use of SWF files
for hotspot media. This support presents the possibility of
alternative mouse click behaviors, however, the default behavior
must first be disabled for any interactivity in the SWF hotspot
media to react to a mouse-click.
Zoomify hotspots have default
behavior that occurs on a mouse-click. The ActionScript that
enables this functionality can be seen by opening any Flash
document that includes the Zoomify Viewer Component, opening
the Library, selecting Expand All Folders, scrolling down
to emptyLable_mc, right-clicking and selecting Edit, then
- important - clicking the little crosshair in the middle
of the display, then viewing Actions. You'll see, for example:
on(press)
{
this._parent.gTextMovieClip.labelText_mc.StartDragLabel(false);
}
By commenting out or deleting
the 'on(press)' event handler above the default mouse interaction
can be disable. Mouse clicks will then 'fall through' to whatever
ActionScript is in the SWF that is used as a hotspot media
item.
top of section
| top of page
How
can I pass mouse-drag events through a hotspot to the underlying
image?
PRIOR VERSION NOTE: Prior versions of Zoomify
Flash ('Zoomifyer for Flash v3') support the use of SWF files
for hotspot media. This support presents the possibility of
alternative mouse click behaviors, however, the default behavior
must first be disabled for any interactivity in the SWF hotspot
media to react to a mouse-click.
Example: the default behavior of a hotspot is to react to
a mouse-click. An alternative behavior would be to pass a
mouse-drag through to the image below in order to allow panning
of the image even when the hotspot is 'in the way'. To accomplish
this, a few lines of ActionScript need to be modified. The
following information provides the necessary steps.
Zoomify hotspots have default behavior that occurs on a mouse-click. The ActionScript that enables this functionality can be seen by opening any Flash document that includes the Zoomify Viewer Component, opening the Library, selecting Expand All Folders, scrolling down to emptyLable_mc, right-clicking and selecting Edit, then - important - clicking the little crosshair in the middle of the display, then viewing Actions. You'll see, for example:
on(press)
{
this._parent.gTextMovieClip.labelText_mc.StartDragLabel(false);
}
The function StartDragLabel can be found by scrolling further down in the Library and Editing LabelText_Text_mc. Be sure to click the stage, then view Actions. You'll see on line 5:
function StartDragLabel(launchURL)
The important action is on line 21:
getURL(this.gZoomifyURL,"_blank"); //Standard viewer functionality.
This can be commented out and replaced with other functionality. For example:
//getURL(this.gZoomifyURL,"_blank"); //Standard viewer functionality
_root.myPanFunction(this._parent._name, "start");
Next, create the function myPanFunction a the root of your project (frame1 of layer1 in the timeline of the stage). This function will receive two parameters: the name of the calling hotspot (label), and whether the call is to 'start' or 'stop' the function:
function labelsSelectGridRow(clickedLabelName, labelsSelectEvent)
The function must parse the hotspot name and compared it with a hotspot ID. This ID is assigned in the addLabel function when the hotspots are created. The IDs will either be stored in an array and used as numerous addLabel calls are made in sequence, or, if the number of hotspots is small, the values can be stored in variables.
if(clickedLabelName == "label" + gArrondID + "_mc")
Based on a match, a call to the mousePan function of the Zoomify Viewer Component is made and the parameter to start or stop is passed in:
This ensures that - in addition to doing whatever else is desired when a hotspot is clicked, the underlying image can be panned via mouse-click-drag. For more information on using hotspot IDs and parsing hotspot names see the TechNote 'How are hotspots named?'.
top of section | top of page
How can I hide or show all hotspots?
The Zoomify Flash product includes, a pre-built
example of this functionality. It applies the setHotspotsVisibility()
method of the Zoomify ActionScript API. The example can be
found in the 'Developer Examples' folder and is titled 'Hide-Show
All Hotspots'. This example includes source code.
top of section | top of page
How can I hide or show individual hotspots?
The Zoomify Flash product includes a pre-built
example of this functionality. The example can be found in
the 'Developer Examples' folder and is titled 'Hide-Show One
Hotspot'. The example includes source code.
PRIOR VERSION NOTE: In the prior version of
Zoomify Flash ('Zoomifyer for Flash v3') hiding or showing
all hotspots (labels) can be achieved using a simple call
to the setLabelVisibility() function of the Zoomify ActionScript
API. Setting an individual hotspot visible or invisible requires
directly addressing it. To directly address a hotspot requires
knowing the path to the hotspot as well as its unique ID.
The implementation of hotspots within the Zoomify Viewer Component requires nesting hotspot icons within a zoomable/pannable layer - a container movie clip within the Viewer Component. For this reason, the path to any specific hotspot will be:
_level0.ZoomifyViewerInstance.gLabelTier_mc.labels_mc
Within that container movie clip, each hotspot will be labeled according to simple naming convention. For example, the first hotspot created will be named:
lable1_mc
Knowing the order in which hotspots are created allows addressing them individually. Alternately, specific IDs can be assigned within the addLabel function call. These IDs can be stored in an array or variable for later use in a conditional statement of a custom function.
Given the above hotspot path and name information, any hotspot can be hidden or shown as follows:
or
Additionally, hotspots can be hidden or shown in a manner that allows them to continue to respond to mouse events. This can be done using the alpha movieclip property:
or
For more information on using hotspot IDs and parsing hotspot names see the TechNote 'How are hotspots named?'.
top of section | top of page
How
can I change properties of individual hotspots?
The Zoomify Hotspots Viewer presents hotspots
with numerous properties. These can be changed directly using
ActionScript. A related example is included in the Zoomify
Flash product in the 'Developer Examples' subfolder. It is
named 'Hide-Show One Hotspot' and includes complete source
files. This question originally related to a need in the prior
version of the product. The answer for users of that prior
version is presented below. It discusses changing the color
of a hotspot.
PRIOR VERSION NOTE: The prior version of Zoomify Flash ('Zoomifyer
for Flash v3') supported SWF files as hotspot media and involved
a nested presentation that required careful addressing to
implement changes. The following code addresses a hotspot
individually and highlights or unhighlights it by toggling
its color between one hexidecimal value and another. In this
example, the hotspot media is a SWF file that contains a movie
clip named 'container' with a graphic fill inside it named
'map'.
top of section | top of page
Why do Hotspots seem to shift position slightly at extreme zoom?
Very large images present a special challenge with respect to the accurate placement of hotspots. This is due at least in part to the fact that the coordinates for a hotspot will have to be extremely exact - and in some cases, more exact than Flash Player may allow.
The basic unit of measure for coordinates in Flash is 1/20-th of a screen pixel, or a TWIP. Coordinates with finer precision than .05 are simply rounded to the nearest .05. The fractional pixel positions are approximated using anti-aliasing. This would not normally present a problem, but with the extreme range of resolutions in the Zoomify Viewer, and the fact that the label "tier" (i.e. layer) has to correspond to the lowest resolution "tier" the coordinate calculations can result in th rounding process creating a noticable shifting effect as an image is panned slightly in one direction and then back again.
Zoomify is working to implement an alternate approach in upcoming releasese which, it is expected, will resolve this issue through forced, smooth, miniscule readjustment of image pan positions to allow exact placement of hotspots and avoidance of any need to exceed the supported degree of precision.
top of section | top of page
Can I add hotspots in Viewers other than the Zoomify Hotspot Viewer?
Certainly. The hotspot support in the Zoomify
Hotspot Viewer (and other Viewers that support hotspots such
as the Watermark, Tour, and Geo Viewers) involves a Hotspots
class as well as references to it in several higher order
classes: the ZoomGrid and ZoomifyViewer classes, as well as
the main viewer project all contain relevant methods and method
calls.
Moving ActionScript from one Viewer to another followed
by recompiling the target Viewer is certainly possible. This
approach is, however, somewhat involved. An alternative approach
that may be simpler would involve moving other functionality
into the Hotspots Viewer codebase. For example, the Tour Viewer
is a hybrid of the Slideshow and Hotspot Viewers so it presents
a natural starting point for any project requiring both types
of features - sequential transitions between images or places
in an image as well as presentation of graphical icons at
points of interest within an image.
It is important to note that efficient development and the
simplest possible codebase for a range of developer skill
levels were the primary consideration when considering the
optimal combination of object oriented development and duplicate
code customization. The Zoomify ActionScript codebase provides
the expected class, method, property, event, and other elements
required for efficient code reuse and effective code extensibility.
It should be noted that in limited cases opportunities for
utilizing inheritance or other OOP programming approaches
are declined in the interest of maintaining more streamlined
code. As an example, several of the Zoomify Viewers implement
customized versions of the Zoomify Toolbar – the Full Screen,
Slideshow, Tour, Comparison, and Rotation Viewers.
These custom Toolbars require only limited additional lines of ActionScript to add one, two,
or three special buttons. Creating a new Toolbar that inherits from the base Toolbar
would, on the other hand, involve considerable code to manage the various interactions of
the Viewer and Navigator Components with the Toolbar Component through the new
Toolbar class.
The obvious disadvantage is that any change or fix to the ActionScript in one Toolbar
version will need to be propagated to the other Toolbar versions. This, however, is
primarily an impact on the Zoomify team, while Zoomify customers enjoy the benefit of
working with an individual Toolbar with a simplified codebase.
top of section | top of page
What are the alerts presented when switching between Normal and Full Screen viewing modes?
Two alerts are presented when switching between
viewing modes. The first is displayed by the Flash Player.
It reminds the user that the Escape key can be used to exit
Full Screen mode. This was implemented by Adobe in anticipation
of the possibility that a clear means to return to normal
viewing mode might not always be presented in projects created
by Flash developers.
The second alert, presented directly below the first, notes
that an initial click is required to activate the new mode
- whether Full Screen or Normal. This is necessary because
a click-drag will cause an unintended behavior (view scaling
not under the control of the Zoomify Viewer) if not preceded
by an initial click. That is, attempting to pan prior to clicking
the view in the new mode will create unexpected consequences
and potential errors. Zoomify is monitoring reports to Adobe
related to Full Screen / Normal mode changes. As quickly as
the source of this issues is identified and addressed an update
wil be developed. Additional information will be posted to
the Zoomify web site as it becomes available.
top of section | top of page
How are the Zoomify Slideshow and Zoomify Gallery Viewers different?
Both the Zoomify Slideshow Viewer and Zoomify Gallery Viewer
provide sequential viewing of Zoomify Images. Both present
an enhanced Slideshow Toolbar and a choicelist of Slides for
easy navigation. To these features the Gallery Viewer adds
a Zoomify Gallery Scrollbar that supports navigation just
like the Slides choicelist, but with a thumbnail image of
each Slide as a preview of the Zoomify Images available for
viewing. Note that the Gallery Scrollbar can be positioned
at the bottom or top of the Gallery Viewer using an HTML or
XML parameter, and like the Slides choicelist, it can be turned
off.
top of section | top of page
Can I specify rotation values over 360 degrees in the Zoomify Rotation Viewer?
Absolutely. Values over 360 degrees will be automatically converted
internally to the appropriate value under 360.
top of section | top of page
Can I specify negative rotation values in the Zoomify Rotation Viewer?
Yes. Values below 0 will be automatically converted internally
to the appropriate value between 0 and 360. Note that clicking
the Reset Initial View button will initiate a zoom-to-view
transition to the initial X, Y, Zoom, and rotation values,
and that the shortest path will be taken. For example, if
the current rotation is 185 degrees and the initial rotation
was 0 degrees, the view will rotate clockwise in returning
to 0. However, if the current rotation is 175 degrees, the
view will rotate counter-clockwise in returning to 0.
top of section | top of page
Can I specify rotation values radian rather than degress in the Zoomify Rotation Viewer?
Unfortunately, no. Values in degrees are expected
by the Zoomify Rotation Viewer. Customization of the underlying
ActionScript to autoconvert internally from radian parameter
inputs to degrees is certainly possible and would not be difficult.
top of section | top of page
Can the Zoomify Geo Viewer be used with coordinate systems other than latitude and longitude?
As delivered, the Zoomify Geo Viewer expects
parameter inputs in latitude and longitude. Modifying the
internal methods to support an alternative matrix or grid
system is certainly possible. The relevant methods are grouped
at the bottom of the ZoomifyGeoViewer.as class file beneath
a header 'GEO VIEWER METHODS'. The two methods most requiring
attention are the geoDataPrep() and geoTrackOnMouseMove()
methods.
top of section | top of page
Zoomify Enterprise
How do I install Zoomify Enterprise?
Zoomify Enterprise does not require installation.
The various features of the product are useful immediately
upon unzipping/unstuffing the product download. That is, the
Zoomify Enterprise converter can be used simply by dropping
any image file onto the Converter application (exe or app)
icon. To publish the resulting Zoomify Images and/or implement
the Zoomify Annotation System the Zoomify Images (in folder
or single-file PFF form) and a Zoomify Viewer file (simple
or annotation) will need to be copied to your web server.
For detailed publishing information please review the Zoomify Enterprise User's Guide. Additional useful information can
be found in the answers to the questions 'What
do I need to set up on my Web server?', 'What
should my ZAS HTML parameters look like?', 'Does
my setup differ if I'm using single-file (PFF) or folder-based
image storage?', 'Do
I need the Zoomify Servlet on my Web server?', and 'If
I need a servlet container, how do I set it up?'.
top of section | top of page
Is there a trial version available?
Our free product, Zoomify Express, substitutes for
a trial product and can be downloaded from our home page or
here: Win
| Mac.
This product demonstrates drag-and-drop image conversion and
intuitive Flash-based zoom-and-pan viewing and is ideal for
web designers needing a quick and simple way to include high-quality
images in their sites - whether private or public, personal
or commercial. Customers requiring a means to more deeply
evaluate the specific features of Zoomify Enterprise may
contact our Support team at the address provided below
for receipt of evaluation a copy of that product on a case-by-case
basis.
top of section | top of page
Zoomify has released version 4 of its other products. When will Zoomify Enterprise v4 be available?
A release date for version 4 of Zoomify Enterprise
has not yet been announced. It is expected, however, that
the Zoomify Annotation Viewer will be built upon the Zoomify
v4 Components and wrappers have already been created for these
to support the draggable, palette-like presentation of the
Components as delivered in the v3 Annotation Viewer. Additionally,
a new converter with enhanced functionality and unix/linux
support is nearly complete via a trusted partner. For more
information about the converter under development, please
contact us.
top of section | top of page
Why did Zoomify create the PFF format?
Zoomify makes high-quality images fast and interactive
over the web - regardless of image size. Zoomify customers
commonly make use of images hundreds of megabytes or even
gigabytes in size. Popular formats such as TIFF are limited
to 4 gigabytes of image data due to the way in which their
data offset information is stored. Other formats such as JPEG2000
provide opportunities for storage of larger files but have
not enjoyed widespread adoption or broad support in popular
imaging software.
Zoomify's Pyramidal File Format (PFF) is designed
to allow lightweight, single-file storage of the JPEG-compressed
image 'tiles' that make up multi-resolution zoomable image
content. The PFF format's technical file size limit is expected
to match or exceed that of operating systems and related technologies.
Zoomify also offers 'folder-based' zoomable image storage,
in which image tiles are stored as JPEG files within a folder.
For more information on folder-based and PFF storage alternatives,
see the TechNote 'When should I choose
one-file PFF-based storage?'
top of section | top of page
Should I
use single-file (PFF) or folder-based storage for my Zoomify
Images?
Zoomify provides two storage alternatives for
zoomable image content. The first method involves creating
a folder filled with small JPEG files or 'tiles' at many different
resolutions. When a zoomable image is viewed, these JPEG files
are downloaded as needed as the site visitor zooms and pans
using the Zoomify Viewer. The second storage alternative simply
places all the JPEG tile files within a single file with the
extension '.pff' (Pyramidal File Format). The advantage of
this approach is compactness. Zoomify works equally well with
images megabytes or gigabytes in size, and customers with
a large number of large images sometimes find managing the
content (copying from drive to drive, backing up, etc.) simpler
with just one file per zoomable image. The disadvantage of
this approach is the need for small helper application on
the web server. This small 'servlet' or server-side Java application
is needed to pull the JPEG tiles out of the .PFF file and
fulfill the requests from the Zoomify Viewer - the Flash-based
viewer cannot make these requests directly to the web server
itself. A 'servlet container' must therefore be set up on
the web server. Both the folder-based and the PFF-based approaches
are completely compatible with all Zoomify products: Zoomify Express, Zoomify Flash, and Zoomify Enterprise.
top of section | top of page
What type of support can I expect after purchasing Zoomify Enterprise?
Each Zoomify Enterprise purchase includes one
year of priority support. Priority support includes account
maintenance - full integer product upgrades in addition to
product updates (within the duration of the support contract)
as well as priority phone and email support.
top of section | top of page
How long do I receive priority support after purchase?
One year of priority support is included with
each purchase of Zoomify Enterprise. See the question 'How
can I extend my priority support?' for information on
how this period can easily and inexpensively be extended.
top of section | top of page
How
can I extend my priority support?
Priority support as provided with our Enterprise
product can be extended beyond the included first year by
contacting Zoomify Support. Priority
support includes account maintenance - full integer product
upgrades in addition to product updates - within the duration
of the support contract. Pricing is intended to provide convenience
and ensure satisfaction by delivering a significant cost savings
when compared to typical upgrade fees combined with potential
costs of 'incident style support' as offered by many Enterprise
product vendors.
top of section | top of page
What do I need to set up on my Web server?
To publish Zoomify Images you need only place
the Zoomify Image folders on your web server. Theses are created
with the Zoomify Converter. Then place the zoomifyViewer.swf
on your server, and include the few lines of HTML in any web
page to tell the Viewer which image to display.
To publish Zoomify Images stored using the single-file
PFF image storage approach, use the Zoomify Converter to create
the PFF image files (see the question 'How
can I tell the Zoomify Converter to create PFF files rather
than folder-based Zoomify Images?' to change the setting
so that the Converter creates PFF files instead of image folders).
Place the PFF files on your web server along with the special
Zoomify Viewer. The HTML you add to any web page will
differ only slightly (see the Zoomify Enterprise User's
Guide for information on the zoomifyByteHandler parameter
that you'll need to include).
top of section | top of page
Do I need the Zoomify Servlet on my Web server?
The Zoomify Servlet is used to support the use
of one or both of two optional features: single-file
PFF-based storage of Zoomify Images, and/or, use of the Zoomify
Annotation System in Edit mode.
PFF-based image storage is an optional alternative
to default folder-based image storage. See the question 'Should
I use single-file (PFF) or folder-based storage for my Zoomify
Images?' for more information.
ZAS Edit mode is an optional means to add, modify,
and delete annotations using the same web-based Annotation
interface that site visitors use for zoom-and-pan image viewing.
Note that the Zoomify Servlet is not required for annotation
editing, it is simply one option for saving edits. The Zoomify
Annotation System presents a Save button that, when clicked,
must pass new data to something on the server to 'post' -
that is, to save and overwrite the existing XML file for the
image in question. Posting data is an extremely simple process.
In fact, Zoomify includes an example ASP page that provides
the same functionality. This page contains only 25 or fewer
lines of ASP instructions and can easily be ported to the
scripting language of your choice. The Zoomify Servlet's posting
capability is only included as a convenience for sites already
using the Servlet to support (optional) PFF-based image storage
as discussed above.
top of section | top of page
Do I need a servlet container like JRun or Tomcat on my Web server?
A servlet container is required in any implementation
making use of a Java servlet. See the question 'Do
I need the Zoomify Servlet on my Web server?' for information
on which optional Zoomify features require the use of the
Zoomify Servlet.
top of section | top of page
If I need a servlet container, how do I set it up?
Two servlet container alternatives are JRun from Adobe and Tomcat which is open source. Setting up JRun is quite simple as a reliable installer is provided by Adobe. Setting up Tomcat can be more challenging - a reliable installer is not available and documentation for the many setup options is not always available.*
For either servlet container, begin with a default installation according to the instructions included with the product.** We recommend that you integrate the servlet container with your web server, not as a standalone server that requires a separate port designation.***
Once you've successfully installed either program, locate the appropriate servlet directory to copy files into. For JRun this is typically
c:\JRun4\servers\<server>\SERVER-INF\classes\. That is, a specific implementation would commonly be C:\JRun4\servers\zoomify\SERVER-INF\classes. For Tomcat the location would typically be \webapps\root\WEBINF\classes\. Note that if you don't see the appropriate folders (such as \WEB-INF\ or \classes\) you may create them.****
The files to drag in will be in Zoomify Enterprise\For Annotating\Zoomify Servlet. They include the entire contents of the 'classes' folder. The contents of the \classes\ folder will at least contain the file 'web.xml' and a folder called 'zoomifyservlet' which contains the servlet files.
Next, stop and start your servlet container service or server. Consult the documentation included with JRun, Tomcat, or other servlet container if you have questions about how to do this.
Finally, drag your new Zoomify image file (the PFF file) into your Web root. You may create a folder called 'zoomifyImages' or something similar and place the PFF in that folder.
*Be sure that 'Execute' and 'Write' permissions are not set simultaneously in any directory in your Web site (except for special applications) as that may enable malicious code to be copied to your server and executed.
**To test your newly configured servlet container, please refer to the sample applications that come with either JRun 4 or Tomcat.
***This will ensure that visitors to your Web site who are behind firewalls will have access to your Zoomify content.
****There may already be files in the 'classes' folder if you are running other servlets.
Note that you can test the servlet by going directly to it. On Zoomify’s site the location is:
http://www.zoomify.com/servlet/zoomifyservlet.ZoomifyServlet
When you get a message stating as follows you’ll know the servlet is working properly:
Error=1&reply_data=You must specify a file path&Usage=file,begin,end,requestType,head
Your path would be: http://[domain]/servlet/zoomifyservlet.ZoomifyServlet
The following are example HTML parameters for a sample page including the Zoomify Annotation Viewer in Edit mode:
Additional Notes:
Regarding Apache: some versions of Apache may by default have a relevant utility named the 'servlet invoker' disabled. It is also possible that the invoker class can be 'commented out' within the server.xml and/or web.xml files. Either of these issues will prevent any servlet from functioning. Information about these possibility and how to address them can be found at http://jakarta.apache.org/tomcat/faq/misc.html
Some user-provided steps to address Tomcat '404 Servlet Not Found' errors:
1. Enable the root context. Edit instll_dir/conf/server.xml and uncomment this line:
<Context path="" docBase="ROOT" debug="0"/>
This is not necessary in Tomcat4.0.3 and earlier.
Note that in most versions of Tomcat5, the element is missing
a trailing slash and this must be added.
2.Turn on servlet reloading. Edit install_dir/conf/server.xml and add the following just above the entry for the ROOT context from the previous step:
<DefaultContext reloadable="true"/>
3. Enable the invoker servlet. Go to install_dir/conf/web.xml
(not ...server.xml) and uncomment the servlet and servlet-mapping
elements that map the invoker servlet to /servlet/*. In tomcat
4, only the latter step, uncommenting the servlet-mapping
element, is necessary. In Tomcat versions prior to 4.1.2,
neither uncommenting the servlet nor uncommenting the servlet-mapping
is necessary.
Special note regarding Tomcat version differences: Tomcat versions 3, 4, and 5 all behave differently given the same code. This can add additional difficulty to setups and updates.
top of section | top of page
Can I use ColdFusion as servlet container?
At the current time Adobe is not recommending
use of ColdFusion as a servlet container. While this is technically
feasible, it is not reliable, perhaps because the servlet
container functionality of ColdFusion is specifically implemented
and tested for the use of ColdFusion rather than third-party
servlets. For this reason, Adobe recommends JRun be used for
containing servlets. (Note that there is a difference between
using ColdFusion as a servlet container and simply using it
to call a servlet from a ColdFusion page. The latter involves
use of the ColdFusion GetPageContext tag as referenced at
and is documented and supported by Adobe.)
top of section | top of page
Does my setup differ if I'm using single-file (PFF) or folder-based image storage?
Yes, your servers-side setup will differ in one
respect when using single-file PFF-based storage rather than
default folder-based storage. When using folder-based storage
no special setup on the server is required. However, when
using PFF storage the Flash Player and Zoomify Viewer require
a 'helper application' on the server. This is because the
JPEG 'tiles' that make up each new view the user zooms and
pans to are stored not as simple JPEG files in a folder, but
as parts of a single file - specifically, byteranges within
the PFF file.
The Zoomify Servlet is used to receive tile requests
from the Zoomify Viewer, retrieve the JPEGs from within the
PFF file, and fulfill the Viewer requests. Because the Zoomify
Servlet is a Java Servlet, a 'servlet container' is needed
on the server. (This is analogous to the need for a Java 'virtual
machine' on a client computer when using Java applets.) Popular
servlet containers include Tomcat (free, open source, sometimes
tricky to configure) and Adobe JRun (simpler to set up, complete
documentation, neither open source nor free).
Lastly, when storing Zoomify Images as PFF files
rather than image folders a different Zoomify Viewer is needed
- one that has the additional 'access component' inside to
enable it to properly format tile requests for fulfillment
by the Zoomify Servlet. For additional information and to
download the latest version of this Viewer please see the
question 'Can I use
the ZoomifyDynamicViewer.SWF with PFF, Aperio or LizardTech
content?'
top of section | top of page
I don't need annotation. Can I still use single-file (PFF) image storage?
Certainly. The choice of storage approach is
a separate issue from the choice of whether or not to implement
annotation. Zoomify provides a simple, streamlined viewer
appropriate for Zoomify Images stored using the single-file
PFF approach. For additional information and to download the
latest version of this Viewer please see the question 'Can
I use the ZoomifyDynamicViewer.SWF with PFF, Aperio or LizardTech
content?'
top of section | top of page
Can I use the ZoomifyDynamicViewer.SWF with PFF, Aperio or LizardTech content?
Yes, this viewer is included with Zoomify Enterprise and can be used to view Zoomify Images stored in single-file
PFF file format as well as image content stored on the above
named third-party image servers. This viewer presents a standard
image display and toolbar without annotation features much
like the Zoomify Viewer included with Zoomify EZ and Zoomify
Flash. This simple viewer differs from those, however, in
that it includes the necessary 'access components' to properly
request and receive image data in these special contexts.
Please note that the Zoomify download server offers a newer
version of this non-annotation, PFF
and third-party image content viewer.
top of section | top of page
What is the MIME Type of Zoomify's PFF file format?
The MIME Type for Zoomify's PFF file format is
"image/zoom". This value is useful only in extremely limited
circumstances where a web site user has a very old version
of the Netscape browser and reports difficulty viewing Zoomify
Images. Additionally, this is typically only an issue with
Zoomify's non-Flash viewing alternatives. In these rare cases
It may be useful to associate the above mime type value with
the PFF file extension. This can be achieved using either
a set of menu choices to Add a new mime type or to Map a new
mime type - which language is used will depend on the server
in use.
top of section | top of page
What tests do I use
when my image doesn't appear?
If the Zoomify logo appears but image content
does not, the Flash Player is correctly finding the Zoomify
Viewer file 'zoomifyViewer.swf' but the viewer is not finding
the image folder. Double check the zoomifyImagePath to be
sure it is accurate. It does not need a leading or tailing
'/'. It must be included in the page TWICE - once for Windows
Internet Explorer and once for all other browsers. And most
importantly, it should point to the image folder, not to the
tileGroup0 subfolder within nor to the imageProperties.xml
file also therein.
If neither the image nor the Zoomify logo appear,
the Flash Player is not finding the Zoomify Viewer file 'zoomifyViewer.swf'.
Check the Flash embed statement to be sure the SRC parameter
states the correct relative or absolute path to the file.
It must be included in the page TWICE - once for Windows Internet
Explorer and once for all other browsers. (Note: the embed
statement is case sensitive and the default name for the Zoomify
Viewer included with the Adobe Photoshop CS5, CS4, and CS3
Zoomify Export feature is 'zoomifyViewer.swf' while the default
name of the viewers shipped with other Zoomify products begin
with a capital 'Z' as in 'ZoomifyViewer.swf' and 'ZoomifySlideshowViewer.swf'.)
Three additional tests can prove helpful: visit
the Adobe homepage and verify that the Flash content on that
page displays. This will verify that Flash Player is installed
and working on your system. Second, visit the Zoomify homepage
and verify that the Zoomify demo on that page displays. This
verifies that your Player version is adequate for Zoomify
content. Lastly, download the free Zoomify product from the
Zoomify homepage and review the contents of the file template.htm
in a text editor. Compare the Flash embed statement with the
statement in your web page. Copy the embed lines into your
page and verify that they work. Then modify only the zoomifyImagePath
and verify that your image now displays properly. Any differences
in the page that lead to the failure to properly display should
be clear as you make these changes.
top of section | top of page
Why does my image show up in one browser and not in others?
Generally when Zoomify works within Windows Internet
Explorer and not other browsers - or vice versa - it is because
the Flash embed statement has the correct parameters once
but not twice. For example, zoomifyImagePath may be set to
the correct URL in one instance in the web page but it may
be missing or set incorrectly in the second instance. The
parameters must be provided twice because the Flash Player
is an ActiveX on Windows IE and a plugin in other contexts.
This need for duplicate parameters is true for all Flash content
and is not specific to Zoomify.
top of section | top of page
How
can I use a cross domain policy file to allow content on multiple
domains?
Beginning with Flash Player 6, Flash movies are
prohibited by default from accessing content on a domain other
than that on which they themselves are hosted. Beginning with
Flash Player 7, this prohibition further extends to subdomains
of the movie's own domain. To specifically permit a movie
access to a server on a domain a 'cross domain proxy file'
must be place on the target server at the root. This file
will be an xml file (text with '.xml' extension) with content
such as the following:
<cross-domain-policy>
<allow-access-from domain="*.domainThatMyMovieIsAt.com"
secure="false"/>
</cross-domain-policy>
For more information about cross-domain proxy
files, see Adobe's Tech Note 14213 at: http://www.adobe.com/go/tn_14213.
top of section | top of page
What platforms is Zoomify Converter available for?
The Zoomify Converter is currently available
for Windows (Win2000 or later) and Macintosh (OSX) platforms,
however, scripted alternatives are available for UNIX/LINUX
environments. See the question 'How
can I convert images on a UNIX or LINUX machine?' for
additional information about script-based conversion alternatives.
top of section | top of page
How can
I tell the Zoomify Converter to create PFF files rather than
folder-based Zoomify Images?
By default, the Zoomify Converter will create
Zoomify Images in folder-based form. To tell the Converter
to output Zoomify Images in single-file PFF form, simply locate
the zoomifyConvertPrefs.asp file (this will be directly next
to the Zoomify Enterprise Converter after at least
one conversion has completed) and open it in any text editor.
Scroll to the line
ZOOM_OUTPUT_TYPE: 1
and change it to read
ZOOM_OUTPUT_TYPE: 2
For additional information on this change as
well as information on command-line switches please see the
Zoomify Enterprise User's Guide and find the relevant section
by searching on 'zoomifyConvertPrefs'.
top of section
| top of page
How can
I convert images on a UNIX or LINUX machine?
The Zoomify Converter is currently available
for Windows and Macintosh platforms, however, scripted alternatives
are available for UNIX/LINUX environments. Access information
is provided below. These alternatives have been developed
by Zoomify customers and partners and, as script-based implementations,
are editable and portable to other scripting languages. They
are, however, slower than the compiled offerings for Windows
and Macintosh. Zoomify is pursuing the creation of a UNIX/LINUX
converter through partners and we hope to have more to announce
soon. Please watch our home page for information on this topic.
For a Python/PIL/Zope-based conversion solution
please see SourceForge.net
and search on 'ZoomifyImage'. For a PERL-based conversion
alternative you may download the PERL-Slice.zip
file from the Zoomify download server. (Note: the PERL-based
solution does not support incremental source image data loading
so it is only appropriate for images tens or hundreds of megabytes
in size rather than gigabytes in size).
top of section | top of page
How can I script conversion of one file after another?
Automated (scripted) conversion of images using the Zoomify Enterprise converter will be faster, less processing intensive, and more reliable, if implemented in a sequential manner. That is, each call to the converter should proceed only after the immediately prior call has completed. The alternative - passing all filenames to the converter without waiting for any to complete - risks causing the converter or the operating system itself to exceed memory, processing, internal variable, or other limitations.
Implementing a sequential process involves using
a 'folder watch' or 'directory watch' DLL (Dynamic Link Library).
Numerous such DLLs can be found with a quick Internet search.
The DLL is used to test for the creation of the 0-0-0.jpg
thumbnail file - the last file created in the conversion -
before proceeding to the next conversion request. (If using
Zoomify's optional 'one-file' storage approach, test instead
for the creation of the final PFF file.)
Customer feedback note: several customers have experienced good results working with the product WatchDirectory by GdP software (http://www.watchdirectory.net). While Zoomify has note tested this product and is therefore not able to recommend it, this note may prove useful for customers considering product alternatives.
top of section | top of page
How can my server-side script tell when the conversion of
an image is complete?
The Zoomify Converter proceeds through an orderly
process in creating a Zoomify Image - whether folder-based
storage or single-file PFF-based storage is chosen. In the
case of folder-based storage, the last step in conversion
is the creation of the 0-0-0.jpg thumbnail file. In the case
of single-file PFF-based storage, the last step in conversion
is creation of the final (non-temp) PFF file itself. In both
cases, a server-side script can verify conversion completion
using a 'folder watch' or 'directory watch' DLL (Dynamic Link
Library). Numerous such DLLs can be found with a quick Internet
search. For additional information see the question 'How
can I script conversion of one file after another?'
top of section | top of page
How
can I create a Zoomify Image from multiple source images?
Zoomify's Enterprise converter supports creation
of Zoomify Images from multiple source image files. These
image 'strips' or 'stripes' can be created by microscopy equipment
frequently used by digital pathologists. In addition image
tiles available from similar equipment can be combined into
strips for use with this Zoomify feature.
The requirements for making use of this support
are as follows:
1. This feature is supported only in our Zoomify Enterprise
converter;
2. This features has not been tested with image formats
other than TIFF;
3. The image strips must be horizontal - that is, they must
be wider than tall. They therefore represent slices that
are stacked vertically. For clarification, note that the
x values vary only slightly while the y values vary significantly.
That is, the image strips may be slightly out of line to
the left and right, while they are offset up/down by up
to the full height of a strip.
4. The format of the text file must be exactly as follows:
3842x_1.tif
0.000000 0
3842x_2.tif 0.788357 2006
3842x_3.tif 0.723662 4011
The first column contains image strip filenames,
the second contains x values and the third contains y values.
The columns are separated by a space, not a tab, comma,
or other character. The file must not contain any additional
content - no extra columns, no extra lines, no notes or
comments.
5. The source images' filenames must match
those in the text file. They must provide a clear order
for the image files. The filenames must be simple, web-friendly
names - underscores and dashes are supported, but not spaces,
as these are used for delimited the columns.
6. The filename's extension must be '.apr'.
If the text file has a '.txt' extension the converter will
ignore its contents.
A text file in the above format can simply be
dropped upon the Enterprise converter and the named image
files will be loaded sequentially to produce one Zoomify Image.
top of section | top of page
What formats does the Zoomify Converter support?
The Zoomify Converter natively supports TIF,
BMP, and JPEG formats. Numerous additional formats are supported
through the built-in Zoomify Export available in Adobe Photoshop
CS5, CS4, and CS3. Note that the Zoomify solution can also
work in conjunction with third-party image servers to access
image content stored in certain proprietary image formats.
See the question 'What
third-party storage alternatives is Zoomify compatible with?'
for additional information.
top of section | top of page
I'm seeing
errors using the Zoomify Enterprise Converter. How can I fix
this?
The Zoomify Converter supports a wide variety
of formats, many of which are extremely flexible (for example,
TIF). As a result, it is possible that some files in some
formats may not be supported. This may result in an error.
Additionally, many customers convert very large numbers of
image files which raises the possibility of occasionally encountering
a corrupt file. Lastly, there are formats Zoomify does not
support, attempting conversion of a file in such a format
can cause an error to be presented.
In each case there are several simple steps to observe to
quickly ascertain the cause of the error and, most commonly,
resolve it. First, verify that the format is natively supported
by Zoomify (TIF, BMP, JPEG).
Second, verify that the image file is saved in the RGB color
space rather than CMYK. Zoomify support for CMYK is not yet
available.
Third, verify that sufficient disk space and
memory are free for the conversion process. You may also wish
to close any other programs to help determine if a conflict
is occurring.
Lastly, a simple resolution can often be achieved by opening
the image file in an image editor such as Adobe Photoshop
and saving it out to a new filename. If this does not resolve
the problem, try saving it to a new filename in a very simple
format such as BMP or JPEG.
Special note: It has been reported by some customers that
Microsoft.Net 1.1 produces PNG images that may possess invalid
optional settings. These settings can cause the Zoomify Converter
to fail to complete conversion. Additionally, conversion from
such PNG files to BMP files can cause optimization of the
colorspace of the resulting image file in a manner that also
causes problems for many image editors as well as for the
Zoomify Converter. A workaround for this problem is to open
the PNG or BMP in an image editor and save it to a new file
after verifying that the image is set as RGB.
top of section | top of page
The Zoomify Converter was working, but now I'm seeing errors. How can I fix this?
It is sometimes possible for one unsuccessful
conversion attempt to interfere with subsequent conversion
attempts. This is because the Zoomify Converter creates temporary
files and a preference file during conversion and, if the
conversion is interrupted, these temporary files can remain
undeleted and potentially improperly formatted. Possible reasons
for an initial conversion failure include a corrupt source
image, memory or disk shortages, conflict with other running
software, or an operating system error. Undeleted temporary
files can be found by searching for files containing 'pff'
in their filename (other than properly converted files with
a '.pff' extension). Additionally, find and delete the file
'zoomifyConvertPrefs.asp'. This preferences file will be located
next to the converter (in the same folder), or for some versions
on Windows, in the directory: Windows | Zoomify | Viewer |
Cache. Note that the converter will create a new preferences
file during any subsequent conversion if it is not already
present. Deleting temporary files and the preferences file
will help eliminate any errors on subsequent conversion attempts.
top of section | top of page
Where can I see detailed steps to set up the Zoomify Annotation System?
The Zoomify Enterprise User's Guide provides
detailed information on setting up the Zoomify Annotation
System. In addition, the questions 'What
should my ZAS HTML parameters look like?' offers detailed
examples of annotation web page setup and the question 'If
I need a servlet container, how do I set it up?' provides
helpful information on setting up a servlet container if your
implementation will use the Zoomify Servlet for saving annotation
edits, or if your implementation will be based on single-file
PFF storage rather than folder-based storage.
top of section | top of page
What should my ZAS HTML parameters look like?
The following are example Zoomify Annotation HTML parameters in view mode (non-editable):
The following are example Zoomify Annotation HTML parameters in view mode (non-editable):
NOTE: only the gXMLSaveHandlerPath parameter is added to make the first (view mode) example into the second (edit mode) example.
NOTE: only the 'FlashVars' parameter content is Zoomify-specific. Everything else is common to other Flash embed statements. The FlashVars parameter is supported by the Flash Player exactly so that information can passed into a Flash movie with specific data needs.
top of section | top of page
What alternatives are there for saving Zoomify Annotations?
Zoomify annotations are stored as simple text in XML format - one xml file per image. Because of this, the process of saving or 'posting' new or edited annotations is very simple. Zoomify Enterprise includes a sample ASP page that is
very small, just 16 lines (not counting blank lines). It can be easily ported to JSP, PHP, Python, PERL, or the scripting language of your choice.
In addition, Zoomify Enterprise includes the Zoomify Servlet. This is primarily
used for support of 'one-file' PFF-based image storage (in which the servlet extracts JPEG 'tiles' from within a singe file with a '.PFF' extension), however, it can also support annotation posting requests. Because servlets require servlet containers (such as Adobe JRun or Tomcat)
setting up this approach for saving annotations is unnecessary extra effort unless the servlet is already being used to support PFF-based image storage.
Additional information regarding using JSP to save annotations in included in the answer to the questions "How can I use JSP for saving Zoomify Annotations?"
How can I use JSP for saving Zoomify Annotations?
Saving Zoomify Annotations using JSP requires
the same general steps as using the example ASP page included
with Zoomify Enterprise. For this reason, porting the example
ASP to JSP should present no significant challenges. However,
saving annotations from Flash via a JSP page will differ in
some respects. With respect to those differences, the following
notes may be helpful:
1. Flash doesn't need "returnToFlash" before key/value pairs in the response - though Adobe examples do include this. That is, the following is not required:
out.println("returnToFlash = %22serverResponse=saveSuccessful%22");
2. The content type of the response should be set as "text/plain".
3. For as yet unidentified reasons, JSP page directives to import other JSP pages confuse Flash.
Example JSP page for returning a response from JSP:
This example will properly display a response - "saveSuccessful" or "saveFailed" - when saving from Flash via a loadVars with a sendAndLoad and a replyData handleReply.
top of section | top of page
What is the specification for the XML used by ZAS?
The Zoomify Annotation Viewer uses a straightforward XML structure for annotation storage. This structure is tagged in a self-explanatory way, though additional documentation is planned.
The Zoomify web site implementation serves as a useful example case. The relevant demos are at: http://www.zoomify.com/enterprise.htm. Two can be found: 'Medical Annotation' and 'Defense Annotation' - both of which can be viewed in read-only and editable mode.
The XML for the sample content in the medical example follows below. Record tags include POI ('point of interest') designators. Field tags include x, y, zoom, user, date (date/time), id, and name. Subrecords include Labels and Notes, each with their own field tags, as listed below.
Note that direct editing of the annotation XML is never necessary as the Zoomify Annotation Viewer provides a simple means of visual editing. The information in this TechNote is provided primarily to support output of XML in a Zoomify-compatible format from pre-existing database resources, or database systems that are to operate in an integrated manner with the Zoomify Annotation System.
top of section | top of page
How can I use the Zoomify Annotation System with my database backend?
The simplest and optimal approach for integrating
the Zoomify Annotation System with a database backend is to
continue to rely on the built-in XML loading support in the
Annotation System for viewing purposes, but to use your database
for master storage purposes. That is, should an annotation
author post changes to the annotations of an image via the
Annotation System, these changes can be posted to the database
which would then recreate the XML and overwrite it. All other
annotation access would be via the XML, with read requests
being fulfilled by the web server as usual. This approach
minimizes impacts on the database server and simplifies system
setup and development.
top of section
| top of page
What screen capture options are available?
The Zoomify Annotation System was designed to
support high-resolution capture of the current view in order
to support the publishing needs of many of our customers.
The current solution depends on a custom ActiveX and/or plugin
that has proven difficult to maintain as browsers and operating
systems have rapidly changed. We are developing an alternative
approach for our next version that is expected to be easier
to implement while still being simple and intuitive to use.
We appreciate your patience as we pursue the necessary development
to complete this complex functionality.
top of section | top of page
Does the Annotation Viewer support initial x, y, and zoom parameters?
The Zoomify Annotation Viewer does not currently
support the initial view parameters that are present in our
non-annotation viewers. This oversight will be addressed in
our v4 solution. Thank you for your patience.
top of section | top of page
Why is the Annotation Viewer's gUser parameter sometimes not applied?
Reports have been received of a gUser parameter
problem which causes the parameter to fail to properly function
in certain contexts. We have explored several possible fixes
for our v3 product but it is now expected that our v4 product
will address the problem and serve as a substitute solution.
top of section | top of page
Why is the Annotation Viewer's Open Palette hidden or off center?
We have received reports that the Open Palette
may position incorrectly given in certain contexts. We are
investigating this issue but it is expected that our v4 product
will address the problem and serve as a substitute solution.
top of section | top of page
Can I customize the Zoomify Annotation Viewer?
Yes, of course. Complete '.FLA' and '.AS' source files
are included in the Zoomify Enterprise product. Customization
requires a Flash editor and some familiarity with Flash (and
preferably with ActionScript as well). The Zoomify ActionScript
API Reference contains considerable information that will
prove useful and can be acquired at no cost by contacting
us.
top of section | top of page
Can I customize the Zoomify Dynamic Viewer?
Absolutely. Complete FLA source files are included
in the Zoomify Enterprise product. Note, however, that the
Zoomify Dynamic Viewer has been specifically designed to support
viewing of content served by third-party image servers. For
projects requiring neither annotation nor access to content
served by third-party image servers it is advisable to begin
any design or development efforts with one of the Zoomify
Viewers included in the Zoomify Flash product. These support
standard zoom-and-pan viewing as well as enhanced viewing
capabilities such as Slideshow, Hotspot, and Rotation viewing.
The Zoomify Flash product is available to Zoomify Enterprise
customers on request. Simply contact
us.
top of section | top of page
Where can I find more information about custom viewer alternatives?
Our Zoomify Flash product is designed specifically
for Flash designers and developers and includes substantial
resources to support viewer customization. These include eleven
different Zoomify Viewers supporting numerous enhanced features,
a User's Guide more focused on Flash and ActionScript editing
and component use as well as a complete Zoomify ActionScript
API Reference. The Zoomify Flash product is available on request
to Zoomify Enterprise customers.
top of section | top of page
What third-party storage alternatives is Zoomify compatible with?
Zoomify provides a flexible viewing and annotation
interface, which, through modular design, delivers maximum
compatibility with popular repository structure alternatives:
XML-format text files per image, SQL database, etc. We are
currently working with Aurora Interactive, Aperio, MicroBrightField,
and other content management solutions to define the ideal
integration path. We are also working with partners to provide
a more generic database interface.
top of section | top of page
How
can I use Zoomify with image servers from other companies?
Zoomify's Enterprise product viewers are able
to view image data served by several image servers from other
companies, including Aperio Technologies and LizardTech (now
Celartem). Please note that 3rd party technology is continually
being modified. The information here as well as in the Zoomify
Enterprise User's Guide may therefore need to be supplemented
by information from the relevant vendor.
Viewing image content in a Zoomify Enterprise
product viewer requires using different HTML parameters. Both
the bytehandler path and the image path will change.
For Aperio's Image Server, the bytehandler path
will be as follows: "http://xxx.xxx.xxx.xxx:<port>".
The image path format will be: "/myImage.jp2.apr".
The Aperio Image Server may return progressive
JPEGs in certain configurations. This feature should be automatically
be disabled upon requests from a Zoomify viewer, however,
should this not occur, the feature can and should be disabled
manually.
Working with a LizardTech Content Server, the
bytehandler will be as follows:
http://xxx.xxx.xxx.xxx:<port>/lizardtech/iserv/browse
The image path format will be:
cat=test_images&style=none&img=test.sid
For examples of standard Enterprise viewer Flash
embed statements, please see the examples on the Enterprise
product page on the Zoomify web site. Modifying the HTML in
these examples as noted above will provide an easy route to
creating web pages specific to your needs.
Please note that when using Zoomify with image
servers from other companies, the viewer SWF must reside on
the same domain as the image server. Other deployments require
the use of a 'cross-domain policy file' on the target server.
This is a standard Flash Player security requirement. Additional
information is provided in the relevant question in this FAQ.
top of section | top of page
Can
I use Zoomify with Aperio Annotation?
We're very pleased with our partnership with
Aperio and have had good success meeting the needs of our
mutual customers. Our Annotation System is able to talk to
Aperio's Image Server to request image data, it is not, however,
able to request annotation data at this time. Please note
that the Zoomify Annotation System can be used in combination
with Aperio's Image Server in a hybrid manner, presenting
image data served from an Aperio Image Server while displaying
annotation data stored in the default Zoomify Annotation System
xml file structure. For additional information on using Zoomify
and Aperio technologies together, please refer to the Zoomify
Enterprise User's Guide.
top of section | top of page
Can I use Aperio
SVS files with Zoomify?
Aperio has been aggressively developing their
SVS file format to take advantage of the benefits of TIF,
JP2 and other technologies. At the current time SVS files
can be accessed via Zoomify Viewing technology courtesy of
an enhanced viewer SWF that works in conjunction with the
Aperio Image Server. The latest information on this capability
will be available from Aperio, however, as Aperio is the exclusive
partner of Zoomify for digital pathology we are eager to support
our common customers to ensure successful use of our technologies.
After contacting Aperio if you have any needs you feel we
can assist with please let
us know.
top of section | top of page
What
support does Zoomify offer for JPEG2000?
Zoomify has developed a sophisticated system
for viewing images stored as JPEG2000 files in Flash. This
best-of-both-worlds solution is currently in 'beta' form,
requiring only speed optimization and final testing for final
release. JPEG2000 is a complex format offering numerous encoding
options - any number of which can impact decoding speed as
relevant to zoom-and-pan interaction. Zoomify developed this
system over the past several years based on a leading third-party
software developer kit created by the author of the JPEG2000
reference implementation. The motivation for this development
effort included inquiries from numerous institutions. However,
the vast majority of these institutions have not yet decided
to deploy JPEG2000 within their application environments.
Zoomify has therefore chosen to suspend development pending
greater customer demand. Development resources are instead
being focused on more urgently desired features and functionality.
top of section | top of page
Does Zoomify support PDF, DICOM, or other formats?
Zoomify's converter currently supports the following
formats natively: TIFF, JPEG, and BMP. Support for numerous
additional file formats can be had using the built-in Zoomify
Export capability in Adobe Photoshop CS5, CS4, and CS3. Using
this feature of Photoshop one can create Zoomify Images from
content in any of the formats supported by Photoshop.
The Zoomify Converter creates tiled, tiered,
multiresolution image content stored in one of two approaches:
a folder of JPEG 'tiles' as well as a single-file approach
in which the tiles are all stored within a file with a '.PFF'
extension. This 'Pyramidal File Format' is tailored specifically
to meet the needs of multi-resolution network imaging. It
has a lightweight architecture, non-redundant tile header
optimizations, initial view optimizations, can support file
sizes greater than the 4Gig limit of TIFF, supports multiple
frames for animations and slideshows, and is even able to
store polygon data for 3D, panoramic and other rich media
types.
In addition to the pre-processing afforded by our converter, have invested in some development of server-side extensions that allow publishing directly from non-pre-processed images in certain formats. These include JPEG2000, PDF, and JBIG - though we have not commercialized the results of this development yet. This support could be extended to support DICOM should customer demand warrant it. No timeline has yet been established for further development in this area.
We are aware of the prevalence of images in the Dicom format within the medical arena and PDF images in the prepress market. We are eager to ensure that our development and product evolution is driven by customer needs and we welcome your input.
top of section | top of page
Does
Zoomify work with Akamai and other edge servers?
Zoomify's default 'folder-based storage' involves
just JPEGs, HTML, and a tiny Flash movie which functions as
the 'viewer'. This zoom-and-pan solution is completely standard
in terms of web server hosting, caching, and other publishing
considerations. Whether working with Akamai or another 'edge
server' system, the small JPEG image files which make up any
Zoomify view will be propagated over the network optimally
and independently based on demand - just as if they were individually
placed within a web page.
Zoomify's 'one-file' storage approach, in which
the JPEG files that make up different views of an image are
stored in a single file with a '.PFF' extension, involves
the use of a small Java servlet for fulfillment of file requests
during the zoom-and-pan viewing of site visitors. Due to Java
security requirements, the servlet may need to be distributed
to the edge servers to support image file delivery from the
edge network servers.
top of section | top of page
Other Products
Can
I still buy Zoomifyer Pro or Zoomifyer VR?
Zoomify is not currently selling the Zoomify
VR product or its precursor, Zoomifyer Pro. In fact, Zoomify
has not sold either product for many years. Zoomify's roots
are in panoramic, 3D, and other VR technologies and the decision
to shift resources to other imaging applications was a difficult
one. The primary driver was technology. Flash-based viewing
presents an opportunity to rapidly change how high-quality
images are used on the Internet. The opportunity to do have
the same impact on the use of high-quality VR images is both
more limited in scope and more difficult to realize: more
limited in scope due to the current overwhelming prevalence
of 2D photographic images; more difficult to realize due to
the extreme development, testing, and maintenance impacts
of non-Flash custom clients developed using Activex, plugin,
Java, and other technologies. We have created a special page
which provides additional information regarding the status
of our non-Flash based viewers and the related products. Please
review it and let
us know your thoughts. We appreciate your understanding
as we face the challenge of creating innovative solutions
within a challenging technology space and a rapidly changing
technology market.
top of section
| top of page
I'm
seeing errors at a web site that uses the Zoomify ActiveX,
Plugin, or QuickTime viewer.
Due to the substantial period of time since we
refocused our development resources on Flash-based viewing
and related products numerous browser, operating system, and
other changes have occurred in the context of the non-Flash
viewers. Additionally, the Zoomify web site have undergone
several complete overhauls. As a result it is possible that
some web sites using these special clients may require modification.
We are doing our best to support the creators of such sites
and appreciate you letting
us know the URL of any site you encounter that is having
problems as well as any contact information you may have for
the site's web master. In addition, you may benefit from the
information we have made available at a special page we have
created which provides additional information regarding the
status of our non-Flash based viewers and the related products.
Please
review it and let
us know your thoughts. We appreciate your patience and
support.
top of section
| top of page
My
site uses the Zoomify ActiveX, Plugin, or QuickTime viewer,
how can I update it?
We have created a special page which provides
additional information regarding the status of our non-Flash
based viewers and the related products. Please review
it and let us know
if you still require assistance. We appreciate your patience
and support and will do our best to assist you in resolving
any issues you are encountering.
top of section
| top of page
