colabcalub wrote:
How do acturly make blocks with the make a block function? I can't work it out.
You enter the name of you new block and then drag blocks from the palette into the block editor. Check out the examples and tutorials, too. There are lots of them
Offline
Can you make new blocks that can be used in the BYOB area, with elements? And if so, how?
Offline
Build Your Own Blocks -- With other blocks
It's quite complicated, but I love it
Offline
BlackMarket wrote:
Build Your Own Blocks -- With other blocks
It's quite complicated, but I love it
Build your own blocks using blocks you built using blocks?
Offline
ironmannn wrote:
ive made a login block with the v2.29 version of byob
but the offical block will be out on my site soon.
Login block? What does it look like?
I just has a go at it, it seems to work:
The script
The block
Last edited by markyparky56 (2010-07-06 07:15:03)
Offline
Jens wrote:
colabcalub wrote:
How do acturly make blocks with the make a block function? I can't work it out.
You enter the name of you new block and then drag blocks from the palette into the block editor. Check out the examples and tutorials, too. There are lots of them
But for somereason the examples don't work.
Offline
colabcalub wrote:
But for somereason the examples don't work.
Please give us a specific example that doesn't work, and what response you get when you try it.
Or you can report bugs directly at http://byobugs.com.
Offline
markyparky56 wrote:
One little programming detail: There's no need to say
LAUNCH ...
STOP BLOCK
That combination is exactly equivalent to RUN ... .
Oh, P.S., real security mavens say that you shouldn't tell people which of username and password didn't work; instead collect both of them and either accept or deny them as a unit.
EDIT: I'm sorry, not "exactly equivalent," but exactly equivalent as you've used them, where the block is going to stop anyway because there's nothing left to do after the IF/ELSE. I should have said that LAUNCH+STOP is the same as RUN+STOP.
Last edited by bharvey (2010-07-06 23:21:39)
Offline
markyparky56 wrote:
Can you make new blocks that can be used in the BYOB area, with elements? And if so, how?
Here, look at my post in this thread: http://scratch.mit.edu/forums/viewtopic.php?id=39080
Offline
BlueFlame wrote:
Can you export your blocks into normal Scratch, or save them so that you can use them with any project?
No, sorry. Not until we talk the Scratch Team into incorporating BYOB into Scratch 2.0.
Offline
Grin1 wrote:
how to you get byob blocks into scratch
You shouldn't, and can't. The point of a Scratch modification is so that it is different than Scratch. It is illegal to post Scratch modification projects because it is against the Scratch Terms of Use. If you make/import the given block into Scratch without it turing into an
[obsolete!]
block, then it would be illegal to share it. Kind of. Even if it is legal, it is rude and frowned upon. If you do want to share your project with people, you can ask your family, friends etc. Or you could edit the player that Scratch already has and share it on a separate website.
Offline
bharvey wrote:
colabcalub wrote:
But for somereason the examples don't work.
Please give us a specific example that doesn't work, and what response you get when you try it.
Or you can report bugs directly at http://byobugs.com.
It's ALL the examples, and there is no scripts.
Offline
Is there any simple squeak/smalltalk I could use to implement new block names for existing blocks through the 1.4 source code?
Offline
bobbybee wrote:
Is there any simple squeak/smalltalk I could use to implement new block names for existing blocks through the 1.4 source code?
yeah there is.
Turn fill screen off, open a browser, and go to Scratch-Objects>ScriptableScratchMorph (make sure you have 'class' selected)>block specs>blockSpecs, and change block names there. Here is how to do that:
you will see a lot of things that look like: ('bla bla bla' #- #blaBlaBla). let's take the |wait (1) secs| block for example. Find this: ('wait %n secs' #- #duration:elapsed:from: 1) change the 'wait %n secs' to whatever you want, just keep the %n. For example change it to 'delay %n' and the block will now look like |delay (1)|. If you need additional information (call this toll free number ......... just joking) click this smiley:
Last edited by ScratchReallyROCKS (2010-07-13 20:21:39)
Offline
it's not working
Offline
bobbybee wrote:
it's not working
Oh. Sorry, I was in a hurry, here's a better tutorial:
http://scratch.mit.edu/forums/viewtopic.php?id=31200
Offline
How do you make a block like the one in "Polygons" in BYOB?
Offline
Jens and I are extremely pleased to announce (finally!) the release of BYOB 2.995 beta. You can download the Macintosh and Windows files-only version (just put it in /Applications on a Mac) or the Windows installer. You should download the complete package even if you already have BYOB, because of changes to the manual, the help files, the compiler, the dev access, etc.
Jens wrote:
Windows installer: It's best not to select the default folder offered by the installer (C:\program files\BYOB) but to select some other folder that is not a subfolder of Vista's paranoid UAC system. BYOB will run fine from C:\program files\BYOB, but editing the source code and trying to open Elements may lead to strange, Vista-related error messages. These don't happen if you select another folder.
One major change since the last alpha: By popular demand, BYOB now has special forms. This means that you can declare a block input slot to be of type "Any (unevaluated)" or "Boolean (unevaluated)"; these inputs look to the block's caller like Any or Boolean, but actually behave like Reporter or Predicate respectively -- the expression you drag onto that input isn't shown with a grey border, but in fact BYOB puts an invisible THE BLOCK around it. The first and most important application is in tools.ypr 1.6, in which the reporter IF/THEN/ELSE block is intuitively usable by someone who doesn't know anything about procedures as data. This also means we can explain the behavior of the Scratch looping and conditional blocks' hexagonal input slots with the truth: They are of type Boolean (unevaluated), not of type Predicate. (You'll remember that this was a point of confusion for several alpha users!) The shapes and colors of the input slot types have been changed to reflect this new story.
Also new in this release: the "compile" option works on the Macintosh as well as on Windows.
Finally, in the folder are files named "BYOB development.sh" (Mac) and "BYOB development.bat" (Win) that can be double-clicked to open BYOB in developer mode. Shift-click the Edit menu to get access to the Smalltalk browser and the full source, comments and all.
Many. many thanks to all of you who've helped us get this far. There are still bugs and missing features, but it's in so much better shape than 2.99.000 because of your contributions!
Offline
I'm trying to use the .changes file to add BYOB to Slash, but I can't. Can anyone help?
Note: if you try, download the .image as of now, I just updated it.
Update: I've made a bit of progress, but it's hard. Does anyone have advice?
Last edited by Billybob-Mario (2010-07-24 19:01:13)
Offline
Many comments in the changeset cause errors, making it unusable. Could you make a comment-free changeset or something?
All of the problems are from the "I am the...
"I represent...
and similar things above many methods.
So far I've had to type in the classes myself and delete lots of comments, but it's near impossible.
Last edited by Billybob-Mario (2010-07-25 10:34:29)
Offline
Hi Billybob-Mario,
it's great that you're trying to incorporate BYOB in your Scratch mod! That's exactly why we made it easy to switch into development mode. Unfortunately, it's not just importing a file (like the .changes file) that will make it work. Also, the comments shouldn't be the problem. What you need is the changesets in their correct order. But these aren't really well kept in BYOB, because mostly I've been hacking away under great time pressure, often switching back and forth between changesets, and sometimes not creating new ones when I should have. Also, BYOB fundamentally changes almost everything internal in Scratch, even the most simply code like moving a Sprite forward by 10 steps, because of the nested sprites feature. Therefore my advice would be to do it the other way round: Why not file out your changes file them into BYOB and make the adjustments you need. I'm pretty sure that this would be way easier and might just work.
Good luck!
Last edited by Jens (2010-07-25 17:18:51)
Offline