KimDaBa’s HTML export explained
Automated disclaimer: This post was written more than 15 years ago and I may not have looked at it since.
Older posts may not align with who I am today and how I would think or write, and may have been written in reaction to a cultural context that no longer applies. Some of my high school or college posts are just embarrassing. However, I have left them public because I believe in keeping old web pages alive—and it's interesting to see how I've changed.
Update: KimDaBa is now known as KPhotoAlbum.
- Problem
KimDaBa doesn't always have the clearest interfaceKimDaBa, despite being a wonderful program, still has a few interface issues left to work on. Notably, the gallery creation tool, "HTML Export", requires quite a bit of trial-and-error before it can be used successfully. I could not find any useful documentation on the "Destination" tab's fields, so I write it here today.- Solution
-
The philosophy behind the KimDaBa HTML Export dialog is that you will have a series of galleries in the same folder. The "Base URL" is the publicly accessible base directory, while the "Base directory" is the location you want to store the actual files to. "URL for final destination" is the most confusing of all; it refers to the address of the main page of the gallery. I use index.html, but you can use an absolute address instead, if you want. "Output directory" is appended to the "Base URL" and "Base directory" to form the full directory path.
Enough with the philosophy, here's an example. I want to publish a set of photos, accessible at http://brainonfire.net/gallery/party/index.html. Let's say brainonfire.net runs off of my local machine, to make this easier. The server is located at /var/www, and has a directory called gallery. Here are the proper field values:
- Base directory
- file:///var/www/gallery
- Base URL
- http://brainonfire.net/gallery
- URL for final destination
- index.html
- Output directory
- party
You can publish to an ftp server as well, or over various other protocols. I won't go into that here.
No comments yet.
Self-service commenting is not yet reimplemented after the Wordpress migration, sorry! For now, you can respond by email; please indicate whether you're OK with having your response posted publicly (and if so, under what name).