|
Well, first of all it's not about what I personally want, really. I've just suggested a couple of scenarios to illustrate the point that the app could be made a bit more predictable in certain aspects.
Where did I say that I don't like the way the app advertises its handling capabilities to the OS? I only said I'd prefer to be informed what the app is going to do, and have a choice to agree to that or not. One of those "do you want the app to register file associations" dialogs with a list to choose from. And it'd be nice to have that applied only once you've pressed "Finish": it doesn't even matter now if you cancel of finish the welcome wizard — you've run the app and here you go.
So, the polite behaviour would be to display the dialog, register file associations once the welcome wizard was successfully run and not do anything if it was cancelled, given that you can always run it again.
I've already figured out a somewhat cheesy but functional way to keep Calibre from doing that:
Create an empty AppData\Roaming\calibre directory in your profile and put a dynamic.pickle.json file there with only the following before running the app for the first time:
{
"welcome_wizard_device": "cybook_odyssey (or whatever you have)",
"welcome_wizard_was_run": true
}
No associations added, just the way I want it.
That's essentially what I'd like to see if I cancel the welcome wizard.
As for the portable mode, I just reported something that's not exactly the way one would expect a portable app to behave, and I'm somewhat perplexed by the answer. Let's say you want to run the ebook-viewer component directly in the portable mode. And all of a sudden the app is not so portable, writes its configuration files to your home directory and writes a bunch of settings to the registry. All of that with no warning whatsoever. It's not a question of what I or anyone else has to use, it's a question of how an app should behave — in a polite and predictable way.
|