Comments on: eReader updated to version 2.1 http://www.teleread.org/2009/05/08/ereader-updated-to-version-21/ News & views on e-books, libraries, publishing and related topics Sun, 22 Nov 2009 13:46:44 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Bill Davidson http://www.teleread.org/2009/05/08/ereader-updated-to-version-21/comment-page-1/#comment-1054476 Bill Davidson Sun, 10 May 2009 03:05:42 +0000 http://www.teleread.org/?p=21586#comment-1054476 Thanks Chris! bill Thanks Chris!

bill

]]> By: Chris Meadows http://www.teleread.org/2009/05/08/ereader-updated-to-version-21/comment-page-1/#comment-1054469 Chris Meadows Sun, 10 May 2009 02:43:57 +0000 http://www.teleread.org/?p=21586#comment-1054469 The evidence is 1)in the email that Steve P. sent me saying it was for a Terms of Service issue (which, granted, you can't directly access) and 2) in the paragraph at the bottom of the help page you get when you tap the question mark button on the "other websites" page in your eReader app (which you can). The evidence is 1)in the email that Steve P. sent me saying it was for a Terms of Service issue (which, granted, you can’t directly access) and 2) in the paragraph at the bottom of the help page you get when you tap the question mark button on the “other websites” page in your eReader app (which you can).

]]> By: Bill Davidson http://www.teleread.org/2009/05/08/ereader-updated-to-version-21/comment-page-1/#comment-1054404 Bill Davidson Sun, 10 May 2009 00:19:34 +0000 http://www.teleread.org/?p=21586#comment-1054404 I didn't see evidence of Apple's interference. Can you provide some? bill I didn’t see evidence of Apple’s interference. Can you provide some?
bill

]]> By: Chris Meadows http://www.teleread.org/2009/05/08/ereader-updated-to-version-21/comment-page-1/#comment-1053859 Chris Meadows Sat, 09 May 2009 00:43:23 +0000 http://www.teleread.org/?p=21586#comment-1053859 Well, presumably we won't need to "build" a custom prefix. Just type it into the blank in eReader where you'd otherwise type http://. But for people who have actual directory pages set up, that could be a problem. (Though then again, perhaps a mass search-and-replace in the HTML code could take care of that.) What with the Tweetie thing, the NIN thing, and now the <a href="http://arstechnica.com/apple/news/2009/05/apple-drawing-30-line-in-the-sand-for-iphone-developers.ars" rel="nofollow">OS 3.0 vs OS 2 compatibility catch-22</a>, I've long since stopped expecting sensibility out of Apple. Well, presumably we won’t need to “build” a custom prefix. Just type it into the blank in eReader where you’d otherwise type http://.

But for people who have actual directory pages set up, that could be a problem. (Though then again, perhaps a mass search-and-replace in the HTML code could take care of that.)

What with the Tweetie thing, the NIN thing, and now the OS 3.0 vs OS 2 compatibility catch-22, I’ve long since stopped expecting sensibility out of Apple.

]]> By: David S. http://www.teleread.org/2009/05/08/ereader-updated-to-version-21/comment-page-1/#comment-1053805 David S. Fri, 08 May 2009 22:16:47 +0000 http://www.teleread.org/?p=21586#comment-1053805 Chris is on the money re 2.1, it seems to have fixed all the auto-syncing nonsense from 2.0.x and returned the ability to add your own content, but at the cost of a much more convoluted (and far less flexible) eReader>Safari>eReader download process. I am also assuming this was done at Apple's behest, but whatever the explanation it's a mess and creates all sorts of problems for users with large collections of .pdb files on their hard drives (both DRMed and non-DRMed from both Fictionwise/eReader and other sources) that they want to selectively upload to their iPhone/iPod touch. Forcing us to build custom HTML prefixes for every file is a real burden and requires much more work in setting up (and maintaining) a local webserver than was previously the case. Why oh why won't Apple just let users import generic data files into iTunes, associate them with a given application, and then sync them to the device and app like music/movies/podcasts? Chris is on the money re 2.1, it seems to have fixed all the auto-syncing nonsense from 2.0.x and returned the ability to add your own content, but at the cost of a much more convoluted (and far less flexible) eReader>Safari>eReader download process. I am also assuming this was done at Apple’s behest, but whatever the explanation it’s a mess and creates all sorts of problems for users with large collections of .pdb files on their hard drives (both DRMed and non-DRMed from both Fictionwise/eReader and other sources) that they want to selectively upload to their iPhone/iPod touch.

Forcing us to build custom HTML prefixes for every file is a real burden and requires much more work in setting up (and maintaining) a local webserver than was previously the case.

Why oh why won’t Apple just let users import generic data files into iTunes, associate them with a given application, and then sync them to the device and app like music/movies/podcasts?

]]> By: Chris Meadows http://www.teleread.org/2009/05/08/ereader-updated-to-version-21/comment-page-1/#comment-1053634 Chris Meadows Fri, 08 May 2009 15:20:37 +0000 http://www.teleread.org/?p=21586#comment-1053634 It definitely has both Manybooks and "other site" access, the two things that people were complaining had disappeared from v2.0. Interestingly, it now launches Mobile Safari to browse the site, instead of doing it from within eReader itself. Also interestingly, and perhaps a bit annoyingly, one can no longer download a file directly in just by entering http:// and the URL/name of the file. You must use the prefix ereader:// and any website offering eReader files for direct iPhone download must use said prefix as well. I guess this is a result of the Apple terms of service issue that forced the removal of the features in 2.0. They weren't allowed to act like a web browser, and had to use the actual web browser instead. It definitely has both Manybooks and “other site” access, the two things that people were complaining had disappeared from v2.0. Interestingly, it now launches Mobile Safari to browse the site, instead of doing it from within eReader itself.

Also interestingly, and perhaps a bit annoyingly, one can no longer download a file directly in just by entering http:// and the URL/name of the file. You must use the prefix ereader:// and any website offering eReader files for direct iPhone download must use said prefix as well.

I guess this is a result of the Apple terms of service issue that forced the removal of the features in 2.0. They weren’t allowed to act like a web browser, and had to use the actual web browser instead.

]]>