Active Topics
-
[HOWTO] Comprehensive Firmware Flashing Guide for N9 (1,580)
to Nokia N9 / N950 by aspergerguy - 12 hrs, 44 mins ago -
Nokia N9-00 Prototype Build S1.12 (RM-680 codename "Dali") (250)
to Nokia N9 / N950 by en0s - 3 days, 9 hrs ago -
[Announce] Maebble - Pebble support for Maemo (118)
to Applications by glo-worm - 3 days, 21 hrs ago -
Possible to flash Leste to eMMC? (6)
to Maemo 7 / Leste by Eri - 4 days, 11 hrs ago - more...
attila77 |
2009-03-22
, 02:57
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#21
|
Comparing shoot'emups with fbreader is apples and oranges. Let me put it another way. Would you rewrite fbreader from scratch just to have autoscrolling ?
|
|
2009-03-22
, 03:35
|
|
Posts: 1,418 |
Thanked: 1,541 times |
Joined on Feb 2008
|
#22
|
Originally Posted by attila77
I do not see why this is the reason for scrolling being impossible in fbreader while being possible in a shoot'em'up. In other words, both apples and oranges have seeds.
Comparing shoot'emups with fbreader is apples and oranges.
Let me put it another way. Would you rewrite fbreader from scratch just to have autoscrolling ?
 |
