[sugar] another response time

[Eben Eliason]

Yeah, this sounds like something that should be added to the HIG.
Activities should strive to put up a screen as soon as they can, even
if it will take more time to fully present the UI or the content. I
opened #8739 to keep track of this, when I get a chance to get back
into the HIG.

- Eben


On Wed, Oct 1, 2008 at 8:49 AM, Mikus Grinbergs <mikus at bga.com> wrote:
>> as you probably installed previously the Wikipedia activity, my guess
>> is that the jffs2 gc thread was taking most of the CPU.
>
> If I understand correctly, this raises the possibility that other
> actions performed *prior* to the launching of an Activity can
> noticeably affect the time it takes to launch that Activity.
>
> Would someone else please launch XaoS, and see what kind of
> "response time for the launch" they get?
>
> Tried it again, after the XO had sat there overnight (having now
> hopefully done everything it needed to, for jffs2 housekeeping).
> For me, the "launch screen" for XaoS pulsed for 100 seconds before
> the "activity screen" was drawn.  [My guess is that it is
> calculating the fractal picture before showing it.]
>
> mikus
>
> _______________________________________________
> Sugar mailing list
> Sugar at lists.laptop.org
> http://lists.laptop.org/listinfo/sugar
>