Scratch

2.99.023, more bug fixes.

Jens wrote:

tonight's release completes most of the reported programming language bug fixes that I know how to fix, and some others that only I noticed. :-) Right-clicking in the block editor's scripts pane now triggers a somewhat extended context menu, that also lets you undo the last drop and "make a block"

henley wrote:

Wow. It's like you make a new one every day! I'm behind four, and I feel like I keep having to replace!

Jens was producing at this rate for half a year before we went public with 2.99!  The changes from one day to the next are relatively small now.  The good news is, if you miss a day, there won't be a quiz on it.     Just update when you get a spare minute, or once a week, or only on those days when the announcement has the word "major" in it, or a lot of exclamation points!!!

Jonathanpb wrote:

Just a random crazy idea - what if on a site, there was a library of blocks you could make in BYOB? If you wanted to look at the blocks you could make or wanted to see how to make a block, you could look it up on the site. 

But that's a bit extreme... 

It's not complicated, see the example of my tutorial where I try to keep a trace of my exploration of Byob :

http://www.xleroy.net/ByobTuto/thumbnails.html

On the other hand, as it is possible to export one sprite -including its scripts - it would be easy to implement a bank of blocks. Mainly for highly specialized matters (multi-player for example).

But we still hope than soon the Scratch team will adopt and endorses Byob, because Scratch already provides an excellent solution by offering all the applications (more then one million !) with sources which can be downloaded by everyone to find models of scripts and borrow a lot of excellent ideas. !

@ bharvey

I've an application where I need to save several lists of coordinates. I can now export them into a text file "manually" (right click etc). I would like to know if, and if yes how, Byob has one solution (*) to export/import text lists (by the way a list of list can't be exported like that, even manually. It gives a list of "pointers". It is not a problem as these coordinates can be transposed into a text file.



(*)
1 -  bharvey, you have already answered, see the "streams". But I've not at all understood how to use this to achieve what I'm asking for.
2 - you told that this issue is not so easy to implement, as it is related to the OS, OK for an interactive application, but probably not for an import/export feature.
3- It's just a question,nothing else, because I consider that -to play only with the available tools - is part of the game and of the discipline of programming in Scratch/Byob. I'm now looking how to transpose in Scratch applications initially developed in Byob. It can be long and tricky, but it is maneagable. The programming limits of Scratch and even more Scratch+Byob are already very, very high !!!

xly wrote:

I would like to know if, and if yes how, Byob has one solution to export/import text lists (by the way a list of list can't be exported like that, even manually.)

I think probably no for 3.0, yes for 3.1.  Definitely non-text values should survive save/load, and if we can do that we can also do import/export.

Billybob-Mario wrote:

As I've said, two features that are necessary are a way to name a script, and on the (x position of sprite1) block, a way to access them.

You can already say

SET <var> TO [THE SCRIPT [...]]

so we can give names to headless scripts.  All that's missing is a way to include a hat block in a named script.  That's on the wish list, but I still don't see why it's such a big deal unless you want to construct a sprite out of pieces.

bharvey wrote:

Well, you know, we already have a small collection of user projects on the site, and there's no reason we couldn't include any tutorial projects or specialized tool collections that anyone wanted to contribute.

This would be a lot easier to accomplish if sprites only exported the blocks that they specifically use...consider this a feature request 

bharvey wrote:

fullmoon wrote:

bharvey wrote:

specialized tool collections that anyone wanted to contribute.

This would be a lot easier to accomplish if sprites only exported the blocks that they specifically use

I'm confused.  I can see how other problems might be solved more easily, but a tool collection explicitly wants to export blocks it doesn't use.

A one-size-fits-all solution might require something like remembering which sprite contributed each global block, and being able to say "export only the ones I contributed."

I still think the simplest solution would be what I described above. If someone needed to collect some blocks into a sprite to export them, they could just drag the blocks into the sprite's script area...or better yet, make a library reporter that simply contains all the other blocks.

You could also open an exported sprite in a separate instance of BYOB and just delete all custom block definitions in there that you don't want in you target project, then save it under a different name and import it into the target project 

xly wrote:

I shall investigate further on and report.

Error message is "Could not write file. Export failed"
The error occurs both with FILE/EXPORT SPRITE and CLICK-RIGHT/EXPORT commands
Up to now I can only export the sprite image from the COSTUME tab.

This seems to be a recent error, because in the past I have already succeeded to export a sprite, but never to re-import it.

This very promising feature need to be evaluated further on

xly

Hi Xavier, I just tried to reproduce this error (exporting a sprite fails and raises an exception), but was unable so. I'd really love to find out what's wrong, so could you perhaps send me the project that's causing this problem, or point me to a link where I can find it?

Thanks for all the relentless testing, you're fantastic!

The official distro site for BYOB 3 is:

byob.berkeley.edu