Futurebot5 wrote:

TOLORS wrote:

2.3 Set the editor to look like older versions of Scratch
Some users prefer the look and feel of the Scratch 2.0 editor, and have suggested that the editor look like Scratch 2.0, but still run off of HTML5 like Scratch 3.0 does. However, this would be more complicated for educational and documentation purposes. It could be confusing if someone is trying to learn Scratch from someone who is using a completely different layout of the editor than them.

In addition, the Scratch Team changed the design for a reason: to make it easier, more intuitive, and friendlier for newcomers to use. If you dislike the Scratch 3.0 editor, you can still download the Scratch 1.4 or Scratch 2.0 offline editors.

That also applies to this suggestion.

Futurebot5 wrote:

the2000 wrote:

Futurebot5 wrote:

I think this would be rejected for the same reason as a 2.0 or 1.4 style.

How is this related to that at all?

TOLORS wrote:

2.3 Set the editor to look like older versions of Scratch
Some users prefer the look and feel of the Scratch 2.0 editor, and have suggested that the editor look like Scratch 2.0, but still run off of HTML5 like Scratch 3.0 does. However, this would be more complicated for educational and documentation purposes. It could be confusing if someone is trying to learn Scratch from someone who is using a completely different layout of the editor than them.

In addition, the Scratch Team changed the design for a reason: to make it easier, more intuitive, and friendlier for newcomers to use. If you dislike the Scratch 3.0 editor, you can still download the Scratch 1.4 or Scratch 2.0 offline editors.

That also applies to this suggestion.

Za-Chary wrote:

I'll be honest, this looks cool. Somewhat unnecessary, but it's still cool.

I'm also here to confirm that this is not rejected (before anyone tries saying otherwise).

mybearworld wrote:

Greg8128 wrote:

No support, this isn't a good way to teach how Scratch code corresponds to code in other languages. The difference between Scratch, JavaScript and Python isn't just syntax. If code written in Scratch was translated literally to Python code then the result would be very bad Python code. Same goes with JavaScript and basically every other language out there.

Give some examples, please

• Most programming languages have local variables. Scratch does not. In Scratch, each variable exists only once in each sprite. If you want local variables, you must create your own stack.
  
• Most programming languages allow functions to return a value (think custom reporters). Scratch does not. You must create your own system for managing return types.
  
• Most programming languages have efficient implementations for sets and maps. Scratch does not. You must implement your own efficient implementation or use the inefficient workarounds:
  

  <[values v] contains [thing] ?>
  (item (item # of ( thing ) in [keys v] :: list)  of [values v] :: list)

• Most programming languages have support for dynamic memory allocation. Some even have automatic garbage collection. Doing the first in Scratch is hard, doing the second in Scratch is very hard.
  

the2000 wrote:

You could say the same thing about adjusting the block colors but they added that to Scratch 2.0 anyway.

the2000 wrote:

Futurebot5 wrote:

TOLORS wrote:

2.3 Set the editor to look like older versions of Scratch
Some users prefer the look and feel of the Scratch 2.0 editor, and have suggested that the editor look like Scratch 2.0, but still run off of HTML5 like Scratch 3.0 does. However, this would be more complicated for educational and documentation purposes. It could be confusing if someone is trying to learn Scratch from someone who is using a completely different layout of the editor than them.

In addition, the Scratch Team changed the design for a reason: to make it easier, more intuitive, and friendlier for newcomers to use. If you dislike the Scratch 3.0 editor, you can still download the Scratch 1.4 or Scratch 2.0 offline editors.

That also applies to this suggestion.

You could say the same thing about adjusting the block colors but they added that to Scratch 2.0 anyway.

Edit: Ayy, king of the page!

Maximouse wrote:

the2000 wrote:

You could say the same thing about adjusting the block colors but they added that to Scratch 2.0 anyway.

You could even say that about different languages.

I rate this suggestion a [5 v] out of [5]. ::hat #5CB712
I support. ::#2CA5E2
comment: [This would help people learn what the Scratch blocks (not talking about the forum tag) equal in other programming languages. ]
 -TheGlassPenguin ::cap #4A6CD4 

Futurebot5 wrote:

It is not likely that people in the same class would have different language settings.

Maximouse wrote:

rebot5 wrote:

rebot5 wrote:It is not likely that people in the same class would have different language settings.

It is not likely that only some would have PyMode either.

Futurebot5 wrote:

Maximouse wrote:

rebot5 wrote:

rebot5 wrote:It is not likely that people in the same class would have different language settings.

It is not likely that only some would have PyMode either.

Would it be likely only some people would have 2.0 mode? No. Did they reject it? Yes.

Basic88 wrote:

No support. You can use leopard

Rendangbike2 wrote:

Basic88 wrote:

No support. You can use leopard

Leopard doesn't use blocks, It uses a modified JS, The only thing close to this is EduBlocks but it's in Python.

Basic88 wrote:

Rendangbike2 wrote:

Basic88 wrote:

No support. You can use leopard

Leopard doesn't use blocks, It uses a modified JS, The only thing close to this is EduBlocks but it's in Python.

What the OP wants to do is create something that will help users advance to other languages. Leopard already does that.

Rendangbike2 wrote:

Leopard doesn't use blocks, It uses a modified JS,

mybearworld wrote:

But I think we can create a mode called “PYMode” where you would still have drag'n'drop, but it would look more like a real programming language:

TheGlassPenguin wrote:

I rate this suggestion a [5 v] out of [5]. ::hat #5CB712
I support. ::#2CA5E2
comment:
[This would help people learn what the Scratch blocks (not talking about the forum tag) equal in other programming languages. ]::stack
 -TheGlassPenguin ::cap #4A6CD4 

Greg8128 wrote:

• Most programming languages have local variables. Scratch does not. In Scratch, each variable exists only once in each sprite. If you want local variables, you must create your own stack.
  
• Most programming languages allow functions to return a value (think custom reporters). Scratch does not. You must create your own system for managing return types.
  
• Most programming languages have efficient implementations for sets and maps. Scratch does not. You must implement your own efficient implementation or use the inefficient workarounds:
  

  <[values v] contains [thing] ?>
  (item (item # of ( thing ) in [keys v] :: list)  of [values v] :: list)

• Most programming languages have support for dynamic memory allocation. Some even have automatic garbage collection. Doing the first in Scratch is hard, doing the second in Scratch is very hard.
  

• The following looks like a regular Python function call.
  

  self.say\("[Hello, world]"\) :: looks

  However, as soon as you put a reporter in it, it stops looking correct.
  

  self.say\("(my variable)"\) :: looks

  This looks like it'll print the literal text my variable, as opposed to the value of the variable. This is probably fixable, but would make this mode a lot more difficult than just a locale change.
  
• I'm not sure if Python is the best language to use for this?