Beta testers for calibre 3.0 needed - Page 29

Martina Schein · 06-05-2017, 10:31 AM

I'm working on all the eBooks with the Calibre Editor I've purchased and those that are free, before I copy them to my Reader. With none of the different versions (2.99.1 to 2.99.10) I had any problems.

However, the eBook must be saved before you can view it with the Calibre Viewer (not the real-time preview in the editor). Than the eBook is already saved.

aCIDsLAM · 06-08-2017, 07:15 AM

Hello kovidgoyal,
just wanted to let you know. The problem with a windows core server (Now its 2016) as explained here,
https://www.mobileread.com/forums/sh...d.php?t=279312
also exsist in the new beta.

Output:

Python function terminated unexpectedly
cannot import name QColor (Error Code: 1)
Traceback (most recent call last):
File "site.py", line 101, in main
File "site.py", line 77, in run_entry_point
File "site-packages\calibre\srv\standalone.py", line 15, in <module>
File "site-packages\calibre\srv\library_broker.py", line 13, in <module>
File "site-packages\calibre\db\legacy.py", line 18, in <module>
File "site-packages\calibre\db\backend.py", line 33, in <module>
File "site-packages\calibre\utils\img.py", line 16, in <module>
ImportError: cannot import name QColor

I am still using calibre 2.55

kovidgoyal · 06-08-2017, 08:50 AM

@acidslam: As I sad the memoryloadimage problem is gone. Now you seem to be having another problem. What does running the following output

calibre-debug -c "from PyQt5.QtGui import QColor"

aCIDsLAM · 06-08-2017, 09:19 AM

Quote:

Originally Posted by kovidgoyal

@acidslam: As I sad the memoryloadimage problem is gone. Now you seem to be having another problem. What does running the following output

calibre-debug -c "from PyQt5.QtGui import QColor"

PS C:\DFSRoots> calibre-debug -c "from PyQt5.QtGui import QColor"
Python function terminated unexpectedly
DLL load failed: The specified module could not be found. (Error Code: 1)
Traceback (most recent call last):
File "site.py", line 101, in main
File "site.py", line 78, in run_entry_point
File "site-packages\calibre\debug.py", line 261, in main
File "<string>", line 1, in <module>
File "site.py", line 39, in load_module
ImportError: DLL load failed: The specified module could not be found.

Mhhh. Actually its 2.56 which is working last. Not 2.55. Thanks for looking

kovidgoyal · 06-08-2017, 10:34 AM

That indicates it is failing to find a DLL. Hard to know why, since it doesn't say which DLL. I assume the calibre installation folder is not corrupted? All the DLLs are present?

kovidgoyal · 06-09-2017, 03:41 AM

@acidslam: You can use procmon.exe to figure out what DLL it is trying to load when failing. Unfortunately I dont know of a non-GUI way to do that on windows.

kovidgoyal · 06-09-2017, 04:31 AM

I decided to make one more beta release (2.99.11) to try out a little UI polishing. The changes are:

1) Add a button in the bottom right corner to hide the search bar

2) Remove the saved search box, replacing it with a button to add a saved search. Since saved searches can be run from the Tag browser this box was unnecessary duplication. However if you dont use the Tag browser and want to get the box back, there is a tweak for it in Preferences->Tweaks.

3) Hide the "Find in Tag browser" search box by default. There is a button you can use to show it at the bottom of the Tag browser and it will remember its state between calibre restarts

4) Fix extra padding between the toolbar and search bar.

5) Remove the button to clear the search box, instead moving it into the search box itself.

theducks · 06-09-2017, 05:36 AM

I did not know what all the hoo-ha was about. Then I tried dot 11 and found the cleaner UI is very nice without the clutter of a lesser used (frequency) set of controls

FWIW Ctrl-F (the way I typically jump to the search), makes the bar appear, if hidden. Bravo, for a feature I did not know I wanted.

chaley · 06-09-2017, 05:41 AM

Quote:

Originally Posted by kovidgoyal

I decided to make one more beta release (2.99.11) to try out a little UI polishing. The changes are:

1) Add a button in the bottom right corner to hide the search bar

2) Remove the saved search box, replacing it with a button to add a saved search. Since saved searches can be run from the Tag browser this box was unnecessary duplication. However if you dont use the Tag browser and want to get the box back, there is a tweak for it in Preferences->Tweaks.

3) Hide the "Find in Tag browser" search box by default. There is a button you can use to show it at the bottom of the Tag browser and it will remember its state between calibre restarts

FWIW: I am not in favor of these changes. I use all three features frequently, but that isn't the reason I am opposed. The reasons:

I suspect that the three changes will create no end of unhappiness similar to when the search highlight button was removed; post after post saying "WTF? Where did X go?" or "How do I do X?".
Saved searches are no longer discoverable.
Navigating down through the tag browser is much slower than using the dropdown box and is harder for people who prefer keyboards.
Searches in the tag browser are also no longer easily discoverable.
The changes seem to target smaller screens, which are becoming more and more a rarity.

