This is a read-only archive of the old Scratch 1.x Forums.
Try searching the current Scratch discussion forums.

#1 2010-06-27 03:23:33

ihaveamac
Scratcher
Registered: 2007-09-22
Posts: 1000+

Some blocks that should not be added to Scratch 2.0

All these ideas were taken from Block idea projects for Scratch 2.0.
If you can explain why and how a block can be added, and all the others agree, I'll remove it from the list.

"Go to [url]" - Virus and Adult stuff alert!

"When Stop Clicked" - Stop stops all scripts. How will this work differently?

"Repeat for (secs) seconds" - Self-explanatory.

"Hide speech bubble" - Use "Say [(no input)]".

"Point away from edge" - The sprite will just face another edge.

"If <> then <> else <>" - What the heck is this supposed to mean?

"Color touching [sprite]" - Use "Touching color [color]".


~ihaveamac - visit ihaveamac.net

Offline

 

#2 2010-06-27 03:58:22

keikij
Scratcher
Registered: 2009-02-22
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

If <> then <> else <> being the same as

[block]<if>
<else>[/block]

is a better reason.

Also, "when stop clicked" could be used to do 1 quick thing before it ends the project. For example, if it's a virtual ChatBot thing, this might be useful:
(When Stop Clicked]
[Say "Bye!"]

Or something like that.

Last edited by keikij (2010-06-27 03:59:01)


Back from the Dead (And Stuff)

Offline

 

#3 2010-06-27 04:00:52

ihaveamac
Scratcher
Registered: 2007-09-22
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

1. It means If bool then bool else bool

2. I meant as in it stops all scripts. It might take a lot of programming to make it run.


~ihaveamac - visit ihaveamac.net

Offline

 

#4 2010-06-27 04:48:42

juststickman
Scratcher
Registered: 2009-05-31
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

"Go to [url]" - Virus and Adult stuff alert!

"When Stop Clicked" - Stop stops all scripts. How will this work differently?

"Repeat for (secs) seconds" - Self-explanatory.

"Hide speech bubble" - Use "Say [(no input)]".

"Point away from edge" - The sprite will just face another edge.

"If <> then <> else <>" - What the heck is this supposed to mean?

"Color touching [sprite]" - Use "Touching color [color]".

1. Virus and adult stuff alert? Seriously... That's not a good enough reason to stop what could be a great feature. If you say this, why not stop all links?

2. It starts new scripts. I agree with this, stop all is supposed to stop the program.

3. I don't get how it's self explanatory

4. Makes sense.

5. Agreed.

6. Agreed.

7. No, that won't work. Sprites can be more than one color, what if a color is also used in another sprite? You'd have to have very weird looking graphics for this one to make sense.


http://is.gd/iBQi2 Add grob to your sig and help with world dominiation!http://is.gd/iBQ9Q                                                             Hey guys, we're seriously naming our team bob?

Offline

 

#5 2010-06-27 06:47:16

Jonathanpb
Scratcher
Registered: 2008-07-25
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

juststickman wrote:

1. Virus and adult stuff alert? Seriously... That's not a good enough reason to stop what could be a great feature. If you say this, why not stop all links?

Here on the Scratch Forums and website, we can choose if we click on the links or not. In the Scratch project, the website will automatically appear without our choice.

juststickman wrote:

3. I don't get how it's self explanatory

If the block is still operating while all the seconds are used up, what happens? It doesn't work.

big_smile


"Human beings... must have action; and they will make it if they cannot find it.
-Charlotte Brontë

Offline

 

#6 2010-06-27 08:06:58

climber59
Scratcher
Registered: 2009-12-15
Posts: 100+

Re: Some blocks that should not be added to Scratch 2.0

The last block lets you choose the sprite and color instead of a color and the sprite it's in. But it can be done with variables.


Check out my projects if you have a chance.

Offline

 

#7 2010-06-27 08:12:17

colorfusion
Scratcher
Registered: 2009-10-03
Posts: 500+

Re: Some blocks that should not be added to Scratch 2.0

<Touching stamp of>
<I receive [  ]>
<I have received [ ]>
[Clear stamps of [Sprite1]]
[Clear pen of [Sprite2]]
[Comment [__]]

Offline

 

#8 2010-06-27 09:36:46

coolstuff
Community Moderator
Registered: 2008-03-06
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

"Go to [url]" - Virus and Adult stuff alert!

You could make it so that it can only go to pages within the Scratch website... Although that might sort of defeat the purpose of the block.

