Calibre eReader/Marvin Sync

[LUEBECKER]

Is there a way to make the Calibre eReader module in Windows 10 sync with my reading position in Marvin from my iPhone or iPad? If there is it would make things perfect. A connection through Dropbox the way Marvin works would be ideal.

[kovidgoyal]

No, there isn't. Although in calibre 3.0 you can just read books using your browser via the calibre Content server and that implements last read position syncing across all devices you read on automatically.

However, for the syncing to work, you have to leave the Content server running.

[LUEBECKER]

Kovid,
Thanks for the response. Where do I get Calibre 3.0. I try to stay up to date, but I have version 2.83.0 and don't see a download for 3.0 on your web site.

[PeterT]

3.0 is still in development and there is no download link

[kovidgoyal]

I'm hoping calibre 3.0 will be released within the next month. Certainly there will be a beta anouncement for it in May.

[LUEBECKER]

Thanks

[LUEBECKER]

Originally Posted by kovidgoyal

I'm hoping calibre 3.0 will be released within the next month. Certainly there will be a beta anouncement for it in May.

Thanks! I love calibre and look forward to the beta of 3.0

[webmaven]

Originally Posted by kovidgoyal

I'm hoping calibre 3.0 will be released within the next month. Certainly there will be a beta anouncement for it in May.

Woot!

I've been checking out calibre-debug --new-server, and it is pretty slick.

Would feedback (bug reports, feature requests) in the dev forum be appropriate at this point, or should I wait for the beta?

[kovidgoyal]

Wait for the beta -- I basically have one thing left to do

I'm anticipating a beta period of *at least* a couple of weeks, so there will be plenty of time to give feedback.

[webmaven]

Originally Posted by kovidgoyal

Wait for the beta -- I basically have one thing left to do

I'm anticipating a beta period of *at least* a couple of weeks, so there will be plenty of time to give feedback.

Two weeks seems too short to gather significant feedback from users, unless you're using "Beta" to mean "Release Candidate", or unless Beta releases show up as an in-app notification similar to regular releases...

So I'm curious, do you have any data (or just anecdata) on what the distribution of calibre versions is among users "in the wild" at any given moment?

Or, failing that, how long it usually takes until most (however you want to define "most") users upgrade to the latest version?

Or, failing that, just what the graph of downloads/day looks like in the period after you release a new version and how long it takes to taper off (assuming it does)?

[kovidgoyal]

https://calibre-ebook.com/dynamic/calibre-usage

The purpose of the beta is to increase the probability that there are no showstopper bugs in commonly used functionality on all the major platforms calibre supports.

Since calibre follows the release early and often development philosophy, and has a fairly extensive test suite (at least for more modern features), that is all that is needed.

Feature requests get taken care of in the usual calibre release cadence.

[kovidgoyal]

Oh and I did day *at least* two weeks, not at most two weeks

[theducks]

This croud is *GOOD* at quickly discovering previously unknow show stoppers
Just look at how fast Kovid pulled XP support from the Calibre 2.0 release when it was discovered how fragile that combination was (it was not worth holding back NEW functionality, just for an obsolete OS )

[webmaven]

Originally Posted by kovidgoyal

https://calibre-ebook.com/dynamic/calibre-usage

Ah, good data! So, in the 3 weeks since 2.83 was released, 25% of the installs are at that version or higher (for comparison, it's taken 3 months for ~50% of users to be at 2.79 or higher). That's a lot more than I would have expected, so I guess 2 weeks or so would be quite enough.

Originally Posted by kovidgoyal

The purpose of the beta is to increase the probability that there are no showstopper bugs in commonly used functionality on all the major platforms calibre supports.

This does sound a lot more like the definition of a "Release Candidate" than a "Beta", but I do understand many people use "Beta" in this way.

Originally Posted by kovidgoyal

Since calibre follows the release early and often development philosophy, and has a fairly extensive test suite (at least for more modern features), that is all that is needed.

Feature requests get taken care of in the usual calibre release cadence.

OK.

BTW, do you follow semantic versioning conventions? That is, does changing from "2.x" to "3.x" indicate breaking backwards compatibility?

[kovidgoyal]

No I dont follow semantic versioning. calibre is way to ocomplex to try to communicate something as complex as breakage of backward compatibility by a single number.

That said, large, likely to be disrputive changes do get a bump in major version number.