I think that tweaks should be used to make them go away, not to make them appear.

kovidgoyal · 06-09-2017, 07:05 AM

@chaley: My intention is to make saved searches less discoverable. There are virtual libraries that perform the same function in a much user-friendlier manner. The only case where saved searches are useful is if you want to use both VLs and Saved searches. And for such use cases (which are relatively rare) the tweak exists to restore the saved search box.

As for the button to hide the search bar, if you dont want to use it, simply ignore its existence. The search bar defaults to shown.

My overall concern with these changes is to de-clutter the UI a bit to make it more obvious what are the main functions of calibre, while still allowing power users to use the power tools relatively easily. It doesn't have much to do with small screens, although working better on small screens is a nice bonus.

I dont think this change is on par witht he chage to remove the search highlights button. The hide search bar button basically works just like the hide tag browser/etc. buttons. And while we do get the occasional post from someone who has hidden one of the panels and cant find them again, it is not nearly as bad as for search highlights. Not to mention that, IIRC, the problem with the search highlights button was much worse before that button was hidden. People would keep clicking it and not knowing why their searches were not filters any more.

aCIDsLAM · 06-09-2017, 07:42 AM

Quote:

Originally Posted by kovidgoyal

@acidslam: You can use procmon.exe to figure out what DLL it is trying to load when failing. Unfortunately I dont know of a non-GUI way to do that on windows.

The same way as a gui server. if its not a nano server, you can run minimal gui programms such as procmon.exe

Here is the output of calibre-debug -c "from PyQt5.QtGui import QColor", excluding success. Acutally its hard to read and is missing alot of stuff, so it pasted it completly, without taskname, time etc

Spoiler:

chaley · 06-09-2017, 07:44 AM

Quote:

Originally Posted by kovidgoyal

@chaley: My intention is to make saved searches less discoverable. There are virtual libraries that perform the same function in a much user-friendlier manner. The only case where saved searches are useful is if you want to use both VLs and Saved searches. And for such use cases (which are relatively rare) the tweak exists to restore the saved search box.

I use both saved searches and VLs and I don't think they are at all equivalent. Saved searches don't change the tag browser. They don't change the counts or average ratings. They don't affect QuickView. I can compose them trivially with "or", something that can't be done with VLs because VLs support "and" composition of searches only as long as the primary search is the VL itself. Saved searches are trivially editable, or at least they were until you removed the "Copy current search" button. And as far as I can tell, the new browser pushes users hard toward using saved searches instead of VLs because of user restrictions.

It seems that you are moving toward what lots of Android apps are doing, "simplifying" the interface to the point that no one has a clue what the app can do. One must guess to find the functions: tap, press, squeeze, shake, swipe, rotate, double-tap, and other stuff. Yes, this works for people who want only the functions that are easily visible. Others simply give up. I have several relatives who refuse to use their phones because they can't figure out how the apps work, and once they *do* figure it out then the app changes.

On the other hand, calibre *is* yours to change as you wish. And perhaps you are correct and the changes will increase happiness with calibre. I hope so.

aCIDsLAM · 06-09-2017, 08:08 AM

Quote:

Originally Posted by kovidgoyal

@acidslam: You can use procmon.exe to figure out what DLL it is trying to load when failing. Unfortunately I dont know of a non-GUI way to do that on windows.

The same way as a gui server. if its not a nano server, you can run minimal gui programms such as procmon.exe

Here is the output of calibre-debug, excluding success and runngin with the debug command and parameter. Acutally its hard to read and is missing alot of stuff, so it pasted it completly, without taskname, time etc

Spoiler:

kovidgoyal · 06-09-2017, 08:57 AM

@chaley: Take it easy, I have no intention of appifying calibre's interface. And editing saved searches remains pretty easy even if you dont use the tweak to restore the saved search box. You can right click on the add search button and manage saved searches.

In fact, I think I will add the existing saved searches to that right click menu, so you dont even have to use the tag browser to launch a saved search.

The one thing the change does do is make the feature less discovereable. That is indeed an unaviodable tradeoff.

kovidgoyal · 06-09-2017, 09:00 AM

@acidslam: As best as I can tell, it looks like its looking for opengl32.dll and failing.

