Quote:
Originally Posted by chaley
Calibre already insists that destination folder for a library be empty. How does adding a subfolder make it better?
|
Oh, I didn't realize this. I see it in choose_library.py now. I'm glad this safety mechanism is there.
OK, so assume that I didn't know about the empty subfolder requirement. I thought that calibre would still let you pick any folder at all. This still requires the user to create an empty folder using their operating system tools (shell, Windows explorer, Mac Finder, whatever). I think it would be a nice touch if calibre took care of the folder creation for the user. Let it create that empty folder based on a library name supplied by the user.
Here's a mockup of how I would change the Choose Library dialog:
The user selects where they want their library to be stored and enters a name for the library. Calibre creates an empty folder with the library name at the location and stores its files there. Come to think of it, why is the "new location" field blank? It would help to populate that with either (1) the basename of the currently open library or (2) the value of $HOME.
If it helps to know where I am coming from, I'm thinking of how I can make a program like calibre easier for my mom to use by adding some polish. She's not very computer literate, and come to think of it neither are many of the computer users that I deal with day-to-day.