KIO::convertSize(.,.) vs. KFormat::formatByteSize(...)

Friedrich W. H. Kossebau kossebau at kde.org
Sun Jan 26 03:21:47 UTC 2014


Am Samstag, 25. Januar 2014, 21:20:25 schrieb Michael Pyne:
> On Sun, January 26, 2014 00:20:02 Friedrich W. H. Kossebau wrote:
> > In a Plasma Workspace I expect the bytesize parameter defaults to be
> > configurable, like it used to be. And any program which wants to properly
> > integrate into that environment should pick these defaults up. Like I
> > expect the position of the Cancel/Ok buttons to be picked up :)
> > Possibly Plasma Workspace might be the only one where it is configurable,
> > but fine. That is one of the added-value of it :) (LXDE/Razor might be
> > interested to have it as well)
> 
> If it helps (and might also answer a quasi-question of David's), this
> setting is configurable in the "Other" tab of the 'language' KCM (the
> "Locale" button in KDE 4's System Settings).
> 
> I'm not sure where that was put in KF5/PW2 yet.

Hm, that was not my point :)
I was not wondering where in the UI of a Plasma (or perhaps Razor) environment 
a certain setting can be configured.
Instead I was wondering what I if I wear the hat of a developer who considers 
using next to Qt5 also KF5 should expect in non-Plasma(/Razor) environments. 

And IMHO we (KDE hat on) should with KF5 also target/embrace those who look at 
Qt5 as the option to reach a lot of platforms in one go (even those less 
preferred by us, such is life).
And IMHO KF5 code should integrate as much as possible in other 
platforms/system. And things which can not be configured in those systems 
should be hardcoded there to sensible values.

Otherwise I fear KF5 will continue to be considered rather bloatware by so far 
Qt-only using devs because it pulls in all things needed for the rich 
configurability also in non-Plasma environments.

Cheers
Friedrich


More information about the Kde-frameworks-devel mailing list