[sugar] perceived sugar performance
Tue Apr 29 13:47:20 EDT 2008
Broken or not, they are going to be written. They are going to be
written by teachers. They are going to be written by kids. Not
everyone will write perfectly optimized code.
And, regardless, I want this form of feedback. I don't care if it
lasts 7/10 of a second. I think it will still serve as a valuable
reinforcement of the UI paradigms, and a nice transition as the
activity takes over the screen.
On Tue, Apr 29, 2008 at 1:44 PM, Michael Stone <michael at laptop.org> wrote:
> On Tue, Apr 29, 2008 at 07:26:12PM +0200, Tomeu Vizoso wrote:
> > We cannot presume that _all_ activities will be able to put a window
> > in 0.1-0.5s,
> I think we are better served by presuming that activities which fail to
> start quickly are broken need to be fixed. For goodness' sake, we have a
> processor clocked at over 400 MHz that can play full-screen video. Does
> someone here actually wish to argue that it's acceptable for process
> creation, X connection setup, window creation, and painting to take long
> enough to require secondary feedback mechanisms?
More information about the Sugar-devel