Pages: 1
Topic closed
This is not a scientific poll, as it is for referencing sources on the Scratch Wiki. Please answer in a way that abides to these guidelines. Thanks.
The Scratch Wiki needs reference sources, so I'm going to create a series of polls to check the info, then reference it with this.
THE PAGE: Next Costume (block)
THE STATEMENT: "Many users have made suggestions about removing this block, insisting that its alternative is perfectly fine to use, however, others have disagreed saying that it saves lots of time and is handy for animation."
THE QUESTION: Would you want the Next Costume block abolished? Why or why not?
Your input helps keep the information correct and up to date, and gives it a source to go by. Thanks!
If this little poll actually works out, I'll make some more.
Offline
Well, I do agree that it does save time, and it is helpful in reducing confusion. For example, a new scratcher isn't necessarily going to know how to get to the next costume, though this provides a nice, simple way of doing that. However, it can be replicated and that's needed information in some more complex projects. What pushes me over is that this nice feature can be useful at times because it creates a cleaner scripting area and is easy to understand, which when combined with the above benefits, it becomes a "neat little feature". Therefore, I say that it should be kept.
With regards,
ErnieParke
Offline
I vote that we should keep the "next costume" block.
This is mainly because it definitely helps save time and makes the script area less congested and stuff. It helps me when I'm creating animations, because I don't have to constantly pick the costume a sprite has to switch to. Getting rid of it won't, as far as I'm concerned, necessarily help anyone. It will prove a greater stumbling block for creating a smooth animation. The "switch to 'x' costume" box is only for when you don't want certain costumes to be shown at that given time
Sincerely,
18yuj
(aka normal_girl XD)
Offline
I think it's so useful that I'd go as far as saying that there should be a previous costume block and a change costume by block.
Offline
Meh. I don't particularly care either way, I mean, it's useful, but I personally rarely use it and the work around is more verbose.
Offline
How about
change costume # by (3)
Offline
Laternenpfahl wrote:
How about
change costume # by (3)
Well, in 2.0, you can do this:
define next costume (count) repeat (count) next costume end
Offline
Let's not forget, that Scratch is a programming language designed to introduce children to programming, without going through much of the hassle involved in learning to use an actual programming enviroment.
Do you really think some 5 year old (as we have users this young in this very website), just starting to use Scratch, possibly with no access to an Internet connection to ask for help, will be able to figure out something like [set costume to ((costume #) + [1])], as trivial as it may be to us?
Keep it.
Offline
I think that we should abolish this, or create another block.
What's the second option?
Well, I think that the "next costume" block feels out of place, so I suggest creating a "previous costume" block to make it less lonely!
Offline
technoguyx wrote:
Let's not forget, that Scratch is a programming language designed to introduce children to programming, without going through much of the hassle involved in learning to use an actual programming enviroment.
Do you really think some 5 year old (as we have users this young in this very website), just starting to use Scratch, possibly with no access to an Internet connection to ask for help, will be able to figure out something like [set costume to ((costume #) + [1])], as trivial as it may be to us?
Keep it.
+10
Offline
I really really really really want it to stay.
Offline
Thanks for your replies! I think this is enough feedback to work by, so I'm requesting this topic to be closed now.
Scratch on!
Offline
Closed by request of the topic owner.
Offline
Topic closed
Pages: 1