|
No, the purpose of the plugin system is to modularize calibre code to help promote robustness and ease of development/maintenance. In addition, a secondary goal is to allow people to customize aspects of calibre's behavior by writing their own plugins. The existence of a plugin system should not be construed to mean that I will happily implement every feature request that comes across my way. And I should note that the user interface of calibre is not pluginized. Plugins are typically for backend logic.
As far as user interfaces go, my philosophy is to provide as flexible an interface as possible, so users (with a little thought) can customize it to do what they need. At the same time I try to keep the interface as consistent and easy to use as possible, for the vast majority of people that want to use calibre do a few simple common things.
The key point is with a little thought. There are always going to be users who as you say, want what they want, and aren't willing to learn/experiment a little to see how they can use calibre's UI to accomplish what they want.
Typically these are users who are used to a certain paradigm and are unwilling to move off it. That's fine, it's their call, but I'm not going to compromise calibre's UI integrity to cater to them.
@rchiav: I'm not implying you are such a person. This post really has nothing to do with any individuals at all.
|