Calibre Notifications

[BetterRed]

Those who install something just because they can, are the same 'those' who wouldn't read a change log for love or money.

Better to inject a real bug onto it… if no one complains after 60 days, remove it from the PI Index… or deprecate it, if you can remember how.

BR

[kovidgoyal]

I am definitely not going to spam all calibre users with preview/beta release notifications. That would just be hostile. If every software I used started spamming me with these I would be very annoyed. As it is, I still get complaints from people that think calibre updates too frequently. I could see having an option to turn on such notifications, but then that would defeat the purpose which is to make those more widely noted, since most people would never see let alone turn on such an option.

As for new plugin notifications, again I am not comfortable spamming every calibre user with every new plugin. 99.99% of these notifications would just be noise.

[un_pogaz]

Originally Posted by BetterRed

And I knowingly, wittingly, deliberately avoided the use of 'popup', 'toast', etc, because they are intrusive.

What I suggested is a non-removable button in the status bar that 'glows' when there's something new. If I were implementing my suggestion, I'd probably change the appearance of a button that already exists, this one ==>> "calibre 9.2.1 created by Kovid Goyal...", I'd bold it or change its colour if there are unread messages.

BR

Oh, inded, better. But personally, I prefer to use the same one used to show update notifications Calibre/Plugin at the bottom right, but with the text "X new plugin"


Anyway. As Kovid says, it would be a potentially unwanted noise.

A compromise would be to display this notification only once when you open Calibre and it detects a new plugin in the list, and simply restarting Calibre will automatically hide it. Not even the date, but just a raw list of the plugin name...
But that would require keeping this list somewhere, adding it to the resource/config files, and updating it with each release... That's a lot of effort for not much gain. Better to use a plugin.

[un_pogaz]

Originally Posted by Comfy.n

it's for CCR: https://www.mobileread.com/forums/sh...d.php?t=369555

Hmm, it could be better to make it a standalone plugin, rather to integrat it into a other plugin that I would never use. And with a little ingenuity, it would be possible to use the notification area at the bottom right for show info of newest plugin.

A plugin names "Plugins Update News"

[Comfy.n]

Welp...That can be arranged but if it only serves to display this dialog, then one might as well just click the plugin updater built-in button and sort it by released date.

[JSWolf]

How many plugin that say they work from version X to version Y work with newer versions of calibre? Those plugins should be updated to show the last version it works with.

On Windows 7, calibre 3.48 is the last version that's allowed to be run. I cannot say on MacOS. So the problem is that some plugins are not needed on calibre 9 but they may be useful with 3.48. And they may no longer work on newer versions of calibre, but they work perfectly well with 3.48. So what I think needs to be done is to update (as needed) all plugins to say what early version they work with to the latest version they work with. And calibre should be updated to notify anyone using said plugin(s) that the plugin may or may not work.

One thing I would not do is use specific version numbers such a 9.2.1 because if you do that then hen 9.3 comes out, everyone would get notified. Use just version 9 and that would mean no notifications for any version 9..

[un_pogaz]

@JSWolf I can't remember where it was said, but the answer is No. Hard No.

First there are all the problems that would that to having to update all the plugins to add this max version, and that to satisfy a very marginal case.

Not to mention the fact that if the plugins have a version, you would have to update that version every time a new version of Calibre comes out, so push a new updated version of the plugin at the same time (oh dear).

And, cherry on the top, the version you target like the one of you example would not support such a feature, so all that work for nothing.

Especialy that breaking change for Calibre version above are trully rare, extremely rare and marginal.

Is a very quick reply with half cooked argues (so don't quote on me), and if someone have a link to a thread that already discussed, thanks, but be sure is a great No No.

[DNSB]

Perhaps it would be best if Jon who seems rather enthused about having this update feature is tasked with creating & debugging the feature and working out how push an update for all older calibre versions to support the suggested update display in all his copious and unlimited spare time! With perhaps a subtask of adding the maximum calibre version to all registered plugins to support the update feature.

Any programming task is trivial to the person who does not have to implement it.

[BetterRed]

Originally Posted by kovidgoyal

I am definitely not going to spam all calibre users with preview/beta release notifications. That would just be hostile. If every software I used started spamming me with these I would be very annoyed. As it is, I still get complaints from people that think calibre updates too frequently. I could see having an option to turn on such notifications, but then that would defeat the purpose which is to make those more widely noted, since most people would never see let alone turn on such an option.

As for new plugin notifications, again I am not comfortable spamming every calibre user with every new plugin. 99.99% of these notifications would just be noise.

Thanks Kovid, I understand.

Messages regarding new plugins was icing on the cake, ~220 messages over the space of almost 15 years doesn't seem excessive to me, I get that many in a week from the Daily Telegraph and Quillette - no matter how often I unsubscribe