Using digikam on two computers?

[Turgut Durduran]

Hello,

I am a new user of digikam. So far I like it over my
previous method of using various perl scripts and
file-naming conventions.

I can't figure out one thing though (well, few more
too see below).

I use a desktop computer for storage of my photos.
That contains all my collections. Then I have a laptop
that contains a subset that I am working on --
cropping, adjusting colors, sorting, tagging etc. The
laptop does not have large enough of a hard-drive to
contain the whole set.

Ideally, I want to be able to open an album, tag my
photos, play with them on my laptop and somehow sync
with those on desktop. Ofcourse, I am talking about
digikam purposes, I know how to sync the files. This
is probably not so straightforward.  So I am thinking,
I should be able to "merge" two databases of tags
somehow. Is it possible?

Also, I tried converting a .nef file to BW and it
played (and pretty much destroyed) the preview file
and did not ask me for a "save as" option. Is that
normal behavior?

regarding exports to html. I realize that may be
question for the plugin forums but I will give it a
shot anyway. is it possible to change the layout?
colors etc? is it a css based system?

finally the print-wizard. can I create custom
thumbnail sizes?

thanks,

turgut






_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Duncan Hill-5]

Turgut Durduran wrote:

> Ideally, I want to be able to open an album, tag my
> photos, play with them on my laptop and somehow sync
> with those on desktop. Ofcourse, I am talking about
> digikam purposes, I know how to sync the files. This
> is probably not so straightforward.  So I am thinking,
> I should be able to "merge" two databases of tags
> somehow. Is it possible?

At the moment, no.  It has been discussed several times on the list in
the past few months - if you can find the archives, you should be able
to get a feel for what ideas have been kicked around.

Personally, I use the GPL version of the NoMachine X server on my file
server, and just remote-client in to it from my laptop.  Full KDE
session in Windows :)  Works fine over a 256kbit ADSL link too.

> Also, I tried converting a .nef file to BW and it
> played (and pretty much destroyed) the preview file
> and did not ask me for a "save as" option. Is that
> normal behavior?

Not that I'm aware of - whenever I manipulate my MRW files, Save As is
always a menu option.  Maybe I'll find a sacrificial mrw file and see
what happens when I click save instead.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Thursday 15 June 2006 07:40, Duncan Hill wrote:

> Turgut Durduran wrote:
> > Ideally, I want to be able to open an album, tag my
> > photos, play with them on my laptop and somehow sync
> > with those on desktop. Ofcourse, I am talking about
> > digikam purposes, I know how to sync the files. This
> > is probably not so straightforward.  So I am thinking,
> > I should be able to "merge" two databases of tags
> > somehow. Is it possible?
>
> At the moment, no.  It has been discussed several times on the list in
> the past few months - if you can find the archives, you should be able
> to get a feel for what ideas have been kicked around.

This is relevant of the database backend limitation used in digiKam (SQLite)

>
> Personally, I use the GPL version of the NoMachine X server on my file
> server, and just remote-client in to it from my laptop.  Full KDE
> session in Windows :)  Works fine over a 256kbit ADSL link too.
>
> > Also, I tried converting a .nef file to BW and it
> > played (and pretty much destroyed) the preview file
> > and did not ask me for a "save as" option. Is that
> > normal behavior?

You talking about JPEGlossless kipi plugin witch have a B&W converter. This
option is available from main interface, not image editor.

I have fixed this bug relevant of RAW file with this plugin. It will be
available into next kipi release.

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Arnd Baecker]

Hi,

On Wed, 14 Jun 2006, Turgut Durduran wrote:

[...]

> I use a desktop computer for storage of my photos.
> That contains all my collections. Then I have a laptop
> that contains a subset that I am working on --
> cropping, adjusting colors, sorting, tagging etc. The
> laptop does not have large enough of a hard-drive to
> contain the whole set.
>
> Ideally, I want to be able to open an album, tag my
> photos, play with them on my laptop and somehow sync
> with those on desktop. Ofcourse, I am talking about
> digikam purposes, I know how to sync the files. This
> is probably not so straightforward.  So I am thinking,
> I should be able to "merge" two databases of tags
> somehow. Is it possible?

