Thanks Albrecht, that's exactly my opinion and the reason I want to develop this module :-)

2017-01-12 15:15 GMT+01:00 J Albrecht :

On 07 Jan 2017, at 09:41, Juan Jose Casafranca wrote:

They need a way to organize their library, which DK is good at, and a way to process raw files, which DT is
good at (DK is not a good raw processor and DT is not good for library management).

For the Developer’s benefit, I’d like to reiterate the above statement: digiKam is a brilliant program but please, let’s maintain the focus on where it is brilliant rather than trying to craft it into an all-singing-all-dancing piece of bloatware comprising relatively mediocre modules just for the sake of doing so. In the FOSS realm, digikam is an excellent Digital Asset Management program, darktable is, IMHO, the best Raw editor and GIMP is unparalleled for post-processing. It’s folly and perhaps a bit arrogant to assume that Users would willingly be hobbled by using only one program simply because they are “loyal” to that program.

Wouldn’t it be nice if we could just all get along….

On Thu, Jan 12, 2017 at 5:15 PM, J Albrecht wrote:

For the Developer’s benefit, I’d like to reiterate the above statement: digiKam is a brilliant program but please, let’s maintain the focus on where it is brilliant rather than trying to craft it into an all-singing-all-dancing piece of bloatware comprising relatively mediocre modules just for the sake of doing so. In the FOSS realm, digikam is an excellent Digital Asset Management program, darktable is, IMHO, the best Raw editor and GIMP is unparalleled for post-processing. It’s folly and perhaps a bit arrogant to assume that Users would willingly be hobbled by using only one program simply because they are “loyal” to that program.

..or you could politely ask whether having a switch for the preferable raw plug-in is planned for GIMP (hint: it is).

Alex

That is the point. Askibg which raw processor to use when decoding the raw file for showing the preview and thumbnail.

Anyway, I have been trying to understand the code and doing a todo list and it looks like a lot of work just for me (as I dont understand the code). The todo list is:
-Add code to generate the thumbnail when thumbnails are being created (this is easy and its done, although in a very bad manner) -Schedule thumbnail creation when a raw file OR the file where the edition is saved are modified. This is not done and I dont know how to do it. Maybe a new table in the database where we stored the edition files and the image file which are related to. When an edition file is changed, schedule an update for the image.
-Being able to show several thumbnails for a single raw file is several editions coexist. Maybe the previous approach can do this also. -Config for selecting the raw processor.

Without some help from a experienced developer its impossible for me to do all this tasks in a correct, bugfree and eficient way. So unless a developer wants to help me with support, docs and code, and I know they have other roadmap, Ill have to leave the project, as I dont have enough time for solving those task in my own.

Thanks!

El 20 ene. 2017 21:09, "Alexandre Prokoudine" < alexandre.prokoudine@gmail.com> escribió:

On Thu, Jan 12, 2017 at 5:15 PM, J Albrecht wrote:

For the Developer’s benefit, I’d like to reiterate the above statement:

digiKam is a

brilliant program but please, let’s maintain the focus on where it is

brilliant rather

than trying to craft it into an all-singing-all-dancing piece of

bloatware comprising

relatively mediocre modules just for the sake of doing so. In the FOSS

realm,

digikam is an excellent Digital Asset Management program, darktable is,

IMHO,

the best Raw editor and GIMP is unparalleled for post-processing. It’s

folly and

perhaps a bit arrogant to assume that Users would willingly be hobbled

by using

only one program simply because they are “loyal” to that program.

..or you could politely ask whether having a switch for the preferable raw plug-in is planned for GIMP (hint: it is).

Alex