ervin accepted this revision.
This revision is now accepted and ready to land.
REPOSITORY
R241 KIO
REVISION DETAIL
https://phabricator.kde.org/D8348
To: renatoo, #dolphin, #frameworks, #vdg, ervin
Cc: mlaurent, anthonyfieroni, ngraham, #frameworks
ervin requested changes to this revision.
ervin added a comment.
This revision now requires changes to proceed.
Found a small one after all.
INLINE COMMENTS
> kfileplacesitem_p.h:51
> +DevicesType = 3,
> +RemovableDeviceType = 4
> };
RemovableDevicesType (since you used
ervin requested changes to this revision.
ervin added a comment.
This revision now requires changes to proceed.
All the fiddling with URLs makes me wonder if that wouldn't be better done on
the KIO implementations side... but that's out of scope for that patch I think.
INLINE COMMENTS
> kfil
ervin added a comment.
Great work BTW, this looks really nice now.
REPOSITORY
R241 KIO
REVISION DETAIL
https://phabricator.kde.org/D8243
To: renatoo, #frameworks, dfaure, ervin, #vdg
Cc: markg, ngraham, mlaurent, ervin, anthonyfieroni, cfeck, #frameworks
ervin accepted this revision.
REPOSITORY
R241 KIO
REVISION DETAIL
https://phabricator.kde.org/D8243
To: renatoo, #frameworks, dfaure, ervin, #vdg
Cc: markg, ngraham, mlaurent, ervin, anthonyfieroni, cfeck, #frameworks
ervin added a comment.
Looks fine code wise now, just a couple more tweaks to make those sections
look closer to what Dolphin got.
INLINE COMMENTS
> kfileplacesmodel.cpp:476
> +[](KFilePlacesItem *itemA, KFilePlacesItem *itemB) {
> + return (itemA->groupType() < itemB->
ervin added a comment.
A couple more changes needed.
INLINE COMMENTS
> kfileplacesitem.cpp:153-158
> +if (role == KFilePlacesModel::GroupRole) {
> +return QVariant(m_groupName);
> +}
>
> +QVariant returnData;
> if (role != KFilePlacesModel::HiddenRole && role != Qt:
ervin requested changes to this revision.
ervin added a comment.
This revision now requires changes to proceed.
You probably missed my comment on the previous iteration:
"Note that the summary part of the commit is now wrong (it still refers to
KCategorizedView).
Also, KFilePlacesModelTest
ervin added a comment.
One more thing, the way the sections are currently done, if I drag the first
item of a section the visual feedback I get also includes the section itself
giving the feeling that the section itself is being moved. Also I can drag from
the section title itself which is a
ervin requested changes to this revision.
ervin added a comment.
This revision now requires changes to proceed.
Note that the summary part of the commit is now wrong (it still refers to
KCategorizedView).
Also, KFilePlacesModelTest needs to be adjusted to take into account the new
behavi
ervin added a comment.
Not my forte, but I don't see anything blatantly wrong in here. Adding dfaure
to see if he got something to say about it.
REPOSITORY
R240 Extra CMake Modules
BRANCH
master
REVISION DETAIL
https://phabricator.kde.org/D3826
EMAIL PREFERENCES
https://phabricator
ervin added a reviewer: dfaure.
REPOSITORY
R240 Extra CMake Modules
BRANCH
master
REVISION DETAIL
https://phabricator.kde.org/D3826
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
To: adridg, apol, arrowdodger, #buildsystem, #frameworks, ervin, tcberner,
This revision was automatically updated to reflect the committed changes.
Closed by commit R240:5ed7ba07e4f3: appstreamtest: handle non-installed
programs (authored by ervin).
REPOSITORY
R240 Extra CMake Modules
CHANGES SINCE LAST UPDATE
https://phabricator.kde.org/D3860?vs=9459&id=9477
REV
ervin updated this revision to Diff 9459.
ervin added a comment.
Of course, I notice just now I got the order of the parameters wrong.
Now properly working both with and without install_manifest.txt in the
build directory.
REPOSITORY
R240 Extra CMake Modules
CHANGES SINCE LAST UPDATE
ervin created this revision.
ervin added reviewers: Frameworks, apol.
REVISION SUMMARY
If you just built the software without installing it and then run ctest,
this will systematically fail while trying to read install_manifest.txt.
With this patch this case is now handled gracefully, not fo
oever maintains kwidgetsaddons to
give the ship it.
- Kevin Ottens
On Aug. 3, 2016, 10:12 p.m., Albert Astals Cid wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard
e 92)
<https://git.reviewboard.kde.org/r/128581/#comment66028>
Might be a somewhat common scenario, I'm not sure we want to issue a
warning unconditionally.
- Kevin Ottens
On Aug. 2, 2016, 10:27 p.m., Albert Astals Cid wrote:
>
> -
Hello,
On Saturday, 2 July 2016 12:23:31 CEST David Faure wrote:
> > [...]
> > We still need to handle the migration when/if the user installs
> > FrameworksIntegration no? Suddenly all his MessageBoxes will be back
> > without any apparent reason.
>
> True. Although this feels like a corner case
Hello,
Not sure I can be of any help anymore in that area, I've been way to remote
from that code for years now. That said there's a couple of questions at the
end I might be able to answer:
On Saturday, 7 May 2016 14:33:53 CEST David Faure wrote:
> The thing I wonder is... does it really make
Hello,
On Monday, 25 April 2016 07:29:51 CEST Albert Astals Cid wrote:
> I object.
> a) I already told you, don't use something nobody else uses, use the
> separate repos
I think you're making that up to some extend, it's used and tested, more than
all the possible combinations of using the sepa
eated at startup is leaked.
Diffs
-
src/kcheckaccelerators.cpp 85a7d17
Diff: https://git.reviewboard.kde.org/r/127019/diff/
Testing
---
Thanks,
Kevin Ottens
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://git.reviewboard.kde.org/r/127019/diff/
Testing
---
Thanks,
Kevin Ottens
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Hello,
On Sunday, 31 January 2016 10:40:12 CET David Faure wrote:
> On Thursday 28 January 2016 09:35:53 laurent Montel wrote:
> > Yep some time I forgot it in kmail when I used manual call to start.
> > So if you want to use it make it automatic it's better.
>
> I agree, but then I wonder why KJ
Hello,
Here comes my purely API focused comments. I'll snip anything else (even
comments). If I missed something important due to this approach, feel free to
point it out.
On Thursday, 28 January 2016 01:33:32 CET David Faure wrote:
> namespace KIO {
>
> class KIOGUI_EXPORT FavIconsManager : p
Hello,
On Thursday, 14 January 2016 13:20:01 CET Martin Gräßlin wrote:
> By moving it to frameworks we get closer to getting rid of kdesupport
> and get the making releases problem solved once and for all: bug fixes
> will get to users in a timely manner.
>
> Opinions?
Personally I like it. Simi
On Thursday 10 December 2015 12:43:29 Martin Graesslin wrote:
> On Thursday, December 10, 2015 12:24:06 PM CET Kevin Ottens wrote:
> > > As I just said: I consider this as a useless exercise and a waste of my
> > > time (and of anybody else who would do that).
> >
&g
On Thursday 10 December 2015 08:02:49 Martin Graesslin wrote:
> On Wednesday, December 9, 2015 6:14:47 PM CET Kevin Ottens wrote:
> > > I just started looking into doing the replacement and noticed that I'm
> > > also using:
> > > * Non-static data m
Hello,
On Wednesday 09 December 2015 10:07:50 Martin Graesslin wrote:
> On Thursday, November 5, 2015 11:10:49 AM CET Kevin Ottens wrote:
> > Hello,
> >
> > On Thursday 05 November 2015 10:50:06 Martin Graesslin wrote:
> > > There are two things which make the move
Hello,
On Thursday 05 November 2015 10:50:06 Martin Graesslin wrote:
> There are two things which make the move to frameworks difficult and I don't
> see a solution to it at the moment:
>
> 1. We require C++11 without exceptions: reason, it's designed for Linux and
> it didn't come to my mind to
Hello,
On Wednesday 21 October 2015 22:22:54 Christoph Cullmann wrote:
> > On Wednesday 21 October 2015 21:06:02 Christoph Cullmann wrote:
> > My concern there is more the fact that this kind of "short term" or
> > "temporary" solutions tend to become permanent. As long as it is causing
> > pain y
Hello,
On Friday 23 October 2015 16:35:36 Luigi Toscano wrote:
> On Wednesday 21 of October 2015 20:09:33 Kevin Ottens wrote:
> > And then, three areas of efforts which we are missing right now in
> > Frameworks: - systematically try to reduce the tier and type of our
> > fra
Hello,
On Wednesday 21 October 2015 21:06:02 Christoph Cullmann wrote:
> >> > If it is linked to runtime dependencies, I think you ought to not only
> >> > look at the Tier but also the Type. Only frameworks of the "functional"
> >> > type have no such dependencies.
> >>
> >> Perhaps.
> >
> > At
Hello,
On Wednesday 21 October 2015 09:26:35 Christoph Cullmann wrote:
> Hi,
>
> > Hello,
> >
> > On Wednesday 21 October 2015 08:13:42 Christoph Cullmann wrote:
> >> > On Tuesday 20 October 2015 19:49:54 Aleix Pol wrote:
> >> >> 3) non-existing stuff? really? Let's rephrase it as: "Frameworks w
Hello,
On Wednesday 21 October 2015 08:13:42 Christoph Cullmann wrote:
> > On Tuesday 20 October 2015 19:49:54 Aleix Pol wrote:
> >> 3) non-existing stuff? really? Let's rephrase it as: "Frameworks will
> >> only be advertised as available on a platform if they are just require
> >> Qt or other av
Hello,
On Tuesday 20 October 2015 19:49:54 Aleix Pol wrote:
> 3) non-existing stuff? really? Let's rephrase it as: "Frameworks will
> only be advertised as available on a platform if they are just require
> Qt or other available dependencies on the platform". For example,
> requiring libssh could
Hello,
On Thursday 15 October 2015 02:04:45 Aleix Pol wrote:
> On Wed, Oct 14, 2015 at 10:28 PM, Kevin Ottens wrote:
> > Hello,
> >
> > On Wednesday 14 October 2015 21:20:33 Christoph Cullmann wrote:
> >> Therefore my goal for frameworks is to make them actually
Hello,
On Wednesday 14 October 2015 21:20:33 Christoph Cullmann wrote:
> Therefore my goal for frameworks is to make them actually as easy usable
> for people in that situation. We advertise that a lot everywhere but at the
> moment that is just not true beside for really simple stuff like "karchi
Hello,
On Thursday 13 August 2015 22:49:45 David Faure wrote:
> On Sunday 09 August 2015 17:41:16 Kevin Ottens wrote:
> I thought this would impact the ordering seen by users, so I made it stable
> by adding a std::sort. Patch for review:
> http://www.davidfaure.fr/2015/solid_o
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124596/#review83366
---
Ship it!
Ship It!
- Kevin Ottens
On Aug. 3, 2015, 9:11
Hello,
On Saturday 04 July 2015 22:24:50 David Faure wrote:
> CI says:
>
> 10:59:57 QDEBUG : KFilePlacesModelTest::testReparse() Expected:
> ("/home/jenkins", "remote:/", "/", "trash:/", "/media/nfs", "/foreign",
> "/media/XO-Y4", "/media/floppy0", "/media/cdrom", "/foo") 10:59:57 QDEBUG :
> KFil
Hello,
Since the discussion on mailing lists regarding the "Future frameworks
releases" thread couldn't get to a proper conclusion and we agreed on
discussing the matter at Akademy, I took the liberty of scheduling a BoF
session about it ASAP.
The discussion is scheduled for Monday 27 July at
Hello,
On Tuesday 12 May 2015 09:22:12 David Faure wrote:
> On Monday 11 May 2015 15:51:20 Christian Mollekopf wrote:
> > I think there are two possibilities:
> > * "master" is the development branch and we have a separate "release"
> > branch
> > => contributors have it easier because that is per
Hello,
On Monday 20 April 2015 10:34:40 Christian Mollekopf wrote:
> Is there a nameing convention for frameworks? I'd like to name the kimap
> library, which isn't yet a framwork but will eventually become one,
> "KIMAP" (all upper-case), instead of the current "KImap", since IMAP is
> an acronym
On Tuesday 17 March 2015 08:21:22 Martin Gräßlin wrote:
> On Monday 16 March 2015 23:16:51 Albert Astals Cid wrote:
> > We have KPackage depending on kdoctools but since it's optional we pretend
> > it's not a real dependency and call KPackage tier2
> >
> > What's in it for us other than lying to
Hello,
On Wednesday 04 February 2015 01:33:00 Aleix Pol wrote:
> Do we want a KDE Frameworks sprint?
>
> I think it could be interesting, at least to recapitulate about the
> first year of KF5, find what we liked and decide how to keep going.
>
> Who would be interested?
Just an idea, but maybe
On Tuesday 03 February 2015 12:53:08 Jeremy Whiting wrote:
> Hey frameworks developers,
>
> Albert wrote a couple weeks ago:
> > As far as i remember, functional means you can use it standalone, solution
> > means it needs a daemon and integraion means it needs more stuff (more
> > daemons?
>
> I
On Thursday 29 January 2015 09:49:58 Ivan Čukić wrote:
> Hi all,
>
> So, the thread died out again.
>
> Who is in favour of the following:
> - Require MSVC10 like (aka status quo)
> - Require MSVC11
> - Require MSVC12
My opinion is still the same on this matter: VS2012 (aka MSVC11).
Regards.
--
Hello,
On Thursday 15 January 2015 07:25:22 David Faure wrote:
> After the discussion on https://gerrit.vesnicky.cesnet.cz/r/#/c/323/, I just
> had another idea (inspired by a discussion with Alex Fiestas (iirc) long
> ago)...
>
> We could combine the 4 kded modules installed by KIO into a single
On Tuesday 06 January 2015 11:01:19 David Faure wrote:
> Well, that's interesting, I didn't expect you would reply that :-)
You probably picture me as wanting KF to grow wide and large as much as
possible. That'd be wrong. I actually have this concern that we might reach a
point of "too much stu
Hello,
I've been summoned by CCing, loose all hope! :-)
On Sunday 04 January 2015 11:23:49 David Faure wrote:
> On Tuesday 16 December 2014 14:02:18 Sebastian Kügler wrote:
> > - If it's effectively GPL-licensed, it should not be a proper Framework
>
> I would like to challenge this reasoning.
>
On Sunday 16 November 2014 18:01:04 Ivan Čukić wrote:
> Hi,
>
> The topic of increasing the compiler versions we require might have been
> started for the specific issue one of the frameworks had, but I think it
> shouldn't have died out when the issue in question got patched.
>
> IMO, this topic
Hello,
On Wednesday 05 November 2014 09:25:27 Mirko Boehm wrote:
> > On 05 Nov 2014, at 09:02, Kevin Ottens wrote:
> >> I propose to bump the required compiler versions across the board to
> >> compilers that fully 100% implement C++11. It is 2014 and C++14 is
> >
On Wednesday 05 November 2014 09:05:19 Milian Wolff wrote:
> On Wednesday 05 November 2014 00:33:58 Nicolás Alvarez wrote:
> > So, I hereby propose making an exception and bumping the minimum
> > compiler version *for ktexteditor only* to MSVC2012. Opinions?
>
> OK from my side, but I'd say Christ
Hello,
On Wednesday 05 November 2014 08:58:04 Martin Graesslin wrote:
> So in stead of adding one exception after the other, just go the full way
> and raise the requirement.
I'm rather against per framework exception too. That said, raising the
requirement should be done responsibly regarding t
On Wednesday 05 November 2014 08:53:42 Mirko Boehm wrote:
> Hi,
>
> > On 05 Nov 2014, at 04:33, Nicolás Alvarez
> > wrote:
> >
> > So, I hereby propose making an exception and bumping the minimum
> > compiler version *for ktexteditor only* to MSVC2012. Opinions?
>
> I propose to bump the requir
Hello dear KDE contributors,
I'm sending this from Akademy 2014. Our KDE Frameworks BoF is now over, as
usual we did great progress:
https://community.kde.org/Frameworks/Meetings/201409Akademy
Also I put in place the goals for the months to come before coming:
https://community.kde.org/Framework
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120062/#review65873
---
Ship it!
Ship It!
- Kevin Ottens
On Sept. 5, 2014, 8:39
On Thursday 04 September 2014 11:36:38 Martin Klapetek wrote:
> On Wed, Sep 3, 2014 at 10:10 PM, Eike Hein wrote:
> > On 09/03/2014 10:07 PM, Nicolás Alvarez wrote:
> >> So if I'm not in a Plasma session I get no icons?
> >
> > If you're not in a Plasma session you don't get the Plasma
> > platfo
Hello all,
Next week Akademy 2014 starts!
I booked a room for an afternoon for the KDE Frameworks BoF. It will be on
Room 1, the whole afternoon on Tuesday 9 September. Make sure you will be
there!
I prepared the area for the details about the meeting, and the etherpad.
Details can be found a
Hello,
On Tuesday 26 August 2014 18:25:01 Daniel Vratil wrote:
> I definitely want to have the Server and the client libraries in one repo,
> shipped as a complete solution for PIM storage with the server being just
> part of the solution, not a standalone one.
Excellent. Definitely what I'd like
On Tuesday 26 August 2014 15:51:33 David Gil Oliva wrote:
> El 26/08/2014 15:49, "Vishesh Handa" escribió:
> > On Tuesday, August 26, 2014 11:50:50 AM Kevin Ottens wrote:
> > > > gpgme++
> > > > kabc
> > > > kalarmcal
> > > > k
On Tuesday 26 August 2014 11:20:25 laurent Montel wrote:
> Hi,
> I will split kdepimlibs as it
>
> akonadi (need to find another name because it's still used)
> akonadi-abc
> akonadi-calendar
> akonadi-contact
> akonadi-mime
> akonadi-notes
> akonadi-socialutils
To me it sounds like some of those
On Tuesday 19 August 2014 22:39:32 Cornelius Schumacher wrote:
> On Tuesday 19 August 2014 09:33:07 Kevin Ottens wrote:
> > On Tuesday 19 August 2014 08:44:10 David Faure wrote:
> > > IMHO the solution is just to publicize the upcoming frameworks
> > > somewhere.
>
On Tuesday 19 August 2014 16:53:58 Sebastian Kügler wrote:
> On Tuesday, August 19, 2014 09:33:07 Kevin Ottens wrote:
> > > Wouldn't early adopters just checkout and build from git ?
> >
> > Well, I guess some of them might just want to grab something and run with
&g
On Tuesday 19 August 2014 15:09:46 Aleix Pol wrote:
> On Tue, Aug 19, 2014 at 2:04 PM, Kevin Ottens wrote:
> > I'd wait for the demand for that. api.kde.org is already very loaded in
> > information no need to add even more IMO.
>
> Well, we did some information un
On Tuesday 19 August 2014 12:22:17 Aleix Pol wrote:
> On Tue, Aug 19, 2014 at 9:33 AM, Kevin Ottens wrote:
> > On Tuesday 19 August 2014 08:44:10 David Faure wrote:
> > > IMHO the solution is just to publicize the upcoming frameworks
> > > somewhere.
> >
>
On Tuesday 19 August 2014 08:44:10 David Faure wrote:
> On Friday 15 August 2014 12:51:58 Kevin Ottens wrote:
> > And that's the problem if we release them. If it's released "with the
> > rest" expect people to have wrong expectations about them.
> >
>
On Friday 15 August 2014 09:34:04 Alex Merry wrote:
> On Friday 15 August 2014 10:21:57 Mark Gaiser wrote:
> > On Fri, Aug 15, 2014 at 12:12 AM, Àlex Fiestas wrote:
> > > Hi there
> > >
> > > At the Randa sprint we have discussed a little bit what to do with those
> > > frameworks that are still
On Wednesday 13 August 2014 14:20:58 Aleix Pol wrote:
> On Wed, Aug 13, 2014 at 12:29 PM, Denis Steckelmacher
> > The e-mail is currently generated by appending "@kde.org" after the
> > maintainer name. If this is not correct, you can put a full e-mail address
> > in "maintainer" and it will be us
Hello,
On Wednesday 13 August 2014 11:30:48 Denis Steckelmacher wrote:
> Yesterday, api.kde.org has been updated so that it displays a bit more
> information about the frameworks, including code snippets telling the
> user how to add a framework to his/her CMakeLists.txt or .pro file.
>
> In orde
On Wednesday 06 August 2014 17:47:49 Milian Wolff wrote:
> > > Though note that the above does not mean that a call to extract would be
> > > async. It would still be sync. But you could use QFile and its readyRead
> > > signals internally to process stuff asynchronously and then emit the
> > > dat
On Wednesday 06 August 2014 16:09:19 Milian Wolff wrote:
> On Wednesday 06 August 2014 16:05:27 Vishesh Handa wrote:
> > On Tuesday, August 05, 2014 11:19:16 PM Kevin Ottens wrote:
> > > Hello,
> > >
> > > On Tuesday 05 August 2014 18:36:24 Vishesh Handa wro
Hello,
On Tuesday 05 August 2014 18:36:24 Vishesh Handa wrote:
> I would appreciate it if everyone could review the code once before it gets
> into frameworks.
metainfo.yaml should have "release: false" until it's part of a KF release.
Also it should be integration and not functional (relies on
On Saturday 02 August 2014 11:50:17 David Faure wrote:
> Then let's go more "bare bones" in frameworks that can't afford the
> KConfigWidgets dependency, but let's provide the more convenient and more
> usable "out of the box" solution in frameworks that can provide it, such as
> KIO?
Well, if you
Hello,
On Saturday 26 July 2014 16:32:43 Luigi Toscano wrote:
> are autotests - and the corresponding tests in kdelibs4 world - always run
> against a valid installation (aka: make test always after make install), or
> should they work after a simple make?
Ideally they should work after a simple
On Friday 18 July 2014 00:37:02 Kevin Ottens wrote:
> On Thursday 17 July 2014 10:37:45 David Faure wrote:
> > On Wednesday 16 July 2014 22:05:21 Kevin Ottens wrote:
> > > On Wednesday 16 July 2014 10:33:43 David Faure wrote:
> > > > On Tuesday 15 July 20
On Thursday 17 July 2014 10:37:45 David Faure wrote:
> On Wednesday 16 July 2014 22:05:21 Kevin Ottens wrote:
> > On Wednesday 16 July 2014 10:33:43 David Faure wrote:
> > > On Tuesday 15 July 2014 15:16:20 Kevin Ottens wrote:
> > > > (ie at most a
> > > &g
On Tuesday 15 July 2014 16:59:29 Eike Hein wrote:
> On 07/15/2014 03:16 PM, Kevin Ottens wrote:
> > Well, for a single entry menu, really? :-)
>
> Yeah, I do care about every single menu entry not being broken, no
> matter where users use my app :).
Sorry, I was unclear there.
On Wednesday 16 July 2014 10:33:43 David Faure wrote:
> On Tuesday 15 July 2014 15:16:20 Kevin Ottens wrote:
> > (ie at most a
> >
> > widget would be enough for the app related settings, we should talk to the
> > underlying platform for the other ones).
>
&
On Wednesday 16 July 2014 21:12:25 Kevin Krammer wrote:
> On Wednesday, 2014-07-16, 10:33:43, David Faure wrote:
> > On Tuesday 15 July 2014 15:16:20 Kevin Ottens wrote:
> > > (ie at most a
> > >
> > > widget would be enough for the app related s
On Tuesday 15 July 2014 14:59:43 Eike Hein wrote:
> On 07/15/2014 10:24 AM, Kevin Ottens wrote:
> > Which applications? I experience that mostly in krunner and the browsers.
> > As a user I don't think I get to type those anywhere else.
>
> It's not just typing. K
Hello,
On Tuesday 15 July 2014 10:01:50 David Faure wrote:
> On Tuesday 15 July 2014 08:15:46 Kevin Ottens wrote:
> > Honestly to me it looks like a wrong move. A better move would be to have
> > the framework (e.g. KIO) read the settings from the platform for its
> > s
hread, I'm very much not in
favor of such a code move.
- Kevin Ottens
On July 14, 2014, 8:36 p.m., Eike Hein wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.r
On Monday 14 July 2014 13:15:32 John Layt wrote:
> Over on the Windows list we've been discussing about KCM's for
> configuring common services/frameworks like this when running apps
> under non-Plasma desktops, including Gnome, Windows, Mac, etc.
> General gist is that we don't want to have system
Hello,
On Monday 14 July 2014 12:46:15 David Faure wrote:
> On Monday 14 July 2014 12:34:44 Eike Hein wrote:
> > I'd like to port the ebrowsing KCM and move it to
> > plasma-desktop or -workspace, since it has plenty
> > of users outside of Konq (e.g. Konvi, Konsole and
> > Okular, the first two o
On Wednesday 09 July 2014 22:24:20 Marko Käning wrote:
> Hi,
>
> On 09 Jul 2014, at 07:14 , Kevin Ottens wrote:
> > On Wednesday 09 July 2014 09:57:27 Ben Cooksley wrote:
> >>> * finally he thinks we need to strengthen our CI system and tests to
> >>> rais
Hello,
On Wednesday 09 July 2014 09:57:27 Ben Cooksley wrote:
> On 9 July 2014 03:30, Kevin Ottens wrote:
> > * ervin hopes to see kdepimlibs bits getting in sooner rather than later;
>
> Hmm? Sysadmin has already received a request to get the frameworks
> branch of kdepimli
On Tuesday 08 July 2014 18:27:52 John Layt wrote:
> Here's a bit of bike-shedding for you: when creating completely new
> Frameworks in Tier 1, do we name them with a Q or with a K or with
> something completely neutral?
Not really a bike-shedding topic hopefully... We had the case already and we
Hello everyone,
This is the minutes of the Week 28 KF5 meeting. As usual it has been held on
#kde-devel at 4pm Paris time.
Were present: agateau, apol, d_ed, dfaure, fregl, mgraesslin, notmart,
PovAddict, Riddell, sandsmark, tosky, unormal, vHanda and myself.
Announcements:
* KF 5.0 got offic
Hello all,
I'm back, so a quick reminder:
The next KF5 Update Meeting will happen on #kde-devel tomorrow at 4pm Paris
time.
This one will be a bit special, it'll be more about future thinking than
reporting. It'll also probably be the last one for a while.
See you there!
Regards.
--
Kévin Ot
On Friday 04 July 2014 09:17:04 laurent Montel wrote:
> Le vendredi 4 juillet 2014 08:13:58 Kevin Ottens a écrit :
> > On Thursday 03 July 2014 19:50:35 laurent Montel wrote:
> > > Hi,
> > > During kdepim porting I saw that it was not possible to add a
> > >
On Thursday 03 July 2014 19:50:35 laurent Montel wrote:
> Hi,
> During kdepim porting I saw that it was not possible to add a ActionButton
> as QButtonBox is protected.
> => we can do it if we create a derived class.
> But it’s not a very easy method for just add a button.
>
> I would like to add
On Thursday 03 July 2014 13:31:16 Kevin Ottens wrote:
> On Thursday 03 July 2014 10:08:13 David Faure wrote:
> > On Thursday 03 July 2014 09:22:45 Kevin Ottens wrote:
> > > On Thursday 03 July 2014 09:12:17 Marko Käning wrote:
> > > > > Please pick one A
On Thursday 03 July 2014 10:08:13 David Faure wrote:
> On Thursday 03 July 2014 09:22:45 Kevin Ottens wrote:
> > On Thursday 03 July 2014 09:12:17 Marko Käning wrote:
> > > > Please pick one ASAP.
> > >
> > > Yes, please!
> >
> > You can help
On Thursday 03 July 2014 09:12:17 Marko Käning wrote:
> > Please pick one ASAP.
>
> Yes, please!
You can help us there though, please locally revert the commit I mentioned,
and confirm if that fixes the build for solid and allows to build all the way
up to tier 3. I guess you might need to reve
Hello,
On Wednesday 02 July 2014 08:33:01 Marko Käning wrote:
> on OSX solid fails to build because of this:
>
> ---
> /Users/marko/WC/KDECI-builds/solid/src/solid/devices/backends/iokit/iokitdev
> ice.cpp:227:25: error: allocating an object of abstract class type
> 'Solid::Backends::IOKit::Batte
Hello,
On Wednesday 02 July 2014 10:48:58 David Faure wrote:
> On Wednesday 02 July 2014 10:35:29 Jos Poortvliet wrote:
> > On Tuesday 01 July 2014 23:13:24 David Faure wrote:
> > > On Tuesday 01 July 2014 16:16:48 Jonathan Riddell wrote:
> > > > KDE Frameworks 5 gets its first release this week,
On Tuesday 01 July 2014 11:38:29 David Faure wrote:
> On Friday 27 June 2014 12:24:17 Mario Fux wrote:
> > And what about the future releases of KF5? Any decisions made?
>
> Yes. A new release at the beginning of every month,
> rounded up to the nearest weekend.
>
> Here's my suggested release sc
On Saturday 28 June 2014 13:13:19 Mario Fux wrote:
> Am Samstag, 28. Juni 2014, 13.05:09 schrieb Alex Merry:
>
> Morning Alex
>
> > > And what about the future releases of KF5? Any decisions made? At least
> > > Plasma 5 has a tentative schedule now:
> > > http://techbase.kde.org/Schedules/Plasma
On Tuesday 24 June 2014 20:28:00 Aleix Pol wrote:
> Well, if we don't like it, we can enable the API. It's tested and somewhat
> reviewed.
I don't feel "somewhat reviewed" is enough. :-)
> On the other hand, it can be a good exercise for KF5 to start adopting new
> API's.
Yes, that's in fact my
301 - 400 of 1776 matches
Mail list logo
