![]() Drive letter assignments can change for removable drives. It is the value of the USERPROFILE environment variable with \Pictures appended. The first time the program is run, it will start with a configuration assistant known as “The First Run Dialog.” On the “Configure where you keep your images” screen, the assistant will propose a location such as H:\digiKam\Pictures. :: An alternative is to set USERPROFILE to a folder on the same drive, :: The program uses this as the parent for the AppData\Local folder. :: This will set USERPROFILE to the digiKam folder. Later in the web page is the section “Collections Settings.” There is a screenshot of “Root Album Folders.” One of the options is “Collections on Removable Media.” It may be wise to first focus on the simpler option of using SQLite in implementing a portable version of digiKam. MySQL and MariaDB are also options for digiKam storage. It is out of the range of most current thumb drives, but not of larger removable drives. webfork’s posting indicated that the storage requirements for digiKam are hefty. It says, “For performance reasons, it’s also recommended not to use removable media.” I think that performance should be acceptable in most cases when using Thunderbolt or fast USB drives. In the “The SQLite Database” section is a screenshot of “Database Configuration.” The user can set the location of three databases. Rem A line should be added to run digikam.exeĭigiKam Configuration > Database Settings Rem The md command is not needed after the AppData_Local folder is created. Rem An alternative is to set it to a folder on the same drive, Rem This will set LOCALAPPDATA to a subfolder within digiKam. ![]() Rem The md command is not needed after digiKam is installed. Rem The batch modifier for d0 is on the next line. Probably PhotoScape is the best program to play in both camps.Ĭode: Select all Rem Batch file with extra commands to show portability. Again, this is a feature monster so at least this is one program who's size is comiserate to the features, but it's probably unwise to have it running in the background all the time.Ĭomparison to other programs here on the site: Like PhotoDemon, the program is primarily targeted to photographers and not for standard image addendums for screenshots, such as arrows, text, boxes, etc. Resource: Still huge the download is 275 megs, install is 1.3 gigs, RAM was 313 megs on my Win10圆4 system. ![]() Also writes to \AppData\Local\kxmlgui5\digikam\ I was also unable to determine how to get the photos database to work within the local folder. Status: Not portable, writes to C:\Users\USERNAME\AppData\Local\digikamrc. Steps: download and unzip, overwriting when prompted, launch digikam.exe Also, this program did *finally* add a functionality I've been looking for: you can select multiple thumbnails and modify just those items for size, color, conversion, filters, etc. I retested recently and the crashing discussed previously seems to have mostly been worked out. Select the MySQL item from the Type drop-down list.As Stephen Leibowitz suggested earlier in the thread, the program did see some really positive updates. If you’ve just installed digiKam, and you haven’t yet added any collection to it, choose Settings -> Configure digiKam, and switch to the Database section. There are two ways to switch digiKam from SQLite to MySQL. And before you proceed, note the database connection information such as MySQL server address, user name, and password - you’ll need it when configuring MySQL settings in digiKam. You also have to create two MySQL databases: one for storing photo metadata (e.g., digikam) and the other for storing thumbnails (e.g., thumbnails-digikam). Obviously, to use digiKam with MySQL, you need a MySQL server. You can also use MySQL tools to back up and analyze digiKam’s data. This way, you can use multiple digiKam installations (e.g., on your notebook and desktop machine) to access and manage your photo collections. Of course, you might wonder why you’d want to switch to MySQL when SQLite already does a good job of managing the data? Using MySQL as digiKam’s database back-end allows you to store the data on a remote server. But the photo management application also provides support for the popular MySQL database engine, and it comes with a database migration tool that can help you to move your data from SQLite to MySQL. Transcribed from Dmitri Popov's blog, 15 October 2010īy default, digiKam uses SQLite as its back-end for storing important metadata and thumbnails.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |