[PATCH] Animations enable/disable system wide
robertknight at gmail.com
Sat Feb 16 13:20:41 GMT 2008
> Finally, as you say, qualifiers like 'need high contrast', 'does not have much
> color space', 'is software redendered', 'wants to save battery' etc would need
> to be taken into account, somehow
This is about performance, "need high contrast" is an accessibility
issue. "wants to save battery" is a dynamic state which is already
available though Solid.
> Also, I would want to be able to create my
> own profiles from that.
That makes it more complicated all of a sudden. Right now I'd suggest
keeping it simple and getting it working where it matters, eg. as per
Aaron's pre-defined list above.
On 16/02/2008, Richard Hartmann <richih.mailinglist at gmail.com> wrote:
> On Feb 16, 2008 1:18 PM, Robert Knight <robertknight at gmail.com> wrote:
> > One thing to bear in mind about those use cases is that the
> > performance of those categories of devices will probably change
> > somewhat over the life-span of KDE 4, particularly mobile devices.
> Especially with hand-held devices, profiles for specific hardware might
> be the best approach to handle this problem. An OpenMoko v1 will
> have the same hardware and similar software restraints like all other
> OpenMoko v1 out there. At least until we get really lego-like mobiles,
> but that is probably too far in the future to care about, anyway.
More information about the kde-core-devel