nXIII wrote:

I think limiting the format to prevent stuff like this is not a good idea. We're not introducing Scratchers to any really new concepts—they've seen all the argument types we can use, they've seen custom block inputs, and they've seen reporters answering their value in place of input slots. We're just putting some of these concepts together to achieve specific functionality that helps us write better, more concise, and more useful Scratch projects.

A curious Scratcher can leave a comment like "How did you do X?," and I'm sure everyone here would be happy to reply with a short message and a link to this topic if the Scratcher is interested.

I most thoroughly agree. It was easy enough to make “corrupt” scratch programs that ran on the scratch system in 1.4, but no one did. WWe shouldn't stop supporting slightly modified scratch programs just because some may think they are confusing!

lalala3 wrote:

to prevent interface cluttering, there could be scrollbars. Yeah.

That's still cluttered; that's just cluttered and hidden.

Nathanator1416J wrote:

It was easy enough to make “corrupt” scratch programs that ran on the scratch system in 1.4

No, it was much harder. Messing with the binary was practically impossible until Kurt, and simple hacks with shift-click-r (moving variable) didn't normally work with the Java player anyway.

Hardmath123 wrote:

Nathanator1416J wrote:

It was easy enough to make “corrupt” scratch programs that ran on the scratch system in 1.4

No, it was much harder. Messing with the binary was practically impossible until Kurt, and simple hacks with shift-click-r (moving variable) didn't normally work with the Java player anyway.

Thats hard??? I don't personally think that was hard with Textpad.

Hardmath123 wrote:

Messing with the binary was practically impossible until Kurt,

Back in the old days before Kurt, we used to have to write our own readers in JavaScript…



But seriously, it wasn't that difficult.

How do you open .json file? it doesn't have the ‘right program’ to view it.

Lightnin wrote:

This is a cool hack, but my concern is that when anyone who doesn't know what you've done (or how you've done it) tries to view your project, they won't be able to understand your scripts - they won't even make sense.

I wouldn't mind at all if this was being done only with downloaded, local projects. But these are public, shared ones, that people are likely to “see inside”.

Any thoughts on the issue?

I have a great idea!
How about a comment linked to the block that says this:
'This is a custom block.
I did NOT use the make a block function.
I used Hard math's way of making a block.
This was VERY hard and if you cannot do it,
it is okay.'
That is the end of the comment.
Would that work?

Lightnin wrote:

This is a cool hack, but my concern is that when anyone who doesn't know what you've done (or how you've done it) tries to view your project, they won't be able to understand your scripts - they won't even make sense.

I wouldn't mind at all if this was being done only with downloaded, local projects. But these are public, shared ones, that people are likely to “see inside”.

Any thoughts on the issue?

I think that this should be fixed as soon as possible, because it's going to mess things up if it isn't. I agree with your concern: people reading your project won't understand your scripts. I think Scratch should be a community where everyone programs in the same language, and if people start implementing these custom blocks into their scripts, Scratch will become, well, different, in many ways.

We've gotta come up with an idea on how to stop this from happening. I was thinking that Scratch should only allow you to import and export .sb2 files. Do you think that would work?

MrScribblenaut wrote:

Lightnin wrote:

This is a cool hack, but my concern is that when anyone who doesn't know what you've done (or how you've done it) tries to view your project, they won't be able to understand your scripts - they won't even make sense.

I wouldn't mind at all if this was being done only with downloaded, local projects. But these are public, shared ones, that people are likely to “see inside”.

Any thoughts on the issue?

I think that this should be fixed as soon as possible, because it's going to mess things up if it isn't. I agree with your concern: people reading your project won't understand your scripts. I think Scratch should be a community where everyone programs in the same language, and if people start implementing these custom blocks into their scripts, Scratch will become, well, different, in many ways.

We've gotta come up with an idea on how to stop this from happening. I was thinking that Scratch should only allow you to import and export .sb2 files. Do you think that would work?

By my priorities, usefulness trumps that kind of standardization. If a goal simply can't be achieved in the base editor, I feel we should not be limited to only what we're given. That being said, there are two apparent options for fixing the possible conflict without limiting Scratchers' options, which should be a last resort as opposed to an instant solution to every problem, and by last resort I mean last. One way is to promote it as a basic skill for Scratch programming, and not as something that only advanced people who should probably be using higher/better languages know how to do. The other is to make the standard system more flexible and versatile, so there are official ways to accomplish almost everything that would have required hacking.

when i try to open project.json it says ‘Windows can not open this file.’
help?

The idea for scratch is to teach programing right?
So if somone hacks a block to do cool things and somone asks how to do it, they understand programming a little better as they now know how to program that in the .json file.
I think the fact that you can do these hacks in scratch is great since it opens up many possibilities

Awesome. I'm gonna try it.

cool, it works. I wonder if there's a way to create reporter blocks or boolean blocks with this >.>

bullelk12 wrote:

cool, it works. I wonder if there's a way to create reporter blocks or boolean blocks with this >.>

hmm

Epicness123 wrote:

when i try to open project.json it says ‘Windows can not open this file.’
help?

Rename it to project.txt, edit, and when you're ready, make it project.json again.

(sorry for the late response)

Hardmath123 wrote:

Epicness123 wrote:

when i try to open project.json it says ‘Windows can not open this file.’
help?

Rename it to project.txt, edit, and when you're ready, make it project.json again.

(sorry for the late response)

thanks! (i asked it too )

SFollis wrote:

How do you open .json file? it doesn't have the ‘right program’ to view it.

Use Notepad (Windows), TextEdit (Mac), or gedit (Linux), or any other plaintext editor you want.

scimonster wrote:

SFollis wrote:

How do you open .json file? it doesn't have the ‘right program’ to view it.

Use Notepad (Windows), TextEdit (Mac), or gedit (Linux), or any other plaintext editor you want.

but mine says it doesnt have the left editor to view it

comp500 wrote:

scimonster wrote:

SFollis wrote:

How do you open .json file? it doesn't have the ‘right program’ to view it.

Use Notepad (Windows), TextEdit (Mac), or gedit (Linux), or any other plaintext editor you want.

but mine says it doesnt have the left editor to view it

Oh, you're hilarious.

AWESOME