KDE Frameworks 5: Rhythm

Stephen Kelly steveire at gmail.com
Mon Jan 23 08:56:40 GMT 2012

Thiago Macieira wrote:

> On Sunday, 22 de January de 2012 12.08.57, Stephen Kelly wrote:
>> Valentin Rusu wrote:
>> > Stephen Kelly wrote:
>> >> Kevin Ottens wrote:
>> >>> There's three main reasons for this rhythm:
>> >> * KAction/QAction stuff - Don't know what's needed. If QAction needs
>> >> new virtual method that would need to be determined soon. Is anyone
>> >> driving that? Again, needs subtask here if it's going to happen:
>> >> https://bugreports.qt.nokia.com/browse/QTBUG-20885
>> > 
>> > Well, I volunteered for this item but "real life/job" got a hold on me
>> > since the last meeting. But now I'm getting more time for hacking.
>> > 
>> > I wasn't aware about the QTBUG you linked us to. Thanks for that. And I
>> > can tell I'm far from having a precise plan about KAction merge. But
>> > I'll try to have one in a couple of weeks.
>> Note that feature freeze of Qt is early February.
>> There will be a feature window after that at some point, but it will
>> become even harder to get anything in after that especially with no clear
>> plan.
> Please note that the task is for Qt 5.0 blockers: stuff that needs to
> happen in 5.0 because it cannot happen in 5.1 or later releases.
> If this is about a few methods that need to change in QAction, it's
> probably fine to do them even after the feature freeze. If it's a major
> change, it needs to happen *now*. And by that I mean this week, starting
> tomorrow.

Yes, this was the impression I was trying to give too.

Someone who does not already have a history of contribution to Qt and is not 
already part of the mailing list, patch tracker, and culture can't just fly 
by with a non-trivial patch and expect it to be submitted.

In this particular case (QAction) it probably doesn't matter. QAction is in 
a not-maintained (done) module (widgets). That means it is not usable by QML 
applications which will need a new class to represent an action. It makes 
more sense for whoever knows KAction to make sure that the new class 
satisfies the needs KDE has for actions, or to drive the effort for that new 
class in the first place.



More information about the kde-core-devel mailing list