Scratch

Welcome to Scratch! 

Anyways, I support. People could still learn from the Scripts! 

Don't support.
Scratch is all about seeing other peoples' scripts, so this defeats that purpose.

Then how can they remix it?

Perhaps this could be an 'educator' or 'challenge' mode?

ImagineIt wrote:

Wes64 wrote:

ImagineIt wrote:

Then how can they remix it?

777w wrote:

id like you to look through and actually read the first post this time

*ahem* They still cannot remix. What if it's an extremely long script that they don't want to recreate. I did read it too anyways. Actually read my post next time.

imagineit, dont go saying "actually read my post next time" when he obviously did
and wes64, dont take my posts directed at jvvg and direct them at somebody else

technoboy10 wrote:

Perhaps this could be an 'educator' or 'challenge' mode?

this would be cool, but people might abuse it
maybe there could be a seperate program for educators wherein you have this option but you cant upload it to the main site if youve got it enabled

ImagineIt wrote:

Wes64 wrote:

ImagineIt wrote:

Then how can they remix it?

777w wrote:

id like you to look through and actually read the first post this time

*ahem* They still cannot remix. What if it's an extremely long script that they don't want to recreate. I did read it too anyways. Actually read my post next time.

Hi,

Thanks for the response.

The idea is they shouldn't remix this part of it within the project. Sure, outside of the set challenge, switch off the read only mode and then change to your hearts content, in fact a great extension task would be to try and improve the maze and set it to a peer to solve. But once someone tries to solve the maze, they should not be allowed to change the framework of the maze.

Scratch is an amzing tool for introducing young kids to programming and other computing concepts. Doing this kind of thing is why I left a 15 year software development career to teach computing. However, in order to use this to teach structured content, a teacher needs to be able to structure the learning. In reality, i am currently just telling them not to chaneg the maze and only add to the cat sprite. However in each class there is usual 4 or 5 who when I come to see how they are doing have just moved the walls aside and dragged the cat with the mouse. This does not help anyone, least of all scratch in it's goals (program)!

Stu

Mokat wrote:

This is like downloading/remixing locks, so I don't support. If you don't want your students to edit the script of the maze, (as you mentioned above to the 4 or 5 who just drag aside the walls and move the cat and alll that) is to watch them, and if you catch some one doing that, then make sure they won't do it again.

Hi,

Thanks for your feedback.

Sadly, watching for students doing this is very far from viable. My time in the lesson should be spent answering genuine questions for people trying to design a script to get the cat around the maze, not running from screen to scrren looking over 30 shoulders tosee if anyone is breaking the rules.

Mokat wrote:

Make them start over or something. Everyone can remix a project if they want to, and theres nothing you can do about it.

Well, I can. I can come on here and make a suggestion for a feature in 2.0. Scratch is pitched as a teaching tool. For it to be a robust teaching tool this would be essential. I am not talking about blocking access to scripts. I am not even talking neccesarily about a locking feature that can't be swithed off by anyone. But by locking a script or sprite, I am making it clear that for the term of this excersice these values are not to be changed. Clicking an unlock button will undo this, but by doing this they would know that in this excercise this is breaking the rules. As I said, at other times changing the parameters of the maze would be an excercise in itself.

Mokat wrote:

And, from the situation you have described in the original post, you could easily do this by making something and not saving it anywhere on the computer. I am assuming that you would have a separate computer and maybe having it projected somewhere (again this is an assumption) and you could quickly make a maze and project it somewhere, so they can see the scripts but don't save it anywhere, so that there isn't a way to access the scripts to edit them unless they actually go up to the computer your using.

I am not sure what you mean here. Each student has their own copy of the project. They need this as they need to write their own script to solve the maze!

Stu

I don't support this,because it would stop cooperation on projects,even those that are
different.

This in vanilla Scratch wouldn't work, but maybe a teachers' version could have this as an option.

EDIT: And, ninja'd by 777w by 22 hours.

Last edited by jackrulez (2012-06-27 09:47:53)

StuartMaher wrote:

Hi Everyone,

First post here!

I have a number of feature suggestions, one of which I understand walks the line of the share part of the Scratch slogan.

Basically it's similar to the hidden blocks/sprites request, but actually, they don;t need to be hidden. What I would like is the ability to make the read only or non editable. I use scratch in teaching computing at secondary school in the UK and the first unit of work I use scratch for is understanding sequences of instructions for 11/12 year olds. The first lesson is a play lesson to introduce themto the program, show them some basic script element get the cat moving then experiment. For the second lesson we get more serious and look at how we can use sequences of instructiosn to solve a problem. So I created a project with a number of black bars in a maze, a green square as a destination and the top down cat sprite at the start, Their job is to get the cat to the green square using a sequence of intsructions. I have written some scripts on the black bars that if the cat touches them it says "Oh No" and stops all the scripts. If it hits the green square they get "Hooray". Simple stuff. I have no problem them seeing what I have written, in fact I think it helps the real inquisitive people. However, for some of them, using your imagination involve either moving the wall sprites or deleting the scripts on them. Now I have no problem with using their imagination within the context of the assignment (Despite me starting the cat script with Move to X, Y to get it to the begingin no one has just put in a move x, y to the end point!) but I need them to solve it using instructions. Not by editing the maze!

So what I would like is the ability to mark sprites, scripts and/or instructions as read only. People can read them, learn from them, but not break a challenge set for them

Stu

Scratch2EXE?