"When Stop Clicked" - Stop stops all scripts. How will this work differently?

Yeah, it doesn't make sense to me. The "Stop" button is supposed to stop all of the scripts. When somebody presses that button, they expect it to stop - wouldn't it kind of defeat the purpose of the stop sign?

"Repeat for (secs) seconds" - Self-explanatory.

I think this should be added. It would make a great addition  smile  When the time's up, why shouldn't it just finish its loop?

"Hide speech bubble" - Use "Say [(no input)]".

Yes, you can already do that - two blocks that say the same thing? Kind of pointless.

"Point away from edge" - The sprite will just face another edge.

I've never heard this suggestion... And frankly, it makes no sense. The edges are surrounding you on all angles.

"If <> then <> else <>" - What the heck is this supposed to mean?

It's basically another way to write if <> else, there's just another word in there. There should still only be two booleans. I don't see the point, though.

"Color touching [sprite]" - Use "Touching color [color]".

Yep. Pointless.

Offline

 

#9 2010-06-27 09:51:14

mariobrosrule
Scratcher
Registered: 2008-06-09
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

ihaveamac wrote:

All these ideas were taken from Block idea projects for Scratch 2.0.
If you can explain why and how a block can be added, and all the others agree, I'll remove it from the list.

"Go to [url]" - Virus and Adult stuff alert!......fine

"When Stop Clicked" - Stop stops all scripts. How will this work differently?.......not very smart so take it out

"Repeat for (secs) seconds" - Self-explanatory.............fine

"Hide speech bubble" - Use "Say [(no input)]"...........taken out

"Point away from edge" - The sprite will just face another edge.........lol take it out

"If <> then <> else <>" - What the heck is this supposed to mean?..........shorter, but harder to understand

"Color touching [sprite]" - Use "Touching color [color]"........keep it, one color touches the WHOLE sprite.....

look above, i added stuff

Last edited by mariobrosrule (2010-06-27 09:52:11)

Offline

 

#10 2010-06-27 12:06:46

fullmoon
Retired Community Moderator
Registered: 2007-06-04
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

Jonathanpb wrote:

Here on the Scratch Forums and website, we can choose if we click on the links or not. In the Scratch project, the website will automatically appear without our choice.

If there ever was any sort of URL connectivity in Scratch...*fingers crossed*...then I'm sure the Scratch team would take plenty of precautions in how it worked. For instance, the Scratch player could include a Flash-style dialog box:

http://i.zdnet.com/blogs/flash_camera_privacy.png

Instead of warning about camera access, it would ask something like this:

The project is trying to access the URL:
http://windows-security-panel-2010.info/get?m=not_a_virus

[ ] remember my choice
(Allow) (Deny) (Report)

That would give the user the same choice they have when clicking other links.


http://i302.photobucket.com/albums/nn100/fullmoon32/wow.jpg

Offline

 

#11 2010-06-27 13:02:19

fullmoon
Retired Community Moderator
Registered: 2007-06-04
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

ihaveamac wrote:

"If <> then <> else <>" - What the heck is this supposed to mean?

I think a block like that would be useful. It would shorten scripts like this:
http://img714.imageshack.us/img714/761/boringifelse.gif
Into this:
http://img163.imageshack.us/img163/3362/ifelsereporter.gif


http://i302.photobucket.com/albums/nn100/fullmoon32/wow.jpg

Offline

 

#12 2010-06-27 13:36:46

The-Whiz
Scratcher
Registered: 2007-07-09
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

I see what the (if <> then [] else []) block does now... Thanks fullmoon.

Offline

 

#13 2010-06-27 14:08:09

ihaveamac
Scratcher
Registered: 2007-09-22
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

The if thing means

If <BOOL> then <BOOL> else <BOOL>


~ihaveamac - visit ihaveamac.net

Offline

 

#14 2010-06-27 14:32:32

fullmoon
Retired Community Moderator
Registered: 2007-06-04
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

ihaveamac wrote:

The if thing means

If <BOOL> then <BOOL> else <BOOL>

Well, you can put any value into the second two slots.


http://i302.photobucket.com/albums/nn100/fullmoon32/wow.jpg

Offline

 

#15 2010-06-27 14:34:45

The-Whiz
Scratcher
Registered: 2007-07-09
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

How would that work then?

if <mouse down> then <touching mouse-pointer> else <y position=0>

It doesn't seem like that would serve any purpose...  hmm

Offline

 

#16 2010-06-27 15:57:11

fullmoon
Retired Community Moderator
Registered: 2007-06-04
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

