Calibre Notifications

[DNSB]

Originally Posted by thiago.eec

As far as I know, calibre won't offer you a plugin that is incompatible. Are you sure about this?

Otherwise it would make no sense the 'minimum calibre version' variable in the python code. This is suposed to be read by calibre.

If I remember correctly, even if you try to manually install the zip file, calibre will tell you that it doesn't work with your installed version.

Perhaps Jon is wanting a system where plugins would have a maximum calibre version? Though since that would require testing every plugin with every new calibre release to update the version, it's never going to fly. An example could be the KoboTouchExtended plugin and calibre 8.

[thiago.eec]

Originally Posted by DNSB

Perhaps Jon is wanting a system where plugins would have a maximum calibre version? Though since that would require testing every plugin with every new calibre release to update the version, it's never going to fly. An example could be the KoboTouchExtended plugin and calibre 8.

I see. Indeed this is the plugin's problem, to be solved by the developer. Kovid can't do anything about it. I always test my plugins against relevant previews and specially against new major releases (like calibre 9). When the beta ends, they are already fixed, so the user won't notice a thing.

[Comfy.n]

FWIW:

Tested on 7.26: calibre lists plugins with min version higher but disables the install button (prevents install):



there is also a tooltip:

[thiago.eec]

Originally Posted by Comfy.n

FWIW:

Tested on 7.26: calibre lists plugins with min version higher but disables the install button (prevents install):

Attachment 220911

there is also a tooltip:

Attachment 220912

That's right. And you won't get a notification about the plugin's new version, when the minimum required version criteria is not met.

[Comfy.n]

Yes, I think what Jon wants is not having them listed (showing) at all. "Plugin system" is quite vague.

Regarding Max Version, some people have suggested this in the past, including me at the TTS to MP3 plugin thread. It was not feasible for some reason.

[JSWolf]

Originally Posted by thiago.eec

As far as I know, calibre won't offer you a plugin that is incompatible. Are you sure about this?

Otherwise it would make no sense the 'minimum calibre version' variable in the python code. This is suposed to be read by calibre.

If I remember correctly, even if you try to manually install the zip file, calibre will tell you that it doesn't work with your installed version.

I am sure. This is from calibre 1.48 portable. It's showing new plugins that are not compatible. Have have the plugins sorted by date, latest first. At least it's showing the minimum calibre version. But that also means that if the plugin no longer works with a newer calibre, you won't know it won't work.

[Comfy.n]

I ran 1.48 the other day, while testing Current Paths plugin.

It's nice to see how far calibre evolved since then.

(I chose to restrict backwards compatibility to 3.48, though)

[JSWolf]

Originally Posted by Comfy.n

I ran 1.48 the other day, while testing Current Paths plugin.

It's nice to see how far calibre evolved since then.

(I chose to restrict backwards compatibility to 3.48, though)

I used calibre back before it was calibre. Back then, it was LibPRS500 for the Sony Reader. It was created so you didn't have to use the Sony Software and to be able to convert eBooks in other formats to LRF,

[BetterRed]

Originally Posted by un_pogaz

I can see the use, but I'm not sure that it will be good to be natively in Calibre, better a plugin. I don't found that it will fit to Calibre. Or maybe make this popup system off by default.

Read my response to the same suggestion from PeterT

Originally Posted by BetterRed

If you mean a plugin hosted here, how many of the 2.8m active users would know it existed, and how many of them would install it.

IMO be lucky if it was .1%, probably closer to .01%.

BR

And the .01% (~300) who did install it, are not the people the suggestion is targeting.

The users who would install an optional plugin, are the users we see here, who likely keep one eye on the commit list at github, and the other on the bug reports and enhancement requests at launchpad etc. They don't need a notification thingamabob -- they already know what's happening in the calibre space.

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

[BetterRed]

Originally Posted by Comfy.n

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

And how many downloads of CCR?



About 0.01% of the active user base.

The view count here is BS, that's how many web crawling AI bots have nicked off with your code

BS

[Comfy.n]

Yeah i don't mind the counts in that screen. One CCR version, I believe 2.0.11? had 4.000 downloads. (according to MR count)

I dont bother posting dates in the changelog, sigh. Too much detail, but sometimes I miss that.

[BetterRed]

OT - what's needed is a cull of the defunct PIs that no one actually uses (some people install everything… just because they can) -- example, how many people actually use Entities Manager or Recoll Full Text Search.

The issue EM attempted (and largely failed) to address has been covered by enhancements to the core - Link and Notes for all Category columns and calibre:// URLs etc. And calibre's FTS does for Linux, MacOS and Windows what the RFTS plugin does/did for Linux only.

The only way to find out how many people actually use a plugin is to release a version with a bug, the devil is tempting me to do that with EM… afaik I am the only person who tried it in anger

BR

[Comfy.n]

Originally Posted by BetterRed

The only way to find out how many people actually use a plugin is to release a version with a bug, the devil is tempting me to do that with EM… afaik I am the only person who tried it in anger
BR

Or perhaps include AI integration in it.

[JSWolf]

Originally Posted by Comfy.n

Or perhaps include AI integration in it.

Or just update the version number and say there is AI in it.

[Comfy.n]

Originally Posted by JSWolf

Or just update the version number and say there is AI in it.

correct , lol