Re: DrKonqi placement
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. > > Today I stripped out KDE4Support from it and realized the amount of > dependencies is quite considerable: > - without bugzilla integration: > KF5::I18n Can be stripped using tr()? > KF5::IconThemes Huh? I wonder what it's using there... I'd be surprised if it needs something fancier than QIcon::fromTheme(). > KF5::WindowSystem That's only for KStartupInfo right? > KF5::Crash To be expected. :-) > - with bugzilla integration (additionally to the previous ones): > KF5::XmlRpcClient KF5::Wallet KF5::WebKit KF5::ConfigWidgets > KF5::WidgetsAddons KF5::JobWidgets KF5::Completion KF5::Wallet Qt5::DBus Woh! > Because of that fact, I considered turning the bugzilla integration into a > plugin, but then it's very tied to the rest of the code in drkonqi, so it > would mean quite some work splitting it and making sense out of the > abstraction. > > Does anybody want to give a hand so I can concentrate on the rest of > kde-runtime? > Otherwise, we can also put it in a separate repository, or we can move > KCrash to tier 3. Or we keep drkonqi out and have it provided by the workspace. If not available then kcrash could provide a default very basic one. Sounds like something for 5.1 though. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
On Wed, Apr 2, 2014 at 7:07 PM, Kevin Ottens 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. > > > > Today I stripped out KDE4Support from it and realized the amount of > > dependencies is quite considerable: > > - without bugzilla integration: > > KF5::I18n > > Can be stripped using tr()? > > > KF5::IconThemes > > Huh? I wonder what it's using there... I'd be surprised if it needs > something > fancier than QIcon::fromTheme(). > > > KF5::WindowSystem > > That's only for KStartupInfo right? > > > KF5::Crash > > To be expected. :-) > > > - with bugzilla integration (additionally to the previous ones): > > KF5::XmlRpcClient KF5::Wallet KF5::WebKit KF5::ConfigWidgets > > KF5::WidgetsAddons KF5::JobWidgets KF5::Completion KF5::Wallet Qt5::DBus > > Woh! > > > Because of that fact, I considered turning the bugzilla integration into > a > > plugin, but then it's very tied to the rest of the code in drkonqi, so it > > would mean quite some work splitting it and making sense out of the > > abstraction. > > > > Does anybody want to give a hand so I can concentrate on the rest of > > kde-runtime? > > Otherwise, we can also put it in a separate repository, or we can move > > KCrash to tier 3. > > Or we keep drkonqi out and have it provided by the workspace. If not > available > then kcrash could provide a default very basic one. Sounds like something > for > 5.1 though. > > Regards. > -- > Kévin Ottens, http://ervin.ipsquad.net > > KDAB - proud supporter of KDE, http://www.kdab.com > > > ___ > Kde-frameworks-devel mailing list > Kde-frameworks-devel@kde.org > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel > > I confirm that KIconThemes wasn't needed, I guess I dropped the dependency while porting, on the other hand I just realized that I was wrong at the non-bugzilla dependencies, this is the correct list: KF5::I18n KF5::WindowSystem KF5::CoreAddons KF5::Service KF5::ConfigWidgets KF5::JobWidgets KF5::KIOCore KF5::Crash And yes, we can try to trim it down, but I'm unsure how useful that would be. So I agree that we can not move it to KCrash and consider it a task for 5.0+. Aleix ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
On Wednesday, April 02, 2014 07:07:27 PM Kevin Ottens wrote: > On Wednesday 02 April 2014 18:48:24 Aleix Pol wrote: > > - with bugzilla integration (additionally to the previous ones): > > KF5::XmlRpcClient KF5::Wallet KF5::WebKit KF5::ConfigWidgets > > KF5::WidgetsAddons KF5::JobWidgets KF5::Completion KF5::Wallet Qt5::DBus > > Woh! > KF5::Wallet is for the convenience log-in into bugs.kde.org. I 'hinks that's nice on it :-) -- Valentin Rusu irc: valir signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
On 02/04/14 18:07, Kevin Ottens wrote: >> KF5::WindowSystem > > That's only for KStartupInfo right? Pretty sure that doesn't work, either. QX11Info should probably get a startupId() method. That's vaguely on my to-do list somewhere... Alex ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
On Thursday 03 April 2014 22:36:04 Alex Merry wrote: > On 02/04/14 18:07, Kevin Ottens wrote: > >> KF5::WindowSystem > > > > That's only for KStartupInfo right? > > Pretty sure that doesn't work, either. > > QX11Info should probably get a startupId() method. That's vaguely on my > to-do list somewhere... You mean like this? :-) https://codereview.qt-project.org/#change,82386 -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
On 05/04/14 11:36, David Faure wrote: > On Thursday 03 April 2014 22:36:04 Alex Merry wrote: >> On 02/04/14 18:07, Kevin Ottens wrote: KF5::WindowSystem >>> >>> That's only for KStartupInfo right? >> >> Pretty sure that doesn't work, either. >> >> QX11Info should probably get a startupId() method. That's vaguely on my >> to-do list somewhere... > > You mean like this? :-) > > https://codereview.qt-project.org/#change,82386 > Always one step ahead :-) Alex ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
On Wednesday 02 April 2014 19:07:27 Kevin Ottens wrote: > > KF5::WindowSystem > > That's only for KStartupInfo right? Removed now. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
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. > - with bugzilla integration (additionally to the previous ones): > KF5::WebKit Could this maybe be replaced by using QtWebKit directly? Bye -- Milian Wolff m...@milianw.de http://milianw.de ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
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. > > > > > - 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 Maybe we need to separate the basic crash dialog from the bug reporting functionality -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: DrKonqi placement
On Wed, Oct 22, 2014 at 8:13 PM, David Faure 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. >> >> >> >> > - 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, fa...@kde.org, http://www.davidfaure.fr > Working on KDE Frameworks 5 Thanks, Ben Cooksley KDE Sysadmin > > ___ > Kde-frameworks-devel mailing list > Kde-frameworks-devel@kde.org > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
