It seems like such a big step backwards to me... Its almost ...
like going back to WINDOWS!!! Ah!
Perhaps most people will not notice until 5.6 is released, and it is too
late to complain. Hopefully the few now can convince them to continue to
support it in 5.6 after a
Le 11/10/2015 01:04, Moviga Technologies a écrit :
>
>
> OK... that sort of pops my balloon of excitement... :(
Read that too:
http://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/828663-qt-5-6-drops-webkit-qt-qml-uses-less-memory-other-forthcoming-features
https://github.com/O
OK... that sort of pops my balloon of excitement... :(
--
___
Gambas-user mailing list
Gambas-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gambas-us
Le 10/10/2015 20:12, Moviga Technologies a écrit :
>
>
> That makes me want to continue working on my apps that depend on WebView
> with new-found motivation again :)
>
> Hurray!
As I said, in QT 5.4 (which I use at the moment), the new QtWebEngine
classes that replace QtWebKit classes do not sup
That makes me want to continue working on my apps that depend on WebView
with new-found motivation again :)
Hurray!
--
___
Gambas-user mailing list
Gambas-user@lists.sourcef
Good (old) news! I found this article[0] from 2013, and from the sound
of it, all will be well :)
"Qt WebKit works fine right now, and will continue to do so in the years
to come." (2013)
"For the Qt Quick WebView element, we can most likely provide a close to
100% compatible API."
[0]:https:
Oh! OK, wow! Then I am surely hoping with you! It is such a central
component that I'd hate to lose
--
___
Gambas-user mailing list
Gambas-user@lists.sourceforge.net
https
Le 08/10/2015 13:21, Moviga Technologies a écrit :
> Hello, and thanks for the reply!
> I suppose it will be replaced with QtWebEngine? I see that it at least
> has this method
>
> void RUNJAVASCRIPT [1](string _script_, variant _callback_)
>
> so I guess .Eval() will still work, no? Which means we
Hello, and thanks for the reply!
I suppose it will be replaced with QtWebEngine? I see that it at least
has this method
void RUNJAVASCRIPT [1](string _script_, variant _callback_)
so I guess .Eval() will still work, no? Which means we can still
manipulate the DOM, and use it as a texteditor?
Le 07/10/2015 11:07, Moviga Technologies a écrit :
>
>
> What will happen when QT discontinues QtWebkit? Will Gambas lose the
> qt.webkit component for QT5? Will there be any possibility for making an
> alternative webview component for Gambas?
WebKit has already been deprecated. I'm waiting for t
What will happen when QT discontinues QtWebkit? Will Gambas lose the
qt.webkit component for QT5? Will there be any possibility for making an
alternative webview component for Gambas?
--
Full-scale, agent-less Infrastru
11 matches
Mail list logo
