[digiKam-users] Web based interface (in PHP etc)
Daniel Fenn
danielx386 at gmail.com
Wed Apr 10 21:49:02 BST 2019
Personaly I would just store thumbnail in the database but having extra options is always nice.
________________________________
From: Tac Tacelosky
Sent: Wednesday, 10 April 2019 11:24 pm
To: digiKam - Home Manage your photographs as a professional with the power of open source
Subject: Re: [digiKam-users] Web based interface (in PHP etc)
Although it might seem like bad programming practice to put jpeg/png blob in a database instead of a filesystem, I'd love that option. In particular, it'd allow a cloud-based solution to not require an disk usage, making it cheaper to deploy.
That is, pay for a cloud-based database, then use a free or low-cost deployment like heroku, create a dynamic site, and not need access to the original images to create the thumbnails, nor need access to a disk system in the heroku deployment.
A second database could be used, or another table in the database with the image blob, but MUCH better would be an option for how you wanted in the images stored. PNG and JPG rendering will come from a library, so perhaps the developer would be open to this, even if it renders images differently than the current method.
Of course, the images could also be stored on s3, but that's considerably more complicated, since the images are de-coupled from the database.
On Wed, Apr 10, 2019 at 4:41 AM Daniel Fenn <danielx386 at gmail.com> wrote:
>
> I wonder if it would be possible to get that changed, not just for this Web project but to make everything accessible for future generations to come.
>
>
> ________________________________
> From: Tac Tacelosky
> Sent: Tuesday, 9 April 2019 9:37 pm
> To: digiKam - Home Manage your photographs as a professional with the power of open source
> Subject: Re: [digiKam-users] Web based interface (in PHP etc)
>
> The thumbnails are stored in format that hardly anyone uses (blanking on the name of it now). In particular, there are no PHP libraries for reading it, even integrating GD, the popular and powerful image manipulation library.
>
> I wish there were an option for selecting the thumbnail format, which included jpg and png (and the associated quality and size options). Even if the database were bigger, it would allow much easier access to the thumbnails, without all the complications of re-creating thumbnails from somewhere else.
>
> Tac
>
> On Mon, Apr 8, 2019 at 4:12 PM Daniel Fenn <danielx386 at gmail.com> wrote:
>>
>> To answer a question about if thumbnails can be extracted from a database, it depends on the format. Is it an jpg file or something like that?
>>
>>
>> ________________________________
>> From: jdd at dodin.org
>> Sent: Tuesday, 9 April 2019 5:38 am
>> To: digikam-users at kde.org
>> Subject: Re: [digiKam-users] Web based interface (in PHP etc)
>>
>> Le 08/04/2019 à 21:07, woenx a écrit :
>> > Are we talking about the same piwigo?
>>
>> I don't know what you expect. I use Piwigo for a lot of time now, with
>> success
>>
>> http://dodin.org/piwigo/index.php
>>
>> > serious rough edges that prevented normal usage, such as displaying any
>> > directory that had special characters such as aphostrophes
>> > (https://piwigo.org/bugs/view.php?id=3030).
>>
>> like any software it have syntax guidelines. I can use "?" in file names
>> (linux), when Windows wont like them... nor piwigo. use "detox" and voilà
>>
>> http://www.dodin.org/wiki/pmwiki.php?n=Photo.GestionDesImages#toc8
>>
>> >
>> > Apart from that, I personally prefer to write the metadata in the same
>> > picture file instead of sidecar files
>>
>> the problem is syncing metadata to/from web/local. It's not possible to
>> send or receive full image files only to sync metadata, when moving xml
>> files is easy and cheap. This do not prevent writing also to the images,
>> as I always do
>>
>> jdd
>>
>>
>> --
>> http://dodin.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20190411/e9058c3d/attachment.html>
More information about the Digikam-users
mailing list