From: "BJ Freeman" <[EMAIL PROTECTED]>
this gets somewhat complicated since there are many varialbles to
consider and present to the person doing the upload.
size( in dimension and file size), lenght and width ratios
and a few others would probably be confusing.
Using a WYSIWYG like gimp is a better alternative.
Yes this was my answer too (resize your images for better user experience and bandwidth performance).
But the prospective client was not satisfied since she said she has a lot of images changing everyday.
So the inline resizing is my answer so far. You can't have your cake and eat it !
Jacques
Jacques Le Roux sent the following on 7/27/2008 3:16 PM:
From: "Bruno Busco" <[EMAIL PROTECTED]>
BJ, the CSS resize is something that is performed in the web browser; the
image file is downloaded as it is saved in the server and then locally
resized according to the css specified dimensions.
Having only a large file stored in the server is very band consuming
when,
for example, many images are displayed as thumbnails in one page.
On the other hand, having only a low resolution (light) file is bad
when you
want a single large image in one page to show details.
This is why normally several formats of the same image are stored in the
server.
The way ofbiz handles the small, medium, large and detailed images
could let
to have also completely different images but I do not now I often this
feature is used.
I think that having a mechanism that when the detailed (high resolution)
image is uploaded automatically generates all other small, medium and
large
would be very useful.
In some systems I have seen a derived image is generated the first
time it
is requested by a client.
Yes, I have been asked this question sometimes too... Some people wonder
why resizing online over and over, some argue that loading
3 different images is a bandwidth waste. I never did a profile on this,
would be curious if someone did (OK I understand it depends
on a lot of things ;o)
I agree that providing an optionnal such one-time-resizing-and-save tool
OOTB would be cool...
Jacques
2008/7/27 BJ Freeman <[EMAIL PROTECTED]>
The would be handled by assigning a class type to the image and put in
the CSS.
I believe that is done now, if not then it would be a nice addition. you
would specify the same image path for all
https://demo.hotwaxmedia.com/catalog/control/EditProductContent?productId=dropShip1
then change
applications/order/webapp/ordermgr/entry/catalog/ *.ftl's that show
images like
productdetail.ftl
to put the classes for image sizing you put in the
framework/images/webapp/images/ecommain.css
Bruno Busco sent the following on 7/27/2008 8:38 AM:
> Hi,
> does anybody know if there is some mechanism to have a sort of
control on
> uploaded image sizes?
> I mean, l would like that when I upload a new image for a product
ofbiz
> automatically generates the small, medium, large and detailed images
scaling
> the uploaded image with a fixed dimension regardless of the
original one.
>
> Many thanks,
> Bruno
>
