![]() |
#31 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 196
Karma: 1199690
Join Date: Apr 2011
Location: Massachusetts, USA
Device: Kobo Touch (gifted to a friend), Sony PRS-T2, iPad mini
|
I would like to be able assign tags to books and to import the tags from Calibre.
I want to be able to sort the books by series - I don't think that title and author is enough, especially if you read (as I do) a lot of books that are part of a series. To be able to see the series name under each book is nice, but being able to sort by it It would be great. I want to be able to choose what my Touch displays on "My home" screen. I never connect through Wi-fi and I never buy books directly from Touch. Therefore, I want to be able to choose "My home" screen to display features that are useful for me and make my reading experience better. |
![]() |
![]() |
![]() |
#32 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 4,466
Karma: 6900052
Join Date: Dec 2009
Location: The Heart of Texas
Device: Boox Note2, AuraHD, PDA,
|
Searching pretty much requires that you have a specific thing you are looking for.
Browsing is similar to searching but with no specific object as your goal. If I always know the next book I wish to read, then all I would need is a search tool. Most of the time I have no particular book in mind and want to browse through defined listings of books, to see what might meet my needs and mood. Being able to browse through a listing of all the "Mystery" ebooks I have on hand, or all the "SciFi", or all the "Fantasy", or all the "PolyTicks", or all the "Comedy", or all the ebooks in any of over 50 catagories, is not something that you can replace with a search function. Luck; Ken |
![]() |
![]() |
![]() |
#33 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Yep, we already have two library listing styles (small covers and details, large covers no details), two sleep screen styles, two different epub readers. Two home screen styles should not be a problem.
|
![]() |
![]() |
![]() |
#34 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,847
Karma: 3212428
Join Date: Jun 2011
Device: iphone stanza, kobo touch,ASUS TF300,KOBO GLO, Kobo Aura HD, Kobo Mini
|
Quote:
Usually works better than the original unless the hardware changes. regards JAck |
|
![]() |
![]() |
![]() |
#35 |
Always been the caretaker
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 479
Karma: 1406369
Join Date: Dec 2012
Location: Canada
Device: Aura H2O, PW2
|
Nothing new to contribute, but if there is a chance the right people at Kobo are reading, I'd just like to echo a couple of suggestions:
Just polish up and fix the current firmware. An option for full screen mode or something very close to it. It seems many people would like to optimize their reading space, especially Aura owners. Do I really need my device to display that it's sleeping or powered off? Yeah, I know that already, Kobo. It would look so much nicer if having the book cover uncluttered with unnecessary info. when not in use. |
![]() |
![]() |
![]() |
#36 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 45,544
Karma: 168929301
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
As for recreating shelves, I don't use any shelves. I use search against the database to locate files in a very simple directory structure on the ereader. For me, that removes any need for shelves. My original attempts at using shelves ended with books on 3 or 4 shelves and several hundred shelves which was a pain to maintain and even more of a pain to restore after a factory reset. So now I just use the search function. If I could specify the search criteria such as author, title, etc., it would be an improvement but that would add considerably to the complexity of the search interface -- a build your own SQL query interface is pretty unlikely to be delivered. Unlike you, most of my books use a Latin alphabet and for those few that are not, I use Latin characters for the metadata so search works for me. A pain in some cases but since I'm running most of the ebooks I get through Sigil in any event, not that much added trouble. Regards, David |
|
![]() |
![]() |
![]() |
#37 |
doofus
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,543
Karma: 13089041
Join Date: Sep 2010
Device: Kobo Libra 2, Kindle Voyage
|
IMO, they need to a) redesign the reading screen so they do not have huge space wasted on top and bottom ; b) total user control of margin and line line spacing ; c) fix HTML/ rendering annoyances, like the widow/orphan bug.
Until they get these right, nothing else matters to me and I will not buy a kobo. |
![]() |
![]() |
![]() |
#38 |
One
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 107
Karma: 137282
Join Date: Oct 2009
Device: Sony, Kindle,Pocketbook, Nook...
|
DNSBI don't see that we have to disagree at all.
It is only if you use an approach of either one or another, I think we should strive for both. I like smaller margins, smaller line height- let me use settings at their minimum- you can use them at your convenience. You like using search, I like it too. You ended up not even using shelves. I like browsing by my authors, the thing is that neither search, nor shelves give me the opportunity to do-is to have subsets, multi level organization. File manager gives that opportunity- why not have a choice. Database is a programming issue and programming decision, it is huge, reader takes long to generate it and update it, so- we need to be able to choose when and how we deal with it- when we have time overnight- plug it in and let it chug along, when we travel- put a card in, have file manager to see our structured files and be ready in minutes. We should not choose either your way or mine, we should have both. My control over my reader screen is important to me- let me choose what and when appears there, you'd like to see suggestions, live updates - fine, have it. Those choices are not something that is impossible, it is quite possible and achievable right now, why not insist that devices we buy with our own money give us those choices? |
![]() |
![]() |
![]() |
#39 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,847
Karma: 3212428
Join Date: Jun 2011
Device: iphone stanza, kobo touch,ASUS TF300,KOBO GLO, Kobo Aura HD, Kobo Mini
|
Quote:
2)furthers the enjoyment of the user whilst reading, 3) helps to organize the books or menu in a more logical intuitive way that customizes our reading experience on an unprecedented personal level... Again ramping up loyalty by simple enjoyment. regards JAck |
|
![]() |
![]() |
![]() |
#40 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 4,812
Karma: 26912940
Join Date: Apr 2010
Device: sony PRS-T1 and T3, Kobo Mini and Aura HD, Tablet
|
Quote:
I have never seen such a controversy over the Sony or Amazon use of screen space and menus in the Sony and Kindle forums. The Sony has had a menu bar on the bottom, not disimiliar to the Kobo one, and nobody seemed to take offense at it. The Kindle had a menu bar, then they hid it, had location numbers and changed to page numbers etc. which caused some dsicontent, but nothing like the sheer outrage being generated by Kobo. Of course were and are far more robust and functional in terms of basic reading and navigation although sorting on the kindle three at least was a tad bizarre to me (most kindle owners seemed fine with it). I am all for choice, but I think I value reliabilty and stabilty more. Sure give those who want features the features, I won't be upset by there presence. Just don't keep randomly deleting basic functions to add those features. Add another screen or menu level, like the other software based systems. When I bought my Mini it had a functional back button. Now it doesn't although I have glimpsed it twice before it was covered up by the menu bar. Surely if they were going to delete the back button they should have deleted the code that displayed it instead of just displaying it and displaying something else on top of it. This seems to be very sloppy programming practice, that should not be condoned by Kobo management. Then they take away the ability to have a black menu bar, which I have never used, but many like and no one seems to know why. It is like a crap shoot, almost Pavlovian in the sequence of good ereader, bad ereader, better in one function ereader one day , and worse than ever ereader the next (the book I was reading opened 12 page turns back today the forth time opening it after upgrading to 2.61, I was sort of used to 1-4 page turns, and I do not have any margins). Then there is the kepub epub thing. What do they hope to gain by that I wonder. Saving some money on ADE. I don't think so as they must pay it anyway if they are selling access to both formats together. Oh well sorry for ranting like a lunatic and I hope I haven't thrown the thread more off topic than it already was. Good idea for a thread BTW. Helen |
|
![]() |
![]() |
![]() |
#41 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,847
Karma: 3212428
Join Date: Jun 2011
Device: iphone stanza, kobo touch,ASUS TF300,KOBO GLO, Kobo Aura HD, Kobo Mini
|
Quote:
Regards Jack |
|
![]() |
![]() |
![]() |
#42 | |
GranPohbah-Fezzes r cool!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,056
Karma: 3151024
Join Date: Jul 2010
Device: Nook STRs, Kobo Touch, Kobo Glo
|
Ken,
Quote:
Granted, this will not speed up the firmware in it's glacial processing of new books. I cannot fathom why it is so slow unless there is some very sloppy database programming or far too much data is being unnecessarily stored and manipulated per title -like moving data around rather than pointers, etc. PS. Could you stop using hard breaks in your posts? The nearly blank lines with only a few words following each post line are driving me nuts like a badly formatted ebook. Last edited by TechniSol; 06-09-2013 at 09:11 PM. |
|
![]() |
![]() |
![]() |
#43 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 45,544
Karma: 168929301
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
Regards, David |
|
![]() |
![]() |
![]() |
#44 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 4,812
Karma: 26912940
Join Date: Apr 2010
Device: sony PRS-T1 and T3, Kobo Mini and Aura HD, Tablet
|
Quote:
Aura process 1000 new books pretty fast, actually faster than My Sony, one of the few things it does better. Mini maybe a minute or two, still faster than the Sony. Is this glacial processing of new books a new thing? Helen |
|
![]() |
![]() |
![]() |
#45 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 45,544
Karma: 168929301
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
Line and margin spacing? Give the user total control and take it away from the ebook publishers who have an idea (vague and misdirected though it might be) as to what they want the ebook to look like. Widows and orphans are not a bug. They were a part of the CSS 2 specification and Adobe was simply following that standard when they included widow/orphan support with a default of 2. And please note that Adobe not Kobo supply the Adobe Reader Mobile SDK. To quote from "Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification": Code:
13.3.2 Breaks inside elements: 'orphans', 'widows' 'orphans' Value: <integer> | inherit Initial: 2 Applies to: block container elements Inherited: yes Percentages: N/A Media: visual, paged Computed value: as specified 'widows' Value: <integer> | inherit Initial: 2 Applies to: block container elements Inherited: yes Percentages: N/A Media: visual, paged Computed value: as specified The 'orphans' property specifies the minimum number of lines in a block container that must be left at the bottom of a page. The 'widows' property specifies the minimum number of lines in a block container that must be left at the top of a page. Examples of how they are used to control page breaks are given below. Only positive values are allowed. David |
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Translate Kobo Touch User Interface ( UI ) | choper81 | Kobo Reader | 0 | 04-23-2012 05:44 PM |
Rethinking the user interface | fesja | Calibre | 98 | 02-10-2012 02:02 AM |
User Interface settings | Ponderstibbons | Calibre | 1 | 09-05-2010 01:16 PM |
iLiad User interface programming | eth777 | iRex Developer's Corner | 3 | 12-23-2007 05:58 AM |
iLiad Interface Design | nathany | iRex Developer's Corner | 6 | 09-17-2007 02:05 PM |