Discuss Scratch
- Discussion Forums
- » Advanced Topics
- » ~scratchblocks~ discussion thread
- blob8108
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread

Hi! I've been working on a new renderer now a new parser for scratchblocks.
Please try it out, and let me know what you think!
Old parser: http://scratchblocks.github.io/v3/
Old parser + renderer: http://scratchblocks.github.io/v2/
Let me know here/on GitHub if you find any bugs. Thanks. (Or just go right ahead and send a PR!)
Last edited by blob8108 (April 18, 2016 10:56:41)
- NickyNouse
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
It's looking really gorgeous right now! I reported a few things. Are comments still being written? ‘Cause they break for me but idk if they’re just still in the works
Last edited by NickyNouse (April 11, 2016 13:48:03)
- blob8108
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
@NickyNouse Comments should work, yes. If not, that's a bug.
- Dylan5797
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
It looks really good!
I'd like to point out (this really is a bug with the parser) that variables and custom procedure inputs called “end” don't end a c-block but display without any text and appear to be in the control category.
Edit: Link
I'd like to point out (this really is a bug with the parser) that variables and custom procedure inputs called “end” don't end a c-block but display without any text and appear to be in the control category.
Edit: Link
Last edited by Dylan5797 (April 11, 2016 13:53:00)
- blob8108
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
It seems to work great for me!
It's looking really gorgeous right now!
It looks really good!Thanks all

I'd like to point out (this really is a bug with the parser) that variables and custom procedure inputs called “end” don't end a c-block but display without any text and appear to be in the control category.Mmm, that's true. In the new parser they'll just be yellow:

- Dylan5797
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
Is there an estimated release date for the new renderer and parser on the scratch forums?It seems to work great for me!It's looking really gorgeous right now!It looks really good!Thanks allI'd like to point out (this really is a bug with the parser) that variables and custom procedure inputs called “end” don't end a c-block but display without any text and appear to be in the control category.Mmm, that's true. In the new parser they'll just be yellow:
- blob8108
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
Is there an estimated release date for the new renderer and parser on the scratch forums?Lol, no. It's not even finished yet! And the ST tend to take a while to merge things; they have lots of users, so they have to be very careful

- Sigton
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
All worked well, apart form custom blocks turned out obsolete for me (The actual blocks not the definitions).
Sigton
Sigton
- helloandgoodbye9
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
It's looking really gorgeous right now! I reported a few things. Are comments still being written? ‘Cause they break for me but idk if they’re just still in the works
@NickyNouse Comments should work, yes. If not, that's a bug.Free standing comments don't work. Not only that, but if you write one, the screen no longer updates. Here is the link.
- Jonathan50
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
Hype!
What's the syntax for multiline rings? http://scratchblocks.github.io/v3/#(%7Blol%0Ayay%7D%20%E2%96%B6%20%3A%3Agrey%20ring)
What's the syntax for multiline rings? http://scratchblocks.github.io/v3/#(%7Blol%0Ayay%7D%20%E2%96%B6%20%3A%3Agrey%20ring)
- Jonathan50
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
Can you make ◀ ▶ look black again?
But upvars look sort of okay: http://scratchblocks.github.io/v3/#script%20variables%20((foo)%3A%3Agrey)%20%E2%97%80%20%E2%96%B6%20%3A%3A%20grey
But upvars look sort of okay: http://scratchblocks.github.io/v3/#script%20variables%20((foo)%3A%3Agrey)%20%E2%97%80%20%E2%96%B6%20%3A%3A%20grey

- Jonathan50
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
And this thing: http://scratchblocks.github.io/v3/#define%20foo%0A(1)%20%2B%20(1)%0Afoo%0A%0Awhen%20gf%20clicked%0Afoo
define fooWeird.
(1) + (1)
foo
when gf clicked
foo
- NickyNouse
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
And this thing: http://scratchblocks.github.io/v3/#define%20foo%0A(1)%20%2B%20(1)%0Afoo%0A%0Awhen%20gf%20clicked%0AfooAll the parser knows is colors, and which blocks aren't stacks or reporters. It figres everything else out from contextdefine fooWeird.
(1) + (1)
foo
when gf clicked
foo
Also, going offtopic for a sec, but can we take a moment to appreciate these commit names out of context:

Last edited by NickyNouse (April 12, 2016 07:15:39)
- NickyNouse
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
The screenshot in the readme is missing the “Export SVG” link and the “by blob8108” subtitle
- blob8108
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
What's the syntax for multiline rings?
Can you make ◀ ▶ look black again?Both of these things will have to wait until the new parser in v3.1.
I'm glad you're happy about upvars

The screenshot in the readme is missing the “Export SVG” link and the “by blob8108” subtitleThanks, good catch!
- helloandgoodbye9
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
It's looking really gorgeous right now! I reported a few things. Are comments still being written? ‘Cause they break for me but idk if they’re just still in the works@NickyNouse Comments should work, yes. If not, that's a bug.Free standing comments don't work. Not only that, but if you write one, the screen no longer updates. Here is the link.
- Sigton
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
All worked well, apart form custom blocks turned out obsolete for me (The actual blocks not the definitions).Bump; seems to have been missed
Sigton

Sigton
- NickyNouse
-
Scratcher
1000+ posts
~scratchblocks~ discussion thread
Will you rework the generator and Nathan's spec to reflect the new parser? (IDK if the generator'll need to change, except to add slashes for escaped brackets)
Last edited by NickyNouse (April 12, 2016 16:08:38)