[...]

This has been asked for several times, see the B.K.O
(KDE Bugs report system :
http://bugs.kde.org/buglist.cgi?product=digikam
)
For this particular case:
http://bugs.kde.org/show_bug.cgi?id=125474

This is very high on my wishlist ;-) -
I am already frightened about my next holiday,
which will surely be several 100 pictures and I really
would like to tag, label and rate them if
possible everyday (Sitting there with a huge bunch of
pictures after the holiday is no fun).

Would something like the following be possible:
- no digikam running on main computer
- copy all new images to the corresponding directories
- open digikam sqllite database and
- add every additional file registered in the digikam database of the
  laptop
  (also new tags etc. will be added during this procedure,
   but no tags or images deleted.)
(by now you will have realized that I don't have any idea
about sql, but still maybe an expert can do this,
or give some pointers?)
If the above was possible, it surely is not *the* solution,
but it could fulfill the needs of many(?) users.

BTW, when writing this above procedure, I had in
mind that on the laptop one already has a digikam database
which at least contains all the tags of the main computer.
Recently I wrote a small script which runs over all images
and scales them down.
(With this I managed to keep 1500 in just 270 MB, of course
in pretty poor quality, but almost good enough
for the laptop)
If someone is interested I can post the script.

Best, Arnd
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gerhard Kulzer]

On Thursday 15 June 2006 08:04, Arnd Baecker wrote:

> Hi,
>
> On Wed, 14 Jun 2006, Turgut Durduran wrote:
>
> [...]
>
> > I use a desktop computer for storage of my photos.
> > That contains all my collections. Then I have a laptop
> > that contains a subset that I am working on --
> > cropping, adjusting colors, sorting, tagging etc. The
> > laptop does not have large enough of a hard-drive to
> > contain the whole set.
> >
> > Ideally, I want to be able to open an album, tag my
> > photos, play with them on my laptop and somehow sync
> > with those on desktop. Ofcourse, I am talking about
> > digikam purposes, I know how to sync the files. This
> > is probably not so straightforward.  So I am thinking,
> > I should be able to "merge" two databases of tags
> > somehow. Is it possible?
>
> [...]
>
> This has been asked for several times, see the B.K.O
> (KDE Bugs report system :
> http://bugs.kde.org/buglist.cgi?product=digikam
> )
> For this particular case:
> http://bugs.kde.org/show_bug.cgi?id=125474
>
> This is very high on my wishlist ;-) -
> I am already frightened about my next holiday,
> which will surely be several 100 pictures and I really
> would like to tag, label and rate them if
> possible everyday (Sitting there with a huge bunch of
> pictures after the holiday is no fun).
>
> Would something like the following be possible:
> - no digikam running on main computer
> - copy all new images to the corresponding directories

Just a rough idea here:
With union-fs it would be possible to make the main folder of the photos
including the database file available per nfs to a laptop. Then you can
manipulate as much as you want on the laptop, the changed files being kept on
the laptop. Then you could at any time start to sync the files with the main
folder. This method would avoid copying all the images to the laptop. Off
course if you modify anything in the meantime in the main computer it would
be difficult to sync afterwards. This scheme works a bit like cvs or svn.
Gerhard

> - open digikam sqllite database and
> - add every additional file registered in the digikam database of the
>   laptop
>   (also new tags etc. will be added during this procedure,
>    but no tags or images deleted.)
> (by now you will have realized that I don't have any idea
> about sql, but still maybe an expert can do this,
> or give some pointers?)
> If the above was possible, it surely is not *the* solution,
> but it could fulfill the needs of many(?) users.
>
> BTW, when writing this above procedure, I had in
> mind that on the laptop one already has a digikam database
> which at least contains all the tags of the main computer.
> Recently I wrote a small script which runs over all images
> and scales them down.
> (With this I managed to keep 1500 in just 270 MB, of course
> in pretty poor quality, but almost good enough
> for the laptop)
> If someone is interested I can post the script.
>
> Best, Arnd
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Arnd Baecker]

