cdigi
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
Cdigi is a command line and service menu tool for extracting data from Digikam sqlite database and produce nice HTML galleries.
15 years ago
30 Nov 2005
Migrating to 0.8.x - at the moment only operations on albums works (-a)
- added: numbering of converted photos (1/30)
- fixed: make everything in UTF-8
- fixed: change default program to sqlite3
- fixed: change name of database to database3.db
14 Apr 2005 * Release 1.5: - --report option; bugfixes
19 Aug 2004 * Release 1.3: - it is possible to have multiple albums/tag queries in one call: cdigi -a album1 album2 ... cdigi -qt qtag1 qtag2 ... 17 Aug 2004 - fixed: return individual pages to XHTML 1.0 Strict 14 Aug 2004 * Release 1.2: - fixed: Digikam doesn't put all images in database. Use find-sed combo for albums chosing - other options shuld be covered by database - add accesskeys for individual pages (p - previous, n - next, i - index). - add accesskeys for index page (both work great in Konqueror - much kudos to bj :). Limit of access keys is 24+10 13 Aug 2004 * Release 1.1: - move index page back into XHTML 1.0 Strict - remove unnecessary double quotes - remove offending quotes from alt attribute values 12 Aug 2004 - add error codes for exits - remove image extension (last .xxx) from names of html files - shell code cleaning: removing unncesessary sed calls, simplifying tests (conclusions after reading first chapters of ABSG) 11 Aug 2004 - shell code cleaning
15 years ago
30 Nov 2005
Migrating to 0.8.x - at the moment only operations on albums works (-a)
- added: numbering of converted photos (1/30)
- fixed: make everything in UTF-8
- fixed: change default program to sqlite3
- fixed: change name of database to database3.db
14 Apr 2005 * Release 1.5: - --report option; bugfixes
19 Aug 2004 * Release 1.3: - it is possible to have multiple albums/tag queries in one call: cdigi -a album1 album2 ... cdigi -qt qtag1 qtag2 ... 17 Aug 2004 - fixed: return individual pages to XHTML 1.0 Strict 14 Aug 2004 * Release 1.2: - fixed: Digikam doesn't put all images in database. Use find-sed combo for albums chosing - other options shuld be covered by database - add accesskeys for individual pages (p - previous, n - next, i - index). - add accesskeys for index page (both work great in Konqueror - much kudos to bj :). Limit of access keys is 24+10 13 Aug 2004 * Release 1.1: - move index page back into XHTML 1.0 Strict - remove unnecessary double quotes - remove offending quotes from alt attribute values 12 Aug 2004 - add error codes for exits - remove image extension (last .xxx) from names of html files - shell code cleaning: removing unncesessary sed calls, simplifying tests (conclusions after reading first chapters of ABSG) 11 Aug 2004 - shell code cleaning
Support-Box
cdigi is part of Apps, Games and Add-ons, which is supported by the following people:
More Graphic Apps from emdot:
Other Graphic Apps:
lhands
15 years ago
If you have a non-standard DIGIDIR in the .cdigirc (I use ~/Pictures/) then $DIGIDB will still point to ~/Digikam/digikam.db. This seems to work better,
--- cdigi 2005-11-30 20:58:51.000000000 +0000
+++ /usr/bin/cdigi 2006-01-02 18:08:44.000000000 +0000
@@ -20,9 +20,6 @@
# Defaults {{{
# Digikam top dir
DIGIDIR=$HOME/Digikam
-# It is possible, in future versions of Digikam, database will be stored in different
-# place
-DIGIDB=$DIGIDIR/digikam3.db
# Size of images (in fact it can be anything allowed in convert -resize)
RESIZE="640>"
@@ -94,6 +91,12 @@
# Find and read $HOME/.cdigirc {{{
[ -r $HOME/.cdigirc ] && source $HOME/.cdigirc
+if [ "$DIGIDB" = "" ]; then
+ # It is possible, in future versions of Digikam, database will be stored in different
+ # place
+ DIGIDB=$DIGIDIR/digikam3.db
+ echo $DIGIDB
+fi
# }}}
# Auxiliary functions: {{{
Also this doesn't work with anything other than the latest version of digikam, unless sqlite3 is replaced with sqlite (seems to work with digikam 0.73) - this would be nice as a configuration option?
Report
matt2002
16 years ago
How about adding one or two lines at the beginning of the description (which currently does *not* describe the app, but its requirements and technical details only)
yes, I know, I could follow the link to your homepage, and I will, but still, a few words telling what it is for should be on this page.
Regards,
Matt
Report
matt2002
16 years ago
Regards,
Matt
Report