Beta testers for calibre 3.0 needed

[kovidgoyal]

@DD: That image is buggy, if you look at they style attribute on the <svg> tag it has max-with and max-height defined without units. That's why it gets blown up. And note that it only gets blown up in Firefox, not Chrome. Probably the ebook authors only tested it on webkit based rendering engines (which botht he calibre viewer and chrome have), which are more common so that's why they didn't notice the problem. In any case if you fix the max-width it will be fine in firefox as well.

[kovidgoyal]

@Martina: Yeah the detailed list view does not work very well on extremely narrow screens. Maybe I should have it auto hide the rating and series part if the screen is too narrow.

[kovidgoyal]

@Martina: This should fix it:
https://github.com/kovidgoyal/calibr...f754782b4a3947

[Divingduck]

Originally Posted by kovidgoyal

@DD: That image is buggy, if you look at they style attribute on the <svg> tag it has max-with and max-height defined without units. That's why it gets blown up. And note that it only gets blown up in Firefox, not Chrome. Probably the ebook authors only tested it on webkit based rendering engines (which botht he calibre viewer and chrome have), which are more common so that's why they didn't notice the problem. In any case if you fix the max-width it will be fine in firefox as well.

Thanks for the feedback. I guess the publisher tests against ADE too. I checked my books from this Publisher (~30) with the editor and a lot show the same coding and behavior with Firefox. My eReader's from Sony and Pocketbook and different viewer like ADE and your GUI-Viewer do not have an issue with it. Anyway, I won't change the books for Firefox only. But I need to remember, that the combination svg/viewbox/units and Firefox sometimes have problems.
The point I wonder about is, why Firefox need a unit where others do not need it. I often don't use units too because of the fallback to px if I want to measure in px for my ebook and as fare as I remember, I had never a problem with this. But maybe I had only luck in the past.

Again, thanks for looking to this.

Best regards, DD

[kovidgoyal]

As per the CSS spec those properties require units, so Firefox is technically correct. https://developer.mozilla.org/en/docs/Web/CSS/max-width

[Divingduck]

Yeah, that drives me grazy. If I look into W3/SVG (https://www.w3.org/TR/SVG/coords.html) "7.10 Units" it starts with:
All coordinates and lengths in SVG can be specified with or without a unit identifier.
If I remember correct, there were some SVG teacher's who recommend to initialize the coordinate system with a first measurement unit statement like you have explain to me.
Well, that's life. Have a nice week end.

DD

[Martina Schein]

Originally Posted by kovidgoyal

@Martina: This should fix it:
https://github.com/kovidgoyal/calibr...f754782b4a3947

Thank you very much, Kovid. I'm excited.

Have a nice Sunday
Martina

[patrik]

Just noticed that I got this output:

# cbeta2996/calibre
Failed to initialize plugin: '/home/patrik/.config/calibre/plugins/KePub Output.zip'
Failed to initialize plugin: '/home/patrik/.config/calibre/plugins/KoboTouchExtended.zip'
Failed to initialize plugin: '/home/patrik/.config/calibre/plugins/KePub Metadata Writer.zip'
Failed to initialize plugin: '/home/patrik/.config/calibre/plugins/KePub Metadata Reader.zip'
Failed to initialize plugin: '/home/patrik/.config/calibre/plugins/KePub Input.zip'

I restarted Calibre in debug-mode, but it all looked good. Restarted in normal mode, all good.

Have been using 2.99.x normally and so far everything has worked fine.

Not sure it's anything, but thought you may want to know in case there are other similar problems.

- Linux Mint 17
- Calibre 2.99.6 64 bit (in test directory)
- Calibre 2.83 installed per default

[BetterRed]

Originally Posted by kovidgoyal

Released version 2.99.6 with the following changes:

• Make the book details page in the browser render the same way as in the GUI, including the order and excluded fields. In other words you can now control the displayed fields the same way as you do in the GUI (the setting is common to both server and GUI)

Thanks, but...

My hope for the new server was that I'd be able to use it to compare all the metadata columns of book X in library A, with all the metadata columns of book Y in library B, using a split browser.

Checking all the columns in L&F->Book Details in both libraries results in all the metadata being shown in the Book Details panel. I really would prefer to keep that to a 'most need to see' subset of the metadata columns.

It's a low volume issue, and I already have an established 'method' to do what I want. So I will continue with it.
================

Is there a way to exclude items from the list of categories in Search?

Will future versions of the new server have support for anything like 'add-ons' and 'adaptations', a'la GUI 'plug-ins' and 'customisations'?

BTW - I like the idea of a GUI front-end to server, especially if the opens up the possibility of running multiple GUI's to multiple libraries. I'm not enamoured with browser based UI's for fixed data applications.

BR

[kovidgoyal]

@BR: No reason the server cannot grow an "all metadata view" just like double clicking on the book details panel gives you now. No there's no way to restrict the list of categories in Search (other than using Virtual Libraries). Again not particularly hard to add in the future. I have no plans to add a plugin system for the server, but that does not mean it will never happen. We shall see how much interest there is in the server UI iin the first place. There are lots of other parts of calibre that need love, I've spent a lot of time on this beastie already

[kovidgoyal]

@BR: https://github.com/kovidgoyal/calibr...97e2c1df01a185

[kovidgoyal]

For those of you running from source, I have merged the vs2015 branch into master. So switch back to master. And note that you cannot run from source and use a 2.x calibre build anymore.

[chaley]

Originally Posted by kovidgoyal

For those of you running from source, I have merged the vs2015 branch into master. So switch back to master. And note that you cannot run from source and use a 2.x calibre build anymore.

What binary do we use? The only ones I can find are V2. Can we use the V2.99 binaries?

[eschwartz]

chaley -- sure, it is merely that the beta is now live and living on the master branch.

... and python2-mechanize is still not updated in the Arch repos, which is slightly awkward for my AUR calibre-git package...

[kovidgoyal]

@chaley: Yes, you use the 2.99 binaries.