View Single Post
Old 01-28-2016, 10:22 AM   #6
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,892
Karma: 6120478
Join Date: Nov 2009
Device: many
As far as I can tell, our usage of QWebElement in BookView is to retrieve layout geometry information from the currently selected position being editing inside BV so that positional scrolling can be controlled independent of the user needing to move the scroll bars. I will have to look into how to use javascript to get geometry information from the layout engine. I did not know that was doable.

Thanks,

KevinH

Quote:
Originally Posted by kovidgoyal View Post
@DiapDealer Python 3.5 is built with VS 2015, so if you are willing to switch to that, you dont need to do any work. In any case, if you wish to peruse my fork, feel free -- it can be found in my github profile.

@KevinH: Most QWebElement usages can be replaced (with a bit of work) by pure javascript. As for web inspector, that exists in QWebEngine, although in an insecure form. See https://bugreports.qt.io/browse/QTBUG-50725
KevinH is online now   Reply With Quote