On Thu, 15 Jun 2006, Gerhard Kulzer wrote:

[...]

> With union-fs it would be possible to make the main folder of the photos
> including the database file available per nfs to a laptop. Then you can
> manipulate as much as you want on the laptop, the changed files being kept on
> the laptop. Then you could at any time start to sync the files with the main
> folder. This method would avoid copying all the images to the laptop. Off
> course if you modify anything in the meantime in the main computer it would
> be difficult to sync afterwards. This scheme works a bit like cvs or svn.
> Gerhard

Interesting - does this also work if the laptop and
main computer are not connected (i.e. because they
are at different places) - somehow I have the impression
that this would not work.

Many thanks,

Arnd
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gerhard Kulzer]

On Thursday 15 June 2006 10:12, Arnd Baecker wrote:

> On Thu, 15 Jun 2006, Gerhard Kulzer wrote:
>
> [...]
>
> > With union-fs it would be possible to make the main folder of the photos
> > including the database file available per nfs to a laptop. Then you can
> > manipulate as much as you want on the laptop, the changed files being
> > kept on the laptop. Then you could at any time start to sync the files
> > with the main folder. This method would avoid copying all the images to
> > the laptop. Off course if you modify anything in the meantime in the main
> > computer it would be difficult to sync afterwards. This scheme works a
> > bit like cvs or svn. Gerhard
>
> Interesting - does this also work if the laptop and
> main computer are not connected (i.e. because they
> are at different places) - somehow I have the impression
> that this would not work.

To have the main folder visible on the laptop you need nfs connection.
Otherwise you would only see the modified files. So you need a connection.

> Many thanks,
>
> Arnd
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Arnd Baecker]

On Thu, 15 Jun 2006, Gerhard Kulzer wrote:

> On Thursday 15 June 2006 10:12, Arnd Baecker wrote:
> > On Thu, 15 Jun 2006, Gerhard Kulzer wrote:
> >
> > [...]
> >
> > > With union-fs it would be possible to make the main folder of the photos
> > > including the database file available per nfs to a laptop. Then you can
> > > manipulate as much as you want on the laptop, the changed files being
> > > kept on the laptop. Then you could at any time start to sync the files
> > > with the main folder. This method would avoid copying all the images to
> > > the laptop. Off course if you modify anything in the meantime in the main
> > > computer it would be difficult to sync afterwards. This scheme works a
> > > bit like cvs or svn. Gerhard
> >
> > Interesting - does this also work if the laptop and
> > main computer are not connected (i.e. because they
> > are at different places) - somehow I have the impression
> > that this would not work.
>
> To have the main folder visible on the laptop you need nfs connection.
> Otherwise you would only see the modified files. So you need a connection.

I feared so - hmm, that would mean a very long cable
to the holiday location ;-).

More seriously, if one already has a ethernet (or whatever)
connection to the main computer, I would just
log into the main computer via ssh -X and start digikam there.

Many thanks,

Arnd
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Duncan Hill-5]

On Thursday 15 June 2006 09:37, Arnd Baecker wrote:
> More seriously, if one already has a ethernet (or whatever)
> connection to the main computer, I would just
> log into the main computer via ssh -X and start digikam there.

Either the GPL or commercial version of NoMachine X is good for this (see my
earlier posting).  I'm using it right now over DSL, and the performance is
definitely acceptable (and downright fast considering it's DSL).
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Turgut Durduran]

Hello,

I apologize for not checking the archives/bug reports
carefully before asking the question. Thank you very
much for answering my question nevertheless.

The NFS or other mounting options are ofcourse there
but they defeat the purpose. Like someone was saying,
the idea is to be able to tag/edit my photos on my
laptop while on the "field" (e.g. on a trip).

