On 12/15/12 13:50, Kim wrote:
Kim <kimtoufectis <at> gmail.com> writes:

I'd call my 1.5 HS first impressions "poor."  Beginning from a clean install
(fs-update from a USB stick), things loaded fine and the opening "hello" boot-up
experience is improved.  After using the control panel to connect to the web,
set time, place, jabber, and frame settings, I killed Sugar in Browse amost
immediately (I tried to save the clipping I had just made of my developer key
link to my journal using the context menu the appears when hovering over the
clipping icon on the left side of the frame).  In three years of using an xo-1
and -1.5, this OS crashed more quickly than any other, and that includes some of
the earlier builds in this sequence (number 8 didn't have these problems).

Finally getting the developeer key into Terminal produced a "that certificate is
invalid" message, so to complete the process I needed to add
"--no-check-certificate" to the end of the command as instructed.  These are
great ways to let send non-tech folks like me know they're not the target
audience...

I agree the Sugar interface doesn't seem a developer priority right now; that's
a shame.  I am puzzled that brand new activities often only support older
OS's...and Dextrose 3 had some features I've given up hoping for in other
versions of sugar, like an indicator of processor/memory strain in the frame and
an easy way to offer user feedback

Switching over to the Gnome interface also failed to delight:  I can't hide the
bars at the top and bottom of the screen by right-clicking as I could in the
past, and choosing on "Change Desktop Background" after right-clicking on the
desktop did nothing.

In gnome I do like that I don't have to reconnect to wifi; my settings carry
over from Sugar.

Playing with this iteration of Sugar some more on a 1.5 HS, I find that trying
to save any clipping to the journal kills the activity, and code streams by on a
black background as (presumably) Sugar reboots, whether in Browse or elsewhere.

As was true for version 8, certain letters (L's and I's I think) seem to vanish
from certain text; so "Feliz Navidad" becomes "Fe  z Nav dad" in the
similarly-named activity.  Closing that activity also caused Sugar to reboot.

Ignore the repeat that follows; I wasn't able to post less than I quoted so I'm
just going to triple my post through repetition.
Playing with this iteration of Sugar some more on a 1.5 HS, I find that trying
to save any clipping to the journal kills the activity, and code streams by on a
black background as (presumably) Sugar reboots, whether in Browse or elsewhere.
Seems to general bug :
 http://bugs.sugarlabs.org/ticket/4312
f18 TC-1-selecting text from entry line and hitting copy with mouse in IRC-10 causes sugar-desktop and SoaS to reboot
Quoted from bug:"Actually, its not only localized to IRC. I tried Copy in Browse and ViewSlides and it crashes sugar."

 https://bugzilla.redhat.com/show_bug.cgi?id=885319f18
TC-1-selecting text from entry line and hitting copy with mouse in IRC-10 causes sugar-desktop and SoaS to reboot


As was true for version 8, certain letters (L's and I's I think) seem to vanish
from certain text; so "Feliz Navidad" becomes "Fe  z Nav dad" in the
similarly-named activity.  Closing that activity also caused Sugar to reboot.

Playing with this iteration of Sugar some more on a 1.5 HS, I find that trying
to save any clipping to the journal kills the activity, and code streams by on a
black background as (presumably) Sugar reboots, whether in Browse or elsewhere.

As was true for version 8, certain letters (L's and I's I think) seem to vanish
from certain text; so "Feliz Navidad" becomes "Fe  z Nav dad" in the
similarly-named activity.  Closing that activity also caused Sugar to reboot.



_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Reply via email to