KDE Devises New Release Plan, Frameworks 5 Ahead

[smitty3268]

The last weeks I have only focused on Qt 5, but the weeks before that only focused on Wayland. So you see I am working on both.

Oh, my mistake then.

I don't know how you got to spring 2015, but that doesn't sound reasonable at all. Our timeline hasn't shifted.

Is there a public timeline available for Wayland? I haven't seen it. I guess i was going by 6 month releases - spring 2014 for frameworks 5, fall 2014 for the initial wayland test releases, and spring 2015 for a final release worthy version that distros might switch to. I guess you are saying it will be faster than that?

[mgraesslin]

If you could point out what i said that was wrong, i'd be grateful.

sorry, I don't want to go through a 50 posts thread to search for incorrect things ;-)

Are you saying the current focus of most development is not on the frameworks 5 port right now?

Right now it's Sunday and I don't have any development focus ;-) Overall my personal focus has been on Qt5, by that implied XCB, and Wayland since January. That hasn't changed and won't change. The last weeks I have only focused on Qt 5, but the weeks before that only focused on Wayland. So you see I am working on both.

Also, does my guess of a spring 2015 kde on wayland release sound reasonable?

I don't know how you got to spring 2015, but that doesn't sound reasonable at all. Our timeline hasn't shifted.

[smitty3268]

I think that's a very good idea. It doesn't make sense to say what I am supposed to have said. Both sides in this discussion. As I already wrote: I find this thread highly amusing.

It would be so simple, like just asking me for a statement instead you try to interpret google plus postings on completely unrelated topics and try to interpret them in a way I would not even have imagined in my wildest dreams.

If you could point out what i said that was wrong, i'd be grateful. Are you saying the current focus of most development is not on the frameworks 5 port right now? Also, does my guess of a spring 2015 kde on wayland release sound reasonable? That was just a guess on my part, and i said so from the beginning.

[mgraesslin]

I give up. There's no point continuing this.

I think that's a very good idea. It doesn't make sense to say what I am supposed to have said. Both sides in this discussion. As I already wrote: I find this thread highly amusing.

It would be so simple, like just asking me for a statement instead you try to interpret google plus postings on completely unrelated topics and try to interpret them in a way I would not even have imagined in my wildest dreams.

[smitty3268]

Except for the fact that the developers have been constantly working on Wayland while doing the Frameworks 5 port at the same time. Then it shouldn't be that hard to provide a source, which you have been asked for already.

How about this: http://blog.martin-graesslin.com/blo...-frameworks-5/

With Akademy behind me and the situation about ?what is master? in kde-workspace resolved I decided to switch my work away from Wayland towards getting KWin on top of Qt 5 and KDE Frameworks 5.

But of course at the moment KWin does not work yet when compiled against KF5 as the event filter is not yet ported to xcb. This is what I will focus on next so that we can soon start testing a KWin on 5

Let?s rock to get KWin working on Qt 5 as fast as possible to get an awesome next release.

http://blog.martin-graesslin.com/blog/2013/08/next-step-running/

http://blog.martin-graesslin.com/blog/2013/08/kwin-enters-the-world-of-qtquick-2/

https://trello.com/b/hY9TcRcK/kwin-frameworks

Now where's your source? Perhaps you can point out the commits, since they are all done in the open. Should be easy.

There is nothing regarding Wayland that depends on Frameworks 5, in fact there is experimental Wayland support in Kwin for 4.11.

/sigh
That's like saying Ubuntu 3.10 has experimental Mir support. I guess technically that's correct, but it's incredibly stupid. XMir is not Mir, and KWin outputting X to a wayland display is not wayland. It's still X, just like XMir is still X.

The thing that Wayland support requires is Qt 5, but that is not the same thing.

/sigh
/sigh
Qt5 support comes with Frameworks 5. I thought that was understood.

I give up. There's no point continuing this.

[TheBlackCat]

Nothing except the lack of manpower. Which is actually an extremely important something.

Except for the fact that the developers have been constantly working on Wayland while doing the Frameworks 5 port at the same time.

Guys, do some research. I'm not making this stuff up, it's coming straight from the mouth of the kwin maintainer.

Then it shouldn't be that hard to provide a source, which you have been asked for already.

Since porting to frameworks 5 is a necessary step along the way of getting wayland support, you can say they are never stopping the wayland work. But that's just sophistry - the truth is that right now they are focused on frameworks 5, and after that is working they will switch their focus back to wayland.

There is nothing regarding Wayland that depends on Frameworks 5, in fact there is experimental Wayland support in Kwin for 4.11. The thing that Wayland support requires is Qt 5, but that is not the same thing. They can't release the Wayland port before the Frameworks 5 port because of the Qt 5 dependency, but they can certainly include a working Wayland port in the initial Frameworks 5 release.

[LinuxGamer]

You don't know what you're talking about.

The OpenGL support is just part of the compositing portion of the code, which is rather minor compared to the rest of KWin.

Try finding all the places that use the xlib or xcb APIs.

but you know what glx is Dead!!

[accumulator]

waah!

Visual impression of phoronix forums:

http://www.youtube.com/watch?v=1Gy2FkKrxpw

[mgraesslin]

I have to admit I find this discussion highly amusing.

[smitty3268]

"KWin integrates extremely heavily with X" wait what?

Martin Gr??lin


so is this heavily integrated? looks like it's heavily integrated to OpenGL

You don't know what you're talking about.

The OpenGL support is just part of the compositing portion of the code, which is rather minor compared to the rest of KWin.

Try finding all the places that use the xlib or xcb APIs.