So, I discovered scratch and have been doing some simple puzzle games as a stress reliever. Not wanting to copy sprites a bazillion times, the problem I had to overcome with a stamp based approach is that it's fairly challenging to get a color off the screen and store it, even though testing to see what's on the screen is pretty easy.
If there was a way to store a color in a variable, and test it against other stored colors, my projects would have been much simpler. I expect that you're trying to avoid having multiple data types in Scratch, but couldn't colors be stored as integer values (packed 24 bit, I'd assume)? Then, all it would take is a (color []) block in the sensing or numbers pane that would provide the standard color selector.
Also, I've seen a lot of comments about incorporating arrays, but my short experience with Scratch makes that seem like it would not integrate well with the visual designing. I think what I'd like to see is the ability to copy the current sprite, including it's current variables and their values. Then, in an odd sort of way, could solve the same kind of problems recursively and visually. I think that would also make it easier to take advantage of the inherently parrallel nature of scratch, as well.
Offline
color variables and string variables are high on my list of things needed.
I think that arrays are *more* important than dynamic sprite creation, though both would be valuable.
Offline
I'm not even particularly advocating for dynamic sprite creation in a general sense, as I think that would be rather complicated. I'm just hoping for an exact copy, sort of like a more complete version of stamp.
I agree that arrays would do much to make complicated projects easier, but is scratch really supposed to be worried about complicated projects?
Personally, I don't see much of a use for strings though, without extending the environment significantly to provide text input/output. It may just be because it's too close to my day job, but text parsing in scratch just sounds like a chore.
Offline
I think Helot has a good point advocating color variables in form of integers. This wouldn't even change the 'language' of Scratch but still allow for dynamic color settings and for 'wider walls'. One more vote for this!
Offline
One more vote for the color variable! That would simplify a lot of code.
I'd also like character string variables. I don't think they would be that hard to add to the environment, and they would open up a world of text-based games. But I suppose you'd have to have some way of parsing them out too which means a stable of string functions. Maybe it's too hard after all. How about in Scratch Pro? Different "skins" on the IDE depending on the level of the programer?
Offline
Another vote for the color variable! (seriously, that would be useful in a project I'm thinking of making.)
Offline
Paddle2See wrote:
One more vote for the color variable! That would simplify a lot of code.
I'd also like character string variables. I don't think they would be that hard to add to the environment, and they would open up a world of text-based games. But I suppose you'd have to have some way of parsing them out too which means a stable of string functions. Maybe it's too hard after all. How about in Scratch Pro? Different "skins" on the IDE depending on the level of the programer?
colour variable, another vote! and what about your screen colour, 32-bit or 16-bit?
Offline
likegames wrote:
Paddle2See wrote:
One more vote for the color variable! That would simplify a lot of code.
I'd also like character string variables. I don't think they would be that hard to add to the environment, and they would open up a world of text-based games. But I suppose you'd have to have some way of parsing them out too which means a stable of string functions. Maybe it's too hard after all. How about in Scratch Pro? Different "skins" on the IDE depending on the level of the programer?colour variable, another vote! and what about your screen colour, 32-bit or 16-bit?
Thank you for bumping this!!!!!!!!!!! I would love a circular block (that you could put in math blocks, lists, etc) for the pen color and maybe graphic effects (because you could always just store the costumes)
Offline
another vote!!!
[blocks]
((hi))
[/blocks]
Offline
Just a question, but what's wrong with using the block that goes like:
set pen color to (#number)
set color effect to (#number)
I don't exactly get the premonition. Do you mean that you want to use 24 bit colors instead of colors that range 1 to 200? Or do you want to be able to save a color as a variable, because that's possible.
Offline
open two (Make sure its two!) offline scratch program windows. shift click on the R in scratch while using the offline scratch program. press turn fill screen off then go to the white space and click. Then click on open. click on browser. Scratch objects. scriptablescratchmorph. then variables. click variableblockcolor. change the number for h:. right click and click on accept. click the x on the top of the green box and when it asks you if you want to save changes click yes. look at your new variable color!. WARNING: when you try to exit your Scratch window it will ask you if you want to save changes. click no or else the variable color will be permanent. If you do switch to the other scratch window I asked you to open. and shift click the R in scratch. click save image for end-user. open another scratch window to see if it worked.
Offline
Another vote! As Paddle2See said another version of Scratch with more advanced features would be good.
Offline
Yes! This would be great to have, especially if we also had a reporter block that reports a color the sprite is touching. (It would report which color the center of the sprite is touching, of course.)
Offline
yeah, I made a project ( http://scratch.mit.edu/projects/piguillaud/1439519 ) that took me alot of time to make... with a color variable, it would have taken only 20 minutes.
please look at it...
http://scratch.mit.edu/projects/piguillaud/1439519
http://scratch.mit.edu/projects/piguillaud/1439519
http://scratch.mit.edu/projects/piguillaud/1439519
http://scratch.mit.edu/projects/piguillaud/1439519
Offline