Quote:
Originally Posted by kiwidude
It sounds like you intend to look into it anyways but I would +1 something being there for it. I confess to not having read your post in detail and you obviously know the issues better than anyone. From my "end user" perspective, given that I have already got the ability to specify what Kindle collections are to be preserved, I think anything outside of that is fair game to be blown away by your plugin. My fear is that if you bend over too far to try to be flexible for every situation it all just becomes too complex to use and know why collections appear/disappear.
Again this is based on a simplistic ignorance view - but surely if a user specifies what collections they want to keep (as you have already got the ability to do), it is perfectly reasonable to assume that anything else can be overwritten/removed?
|
I agree, its a good suggestion.
It wasn't there originally simply because, as you can tell with the number of versions, I've been building up the code as people have commented and as I've gotten to be more familiar with the Kindle and Calibre (part of the fun of writing this as I'm sure you're aware
). And the original code only read the files on the Kindle so wouldn't have known about the rest of the collections until I learned how to access Calibre's library. This should actually slot in quite well into the code, but I'm finding more and more of course that even with the code split into classes and separate areas, if you change one thing it can have unexpected consequences somewhere else
