Test: new scratchblocks plugin

blob8108

EDIT: thanks to everyone who helped! The new plugin's already released now

—

I'm working on a new version of the scratchblocks plugin, and want to make sure that it works the same as the old one.

You can get to the new one on the secret test page, and the old one on the usual test page.

Please could you test them both, and let me know if you find any differences? I'm particularly interested in edge cases (think adding lots of spaces in weird places, or breaking scripts over lines in weird ways).

Things that are supposed to be different:

“defineblock” is no longer a valid “define” block.
I've dropped the “when «Sprite1» clicked” block.
Ellipses now look right (“…” now aliases to “…”)

Bugs I haven't fixed yet:

“defineblock” is still valid (d'oh)
The “// category = ” hack should hide the comment
Define blocks stack wrong
Comments seem to want to go to the previous block
Can't define a block with the same name as a pre-existing block
Single custom arguments get ringed
Can't have stack blocks that start with an insert
Adding a comment on the “else” makes it show up on the original “if”.
Cap blocks before “else” render wrong.
Inserts with a bad category get messed up
Fix shape hack for inserts
Fix reporter ring styling
Custom blocks aren't automatically recognised
List reporters aren't automatically recognised
Can't put comments in c-mouths
Custom args aren't automatically recognised
Comments inside C mouths aren't aligned correctly
Multi-line comments?

Thanks!

Last edited by blob8108 (June 4, 2014 20:10:17)

tosh · slowly becoming a grown-up adult and very confused about it

davidkt

The only block that works on the new one is

define

Remember when I looked like this? I still do.

Float, my Scratch 2.0 mod | My (somewhat under-construction) blog

technoboy10

Secret ring syntax looks wrong for reporters.
http://blob8108.github.io/scratchblocks2/secret-test/test.html#{%28list%20%3A%3A%20list%29}

trans rights are human rights

blob8108

technoboy10 wrote:
Secret ring syntax looks wrong for reporters.

That's because you've made a stack-shaped ring block.

It should be `((list :: list))`.

tosh · slowly becoming a grown-up adult and very confused about it

technoboy10

blob8108 wrote:
technoboy10 wrote:
Secret ring syntax looks wrong for reporters.
That's because you've made a stack-shaped ring block. It should be `((list :: list))`.

Why not just have a {ring} syntax for all of the things?

trans rights are human rights

blob8108

technoboy10 wrote:
Why not just have a {ring} syntax for all of the things?

Because there are different shaped rings. The {} syntax actually means “make a stack block”.

tosh · slowly becoming a grown-up adult and very confused about it

DigiTechs

BUG!!11

say [Hello!] [I'm a secondary input… what?]

on the new one, of course.

Last edited by DigiTechs (Nov. 24, 2013 11:13:37)

I do, in fact, have my own site; it's here.
I'm also working on a thing called Fetch. Look at it here!
@thisandagain pls explain. @thisandagain pls explain. @thisandagain pls explain. @thisandagain pls explain. @thisandagain pls explain.

blob8108

DigiTechs wrote:
say [Hello!] [I'm a secondary input… what?]

What's wrong with that? That behaviour is the same is the old one…

tosh · slowly becoming a grown-up adult and very confused about it

ErnieParke

I've done a bit of testing, and putting in:

Scratchblocks wrote:
say (test :: list)

define cake
define cake
define cake
define cake
define cake
if on edge, bounce//Where this works.

. . .
move (90) st eps//Where will this appear?
defineblock

when this sprite clicked//category=looks

Creates:

A few bugs that I can see are that the define blocks are stacking on top of each other, and that comments seem to want to go to the previous block. Also, the defineblock block still works, and when you're setting the category of a block, the comment still shows. I haven't found anything past that.

Reporting,

ErnieParke

Last edited by ErnieParke (Nov. 24, 2013 23:31:53)

blob8108

@Ernie Thanks, that's really helpful!

ErnieParke wrote:
the define blocks are stacking on top of each other

comments seem to want to go to the previous block

These are style issues. I seem to have (deliberately?) broken the styling.

the defineblock block still works

Well caught, thanks!

when you're setting the category of a block, the comment still shows

Ooh, I would not have got that! (Because the syntax is changing.)

Thanks again! If anyone finds anything else, let me know…

tosh · slowly becoming a grown-up adult and very confused about it

PullJosh

This causes issues:

define move (10) steps

(As does defining any other real block)

Last edited by PullJosh (Nov. 25, 2013 01:17:15)

Convert your Scratch projects to JavaScript automatically with Leopard!

PullJosh

Hmm… blocks inside blocks seems to be a theme…

move (move (10) steps) steps

Convert your Scratch projects to JavaScript automatically with Leopard!

blob8108

PullJosh wrote:
define move (10) steps

Ooh, thanks. Dang, I tried to simplify the code by using the same path for both, but clearly that was a bad idea.

move (move (10) steps) steps

That's usual and expected and behaves the same as the old one, unless you're seeing something different to me.

tosh · slowly becoming a grown-up adult and very confused about it

Gravitation

I found 2 glitches:

define (testing?)

[]()

blob8108

Gravitation wrote:
I found 2 glitches:

Thanks, I added them to the list

tosh · slowly becoming a grown-up adult and very confused about it

mathfreak231

I found another cool fix: you decided to special-case Stop ().

i have grown as a person. and ive grown, literally. none of my posts from before 2022 represent me accurately.

mathfreak231

if <mouse down?> then
else
delete this clone
else//fasd
else
else
else
else //erwa

Infinite else's are possible.
Adding a comment on the “else” makes it show up on the original “if”.
Multiple comments can therefore be shown on the “if” block.
The “else” puzzle gap is back.

Last edited by mathfreak231 (Nov. 26, 2013 02:02:47)

i have grown as a person. and ive grown, literally. none of my posts from before 2022 represent me accurately.

blob8108

mathfreak231 wrote:
I found another cool fix: you decided to special-case Stop ().

Yup, the rewrite makes fixes like that much easier

tosh · slowly becoming a grown-up adult and very confused about it

blob8108

mathfreak231 wrote:
Infinite else's are possible.

That's not a bug!

I'll add the rest, thanks.

tosh · slowly becoming a grown-up adult and very confused about it

mathfreak231

if <mouse down?>
//do this
else
//do this
end

You can't put comments in the c-mouths anymore…

i have grown as a person. and ive grown, literally. none of my posts from before 2022 represent me accurately.

Discuss Scratch