Image is the main part of any product or service. In PHP, many developers has created the script that cut/crop the image into desired size in height and width. But in different project or Website Development process, developer has to setup the size and width according to design.
Another main issue is as per the design of the site, for single image, developer has to create different height and width image which is stored into specific folder with different name. So from personal point of view it is miss-use of space or better to say its time consuming process. Generally we have to create 2-3 images for single product to show in different pages.
Another issue comes with gallery. Most of the gallery scripts uploads the main picture and crop into different sizes and stores multiple images on the server without caring space on the server.
This all is simply west of time and space on server. This can be also a problem while deleting the record from the database and images as per the record. With database, we have to create 2-3 fields for the single record to store different image name as per the size like thum_1, thum_2 and main_image. This is clearly non-engineering of the database design.
I have best better way.
Lets simply upload original image and crop the image into desired size at RUN TIME or ON THE FLY.
This will solve your all the problems. Simply need one field into database to store the image name. While deleting - need to delete only one image.
Thanks
Mukesh
Another main issue is as per the design of the site, for single image, developer has to create different height and width image which is stored into specific folder with different name. So from personal point of view it is miss-use of space or better to say its time consuming process. Generally we have to create 2-3 images for single product to show in different pages.
Another issue comes with gallery. Most of the gallery scripts uploads the main picture and crop into different sizes and stores multiple images on the server without caring space on the server.
This all is simply west of time and space on server. This can be also a problem while deleting the record from the database and images as per the record. With database, we have to create 2-3 fields for the single record to store different image name as per the size like thum_1, thum_2 and main_image. This is clearly non-engineering of the database design.
I have best better way.
Lets simply upload original image and crop the image into desired size at RUN TIME or ON THE FLY.
This will solve your all the problems. Simply need one field into database to store the image name. While deleting - need to delete only one image.
Thanks
Mukesh