I do not quiet follow what are the technical
limitations. I did not want to break what I already
did so I did not attempt this yet but similar to the
recipe that was suggested, I would imagine it should
be tweakable to allow a user to edit the database file
and keep references to real files *relative* to the
album path. So I can keep /home/myname/myalbums on
both computers but both won't have the same photos. I
could "unison" or sync the database files (may be not
in a  smart way but just copying the newer one over
the older one --- one way edits allowed) and have a
working digikam database. If a file is missing, it
would warn me and let me choose to ignore it.

The other idea of keeping an identical copy of the
whole album structure but with tiny images is
interesting too but don't you get into complications
when trying to keep track of what is new/what is
old/what is large/what is small?  I imagine this one
would be able to fool digikam into working state on
both computers?

finally, how hard is it to let advanced users to edit
the database manually to add new photos to certain
tags if the tag already exists and if not, create a
new tag with references to pictures?

thanks a lot again.

ulugeyik

PS: one final question, do competing systems like
f-spot have such abilities?
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Duncan Hill-5]

Turgut Durduran wrote:

> The NFS or other mounting options are ofcourse there
> but they defeat the purpose. Like someone was saying,
> the idea is to be able to tag/edit my photos on my
> laptop while on the "field" (e.g. on a trip).

NFS + SQLite has been shown to have a few problems, though only with
concurrency I think.

> I do not quiet follow what are the technical
> limitations. I did not want to break what I already
> did so I did not attempt this yet but similar to the
> recipe that was suggested, I would imagine it should
> be tweakable to allow a user to edit the database file
> and keep references to real files *relative* to the

The 'problem' is that digikam uses one single .db file to store all of
the information about the images and albums.

Because it's an sqlite driven db, it's not that easy right now to
maintain two separate copies, and then merge.  I'm sure I can think of
ways using perl to do it, but I haven't got that much of an itch to
scratch to do it right now :) (that and my time is way too limited right
now).

The only thing you cannot do in the field right now would be tagging.
You could edit to your heart's content on your laptop, and then just
merge in the files themselves into the album tree.  Digikam would detect
the new images and import them into the database.  No tags that way
though (though, with .9's ability to store tags in ITPC, there might be
a way to pull tags back out).

> finally, how hard is it to let advanced users to edit
> the database manually to add new photos to certain
> tags if the tag already exists and if not, create a
> new tag with references to pictures?

digikam.db is an sqlite database.  There are command line tools that
could do it.  There's at least one chap who wrote a PHP interface for
displaying based on the digikam db, so he probably has all the queries
you'd want, as does the source code to digikam.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Arnd Baecker]

On Thu, 15 Jun 2006, Turgut Durduran wrote:

> Hello,
>
> I apologize for not checking the archives/bug reports
> carefully before asking the question. Thank you very
> much for answering my question nevertheless.

Don't worry - I did not know about BKO before posting
here and also asked a registered complaint (aeh feature wish ;-).

I think this discussion is very helpful as it
highlights the possible problems of merging databases.
Somehow I get the feeling that this is doable though!

[...]

> The other idea of keeping an identical copy of the
> whole album structure but with tiny images is
> interesting too but don't you get into complications
> when trying to keep track of what is new/what is
> old/what is large/what is small?  I imagine this one
> would be able to fool digikam into working state on
> both computers?

Yes, but maybe if one does an "intelligent" syncing procedure it
might work. Let's try the following workflow:
(Notation: "main computer" has the full database, all figures
in large size. "laptop": the one which is taken into the field,
to this one new figures are being added)

(1) create a full copy of all Pictures on the main computer,
    with all images rescaled to some prescribed resolution.
(2) copy this (including the corresponding digikam3.db) onto
    the laptop in some directory.
    Working with digikam on those files is no problem (tested).

    *All these files are considered to be unchangeable, including
     their tags etc. - all changes will be ignored*
(3) In the field: add new pictures to new folders,
    tag them, rate them, and also add tags if necessary.
