I use 1.2.1 because it is and unbugged versoin of 1.2 beta but you've taken away the comment block, why is that? I think it was a good idea because it's basicaly like having project notes about a single script.
If it bugged up the programme then keep it out but if it doesn't do anything to the scripts and it just ignores it, why not bring it back in 1.2.2?
Offline
There was a whole thread on the comment block under Advanced Topics. The short answer is that the Team was not happy with the comment block as it was causing confusion with some beginning programmers who thought it was supposed to affect program behavior somehow. So the Team is trying to come up with an approach to commenting that won't be confused.
I'm with you. I think the comment block was a very helpful feature...maybe not perfect but certainly a great deal better than the current alternatives. I wish they would put out a minor release and bring it back to life. Maybe we can circulate a Scratch based electronic petition and beg to have it put back in.
Here's the link to the topic in Advanced Topics:
http://scratch.mit.edu/forums/viewtopic.php?id=2359
Last edited by Paddle2See (2008-01-02 14:37:54)
Offline
For those not familiar with the comment block, there is a good example of its use in the School Pinball game: http://scratch.mit.edu/projects/kevin_and_abe/54377
Offline
i really dont think that comment block was very good. i knew what it was for and everything, but i thought it was just a waste of space.
Offline
funkymonkey, you would find it much easier to remix other people's programs if you could read and understand what they were doing. Comments are a big help in understanding what someone was attempting to do, so are very useful in debugging programs that aren't quite working, as well as for explaining programs that are working.
Offline
kevin_karplus wrote:
funkymonkey, you would find it much easier to remix other people's programs if you could read and understand what they were doing. Comments are a big help in understanding what someone was attempting to do, so are very useful in debugging programs that aren't quite working, as well as for explaining programs that are working.
cant you explain problems in the description of the project? thats what i do. but you are right about making it easier to remix projects
Offline
I think the scratch team has kept it (a little) Comments in projects can still be read, because the comment block shows and not the"obsolete". But if I import projects using comments the squeak debugger appears. commentBlockBlabla error. Import commentblala failed blabla
Offline
The project description is all located in one place, and has no way of referring to what specific scripts are supposed to do. If you have six scripts that all start with the same "when I receive " hat, how do you indicate which one does which action?
Properly, the project description should only have an *external* view of the project, with internal implementation details documented in each sprite. This becomes even more apparent when sprites are exported as separate objects.
Offline
comment blocks are a good and organized way to create a project and know what each script does. i think they are necessary because how are you supposed to memorize what each script does in a big project with many sprites and even more scripts?
Offline
OJY321 wrote:
I use 1.2.1 because it is and unbugged versoin of 1.2 beta but you've taken away the comment block, why is that? I think it was a good idea because it's basicaly like having project notes about a single script.
If it bugged up the programme then keep it out but if it doesn't do anything to the scripts and it just ignores it, why not bring it back in 1.2.2?
is this some thing to do with these?
<go back( )layers>
<point towards(
Offline