Bible App for Maemo 5 Device(s) - Page 7 - maemo.org

Active Topics

Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 12 hrs ago
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 13 hrs ago
Maemo repository (3)
to Community by torsen - 2 days, 5 hrs ago
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 2 hrs ago
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 9 hrs ago
more...

Page 7 of 55

Thread Tools

joshn53	2009-10-09 , 14:17
Posts: 111 \| Thanked: 80 times \| Joined on Oct 2009	#61

Originally Posted by ARJWright

Neither BibleTime or Rapier's front ends are conductive to good reading or cusory studying. For what ever port is made, the front end should probably be redesigned (I have wireframes somewhere) and done in Qt for best future proofing.http://talk.maemo.org/showthread.php?t=32618

I couldn't agree more. I've got a UI design in mind, but haven't prototyped anything. I've considered prototyping in desktop QT first, then porting to maemo.

Quote & Reply |

joshn53	2009-10-09 , 16:12
Posts: 111 \| Thanked: 80 times \| Joined on Oct 2009	#62

One hiccup: I've been hoping to have the "infinite scroll" effect for the actual Bible text itself, but QT doesn't really have good facilities for this - QAbstractScrollArea (which is the base class that the hildon finger scrolling is tied into) requires a defined height. Thoughts?

Quote & Reply |

	Flandry	2009-10-09 , 16:31
	Posts: 1,559 \| Thanked: 1,786 times \| Joined on Oct 2009 @ Boston	#63

Wait, how is the height less defined with the Bible text than it is with a random Web page?

Quote & Reply |

Hogwash	2009-10-09 , 16:33
Posts: 369 \| Thanked: 191 times \| Joined on Sep 2009 @ Virginia	#64

Originally Posted by pamadio

Be sure to test searching texts before deciding to get rid of clucene.

For sure. Dropping the clucene dependency is not something I consider lightly, I assure you. I will thoroughly test the impact of its absence.

Then some sound judgement needs to be leveled at the front end. Do we port existing code (like Rapier), or - in the light of recent Qt4.6 revelations - bite the bullet and make some new design decisions?

Quote & Reply |

	ARJWright	2009-10-09 , 17:58
	Posts: 861 \| Thanked: 734 times \| Joined on Jan 2008 @ Nomadic	#65

Originally Posted by joshn53

I couldn't agree more. I've got a UI design in mind, but haven't prototyped anything. I've considered prototyping in desktop QT first, then porting to maemo.

I've got a few UI designs, use em if you want:
http://mobileministrymagazine.com/20...cept-ui-1.html
Addition: http://mobileministrymagazine.com/20...le-widget.html

__________________

antoinerjwright.com | Mobile Ministry Magazine

Last edited by ARJWright; 2009-10-11 at 16:17.

Quote & Reply |

joshn53	2009-10-09 , 18:17
Posts: 111 \| Thanked: 80 times \| Joined on Oct 2009	#66

Originally Posted by Flandry

Wait, how is the height less defined with the Bible text than it is with a random Web page?

Because of the infinite scroll. The idea with infinite scroll is that, say, you select a verse in the middle of Matthew, but you could scroll continuously all the way to Acts without stopping if you wanted to. For me, having breaks between chapters is unintuitive and a pain.

Quote & Reply |

The Following User Says Thank You to joshn53 For This Useful Post:
buurmas

joshn53	2009-10-09 , 18:18
Posts: 111 \| Thanked: 80 times \| Joined on Oct 2009	#67

Originally Posted by ARJWright

I've got a few UI designs, use em if you want:
http://mobileministrymagazine.com/20...cept-ui-1.html

A lot of the basic concepts are what I'm thinking, though I'm planning that it will be much simpler, at least to start with.

Quote & Reply |

	Flandry	2009-10-09 , 18:19
	Posts: 1,559 \| Thanked: 1,786 times \| Joined on Oct 2009 @ Boston	#68

Re: scroll Ok, so the problem is you want to have kinetic scrolling, but need to also dynamically load books as you come to them. Right?

Re:Concept wireframes Nice. So you don't see side-by-side comparative display as part of ideal reader on a small display? Would you on a larger screen?