KDE Platform Profiles
ps_ml at gmx.de
Mon Apr 12 14:37:51 BST 2010
-----BEGIN PGP SIGNED MESSAGE-----
Am 12.04.2010 14:46, schrieb Thiago Macieira:
> Em Segunda-feira 12 Abril 2010, às 13:15:08, Kevin Ottens escreveu:
>> - Desktop: Extensive and power user usage as we know it today (the full
>> game: multimedia, any content reading, complex content editing);
>> - Tablet: Mostly Internet connected devices for multimedia usage, reading
>> content, some content editing;
>> - Mobile: Very constrained devices, multimedia usage, content reading,
>> very light content editing.
> I think you're missing a Netbook/Laptop profile in-between Desktop and Tablet.
> Maybe even the two split up.
> When I'm at home, I use my laptop as a desktop. Power is of no concern, and I
> even build code on it.
> But when I'm travelling, I notice that the KDE environment sucks at power
> consumption. I would even go as far as to say that power consumption is an
> issue in any segment and applications shouldn't wake up unnecessarily, nor
> send broadcasts on D-Bus unnecessarily.
> Of import is the Netbook form factor: it's like the desktop, but on a smaller
> screen. So maybe it won't affect kdelibs, but the apps themselves that want to
> address this segment.
>> Some dependencies can be cut by moving symbols within kdelibs further down
>> in the dependency chain. This type of change is hardly "#ifdef'able" so it
>> would affect also the Desktop profile. This is binary compatible on Linux
>> and Windows but unfortunately not BC on Mac.
> Please read src/corelib/xml/qxmlstream.h:
> // These platforms do not support symbol moving but allow it to be duplicated:
> // Microsoft Windows (COFF PE executable format)
> // special case: Windows CE wasn't supported before 4.4.0
> You can't move the symbols further down the dependency chain on Windows. You
> have to copy them.
Do you have some more information about this or did you just find the note?
I will check again, later tonight, but I think we already tried this
once. I will inform you about my investigations again.
>> To summarize, here are the different profiles, and the type of actions they
>> would imply:
> Please address too the kded dependency issue along with the "klauncher-less
> KDE" mode.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (MingW32)
-----END PGP SIGNATURE-----
More information about the kde-core-devel