[bt-devel] Proposed change for BibleTime
Gary Holmlund
gary.holmlund at gmail.com
Sat Sep 22 08:19:48 MST 2018
I take back the comment about the change being in the backend of
BibleTime. It is in Sword. I don't know what other areas outside of
BibleTime might benefit from it.
Gary
On 09/22/2018 08:10 AM, Gary Holmlund wrote:
>
> I have the functionality I need now by post processing the html. The
> benefit would be cleaner code. The logic would not be in two places if
> the post processing is not needed. Since the code that would have to
> change is in the "backend" of BibleTime I believe it would be specific
> to BibleTime. It is on the list of things I would like to have done,
> but there are several other functionality issues that need to be
> re-implemented because of the changes from QWebEngine to QML Listview
> for display of modules.
>
> Gary
>
>
> On 09/22/2018 12:37 AM, refdoc at gmx.net wrote:
>> Would there be any benefit for you and would this benefit reach
>> further than bibletime if the engine produced the rich text you need?
>>
>> Sent from my mobile. Please forgive shortness, typos and weird
>> autocorrects.
>>
>>
>> -------- Original Message --------
>> Subject: Re: [bt-devel] Proposed change for BibleTime
>> From: Gary Holmlund
>> To: BibleTime development ,Greg Hellings
>> CC:
>>
>>
>> Greg,
>>
>> It is still rendered to html and then sent to QML Text which
>> understands
>> displaying rich text (a subset of html). I am doing some minor post
>> processing of the html before it goes to QML Text. This mostly
>> relates
>> to href tags.
>>
>> Gary
>>
>>
>> On 09/21/2018 08:51 PM, Greg Hellings wrote:
>> > Gary,
>> >
>> > I'm curious - if you're no longer using the QWebEngine widget, what
>> > are you using to format the text? How is it being rendered?
>> >
>> > --Greg
>> > On Fri, Sep 21, 2018 at 8:53 AM Gary Holmlund wrote:
>> >> Jaak,
>> >>
>> >> Thank you for the approval and the suggestions. Perhaps you
>> will have
>> >> other suggestions as this feature develops.
>> >>
>> >> Gary
>> >>
>> >>
>> >> On 09/20/2018 11:47 PM, Jaak Ristioja wrote:
>> >>> Hi, Gary!
>> >>>
>> >>> On 21.09.2018 05:25, Gary Holmlund wrote:
>> >>>> I wanted your approval before going any farther.
>> >>> Thank you for the update. You have my approval. As you have
>> probably
>> >>> already noticed, I'm not currently a (very) active BibleTime
>> developer,
>> >>> and I don't want to get in your way with things. So feel free
>> to go
>> >>> ahead with this feature and merge/rebase to master when ready.
>> >>>
>> >>>
>> >>>> It is implemented for the "read" windows. Most features are
>> implemented.
>> >>>> The main missing features now relate to the context menus
>> (Find, copy,
>> >>>> etc.). These are not a problem to finish. They just require
>> some more
>> >>>> time. Optionally we could eliminate all usage of QWebEngine
>> by working
>> >>>> on the MAG view, the personal commentary editing, the search
>> dialog, the
>> >>>> about dialog, etc.
>> >>> I compiled and ran BibleTime from your mv2 branch, and it
>> looks good.
>> >>> One glitch I noticed is that the BtBibleKeyWidget did not
>> update the
>> >>> location when I scrolled the view using the scrollbar.
>> >>>
>> >>> You might also want to think about improving scrolling with
>> mouse, e.g.
>> >>> change the cursor to a grab cursor when the user can grab the
>> document
>> >>> to scroll, perhaps implement some means for faster scrolling, and
>> >>> perhaps even automatic scrolling. For example, in Okular one
>> can grab
>> >>> the document with the cursor and then scroll it with moving
>> the cursor
>> >>> even up to the top or bottom edge of the screen beyond which
>> scrolling
>> >>> continues so that the cursor appears at the opposite of the
>> screen still
>> >>> holding the grab. Okular also has the nice feature of automatic
>> >>> scrolling, which can be toggled and incrementally acceleratedor
>> >>> decelerated by the Shift+Up or Shift+Down key combinations.
>> >>>
>> >>> J
>> >>>
>> >>> _______________________________________________
>> >>> bt-devel mailing list
>> >>> 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
>> > _______________________________________________
>> > bt-devel mailing list
>> > 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
>>
>>
>>
>> _______________________________________________
>> 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/20180922/21e4d5f0/attachment-0001.html>
More information about the bt-devel
mailing list