dw08gm:
The images we are talking about are event images, not product images, which could be in any of the prescribed graphical forms, and not limited to scenic photos or scans. The main type of image I envisage most shopowners uploading for their event image is an informational flyer or poster, mostly containing text but which could also include a map, corporate logo and other graphics, including photos.I think that everyone participating inthis conversation understands that we are not talking about product images.. So yes we are indeed all on the same page..
dw08gm:
If the shopowner drafts the flyer themselves, and have already been through the process of size editing their product images, then they should already be familiar with many of the layout constraints of zencart sufficient to determine an appropriate size of their event image.You cannot make this assumption.. Not every shopowner will be drafting their own flyers or even understand FULLY the constraints of Zen Cart. YOU may understand this, but I can assure you from my years of experience working with end users is that I would NEVER make this assumption. I do believe that Rus will concurr with my thoughts here since he and I have worked in the same line of work outside this forum (he as a developer and I as a Business Analyst)..
dw08gm:
If, however, the shopowner is participating in an event organised by or under the direction of others, such as operating a stall at a sporting, artistic or cultural event, then the shopowner may be required to use an event image supplied by the organisers, which could come in any format. The particular instance I was referring to is where a shopowner downloads or otherwise acquires a graphic from another source and then simply inserts that graphic directly into the shopowners website.
Understood.. But to Rus' point we see shopowners who upload their OWN images from digital cameras. This is NOT a good thing.. and NO you cannot assume they will or even know how to edit these images..
dw08gm:
The code supplied in tpl_events_calendar_default will handle all sizes of event image (up to 2048kb IIRC) and reduce the image only so far as to fit it into the events page and without physically altering the size of the image. This I consider a good thing, as the graphic is not altered to fit the page but delivered to suit the customer. If the customer then saves the event page, the event image as supplied will also be saved at its intended size, which then allows a customer to view the event image offline and print or otherwise use it at their discretion.This statement right here says that there are two different images in use
- the image that is displayed on the event page
- the image that is saved/downloaded (flyer) by an event participant.
The display and print image cannot be one and the same image file as the requirements for displaying an image on a page and downloading an image for print are different. The code supplied in the Events Calendar uses poor practices for displaying the images, and keeping this improper display code in place just for the sake of having a print sized image is not the right way to deliver a print sized image.
We also don't want to use artificial means of displaying event images.. Down and dirty why it's not a good practice to use height and width tags to artificially re-size images..
While it is advisable to specify actual image height and width via these tags, it's not advisable to use these tags to change the image display size for a few reasons.
-
- You're forcing your viewers to download larger files then they need. Cropping your photos before putting them on your Web page will result in smaller files and less download time.
- Browsers don't do a very good job of resizing images. The images are going to look either blurry or blocky if you resize them via the browser. GIF images are the worst. Never resize GIF images via the browser; they'll look awful!
- Resizing in the browser requires more time to render the page and uses more of your viewer's system resources and RAM.
IF the image should be available for printing at dimensions meant for print, then there really should be a function that explictly calls the print sized image and delivers it to the printer. (or for download)
AND..
That code will STILL need some admin configurable parameters to ensure that 2500 x 2500 images are not uploaded and delivered as print images.
dw08gm:
I hope you can see there is more to event images than may first meet the eye.
I do, but I hope you can also see that the code in this module doesn't fully satisfy the requirements for images without some modifications..
dw08gm:
Diva
I really do appreciate your comments and criticisms and hope that I am not responding in too harsh a fashion as to drive you away.
Sunday, when I am back on my main pc, I hope to properly address all of these issues, but for the moment I am using a win8 laptop that drives me half-crazy with the things it makes me endure.
CheersNo worries.. Just trying to add something useful to the conversation. Hope you don't mind.. At the end this will make things better right??
dw08gm:
It works to my satisfaction in the ec4_alpha version, in that it only provides a link in event manager and the event page. I am still a little unclear as to what Rus was trying to achieve with this.
cheersAnd I'm going to work with Rus to figure out why it doesn't work on my test store since he reports it works on his.. So I'm sure it's a completely resolvable issue..