dreamod wrote:
I think snap! is cool and BYOB has greatly inspired my mod dream. I love BYOB!
(by the way, 6000th post!)
Did you post that just to get the 6,000th post?
Offline
Hardmath123 wrote:
dreamod wrote:
I think snap! is cool and BYOB has greatly inspired my mod dream. I love BYOB!
(by the way, 6000th post!)Did you post that just to get the 6,000th post?
Did you post that just to get the 6,001st post?
Offline
Did anyone know that in BYOB 3 if you right-click the stage icon it comes up with a sprite selector? 0_0
Last edited by shadow_7283 (2012-09-30 18:28:03)
Offline
bharvey wrote:
srtate wrote:
Move the exact same reporter block into a "set" block with a dummy variable - and nothing else - and it takes 25 seconds.
Was there a stage watcher for that variable? Updating the display takes more time than computing the value.
No, no watch variables set. Just straight computation - or at least it should be.
Apparently I can't post a live link, but here's the URL of a very simple example (a page with a short explanation and a link to the BYOB file):
http://www.uncg.edu/cmp/faculty/srtate/100.f12/byobstrangeness.php
Offline
dreamod wrote:
I think snap! is cool and BYOB has greatly inspired my mod dream. I love BYOB!
(by the way, 6000th post!)
That's actually the 6000th reply.
That was the 6001st post.
Offline
srtate wrote:
No, no watch variables set. Just straight computation - or at least it should be.
That is strange. It's nothing special about SET, either; if I put the MAX in a SAY block it takes forever, too. Jens?
Offline
Yeah, we know that BYOB 3's execution engine has all kinds of problems and bugs, because we've had to bent it so much to make it do all the stuff it wasn't meant to do in Scratch (recursion, first-class-lists, lambda, message passing). The good news is that your Max Test Project works perfectly well in Snap! 4.0, displaying all the intended behavior.
The other good news is that Snap! 4.0 is already very complete, usable and supported. Granted, cloud storage would be nice (and is about to be added), so is music support, but those aren't major deficiencies. The only reason BYOB 3 is still in use this semester is that the BJC course materials haven't been updated to Snap! 4.0 yet.
Last edited by Jens (2012-10-01 03:39:21)
Offline
Cloud data? Cool! How are you going to do it; PHP/Python server-side code, or something cleverer?
Last edited by Hardmath123 (2012-10-01 04:50:16)
Offline
xly wrote:
@Jens
What about OOP inheritance blocks CLONE, ATTRIBUTE, OBJECT, property OF sprite ??
Yup, OOP will also come, and soon, but I'd prefer to add those features in 4.1 (similar to the BYOB 3 to 3.1 step), getting 4.0 out of the door before.
Offline
Hardmath123 wrote:
Cloud data? Cool! How are you going to do it; PHP/Python server-side code, or something cleverer?
Wait, Cloud data will also come, but first wil be Cloud storage for 4.0. And yes, everything will be incredibly clever, of course!
Offline
Jens wrote:
Hardmath123 wrote:
Cloud data? Cool! How are you going to do it; PHP/Python server-side code, or something cleverer?
Wait, Cloud data will also come, but first wil be Cloud storage for 4.0. And yes, everything will be incredibly clever, of course!
Will we be able to save projects to the server and share them like on Scratch?
Offline
Jens wrote:
Yeah, we know that BYOB 3's execution engine has all kinds of problems and bugs, because we've had to bent it so much to make it do all the stuff it wasn't meant to do in Scratch (recursion, first-class-lists, lambda, message passing). The good news is thatyour Max Test Project works perfectly well in Snap! 4.0, displaying all the intended behavior.
The other good news is that Snap! 4.0 is already very complete, usable and supported. Granted, cloud storage would be nice (and is about to be added), so is music support, but those aren't major deficiencies. The only reason BYOB 3 is still in use this semester is that the BJC course materials haven't been updated to Snap! 4.0 yet.
OK, so I'll look more into moving to Snap! - when I was planning out this course Snap! didn't seem quite ready for prime time. Having the pre-loaded sprites that come with BYOB make it considerably more engaging right out of the box, and it's still not clear to me how project storage works (in my dream world there would be an online storage repository that I could set up and have students link to me or a grader so that we could pull up projects directly - and versioned storage would be even better... and if I could tag parts of the code with notes... and... and... and... OK, I'll stop).
Offline
Right now, you can either save projects to local storage, or - better - export them to regular files. Just select "Export project..." in Snap's File menu, and save the resulting browser page (which displays an XML representation of your project) to your disk. You can open saved projects simply by dragging and dropping them (the XML files) onto Snap!, or via a native File dialog by selecting "Import..." in Snap's File menu.
Oh, and you can, of course, import any of Scratch's / BYOB's costumes, backgrounds or sounds the same way (drag & drop - even multiple selections for stop-motion animations - or via the "Import..." menu option).
And yes, there is going to be an online storage repository with bells and whistles, but saving, exporting, and loading already works quite well even without! Please let me know if something doesn't work for you and I'll be glad to hasten to the rescue
Offline
nathanprocks wrote:
Will we be able to save projects to the server and share them like on Scratch?
Save, pretty soon; share, maybe, after we get the political implications (about site policing etc) worked out.
Offline
boukeas wrote:
Now, another problem of a different flavour: I run BYOB in Greek. When I create a new block, its name looks perfectly normal (see http://db.tt/0k3TItq3). However, when I try to add a parameter to the block characters do not display normally anymore, even those that used to (http://db.tt/GURGwt6G). Any thoughts?
Ok, since this has gone unanswered, let me ask: will it be possible (at some point) to localize Snap! so that it can support other languages?
Offline
boukeas wrote:
let me ask: will it be possible (at some point) to localize Snap! so that it can support other languages?
Sorry for not answering promptly. I'm happy to report that I'm working on a localization mechanism at this very moment, and expect to have a first version ready in a few days. In my local dev environment I'm already switching back and forth between English and - an as of now still incomplete version of - German.
It would awesome if you were willing to contribute the Greek translation for Snap!
Offline
Jens wrote:
boukeas wrote:
let me ask: will it be possible (at some point) to localize Snap! so that it can support other languages?
Sorry for not answering promptly. I'm happy to report that I'm working on a localization mechanism at this very moment, and expect to have a first version ready in a few days. In my local dev environment I'm already switching back and forth between English and - an as of now still incomplete version of - German.
It would awesome if you were willing to contribute the Greek translation for Snap!
RTL also planned?
Offline
Jens wrote:
I'm happy to report that I'm working on a localization mechanism at this very moment, and expect to have a first version ready in a few days. [...]
It would awesome if you were willing to contribute the Greek translation for Snap!
In principle I would be more than happy to, but I guess it depends on what it would practically involve. The standard .po files used for localization are text files with msgid, msgstr pairs, i.e. original strings along with their translations. If something similar is used in the mechanism you are implementing then a large part of the localization effort can be automated using the existing .po files. Is this the case?
Offline
Jens wrote:
Hardmath123 wrote:
Cloud data? Cool! How are you going to do it; PHP/Python server-side code, or something cleverer?
Wait, Cloud data will also come, but first wil be Cloud storage for 4.0. And yes, everything will be incredibly clever, of course!
*COUGH* node.js
Offline