MobileRead Forums - View Single Post

JimmXinu · 06-02-2017, 12:50 PM

I've been successfully using the beta version (running from source usually) for a week or so. It's looking really good.

There are a few cosmetic differences in the GUI, but the only substantial change I've noticed is that 'sending metadata to device' (ie, writing the metadata file) is hugely faster. Thanks for that.

In the new Content Server a couple nitpicks I've noticed:

content_server_will_display and content_server_wont_display tweaks don't work. Tweaks specific to older versions could be removed, hidden or documented as older-version-only perhaps?
'Comma' formatting on custom Integer('{:,}') and Float('{0:,.3f}') columns isn't being applied. (1234 vs 1,234 and 1234.11 vs 1,234.11) Float decimal format ('{0:,.3f}' vs '{0:,.2f}') is applied. I assume comma grouping is a calibre extension to Python's formatting?

FYI, the links you gave in first post to github are broken with removal of branch v2015. v2015->master gives usable links:

https://github.com/kovidgoyal/calibr...e/srv/TODO.rst
https://github.com/kovidgoyal/calibr.../custom.py#L99

I'm looking at the source for the server and the calibredb client. I'll need a while before I'm familiar enough to offer any useful comment myself, but do you have any plans or ideas for content server plugins, or integrations so GUI plugins could be called from content server or calibredb?

Semi-related, are DB updates transacted now such that plugins could skip using proceed_question() to obtain DB lock before updating metadata?

As always, thanks for all your great work on calibre.

06-02-2017, 12:50 PM	#410
JimmXinu Plugin Developer Posts: 7,027 Karma: 4604637 Join Date: Dec 2011 Location: Midwest USA Device: Kobo Clara Colour running KOReader	I've been successfully using the beta version (running from source usually) for a week or so. It's looking really good. There are a few cosmetic differences in the GUI, but the only substantial change I've noticed is that 'sending metadata to device' (ie, writing the metadata file) is hugely faster. Thanks for that. In the new Content Server a couple nitpicks I've noticed: content_server_will_display and content_server_wont_display tweaks don't work. Tweaks specific to older versions could be removed, hidden or documented as older-version-only perhaps? 'Comma' formatting on custom Integer('{:,}') and Float('{0:,.3f}') columns isn't being applied. (1234 vs 1,234 and 1234.11 vs 1,234.11) Float decimal format ('{0:,.3f}' vs '{0:,.2f}') is applied. I assume comma grouping is a calibre extension to Python's formatting? FYI, the links you gave in first post to github are broken with removal of branch v2015. v2015->master gives usable links: https://github.com/kovidgoyal/calibr...e/srv/TODO.rst https://github.com/kovidgoyal/calibr.../custom.py#L99 I'm looking at the source for the server and the calibredb client. I'll need a while before I'm familiar enough to offer any useful comment myself, but do you have any plans or ideas for content server plugins, or integrations so GUI plugins could be called from content server or calibredb? Semi-related, are DB updates transacted now such that plugins could skip using proceed_question() to obtain DB lock before updating metadata? As always, thanks for all your great work on calibre.