Re: [Sugar-devel] Atom shell

[Lionel Laské]

Sure I will do.
Thanks.

   Lionel.

2014-05-18 11:10 GMT+02:00 Christian Stroetmann :

>  On the 18th of May 2014, Lionel Laské wrote:
>
> While you are already updating your website you may want to take care of
> some typos:
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] Sugar Digest 2014-05-15

[Flavio Danesse]

Beautiful photos, I have no shame that facebook, I can not give in I like.

Congratulations on a job.


Hermosas fotos, lástima que no tengo facebook, no puedo darle en me gusta.

Felicitaciones por el trabajo.


2014-05-15 15:25 GMT-03:00 Mike Lee :

> And great photos from Turtle Art sessions in Kathmandu posted on Facebook:
>
> Introducing Turtle Art
>
> https://www.facebook.com/permalink.php?story_fbid=10151995403127583&id=187845102582
>
>
> A photo from Turtle Art Day
>
> https://www.facebook.com/photo.php?fbid=10152402311569362&set=a.140818034361.110570.552694361&type=1&theater
>
> Turtle Art Day 2
>
> https://www.facebook.com/permalink.php?story_fbid=10151996917067583&id=187845102582
>
> Winning Project of Turtle Art Day
>
> https://www.facebook.com/permalink.php?story_fbid=10151996931477583&id=187845102582
>
>
>
>
> On Thu, May 15, 2014 at 1:37 PM, Walter Bender wrote:
>
>> ==Sugar Digest==
>>
>> Happy 6th Birthday Sugar Labs
>>
>> 1. I just got back from Turtle Art Day in Kathmandu, Nepal. OLE Nepal
>> helped organize a 2-day workshop with 70+ children from four schools. Many
>> thanks to Martin Dluhos, Basanta Shrestha, Subir Pradhanang, Rabi
>> Karmacharya, Bernie Innocenti, and Adam Holt, all of who contributed to the
>> event.
>>
>> It was not a surprise that children in Nepal are like children everywhere
>> else: they take to programming like ducks to water. We began by taking the
>> children in small groups to learn some basics about controlling the turtle:
>> one child plays the role of turtle, one holds the pen (a piece of chalk)
>> and the rest, in a circle, instruct the "turtle" how to draw a square. They
>> need to be very precise with their instructions: if they just say "forward"
>> without saying how far forward, the turtle keeps walking. If they say
>> "right", without saying how far to turn, the turtle keeps spinning after
>> they draw a square, I ask them to draw a triangle then they are ready to
>> start with Turtle Art. I've posted a few of the chalk drawing in the wiki:
>> simple ones [1] from my session to more elaborate [2] from those working
>> with another one of the mentors.
>>
>> After working with chalk, we went to the computers. On a laptop connected
>> to a projector, I introduced Turtle Blocks, and again ask for a square. I
>> show them that they can snap together blocks, e.g., forward 100, right 90;
>> showed them the repeat block; and then I show them how to use the start
>> block to run their program with the rabbit or snail (fast or slow). Over
>> time, I introduced the pen and let them explore colors for awhile. Next, I
>> introduce action blocks: make an action for drawing a square and then call
>> that action inside of a repeat block followed by right 45 and you get a
>> pretty cool pattern. This was followed by more open-ended exploration. I
>> introduced a few more ideas, such as using "set color to heading" (the
>> color is determined by the direction the turtle is heading); "set color =
>> color + 1" to increment the color; and "set color = time" to make the color
>> slowly change over time. I also introduced a few other blocks, such as
>> show, speak, and random. Finally, I introduced boxes. For this, I use a
>> physical box: I ask the children to put a number (written on paper) in the
>> box; then I ask them what number is in the box. I ask them to take the
>> number in the box and add 1 to it. Again I ask them what number is in the
>> box. I repeat this until they get used to it; then I show them the same
>> thing using Turtle. The example program I write with them is to go forward
>> by the amount in the box, turn right, and add 10 to the number in the box.
>> I asked them what they think will happen and then show them that it makes a
>> spiral. When they run it with the "snail", they can see the number in the
>> box as the program runs. Another block I explicitly introduced was the
>> "show" block. We programmed an animation with "show image", "wait 1", "show
>> image", "wait 1", ... They recorded dance steps using the Sugar Record
>> activity and used those images in their Turtle projects. As often as
>> possible, we tried to have a child show their work to the entire group. At
>> the end of the second day, we had a table set up for an exhibition; we had
>> to keep adding more tables as more and more children wanted to show off
>> their projects.
>>
>> We originally planned on break-out sessions on Day Two, but we had a
>> technical glitch on Day One, that slowed things down quite a bit. The
>> children were running Sugar 0.82 on XO 1 laptops, which is nearly six-years
>> old. They had them connected to the mesh network, which cannot scale
>> properly to 70+ machines. The result was a lot of frozen machines. It took
>> most of the day to figure out what was wrong. Once we turned off the
>> radios, everything worked great. I also had to spin a stripped down version
>> of Turtle Art, since a number of dependencies I use, such as some Python
>> 2.7 featu

