On Thu, Jan 16, 2014 at 1:37 AM, Albert Astals Cid wrote:
> El Dimecres, 15 de gener de 2014, a les 21:47:17, John Layt va escriure:
>> Hi,
>>
>> * A number of our apps and utilities really have had their day and
>> need "retiring", e.g. KsCD, Kppp, KFloppy. There's no point keeping
>> low-qualit
On Sunday, January 19, 2014 23:42:58 Martin Sandsmark wrote:
> On Sun, Jan 19, 2014 at 11:55:13AM +0100, Aaron J. Seigo wrote:
> > this is not really related at all, and i hesitate to engage in the topic
> > here due to loss of topical focus.
>
> It was merely to illustrate a point, that switching
Hi,
My name is Yichao Yu (yuyichao). I started to use KDE as my main DE
about one and two years ago and started contributing to some KDE
projects soon after including konsole, kdelibs, dolphin etc..
I have recently (about half a year ago) adopted QtCurve[1], a highly
configurable theme engine for
I think this makes a lot sense and I would welcome QtCurve into KDE.
Can you read though http://manifesto.kde.org/ and confirm you would
agree to all the commitments
(http://manifesto.kde.org/commitments.html) of a KDE project.
David
___
kde-community m
On Mon, Jan 20, 2014 at 9:11 AM, David Edmundson
wrote:
> I think this makes a lot sense and I would welcome QtCurve into KDE.
Thank you for your support.
>
> Can you read though http://manifesto.kde.org/ and confirm you would
> agree to all the commitments
> (http://manifesto.kde.org/commitment
Brilliant.
So the next page to read is
http://techbase.kde.org/Policies/Application_Lifecycle. It explains
the entrance process and the SC vs extragear.
In short we leave this thread for a few days for anyone else to make
positive or negative comments about the software entering KDE. Then if
ever
On Mon, Jan 20, 2014 at 9:29 AM, David Edmundson
wrote:
> Brilliant.
>
> So the next page to read is
> http://techbase.kde.org/Policies/Application_Lifecycle. It explains
> the entrance process and the SC vs extragear.
>
Yes, I've also read that and thank you for your explaination.
I believe QtCu
Hello,
On Monday 20 January 2014 15:29:00 David Edmundson wrote:
> Brilliant.
>
> So the next page to read is
> http://techbase.kde.org/Policies/Application_Lifecycle. It explains
> the entrance process and the SC vs extragear.
Note there's the incubator now for existing projects willing to join
On Mon, Jan 20, 2014 at 11:10:06AM +0100, Aaron J. Seigo wrote:
> namely duplication of effort and inconsistency due to multiple
> implementations of what is from a use case perspective the same thing.
This would be all well and good if it wasn't for the gross regressions it
would suffer.
You arg
On Mon, Jan 20, 2014 at 08:53:34AM -0500, Yichao Yu wrote:
> I would like to move QtCurve to the KDE infrastructure
Yes! :-D
I've been using QtCurve for a while now, and I'd even argue for replacing
Oxygen with it for KDE Plasma Desktop Framework Visual Team Studio 5 SC
Edition 2014.1, with the r
On Mon, Jan 20, 2014 at 6:29 PM, Martin Sandsmark
wrote:
>
> The obvious downsides things being replaced would suffer from, thanks to
> the
> immature state of the desktop components, and not including the previously
> mentioned obviously broken components; dreadful performance, no proper
> accele
On Monday, January 20, 2014 18:29:16 Martin Sandsmark wrote:
> On Mon, Jan 20, 2014 at 11:10:06AM +0100, Aaron J. Seigo wrote:
> > namely duplication of effort and inconsistency due to multiple
> > implementations of what is from a use case perspective the same thing.
>
> This would be all well an
On Monday, 2014-01-20, 18:29:16, Martin Sandsmark wrote:
> The current kcalc UI is very good, I often use it for stuff like bit
> fiddling, etc. I can't say the same thing for the calculator plasma applet.
> But please feel free to prove me wrong and make the plasma calculator much
> better than k
On Mon, Jan 20, 2014 at 06:42:14PM +0100, Martin Klapetek wrote:
> Just for the record, we now have almost 1-to-1 visual consistency of
> QtQuickControls with Oxygen style and classic QWidgets with Oxygen style.
> Couple patches are still pending.
I think the amount of work that has gone into Oxyg
I first wrote a long reply talking crap about UX and regressions, but I
re-read it and thought about kittens instead, so I deleted it.
On Mon, Jan 20, 2014 at 07:05:24PM +0100, Aaron J. Seigo wrote:
> Agreed, or at the very least has parity.
This is all I really want. Don't remove kcalc until the
On Mon, Jan 20, 2014 at 12:32 PM, Martin Sandsmark
wrote:
> On Mon, Jan 20, 2014 at 08:53:34AM -0500, Yichao Yu wrote:
>> I would like to move QtCurve to the KDE infrastructure
>
> Yes! :-D
>
> I've been using QtCurve for a while now, and I'd even argue for replacing
> Oxygen with it for KDE Plasm
On Mon, Jan 20, 2014 at 10:12 AM, Kevin Ottens wrote:
> Hello,
>
> Note there's the incubator now for existing projects willing to join:
> http://community.kde.org/Incubator
>
I have seen the email of the restarted Incubator project before but I
thought it was mainly for start up projects?
QtCurv
On Monday 20 January 2014 17:13:47 Yichao Yu wrote:
> QtCurve (although being not very polished) is already stable and have
> made several releases that are packaged by a number of distributions.
> Is there anything I am missing here?
I think Kevin just wanted to point out there's an additional
wi
On Monday 20 January 2014 23:44:01 Eike Hein wrote:
> On Monday 20 January 2014 17:13:47 Yichao Yu wrote:
> > QtCurve (although being not very polished) is already stable and have
> > made several releases that are packaged by a number of distributions.
> > Is there anything I am missing here?
>
>
19 matches
Mail list logo
