Re: --no-thumbnails

David Squire wrote:
> Jonas Lindqvist wrote:
>   
>> Silly me...
>>
>> Here's a new version, containing your hostname stuff as well.
>>
>> Sorry about that.
>>     
>
> No worries. I'll tidy this up, mail it back for you to test, and then we
> can think about committing it. There is some stuff that needs to be
> added to make it consistent with the way the stuff for
> $ENV{HOME}/.gift-add-collection works.
>   

Hi Jonas,

I notice that you have decided to still have a thumbnail url generate
when the --no-thumbnails option is in effect, but to have it simply be
the same as the original image.

This is not what I would have done. I would not only not create the
thumbnail, but would also suppress the thumbnail-url-postfix attribute.
I would expect the client to make a choice of what to display in the
absence of that attribute. For example, my Perl client does this:

    # output the image thumbnail (if it exists), linked to the main image
    print "<A HREF=\"$self->{elementLocation}\">";
    print "<IMG BORDER=\"0\" ALT=\"$self->{elementName}\" ";
    if (defined $self->{elementThumbnailLocation}) {
        print "SRC=\"$self->{elementThumbnailLocation}\"";
    }
    else {
        print "WIDTH=\"128\" SRC=\"$self->{elementLocation}\"";
    }

where the various (renamed) XML attributes are in the $self hashref.

Can anyone tell me whether the other clients behave this way?

Regards

David

PS. Wolfgang, I would also like to hear your thoughts on this from an
"MRML policy" point of view.


-- 
Dr. David McG. Squire, Senior Lecturer. On sabbatical in 2006.
Caulfield School of Information Technology, Monash University, Australia
CRICOS Provider No. 00008C       http://www.csse.monash.edu.au/~davids/