(4) Adding the changes back to the main computer:

    (a) First add all additional tags into the main digikam3.db
        database
    (b) For each *new* folder on the laptop: create that
        folder on the main computer and go over all
        files (and if needed recursively subfolders) and
        add them to the database, copy them into the corresponding
        folder.
        In addition, for each files the corresponding tags are added.

So with some organization on the users side, this might work ...

Some problems/points:
ad (1):
   * Presently I only implemented something like this for jpg
     - what about raw files?
     - what about tiff/png/...
   * If one has changed Pictures on the main machine,
     one does not want to re-create small-size copies of
     all images again. So it should be possible to
     create the small size copies only for newer files.
     (However, files could have become deleted,
     changed or moved - so this is not completely trivial...)
ad (4):
   (a) this should be possible with some sqlite magic, or?
   (b) presumably we need some "tag" to id association
       to make sure that deletion of tags does not screw up things
       here

I think all this should be doable with a python script
of less than 100 lines. Unfortunately, I know close to
nothing about sql, so I cannot go for a proof-of-concept
straight away.
(Are there any good quick references about sqlite,
in particular in connection with digikam?)

More importantly before coding is, whether the above approach
is robust enough - so any comments/criticism is wellcome!

Best,

Arnd


P.S.: I just installed http://sourceforge.net/projects/sqlitebrowser/
      and it seems very helpful to explore/understand the digikam
      database ...





_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gerhard Kulzer]

On Friday 16 June 2006 07:20, Duncan Hill wrote:
> > finally, how hard is it to let advanced users to edit
> > the database manually to add new photos to certain
> > tags if the tag already exists and if not, create a
> > new tag with references to pictures?
>
> digikam.db is an sqlite database.  There are command line tools that
> could do it.  There's at least one chap who wrote a PHP interface for
> displaying based on the digikam db, so he probably has all the queries
> you'd want, as does the source code to digikam.

knoda is an excellent GUI for sqlite (& postgres & MSaccess &Mysql &Paradox
&ODBC). A form could be used to facilitate editing digikam.db

Gerhard
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Turgut Durduran]

Hello,


Let's keep up with the brainstorming, may be I can get
to testing this out this week-end.


>
> Yes, but maybe if one does an "intelligent" syncing
> procedure it  might work.

I was thinking of "unison"
(http://www.cis.upenn.edu/~bcpierce/unison/) or some
script based on rsync. What you describe below is
doable if the users are careful.

>
>     *All these files are considered to be
> unchangeable, including
>      their tags etc. - all changes will be ignored*

We can perhaps achieve this by changing the
permissions on the files. Remove the "write
permission" (chmod a-w) to avoid accidental
overwrites.


> (4) Adding the changes back to the main computer:
>
>     (a) First add all additional tags into the main
> digikam3.db        database


If we make one further assumption that there will not
be any changes on the main computer while the "laptop
is in the field" , then we can just copy back the
digikam3.db , is that correct?



> Some problems/points:
> ad (1):
>    * Presently I only implemented something like
> this for jpg
>      - what about raw files?
>      - what about tiff/png/...

What is the problem with these? Resizing? I can write
a script to resize most formats. I am not entirely
sure but I think we can turn the raw files to "preview
only" (the little tiff file attached to raw files).

>    * If one has changed Pictures on the main
> machine,
>      one does not want to re-create small-size
> copies of
>      all images again. So it should be possible to
>      create the small size copies only for newer
> files.
>      (However, files could have become deleted,
>      changed or moved - so this is not completely
> trivial...)

This would not work with unison. But a custom
perl/shell script can take care of it.

> More importantly before coding is, whether the above
> approach
> is robust enough - so any comments/criticism is
> wellcome!


I am curious about that too :)
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Arnd Baecker]

On Fri, 16 Jun 2006, Turgut Durduran wrote:

> Hello,
>
> Let's keep up with the brainstorming, may be I can get
> to testing this out this week-end.

