Scratch

I suggested this a long while ago:

http://scratch.mit.edu/forums/viewtopic.php?id=16220

Incidentally, I was just thinking it would be awesome if somebody modded Scratch for this 

coolstuff wrote:

I suggested this a long while ago:

http://scratch.mit.edu/forums/viewtopic.php?id=16220

Incidentally, I was just thinking it would be awesome if somebody modded Scratch for this 

That would be really good! And it help introduce people to the reality of programming with text.

But the block-based Scratch should be bigger! After all, Scratch is famous for its method of building with blocks.

A little feature for programming in text would be nice though.

I support. I love text and I can type super fast. But then there's mistyping problems... also, there's no help interface. The blocks function you can figure out from their text. Pure text that YOU type... not so sure. Still, I support.

ScratchReallyROCKS wrote:

helltank wrote:

I support. I love text and I can type super fast. But then there's mistyping problems... also, there's no help interface. The blocks function you can figure out from their text. Pure text that YOU type... not so sure. Still, I support.

Maybe it could sense syntax errors and prompt you to correct them before switching back to the block tab.

Absolutely! I think the syntax should be super-easy to understand, without any hashes, quotation marks, semicolons, or commas. I think maybe auto-correction of common typos and syntax errors (it's pretty easy to tell what you're trying to type with such a small library of commands) may be the best solution to get the errors out of the way from the start.

The mission of Scratch is to keep the programming simple. A lot of programming languages have these difficult to remember, inconsistent syntaxes which nobody really understands - as long as Scratch eliminates that and makes it simple to code, I think it's a great learning tool.

Ace-of-Spades wrote:

Weren't there some people working on a text based Scratch in python?

Yes - it was called "Emerald" (but I think the name got changed). I created one of the major versions of it (introducing variables), and while the discussion continued, I don't think any subsequent versions were released. I left Scratch shortly thereafter for a few months.

I think the difference between that and this suggestion is that this suggestion fully integrates "Text-Based Scratch" in with the current Scratch, whereas the other was a fully text-based program with commands similar to those of Scratch.

coolstuff wrote:

Ace-of-Spades wrote:

Weren't there some people working on a text based Scratch in python?

Yes - it was called "Emerald" (but I think the name got changed). I created one of the major versions of it (introducing variables), and while the discussion continued, I don't think any subsequent versions were released. I left Scratch shortly thereafter for a few months.

I think the difference between that and this suggestion is that this suggestion fully integrates "Text-Based Scratch" in with the current Scratch, whereas the other was a fully text-based program with commands similar to those of Scratch.

I'm Pretty sure it's called M30W now

coolstuff wrote:

ScratchReallyROCKS wrote:

helltank wrote:

I support. I love text and I can type super fast. But then there's mistyping problems... also, there's no help interface. The blocks function you can figure out from their text. Pure text that YOU type... not so sure. Still, I support.

Maybe it could sense syntax errors and prompt you to correct them before switching back to the block tab.

Absolutely! I think the syntax should be super-easy to understand, without any hashes, quotation marks, semicolons, or commas. I think maybe auto-correction of common typos and syntax errors (it's pretty easy to tell what you're trying to type with such a small library of commands) may be the best solution to get the errors out of the way from the start.

The mission of Scratch is to keep the programming simple. A lot of programming languages have these difficult to remember, inconsistent syntaxes which nobody really understands - as long as Scratch eliminates that and makes it simple to code, I think it's a great learning tool.

Yes! And why not syntax highlighting as well, like in the Python Idle interface? It'd make code easier to read and more obvious when you got something wrong, because the incorrect syntax would be in plain black text.

Last edited by Harakou (2010-08-26 10:28:40)

Ace-of-Spades wrote:

Harakou wrote:

coolstuff wrote:

Absolutely! I think the syntax should be super-easy to understand, without any hashes, quotation marks, semicolons, or commas. I think maybe auto-correction of common typos and syntax errors (it's pretty easy to tell what you're trying to type with such a small library of commands) may be the best solution to get the errors out of the way from the start.

The mission of Scratch is to keep the programming simple. A lot of programming languages have these difficult to remember, inconsistent syntaxes which nobody really understands - as long as Scratch eliminates that and makes it simple to code, I think it's a great learning tool.

Yes! And why not syntax highlighting as well, like in the Python Idle interface? It'd make code easier to read and more obvious when you got something wrong, because it would be in plain black text.

??
My python has lots of different colored text for different things o.O

...You do know which Python I'm talking about right?

Ace-of-Spades wrote:

Harakou wrote:

Ace-of-Spades wrote:

??
My python has lots of different colored text for different things o.O

...You do know which Python I'm talking about right?

Python 2.6 or 3.0 the programming language right?

Yeah. And I was talking about syntax highlighting-the colored text. Just to make sure we're on the same page. 

Ace-of-Spades wrote:

Harakou wrote:

Ace-of-Spades wrote:

Python 2.6 or 3.0 the programming language right?

Yeah. And I was talking about syntax highlighting-the colored text. Just to make sure we're on the same page. 

But you said the text was black. My text starts off as black but then switches to another color when it recognizes the function. Is it different versions?

No, I meant that the text with incorrect syntax would be black and easy to recognize.    Let me edit my original post...

Last edited by Harakou (2010-08-26 10:29:03)

Ace-of-Spades wrote:

Harakou wrote:

Ace-of-Spades wrote:

But you said the text was black. My text starts off as black but then switches to another color when it recognizes the function. Is it different versions?

No, I meant that the text with incorrect syntax would be black and easy to recognize.    Let me edit my original post...

Wait, you mean it gets highlighted black?

No, I mean that written code with correct syntax gets colored according to the type of command, but incorrect syntax doesn't get colored and is therefore black. Get it?