Dialogs, KMessage box and job widgets

[Kevin Ottens]

Hello,

On Wednesday 14 November 2012 20:37:53 Valentin Rusu wrote:
> I have a question about KMessage class from kdeui/dialogs.

I actually got an answer for that one only recently. :-)
 
> According to the epics page, kdeui/dialogs will go to tier3.
> On the other hand, kdeui/jobs will go to tier2, only the class
> KDialogJobUiDelegate is actually using KMessageBox.
> If KMessageBox will stay in "dialogs", then tier2 jobs will need to call
> tier3. I suppose that's not the desired situation.
> 
> What would be the best solution in order to follow the defined policies?
> Where should KMessageBox go?

The answer at that point is: KMessageBox will go in the not yet created 
Tier4/consistency[*] framework (the one where we put some of the integration 
parts for applications).

It obviously means that lower tier frameworks couldn't use KMessageBox and 
would use QMessageBox instead. That should be fine as most of the KMessageBox 
uses we have in kdelibs map to QMessageBox just fine. There's of course a 
couple of exceptions which should be evaluated on a case by case basis. 
KDialogJobUiDelegate for instance uses the queued API which doesn't have an 
equivalent in QMessageBox, and because of its use and the feature it provides 
it'd make sense to move it in tier4/consistency[*] as well.

I think it's not ideal, I'd rather see QMessageBox have the missing features 
from KMessageBox, but if you look at:
http://community.kde.org/Frameworks/Epics/Qt_5.1_Merging
It is already quite crowded in there, so we have to pick our battles, and the 
KMessageBox one would be a difficult one, since we have other solutions in the 
meantime it is a bit sacrified for now (from the upstreaming perspective, 
it'll still be here and functional for apps using the tier4/consistency[*] 
framework).

Regards.

[*] Note we still don't have a proper name for that one, let the bikeshed 
session begin!
-- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud patron of KDE, http://www.kdab.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20121119/6518433f/attachment.sig>