Comments on: Merry Christmas, and a PlasMate surprise for you :) [screencast]

By: [Po]lentino

[Po]lentino — Tue, 27 Dec 2011 09:07:41 +0000

I completely agree with you sebas but I still fear that someday, trying to implement a new feature or fixing some bugs, we will look at the codebase and say “if only we made it more modular when we had the chanche”
However, I didn’t “went off to work on my own” : I really don’t have much time for coding (except for the thesis I’m writing), just read my previous post. Since Giorgios was (and is) a very active PlasMate contributor, I decided to spend these couple of hours of this free time of mine to work on this “what if” project, and then see the feedbacks.
I want to come back coding as the old times as soon as this crappy period is over

By: sebas

sebas — Mon, 26 Dec 2011 19:26:44 +0000

The top priority is to get a Plasmate release out. The architecture might not be the most beautiful in the world, but the code base is so small that it doesn’t actually make a big difference.

What Giorgos is doing is actually the right thing: Banging on bugs, filling in parts of essential functionality, and moving it towards releasable state.

I’m a bit disappointed that you instead re-write essential parts in your own private branch. It’s exactly what we talked about a few months back: being able to release it is more important than changing its architecture. It would’ve been nice if you joined our efforts in this (reviewing patches, fixing stuff, etc.) and not go off in private to rewrite stuff. :/

Don’t get me wrong, it’s really cool that you work on Plasmate, it’s just not in line with what the other active contributors are focusing on as a team effort, that makes me unhappy because if we would all pull in the same direction, we’d be moving towards our goal faster.

By: [Po]lentino

[Po]lentino — Sun, 25 Dec 2011 08:40:12 +0000

Don’t worry, the scrollbars will return of course.
About your last two sentences: you can start right now with if you want, just install plasmate from using your favorite package manager
Qml plasma components are just bindings to expose plasma functionalities to plasma; just start plasmate and start a new declarative(qml) project, and plasmate will initialize
a simple project with a stub of a qml applet ready to be modified as you wish.
For the api, look at

By: [Po]lentino

[Po]lentino — Sun, 25 Dec 2011 08:30:18 +0000

Yep it is, in fact my idea in the future is to try to write an Editor plugin which loads the kdevplatform editor, so we get their full featured editor too (the qml/python/js/ruby language plugin still should be written iirc)
But still, i think we should take only the interesting bits of kdevplatform because scripted plasmoids/runner/dataengines simply have a different workflow than the usual projects.

By: Manolin

Manolin — Sun, 25 Dec 2011 06:46:03 +0000

Mmm Isn’t a plugin platform what KDevPlatform is? You should check out KDevPlatform before craeting a Yet Another Pluginable Editor (Kate has Plugins as well, I’m sure you can re-use the base…).