Scratch

rdococ wrote:

Actually, I was refering to if we could create blocks the shape of [the script], not having those inputs.

I'm not sure what you mean by "not having those inputs."  You mean, you want a C-shaped block that doesn't include the "Input names" option?  Because "the shape of [the script] is otherwise just a plain C-shaped block.  You can make a block that has one C-shaped input and in its definition, put the variable oval from the prototype into a THE SCRIPT block.  If that's not what you mean, you'll have to draw me a picture or something.

bharvey wrote:

rdococ wrote:

Actually, I was refering to if we could create blocks the shape of [the script], not having those inputs.

I'm not sure what you mean by "not having those inputs."  You mean, you want a C-shaped block that doesn't include the "Input names" option?  Because "the shape of [the script] is otherwise just a plain C-shaped block.  You can make a block that has one C-shaped input and in its definition, put the variable oval from the prototype into a THE SCRIPT block.  If that's not what you mean, you'll have to draw me a picture or something.

That THE SCRIPT block has no bumps or holes to let it snap, I think you should give us a way to build a block the exact shape and behaviour as the block THE SCRIPT. The reason is that a C-shaped input in a reporter has buggy graphics, and with the shape of THE SCRIPT be able to be chosen, that graphic bug could have a solution for our custom blocks too.
EDIT: By behaviour I mean how it reports, does it report or do something, and stuff like of a THE SCRIPT-shaped block that reports "nil" expect what it reports and what it does and it having no inputs, every block type should allow every input availible from BYOB right now.

Last edited by rdococ (2011-05-10 07:12:30)

rdococ wrote:

The reason is that a C-shaped input in a reporter has buggy graphics, and with the shape of THE SCRIPT be able to be chosen, that graphic bug could have a solution for our custom blocks too.

Oh, I see, it's the rounded ends of custom reporters that you don't like.  I never noticed that THE SCRIPT wasn't like custom reporters.  Arguably it's THE SCRIPT that's wrong, since primitive reporters do have rounded ends.

I don't rhink it's a good idea to support two different shapes for custom reporters; that would confuse people trying to figure out the semantic difference between them when there isn't any.  But maybe all custom reporters should look like THE SCRIPT.  I admit I don't like the wasted space when I nest custom reporter calls and the blocks get fatter and fatter as they get taller.

My proposed solution is to change both THE SCRIPT and custom blocks  to the same new shape: rounded ends, but with the radius of curvature reduced as the block gets taller, so that the ends stick out by a constant amount, namely the same as a primitive (non C clotted) reporter block.

bharvey wrote:

rdococ wrote:

The reason is that a C-shaped input in a reporter has buggy graphics, and with the shape of THE SCRIPT be able to be chosen, that graphic bug could have a solution for our custom blocks too.

Oh, I see, it's the rounded ends of custom reporters that you don't like.  I never noticed that THE SCRIPT wasn't like custom reporters.  Arguably it's THE SCRIPT that's wrong, since primitive reporters do have rounded ends.

I don't rhink it's a good idea to support two different shapes for custom reporters; that would confuse people trying to figure out the semantic difference between them when there isn't any.  But maybe all custom reporters should look like THE SCRIPT.  I admit I don't like the wasted space when I nest custom reporter calls and the blocks get fatter and fatter as they get taller.

My proposed solution is to change both THE SCRIPT and custom blocks  to the same new shape: rounded ends, but with the radius of curvature reduced as the block gets taller, so that the ends stick out by a constant amount, namely the same as a primitive (non C clotted) reporter block.

THE SCRIPT is like a block reporter; the original reporter was only made for numbers. I'd recommend one for numbers, one for text, and one for blocks.

bharvey wrote:

scimonster wrote:

THE SCRIPT is like a block reporter; the original reporter was only made for numbers. I'd recommend one for numbers, one for text, and one for blocks.

Rounded ends go with rounded input slots?  That's an interesting idea, but in fact the Scratch reporter blocks for text (JOIN etc.) are rounded too.  We've been trying to avoid gratuitous incompatibilities with Scratch.

I wouldn't mind if blocks that report blocks or scripts had grey borders, though! 

I know, but that's because it originally was only numbers. I might even suggest this for Scratch 2.0!
EDIT: Make a Text Reporter Block! :D

Last edited by scimonster (2011-05-10 13:30:01)

bharvey wrote:

scimonster wrote:

I might even suggest this for Scratch 2.0!

Well if you talk them into it, then try us again! 

P.S.  I just now figured out that the difference in shape between THE SCRIPT and other reporters is the reason why the left corners of THE SCRIPT stick out when you do

[[THE SCRIPT <...>] OF <sprite23>]

We should definitely fix that!

The reporter blocks with C inputs look huge and take up a lot of space. In fact, I'd prefer it if reporters with C inputs look like the [THE SCRIPT []] blocks.

Wow. You've actually (sort of) reached the point where you can talk about aesthetics! 
That's great!

One thing that bothers me is the color scheme. The gray background should be lightened, IMHO. 

bharvey wrote:

One thing that bothers me is the color scheme. The gray background should be lightened, IMHO. 

Jens's department. 

Are you talking about the script pane's background or about the grey border around reified blocks? I don't much like the grey border around lambdafied blocks either, but so far we haven't come up with a better visualization of "quoting" something or turning a block into a "thing". Personally, I would like to "enchant" blocks and somehow indicate that "enchanted" blocks are "gems" with encapsulated super powers. Any ideas?

Last edited by Jens (2011-05-12 03:51:39)

Jens wrote:

Are you talking about the script pane's background or about the grey border around reified blocks?

Both. 
I have no idea how I'd better represent the grey borders... I'll think on it though.

Taneb wrote:

Found an error. It's possible to remove the "the script" and the "the block" blocks off of the pallete by right-clicking them and saying delete. They re-appear when you leave and re-enter the operators category, though

Thanks!  I think this one will just automatically be fixed in the rewrite this summer. 

knubee wrote:

there does not seem to be a way in "standard" Scratch to convert text input (typed by the user) into a separated list.

Does BYOB support this in some way? I am thinking of something quite minimal which assumes that spaces are separators for assigning typed words as separate list elements.

In the tool package (tools.ypr or ToolSprite.ysp in the BYOB folder) there's a block SENTENCE->LIST that does what you want.

i have a question... how do you get into the byob browser?