Scratch

LiquidMetal wrote:

Jonathan50 wrote:

LiquidMetal wrote:

Ughh why did they change the font? At least we got the orange variables back...

I just made the ultimate javascript bookmark for Scratch2.0!   Save the following code as a bookmark named "Scratch2.0" on your bookmarks toolbar:

Code:

javascript:if(window.location!='http://alpha.scratch.mit.edu/scratchr2/static/Scratch_new.swf'){window.location='http://alpha.scratch.mit.edu/scratchr2/static/Scratch_new.swf'};javascript:document.body.childNodes[0].ASsetEditMode(true);document.body.childNodes[0].ASsetLoginUser(prompt('Please note: the username you enter will be displayed on the top \nright of Scratch2.0 even if the password you enter next is incorrect, but \ncloud variables will not work perfectly.\n\nScratch Username:'),prompt('Scratch Password: (Careful - NOT masked!!)'));

Click your bookmark on any page to go to the 2.0 Alpha Site.
Click your bookmark on the alpha site itself to enter edit mode, and log you in.

Enjoy 

To awesome to survive!

Being that a snippet of javascript code cannot be alive, there is no risk of it dieing, so it will survive!

I actually mean't for me to survive

veggieman001 wrote:

or they're just ignoring us in the hopes that maybe we'll do the right thing and stop

Ha.

About you being allowed:

Lightnin wrote:

So far we haven't done anything to prevent it, basically because we'd rather focus on all the other stuff that needs to get done. It's not ideal but it doesn't seem so bad. But if it gets really bad I guess we'll spend the time to figure out a way to close it off.

Lightning wrote:

Hardmath123 wrote:

Mind if I tell the guys at the AT's that? They're kind of curious about whether you actually care or not.

Here's a longish answer: In general we like to be open - it's why we usually release our source code.  So as long as accessing the editor that way doesn't lead to a lot of drama or confusion, it's ok. But we wouldn't really like to see it advertised widely, you know? And we wouldn't like people complaining that projects made with the alpha editor, which they were never really granted access to, don't work in the final release version.

But as long as people don't go all crazy with it, it's no big deal. Feel free to quote / post this elsewhere, btw.

Oh and btw, we're grateful for any help the AT folks would like to give us by bug reporting / security testing and what not. This code is still pretty raw, and it'll help to get more detailed and accurate bug reports on it once we open it up to the next wave of testers (I'm assuming most AT folks have signed up on Gobo's project).

Last edited by Hardmath123 (2012-10-10 21:08:11)

The alpha website itself is actually blocked to all those without technical access, and there is no way to get around that without being invited by the scratch team.

Lightnin wrote:

Oh and btw, we're grateful for any help the AT folks would like to give us by bug reporting / security testing and what not. This code is still pretty raw, and it'll help to get more detailed and accurate bug reports on it once we open it up to the next wave of testers (I'm assuming most AT folks have signed up on Gobo's project).

So basically, since the scratch team does not want to deal with authentication on a flash object, they left it public.  As long as we don't publicize it excessively, and we understand that alpha version projects are not guaranteed support in the "officially" public versions, we are allowed to use it.  Once we are using it anyway, it would be nice if we reported bugs and potential security issues.  Did I get that right?

Last edited by LiquidMetal (2012-10-10 21:46:47)

Oops! that was a mistake, I fixed it. Thanks!

LiquidMetal wrote:

Lightnin wrote:

Oh and btw, we're grateful for any help the AT folks would like to give us by bug reporting / security testing and what not. This code is still pretty raw, and it'll help to get more detailed and accurate bug reports on it once we open it up to the next wave of testers (I'm assuming most AT folks have signed up on Gobo's project).

So basically, since the scratch team does not want to deal with authentication on a flash object, they left it public.  As long as we don't publicize it excessively, and we understand that alpha version projects are not guaranteed support in the "officially" public versions, we are allowed to use it.  Once we are using it anyway, it would be nice if we reported bugs and potential security issues.  Did I get that right?

Yep. Enjoy 

Jonathan50 wrote:

zubblewu wrote:

Nodog438 wrote:

I just like to call them secret, because they hid them

Nah, they just didn't delete them 

No, they are experimental and not finished.

Actually, they are (for the most part). I've tried them, and they work just fine.

Hardmath123 wrote:

About you being allowed:

Lightnin wrote:

So far we haven't done anything to prevent it, basically because we'd rather focus on all the other stuff that needs to get done. It's not ideal but it doesn't seem so bad. But if it gets really bad I guess we'll spend the time to figure out a way to close it off.

Lightning wrote:

Hardmath123 wrote:

Mind if I tell the guys at the AT's that? They're kind of curious about whether you actually care or not.

Here's a longish answer: In general we like to be open - it's why we usually release our source code.  So as long as accessing the editor that way doesn't lead to a lot of drama or confusion, it's ok. But we wouldn't really like to see it advertised widely, you know? And we wouldn't like people complaining that projects made with the alpha editor, which they were never really granted access to, don't work in the final release version.

But as long as people don't go all crazy with it, it's no big deal. Feel free to quote / post this elsewhere, btw.

Oh and btw, we're grateful for any help the AT folks would like to give us by bug reporting / security testing and what not. This code is still pretty raw, and it'll help to get more detailed and accurate bug reports on it once we open it up to the next wave of testers (I'm assuming most AT folks have signed up on Gobo's project).

Yay bug testing. BUG: Whenever I open a project from a local file, it says i cant edit the cloud data on someone else's project, even though it is mine.

Do you guys think they'll ever just delete this thread and close the player?

Can someone please provide step-by-step instructions for using scratch 2.0 on google chrome?

It's too confusing I tried to get all the stuff but it's still not working.

veggieman001 wrote:

http://oi49.tinypic.com/1zbsz69.png
Me too

HOW??????? please tell me.

ahirbhairav wrote:

Can someone please provide step-by-step instructions for using scratch 2.0 on google chrome?

The easiest way is to use my javascript bookmarklet.  Make a bookmark on your bookmarks toolbar and copy the following code into the location:

javascript:if(window.location!='http://alpha.scratch.mit.edu/scratchr2/static/Scratch_new.swf'){window.location='http://alpha.scratch.mit.edu/scratchr2/static/Scratch_new.swf'};javascript:document.body.childNodes[0].ASsetEditMode(true);document.body.childNodes[0].ASsetLoginUser(prompt('Please%20note:%20the%20username%20you%20enter%20will%20be%20displayed%20on%20the%20top%20\nright%20of%20Scratch2.0%20even%20if%20the%20password%20you%20enter%20next%20is%20incorrect,%20but%20\ncloud%20variables%20will%20not%20work%20perfectly.\n\nScratch%20Username:'),prompt('Scratch%20Password:%20(Careful%20-%20NOT%20masked!!)'));

Click this once to go to the alpha page, and again to open the editor and log in.  If you don't want to log in, just press cancel for both dialogues.