OK - I will stay tuned.

> > Yes, but maybe if one does an "intelligent" syncing
> > procedure it  might work.
>
> I was thinking of "unison"
> (http://www.cis.upenn.edu/~bcpierce/unison/) or some
> script based on rsync. What you describe below is
> doable if the users are careful.


Whatever the technical solution is, I think it is absolutely
necessary that this works without the two computers being
connected all the time.
of tags (which might still be ok, actually).



> >     *All these files are considered to be
> > unchangeable, including
> >      their tags etc. - all changes will be ignored*
>
> We can perhaps achieve this by changing the
> permissions on the files. Remove the "write
> permission" (chmod a-w) to avoid accidental
> overwrites.

That sounds good. However,
this won't prevent changes of tags/tags names
etc. in the digikam database
(which might not be transferred into the original
images on the main computer).

> > (4) Adding the changes back to the main computer:
> >
> >     (a) First add all additional tags into the main
> > digikam3.db        database
>
>
> If we make one further assumption that there will not
> be any changes on the main computer while the "laptop
> is in the field" , then we can just copy back the
> digikam3.db , is that correct?

yes - that should work, at
least I cannot see any problem at the moment
(maybe one could add some protection methods
which make sure that indeed no changes have been applied,
e.g. by an md5 checksum of the original database
which is compared before copying the new one over
the old one on the main computer)

> > Some problems/points:
> > ad (1):
> >    * Presently I only implemented something like
> > this for jpg
> >      - what about raw files?
> >      - what about tiff/png/...
>
> What is the problem with these? Resizing? I can write
> a script to resize most formats. I am not entirely
> sure but I think we can turn the raw files to "preview
> only" (the little tiff file attached to raw files).

No problem for tiff/png (more a reminder
to myself that I did not take care of them in my script yet)
For raw your suggestion sounds good: but the file
should have the same name as before the rescaling,
right? (otherwise we would become inconsistent
with the entries in the sqlite database)
Is this doable?

> >    * If one has changed Pictures on the main
> > machine,
> >      one does not want to re-create small-size
> > copies of
> >      all images again. So it should be possible to
> >      create the small size copies only for newer
> > files.
> >      (However, files could have become deleted,
> >      changed or moved - so this is not completely
> > trivial...)
>
> This would not work with unison. But a custom
> perl/shell script can take care of it.

Yes, that should be not too difficult.

Best, Arnd

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Heiner Lamprecht]

On Saturday 17 June 2006 02:52, Arnd Baecker wrote:

> On Fri, 16 Jun 2006, Turgut Durduran wrote:
> >
> > > Yes, but maybe if one does an "intelligent" syncing
> > > procedure it  might work.
> >
> > I was thinking of "unison"
> > (http://www.cis.upenn.edu/~bcpierce/unison/) or some
> > script based on rsync. What you describe below is
> > doable if the users are careful.
>
> Whatever the technical solution is, I think it is absolutely
> necessary that this works without the two computers being
> connected all the time.
> of tags (which might still be ok, actually).

Full ACK.

> > > (4) Adding the changes back to the main computer:
> > >
> > >     (a) First add all additional tags into the main
> > > digikam3.db        database
> >
> > If we make one further assumption that there will not
> > be any changes on the main computer while the "laptop
> > is in the field" , then we can just copy back the
> > digikam3.db , is that correct?
>
> yes - that should work, at
> least I cannot see any problem at the moment
> (maybe one could add some protection methods
> which make sure that indeed no changes have been applied,
> e.g. by an md5 checksum of the original database
> which is compared before copying the new one over
> the old one on the main computer)

I think, some export / import mechanism would be better than just
copying the whole database.  In my opinion, it's not necessary to
copy all images (even resized) to the laptop.  When I'm on a trip,
I don't need all photos of all previous trips.  It would be fine to
just have the tags available, and maybe a subset of the images, if
I'm in a region I have been before.

If you just copy the database, this will only work with sqlite.  But
maybe in the future, we have a different backend, that is
independent from the db.  Qt4 offers a lot in this field.

> > > Some problems/points:
> > > ad (1):
> > >    * Presently I only implemented something like
> > > this for jpg
> > >      - what about raw files?
> > >      - what about tiff/png/...
> >
> > What is the problem with these? Resizing? I can write
> > a script to resize most formats. I am not entirely
> > sure but I think we can turn the raw files to "preview
> > only" (the little tiff file attached to raw files).
>
> No problem for tiff/png (more a reminder
> to myself that I did not take care of them in my script yet)
> For raw your suggestion sounds good: but the file
> should have the same name as before the rescaling,
> right? (otherwise we would become inconsistent
> with the entries in the sqlite database)
> Is this doable?

If you think of an export and you're sure, that you will do no
changes to the images itself, than there is no need to stick to the
fileformat.  As far as I understand, you will use the resized
images on the laptop as a reminder.  Just to see, what you already
have.  But not for really working on the images.  For this, jpg or
png would be fully sufficient.


Cheers,


    Heiner

--
    heiner at heiner-lamprecht dot net    GnuPG - Key: 9859E373
  Fingerprint:  3770 7947 F917 94EF 8717 BADB 0139 7554 9859 E373
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Dotan Cohen]

