bpkri wrote:hm?
Why can the ID not be used for the fullsized image? I mean, it is accessible via an ID, just like any other version of a photo (like the thumbnail), too.
[...]
Because every photo, if fullsized, or thumbnailed, has its own ID.
So the thumbnailed picture of one photo has another ID than the fullsized picture of the same photo.
So if you'll provide a single ID to the markup-tag, this can only be either for the fullsized-, the sized-, or the thumbnailed picture.
So, lets assume that you'll provide the ID for a thumbnailed picture, then the plugin has to go through the whole /alsbums/cache/derivates directories (and subdirectories), and to read *every* single *.inc file there, to get the correct ID for the other (fullsize and sized) pictures of this photo, because the thumbnailes are stored in *.dat files and the information on how to find the correct *.dat file is stored in a *.inc file which hold a serialized array of all the information of one picture.
Exactly the same, if you'll provide the ID of a fullsized-image.
And also the same in the case of a fullsized picture, if you'll provide the name of a photo. Then the plugin only has access to the ./albums/albums directory where the fullsized images are stored under their correct filenames. But again, to get then the ID of the appropriate thumbnail, the plugin has again to go through all these ./albums/cache/derivates directories, which we can not do, really not - Not for every single picture.
There is no other way, to get the appropriate thumbnail or either the ID of any picture.
The way it is done now, is really the best way.
The plugin generates its own thumbnails. So no need to grab for the IDs and this all.
But without these IDs, the plugin can not link to a picture in the gallery2. It only can provide direct links to the self generated pictures.
That's quiet logically, not? *g*