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

List:       kde-core-devel
Subject:    Re: Support for animated icons (on mouseover)
From:       David Faure <david () mandrakesoft ! com>
Date:       2002-01-18 15:57:33
[Download RAW message or body]

On Friday 18 January 2002 02:48, Andreas Pour wrote:
> Question:  when are these icons loaded?  I think it was on demand.
Yes.

> Now,
> let's say you are currently accessing the disk a lot -- whether b/c you
> launched an application, or you are low on memory and things are
> swapping, or whatever.  Doesn't loading 5 icons then cause a "jump"
> effect, which would be very annoying?  
Note that the 5 icons are in fact a single MNG - it's about a single open().

> There is of course a way to deal
> with that -- start a timer and if the icons have not all been loaded
> within some short period of time, skip the animation.

That would sound like a bug IMHO.
Better have a way to switch the whole thing off - which is possible now.

> The other thing that's worrying to me about these types of animations is
> their effect on bandwidth.  I recall people were discussing at some
> point auto-detecting if the server is on a different machine and, if so,
> automatically turning these things off.  This is particularly important
> for enterprises which run thin clients -- they don't need tons of
> bandwidth used for these things.

I agree, that would be quite nice. I'm not sure how to detect that though.

> Can this type of thing go into KPersonalizer?  There's the "slow
> processor" <=> "fast processor" page, shouldn't this setting effect
> whether these things are turned on by default?

Yes, see my last post.

> BTW, it would be nice to also have a radio button there for "local
> interface" or "network connection", so that in the latter case a lot of
> the animation-type stuff can be disabled (which of course has nothign to
> do with the processor speed).

Who will think about running KPersonalizer when launching a remote connection?
Doesn't sound like the right place, better have a KControl setting or an 
auto-detection. Understand that the same desktop might be used both locally 
and remotely, so the KPersonalizer time (first run) is long gone when using 
the desktop remotely for the first time.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://people.mandrakesoft.com/~david, http://www.konqueror.org
KDE 3.0: Konquering the Desktops

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