Chrischb wrote:
And you can copy and paste text too.
![]()
It'd be lame if you couldn't. Then you could make scripts in a text editor and copy them into Scratch!
Offline
coolstuff wrote:
Chrischb wrote:
And you can copy and paste text too.
![]()
That, my friend, is the ultimate payoff of this idea
![]()
I wouldn't call it the ultimate, but it's definitely a payoff.
Offline
Harakou wrote:
Chrischb wrote:
And you can copy and paste text too.
![]()
Yeah! Collaboration could get easier! (Okay, here's my improvement, just copy/paste this script into Scratch...)
Yeah! Collaborations would be SO much easier!
Offline
ScratchReallyROCKS wrote:
Harakou wrote:
Chrischb wrote:
And you can copy and paste text too.
![]()
Yeah! Collaboration could get easier! (Okay, here's my improvement, just copy/paste this script into Scratch...)
Yeah! Collaborations would be SO much easier!
Especially if we get patching scripts.
Offline
DistantVisit wrote:
Harakou wrote:
I like it! But I don't think variables should be defined in the script, because they aren't in block based Scratch, and there could be an inconsistency.
And of course, the ability to switch between text and block mode should be a setting. I think having both modes easily acessable by default will only confuse some new scratchers that accidentally stumble upon it. (Keep in mind I don't mean a hidden feature like mesh that you need to activate in the browser, just something with an option so you know what you're getting into.)That's exactly the same thought I had when I stumbled upon this idea. I've noticed the scratch team has been very consistent about making scratch very kid-friendly so at most I think they would make this a hidden feature like mesh. I personally like the idea, but new users may find it and become very confused. Scratch is curently simple, made to be simple, ment to be simple, and will most likely stay simple. SO I very much doubt this will ever go on scratch.
Although, there is still hope.![]()
Somehow if we conviced Brian Harvey and Jens Moing to somehow implement this into BYOB, it would be much better. BYOB is ment to be advanced and a "more matured" version of scratch. I find that this feature woud belong much better in BYOB. Of course this all depends on whether the developers would be considerate on implementing this to BYOB.
Nice thinking, and really informative mock up fg123!![]()
Thank you!
ScratchReallyROCKS wrote:
DistantVisit wrote:
Somehow if we conviced Brian Harvey and Jens Moing to somehow implement this into BYOB, it would be much better. BYOB is ment to be advanced and a "more matured" version of scratch. I find that this feature woud belong much better in BYOB. Of course this all depends on whether the developers would be considerate on implementing this to BYOB.
Nice thinking, and really informative mock up fg123!![]()
Yes, we all know what BYOB is meant to be.
![]()
You have a very good point, this does seem like more of a BYOBish thing, especially if you could define procedures in the script, and it would turn into a block when you exit text mode.
But the problem is, when you have scripts like this:
http://img825.imageshack.us/img825/4525/long.gif
it slows Scratch down an amazing amount. With text representation though, it wouldn't have to worry about drawing and compiling scripts constantly. Of course, that isn't saying why it should be in Scratch. I guess the reason for that is basically that, when people make huge, complicated things, they want to share it with other people. It's natural. But, when people download it, if their computer is slower, then it might grind to a halt because of the huge scripting. Then, once it miraculously loads it, it would take forever to scroll or switch sprites. I've had it happen before. So, they could just switch to text view, and only worry about it being slow when they start scripts or switch back to block view, when it does all the compiling.
That's a biiig script!
Offline
fg123 wrote:
DistantVisit wrote:
Harakou wrote:
I like it! But I don't think variables should be defined in the script, because they aren't in block based Scratch, and there could be an inconsistency.
And of course, the ability to switch between text and block mode should be a setting. I think having both modes easily acessable by default will only confuse some new scratchers that accidentally stumble upon it. (Keep in mind I don't mean a hidden feature like mesh that you need to activate in the browser, just something with an option so you know what you're getting into.)That's exactly the same thought I had when I stumbled upon this idea. I've noticed the scratch team has been very consistent about making scratch very kid-friendly so at most I think they would make this a hidden feature like mesh. I personally like the idea, but new users may find it and become very confused. Scratch is curently simple, made to be simple, ment to be simple, and will most likely stay simple. SO I very much doubt this will ever go on scratch.
Although, there is still hope.![]()
Somehow if we conviced Brian Harvey and Jens Moing to somehow implement this into BYOB, it would be much better. BYOB is ment to be advanced and a "more matured" version of scratch. I find that this feature woud belong much better in BYOB. Of course this all depends on whether the developers would be considerate on implementing this to BYOB.
Nice thinking, and really informative mock up fg123!![]()
Thank you!
![]()
ScratchReallyROCKS wrote:
DistantVisit wrote:
Somehow if we conviced Brian Harvey and Jens Moing to somehow implement this into BYOB, it would be much better. BYOB is ment to be advanced and a "more matured" version of scratch. I find that this feature woud belong much better in BYOB. Of course this all depends on whether the developers would be considerate on implementing this to BYOB.
Nice thinking, and really informative mock up fg123!![]()
Yes, we all know what BYOB is meant to be.
![]()
You have a very good point, this does seem like more of a BYOBish thing, especially if you could define procedures in the script, and it would turn into a block when you exit text mode.
But the problem is, when you have scripts like this:
http://img825.imageshack.us/img825/4525/long.gif
it slows Scratch down an amazing amount. With text representation though, it wouldn't have to worry about drawing and compiling scripts constantly. Of course, that isn't saying why it should be in Scratch. I guess the reason for that is basically that, when people make huge, complicated things, they want to share it with other people. It's natural. But, when people download it, if their computer is slower, then it might grind to a halt because of the huge scripting. Then, once it miraculously loads it, it would take forever to scroll or switch sprites. I've had it happen before. So, they could just switch to text view, and only worry about it being slow when they start scripts or switch back to block view, when it does all the compiling.That's a biiig script!
![]()
It's for this project.
Offline
You could still make multi-scripts, more than 1 script, like
when green flag clicked
forever {
move 1 steps
if on edge, bounce
broadcast --- and wait
}
<-- put a space inbetween the scripts to create more scripts.
when I receive ---
say 'Hello!' for (2) secs
reset timer
wait until timer > 0.9
Offline
rdococ wrote:
You could still make multi-scripts, more than 1 script, like
when green flag clicked
forever {
move 1 steps
if on edge, bounce
broadcast --- and wait
}
<-- put a space inbetween the scripts to create more scripts.
when I receive ---
say 'Hello!' for (2) secs
reset timer
wait until timer > 0.9
Yeah, that's exactly what I was thinking.
Offline
What exactly are those like? ^^
I remember some - but it looked a bit odd.
I'll check again in a few hours...
Offline
coolstuff wrote:
There's been quite a bit of chat about the syntax - should it not just be that of project summaries?
Pretty much, but instead of:
when green flag clicked
forever
move 10 steps
end
it would be:
when green flag clicked
forever {
move 10 steps
}
Offline
ScratchReallyROCKS wrote:
DistantVisit wrote:
Somehow if we conviced Brian Harvey and Jens Moing to somehow implement this into BYOB, it would be much better. BYOB is ment to be advanced and a "more matured" version of scratch. I find that this feature woud belong much better in BYOB. Of course this all depends on whether the developers would be considerate on implementing this to BYOB.
Nice thinking, and really informative mock up fg123!![]()
Yes, we all know what BYOB is meant to be.
![]()
You have a very good point, this does seem like more of a BYOBish thing, especially if you could define procedures in the script, and it would turn into a block when you exit text mode.
But the problem is, when you have scripts like this:
http://img825.imageshack.us/img825/4525/long.gif
it slows Scratch down an amazing amount. With text representation though, it wouldn't have to worry about drawing and compiling scripts constantly. Of course, that isn't saying why it should be in Scratch. I guess the reason for that is basically that, when people make huge, complicated things, they want to share it with other people. It's natural. But, when people download it, if their computer is slower, then it might grind to a halt because of the huge scripting. Then, once it miraculously loads it, it would take forever to scroll or switch sprites. I've had it happen before. So, they could just switch to text view, and only worry about it being slow when they start scripts or switch back to block view, when it does all the compiling.
Wow. That's a freaking long script.
I support. I think that there should be both a text-based version and a block version. They're written in the same program, though.
It might not work out... Maybe as a separate project...
EDIT: Grammer error. xD
Last edited by iCode-747 (2010-08-30 05:16:09)
Offline
iCode-747 wrote:
Wow. That's a freaking long script.
Thanks! It's for this project.
Last edited by ScratchReallyROCKS (2010-08-30 10:11:45)
Offline
If you love text based programs, use Greenfoot.
Offline
JAMBAMtheSLAM wrote:
If you love text based programs, use Greenfoot.
I've tried it and I don't really like it. I use like, 5 other text based languages, but I like Scratch's block interface more than text. I don't like it when it gets in the way of programming long scripts though. That's why I suggested this.
Offline
ScratchReallyROCKS wrote:
JAMBAMtheSLAM wrote:
If you love text based programs, use Greenfoot.
I've tried it and I don't really like it. I use like, 5 other text based languages, but I like Scratch's block interface more than text. I don't like it when it gets in the way of programming long scripts though. That's why I suggested this.
Nice explanation! If I wasn't already in support of this suggestion, you've really put me over the edge in terms of support.
It also puts a nice new spin on the whole "learning how to program" philosophy of Scratch, in that not everything is as simple as snapping together a minimal library of blocks.
Offline
coolstuff wrote:
ScratchReallyROCKS wrote:
JAMBAMtheSLAM wrote:
If you love text based programs, use Greenfoot.
I've tried it and I don't really like it. I use like, 5 other text based languages, but I like Scratch's block interface more than text. I don't like it when it gets in the way of programming long scripts though. That's why I suggested this.
Nice explanation! If I wasn't already in support of this suggestion, you've really put me over the edge in terms of support.
![]()
It also puts a nice new spin on the whole "learning how to program" philosophy of Scratch, in that not everything is as simple as snapping together a minimal library of blocks.![]()
Exactly. It would be a great way to introduce people to text-based coding, while keeping them in the relative comfort of the Scratch interface. I think that one of Scratch's huge merits is that you can see what things will look like, and place them on the game window yourself. Creating graphic based programs in other languages is usually more intimidating and in depth.
Offline
I support completely.
Offline