You can save costumes and sprites, so why not scripts? You just right-click on a script, and then choose "export" and then save it as a .SST(Scratch Script) or something(I'm sure there's no such thing as a .SST file though).
To import one you click on a sprite, and click a button called "Import Script". You press it, and it shows all the scripts you've saved in the folder you're looking in.
So, what do you think?
Last edited by BWOG (2009-05-08 10:20:40)
Offline
export/import works nicely as well, but i support this idea
Offline
Along these lines; It would be very convenient to be able to save a script and then be able to call it up as a Universal Subroutine... It would be kind of like Broadcast/Recieve, which i interpret as GOTO, Without The Return...
( i've gotten around this by simply telling my main script to Wait for a second, until the Receiving Script has finished it's Assignment ! )
But this New Feature; Universal Receive would allow programmers to create very large libraries of subroutines, without having to recreate them each time...
i understand how saving an using a sprite might do this; But this way seems subtly more elegant...???
Offline
chrstphre wrote:
Along these lines; It would be very convenient to be able to save a script and then be able to call it up as a Universal Subroutine... It would be kind of like Broadcast/Recieve, which i interpret as GOTO, Without The Return...
( i've gotten around this by simply telling my main script to Wait for a second, until the Receiving Script has finished it's Assignment ! )
But this New Feature; Universal Receive would allow programmers to create very large libraries of subroutines, without having to recreate them each time...
i understand how saving an using a sprite might do this; But this way seems subtly more elegant...???
You should try using the Broadcast and Wait block...it's like the GOSUB with the RETURN.
Offline