03-17-2012, 05:26 PM | #46 | |
Addict
Posts: 377
Karma: 770002
Join Date: Dec 2011
Location: Windsor, Nova Scotia
Device: Kobo Aura
|
Quote:
|
|
03-17-2012, 05:30 PM | #47 |
Cynical Old Curmudgeon
Posts: 1,085
Karma: 8495696
Join Date: Jul 2011
Location: Halifax, Canada
Device: Kobo Mini, Kobo Arc, HTC Desire C
|
|
03-17-2012, 05:36 PM | #48 |
Connoisseur
Posts: 75
Karma: 233442
Join Date: Dec 2009
Location: Toronto, Canada
Device: Sony PRS-600, Kobo Touch, Kindle PW2
|
RareBird, you're right, it was not directed at you.
Windsor, NS? I'm an Acadia Alumnut. |
03-17-2012, 05:52 PM | #49 |
Addict
Posts: 377
Karma: 770002
Join Date: Dec 2011
Location: Windsor, Nova Scotia
Device: Kobo Aura
|
I'm an alum of Acadia too! How about that!
|
03-17-2012, 05:53 PM | #50 |
Wizard
Posts: 2,454
Karma: 5469320
Join Date: Jul 2010
Device: Kobo
|
Try adjusting your margins in the sideloaded e-pubs. If I go from a k-epub with a nice little margin that I like to a sideload e-pub, I have no side margin in the sideload until I change the settting to a slightly larger margin.
|
03-17-2012, 06:08 PM | #51 | |
No Comment
Posts: 3,238
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
Quote:
Be careful, as it is possible to screw this up. |
|
03-17-2012, 06:17 PM | #52 | |
No Comment
Posts: 3,238
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
Quote:
KoboRoot.tgz CRC 2B005F71 Size 59,293,286 Date 16/03/2012 16:44 |
|
03-17-2012, 06:35 PM | #53 | ||
Member
Posts: 17
Karma: 13124
Join Date: Jan 2012
Device: Kobo Touch
|
Quote:
Quote:
Last edited by Boruteczko; 03-17-2012 at 06:50 PM. |
||
03-17-2012, 07:02 PM | #54 | |
Connoisseur
Posts: 75
Karma: 233442
Join Date: Dec 2009
Location: Toronto, Canada
Device: Sony PRS-600, Kobo Touch, Kindle PW2
|
Quote:
- Kobo has several devices, and each device requires both maintenance (support) and new features (development)...not just the Touch - In order for the software to be manageable, I suspect Kobo tries to keep a single set of source code across all devices where possible. Having to add the same function to each device individually would be cost-prohibitive and would just get passed on to the consumer. - Most software shops stick to a regular schedule for software releases. Time for requirements gathering (defects + new features); time to design the changes; time to develop the changes; time to test the changes internally; time to beta test the changes with the community. This all takes time. 3 months is very typical. I've been working in software for 25 years, so I could go on... |
|
03-17-2012, 08:29 PM | #55 | |
Member
Posts: 17
Karma: 13124
Join Date: Jan 2012
Device: Kobo Touch
|
Quote:
PS. I'd be really content with the new firmware but for the margins problems (just try to imagine reading a paper book without any margins.) |
|
03-17-2012, 08:50 PM | #56 | |
Member
Posts: 17
Karma: 11516
Join Date: Jan 2012
Device: Kobo Touch
|
3 Months still too long
Quote:
Oh come off it you may not be affiliated with the Kobo company, but you sure sound like you are. Maybe it's just your round and aboot way of showing your loyalty to a Canadian company( if they are still Canadian) the 59p goodreader app I bought off the app store has been constantly adding new features and bug fixes and they still manage to have a faster development cycle. Btw, the firmware so far is a lot faster and smoother; Library, short-list and page turning are all much faster. Hopefully the unit will also be more stable too. |
|
03-17-2012, 09:35 PM | #57 | |
Wizard
Posts: 1,964
Karma: 5700925
Join Date: Mar 2012
Location: CA
Device: Kindle Paperwhite
|
Quote:
Oh, and to stay on topic, so far my Kobo Touch is working quite well with this new firmware, and also with the newer Calibre upgrade as well. So far I'm happy. |
|
03-17-2012, 10:49 PM | #58 | |
Addict
Posts: 355
Karma: 289856
Join Date: Oct 2011
Location: Honolulu, Hawaii
Device: Kobo Touch
|
Quote:
To cover your points: 1) It is true they have several devices that require support and development. It may be just me but you seem to assume that there is only one or two development groups that cover multiple platforms. That may be true, but I would think it would be more likely to have teams that focused on certain 'groups'. E.g. Linux based (all Kobo readers), mobile based (Android/iOS/etc.), and desktop/Web-based (Win/MacOS/HTML5?). 2) I don't think they have a single set of source code, unless it is that part that deals with the Kobo servers. All other code appears at this point to be specific to the device. Can you honestly tell us that you believe that the UI and features across all the OSes and devices Kobo supports is that similar? Even between Kobo's own devices the UI and features are not. As you point out it would be cost-prohibitive but from all appearances, that is exactly what Kobo is doing. It may be more likely they have (similar to my comment above) certain 'groups' of source code. 3) Yes, I understand time is required for all those phases. I just feel that there should be some community input in the first phase to avoid any large complaints about new features later. e.g. the 5 thumbnail listing on the HOME page. As a developer you are ultimately developing for the User, management may have it's ideas and push through most of them but if it ends in a low UX users will eventually move on. If you've read these forums for very long you see that happening quite often. Would it not be to your and management's benefit to know what the target audience wants and not just force it on them? Also as a developer you must experience times when you will not make the deadline due to unforseen delays or problems. Do you delay the product further or do you cut out/postpone features till a future update. Kobo I believe has leaned towards the former but seeing as how long it has been since the previous update, have finally decided on releasing minus some planned features like the 'collections'. Yes, 3 months is typical, but for kobo their track record was a bit more frequent. |
|
03-18-2012, 01:04 AM | #59 |
Nameless Being
|
That depends upon your definition of spyware. Ultimately, features like Reading Life and Facebook integration are about collecting marketing data. Some people think of this as spyware, others don't. Even though we don't truly know what is being sent back to Kobo servers, it is probably safe to say that they aren't collecting passwords, credit card numbers, and other personal information unless you explicitly provide it to them (say to buy a book). So it probably isn't spyware in that sense.
|
03-18-2012, 04:23 AM | #60 |
Zealot
Posts: 105
Karma: 37668
Join Date: Feb 2012
Device: Kobo Touch
|
A simple hosts file can prevent the device to connect to google-amalytics.
Unzip the attached file to .kobo directory, eject and unplug - the reader will not be able to send any information to google. (to remove it, you have to do a factory reset) hosts.zip |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Touch Kobo Touch Firmware 1.9.16 | MDK | Kobo Reader | 481 | 03-23-2012 01:23 PM |
Touch Kobo Touch Firmware 1.9.12 | MDK | Kobo Reader | 172 | 02-15-2012 02:56 AM |
Touch Kobo Touch Firmware 1.9.9 | danskmacabre | Kobo Reader | 69 | 08-21-2011 11:47 PM |
Touch Kobo Touch Firmware 1.9.8 | MDK | Kobo Reader | 64 | 08-05-2011 04:59 PM |
Touch Kobo Touch Firmware 1.9.7 | MDK | Kobo Reader | 46 | 07-27-2011 02:14 PM |