This is a poll. All in favor of bringing back the comment block, say Yes, all not in favor, say No. (I say yes) If you want, you can say why you want (or don't want) it back in your post.
Current score:
Yes 9
No 0
Last edited by Axeblade (2008-02-04 00:48:07)
Offline
Everyone wants it - just some want it more than others and some want it yesterday!
We are just waiting for the Scratch team to do it.
regards
Simon
Offline
You can put me down for a "Yes!". However, as SimpleScratch implies, I'm pretty sure the Scratch team is aware of our desires; now we just need to be patient and wait for them to do it.
I do hope that discussions such as this will help the team prioritize their resources and put Commenting on the top of their "to-do" list. It's painful to not have a feature - it's far worse to have had it for a little while and then to lose it.
Offline
By all means, sure: Let's have it (again)! And while you're at it: Please make Scratch translate all native language comments seamlessly to any other language (just kidding), lest I have to figure out English comments on my own (again just kidding).
Offline
Comments are very useful in code. Without them it's very difficult to organize your code in larger programs.
Offline
I think most people agree that they would like "a" comment block. The problem is, what should it look like and how should it work? I think there's a long thread about it elsewhere, but if I remember right the main problem with the beta version was that young programmers expected the block to do something ("it says 'comment', and I want my sprite to make a comment, but it's not working?"), and thus it was confusing. I expect that John and the team will come up with something, if only to stop Kevin from complaining about it
Offline
I triple the idea to redesign Scratch. First of all, I do not think that the "timer" block belongs in the sensing category. I think maybe it should maybe go into the control category. Or maybe a category of its own, with new ideas. Here are some ideas for the timer block:
1) A pause block
2) a resume block
3) a change timer by: block
But, I'll stick to topic. I am very upset that they got rid of the comment block. There should be a category of its own with different types of new blocks. That would be useful. Count another vote for "yes".
Offline
yes but like this:
|||||||||||||||
"coment"||
||
||
|||||||||||||||
Last edited by Heybrian (2008-02-03 14:24:05)
Offline
@MITScratcher
relyt12101 meant the Scratch Team's desire to re-design the comment block not the whole of scratch
regards
Simon
Offline
SimpleScratch wrote:
@MITScratcher
relyt12101 meant the Scratch Team's desire to re-design the comment block not the whole of scratch![]()
regards
Simon
Yes that is what I meant. But some of what you said, MITscratcher, contains great ideas! You should re-post that on the suggestions board.
Offline
You kind of can already simulate a comment block by using the <say[ ] block not the <say[ ]for( )secs> block and put right next to the codes.
Offline
Oldschooler2 wrote:
You kind of can already simulate a comment block by using the <say[ ] block not the <say[ ]for( )secs> block and put right next to the codes.
Yeah, unless you use the Clean Up feature to align all your scripts neatly, if you do that the comments get moved away from the script they are refering to. I use Clean Up all the time
Offline
At the moment, where necessary I am using a say command inside a Repeat 0 loop, immediately above the blocks it is refering too.
Offline
Even more terse than the repeat 0 approach is to use
say "comment text" for 0 secs
The only disadvantages of this relative to the real comment block are
1) you have to make your comment only one line.
2) it is confusing to use a "say" block which normally does something to do nothing.
Offline
YES!!!!!!!! i hope they get it done soon!
Offline
i hope they put it back like it used to be!
Offline
I vote in favor of a comment block, despite being a Scratch newbie (unfamiliar with the 'old' comment block) and non-programmer.
But the Scratch team seems so talented, that I have a related suggestion: when right-clicking blocks, a popup now appears; add a 'comment-out' choice that would disable the block and make it gray. Sure, it's easy to drag blocks out, but not always so easy to know where they belonged.
Thanks for Scratch, it's awesome!
Last edited by dagnew (2008-02-07 17:10:57)
Offline
dagnew wrote:
But the Scratch team seems so talented, that I have a related suggestion: when right-clicking blocks, a popup now appears; add a 'comment-out' choice that would disable the block and make it gray. Sure, it's easy to drag blocks out, but not always so easy to know where they belonged.
This is an interesting and novel suggestion! It would help a lot in debugging to have the ability to quickly turn sections of the script "Off" and see how program behavior is impacted. This can be accomplished currently by tearing the script apart, howerver, if it is a long and complicated script, this can lead to other errors when it is reassembled.
If such a feature were implemented, it would have to be made very clear that particular code sections were turned "Off" otherwise it would be a major source of confusion.
Offline
Go to scrolling done right by archmage. It has comment blocks that you guys can pirate!
I don't see why they can't. Many other programming languages have them.
Offline
ooogabooga wrote:
Go to scrolling done right by archmage. It has comment blocks that you guys can pirate!
I don't see why they can't. Many other programming languages have them.![]()
If you really want to use comment blocks that badly, you could just install the old beta version of scratch.
http://scratch.mit.edu/pages/beta
Offline
I can't say no, because it is a great idea, but I cannot say yes, because you do not need comment blocks just do this:
<repeat( 0 )
<say[ Whatever you want ]
<say[ Next line ]
<say[ Next line and repeat (see, you do not need one single row silly)
<end>
My point.
Last edited by Lucario621 (2008-02-13 19:31:39)
Offline