I think it would be cool to be able to make a scratch project and then view the actual, written code. After seeing how it works a few times then we may actually be able to type the code rather than drag and drop it. I think it would be a great way to learn how more complicated programming languages function.
Offline
That would actually be a pretty good way for me to learn flash!
Offline
The whole point of Scratch is that it's easy. All of it is easy to figure out. No block or component can't be figured out by a beginner.
Making the code typeable would defeat the purpose, and if you want to see the Flash code, it uses a player that is simply a parser for the Scratch File Format.
Offline
jvvg wrote:
The whole point of Scratch is that it's easy. All of it is easy to figure out. No block or component can't be figured out by a beginner.
Making the code typeable would defeat the purpose, and if you want to see the Flash code, it uses a player that is simply a parser for the Scratch File Format.
Whoa whoa, that's like limiting what people can do on purpose. Someone could completely ignore that aspect of scratch and wouldn't be hindered a bit. But for those who do care, they would be able to as a learning experience.
Offline
That would be epic, but VERY hard
And then it would lead to a whole new upbringing of Flash games on the internet
Offline
well, maybe not, I mean the computer translates a scratch project into flash, there must be a way to see that flash code if the computer turns it into flash. The code has to exist somewhere. I may somehow be wrong I guess.
Offline
bullelk12 wrote:
well, maybe not, I mean the computer translates a scratch project into flash, there must be a way to see that flash code if the computer turns it into flash. The code has to exist somewhere. I may somehow be wrong I guess.
true.
Offline
Might as well just use Flash. But that is just my opinion. What would be the point of it if you can just drag and drop it? Drag 'n Dropping is faster and easier.
Offline
bullelk12 wrote:
jvvg wrote:
The whole point of Scratch is that it's easy. All of it is easy to figure out. No block or component can't be figured out by a beginner.
Making the code typeable would defeat the purpose, and if you want to see the Flash code, it uses a player that is simply a parser for the Scratch File Format.Whoa whoa, that's like limiting what people can do on purpose. Someone could completely ignore that aspect of scratch and wouldn't be hindered a bit. But for those who do care, they would be able to as a learning experience.
If you really want Scratch to have no limits, then it would have to be able to read/write files, access network ports directly, random-access RAM, use DLL files, be able to integrate directly with OS APIs, etc.
A text-based language provides no additional value to Scratch, and only makes it more difficult for younger people to understand.
If you really want to learn a text-based language, use Python or something. Don't bother with Scratch.
Offline
I would definitely support an option to code Scratch via text instead of blocks, for a multitude of reasons.
1. Huge scripts
Sometimes, projects, especially 1s1s, can grow a script so long that it crashes Scratch or makes edits impossible. When one sees projects such as coolstuff's Path Finder, it quickly becomes apparent that block-based scripts can sometimes be unwieldy. Text avoids this, and would help slower computers greatly.
2. Transport of Scripts
Scratch scripts can never be posted directly onto the forums, comments, or anywhere, but must be typed out with the forum equivalent of Scratch code or go through an image hosting site. If a text-to-code mode existed, it would be a matter of cutting and pasting between pojects or onto the website.
3. Education
Unfortunate as it may seem, not all programming is done with colorful blocks. Scratchers must learn this, and begin to move towards lines of text if they ever want to advance to more powerful coding.
Additionally, I see no way how this could make Scratch harder to understand. If a user cannot figure out the text type of coding, they can simply use the block-based coding until they understand its workings. Users aren't exactly being forced to use the feature, correct?
Offline
Finally someone who get it. Adding more doesn't have to equal harder, anyone who didn't want to wouldn't have to. It's their decision, and if some of you are worried about being bested because you don't want to take the time to learn the real deal, I'm sorry. But I really want this!
Offline
As for scratch having no limits, that's beyond what I was asking for. All I want is to be able to see and write the flash with the scratch software, that's all. As I and OverPowered said, you're not forced to do it this way
Offline
Still a good idea. ^_^
Offline
OverPowered wrote:
I
Scratch scripts can never be posted directly onto the forums
Use the ScratchBlocks tag!
when gf clicked repeat until <(timer) > [10]> go to [mouse-pointer v] end think [Scripts in your posts!] for (3) secs
Offline
iTweak0r wrote:
OverPowered wrote:
Scratch scripts can never be posted directly onto the forums
Use the ScratchBlocks tag!
when gf clicked repeat until <(timer) > [10]> go to [mouse-pointer v] end think [Scripts in your posts!] for (3) secs
I know. What I'm attempting to say is that, if a text-to-code editor existed, you wouldn't have to retype everything into the [/scratchblocks] format, but could copy and paste the actual code.
Offline
Rub0Gameton wrote:
Might as well just use Flash. But that is just my opinion. What would be the point of it if you can just drag and drop it? Drag 'n Dropping is faster and easier.
Typing is a lot faster and easier.
Offline
jvvg wrote:
bullelk12 wrote:
jvvg wrote:
The whole point of Scratch is that it's easy. All of it is easy to figure out. No block or component can't be figured out by a beginner.
Making the code typeable would defeat the purpose, and if you want to see the Flash code, it uses a player that is simply a parser for the Scratch File Format.Whoa whoa, that's like limiting what people can do on purpose. Someone could completely ignore that aspect of scratch and wouldn't be hindered a bit. But for those who do care, they would be able to as a learning experience.
If you really want Scratch to have no limits, then it would have to be able to read/write files, access network ports directly, random-access RAM, use DLL files, be able to integrate directly with OS APIs, etc.
A text-based language provides no additional value to Scratch, and only makes it more difficult for younger people to understand.
If you really want to learn a text-based language, use Python or something. Don't bother with Scratch.
Well, I think Scratch is good for learning the basic concepts, &c., but if you want to do text-based code, then yeah do something else after that.
Offline
bullelk12 wrote:
which is why having this in scratch would promote both worlds.
If you really want the best of everything, then your computer would have a partition for every operating system ever written, have every program ever written on it, etc.
My point is that you don't always need the "best of both worlds". The point of Scratch is to be easy to understand and teach programming to kids. A text based language has nothing to do with that purpose.
Offline
If, according to the original post, it can simply display the flash code, wouldn't that make publishing flash games/animations five times easier?
Offline
As far as I can see, allowing users to see the code behind the blocks won't make Scratch any more difficul to understand. Again, users are not forced to use text, and instead can choose to use whichever option that suits them more.
Offline
I know there must be a reason behind your answers jvvg, but the fact is that by using this idea you could still teach very young kids to code in text and still maintain the policy.
The text programming is the next level of course but it's not all out programming necessarily. Because it's still based off the original scratch blocks, so you could place the blocks and just look at the code as the next very easy step forward without any extra difficulty. Then, once you've gotten the general pattern in your head you could take the next step. Which is trying to type it.
I believe this would still stick with the policy of getting kids to learn to program easily by taking small steps.
Offline
I mean, Imagine this. You place a "move (10) steps" block, you could take a look at what that looks like in text. Then you could an "if" block around the first block and see what that looks like and so on. Those are super small steps that wouldn't even be required.
Offline