On Tuesday, March 1, 2016 7:37:55 PM CET Mark Gaiser wrote:
> Op 29 feb. 2016 11:10 p.m. schreef "Thiago Macieira" :
> > On segunda-feira, 29 de fevereiro de 2016 21:42:11 PST Sven Brauch wrote:
> > > Hey,
> > >
> > > On 02/28/2016 03:58 PM, Luigi Toscano wrote:
> > > > This is what I use:
> > > >
On terça-feira, 1 de março de 2016 21:20:03 PST Mark Gaiser wrote:
> Isn't it possible to have the platform theme as it was before (with no
> plasma deps) for others to use and then some "more fancy" plugin on top of
> that which would implement just the plasma specific things? That way
> everyone
On Dienstag, 1. März 2016 19:42:58 CEST, Sven Brauch wrote:
Otherwise I agree with your reasoning. I'm just not sure what we can
effectively do about it.
Build option to build the kde/plasma QPA into a strict "KF5" (tier 1) QPA?
Forking sucks terribly and a tier 1 QPA might be interesting for
Hey,
On 03/01/2016 07:37 PM, Mark Gaiser wrote:
> but there is
> undoubtedly going to be a point in time where the plugin only works when
> some very specific plasma part is required for it to function
That is already the case; try running an application with a systray
icon, it will not work (or i
On Tuesday, March 01, 2016 06:45:14 PM Martin Koller wrote:
> On Monday 29 February 2016 21:34:13 Luigi Toscano wrote:
> > > Should a KF5 app (with frameworksintegration) not also use the settings
> > > from a still used KDE4 desktop ?>
> >
> >
> > frameworksintegration is going to be part of plas
On Tue, Mar 1, 2016 at 7:42 PM, Sven Brauch wrote:
> Hey,
>
> On 03/01/2016 07:37 PM, Mark Gaiser wrote:
> > but there is
> > undoubtedly going to be a point in time where the plugin only works when
> > some very specific plasma part is required for it to function
> That is already the case; try
Op 29 feb. 2016 11:10 p.m. schreef "Thiago Macieira" :
>
> On segunda-feira, 29 de fevereiro de 2016 21:42:11 PST Sven Brauch wrote:
> > Hey,
> >
> > On 02/28/2016 03:58 PM, Luigi Toscano wrote:
> > > This is what I use:
> > > export QT_QPA_PLATFORMTHEME=kde
> > >
> > > and you need the integratio
Hello,
On Tuesday, 1 March 2016 18:30:23 CET Marco Martin wrote:
> [...]
> right now They are called Plasma mobile components, but the concern is
> that "it depends on plasma", it's intended just to be used on plasma,
> but that's not true.
> Another name was proposed: Kirigami, below the rational
On Monday 29 February 2016 21:34:13 Luigi Toscano wrote:
> > Should a KF5 app (with frameworksintegration) not also use the settings
> > from a still used KDE4 desktop ?
>
> frameworksintegration is going to be part of plasma, in fact. There would need
> to be an "old plasma" integration. Or you
Hi all,
I'm forwarding this message here, because apparently the discussion on
plasma-de...@kde.org was too narrow, we tought we did reach a
consensus, while in reality we didn't.
What plasma mobile components (or kirigami) is:
* A set of QML imports, aimed to be a Tier1 framework, for help in
cre
On Sunday 28 February 2016 15:42:29 Martin Koller wrote:
>
> it says: https://mail.kde.org/mailman/listinfo/kde-core-devel
I have now updated this page to point to the archives
(thanks to Ingo Klöcker for this help).
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Framewo
On 02/29/2016 11:09 PM, Thiago Macieira wrote:
>> So using QT_QPA_PLATFORMTHEME=kde is basically not a viable solution for
>> > any non-plasma desktop out there. Instead you are stuck with a 3rd party
>> > solution like qt5ct to at least set the Qt / icon theme (color scheme is
>> > quite hard alre
Hello all,
My name is Dimitar Dobrev, a Qt/C++ and C# developer. I would like to
participate as part of KDE in the Google Summer of Code this year with my
project. It is C# bindings for Qt called QtSharp -
https://gitlab.com/ddobrev/QtSharp . I understand that KDE supports people and
projects
13 matches
Mail list logo
