In order:

• I don't think it's too confusing. 1=1 is true; 1=0 is false.
  
• …
  
• You can, it just doesn't have a surrounding thingy (outline?) like it used to.
  
• I heard no. You can drag and copy it to the other sprites you want to use it in.
  
• It's on the list of 1001 items to add to 2.0.
  

Thanks!

I think the mimic for true and false is confusing to children, not us programmers who are quite used to that sort of logic! ;-)

Eeep! regarding the user-defined blocks. It would be *brilliant* to be able to define a jump block, for example, and then have all sprites access it. Is this something that could be looked at for the future? Perhaps making them global as you can with a variable?

Sure, the code comments are not a big deal.

It's looking fabulous though! Fantastic job :-D

IMO “While 1 is equal to 1” is a lot more obvious than “While true”.

I wasn't saying ‘while true’. I was passing a boolean parameter to a user defined block.
Your text to link here…

temboConsulting
Eeep! regarding the user-defined blocks. It would be *brilliant* to be able to define a jump block, for example, and then have all sprites access it. Is this something that could be looked at for the future? Perhaps making them global as you can with a variable?

Some of us on Scratch Team also really wanted a global “Make a Block”– but there were numerous questions we couldn't resolve in a simple enough way. One of those was that we couldn't agree on a good place to keep the definition – would it stay within one sprite and would that make sense and how would you find it again? Or get copied to all of them? What if one definition was then edited, would all of them change? How would you distinguish btwn local and global definitions? The definitions could be in a separate interface space but we wanted the process of creating the block part a seamless part of the creating and tinkering process in the scripts area, rather than a separate space. Also that makes them more visible for people reading the project.

I still hold out the hope of being able to right-click (Ctrl+click Mac) on a definition block and say “add to all sprites” so they each get a copy. And also on the right-click menu say “change all jump definitions to this” (or something like that) that would automatically take changed code for a hat with a common name and update in all sprites.

Well, for now we have the backpack for copying local definitions across sprites .

natalie
Well, for now we have the backpack for copying local definitions across sprites

Cool, didn't realize I could put scripts in the backpack. Which makes it simpler to copy scripts across projects. Of course maintaining my backpack without folders will be a challenge as I stuff all that stuff into it. Also there is an issue with the current implementation see description here. I was actually going to use sprites to store sets of scripts for re-use and to help organize my scripts in the backpack.

FYI, when I first saw “Make a Block” I assumed it would be “made” and I would not have to remake or copy it.

So it seems like you are trying to make this more of a Samurai coding environment where to quote Dan Ingalls “The Samurai knows where he is going and our job is to clear all the obstructions out of his way.” And having to re-create or copy tools/scripts each time, seems to me an obstruction. We want kids to focus on creating and expressing ideas (easy to say, hard to do).

Anyway, regarding the issue of “where oh where” to put the definition (and I'm sure you've thought about this before) what about on the Server? Then once you make a block, you have the option of making it persistent in the GUI (with a visual clue that it is a persistent block). Of course this implies that when you change the definition, you change it everywhere and I would want to be able to re-arrange the order of the persistent blocks.


Obviously I need to think about this more. So as I like to drop the names of famous people and quote them I will leave you with one more, the advise from my Great Aunt Suslie - “I wish you lots of luck”

-InsanityPlays- wrote:

BUNP.

Why?

Please create a separate topic for each suggestion you have, rather than creating a list of suggestions. That way, the conversation stays focused and each idea can get the attention it needs.

Before making a new topic, please check out the following:

• The Official List of Rejected Suggestions. If your suggestion is in this list, please do not make a new topic about it, as it will not be implemented anyway.
  
  
• The Suggestions Directory. If your suggestion is in this list, please continue the discussion in the existing topic, rather than making a new topic.
  

Thank you!