if i'm correct, the plasma bugs are now redirected to the main
plasma-de...@kde.org
I don't think so (I've checked the headers of a bug-mail - no mention
of plasma-devel). It was the case some time ago and we were fed up
with it so plasma-bugs list was introduced.
Cheerio
--
While you were
if we go ahead with this time and place, this sprint will coincide with a
Nepomuk and KDE Multimedia sprint, so it will be _quite_ the busy place,
though i think that would be a good thing in this case as having more people
This is (from my POV) both good and bad.
Bad: I guess there are more
Example:
[KDevPlatform] fafd165: Don't completely ignore the retrieved top-context
For me, this is more useful, so +1
Maybe adding a keyword 'commit' before the short hash like this
[KDevPlatform] Commit fafd165: Don't completely ignore the retrieved
top-context
--
Cheerio,
Ivan
--
While
- It should be mostly source compatible with Qt4, and is just an opportunity
to break binary compatibility.
Well, even if we do nothing, we are breaking ABI. So, from my point of
view, this is a perfect time to do some API cleanup (all those
deprecated methods, faking virtuals with slots etc.)
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101885/
---
Review request for kdelibs.
Summary
---
KRecentDocument now sends
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101885/#review4590
---
On July 8, 2011, 5:28 p.m., Ivan Čukić wrote
On July 11, 2011, 11:24 a.m., Aaron J. Seigo wrote:
kio/kfile/krecentdocument.cpp, line 103
http://git.reviewboard.kde.org/r/101885/diff/1/?file=26347#file26347line103
should be an asyncCall?
Ivan Čukić wrote:
yes, we don't need a return value or anything
apart
On July 11, 2011, 11:24 a.m., Aaron J. Seigo wrote:
kio/kfile/krecentdocument.cpp, line 103
http://git.reviewboard.kde.org/r/101885/diff/1/?file=26347#file26347line103
should be an asyncCall?
Ivan Čukić wrote:
yes, we don't need a return value or anything
apart
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101885/
---
(Updated July 20, 2011, 10:11 a.m.)
Review request for kdelibs.
Changes
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101885/
---
(Updated July 20, 2011, 10:16 a.m.)
Review request for kdelibs.
Summary
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101885/
---
(Updated July 31, 2011, 6:11 p.m.)
Review request for kdelibs.
Summary
Both kactivities/master and kdelibs/4.7 install the file
lib/libkactivities.so, preventing package generation, so something
has to change.
kdelibs/4.7 shouldn't be used with a separate libkactivities. This is
for 4.8 and further.
The problem can be that some (plasma active 1.o) packages need
kdelibs/4.7 shouldn't be used with a separate libkactivities. This is
for 4.8 and further.
I believe we are supposed to build the rest of KDE (git) against the 4.7
branch of kdelibs now, since master is stale and frozen? Has that changed
again?
It seems so... I thought there will be libs
I guess I should have posted this to release team mailing list, but
this way the topic will have more people involved.
As you all (probably) know, Dennis Ritchie has passed away. In my
opinion, we should somehow make tribute to him.
I'm not sure the idea to name a release after him would be
Sure, if a naming flamefest can't be big enough on a small list, let's do it
on a list with more subscribers. /irony
Ok, I apologize. Didn't really exoect something like this to become a
flamefest. Mail sent to the r-t.
Cool :)
When we are at it:
Apart from various changes in libkactivities, there is now a branch of
kdelibs called ivan/kparts-activities which provides all kparts-based
applications the ability to report resource events (document
open/close...) to the activity manager.
Since kdelibs are frozen,
On 5 December 2011 09:54, Aaron J. Seigo ase...@kde.org wrote:
On Monday, December 5, 2011 09:31:49 Ivan =?utf-8?B?xIx1a2nEhw==?= wrote:
Since kdelibs are frozen, this will never go into master, but will
need to wait for kf5.
to expand on why this is a bit more: it requires libkactivities,
Hi all,
For the foreseeable future, consider kactivities repository frozen for commits.
There is going to be a rather big refactor-change-all-internals-merge
happening soon for which I'll need to merge all commits pushed since I
branched it one-by-one.
This means that if you do commit
/104261/#comment9139
Why do you want to keep these in memory?
- Ivan Čukić
On March 16, 2012, 11:55 a.m., makis marimpis wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104261
On March 16, 2012, 12:49 p.m., Ivan Čukić wrote:
makis marimpis wrote:
Hm, i did that in order to restore the desktop ids from a previous run of
kamd (let's say, in case of log out).
You misunderstood, I don't mind saving it in the config file, I don't
understand the need to keep
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104261/#review11705
---
Ship it!
Ship It!
- Ivan Čukić
On March 18, 2012, 9:22 a.m
to the private
activity that can't be encapsulated in it.
The things that should be added here are (something I forgot) is first to check
whether url is a local file or not. If not, it should act like it is unmovable.
(web pages...)
- Ivan Čukić
On March 27, 2012, 2:22 p.m., Lamarque Vieira
/globalshortcuts.cpp
http://git.reviewboard.kde.org/r/104428/#comment9499
The default shortcuts is something I'd like discussed on the ML.
Personally, I'd have them empty by default.
- Ivan Čukić
On March 31, 2012, 4:19 p.m., makis marimpis wrote
.
- Ivan Čukić
On April 11, 2012, 9:15 p.m., makis marimpis wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104428
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104428/#review12348
---
Ship it!
Ship It!
- Ivan Čukić
On April 12, 2012, 8:23 a.m
Hi all,
I've tested the waters some time ago [1] what would people say if we
started asking for more modern compilers. I've stated there I'll start
the discussion on k-c-d once we branch out 4.9, so I'm doing as
promised. The post was only about kactivities, but the same could be
applied to more
So, in essence, the summary of the thread so far:
- libs still need to be compilable by old compilers until we get
Qt5/KF5 (afterwards, the requirement will be that of Qt itself)
- apps that don't target Mac, can depend on gcc-4.5-equivalent
compilers, as present in all stable releases of
The service will not be built if the compiler doesn't support some C++11
features. The build should not break, if it does, please report.
P.S. I did accidentally broke the non-new-gcc build yesterday, it is
fixed now. Forgot to run clang and gcc4.5 compilation before pushing.
--
Cheerio,
Ivan
without the
user's knowledge? Is there a way to disable the logging, and can the user
clear the collected data easily?
Ivan Čukić wrote:
There will be a KCM for activities in 4.10 where it will be possible to
filter out specific applications, or to filter out all logging
On Aug. 27, 2012, 12:42 a.m., Lamarque Vieira Souza wrote:
Ship It!
Which branch is this, since it is not master as specified?
- Ivan
---
This is an automatically generated e-mail. To reply, visit:
On Aug. 27, 2012, 12:42 a.m., Lamarque Vieira Souza wrote:
Ship It!
Ivan Čukić wrote:
Which branch is this, since it is not master as specified?
(in master, VD switcher is moved into a separate plugin)
- Ivan
Hi,
The latest master of libkactivities caches and pre-fetches some stuff like the
currentActivity, list of activities, list of running activities, activity
names and icons, to minimise the amount of d-bus related locks*.
What do you think of the idea to go one step further, and instead of
It adds a lot of things you'd need to be careful about (e.g. how to ensure
the data is still in shared memory between when the signal is sent and when
the DBus slots are finally called and processed, naming the key for the
memory segment, etc.), but the idea is sound.
The idea is to keep the
please don't. Debian testing and the next Kubuntu release is currently at
2.8.9 (Debian in fact at 2.8.9~rc1-1) and given that both are frozen there
+1
Cheerio,
Ivan
signature.asc
Description: This is a digitally signed message part.
making a frameworks branch in the kactivities repo is fine. the library
should indeed be easy to port.
The core library currently uses only KDebug, i18nc and KUrl.
The data models library, the service and the workspace addons use more stuff.
So, the core library (that is meant to be used in
In short, the whole libs / runtime split idea from KDE4, is gone in KF5,
replaced with the more modular here is all you need for technology xyz.
I know. That is the reason why I decided to keep it in one repository in the
first place - to have it as close as possible to the layout it will
/
Testing
---
Yes
Thanks,
Ivan Čukić
; urls were opened in
multiple windows, multiple tabs, or split-views, and both open/close and
focusin/focusout events were registered correctly.
Thanks,
Ivan Čukić
, visit:
http://git.reviewboard.kde.org/r/106908/#review20502
---
On Oct. 17, 2012, 3:27 p.m., Ivan Čukić wrote:
---
This is an automatically generated e-mail. To reply, visit:
http
opened in
multiple windows, multiple tabs, or split-views, and both open/close and
focusin/focusout events were registered correctly.
Thanks,
Ivan Čukić
:06 p.m., Ivan Čukić wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/106908/
---
(Updated Oct. 17, 2012, 4:06 p.m
/apps/activitymanager/resources/database - 'select * from
nuao_DesktopEvent;'
Konqueror was used to open webpages and local directories; urls were opened in
multiple windows, multiple tabs, or split-views, and both open/close and
focusin/focusout events were registered correctly.
Thanks,
Ivan
I don't have any knowledge about this, but recently there was some library
named libkgoogle which has been renamed to something other to avoid
possible trademark hazard. This has been in the thread Review request:
moving libkgoogle to extragear starting 2012-05-26.
It has been renamed to
Hi,
I realize that this might be a slightly unusual case, but I've read through
I don't think it would be the first - iirc, some KDE apps already have a Qt-
only build mode (Marble if I'm not mistaken)
So, would the KDE community be interested in making Trojitá a part of KDE's
extragear?
Hi all,
I'm requesting an api freeze exception for the KActivities::Info class to
introduce a simple const method:
bool isResourceLinked(const KUrl url);
The implementation for the method already exists, it is just not published in
the API.
The reason for this is that because the former
If it's going to make things faster and it's just exposing an existing
method i'd say go for it, after all people are committing patches that are
Aaron's stance on this is to leave it as it is since it is only used by SLC
which is not released on the desktop, and he doesn't want to introduce
You should migrate those to repositories under your scratch namespace
on git.kde.org.
Hi Ben,
My scratch namespace ? I'm not sure to understand...
http://community.kde.org/Sysadmin/GitKdeOrgManual#Personal_scratch_repositories
Cheerio,
Ivan
:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104417/
---
(Updated Feb. 8, 2013, 10:59 p.m.)
Review request for KDE Runtime, Plasma and Ivan Čukić.
Description
---
When adding an application
/101885/#review27101
---
On July 31, 2011, 6:11 p.m., Ivan Čukić wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101885
Hi all!
The CMake modules for detecting C++11 features are going to get in kdereview
soon. The target for the repository is kdesupport.
To clone it, just do the regular: git co kde:cxx11-cmake-modules
It would be awesome if our regular CMake experts could give me a few hints on
what should be
Can we discuss whether such module should be used?
Naturally.
Why can't you use the #defines from QtCore?
From my POV:
- it is not documented - at least, I couldn't find it in Qt 4.8 docs, nor 5.0
(might be a fault of qt-project.org's search mechanism)
- it is not extensible - it covers a
One needed feature forgotten, so I'm starting with it:
Is it possible for cmake scripts to test the Qt defines?
Namely, the kactivities repository is consisted of a few parts that have (as
previously agreed) different c++ feature requirements
- the library - compilable with any Qt/KDElibs
Why do you need that? Are you adding source files conditionally, depending
on whether the compiler supports certain features?
Yes, as I said, the library builds with any C++ compiler, but the service
requires at least gcc 4.5 equivalent feature set.
The service can not use #error since that
The solution is to have missing services then?
IMO, better not have something than to lie about it. It is like that mainly
for the systems for which don't really want kde workspaces, but rather just
applications (having activities, kwin, etc. under windows or mac is not a
desire of ours).
So, in the end, we have two solutions for projects that are pro C++11:
1) Use the qglobal.h macros as suggested by Thiago.
If one desires to know of the features in cmake, it would be enough to parse
the output of:
gcc -std=c++11 -fPIE -E -dM -I$QTDIR/include -include QtCore/qglobal.h \
-xc++
/110663/#comment24570
This will break things if kamd has not been shut down by ksmserver. (or if
it crashes - it will not restart in the activity it was in beforehands)
It could use a separate config variable and check those on start.
- Ivan Čukić
On May 27, 2013, 10:02 a.m., Simon
implemented this at a time when Ivan still refused to acknowledge that
there is a bug in his plugin at all. There was no real solution in
From this point on, I'm ignoring this discussion.
I have never said that the plugin is not the reason for the bug 314575, I just
explained why it is
This is trivially to work around by a CMake time check and then just define
override to empty.
Yes, similarly can be done for the nullptr.
Cheerio,
Ivan
--
While you were hanging yourself on someone else's words
Dying to believe in what you heard
I was staring straight into the shining sun
On Sunday 01 September 2013 01:03:59 Ben Cooksley wrote:
Hi everyone,
Due to an unfortunate accident involving git merge, several branches
of the plasma-framework repository were rendered unusable.
To correct this, two branches have been forcibly rewound. They are:
- master: now at
hidden under org.kde.* but that isn't the case anymore if you
introduce private.org.kde.*
From my POV, Sebastian's proposal is spot-on for that reason alone - it is
not a (public) 'qml kde import'. It is a private thing.
Cheerio,
Ivan
p.s. and, in all honesty grepping for org.kde will return
Hi all,
Following kde-workspace (and stealing a few sentences from that announcement),
we're planning to merge the frameworks-scratch branch of kactivities into
master later today. That means if you're building 4.x branch of Plasma
yourself from Git, you should switch to the
KDE/4.11 branch.
Please no. We have a 4.12 release to make in 2 weeks and back when we did
the 4.12 planning the only agreed repo to be freezed for 4.11 was
kde-workspace.
What about doing an early KDE/4.12 branch from master so that the release can
continue as planned, while not slowing us down for further
I was planning to branch master into KDE/4.12 after October 30 and
before November 6.
Forget about it. Decided not to create problems - I'll use the same name
for the branch as kdelibs do for the time being - frameworks :)
Also it means that you don't want a 4.13.x for kactivities, right?
Well, to be honest, if you don't want a 4.13 release i'd prefer you actually
use master for KF5. Otherwise people might random-commit fixes to master
and then wonder why they never got into a release, so the two situations i
think make sense are:
People don't really contribute to
/startactive.
- Ivan Čukić
On Oct. 24, 2013, 2:04 p.m., Martin Klapetek wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113415
On Oct. 24, 2013, 3:35 p.m., Ivan Čukić wrote:
Actually, this is something that I wanted to do ever since I saw it on a
different screen to the one I had when I made it.
If you want to try it with a radial gradient, mind that around the logo,
the background needs to be pitch-black
On Oct. 24, 2013, 4:17 p.m., Fredrik Höglund wrote:
What's the cold startup time like for KSplashQML compared to KSplashX?
Let's not forget that the reason KPlash was rewritten to only depend on
X + libjpeg + libpng was so that the startup time would be limited by
the time it takes
to load the images for the theme.
Martin Gräßlin wrote:
but that's a long time ago, isn't it? So Moore's Law... Anyway could be
interesting to do such comparisons on spinning metal.
Ivan Čukić wrote:
We haven't done any real benchmarks, but it doesn't seem to be noticeably
and adding cifs to the list of mounttypes that are probablySlow?
It's not my place to object since the code isn't mine. Yet i do
Whether it is a good to use probablySlow in okular is one question. The other
one is whether cifs should be in the probablySlow category.
From my point of view,
Aloha,
- Resource Description Framework (RDF)
The biggest problem with RDF is that it raises the knowledge needed to
I'm not sure this was *the* problem with nepomuk adoption, but lets ignore
that for a moment :)
So, nepomuk was based on rdf and sparql. Essentially, a simple and
If we all decide to store stuff in sqlite, then it doesn't matter if they
are separate database files or the same one.
I might be missing a few things here, but asking questions is the road to
enlightenment :)
- There is no way to query across different stores, which was the main appeal
of
for the Plasma Active shell as it currently is, single-store querying might
be workable as we tend to keep most of the different resources separated in
the UI (though that’s one thing i want to change in future releases, so you
can group a set of bookmarks with a given file, e.g.)
today before 17:00; this weekend i’m busy, and then next week i’m relatively
available again.
Monday or later for me.
--
Science gathers knowledge faster than society gathers wisdom.
-- Isaac Asimov
If both are sqlite, then it's one query -
select fid from tagRelation, activityRelation where aid = 'activityId' and
tid = 'TagIdentifier';
Now your talkin'
This looks nice
- It needs to be abstracted into a proper api that can understand that those
are separate dbs. (this removes my
On Tuesday, 24. December 2013. 22.03.28 Àlex Fiestas wrote:
As I see it, the nepomuk maintainer says it works better than Nepomuk for
all cases covered by SC. I don't see any reason not to move forward then.
The truthfulness of Vishesh's claim does not enter into it. If we believe it
(and I
The most notorious exceptions are to this rule are nepgoogle and webminer.
Maintainers of both projects are already working on porting them to Baloo.
This I like.
Baloo seems to be working very nice (I've been running it for some time now),
so if all clients are being ported, then I have no
Hi all,
I wanted to post this on the blog, but my server has some issues lately, so
I decided this is the best alternative.
Some people at Tokamak desired to have completion for kdesrc-build, so I
made a very dirty and ugly completion function for it.
--
function _ksrccomp() {
reply=(`grep
You are evil :) Thank you dude!
On 11 January 2014 21:34, Ivan Čukić ivan.cu...@gmail.com wrote:
You are evil :) Thank you dude!
On 11 January 2014 17:04, Thiago Macieira thi...@kde.org wrote:
On sábado, 11 de janeiro de 2014 11:38:25, Ivan Čukić wrote:
function _ksrccomp() {
reply
Ideally this would be exposed in the File object, maybe with some sort
of QVariantMap userProperties() method.
Please don't make it load all attributes and values into the memory if the
most common use-case is to load a value for a desired key.
I'd rather go for something like
Well, the 'worst case' is actually the real case.
But, the thing is that it will be actively tested and developed simply
because we will have both filesystems with xattr (home etc.), and without
(vfat usb-s, encfs stuff and similar).
So, both are used at the same time, and regressions will be
Ping, 4.13 is looming over. If you want to make it so there's no new
releases of 4.12.x anymore and master is KF5 based, please discuss now.
Personally I'd suggest against it since seems that even if we dicussed for
that happening to kde-workspace people did not get the memo and got angry,
Hi all,
Since we have changed the location of our config files not to use .kde
anymore, we will need some way of moving the old configuration files to their
new locations.
Should we use kconf_update for this, or is something else in the works?
Cheerio,
Ivan
--
Make your code readable.
On Friday 04 Apr 2014 21:36:11 Luca Beltrame wrote:
David Faure wrote:
Kevin Krammer had thoughts on the topic - iirc along the lines of every
application should take care of migrating the relevant data ? (cc'ed)
To give more context on this question: kactivities (KF5 based) can be used
+for (const auto testSubdir: { .kde, .kde5 }) {
Shouldn't that be .kde4?
Yes, already fixed in the next commit. :)
That block of code ($KDEHOME, otherwise ~/.kde, otherwise ~/.kde4) sounds
like code that could be shared. Should we have a kde4ConfigHome() and
kde4DataHome() in,
Hi all,
What do you think about splitting the kactivities repository into these:
- library (would remain in the kactivities repo)
- daemon (kactivities-service)
- workspace stuff (kcm, doplhin file linking, activities:/ kio, something
else?)
The reason why this came up again is that the library
* there is a flag which allows building only the library at the moment,
but
that seems not enough.
Using that flag allowed me to successfully compile the library on Windows.
Sorry, didn't mean that it did not help compiling, just that it seems that a
flag does not seem enough for a
Does the library make sense without the daemon? If not then it falls into
this constraint from https://community.kde.org/Frameworks/Policies :
Solutions have a mandatory runtime dependencies, it is part of their design
and where their added value comes from
That is the reason it ended up in
that needs to be reverted because it's actively objectiona-
ble. As Ivan pointed out, few of us will ever commit any-
thing if we're not confident it would meet with the approval
While I do agree that we have a strange and unreally awesome community that
behaves really well (and I do trust
I got this question from Boris, but do not feel qualified to answer,
so forwarding it here. Please CC Boris in reply.
If the report is not separated into components, then I'd guess kde-devel is
the right place for it.
Lets see what the others will say.
A question that I'd have for Boris is
Yyou need to setup git correctly, so that gerrit in that command is
valid,
I see what you're saying, and you're probably right -- there's a bar,
indeed. That bar could however be effectively removed by having a
spoonfeeding,
An alternative to the setup documentation is to actually do it
I'd add Applications/* and Plasma/* to this.
Would it be possible to add the Calligra/* release branches to that
Seems that release branches are starting with capital letters. Would that be
possible and sufficient for the deletable-branch heuristic?
--
Cheerio,
Ivan
KDE, ivan.cukic at
I want:
* A dashboard to see the patches/Merge requests/whatever against the
projects i care
* A dashboard to see the patches/Merge requests/whatever against all
projects * Upload patches via git diff + web
+ Web APIs for the above. I always wanted to have an applet that shows my
reviews
Therefore sysadmin proposes that both clone and scratch repositories
be eliminated as a concept with the next iteration of our Git
infrastructure.
N not scratch repos. I can see clones being useless as branches
in the actual repos should be used instead, but I personally consider
Hi,
I'm volunteering KActivities for the test.
Cheerio,
Ivan
for:
- experimental namespace to force the user to see that something is not stable
- 0 soversion to show that the library has no stable ABI.
Cheerio,
Ivan
On 10 January 2015 at 10:23, Ivan Čukić ivan.cu...@gmail.com wrote:
The C++ committee uses (for example)
std::experimental::something
I
Hi,
Because of the short release cycle for the frameworks, it is hard to
have bigger new features included into one of them. Slowly evolving
APIs while developing stuff leaves a lot of crud and deprecated
methods later.
What is our policy about having experimental (unstable API/ABI) parts
in a
kevin.kof...@chello.at wrote:
Ivan Čukić wrote:
- 0 soversion to show that the library has no stable ABI.
I'd actually set both the soname and the fully-versioned name to
libfoo.so.0.1, then if you change something binary-incompatibly,
libfoo.so.0.2, etc. (or use libfoo.so.0.1 etc
From www.gitorious.org
System notice: Gitorious is being acquired by GitLab and
gitorious.org will shut down end of May. Please import your
repositories to
We still have a few projects on there. One notable being Grantlee (at
least, my kdesrc-build looks for it over there).
I guess this
And thanks for being on-top of this :).
No problem. :)
kdesrc-build/kf5-kdepim-build-include updated and pushed.
--
Cheerio,
Ivan
If by *we* you mean KDE, no we don't have anything there
Not meant to be a yet-another-what-is-a-kde-project type of thread.
Just a heads-up of what is happening with the host that more than a
few people from KDE are using for KDE-related things.
Heads-up mail on KCD because I have *not*
1 - 100 of 131 matches
Mail list logo
