[bt-devel] Bible Application for Mobile Devices

[Gary Holmlund]

The default for Text.textFormat is Text.AutoText which supports the HTML
text. Also, I inlined the css so it was not external.

Gary


On 08/26/2013 11:48 AM, ????? ?????? wrote:
>
> You need to set explicitly Text.textFormat to Text.RichText. And
> another reason why it is not styled is: *.css file can not be loaded
> (as webmedic mention here you would set full path to it)  or style
> sheet contain constructions that can not be resolved by Qt engine.
> Default BibleTime template contain such constructions...
>
> I get it working in my first qml prototype
> mini_repository/platforms/qml/btmini/main.qml with modified template
> file ./src/display-templates/Basic-Mini.tmpl
>
> 26.08.2013 21:57 ???????????? "Gary Holmlund" <gary.holmlund at gmail.com
> <mailto:gary.holmlund at gmail.com>> ???????:
>
>
>     The QML "Text" object supports HTML 3.2 but no css. I did try out
>     using "Text instead of "WebView" in the Mobile code. As expected,
>     I did see the text, but it is no formatted in any way by the css.
>
>     Gary
>
>     On 8/26/2013 7:30 AM, webmedic wrote:
>>
>>     I have been able to load external resources by giving the entire
>>     path to the local file.
>>
>>     On Aug 26, 2013 2:52 AM, "????? ??????" <kostyamaslyuk at gmail.com
>>     <mailto:kostyamaslyuk at gmail.com>> wrote:
>>
>>         Sorry for confusion. Qt call html format they support as
>>         RichText as opposed to PlainText format. So i'm not about RTF
>>         but HTML that Qt supports internally.
>>
>>         I would mention again that i did not managed to load external
>>         resources with it (QTextDocument: neither css or images) and
>>         it does not support some css features. There is already made
>>         BibleTime template that works with Qt-Html at Mini repository.
>>
>>
>>         2013/8/26 Greg Hellings <greg.hellings at gmail.com
>>         <mailto:greg.hellings at gmail.com>>
>>
>>
>>
>>
>>             On Sun, Aug 25, 2013 at 11:42 PM, Gary Holmlund
>>             <gary.holmlund at gmail.com
>>             <mailto:gary.holmlund at gmail.com>> wrote:
>>
>>                 ?????,
>>
>>                 To use RichText we would have to have a different
>>                 renderer. I am not sure I want to make this now. I
>>                 still hope that Qt 5.2 will support WebKit on
>>                 Android. You have had a rich text renderer in the
>>                 past for Mini. Was it hard to make? We can do it at a
>>                 later date if we decide it is the only choice.
>>
>>
>>             The engine supports RTF output, FYI. FMT_RTF should get
>>             you that. It's only used in BibleCS (aka The SWORD
>>             Project for Windows). So creating the renderer shouldn't
>>             be /too/ difficult.
>>
>>             --Greg
>>              
>>
>>
>>                 Developing on Qt 4.8 does not seem like a good choice
>>                 since the QML code (Quick 1.0) is depreciated.
>>
>>                 I think that developing Quick 2 on desktops is the
>>                 best choice for now.
>>
>>                 I am going to look at a single window mode for
>>                 smaller displays. If you wish to work on the install
>>                 manager, I will avoid changes in that area.
>>
>>                 Gary
>>
>>
>>                  
>>                 On 08/23/2013 05:06 AM, ????? ?????? wrote:
>>>                 It think we would use Qt RichText for a while. It is
>>>                 used in Mini for a long time and WebKit is an
>>>                 runtime option on platforms that supports it. I know
>>>                 that it is not full functional but it was enough.
>>>                 Or develop on desktops, i simply do not know what a
>>>                 features supply WebKit that Qt RichText haven't
>>>                 (except images, proper css handling).
>>>
>>>                 Necessitas project that support Qt 4.8.2 on Android
>>>                 have WebKit support but have QtQuick1 modules only.
>>>
>>>
>>>                 2013/8/23 Gary Holmlund <gary.holmlund at gmail.com
>>>                 <mailto:gary.holmlund at gmail.com>>
>>>
>>>                     On 08/22/2013 07:25 AM, ????? ?????? wrote:
>>>
>>>                         I have tried Mobile on Android, but without
>>>                         WebKit support in Qt, it does not makes
>>>                         sense (fails loading qml file). I also fixed
>>>                         one issue, related to comparison between
>>>                         translated and non-translated strings.
>>>
>>>                         Related to WebKit support on Android,
>>>                         https://bugreports.qt-project.org/browse/QTBUG-32093
>>>
>>>                     I had missed the fact that WebView did not come
>>>                     with the Qt 5.1 Android port. I can see this is
>>>                     on the list they want to do for the next Qt
>>>                     release, but it is not guaranteed to be in Qt 5.2
>>>
>>>                     I don't know that we have a good choice now. We
>>>                     could:
>>>
>>>                      1. Continue on developing a QML version on
>>>                     linux or windows and hope the Qt 5.2 (or later)
>>>                     has the WebView for Android.  The QML "Text"
>>>                     type supports html and we may be able to use it
>>>                     in the sort term and make an Android version.
>>>
>>>                      2. Wait on the QML version and put more effort
>>>                     into the widget version of Mini.
>>>
>>>                     What are your thoughts?
>>>
>>>
>>>                     Gary
>>>
>>>
>>>
>>>                     _______________________________________________
>>>                     bt-devel mailing list
>>>                     bt-devel at crosswire.org
>>>                     <mailto:bt-devel at crosswire.org>
>>>                     http://www.crosswire.org/mailman/listinfo/bt-devel
>>>
>>>
>>>
>>>
>>>                 _______________________________________________
>>>                 bt-devel mailing list
>>>                 bt-devel at crosswire.org <mailto:bt-devel at crosswire.org>
>>>                 http://www.crosswire.org/mailman/listinfo/bt-devel
>>
>>
>>                 _______________________________________________
>>                 bt-devel mailing list
>>                 bt-devel at crosswire.org <mailto:bt-devel at crosswire.org>
>>                 http://www.crosswire.org/mailman/listinfo/bt-devel
>>
>>
>>
>>             _______________________________________________
>>             bt-devel mailing list
>>             bt-devel at crosswire.org <mailto:bt-devel at crosswire.org>
>>             http://www.crosswire.org/mailman/listinfo/bt-devel
>>
>>
>>
>>         _______________________________________________
>>         bt-devel mailing list
>>         bt-devel at crosswire.org <mailto:bt-devel at crosswire.org>
>>         http://www.crosswire.org/mailman/listinfo/bt-devel
>>
>>
>>
>>     _______________________________________________
>>     bt-devel mailing list
>>     bt-devel at crosswire.org <mailto:bt-devel at crosswire.org>
>>     http://www.crosswire.org/mailman/listinfo/bt-devel
>
>
>     _______________________________________________
>     bt-devel mailing list
>     bt-devel at crosswire.org <mailto:bt-devel at crosswire.org>
>     http://www.crosswire.org/mailman/listinfo/bt-devel
>
>
>
> _______________________________________________
> 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/20130826/4c8dc3f4/attachment-0001.html>