Re: [Sugar-devel] Atom shell

[Christian Stroetmann]

On the 18th of May 2014, Lionel Laské wrote:

While you are already updating your website you may want to take care of 
some typos:

Sugarizer is distributed in the form of 3 components:

It could work on any device ...and has also been tested...Sugarizer Thin 
Client doesn't need... but requires ...

...
Features of Sugarizer Thin Client include:
... data store ...
...
Sugarizer Client is Sugarizer installed locally on the device so it does 
not require ... - it can work stand-alone(alternatively: it works 
stand-alone).Server access could be required only when it needs network 
features.Sugarizer could work ...

...
then launch Chrome using the command line:
...
Note that the option "--allow-file-access-from-files" is needed to 
authorize... Don't forget to close all other instances ... For other 
browser equivalent options see here.

...
to allow the installation of an application...

Features of Sugarizer Client include:
... data store ...
...
Currently it just means to expose... In the near future, Sugarizer 
Server will also be used ...

...
just unzip the content of the Sugarizer 
Client in the directory of your web server...



I am also looking if and how the Sugar Local data store storage limited 
by the browser can be increased above the 5Mblimit.




Christian



Hmm. You're right, the repository name had changed ("sugarizer" 
instead of "Sugarizer") because I'm working on the next release.
I've fixed the sugarizer.org  web site. It 
should works now.


   Lionel.


2014-05-18 1:02 GMT+02:00 >
Christian Stroetmann > wrote

:


In fact, I do know the web loaction.
But I only tried to run the Thin Client again yesterday by pushing on
the button "Run it now!" respectively by following the hyperlinks to
"llaske.github.io/Sugarizer/ "
and, honestly, because "llaske.github.io "
is not accessable at all, I have concluded that the code for the
Client
and the Server can't be downloaded anymore as well.
Now I found that the correct address of the repository is:
github.com/llaske/Sugarizer  .



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

Re: [Sugar-devel] Atom shell

[Lionel Laské]

Hmm. You're right, the repository name had changed ("sugarizer" instead of
"Sugarizer") because I'm working on the next release.
I've fixed the sugarizer.org web site. It should works now.

   Lionel.


2014-05-18 1:02 GMT+02:00 :

>
> In fact, I do know the web loaction.
> But I only tried to run the Thin Client again yesterday by pushing on
> the button "Run it now!" respectively by following the hyperlinks to
> "llaske.github.io/Sugarizer/" and, honestly, because "llaske.github.io"
> is not accessable at all, I have concluded that the code for the Client
> and the Server can't be downloaded anymore as well.
> Now I found that the correct address of the repository is:
> github.com/llaske/Sugarizer .
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel