https://bugs.kde.org/show_bug.cgi?id=340917
--- Comment #7 from Stephen Kim ---
Gee, sorry for the late reply.
That is some great news. I was also often let down by the theming quality in
KDE4, it was all too inconsistent and quirky. I really look forward to your
KDecoration2 work, curious how
https://bugs.kde.org/show_bug.cgi?id=340917
--- Comment #5 from Stephen Kim ---
(In reply to Martin Gräßlin from comment #4)
> The problem might be address with Qt code review:
> https://codereview.qt-project.org/#/c/99587/4
Thank you for further informations, Graesslin! I've rea
https://bugs.kde.org/show_bug.cgi?id=340917
--- Comment #1 from Stephen Kim ---
Also discovered that just clicking any window titlebar (including the current
focused one's) reproduce the same effect, and occasionally I should click
multiple times elsewhere to make the problem disappear.
--
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-devel@kde.org
Reporter: stephen...@gmail.com
In Breeze theme, right after changing focus to another window by mouse clicking
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117463/#review55320
---
Ship it!
Looks good to me. Ship It :)
- David Stephen
> 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 c
ul 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., Be
/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 Coo
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 KI18n_LIB
Aaron J. Seigo wrote, On 06/05/2013 06:06 AM:
> On Tuesday, June 4, 2013 20:38:45 Stephen Dowdy wrote:
>> I find the default Popup size displaying the calendar and "events/holidays"
>> to be too small (both height and width). writeConfig() and
>> writeGlobalConfig
dconfig" type
interface in PDS (which would be great), so best i can guess i'd
have to script this stuff up some other way.
So, my question would be how best to leverage the existing PDS
layout-templates + plasma-desktop/init structure with some auxiliary
tools?
Thanks,
--stephen
--
Ste
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 k
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
Aaron J. Seigo wrote:
> On Thursday, September 15, 2011 00:21:39 Stephen Kelly wrote:
>> 9edc8d34b3b0f9983f0eb014f8fbf4bcfcffc3f1 introduced a dependency in
>> plasma on kdepimlibs for gpgme++.
>>
>> The cmake check in kdelibs for kdepimlibs claims it is optional, b
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 fou
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
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
aining the situation and a link 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 t
aining the situation and a link to the
> bug report on the qt bug tracker.
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.
- Stephen
-
few years ago
and which seems to be out of scope now:
http://bugreports.qt.nokia.com/browse/QTBUG-1474
I don't have any opinion on the patch.
I suggest you create a Qt only test case and file a bug in Qt.
- Stephen
On 2010-11-28 20:23:45, Davide Bettio
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
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 els
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. Additi
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
>> appea
Stephen Kelly wrote:
> branches/work/akoports/kdepim/kjots/plasmoid
This should be
branches/work/akonadi-ports/kdepim/kjots/plasmoid
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Sebastian Kügler wrote:
> Hey Steve,
>
> On Friday 23 October 2009 20:01:17 Stephen Kelly wrote:
>> Any more thoughts on the plan and intentions above?
>
> What you probably want is to be able to display interesting collections of
> notes, for example an itemview with
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
Marco Martin wrote:
> On Thursday 22 October 2009, Stephen Kelly wrote:
>> 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,
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
adding/r
Hi,
I'm trying to lower the barrier to entry to KDE contribution by documenting
a path from no experience to valued contributor.
http://techbase.kde.org/Projects/Contributor Paths
The developer path is at its 'easiest' when there is no compilation involved
and you don't need to build trunk befor
On Friday 07 November 2008 11:36:58 am Riccardo Iaconelli wrote:
> On Friday 07 November 2008 18:24:38 Aaron J. Seigo wrote:
> > sigh ok, so if we change the colours of all the windows in kde4
to be
> > black, we're all good?
>
> Theoretically yes... practically we can't do that because of the
ba
On Friday 07 November 2008 9:50:03 am Aaron J. Seigo wrote:
> On Friday 07 November 2008, Celeste Lyn Paul wrote:
> > a light grey-blue? Aaron's gold color was a bit harsh, but a
lemon might
>
> yes, as i noted in the first email, the colour used there sucked. i
opened
> it in inkscape and click
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.
__
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:
http://techbase.kde.org/Policie
Aaron J. Seigo wrote:>
> i'd also recommend setting an appropriate mimetype (e.g. x-app-kde-kjots
> or something similar) on things dragged from the kjots and associating the
> applet with that mimetype (it's done via a Mimetypes= entry in the
> .desktop file..) so you can drop books/pages right o
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 ma
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 takin
37 matches
Mail list logo
