[mobile-devel] Bible - Tree navigation for General Books

SonWon sonwon.1 at gmail.com
Mon Feb 28 13:57:25 MST 2011


I really like the grid navigation.  I would like some separation between old
and new chapters but that is because my color vision is poor.  Anyway that
is another item.  Why not do both?

On Mon, Feb 28, 2011 at 3:34 PM, Martin Denham <mjdenham at gmail.com> wrote:

> Thanks for your inputs.
>
> After seeing the Qt interface (nice!) I thought of using something like the
> JSTree JQuery plugin in a WebView to present a tree to the user but I have
> concerns that it might not look very consistent with the rest of the app and
> Android in general.
>
> Then I realised that we already have a (sort of) tree based key in the main
> bible modules i.e. book/chapter/verse, and that was originally presented
> using ListViews on a series of pages.  So my current thought is to do a
> simple series of ListViews drilling down the tree, similarly to the original
> chapter/verse navigation, at least for the first implementation.  Clearly
> this will be consistent with Android and would have been consistent with the
> rest of the app if we had not migrated to grids for bible nav.  For
> consistency I could try using a grid to represent GenBook tree keys but with
> variable size names it would end up a mess.
>
> Martin
>
> On 27 February 2011 21:27, Brian J. Dumont <bdumont at ameritech.net> wrote:
>
>> On 02/25/2011 05:47 PM, Martin Denham wrote:
>> > I have started to think about supporting General Book modules in And
>> > Bible.  General books have Keys that are in a tree structure and I
>> > notice that BibleDesktop and Xiphos use a tree component that can
>> > expand to any number of levels to display the keys/navigation
>> > control/index/list of contents.  With some books this list can be up
>> > to 4 levels deep e.g. Summa Theologica: FS/i/Q1/A1.
>> EarlyFathers goes 6 levels deep in many places; which is the limit of
>> ThML support.  I don't think that OSIS has a limit on tree depth.
>>
>> > The closest thing to a tree that Android provides is an Expandable
>> > List control but that can only have 2 levels.  We could possibly use a
>> > series of lists or spinners but I think that would look fairly poor
>> > but I don't really want to code my own tree control.
>> Have you looked at the "arrows" controllability in Xiphos?  You can go
>> up the tree, down the tree, next element or last element.  For general
>> reading it works quite well.  I think that a series of lists for more
>> complete browsing would be a good alternate route, though.
>>
>> In Christ,
>> Brian
>>
>>
>> -----------------------------------------------------------------------
>> The question is not "Have you accepted Jesus into your heart", but "Has
>> Jesus accepted you into His heart?"; not "have you given your whole
>> life for God", but "has God given His whole life for you"
>>        - Pr Bryan Wolfmueller, 2010
>>
>>
>> _______________________________________________
>> mobile-devel mailing list
>> mobile-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/mobile-devel
>>
>
>
> _______________________________________________
> mobile-devel mailing list
> mobile-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/mobile-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/mobile-devel/attachments/20110228/ef95e752/attachment.html>


More information about the mobile-devel mailing list