[Sugar-devel] [Dextrose] [PATCH v5 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
greenfeld at laptop.org
Fri Oct 29 00:08:18 EDT 2010
I was wondering about this as well.
I am more of a backend programmer, but the most obvious thing that
stands out to me is that Sugar activities do not seem to regularly
change their launch icons. They are not like system tray or Sugar frame
icons which alter themselves to tell us information.
Pardon me if I missed the back story here (I've read most of this
thread, and glanced at the source code) but why do we see the need to
render the animation on the fly, if that is indeed what is going on? We
may not want activities to package their own animations which could vary
widely in design, but nothing should stop Sugar from pre-rendering
animations for all past used/anticipated screen sizes on the first
download/run of an activity (maybe as an SVG animation, or for speed at
the screen's current resolution/color depth), or any of the OS builders
from generating them for commonly expected screen sizes presuming full
The major drawbacks to this are adding code complexity, as well as a
bias against Sugar on a Stick & CD/DVD-based users; the former may
encounter a variety of different computers, while the latter has no
permanent storage. But I would hope that rendering at first run (or in
an idle detecting process) would take care of them.
Also, I don't know how things are nowadays, but it seems like most Sugar
activity icons are essentially tristate in nature (stroke color, fill
color, and the background mask). While you may or may not be able to
play off of this with hardware color palette rotation anymore, there has
still got to be somewhere where you can use this to your advantage.
On 10/28/10 22:35, Martin Dengler wrote:
> On Fri, Oct 29, 2010 at 05:26:33AM +0530, Anurag Chowdhury wrote:
>> On Fri, Oct 29, 2010 at 12:14 AM, Gonzalo Odiard<gonzalo at laptop.org> wrote:
>>> I think the problem is the code is rendering the svg icon every time
>>> the color is changed.
>>> There are not cache or cairo operation used to avoid this.
>> Certainly that seems to me as a possible reason behind this issue ,
>> but in the present state we need to decide exactly on what future we
>> want for this pulsing icon i.e. keep it , improve it or replace it.
> I guess that's why Gonzalo raised the point. It's usually better to
> fix the problem than to fix a symptom.
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel