[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: [kdelibs/frameworks] /: Solve KMessagebox's dependency on KConfig with a framework-integration-p
From:       David Faure <faure () kde ! org>
Date:       2012-12-01 0:08:10
Message-ID: 1513310.EpztMR7yRW () asterix ! site
[Download RAW message or body]

On Saturday 01 December 2012 00:59:29 David Faure wrote:
> On Friday 30 November 2012 20:09:00 Oswald Buddenhagen wrote:
> > On Fri, Nov 30, 2012 at 08:05:55PM +0100, David Faure wrote:
> > > On Friday 30 November 2012 19:40:45 Oswald Buddenhagen wrote:
> > > > On Tue, Nov 27, 2012 at 07:39:09PM +0100, David Faure wrote:
> > > > > The "don't show again" checkbox will only store in memory (like
> > > > > QErrorMessage does) on systems where the plugin isn't available.
> > > > 
> > > > this makes the api virtually non-deterministic (and thus worthless)
> > > > from
> > > > the app dev's pov.
> > > 
> > > It makes no difference to the app dev. The user is the one who gets
> > > different behavior when running the app on a system where more of KF5 is
> > > installed than on a system where a standalone app ships a minimal amount
> > > of KF5 libs.
> > 
> > as an app developer i'm interested in delivering a consistent user
> > experience. no way in hell i'm going to leave this to the "moods" of the
> > framework. "screw this api" is the only response you can expect from app
> > devs.
> 
> God knows Qt has the exact same behavior on all the platforms... not.

And Qt has no plugins, obviously.

When writing QImage::load("foo.png"), we're leaving this to the "moods" of the 
framework - i.e. to whether Qt finds the png plugin or not. This is exactly the 
same. Any API with plugins leads to this.

Anyway, I will never convince you, so... bleh :)

-- 
David Faure, faure@kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5

[prev in list] [next in list] [prev in thread] [next in thread]