[bt-devel] Bible Application for Mobile Devices

[Костя Маслюк]

>
> > I will try to build Mobile under Android, currently without cmake
> > scripts but pro.
> > Install manager is that what i would make. I think utility for
> > managing background tasks should be prior.
> The current install manager is installing in the background in one
> thread. This is all done at the end after modules to install are
> selected. The progress is shown as it installs.
>
> this is what i wrote in my todo on this matter:
    centralized parallel processing:
        get data from sword
        install a module
        refresh remote sources
        build search index
        maybe backend reloading
        ability for blocking execution (e.g. first text entry)
        make this suitable for main repo
        should know what is current view (text/install), current text,
probably via signals/slots
        i'd prefer to make it in c++ layer

I decide to maximally unload main thread, and keep it from blocking as much
as possible. Your opinion is very valuable here of course.

Here would be different solutions: leave it decentralized as it is, use
QtConcurency - but las time i implemented it i found it not enough
functional as there is no priority control and (not sure) queue management.


> >
> > For interface design i would like to avoid overlapping and hanging
> > elements, it just makes feeling of some kind of a heap, overloads
> > interface. Its better to make sliding panels, shifting and snapping of
> > interface elements, those in my opinion makes feel order and logic.
> > Just a mention, i understand that it is early variant of interface.
> Please give a more complete description of each user interface before
> implementing them. I think we should agree on them before implementation.
>
> Complete description is difficult task. For the final implementation we
should agree on each element, but this should not be braking factor for
development.

Talking of your Install manager, i'd better fill whole screen with it.
Pop-up menu - would be, but i realize that there should be something more
serious, maybe side navigation (like facebook/evernote). And avoid folding
because it makes user's way longer to desired function (for tiling i'd
placed items on menu top level grouped as square tiles with icons).

> I plan to merge prototype i will made and Mobile code, so i able to
> > make this task also. You will need to test this on your devices as well.
> >
> >
> > Recently i got success with my Bible model in QML. Model with 32000
> > heavy text elements been layout almost smoothly on Android device. If
> > there will be threader data acquisition it will be smooth at all.
> > It would be layout with Chapters instead of verses, what mode do you
> > prefer (continuous reading per chapter, continuous reading per verses,
> > single chapter mode)?
> Does "continuous reading per chapter" mean that multiple chapters are
> loaded at once?


Yes, user would see two chapters at time, at the joint.


> Would the entire book be loaded?


With Qml ListView it is difficult, because without scroll bar it optimizes
display and loads first list entry,
entries you actually see and some entries behind visible area (amount equal
to ListView::cacheBuffer property)


> I think this is
> preferred as long as it is not a performance problem. I do worry about
> the performance?
>
>  "?" => "." I do as well.


> >
> > Also i'm interested in how would be realized BibleTime Magnifier tool
> > on mobile device, will method with JS object work?
> This concerns me. I know how the current desktop version works and the
> QML WebView won't work this way. Javascript can be loaded and ran in the
> WebView, but I don't know how to communicate back to the c++ code. I am
> continuing to look for this answer.
>
> Gary
>
> _______________________________________________
> bt-devel mailing list
> bt-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/bt-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/bt-devel/attachments/20130823/f4942c9c/attachment.html>