DrKonqi placement

[Ben Cooksley]

On Wed, Oct 22, 2014 at 8:13 PM, David Faure <faure at kde.org> wrote:
> On Monday 20 October 2014 10:54:51 Milian Wolff wrote:
>> On Wednesday 02 April 2014 18:48:24 Aleix Pol wrote:
>> > Hi,
>> > I know I'm changing what I say about drkonqi every now and then, but every
>> > step I take, I realize that the project is bigger and bigger. What I
>> > wanted
>> > to do originally was to move it to KCrash, KCrash without drkonqi is much
>> > less useful.
>>
>> <snip>
>>
>> > - with bugzilla integration (additionally to the previous ones):
>> > KF5::WebKit
>>
>> Could this maybe be replaced by using QtWebKit directly?
>
> Then it wouldn't use KWallet, KIO, KCookieJar...
> Would be annoying to have to enter your password again there, when the KIO
> infrastructure would normally take care of it....

Please don't abandon usage of KIO.
Without proper application / framework level code,
QNetworkAccessManager as used by default within Qt contains severe
defects which significantly constrain the ability of sysadmin to
manage our infrastructure in the lowest maintenance cost manner
possible.

>
> Maybe we need to separate the basic crash dialog from the bug reporting
> functionality....
>
> --
> David Faure, faure at kde.org, http://www.davidfaure.fr
> Working on KDE Frameworks 5

Thanks,
Ben Cooksley
KDE Sysadmin

>
> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel