/plasma/CMakeLists.txt
http://git.reviewboard.kde.org/r/113139/#comment30269
The if-else shouldn't be needed. INSTALL_INTERFACE should already check if
${INCLUDE_INSTALL_DIR} is absolute.
- Stephen Kelly
On Oct. 7, 2013, 8:13 a.m., Ben Cooksley wrote
as it seems camelcase headers are
installed by KF5::plasma into include/KDE/Plasma/
Odd. I tried to add this dir, but seem to have hit a bug I'll look into. Patch
looks good for now I think, thanks!
- Stephen Kelly
On Oct. 7, 2013, 8:13 a.m., Ben Cooksley wrote
On Oct. 7, 2013, 9:35 a.m., Stephen Kelly wrote:
src/plasma/CMakeLists.txt, line 173
http://git.reviewboard.kde.org/r/113139/diff/1/?file=199605#file199605line173
The if-else shouldn't be needed. INSTALL_INTERFACE should already check
if ${INCLUDE_INSTALL_DIR} is absolute.
Ben
Sebastian Kügler wrote:
CMake-gods, can you confirm the below? (It's inconsistent with my
understanding, and how we've done it in the past months, I'd like to have
a specialist opinion before going around and changing every single
CMakeLists.txt in Plasma.)
Running
git log -S
Marco Martin wrote:
Most important, what is the less messy git way to do it?
As we discussed on IRC, it may be better to split plasma out into its own
repo now already, like we did with nepomuk.
As the frameworks branch has a 'use-by' date, I'd prefer not to import more
things into it from
Alexander Neundorf wrote:
On Friday 16 March 2012, Kevin Ottens wrote:
Hello,
On Wednesday 14 March 2012 14:38:19 Aaron J. Seigo wrote:
[...]
this is what really piques my interest: merge based workflow.
an integration branch would be fantastic. that branch should rebase
Hi,
9edc8d34b3b0f9983f0eb014f8fbf4bcfcffc3f1 introduced a dependency in plasma
on kdepimlibs for gpgme++.
The cmake check in kdelibs for kdepimlibs claims it is optional, but the
build fails later. The stuff that uses gpgme++ should be compiled
conditionally based on whether kdepimlibs was
FYI QtQuick 2 will not be compatible with QtQuick 1.x. Something to keep in
mind, that there may be a migration step.
context:
http://thread.gmane.org/gmane.comp.lib.qt.qml/2499
Alan Alpert wrote:
On Wed, 4 May 2011 03:39:22 ext Jason H wrote:
I thought with modularization, that what is in
FYI QtQuick 2 will not be compatible with QtQuick 1.x. Something to keep in
mind, that there may be a migration step.
context:
http://thread.gmane.org/gmane.comp.lib.qt.qml/2499
Alan Alpert wrote:
On Wed, 4 May 2011 03:39:22 ext Jason H wrote:
I thought with modularization, that what is in
, visit:
http://svn.reviewboard.kde.org/r/6005/
---
(Updated 2010-11-28 20:23:45)
Review request for Plasma and Stephen Kelly.
Summary
---
Text format of the note can't be changed while the note is empty, so I add a
space
to the
bug report on the qt bug tracker.
Stephen Kelly wrote:
Just for clarity, I think it's similar to the bug I filed with Qt before,
but maybe not the same.
I think you should file a new Qt bug and link to that.
Anne-Marie Mahfouf wrote:
Stephen did you investigate further
:
---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6005/
---
(Updated 2010-11-28 20:23:45)
Review request for Plasma and Stephen Kelly.
Summary
Aaron J. Seigo wrote:
On October 30, 2009, Stephen Kelly wrote:
would prefer to only show the actual notes in the stack on click so they
could be dragged elsewhere. Obviously the background svg of it should not
be as it is, or the size it currently is. Additionally I need to give
some
Marco Martin wrote:
On Monday 02 November 2009, Stephen Kelly wrote:
Aaron J. Seigo wrote:
On October 30, 2009, Stephen Kelly wrote:
would prefer to only show the actual notes in the stack on click so
they could be dragged elsewhere. Obviously the background svg of it
should
Sebastian Kügler wrote:
On Monday 02 November 2009 15:08:31 Stephen Kelly wrote:
Marco Martin wrote:
Yeah, that sounds pretty good. This is the kind of thing I meant when I
wrote about a master applet with satellites applets, which Aaron wrote
would fail in some situations. I'm not certain
Stephen Kelly wrote:
i think in this case, maybe start with the intended user experience. i'm
not sure what you are actually envisioning for the user experience. e.g.:
should notes appear automatically on your desktop / panel when they
appear in Akonadi, so if i add a note in Kontact
Hi,
busy day.
Aaron J. Seigo wrote:
On October 22, 2009, Stephen Kelly wrote:
In Akonadi I just create an EntityTreeModel which has api for all of that
stuff. If I can forward those calls to plasma somehow, that would be
good, but I need a starting point. Do I create my model in a Applet
Hi,
I'm trying to get notes from Akonadi onto a plasma workspace.
I've been reading some of the apidocs and I can't figure out if I need a
data engine, whether I need one Plasma::Applet per note, whether I need a
'manager' plasmoid that manages all others, keeping them up to date, and
Aaron J. Seigo wrote:
for those wondering what binary compat means for us, in a nutshell:
* we can't add new members to the public classes (the dptr makes that
unecessary in the first place, of course =)
Are you sure about this one?
Techbase says you can:
Aaron J. Seigo wrote:
yes, functions or methods. not data members (which i usually shortcut to
just members, versus methods ... probably what caused confusion;
sorry.)
You're right. I read methods instead of members. Sorry for the noise.
Steve.
Hi,
One of the things I wanted to do in the KDE 4.2 timeframe for KJots was to
make a plasmoid for it. As time is running fast, I'm going to cheat and ask
people who are already familiar with plasma for help on how it could work.
For those who have never seen/used KJots, it is a simple note
Aaron J. Seigo wrote:
On Thursday 25 September 2008, Stephen Kelly wrote:
The idea would be that the plasmoid would display either all of your
kjots notes, or only a particular kjots book, or notes tagged with a
particular
cool!
(i actually maintined kjots in kde3 and gave it its current
22 matches
Mail list logo
