Scratch

Will there be an easier way to access the source code in future versions of BYOB? I would love that, because the elements editor is just not enough, and I can't get the workaround with the Preferences enableProgrammerFacilities thing to work 

bharvey wrote:

Sidharth wrote:

Will there be an easier way to access the source code in future versions of BYOB?

In the BYOB folder is a file called "BYOB Development" (with extension .sh or .bat depending on your OS).  Just double-click it.

As from 4.0, the source code is Javascript and will be provided as plain text files.

Thanks! That really helps 

Snap! update

Folks, as you know we've been pretty busy getting started with the next version of BYOB. It will be a complete re-write entirely in JavaScript and HTML5, and it will be renamed to "Snap!". I'm very pleased to announce that as of yesterday we have the beginnings of a very first experimental interactive version up and running in the web browser. Don't expect much, as of right now it's basically a bunch of simple blocks that can be applied to a single LOGO turtle-like sprite thing, not more than a proof of concept, really. But hey, we're finally starting to get something Scratch-like right in our web-browsers.

Here's a screenshot that'll take you to our "nasciturus" (=unborn, pre-pre-pre-alpha) prototype:



Enjoy!

Cool!

i have another idea for first classness: first class pictures. there would be blocks like:
(picture of costume ())
((picture input) rotated () degrees cw)
(screen region of rectangle x:() y:() to x:() y:())
([colour picker] < (left and right arrows) > with width() and height())
((picture input) scaled by ())
|add costume (picture input) with name()at ()th in costume list|
|delete costume()|
|stamp (picture input)|
and there should also be first class colours with panther blocks and also a CYOB function

Last edited by joefarebrother (2011-08-11 07:06:17)

joefarebrother wrote:

i have another idea for first classness: first class pictures. there would be blocks like:
(picture of costume ())
((picture input) rotated () degrees cw)
...

We definitely plan on first class costumes, probably in 4.1.  (No major new features in 4.0; it'll be all we can do to recreate the old features!)  I'm not sure it's necessary to have another level of abstraction to distinguish a costume from its picture; I know that costumes have other attributes but still I'm leaning toward an interface in which a costume just is its picture, so ITEM (#) OF (costume) returns a row of pixels, and ITEM of that returns a single pixel.  But maybe not; some days I think you should say

[[ATTRIBUTE (BITMAP)] OF (costume)]

Picture modification blocks such as your ROTATED example should be able to be written in Snap!!  [The first one is part of its name.  ]  If you have access to the individual pixels, and if we make the evaluator fast enough, you can do all that sort of algorithm yourself, which is not only more elegant (we don't want the Snap! palette to look like the Photoshop palette) but more of a learning experience.  (And of course people will publish libraries of such blocks.)

P.S.  On the third hand, someday we should move to representing pictures as vectors and splines!

Last edited by bharvey (2011-08-11 15:01:20)

This is getting exciting like it was when you started releasing the first class sprites and inheritance beta.

14God wrote:

Bump

It's not the end of the world if we're off the front page for a while.   

Don't worry, we'll have plenty of traffic when 4.0 comes out!

a question-is there a way to store the block [say var] in the memory, so it will say what var is at the save time, and not at run time?

roijac wrote:

a question-is there a way to store the block [say var] in the memory, so it will say what var is at the save time, and not at run time?

SAY-REMEMBERED (what-to-say)
    REPORT [THE SCRIPT
                          SAY (what-to-say)]

To remember a value:
    SET (sayer) TO [SAY-REMEMBERED (var)]

To say the remembered value:
    RUN (sayer)

Was that what you wanted?

bharvey wrote:

roijac wrote:

a question-is there a way to store the block [say var] in the memory, so it will say what var is at the save time, and not at run time?

SAY-REMEMBERED (what-to-say)
    REPORT [THE SCRIPT
                          SAY (what-to-say)]

To remember a value:
    SET (sayer) TO [SAY-REMEMBERED (var)]

To say the remembered value:
    RUN (sayer)

Was that what you wanted?

Thanks for the info, but this isn't what I meant to 
I meant such a script:

it should say "Hello", and not "Don't say that"

roijac wrote:

...

Out of curiosity, where did you find a block called THE BLOCK WITH INPUTS?