Plugin Developers, a request

[Rellwood]

Is it possible for you to keep available your plugins versions that were last updated before moving to Python 3 or the most recent Calibre updates that will run on Calibre 4.7?

I understand you are all updating but I still use 4.7 as well as the most recent version (I keep 4.7 in 32bit and the latest in 64bit). I want to make sure I have the most recent versions that will work with the older Calibre to put aside when I switch between the two. If I keep using plugin update I lose those older versions and I don't know if the newest updates will work with the older Calibre.

I hope that makes sense.

Also, the reason I keep the older version is because a certain plugins' updated version doesn't run on the older Calibre, and the newest update (of the plugin) has some problems with my system causing it to run at exceedingly slow speeds. It seems to only happen on my computer and it's not a problem for others. I tried bringing it up, but nothing has been changed. So I keep the older Calibre just to run that plugin.

[davidfor]

Originally Posted by Rellwood

Also, the reason I keep the older version is because a certain plugins' updated version doesn't run on the older Calibre, and the newest update (of the plugin) has some problems with my system causing it to run at exceedingly slow speeds. It seems to only happen on my computer and it's not a problem for others. I tried bringing it up, but nothing has been changed. So I keep the older Calibre just to run that plugin.

And nothing will be done until you actually show me what and where the problem is. As you have never bothered to actually state what function of the plugin is slow or what part of that function is the issue, I have never been able to even think about what to look at. Hell, all you really need to do is run calibe in debug mode with each version of the plugin, run the function an post the logs.

[DiapDealer]

All versions of my plugins are preserved on github. But having said that, they all have been updated to work with the versions of calibre they've always worked with AND the latest python3 versions of Calibre. One size fits all. I've been writing polyglot python for several years now, so it's second nature for me to keep things compatible with both py2/py3 as well as pyqt4/pyqt5. Brand new plugins probably won't support the old, but as long as it's trivial for me to maintain support for the older versions of calibre in my existing plugins, I'll do so.

[theducks]

@rellwood
You can always forgo the automatic installer (beta testers do this)

Download from the selected Plugins forum thread. ( I add the release # to the end of the file name in my archive the PI folder ) , That way I have previous versions (I do delete those that have Known issues, so I don't ever try those again)

You do it the old way (before Get Plugins era)
Preferences:Plugins: Load from File (a button, lower right) If downgrading a previous, find and select from the Installed List: Click the Remove Plugin (button)
I prefer to restart Calibre, before installing a lower version, just to have a clean slate.

[Rellwood]

Originally Posted by davidfor

And nothing will be done until you actually show me what and where the problem is. As you have never bothered to actually state what function of the plugin is slow or what part of that function is the issue, I have never been able to even think about what to look at. Hell, all you really need to do is run calibe in debug mode with each version of the plugin, run the function an post the logs.

Hey there,
I sent you a PM that had gone to Kiwidude thinking that he was running the plugin. I am sorry. The message contains all the info you requested. Bug reports don't show a problem. The long and the short of it is that for some reason the status bar does not move quickly. It runs at about a book(page) a second. No joke. Since that PM I haven't really tried to run tests again trying to week out the variables, however I will today. I apologize for the dropped/mixed signals. I will be happy to provide you with any/all data you need to help me here.

Again, I am sorry if I haven't been clear in the past.

[Rellwood]

Originally Posted by theducks

@rellwood
You can always forgo the automatic installer (beta testers do this)

Download from the selected Plugins forum thread. ( I add the release # to the end of the file name in my archive the PI folder ) , That way I have previous versions (I do delete those that have Known issues, so I don't ever try those again)

You do it the old way (before Get Plugins era)
Preferences:Plugins: Load from File (a button, lower right) If downgrading a previous, find and select from the Installed List: Click the Remove Plugin (button)
I prefer to restart Calibre, before installing a lower version, just to have a clean slate.

Thanks! I have been doing that loading plugin from file for some of the plugins that I have to swap out before upgrading/downgrading.
I just wanted to be sure that the plugins will be available in the future.

[Rellwood]

Originally Posted by DiapDealer

All versions of my plugins are preserved on github. But having said that, they all have been updated to work with the versions of calibre they've always worked with AND the latest python3 versions of Calibre. One size fits all. I've been writing polyglot python for several years now, so it's second nature for me to keep things compatible with both py2/py3 as well as pyqt4/pyqt5. Brand new plugins probably won't support the old, but as long as it's trivial for me to maintain support for the older versions of calibre in my existing plugins, I'll do so.

Sweet! I noticed that a plugin or two mentioned in the update plugin box that the plugin required the updated Calibres

I love Github! I find so many great little .exes there.