|
2009-03-22
, 03:56
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#23
|
Originally Posted by fms
You missed the first part of my little equation.
Sorry, but I think you are wrong. There is at least one vertical scroller shoot'em'up game for the tablets and it scrolls the whole screen just fine.
Originally Posted by GeneralAntilles
I said the current hardware combined with FBReader (i.e., FBReader's architecture; i.e., libzlibrary)
Whatever the developer does or does not think, FBReader + our hardware == no autoscrolling.
Originally Posted by fms
You, apparently, missed the first paragraph, too.
What makes you think that the current hardware prevents auto-scrolling?
Originally Posted by GeneralAntilles
I'm not saying it's not possible (I'm not familiar enough with libzlibrary to say whether optimizations would be feasible or worthwhile), but I definitely don't see the developer doing it, and it seems unlikely that anybody else would (or would you like to volunteer to prove me "wrong"?).
Autoscroll can't be implemented cleanly with the current architecture. FBReader's portability is both a blessing and a curse, in this case, it prevents usable autoscrolling (here's a test, turn one full page and watch how long it takes to refresh the screen).
If somebody wanted to work on drop-in replacement renderer for libzlibrary, that might work, but in the end I suspect it'd be a lot easier to implement the UI and functionality niceties that FBReader has on something that's designed to run well (not just run on everything) like liqreader. . . .
__________________
Ryan Abel
Ryan Abel
|
|
2009-03-22
, 05:01
|
|
Posts: 5,795 |
Thanked: 3,151 times |
Joined on Feb 2007
@ Agoura Hills Calif
|
#24
|
Autoscrolling is kinda fun, but it is hardly the must feature depicted above, it seems to me. To use it, you need to develop a new skill: "synchronized thinking".
With synchronized thinking, you can understand a difficult concept at EXACTLY the same speed as an easy one! That's right, "see Spot run" and "e=mc2" can be read with exactly the same speed of thought! Whereas people who mechanically turn pages are admitting that for them, some thoughts take longer than others.
Unfortunately, I haven't mastered synchronized thinking...
With synchronized thinking, you can understand a difficult concept at EXACTLY the same speed as an easy one! That's right, "see Spot run" and "e=mc2" can be read with exactly the same speed of thought! Whereas people who mechanically turn pages are admitting that for them, some thoughts take longer than others.
Unfortunately, I haven't mastered synchronized thinking...
| The Following 7 Users Say Thank You to geneven For This Useful Post: | ||
|
|
2009-03-22
, 11:57
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#25
|
Originally Posted by fms
AFAIK They use completely different video access. Mplayer and most of the games you talk about render through XV (so, no GTK, no universal RGB pixel drawing, no nothing). FBreader, on the other hand, uses regular X with GTK, and in *that* mode, video operations like scrolling are painfully slow (lcuk can tell a story or two on this).
I do not see why this is the reason for scrolling being impossible in fbreader while being possible in a shoot'em'up. In other words, both apples and oranges have seeds.
Could you elaborate on why the autoscroll feature would require a complete rewrite of fbreader? I would like to hear a technical explanation, if at all possible. Thanks.
I'd ask for any better informed person to say if I'm wrong here, as quite some time has passed since I've looked at fbreader innards.
You might also find this thread useful:
http://www.internettablettalk.com/fo...ad.php?t=27206
|
|
2009-03-22
, 13:10
|
|
Posts: 1,418 |
Thanked: 1,541 times |
Joined on Feb 2008
|
#26
|
Originally Posted by attila77
I use GTK rendering when running emulators in windowed mode on the NIT. Yes, the display updates are somewhat slow but they work. And I update the display much, much more often than required by autoscrolling.
FBreader, on the other hand, uses regular X with GTK, and in *that* mode, video operations like scrolling are painfully slow (lcuk can tell a story or two on this).
So you'd have to do a serious rewrite to adapt everything to XV style operations, redo the whole interface, adapt font rendering to YUV, etc, at which point you're closer to a rewrite than a patch and it would be very maemo/linux specific.
But, again, GTK should be enough for some light scrolling. After all, even that goddamn RSS widget scrolls (and has to be disabled to save battery).
Now, Lcuk uses YUV because the current version of XV extension does not let him use other modes. And he uses XV to stay compatible with the desktop that does support /dev/fb0 but does not support NIT-specific hardware blitting.
| The Following User Says Thank You to fms For This Useful Post: | ||
|
|
2009-03-22
, 15:04
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#27
|
Originally Posted by fms
How smooth are talking about here ? At portrait 1 minute / page (not a stellar reading speed) if you update by the pixel, that's roughly 15fps (not too battery friendly either), easily more if you use a larger font (=read quicker).
I use GTK rendering when running emulators in windowed mode on the NIT. Yes, the display updates are somewhat slow but they work. And I update the display much, much more often than required by autoscrolling.
|
|
2009-03-23
, 11:22
|
|
Posts: 1,418 |
Thanked: 1,541 times |
Joined on Feb 2008
|
#28
|
Originally Posted by attila77
I manage something like 18-22fps.
How smooth are talking about here ? At portrait 1 minute / page (not a stellar reading speed) if you update by the pixel, that's roughly 15fps (not too battery friendly either), easily more if you use a larger font (=read quicker).
|
|
2009-03-23
, 11:38
|
|
Posts: 187 |
Thanked: 23 times |
Joined on Aug 2007
|
#29
|
I was excited about this program reading archive files, zip etc but guess I misunderstood. I've some ebooks that consist of like 100 individual html files (each chapter) .... was thinking I could zip them up and view them as one book but guess not? 
4 books, 2 split by chapter annd 2 as 1 long html file. I tried out this new fbreader cuz browser choked on the large files; ironically I ended up really liking this fbreader but now have to use both.
4 books, 2 split by chapter annd 2 as 1 long html file. I tried out this new fbreader cuz browser choked on the large files; ironically I ended up really liking this fbreader but now have to use both.
|
|
2009-03-23
, 15:26
|
|
Posts: 1,101 |
Thanked: 1,185 times |
Joined on Aug 2008
@ Spain
|
#30
|
Originally Posted by geneven
Obviously it depends on what you are reading. Romantic novels doesn't seem to have concepts too though.
Autoscrolling is kinda fun, but it is hardly the must feature depicted above, it seems to me. To use it, you need to develop a new skill: "synchronized thinking".
With synchronized thinking, you can understand a difficult concept at EXACTLY the same speed as an easy one! That's right, "see Spot run" and "e=mc2" can be read with exactly the same speed of thought! Whereas people who mechanically turn pages are admitting that for them, some thoughts take longer than others.
Unfortunately, I haven't mastered synchronized thinking...
Physic texts, on the other hand....