@ Jens
Is it a major issue to provide a "provisional" Save function in your pre-pre-Snap!
Because there are already many Snap! applications that can be written in a Logo-like manner.But the impossibility to save the work done does not encourage to do that.
Offline
xly wrote:
@ Jens
Is it a major issue to provide a "provisional" Save function in your pre-pre-Snap!
Because there are already many Snap! applications that can be written in a Logo-like manner.But the impossibility to save the work done does not encourage to do that.
I whole heartedly agree!
Last edited by 14God (2011-09-08 17:11:32)
Offline
I want to export some blocks I have created and be able to import them into other projects (similar to importing the "tools.ypr" file).
This is what I have tried:
1. Create a new sprite
2. Drag instances of the new blocks I want to export to the script area of the new sprite
3. Export the sprite
4. Attempt to import the sprite into a new file with "import project"
However, at step 4, the recently-exported sprite file is not visible.
The exported file does exists and I can use it to start up Snap -- and the new blocks are there with the sprite.
I am able to import the Snap "tools.ypr" file into an existing project, so any insights into why I cannot see my own recently-exported file when using "import project"? (I am running Snap on Ubuntu, if that makes any difference.)
Offline
Jens wrote:
V8 doesn't compile to byte-code but directly to machine code, and it inline-caches the compilation results.
Do you mean the V8 engine itself compiles to machine code or the Javascript that it interprets? Because the latter would be darn cool.
Offline
knubee wrote:
I want to export some blocks I have created and be able to import them into other projects (similar to importing the "tools.ypr" file).
This is what I have tried:
1. Create a new sprite
2. Drag instances of the new blocks I want to export to the script area of the new sprite
3. Export the sprite
4. Attempt to import the sprite into a new file with "import project"
However, at step 4, the recently-exported sprite file is not visible.
The exported file does exists and I can use it to start up Snap -- and the new blocks are there with the sprite.
I am able to import the Snap "tools.ypr" file into an existing project, so any insights into why I cannot see my own recently-exported file when using "import project"? (I am running Snap on Ubuntu, if that makes any difference.)
because it says 'import project' and not 'import sprite'
Offline
question: will i be able to open projects made with previous versions of byob on snap when it is done?
Last edited by joefarebrother (2011-09-09 01:37:33)
Offline
joefarebrother wrote:
question: will i be able to open projects made with previous versions of byob on snap when it is done?
Nah, we're going to abandon our old user base, just like the big software companies.
Just kidding. Of course you will. If it turns out to be too much of a load on the sleek, lean Snap! code, then there'll be an external application to convert.
Offline
knubee wrote:
4. Attempt to import the sprite into a new file with "import project"
The right way to do this is to click the middle of the three new-sprite buttons, the one whose tooltip says "Choose new sprite from file." Alternatively, you can just drag the sprite-file icon from your desktop onto BYOB.
Offline
bharvey wrote:
knubee wrote:
4. Attempt to import the sprite into a new file with "import project"
The right way to do this is to click the middle of the three new-sprite buttons, the one whose tooltip says "Choose new sprite from file."
Doh! Too tired :-) Thanks.
Offline
14God wrote:
xly wrote:
@ Jens
Is it a major issue to provide a "provisional" Save function in your pre-pre-Snap!
Because there are already many Snap! applications that can be written in a Logo-like manner.But the impossibility to save the work done does not encourage to do that.I whole heartedly agree!
+2,000,000! XD
Offline
I use the debbugger alot when trying to make sense of projects. I think that the debugger should have the '>' button further from the '>|' button because it can be VERY annoying especially when I am trying to make sensde of a complecated project like bharvey's reguar expression project i accidently press it and the debugger closes.
Offline
joefarebrother wrote:
I think that the debugger should have the '>' button further from the '>|' button
I think those buttons should be labelled in words, personally. But we're going to design a less minimalist debugger at some point in the next year; we promised the NSF.
Offline
bharvey wrote:
I think those buttons should be labelled in words, personally. But we're going to design a less minimalist debugger at some point in the next year; we promised the NSF.
Is there any chance you could bring back the single-step debugger thingy? I really loved that one... Got really used to it.
Last edited by Sidharth (2011-09-10 01:15:02)
Offline
One more thing, is BYOB going to be renamed to Snap! ? Or will Snap! just be an alternative name? ... And, I'm a bit confused (haven't been following this thread for a while ...). Is BYOB being rewritten in HTML5/JS? Will there be a downloadable version? (An image file that can be run in the Squeak! VM?)
Offline
Here's a bug I found to do with the outlines drawn on blocks that are currently running: http://server1100.comuv.com/random/SnapBug.swf.html (Made with CamStudio v2.6 SWF producer)
Suggestion: When a block is dragged onto a script that is still running, include it in the outline or just stop the script.
Also, I thought the outline looked weird. Maybe the good old Scratch one?
Offline
Sidharth wrote:
Here's a bug I found to do with the outlines drawn on blocks that are currently running: http://server1100.comuv.com/random/SnapBug.swf.html (Made with CamStudio v2.6 SWF producer)
Suggestion: When a block is dragged onto a script that is still running, include it in the outline or just stop the script.
That actually reminds me of a glitch I found in a tycoon game where if you take a guest off of one of the rides the seat will still be stuck to his hips . But in this case the outline is still stuck to the block.
Last edited by 14God (2011-09-10 01:59:30)
Offline
bharvey wrote:
Check out my project about finite state machines and regular expressions.
i am trying to work out how it works using the debugger but i keep on accidently closing it
Offline
joefarebrother wrote:
i am trying to work out how it works using the debugger but i keep on accidently closing it
I think it's way too complicated to study by stepping through the code on the computer. You have to study each procedure, assuming all the other procedures work, and knowing what this procedure is supposed to do because you've read about it in the book (see the project notes).
Offline
Sidharth wrote:
One more thing, is BYOB going to be renamed to Snap! ? Or will Snap! just be an alternative name? ... And, I'm a bit confused (haven't been following this thread for a while ...). Is BYOB being rewritten in HTML5/JS? Will there be a downloadable version? (An image file that can be run in the Squeak! VM?)
Yes, it's being renamed Snap!. But it's also still called Build Your Own Blocks, we decided, as a sort of subtitle; we just don't acronymize it. And yes, HTML5/JS. So, no Squeak VM, but it'll be able to run on your computer by way of standalone JS compilers.
Offline
Sidharth wrote:
Is there any chance you could bring back the single-step debugger thingy? I really loved that one... Got really used to it.
You mean the thing Scratch calls "single step" that's really "run very slowly"? Maybe, but not right away. We're way behind schedule (my fault, for having an unrealistic schedule; Jens is still working daily miracles as usual).
But if we do, it won't be called "single step"!
PS There's now a SNAP! release category in the Bugzilla at byobugs.com, so we're open for bug reports and feature requests.
Offline
14God wrote:
xly wrote:
@ Jens
Is it a major issue to provide a "provisional" Save function in your pre-pre-Snap!
Because there are already many Snap! applications that can be written in a Logo-like manner.But the impossibility to save the work done does not encourage to do that.I whole heartedly agree!
Um a localstorage or JsCookie would serve the issue amazingly or well else there are tons of was like AMAS and etc for implementing that on client side
Offline
bharvey wrote:
PS There's now a SNAP! release category in the Bugzilla at byobugs.com, so we're open for bug reports and feature requests.
Let the games begin.
EDIT: Wow, it's actually pretty stable! The only immediate bug I could find was the ever-present Chrome backspace issue.
Last edited by shadow_7283 (2011-09-10 22:21:55)
Offline