scimonster wrote:
I don't always feel like waiting half an hour while my parents are doing other things, especially not for a beta.
Suggestion: Talk them into installing it and then making you the owner of c:/byob, and then you can just replace the image file when a new one comes out.
Last edited by bharvey (2011-05-05 01:58:01)
Offline
bharvey wrote:
Here are the full release packages corresponding to the 2-May-2011 beta:
Macintosh
Windows installer and files only
Fixed the broken links.
Offline
Offline
bharvey wrote:
Check out my animal game BYOB project.
That's really cool! I wish I had the time to build up a huge library of questions and answers.
Offline
shadow_7283 wrote:
That's really cool!
Thanks. Once we get around to first class costumes and first class web pages (Snap v. 4.7 or something) I want to put in real-time scraping of the Wikipedia page for the animal being guessed to find a picture of it and switch to that as a costume!
Offline
bharvey wrote:
Check out my animal game BYOB project.
Wow that is really cool!
Offline
For people who don't know, BYOB 4.0 will be called Snap 4.0.
Offline
Really? I was under the impression that it would just be called "Snap".
Offline
shadow_7283 wrote:
Really? I was under the impression that it would just be called "Snap".
Well, it has to have a version number, just like any software, so people can keep up and so we can make sense of bug reports. We could have called it Snap 1.0, but I think that would be more confusing than starting at 4.0 so we have a single range of version numbers.
In the early days of Unix, AT&T released "version 7" and then they became legally able to sell software (a long story) and so with great fanfare they announced... "Unix System V"! V as in five. You were supposed not to be confused because one was "version 7" and the other was "System V." Weird.
Offline
Huh. OK, I get your point.
Offline
BWOG wrote:
fanofcena wrote:
BYOB is always 1 step ahead of scratch
scratch 1.4 - byob 2.0
scratch 2.0 - Byob 3.0
with all the cool new features BYOB Will soon become a pros language for experimentisationIf they went 1.4, 1.5, 1.6, and so on, BYOB for Scratch 2.0 would be 8.0.
Let me check, not sure...
BYOB 1.0 = Scratch 1.3
2.0 = 1.4
3.0 = 1.4 [yes it is 1.4]
4.0 = 1.5
5.0 = 1.6
6.0 = 1.7
7.0 = 1.8
8.0 = 1.9
Nope, BYOB for Scratch 2.0 would then be BYOB 9.0.
Offline
rdococ wrote:
BYOB 9.0
I don't think I'm going to live that long! If you want a BYOB 9.0 you'll have to invent it yourselves.
Edit: No, nothing wrong with me, just that I don't think we'll continue at the rate of a major version per year. First class procedures really turned everything upside down, and moving to Javascript is a big upheaval, but the other things on the list -- first class costumes, sounds, web pages, files, etc., and many small UI improvements -- won't warrant a major version number. With luck, you'll see ... 4.11, 4.12, ... for quite a while.
It's an example of the usual 90/10 rule of software development (and most other things too): The first 90% of the work takes the first 10% of the time, and the remaining 10% of the work takes the remaining 90% of the time. We're in the tail of that distribution.
I suppose if we develop a phone-screen-friendly version, that might get a major version number, although Jens is having so much fun with Morphic in his iPhone browser that it might be faster than that. Maybe when we invent the version for the chips implanted in your children's or grandchildren's heads?
Last edited by bharvey (2011-05-08 14:01:44)
Offline
bharvey wrote:
I suppose if we develop a phone-screen-friendly version, that might get a major version number, although Jens is having so much fun with Morphic in his iPhone browser that it might be faster than that.
Naw, we're going to support phones with Snap 4.0 right away (otherwise what's the point in switching to JavaScript?). Here's a first taste of how this might look and feel:
BYOB v9.0
Last edited by Jens (2011-05-09 04:25:16)
Offline
bharvey wrote:
shadow_7283 wrote:
That's really cool!
Thanks. Once we get around to first class costumes and first class web pages (Snap v. 4.7 or something) I want to put in real-time scraping of the Wikipedia page for the animal being guessed to find a picture of it and switch to that as a costume!
First-class costumes and first-class webpages?!? You're thinking creative!
What about a [script block]?
It's like [script variable]; but it goes like this: (in BYOB)
[script block (call variable) with script [block insert, not C block] ]
The variable used in the script is set to what's in the block insert, and can be run with the [run] block. Like? It's like first-class blocks!
Offline
Hello. BYOB 3 is a fantastic program, so thank you to Jens and Brian for putting so much work into it. I would like some help. I have made a travelling salesman animation (using BYOB 3.1) and am using a brute force approach to work out all the possible journeys (combinations) a salesman can make between nodes or destinations. I am looking for a cleverer way of doing it and am wondering if some of the custom blocks in the tools.ypr file could be of help. I have made a YouTube video that shows the application working. As you can see, as the number of nodes increases the number of possible journeys increases and the longer it takes to work them out before the drawing starts. YouTube link: http://www.scratch.mit.edu/ext/youtube/?v=tGNNFrdv03Q
Offline
Because of the new grey-bordered notation, what about a grey-bordered block that reports what's inside as if it was grey-bordered?
Last edited by rdococ (2011-05-09 08:39:32)
Offline
bharvey wrote:
Maybe when we invent the version for the chips implanted in your children's or grandchildren's heads?
I don't like to think about that.
Offline
rdococ wrote:
What about a [script block]?
It's like [script variable]; but it goes like this: (in BYOB)
[script block (call variable) with script [block insert, not C block] ]
The variable used in the script is set to what's in the block insert, and can be run with the [run] block. Like? It's like first-class blocks!
Umm, unless I'm misunderstanding what you mean, we already have that -- first class blocks and scripts were the big new thing in 3.0!
SCRIPT VARIABLES <variable>
SET <variable> TO [THE SCRIPT <your script>]
Offline
joebloggsnz wrote:
I am looking for a cleverer way of doing it and am wondering if some of the custom blocks in the tools.ypr file could be of help.
Well, of course there's nothing in the tools project that can get around the NP-completeness of TSP!
You can avoid the big wait at the beginning if you generate the paths one at a time instead of all at once. I'm guessing that you're generating a list of paths and then drawing them all with a FOR EACH block or something equivalent. The easiest way to get them one at a time, I think, would be to use lazy lists -- see the "all the prime numbers" project on the BYOB web site.
I can't be any more specific than that without seeing the actual code in your project.
Offline
rdococ wrote:
Because of the new grey-bordered notation, what about a grey-bordered block that reports what's inside as if it was grey-bordered?
That's what THE BLOCK and THE SCRIPT do. You could easily write a custom block with no name (you have to give a name to the Make a block dialog, but once you're in the block editor you can just change that name to the input name) and a Procedure-type input that just reports the input, if you want the grey-border abbreviation.
A not-well-documented feature is that you can shift-click on a block and BYOB will wrap a THE BLOCK or THE SCRIPT around it for you; that's another way to abbreviate lambdafication.
Offline
scimonster wrote:
bharvey wrote:
Maybe when we invent the version for the chips implanted in your children's or grandchildren's heads?
I don't like to think about that.
I don't either, really. Okay, we'll go to another major version number when we support running your programmable networked refrigerator.
Offline
I have an idea for Snap 4.0. Allow us to make the new types of blocks, e.g. like the script block without the C input. You should be allowed to make a C input if you want in the new block type tho, etc.
Offline
rdococ wrote:
I have an idea for Snap 4.0. Allow us to make the new types of blocks, e.g. like the script block without the C input. You should be allowed to make a C input if you want in the new block type tho, etc.
This already exists. Notice "Command (inline)" and "C-shaped" in the input type dialog below.
Offline
bharvey wrote:
rdococ wrote:
I have an idea for Snap 4.0. Allow us to make the new types of blocks, e.g. like the script block without the C input. You should be allowed to make a C input if you want in the new block type tho, etc.
This already exists. Notice "Command (inline)" and "C-shaped" in the input type dialog below.
http://byob.berkeley.edu/longinput.png
Actually, I was refering to if we could create blocks the shape of [the script], not having those inputs. Therefore it does not exist.
Offline