Foster660:
G'day all,
After a lot of trial and error, I've finally setup this module (ver 2.1.1) into ZC 1.5.5, which seems to be working as it should...
I do have one issue that I can't figure out in that all the pictures (which ARE enclosed in the colorbox) are showing larger than the screen size. It could be the fact that the files are on the large size, but I would have thought they would be resized to suit the screen size.
Am I missing something, or did I just do it wrong? (again...!)
Here's my problem page -> http://www.labelx.net/index.php?main_page=product_info&cPath=2_3_5&products_id=2
that will give a better idea of what I'm babbling about.
Thanks in advance :)
John
Wouldn't say that you missed something specific to the plugin, perhaps could have some improvements to what is presented to the plugin and once provided accomplish additional display modifications by the below.
So sort of two things, the colorbox software can support resizing of an image with the following additional constraints which are also shown from the developer's page: http://www.jacklmoore.com/colorbox/
Dimensions
|
Parameter |
Default Val |
Description |
width |
false |
Set a fixed total width. This includes borders and buttons. Example: "100%", "500px", or 500
|
height |
false |
Set a fixed total height. This includes borders and buttons. Example: "100%", "500px", or 500
|
innerWidth |
false |
This is an alternative to 'width' used to set a fixed inner width. This excludes borders and buttons. Example: "50%", "500px", or 500
|
innerHeight |
false |
This is an alternative to 'height' used to set a fixed inner height. This excludes borders and buttons. Example: "50%", "500px", or 500 |
initialWidth
|
300 |
Set the initial width, prior to any content being loaded. |
initialHeight
|
100 |
Set the initial height, prior to any content being loaded. |
maxWidth
|
false |
Set a maximum width for loaded content. Example: "100%", 500, "500px" |
maxHeight
|
false |
Set a maximum height for loaded content. Example: "100%", 500, "500px" |
One or more of the above can be set/added in includes/classes/zen_colorbox/options.php
The values in the second "column" (Default Val) represent the default value that is used by the code when no assignment is provided.
The current implementation of the software in this plugin offers only the initialWidth/initialHeight settings from the admin.
When I said that there are two things, well, the second is that even without assigning a final/designated maxWidth or maxHeight, the image as compared to either earlier versions of the additional software or earlier versions on a mobile device is that it seems that the image no longer needs to be "chased" while trying to see the image better.
As to why the other options have not been incorporated directly, well there are a few excuses and a few suggested "reasons". I know that one thing is that as you said you're using the actual large sized image which has not been resized say as is done with Image Handler 4 where it will downsize an image to fit within a desired size or by use of the settings in the above table, but another aspect of consideration is how the software/image will respond to attempts by the end user to resize the image after display within the window at a size amenable to the device. Ie. will the image again be resized to fit the knew "view" or will it allow zooming in to really see a larger image?
The goal of the larger image is to be able to see the detail better than as originally presented. Continuously "downsizing" the image to the screen display makes this less than useful if unable to "zoom in" to see that detail. Yes, at the same time making the image unviewable because of its tremendous dimensions also has a negative impact on the user experience. The jquery operation of the colorbox code offers a balance to/with that, but also do other utilities that will push a more appropriate size (potentially less data and therefore faster operation than the recipient's processor making adjustments). Ie. Presenting a downsized image to the device provides this reduction in data and increased speed.
I will look into adding some of the above as features for the plugin, to increase its out-of-the-box versatility. Of course with added features comes the need for additional support.