2009/10/18 Avi <span dir="ltr"><<a href="mailto:fiendishx@gmail.com">fiendishx@gmail.com</a>> wrote:</span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Wade wrote:<br> <br> > Rationale:<br> > 1) Less flashy<br> <div class="im"> > 2) Clock theme represents time<br> </div><div class="im"> > 3) Ability to count how many seconds the launch takes<br> </div><div class="im"> > 4) Close button (instead of timeout) when there is an error<br> </div><div class="im"> > 5) Possibly less startup overhead; needs to be tested on XO </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br><snip />A little bit of thought put<br> into optimization would probably solve the overhead issue. For example,<br> use pre-computed bitmaps instead of that astoundingly inefficient<br> SVG-based algorithm. Also verify that the available hardware is being<br> used effectively.<br> <div class="im"><br></div></blockquote><div><br></div><div>This may be an area where the interests of Sugar & Sugar on a Stick may diverge. Sugar on the XO-1 has a determined size. Bitmaps will be fine. Sugar on a Stick requires vector-based images, because we don't know what screen size we'll encounter. My experience with the GCompris applications in SoaS is that all of the controls are horribly rendered. It comes across as unprofessional, especially when introducing Sugar to teachers & parents.</div> </div>