<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 11, 2013 at 10:01 PM, Gary Holmlund <span dir="ltr"><<a href="mailto:gary.holmlund@gmail.com" target="_blank">gary.holmlund@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have been watching smart phones and tablets rise in sales as desktop/laptop computers are not selling very well. I think it is time to think about BibleTime for mobile computers.<br>
<br>
Qt 5.1 will officially support Android and IOS, if your program is written in Qt Quick/QML. Because QML is quite different from Qt widgets, this requires a completely new frontend.<br>
<br>
I am willing to put in the effort to make this happen for Android. I am not asking for your help, unless you want to. :) I would appreciate guidance along the way.<br></blockquote><div><br></div><div style>I think this is a marvelous idea. The only other Android Sword app that's out there branches off of JSword because of Android's apparently better support for Java apps than for C libraries.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
To show you that I am serious, I have already created a prototype running on linux using Qt 5.0.1. This prototype just has basic bible/commentary windows, verse changing, module changing. The windows can be arranged tabbed, horizontal, vertical, and auto-tiled. It has many features and much usability yet to be worked on. Please look at this screen capture:<br>
<br>
<a href="http://sourcearchives.com/downloads/bibletime-mobile.webm" target="_blank">http://sourcearchives.com/<u></u>downloads/bibletime-mobile.<u></u>webm</a><br>
<br>
The prototype is on a local git branch and integrated with the BibleTime cmake build using the BIBLETIME_FRONTEND mechanism already defined in BTSourceFileList.txt. You can either build BibleTime or BibleTimeMobile.<br></blockquote>
<div><br></div><div style>Part of the process should be a sharp delineation between the frontend code and the backend code. This is an effort we've talked about "in theory" for a while in order to improve the ability to generate new front ends easily. Doing so would permit us to have a structure something like src/backend and src/frontend/desktop, src/frontend/phone src/frontend/tablet or whatever.</div>
<div style><br></div><div style>I'm a fan of it, and your prototype looks like a good start!</div><div style><br></div><div style>--Greg</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
What do you think?<br>
<br>
Gary<br>
<br>
______________________________<u></u>_________________<br>
bt-devel mailing list<br>
<a href="mailto:bt-devel@crosswire.org" target="_blank">bt-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/bt-devel" target="_blank">http://www.crosswire.org/<u></u>mailman/listinfo/bt-devel</a><br>
</blockquote></div><br></div></div>