What about a simple tag import/ export feature? A simple plugin that
saves an xml file like this (for instance):

<photo filename="/home/user/pics/beer.jpg">
    <tag>People*Ester<tag>
    <tag>People*Studies*Eli<tag>
    <tag>People*Studies*Anna<tag>
    <tag>Place*Haifa<tag>
</photo>

<photo filename="/home/user/pics/music.jpg">
    <tag>People*Ester<tag>
    <tag>People*Dotan<tag>
    <tag>People*Army*Jacob<tag>
    <tag>Place*Jerusalem<tag>
</photo>

And then these could be imported again. If it's kipi, then any other
KDE app could import them as well, making migration easy.

Dotan Cohen
http://what-is-what.com
234
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Dotan Cohen]

Forgot to close my tags. This is what i meant:

<photo filename="/home/user/pics/beer.jpg">
   <tag>People*Ester</tag>
   <tag>People*Studies*Eli</tag>
   <tag>People*Studies*Anna</tag>
   <tag>Place*Haifa</tag>
</photo>

<photo filename="/home/user/pics/music.jpg">
   <tag>People*Ester</tag>
   <tag>People*Dotan</tag>
   <tag>People*Army*Jacob</tag>
   <tag>Place*Jerusalem</tag>
</photo>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Heiner Lamprecht]

On Saturday 17 June 2006 14:30, Dotan Cohen wrote:
> Forgot to close my tags. This is what i meant:
>
> <photo filename="/home/user/pics/beer.jpg">

I would suggest to put the xml file in the same directory as the
images are, and than use only the name, without any path.  That
make the import a lot easier.


    Heiner

--
    heiner at heiner-lamprecht dot net    GnuPG - Key: 9859E373
  Fingerprint:  3770 7947 F917 94EF 8717 BADB 0139 7554 9859 E373
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Colin Guthrie-6]

Dotan Cohen wrote:
> And then these could be imported again. If it's kipi, then any other
> KDE app could import them as well, making migration easy.

Good idea.

I think this will require a change to the Kipi API to allow more direct
interfacing with host applications with respect to Tags/Categories/etc.

Kipi is currently about to make a new release and once that is done
there is going to be some consultation to determin how we can break the API!

I for one want to add a preference storage mechanism for images and
albums through KIPI, such that a plugin can store flags and such for
albums and images. These would be internal, non-user visiable values.

So if this kind of thing is to be supported, then it makes sense to
re-evaluate the attributes code currently in the KIPI api (which was
added to work with Gwenview categories IIRC) to work more generically
with tags/categories etc.

Not looked too hard at the code, so I could be mis-informed here - be
warned ;)

Col.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users