Page 1 of 1
Using thumbnail images in component
Posted: Sat Oct 16, 2010 11:28 am
by kekeljevic
Currently component is using original images. This slows down loading a lot, for opening a galleries with great amount of images. It would be wise to use thumbnail images.
There are two possible solution for this:
1. First is to use existing thumbnails and to create missing thumbnails and then use them, like plugin works.
2. Other is to create thumbnails in cache, and use them from there, like similar gallery systems works.
Re: Using thumbnail images in component
Posted: Thu Oct 21, 2010 1:03 am
by paveljosephson
(As you have stated you maybe want to save some image info in a database)
3. Save the thumbnail info in a database (kinda like your cache idea, but permanent as SQL data)
4. Save the thumbnail picture and the info in a database (the picture will be inside a BLOB field), and you could get all thumbs from the database. You could also add more info in the database, like 'show/don't show' and 'priority/order', the image description and image title. Maybe even more.
P.
Re: Using thumbnail images in component
Posted: Thu Oct 21, 2010 8:37 am
by kekeljevic
Actually, I did some testing with caching icons and it went just fine. Newest BETA release will use thumbs from cache.
But, idea of saving images and descriptions into database is worth of talking. Vasiljevski has similar ideas, he say this can be solution for many problems... Me personally love simplicity of image folder with XML files, possibility to move them around and make backups, but this permissions problems on Linux servers are quite headache...
Re: Using thumbnail images in component
Posted: Mon Nov 01, 2010 11:49 pm
by paveljosephson
Consideration for database would be the quicker access. Opening & reading files is slow.
Maybe we can do a speed test some time?
Permissions isn't really a hard problem, but it's often harder to implement.
You can solve the permissions problem by using a folder that you created yourself, like the Thumbs folder. I understand that you don't want to use that folder for the xml files, but maybe consider creating a XML folder that contains all the XML files? That way the script has the permission to write files.
I still would go for SQL tho. I like the speed and the versatility. You can easily add attributes when you need them without 'bothering' existing software, and it's quicker.
(9 years ago) we used yabb-forum, that used txt files for messages. It was SOOOO slow. We then switched to yabbse-forum, that uses MySQL, and it is so much quicker!
P.