Hmm just tried CoolReader now and it's of fmy machine already. I found the hyphenation to be poor and no good justification and that page transition was terrible. IMHO of course.
Mind you nothing will beat uBook once fully ported!
µBook Android -- preview images
Started By uBook, Sep 27 2010 04:03 PM
66 replies to this topic
#61
Posted 29 December 2010 - 03:52 PM
Daron Brewood
C.E.O. www.smartphonegurus.com

Windows Phone 7 Expert
Phones: Sensation XE, Sensation XL, iPhone 4, Desire S, Mozart, HD7, Galaxy SII
C.E.O. www.smartphonegurus.com

Windows Phone 7 Expert
Phones: Sensation XE, Sensation XL, iPhone 4, Desire S, Mozart, HD7, Galaxy SII
#62
Posted 30 December 2010 - 11:30 AM
Yes, CoolReader hyphenation is bad. I don't see any problem with the justification, though, and I've got used to the page transition - it's more subdued that the curly page effect I've seen on some of the others!
I totally agree with your final point...
I totally agree with your final point...
#63
Posted 30 December 2010 - 01:25 PM
Well on my justification I like centered and unless I missed it that is not one of the options. The page turning I can put up with but the latest version of MoonReader really screwed that up for me so I'm back to FBReader alas.
Daron Brewood
C.E.O. www.smartphonegurus.com

Windows Phone 7 Expert
Phones: Sensation XE, Sensation XL, iPhone 4, Desire S, Mozart, HD7, Galaxy SII
C.E.O. www.smartphonegurus.com

Windows Phone 7 Expert
Phones: Sensation XE, Sensation XL, iPhone 4, Desire S, Mozart, HD7, Galaxy SII
#64
Posted 01 January 2011 - 03:31 PM
Bibliophile. I have tested ubook on my epad and it works full screen without issue. Not sure why the galaxy tab doesn't display full screen.
#65
Posted 13 January 2011 - 01:57 PM
Well, the epad has a 10 inch screen, and the Galaxy Tab has only a 7 inch screen, so you would think there would be no problem.
BUT – the epad is 800 x 480 pixels, while the Galaxy Tab is 1024 x 600. So from a development point of view, the Galaxy Tab is actually a larger screen!
I suspect (putting my developer hat on for a moment) that uBook may need to have some extra lines in the AndroidManifest.xml file:
<uses-sdk android:minSdkVersion="3"
android:targetSdkVersion="8" />
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:anyDensity="true" />
(I think I got that from here: http://www.readwrite...t-your-andr.php, It works in my app...)
Samsung have also made an emulator available (here: http://innovator.sam...om/galaxyTab.do) so testing should be no problem. Especially as It's FREE!
BUT – the epad is 800 x 480 pixels, while the Galaxy Tab is 1024 x 600. So from a development point of view, the Galaxy Tab is actually a larger screen!
I suspect (putting my developer hat on for a moment) that uBook may need to have some extra lines in the AndroidManifest.xml file:
<uses-sdk android:minSdkVersion="3"
android:targetSdkVersion="8" />
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:anyDensity="true" />
(I think I got that from here: http://www.readwrite...t-your-andr.php, It works in my app...)
Samsung have also made an emulator available (here: http://innovator.sam...om/galaxyTab.do) so testing should be no problem. Especially as It's FREE!
#66
Posted 25 March 2011 - 04:04 AM
Bibliophile, on 13 January 2011 - 01:57 PM, said:
Well, the epad has a 10 inch screen, and the Galaxy Tab has only a 7 inch screen, so you would think there would be no problem.
BUT – the epad is 800 x 480 pixels, while the Galaxy Tab is 1024 x 600. So from a development point of view, the Galaxy Tab is actually a larger screen!
I suspect (putting my developer hat on for a moment) that uBook may need to have some extra lines in the AndroidManifest.xml file:
<uses-sdk android:minSdkVersion="3"
android:targetSdkVersion="8" />
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:anyDensity="true" />
(I think I got that from here: http://www.readwrite...t-your-andr.php, It works in my app...)
Samsung have also made an emulator available (here: http://innovator.sam...om/galaxyTab.do) so testing should be no problem. Especially as It's FREE!
BUT – the epad is 800 x 480 pixels, while the Galaxy Tab is 1024 x 600. So from a development point of view, the Galaxy Tab is actually a larger screen!
I suspect (putting my developer hat on for a moment) that uBook may need to have some extra lines in the AndroidManifest.xml file:
<uses-sdk android:minSdkVersion="3"
android:targetSdkVersion="8" />
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:anyDensity="true" />
(I think I got that from here: http://www.readwrite...t-your-andr.php, It works in my app...)
Samsung have also made an emulator available (here: http://innovator.sam...om/galaxyTab.do) so testing should be no problem. Especially as It's FREE!
Actually incorrect, my epad has a 1024x600 screen, same as the Galaxy Tab.
#67
Posted 27 March 2011 - 02:27 PM
I stand corrected, Kitiara. I got the figures from somewhere on the web, but I can't remember where. It's a bit academic now, though, because the problem has been solved, and uBook runs full screen for me.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users














