Touch Kobo Touch future firmware feature request thread

[somnolik]

Did anybody already ask for landscape mode?
Seriously though, the option to rotate 90 degrees (in either direction) would be very helpful, and the present inability to do so renders the cbr+cbz engine rather useless.

[readingglasses]

Someone said elsewhere, PREPEND HTTP:// (and possibly https://) to browser addresses.

having to type that to get anywhere is needless, especially when no protocol except http seems to be supported by the browser and no protocol except http and https is likely needed on the web today, without streaming media.


again, internationalization/font selection support on the browser. We're just talking text here and the internet is multilingual.

support for downloading webpages and links onto the device, not just books. does anyone know if this works yet?

[Cottser]

It's obviously been brought up several times in this thread, but I'd like to chime in and express my interest in a search feature within books. When comparing to other readers, this was the one feature I really wanted that the KT doesn't (yet) have.

And yes, having to enter http:// annoyed me when using the web browser. I know it's "experimental", but... yeah.

[PeterT]

In the browser add "shortcuts" for certain well known components of URLs such as

• http://
• https://
• .com
• .org

[bibahbuzemann]

Originally Posted by readingglasses

Just be sure to update to the latest firmware. Don't judge a virtual book by its last incarnation ...but by its latest.

You are absolutly right to assume that Kobo developers will tell you they are solving all those problems people seem to be having with it.

And, piecemeal, the one guy from Kobo keeping an eye on this forum, has indeed done a lot to keep your hopes up(perhaps he has just a little bit of german salesman DNA in there).

Back to the firmware request:

It is the "make or break" of any ereading device, IMHO:
SEARCHING within, at least, the the current text.
BOOKMARKING.

[bibahbuzemann]

At high school programming class 101 the first thing we learnd was to make the screen display "HELLO WORLD". Next came lists, arrays and I forgot what next.

But then we spent the whole first semester learning how best to sort(implying searching), index...bla..bla.

As long as I'm in the Kobo part of this forum, I gotta assume, ain't nobody ever programmed nothing.

It's SO f++k ing easy I'll do it for free! In a week or two. Gi'me a Kobo and the source code(no big deal, it ain't even yours), I'll do it.

[frankieGom]

Originally Posted by bibahbuzemann

At high school programming class 101 the first thing we learnd was to make the screen display "HELLO WORLD". Next came lists, arrays and I forgot what next.

But then we spent the whole first semester learning how best to sort(implying searching), index...bla..bla.

As long as I'm in the Kobo part of this forum, I gotta assume, ain't nobody ever programmed nothing.

It's SO f++k ing easy I'll do it for free! In a week or two. Gi'me a Kobo and the source code(no big deal, it ain't even yours), I'll do it.

Here you go: https://github.com/kobolabs/Kobo-Reader

[singularity]

Originally Posted by bibahbuzemann

At high school programming class 101 the first thing we learnd was to make the screen display "HELLO WORLD". Next came lists, arrays and I forgot what next.

But then we spent the whole first semester learning how best to sort(implying searching), index...bla..bla.

As long as I'm in the Kobo part of this forum, I gotta assume, ain't nobody ever programmed nothing.

It's SO f++k ing easy I'll do it for free! In a week or two. Gi'me a Kobo and the source code(no big deal, it ain't even yours), I'll do it.

I don't want to offend anyone, but looking at this board leaves me with the impression that the SW has some quality problems and the response to customer feature requests is slow. I'm embedded device programmer working on high reliability SW for big bad clients and if I was making so many bugs in already released product and delaying features I would be fired. I guess the reason is tight budget/schedule. Best for Kobo is to make their device fully open and let everyone contribute. Would be cool!

[readingglasses]

For an opinion on this issue of open source see another programmer who hacked a bit at the kobo wifi.

http://blog.ringerc.id.au/2011/07/no...kobo.html#more

[readingglasses]

Originally Posted by frankieGom

Here you go: https://github.com/kobolabs/Kobo-Reader

That doesn't contain a source code for the most functional parts of the actual ereading that the ereader does. It has everything else (networking, fonts, device driver). So, the source code is only partially GPL linux stuff and the code that does things you care about and has the problems, the actual kobo work, is closed source.

[frankieGom]

Originally Posted by readingglasses

That doesn't contain a source code for the most functional parts of the actual ereading that the ereader does. It has everything else (networking, fonts, device driver). So, the source code is only partially GPL linux stuff and the code that does things you care about and has the problems, the actual kobo work, is closed source.

And here I was hoping that bibahbuzemann would give us all those neat features that are missing...
Too bad!

But more seriously, if this code really contains all the HW related stuff it should be fairly simple for half a programmer to patch it together with open source ereader software and give us a choive... Best would be to use a kernel that would boot from the microSD to leave the original FW unscathed.

[volpo]

Here is another wild request for a feature:

When in sleep mode pressing the home button will wake it up. I know it could be pressed accidentally so let's make this a toggle also.

-V-

[Cottser]

A couple more ideas…

Instapaper integration - if the iOS apps have it, why not? If done well, this would be amazing.

Ability to see percent progress (and other stats?) in book listings, and while reading a book without having to bring up Reading Stats or putting the Kobo to sleep (with covers enabled). Related: it would also be nice if there were a shelf/section to display books currently in progress, versus books that are finished or not "opened". Currently I'm using the Shortlist as a "books in progress" area which works OK but I'd like something more integrated. As others have mentioned, "Mark as Finished" should do just that.

Also, I noticed definite margin and possible font size discrepancies between Kobo ePUBs and library/side-loaded ePUBs, they should display the same.

[evrdazed]

I haven't read through the whole thread, so I apologize if some of these are duplicates:

-a clock at the top, either on all the time, or when I bring up the menu (so I can see what time it is when I am lost in a book)
-search function (within the book)
-ability to take notes
-export out the highlights
-another game, please let me play crosswords, that would be amazing.

[bibahbuzemann]

Originally Posted by frankieGom

Here you go: https://github.com/kobolabs/Kobo-Reader

I'll be straight on it, but Kobo hasn't sent me the real source code and the KoboTouch yet. In fact, als of tonight, they haven't even asked where to send it.