06-08-2017, 07:15 AM	#422
aCIDsLAM Enthusiast Posts: 28 Karma: 10 Join Date: Oct 2016 Device: Xiaomi MI Pad 1, LineageOS14.1	Calibre on windows core server Hello kovidgoyal, just wanted to let you know. The problem with a windows core server (Now its 2016) as explained here, https://www.mobileread.com/forums/sh...d.php?t=279312 also exsist in the new beta. Output: Python function terminated unexpectedly cannot import name QColor (Error Code: 1) Traceback (most recent call last): File "site.py", line 101, in main File "site.py", line 77, in run_entry_point File "site-packages\calibre\srv\standalone.py", line 15, in <module> File "site-packages\calibre\srv\library_broker.py", line 13, in <module> File "site-packages\calibre\db\legacy.py", line 18, in <module> File "site-packages\calibre\db\backend.py", line 33, in <module> File "site-packages\calibre\utils\img.py", line 16, in <module> ImportError: cannot import name QColor I am still using calibre 2.55

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Beta testers needed	kovidgoyal	Calibre	54	05-20-2016 12:34 PM
Windows beta testers needed	kovidgoyal	Calibre	19	02-08-2016 04:38 PM
Beta testers for calibre 2.0 needed	kovidgoyal	Calibre	142	05-08-2015 04:44 AM
Arc Updated Jelly Bean release - Beta testers needed	kobo-adrian	Kobo Tablets	19	05-23-2013 09:32 PM
Web Browsing from the Ebw-1150 - BETA Testers needed	Nate the great	Fictionwise eBookwise	26	09-21-2008 11:52 PM

06-05-2017, 10:31 AM	#421
Martina Schein eBook-Reader-Fan Posts: 175 Karma: 444178 Join Date: Sep 2012 Location: Saarbruecken / DE Device: Kobo Aura H2O 2nd Edition	I'm working on all the eBooks with the Calibre Editor I've purchased and those that are free, before I copy them to my Reader. With none of the different versions (2.99.1 to 2.99.10) I had any problems. However, the eBook must be saved before you can view it with the Calibre Viewer (not the real-time preview in the editor). Than the eBook is already saved.

06-08-2017, 08:50 AM	#423
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@acidslam: As I sad the memoryloadimage problem is gone. Now you seem to be having another problem. What does running the following output calibre-debug -c "from PyQt5.QtGui import QColor"

06-08-2017, 10:34 AM	#425
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	That indicates it is failing to find a DLL. Hard to know why, since it doesn't say which DLL. I assume the calibre installation folder is not corrupted? All the DLLs are present?

06-09-2017, 03:41 AM	#426
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@acidslam: You can use procmon.exe to figure out what DLL it is trying to load when failing. Unfortunately I dont know of a non-GUI way to do that on windows.

06-09-2017, 04:31 AM	#427
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	I decided to make one more beta release (2.99.11) to try out a little UI polishing. The changes are: 1) Add a button in the bottom right corner to hide the search bar 2) Remove the saved search box, replacing it with a button to add a saved search. Since saved searches can be run from the Tag browser this box was unnecessary duplication. However if you dont use the Tag browser and want to get the box back, there is a tweak for it in Preferences->Tweaks. 3) Hide the "Find in Tag browser" search box by default. There is a button you can use to show it at the bottom of the Tag browser and it will remember its state between calibre restarts 4) Fix extra padding between the toolbar and search bar. 5) Remove the button to clear the search box, instead moving it into the search box itself.

06-09-2017, 05:36 AM	#428
theducks Well trained by Cats Posts: 31,061 Karma: 60358908 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	I did not know what all the hoo-ha was about. Then I tried dot 11 and found the cleaner UI is very nice without the clutter of a lesser used (frequency) set of controls FWIW Ctrl-F (the way I typically jump to the search), makes the bar appear, if hidden. Bravo, for a feature I did not know I wanted.

06-09-2017, 07:05 AM	#430
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@chaley: My intention is to make saved searches less discoverable. There are virtual libraries that perform the same function in a much user-friendlier manner. The only case where saved searches are useful is if you want to use both VLs and Saved searches. And for such use cases (which are relatively rare) the tweak exists to restore the saved search box. As for the button to hide the search bar, if you dont want to use it, simply ignore its existence. The search bar defaults to shown. My overall concern with these changes is to de-clutter the UI a bit to make it more obvious what are the main functions of calibre, while still allowing power users to use the power tools relatively easily. It doesn't have much to do with small screens, although working better on small screens is a nice bonus. I dont think this change is on par witht he chage to remove the search highlights button. The hide search bar button basically works just like the hide tag browser/etc. buttons. And while we do get the occasional post from someone who has hidden one of the panels and cant find them again, it is not nearly as bad as for search highlights. Not to mention that, IIRC, the problem with the search highlights button was much worse before that button was hidden. People would keep clicking it and not knowing why their searches were not filters any more.

06-09-2017, 08:57 AM	#434
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@chaley: Take it easy, I have no intention of appifying calibre's interface. And editing saved searches remains pretty easy even if you dont use the tweak to restore the saved search box. You can right click on the add search button and manage saved searches. In fact, I think I will add the existing saved searches to that right click menu, so you dont even have to use the tag browser to launch a saved search. The one thing the change does do is make the feature less discovereable. That is indeed an unaviodable tradeoff.

06-09-2017, 09:00 AM	#435
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@acidslam: As best as I can tell, it looks like its looking for opengl32.dll and failing.