On Tuesday 24 June 2014 20:28:00 Aleix Pol wrote:
> Well, if we don't like it, we can enable the API. It's tested and somewhat
> reviewed.
I don't feel "somewhat reviewed" is enough. :-)
> On the other hand, it can be a good exercise for KF5 to start adopting new
> API's.
Yes, that's in fact my
On Tue, Jun 24, 2014 at 7:46 PM, Kevin Ottens wrote:
> On Tuesday 24 June 2014 19:17:44 Àlex Fiestas wrote:
> > On Monday 23 June 2014 19:29:19 Kevin Ottens wrote:
> > > What do you mean? Not releasing solid as part of 5.0? Not enabling the
> new
> > > async API?
> >
> > Not enabling the new api.
On Tuesday 24 June 2014 19:17:44 Àlex Fiestas wrote:
> On Monday 23 June 2014 19:29:19 Kevin Ottens wrote:
> > What do you mean? Not releasing solid as part of 5.0? Not enabling the new
> > async API?
>
> Not enabling the new api.
I don't really like that... But I don't feel like postponing to Au
On Monday 23 June 2014 19:29:19 Kevin Ottens wrote:
> What do you mean? Not releasing solid as part of 5.0? Not enabling the new
> async API?
Not enabling the new api.
signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks
Hello,
On Monday 23 June 2014 17:56:20 Àlex Fiestas wrote:
> As many of you know late in the game I started writing some new code to add
> much needed asynchronous api to Solid/Power which meant moving the old
> deprecate code to kdelibs4Support.
>
> The new API is done (you can review it on mast
As many of you know late in the game I started writing some new code to add
much needed asynchronous api to Solid/Power which meant moving the old
deprecate code to kdelibs4Support.
The new API is done (you can review it on master, there are 2 CMake options to
enable them) and all is left to do