The-Whiz wrote:

How would that work then?

if <mouse down> then <touching mouse-pointer> else <y position=0>

It doesn't seem like that would serve any purpose...  hmm

Actually it might be helpful for choosing which boolean you want to test...

Code:

if < if <level = 1> then <touching [level 1 enemy] ?> else <touching [level 2 enemy] ?>>>:
  change health by -1
end

...however it's still quite useless if it allows only booleans.


http://i302.photobucket.com/albums/nn100/fullmoon32/wow.jpg

Offline

 

#17 2010-06-27 15:59:43

The-Whiz
Scratcher
Registered: 2007-07-09
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

But couldn't you do the same thing with "< < <BOOL> and <BOOL> > or <BOOL> >"?

Offline

 

#18 2010-06-27 20:02:20

climber59
Scratcher
Registered: 2009-12-15
Posts: 100+

Re: Some blocks that should not be added to Scratch 2.0

No, because if the first is true and the second is false it would report false, the and/or thing would report the third boolean.


Check out my projects if you have a chance.

Offline

 

#19 2010-06-28 01:19:44

technoguyx
Scratcher
Registered: 2008-10-18
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

You could use this:

[blocks]<if> bool
<if> bool
stuff
<end>
<else>
<if> bool
stuff
<end>
<end>[/blocks]

ihaveamac wrote:

"Repeat for (secs) seconds" - Self-explanatory.

Why not?


http://getgnulinux.org/links/en/linuxliberated_4_78x116.png

Offline

 

#20 2010-06-28 07:07:39

climber59
Scratcher
Registered: 2009-12-15
Posts: 100+

Re: Some blocks that should not be added to Scratch 2.0

Unless you add a variable that will not work because the <if<> then<> else<>> block is a boolean as well.

Last edited by climber59 (2010-06-28 07:07:46)


Check out my projects if you have a chance.

Offline

 

#21 2010-06-28 08:58:41

The-Whiz
Scratcher
Registered: 2007-07-09
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

I can't see any user for that block, if it was all booleans.  hmm  Wouldn't it just be the same thing as <<BOOL> and <<BOOL> or <BOOL>>>?

Offline

 

#22 2010-06-28 09:06:45

Jimmy-Jermaine
New Scratcher
Registered: 2010-06-25
Posts: 100+

Re: Some blocks that should not be added to Scratch 2.0

ihaveamac wrote:

All these ideas were taken from Block idea projects for Scratch 2.0.
If you can explain why and how a block can be added, and all the others agree, I'll remove it from the list.

"Go to [url]" - Virus and Adult stuff alert!

"When Stop Clicked" - Stop stops all scripts. How will this work differently?

"Repeat for (secs) seconds" - Self-explanatory.

"Hide speech bubble" - Use "Say [(no input)]".

"Point away from edge" - The sprite will just face another edge.

"If <> then <> else <>" - What the heck is this supposed to mean?

"Color touching [sprite]" - Use "Touching color [color]".

Go to URL - Yes I agree, this is a bad idea.
When Stop Clicked - I think they meant something like the Stop Scripts block, but one that affects other scripts.
Repeat for () seconds - This could be done with variables.
Hide Speech Bubble - I don't know what a speech bubble is.
Point away from edge - It might've been point away from mouse.
If (0 then (0 else () - This is just the If and Else block...
Color Touching [sprite] - Could be useful if you have some sprites that are the same colors.

Offline

 

#23 2010-06-28 10:58:03

juststickman
Scratcher
Registered: 2009-05-31
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

I think if then else is actually
(if <boolean> then [text input] else [text input])
For something like
set [total damage] to [1 + (pick random [5] to [-5])]
change [health] by (if <(total damage) < 0 then [0] else [(total damage)])


http://is.gd/iBQi2 Add grob to your sig and help with world dominiation!http://is.gd/iBQ9Q                                                             Hey guys, we're seriously naming our team bob?

Offline

 

#24 2010-06-28 11:05:27

The-Whiz
Scratcher
Registered: 2007-07-09
Posts: 1000+

Re: Some blocks that should not be added to Scratch 2.0

OK, that would work, and we useful... Although you can work around that with complicated equasions...

Offline

 

#25 2010-06-28 18:44:57

climber59
Scratcher
Registered: 2009-12-15
Posts: 100+

Re: Some blocks that should not be added to Scratch 2.0

There are two versions one is a boolean with boolean inserters and one is a reporter with reporter insterters. The block just removes the need for variables.


Check out my projects if you have a chance.

Offline

 

Board footer