KDE Devises New Release Plan, Frameworks 5 Ahead

[Teho]

Look at the freak show called Plasma Active, it was sponsored by Nokia in the days when Qt was thought to be a mobile framework only.

Plasma Active wasn't sponsored by Nokia but rather basykom and open-slx. Qt also was also never "though to be mobile framework only". It has a long history in desktop software.

Like a non-desktop KDErev2.

What...

Now Digia reversed this, but the "declarative scripting is king" still lives and have spilled into places where it should never have been going.

Like where?

I bashed the idea it should be used to the extent KDE does. Or more likely the extent KDE are forced to.

To what extend? Forced how?

And KDE's naming is suffering. App 4.12+Plasma2+Framework5=future5. What a boatload of failure.

Just how utterly clueless can you be? When KDE Applications are ported to KDE Frameworks 5 they will be called KDE Applications 5.0. As the release schedule for Workspaces, Applications and Frameworks is different it's natural that the version numbers are different.

Now Digia did a part reversal

How? QML is as strong as ever.

To be a even greater internet warrior and king troll you should use google a little bit more. But you are pretty good already now!!!

Nah. You are giving him too much credit. He's just stupid beyond belief fanboy.

[Thaodan]

I did not bash declarative language per se. I bashed the idea it should be used to the extent KDE does. Or more likely the extent KDE are forced to. "QML everywhere" is part of the heritage from the Nokia days where Qt was set to be a mobile toolkit. Now Digia did a part reversal, but started to target orther OSes. This only adds to the KDE marketing freak show.

Hmm KDE only said 'QML for gui', GNOME is the one that theys JS everywhere.

[Thaodan]

JS have nothing to do with Nokia forcing Qt to go from old school widgets to QML.

No one forces you. GNOME says new core applications have to be written in JS.

[Awesomeness]

You must be joking, right?

Yes, he is joking and every idiot who even answers him, just gives him the stage to present himself. Just ignore that idiot.

http://phoronix.com/forums/profile.php?do=addlist&userlist=ignore&u=73217

[Awesomeness]

Do you have a source for this?

During Akademy all Blue Systems developers agreed to focus exclusively on KF5 for three months: http://agateau.com/2013/08/12/frameworks-5-push/

KF5 and Qt5 are required for full Wayland compliance anyway, so in KWin?s case the difference is not that big. Part of KWin?s KF5 porting results in now going all in with EGL which Wayland is also based on and no longer caring about GLX: https://plus.google.com/photos/11560...35748721265446

[Teho]

I understand your frustrations. KDE is dying,

You do understand that KDE has more full time developers than ever before? You do understand that KDE is going through major revision of their core right now? If you actually knew anythinga about... well anything really you would know better and wouldn't embarrass yourself with spreading that same bullshit over and over again.

I won't answer anything from your message now, but if you rewrite the angry parts Im ready to answer what ever questions you might have.

You don't anser my question because you can't which was expected.

JS have nothing to do with Nokia forcing Qt to go from old school widgets to QML.

They didn't force anyone to do anything and Qt Widgets are still maintained and available even for Qt 5.

It is not healthy to walk around and be angry like that.

Angry? I'm just stating the facts. When person is repeatedly wrong about virtually everthing he's probably stupid. When the same person mocks another project and praises another without any actual basis, he's a fanboy. You are just an extreme case of both.

[schmalzler]

There is no need to bet, it's a fact:

http://treitter.livejournal.com/14871.html

[schmalzler]

Please quote where I said they have to...
Also give us a similar link, where a KDE dev states that new APPLICATIONS should be written in QML.
You also seem to mix up plasma desktop and kde in general, because it is the desktop (including kwin) where you find more and more QML - simply because its rendering is done on the GPU and not the CPU -> better perfomance, less power usage.

[Marc Driftmeyer]

Please quote the part saying new core apps have to be written in js.

I agree with you on this. The claim that new core apps be required to be written in JS is pure bs.

The JS is a means to get new developers learning about writing basic apps for GNOME. Once comfortable it will expected any semi-intelligent developer would jump to C/C++ and the GTK+ frameworks.

[smitty3268]

Everybody here remembers that KDE already runs on Wayland, just not "well", right? The basic support for Wayland is already there.

The full support comes with the release of Framework 5 sometime in (currently) early 2014. At that time, KDE should work 100% on Wayland.

This has been stated multiple times, people.

KDE apps will run once ported to Frameworks 5 - (at least most of them, or with minimal further porting).

However, that will not provide KWin (and therefore desktop) support. KWin integrates extremely heavily with X - as you would expect, since the entire app was built around being an X window manager.

All that needs to be ported to use the equivalent Wayland APIs. That isn't part of Frameworks 5. There's no need for the libs to implement an entire Wayland compositor like KWin does, they just implement the client parts of the protocol that the applications need.

Porting to Frameworks 5 is one necessary step, but far from the last one required. In fact, it's the 1st step.

So, it makes sense to do what they are doing - port KWin to Frameworks 5 first. Then, after that is accomplished, they can focus back on finishing up the rest of the Wayland port for KWin while the rest of the KDE applications are all porting over to Frameworks 5.