Scratch

the users name was not entered for this quote so we will just put:  wrote:

('%b=%b' #b #a:equalsb:)

Code:

a:t1 equalsb:t2
t1 = t2 ifTrue [^true].
^false.

What it does:
Reports wether or not the two booleans are equal.

@Sparks This block is the same as the original
[blocks]    <(     <=>     )> [/blocks]
block. Remember you can insert booleans into text inserts, so the original is the same only allows you to use text and/or booleans. It is taking up space on Scratch.mit.edu and it isn't free to have a webpage they have to pay $.


                                            <(  <mouse down?> <=>   <loud?> )> [/blocks]

sparks wrote:

SaveTheSpaces!DueToCarelessOveruseageOfSpaces,
TheyHaveBecomeAnEndangeredSpecies!StandUpForWhatIsRight!

Last edited by Pecola1 (2011-01-07 19:49:37)

floppy_gunk wrote:

I've got several BYOB blocks...

Wow, Panther is a great tool for automating stuff (like typing out the images and links) that would normally take an hour! 

Nice! That's about how much I added when I first saw this thread.

Pecola1 wrote:

MathWizz wrote:

Pecola1 wrote:

The hashes are like broadcast almost; it means that the computer will look for a code named whatever is after the #.
The [ and ] are (I am not really sure)  Like for conditions such as ifTrue: [^ true].

(I thought you were an expert?)

No, #selector is a selector. It is almost identical to a string.

I know but it also SELECTS different codes like broadcasting. That is how it is used in block specs.

So it's like this:

 docodingof: t1

#t1

should do the coding of the inout (i.e. 'forward: 10' will make it go forward 10 steps)?

comp500 wrote:

sparks wrote:

Yes, sorry comp, they're already in the library but thanks all the same for your contribution 

The second one isn't in panther or scratch, just byob.

ADD IT!

SSBBMIsSavingSpacesToo!Yay!Hey...MeToo!

ProgrammingFreak wrote:

I tried my code and it didn't work!

Blockspec:
('alert %s' #- #alert:)

code:
alert: t1
t1<-DialogBoxMorph new title: '?' inform: t1.

ProgrammingFreak wrote:

Blockspec:
('alert %s' #- #alert:)

code:
alert: t1
t1<-DialogBoxMorph new title: '?' inform: t1.

The reason why is because you cannot change an insert in the code, you will need to make a new variable like this:

alert: t1
| t2 |
t2 _ DialogBoxMorph new title: '?' inform: t1
^ t2

Note it still wont work.

Last edited by Pecola1 (2011-01-08 14:42:33)

Pecola1 wrote:

ProgrammingFreak wrote:

Blockspec:
('alert %s' #- #alert:)

code:
alert: t1
t1<-DialogBoxMorph new title: '?' inform: t1.

The reason why is because you cannot change an insert in the code, you will need to make a new variable like this:

Code:

alert: t1
| t2 |
t2 _ DialogBoxMorph new title: '?' inform: t1
^ t2

Note it still wont work.

it works!

alert: t1 
    DialogBoxMorph inform: t1 title: '?'

it has to have the inform before the title, and there is no reason for a second variable.

Last edited by scimonster (2011-01-08 15:08:33)

ProgrammingFreak wrote:

Pecola1 wrote:

ProgrammingFreak wrote:

Blockspec:
('alert %s' #- #alert:)

code:
alert: t1
t1<-DialogBoxMorph new title: '?' inform: t1.

The reason why is because you cannot change an insert in the code, you will need to make a new variable like this:

Code:

alert: t1
| t2 |
t2 _ DialogBoxMorph new title: '?' inform: t1
^ t2

Note it still wont work.

if we fix it do you want it in RKT?

Nah... we can use the open dialogue titled ( ) with text ()

Pecola1 wrote:

New block
Spec
('Play default system beep' #- #beepDefault)

Method
beepDeafault
self beep

Just use:
('beep' #- #beep)

Hardmath123 wrote:

Pecola1 wrote:

the users name was not entered for this quote so we will just put:  wrote:

('%b=%b' #b #a:equalsb:)

Code:

What it does:
Reports wether or not the two booleans are equal.
http://dl.dropbox.com/u/6273449/BlockLibDiv2.png

@Sparks This block is the same as the original
[blocks]    <(     <=>     )> [/blocks]
block. Remember you can insert booleans into text inserts, so the original is the same only allows you to use text and/or booleans. It is taking up space on Scratch.mit.edu and it isn't free to have a webpage they have to pay $.


                                            <(  <mouse down?> <=>   <loud?> )> [/blocks]

sparks wrote:

SaveTheSpaces!DueToCarelessOveruseageOfSpaces,
TheyHaveBecomeAnEndangeredSpecies!StandUpForWhatIsRight!

Ok, I get it. 

jk, I understand. On that note, why are the <[]>[]> blocks string inputs?

What note?

Pecola1 wrote:

Hardmath123 wrote:

Pecola1 wrote:

@Sparks This block is the same as the original
[blocks]    <(     <=>     )> [/blocks]
block. Remember you can insert booleans into text inserts, so the original is the same only allows you to use text and/or booleans. It is taking up space on Scratch.mit.edu and it isn't free to have a webpage they have to pay $.


                                            <(  <mouse down?> <=>   <loud?> )> [/blocks]

Ok, I get it. 

jk, I understand. On that note, why are the <[]>[]> blocks string inputs?

What note?

While we're on the topic of the >=< booleans, why are they string inserts?

Let me have a guess...

Scratch 1.4 is the first version to actually have good string technology.  In 1.3.1 and lower, variables couldn't be strings    , strings couldn't be compared, there were no ask or answer blocks, and there were none of the string control blocks (join [][], letter () of [], length of []).  There were four places for strings:

[blocks]<say[ Hello ]for( 2 )secs><say[ Hello <think[ Hmm... ]for( 2 )secs><think[ Hmm... [/blocks]

So now numbers, strings, reporters, and booleans can be compared. 
Anything is a string. 

Last edited by scimonster (2011-01-09 04:06:29)