I have been working on a large project, and editing has become painfully slow. I'm not sure how Scratch works, but it appears to be compiling the scripts after every edit in order to allow the user to have the option to immediately execute the program. If this is the case, would it be possible to have an option to allow the user to choose when they are ready to compile and run? I would gladly trade the ability to immediately execute a program for a less frustrating editing experience.
Offline
I'd love this! It would certainly be a great addition - though I fear that it might take away from the simplicity of the program. Maybe it could be in the shift-clicked "file" menu, with project summaries, etc?
Offline
I agree, this would be nice. But when this happens, they need to make an "script editor only" place/program. Or make it so you can type out the scripts.
Offline
I'm pretty sure the Scratch blocks are compiled into code as the project runs. (That's partly why Scratch is so much slower than other languages.)
I'm pretty sure that the lag in large scripts results from the script having to constantly be redrawn-when it gets big, it takes a while to draw.
Last edited by Harakou (2010-06-25 08:59:38)
Offline
Harakou wrote:
I'm pretty sure the Scratch blocks are compiled into code as the project runs. (That's partly why Scratch is so much slower than other languages.) I'm pretty sure that the lag in large scripts results from the script having to constantly be redrawn-when it gets big, it takes a while to draw.
That would make sense.
I think there's several reasons why Scratch is slow:
- Redrawing scripts everytime you change them.
- Runs directly off the source code in Squeak through a VM
- When running projects, runs directly off the scripts
- Added delay when looping.
Yeah... All those things really add up to an unfortunate series of slow events.
Offline
This would really speed up script editing, meaning no lag when moving blocks around.
Offline