In the next version of scratch. There should be several new blocks, one called "resist" http://scratch.mit.edu/forums/viewtopic.php?id=33213
another called "clock" and the last "translate" so people can make a translator.
The "when I recieve" block should also be in a boolean form just like the "when key []
pressed" is . It would look like this "when [] recieved". And also Build Your Own
Blocks should be intergrated into scratch, and all of the Squeak programs will
not be necessary and therefore people won't have to deal with all of the "v1.0"
bugs. And BYOB projects should be able to be put online.
Offline
The next version is going to be 2.0, not 1.5. And I don't think receiving a broadcast is something that can be true or false, use a variable, like this:
[blocks]<repeat until><( <{ stop }> <=> 1 )>
[DO STUFF]
<end>[/blocks]
Resist and Translate can be done by hand, just go look up for translators and platformers and look at their scripts. Being able to detect the time is a good idea though.
Last edited by technoguyx (2010-04-02 12:10:16)
Offline
But something like:
Translate () to [language]
would be awesome.
Offline
soupoftomato wrote:
But something like:
Translate () to [language]
would be awesome.
Maybe if it connected to a service like Dictionary.com it'd work.
Offline
A translator would be really hard to program and never translates correctly, so I don't think that's possible. A built-in version of BYOB would also be nice. A <when ___ received> block would be great but isn't possible (it seems like it could be a boolean, but for some reason it's not).
Scratch 2.0 is going to take about a year, so they're planning something pretty big.
Offline
hmnwilson wrote:
A translator would be really hard to program and never translates correctly, so I don't think that's possible. A built-in version of BYOB would also be nice. A <when ___ received> block would be great but isn't possible (it seems like it could be a boolean, but for some reason it's not).
Scratch 2.0 is going to take about a year, so they're planning something pretty big.
IT CAN BE A BOOLEAN
When will people ever learn...
Offline
BWOG wrote:
IT CAN BE A BOOLEAN
Maybe if the broadcast is received, a variable would be set to some value, activating the "when _ received" block. That's the only way it'd make sense I think.
Offline
technoguyx wrote:
The next version is going to be 2.0, not 1.5. And I don't think receiving a broadcast is something that can be true or false, use a variable, like this:
[blocks]<repeat until><( <{ stop }> <=> 1 )>
[DO STUFF]
<end>[/blocks]
Resist and Translate can be done by hand, just go look up for translators and platformers and look at their scripts. Being able to detect the time is a good idea though.![]()
Actually, the scratch team is deciding whether or not to go to Scratch 1.5 or skip to Scratch 2.0. Many things Qwertypower said can be done in some other form, but it would be much more better for scratch's philosophy of keeping the programming simple. So I agree with his ideas.
Offline
how about interactive lists?
you can press items on a list and use blocks to find last item pressed
if item (4) of [candy] is pressed are you sure you like (last pressed on [candy])
or,
if item (any) of [veggies] is pressed set x to (last pressed on [veggies])
Offline
BWOG wrote:
hmnwilson wrote:
A translator would be really hard to program and never translates correctly, so I don't think that's possible. A built-in version of BYOB would also be nice. A <when ___ received> block would be great but isn't possible (it seems like it could be a boolean, but for some reason it's not).
Scratch 2.0 is going to take about a year, so they're planning something pretty big.IT CAN BE A BOOLEAN
When will people ever learn...
OK...I quote both messages because I want to settle this argument.
It cannot be boolean
If it was boolean, the Scratch Team would have implemented the feature already.
Q.O.D.
Offline
mman2112 wrote:
how about interactive lists?
you can press items on a list and use blocks to find last item pressed
if item (4) of [candy] is pressed are you sure you like (last pressed on [candy])
or,
if item (any) of [veggies] is pressed set x to (last pressed on [veggies])
That's a good idea
Offline
BWOG wrote:
hmnwilson wrote:
A translator would be really hard to program and never translates correctly, so I don't think that's possible. A built-in version of BYOB would also be nice. A <when ___ received> block would be great but isn't possible (it seems like it could be a boolean, but for some reason it's not).
Scratch 2.0 is going to take about a year, so they're planning something pretty big.IT CAN BE A BOOLEAN
When will people ever learn...
He/she has a point but if he/she IS wrong then I think they could at least
make when recieved normal block
Offline
If you go to goggle.ca and go to "view" and then "source" you should see this at the
very top: <!doctype html><html onmousemove="google&&google.fade&&google.fade(event)">. The "onmousemove" part is what makes the menu at the top fade in to view.
A script in scratch that does the same thing would be very helpful to OS
developers (like me) for making screensavers.
Offline
qwertypower wrote:
If you go to goggle.ca and go to "view" and then "source" you should see this at the
very top: <!doctype html><html onmousemove="google&&google.fade&&google.fade(event)">. The "onmousemove" part is what makes the menu at the top fade in to view.
A script in scratch that does the same thing would be very helpful to OS
developers (like me) for making screensavers.![]()
If that's what makes the Web, Images, Videos, etc. buttons appear some seconds after you visit the page, you can do that with the ghost effect.
Offline
technoguyx wrote:
qwertypower wrote:
If you go to goggle.ca and go to "view" and then "source" you should see this at the
very top: <!doctype html><html onmousemove="google&&google.fade&&google.fade(event)">. The "onmousemove" part is what makes the menu at the top fade in to view.
A script in scratch that does the same thing would be very helpful to OS
developers (like me) for making screensavers.![]()
If that's what makes the Web, Images, Videos, etc. buttons appear some seconds after you visit the page, you can do that with the ghost effect.
No no I'm talking about the on mouse move part not the fade part.
The screensaver script would look like this:
when flag clicked
forever
if
mouse idle for [] seconds
broadcast []
And then the sccreensaver would start then this script would come along
when flag clicked
forever
on mouse move
broadcast []
I forgot to include the mouse idle part in my last post so I put here
Offline
you can do mouse idle by having a timer and a variable like this:
when flag pressed forever set "x1" to mouse x wait 0.001 seconds if mouse x NOT equal to "x1" reset timer. if timer > 50 broadcast start screensaver.
Offline
Lots of interesting ideas here! Keep in mind, the best way to make suggestions for Scratch is one per thread. Thinking it through and making a mockup helps everyone understand what the feature is, and how it works.
So, it's fine to brainstorm about lots of ideas on a thread, but when you get really excited about a particular one, check this page out:
http://info.scratch.mit.edu/Suggestions_for_Scratch
...and then make a mockup, and post a clear explanation of your idea in a new thread.
Offline
A lot of people do not realize that they can make their own blocks, right here.
PS: Credit to LS97 for making the tutorial.
Last edited by celloguy123 (2010-04-23 19:42:29)
Offline
Just make a meaningful script and read aloud block by block. You will see that it makes sense. It happens in case of all the blocks made by the scratch team. And if it doesnt, the script is not meaningful and wont work in case of a project. When something recieved in boolean just doesnt make sense.
Offline
celloguy123 wrote:
A lot of people do not realize that they can make their own blocks, right here.
PS: Credit to LS97 for making the tutorial.
But you can't upload them to the scratch server. Only your own server
Offline
It also needs hide and show list !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PPPPPPPPPPPPPPPPPPPPPPPPPPLLLLLLLLLLLLLLLLLLLLLLLLLLLLLEEEEEEEEEEEEEEEEEEEEEEEEEEEEAAAAAAAAAAAAAAAAAAAAAAAAAASSSSSSSSSSSSSSSSSSSSSSSSSSSSSSEEEEEEEEEEEEEEEEEEE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Offline
Daffy22 wrote:
A good idea I have would be to make a block to detect if the user is online or offline!
You can already do that.
I just forget how. There is a 1 sprite 1 script project that does that.
Offline
qwertypower wrote:
Daffy22 wrote:
A good idea I have would be to make a block to detect if the user is online or offline!
You can already do that.
I just forget how. There is a 1 sprite 1 script project that does that.
this is how:
[blocks]<when green flag clicked>
<set{ online? }to( no
<move( (( 0 </> 0 )) )steps>
<set{ online? }to( yes[/blocks]
the way it works is that scratch picks up the error of 0 divided by 0, but the Java applet ignores it.
Offline