Quote:
Originally Posted by kiwidude
My hope was that we would develop it as a plugin initially so that we could get the kinks out without interfering with Calibre releases. And that one day it might get included for distribution with Calibre if Kovid deemed it useful. Confirmation from Kovid that he would be interested in including it when ready is great. We just need to produce something worthwhile to be included of course...
|
I think Kovid was pretty clear, he agrees it will be useful, so it should eventually be added to the trunk. I have no objection to development as a plugin (and that's what Kovid agrees is a good approach), but once the basic structure is settled in the plugin it should move to the trunk code. Features like this don't interfere with Calibre releases, as long as they don't blow up other parts of the code. Putting them in the trunk draws lots of users with their valuable feedback and gives everyone a tool, even when they aren't comfortable installing plugins.
I think the main worry is that once it's in the trunk, we don't want to fundamentally change the appearance or move too many options around or change defaults. Users get accustomed to new features very quickly. In a plugin , we can play with drastically different approaches. In the trunk, we need to worry about "The Calibre Experience" - something that is already hard enough to dance, without changing the dance floor underneath everyone
