Scratch

bharvey wrote:

A draft Snap 4.0 Manual is up for comments.

One word choice problem that I found was on page 4, paragraph 5 (or 6  ). "...depending on the overall proportion of your browser window." Size might be a better word to describe 'your browser window' IMO. Other than that, I haven't seen any problems.   

Jens, any feedback on my (new and improved... ok, maybe just new) changeset? It's buried a couple of pages back, and has the 10-stepup change for mosaic.

brian, you took my pink floyd refs out! 
[/offtopic]

i really liked the manual, just the font wasn't very readable, maybe take a less serifly one?
i would also like to see less italic/bold text, but that's less of a problem

i also thought that the first chapter had too many comments in parentheses, for example the explanations for alonzo or snap!. it really makes following difficult 

Last edited by roijac (2013-01-01 12:19:22)

How come BYOB calls their mascot "Alonzo" while scratch calls the same image "Gobo"?

found a mistake:

The manual wrote:

In Scratch 1.4, numbers and text strings are first class. You can put a number in a variable, use one as the input to
a block, write a reporter that reports a number, or put a number into a list.

You can't write reporters in scratch!
I think what you meant was "There are reporters that report numbers".

Another 2 mistakes:

<broken image link. Will fix soon. Image at bottom of page 19.>

I think you mean  mean

<is (tree) a [list v]>

and

(join <(tree) as text> [ is not a binary tree]) //could be join or join words, but you need the as text.

Also, I think replace should be a hybrid block because sometimes you need to mutate a linked list. I know there are workarounds using indirection with mutable lists or lambdas, but it would be easier to simply have mutable linked lists.

Last edited by joefarebrother (2013-01-02 13:05:11)

bharvey wrote:

roijac wrote:

brian, you took my pink floyd refs out! 

Huh?

a while ago,  i made a screenshots for you, replacing some of your beatles refs with pink floyd, that i thought you sorted out. after taking a look in my own screenshots i noticed the font was different and you didn't take my pictures at all. take a look at your dropbox folders 

bharvey wrote:

i really liked the manual, just the font wasn't very readable, maybe take a less serifly one?

Ah, you must be a European.     Europeans find sans-serif more readable; Americans find serif more readable.  The font is Baskerville, the most beautiful typeface ever (imho), designed by John Baskerville, first published in 1757.

indeed, european 

bharvey wrote:

roijac wrote:

i would also like to see less italic/bold text

Why?  Among other things, italic is the usual convention for the first introduction of a technical term: "A variable blob is an orange reporter containing the name of a variable, used to dereference the variable in a script."  And of course boldface is for headings.  Was there a particular context in which you didn't like them?

I don't know if that's intended or if it's adobe reader, but that's what i see:

blob8108 wrote:

I still have that changeset that stops Snap! crashing when you "add (foo) to (foo)". I never finished the nice UI for it, though. Do you want it anyhow?

Wait until after 4.0, then, yeah.

In Snap, are scripts compiled to JavaScript before running? I haven't been following this thread enough recently.

The virtual keyboard on iPad is killing me! It doesn't auto-decapitalize, so it types in caps lock unless you manually disable it. Then it keeps popping up randomly, whenever you add focus to a text box (e.g. when you expand the window to add more input type options in a custom block).

Would you change it if I wrote a Morphic local virtual keyboard for you? I think it won't be too hard, I can do it. 

Hardmath123 wrote:

The virtual keyboard on iPad is killing me!

I vote that you get a Google Nexus 7 and make the virtual keyboard work on that!  It isn't just annoying; it downright doesn't work in Snap!.

Awesome!
Snap! 4.0 manual, a 52-page manual that includes things that people in the advanced topics should easily understand such as :
A SNAP! program consists of one or more scripts, each of which is made of blocks.  Here’s a typical script:

when gf clicked
pen down
repeat [4]
move [100] steps
turn ccw [90] degrees
end

The white horizontal line is a signal that if you let go of the green block it will snap into the gold one.
At the top of the script is a hat block, which indicates when the script should be carried out.
To stop the program, click the red stop sign at the right end of the tool bar.

A predicate is a special kind of reporter that always reports true or false.  Predicates have a hexagonal shape:

mouse down?

and those are only a few within the many things in the first 9 of 52 pages

bharvey wrote:

Nope.  Someday, probably.

After that Snap! will take over the world