On Friday April 22 2016 21:28:56 David Faure wrote:
> Yep. A qt5/kf5 based konqueror isn't released yet, so who would need this
> yet...
There's a frameworks branch in kde-baseapps that provides "konqueror5", which
isn't missing too much from what I can see ...
> (dunno about rekonq).
I only
> And only KHTML and QWebkit have KIO integration, QWebEngine doesn't ...
> the browser situation is going downhill :(
I found some mention of a QWebEngine port of kwebkitpart on the webkit ML, but
not the branch mentioned in that post. Maybe KIO integration is going to be
included at that level (?)
Or else QtWebKit could become KWebKit now that Qt have ejected it ... could be
a very good way to attract interest from a wider audience to KF5 ;)
> Set it before starting kdeinit5, and watch kdeinit5 output.
>
> (or export KDE_FORK_SLAVES=1 to get the kioslave started here rather than by
> kdeinit5)
Doesn't really tell me much more except that the http kioslave is started:
kf5.kinit.klauncher: KLauncher: launching new slave
"/opt/local/libexec/kde5/kf5/kioslave" with protocol= "http" args=
("opt/local/share/qt5/plugins/kf5/kio/http.so", "http",
"local:/var/folders/j1/1439ppj08xj8h6006s6drbq00000gs/T/runtime-bertin/klauncherL41926.1.slave-socket",
"local:/var/folders/j1/1439ppj08xj8h6006s6drbq00000gs/T/runtime-bertin/kioclientJ41927.2.slave-socket")
kf5.kinit.klauncher: "/opt/local/libexec/kde5/kf5/kioslave" (pid 41930) up and
running.
Looks like I'm going to have to add output to kio_http and see if the error
message doesn't come from an error==ENOENT returned from a failed function
call. Seems like something that's going to be fun ...
R.
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
