[Sugar-devel] [GSOC] Font Editor Next Steps

[Lionel Laské]

2016-05-17 3:10 GMT+02:00 Dave Crossland <dave at lab6.com>:

>
> I have concerns about the performance of sugar-web apps, especially on
> XO-1s. My understanding is that one of the main engineering concerns that
> OLPC Australia people had with Sugar was the delay in upgrading Browse to
> webkit2; from
> https://github.com/sugarlabs/browse-activity/issues/30#issuecomment-211269328
> I gather this is now completed.
>
> Yash agreed to attempt to write an essential font editor widget (a glyph
> table) in both PyGTK3 and JS and then compare the experience, so we can
> make a decision based on his actual experience rather than a priori
> assumptions :)
>

Nice. Testing on the targeted machine is the key.
I've wrote several Sugar activities in JavaScript. The most sensitive was
KA View [1]  (shortly a video viewer for Khan Academy videos). Because the
activity was written to be deployed on our Malagasy deployment (where we've
got XO-1 laptops), it take me lot of time to ensure first that it make
sense to run videos in a browser on the XO-1.

                 Lionel.


[1] activities.sugarlabs.org/en/sugar/addon/4770
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20160517/14c6c451/attachment.html>