@alloplastic
Right now Snap! allows to share 1 -projects 2 - blocks 3 -sprites.
Pls send your email at [removed by moderator - please don't share contact information]
I shall send you one "sprite" exported from Snap!
@Jens : How is it possible to delete the "turtle" costume ?
Last edited by Paddle2See (2013-04-14 17:27:02)
Offline
WebSockets?
EDIT: I was replying to
joefarebrother wrote:
It will be cool if there was some functionality to allow snap! to communicate with BYOB 3, Scratch 1.4, Panther, and other modifications.
and thought it was the last post in the thread...
Last edited by Hardmath123 (2012-12-23 01:52:51)
Offline
Hie Xavier,
the "turtle" costume isn't technically a costume at all, but the default appearance when no costume is selected or even present. It doesn't take up any memory or disk space in the projectfile.
Offline
Jens wrote:
Hie Xavier,
the "turtle" costume isn't technically a costume at all, but the default appearance when no costume is selected or even present. It doesn't take up any memory or disk space in the projectfile.
... and, most importantly, it isn't part of the "next costume" rotation. (Nevertheless, it's costume 0 if you ask for that explicitly.)
Offline
joefarebrother wrote:
It will be cool if there was some functionality to allow snap! to communicate with BYOB 3, Scratch 1.4, Panther, and other modifications.
I think it's really only an issue with Panther, b/c Snap! can read BYOB and Scratch projects.
And once we can handle files and web pages, we'll pretty much be a superset of Panther.
Offline
And colors, I guess.
Offline
@Jens, bharvey & nXIII
Thanks for the turtle costume, it is OK for me.
There is an issue with TOUCHING color.
Very high ressource consumption (impossible to have 3/4 simple mobiles moving alltogether).+ frequent Chrome crashes (which is very unusual with Snap!)
Offline
I keep getting a 'Save failed: Error: SECURITY_ERR: DOM Exception 18' error when I try to save a project. D:
Offline
Merry Snap! Christmas night! (and thanks to MyRedNeptune for the project!)
Last edited by Jens (2012-12-24 04:05:09)
Offline
bharvey wrote:
Hardmath123 wrote:
And colors, I guess.
Jens is working on that as we speak. Not exactly like Panther but color as a data type is coming.
Will it be compatible with panther?
Offline
Jens wrote:
Merry Snap! Christmas night! (and thanks to MyRedNeptune for the project!)
Sweet! That would make an awesome Google Doodle!
Offline
Jens wrote:
Merry Snap! Christmas night! (and thanks to MyRedNeptune for the project!)
This has been in there for a while, but I just wanted to bring it up again: Snap! lags quite a bit when I click and drag my mouse. It looks like isTransparentAt and visibleBounds take a huge amount of time to execute: in a short sample I took, isTransparentAt took 36% of the execution time and visibleBounds took 28%. The entire program execution took only slightly less than 50% of the profile time. We should definitely look into optimizing those two methods as well as reducing the amount of time spent on stepping each frame.
EDIT: In addition, just moving the mouse around in editor mode caused Snap! to spend about 10% of the profile time processing the mouse motion.
Last edited by nXIII (2012-12-24 13:20:57)
Offline
Future feature request: When you implement OOP, please give sprites an option to be impossible to delete from a script. It's not very fun to have a bug that deletes your 'class' sprite after working on it for a long time. Of course, I'm still an advocate of class based OOP instead of prototyping.
Offline
BornAgainAtheist wrote:
Future feature request: When you implement OOP, please give sprites an option to be impossible to delete from a script. It's not very fun to have a bug that deletes your 'class' sprite after working on it for a long time.
Good idea.
Of course, I'm still an advocate of class based OOP instead of prototyping.
Bad idea.
Offline
BornAgainAtheist wrote:
Future feature request: When you implement OOP, please give sprites an option to be impossible to delete from a script. It's not very fun to have a bug that deletes your 'class' sprite after working on it for a long time. Of course, I'm still an advocate of class based OOP instead of prototyping.
Yeah, once I was implementing an interface for class/instance OOP rather than prototyping and a small bug in my coding caused everything to be deleted when I tested a script. I think dynamic deletion should be an undo-able action.
Also, when we have first class pictures and sound, can you add a block or two to dynamically create a sprite: costumes, scripts, sounds, variables, and all, instead of just a clone of an existing sprite. (of course the clone block will still be there too.)
bharvey wrote:
class based OOP
Bad idea
Why? It's a way to solve the dynamic deletion problem, and it is more common in OOP programming languages.
Last edited by joefarebrother (2012-12-28 13:37:59)
Offline
joefarebrother wrote:
Also, when we have first class pictures and sound, can you add a block or two to dynamically create a sprite: costumes, scripts, sounds, variables, and all, instead of just a clone of an existing sprite.
The goal is that costumes, scripts, and sounds will eventually be first class too, so we won't need one monster block to create all of them; the new object can have an init method that creates those things. I agree that a way to create variables within a script would be good (although right now a script can't use a variable that didn't exist when it was written).
Why? It's a way to solve the dynamic deletion problem, and it is more common in OOP programming languages.
(Sigh.) You didn't quote the tongue-out smiley, which was an acknowledgement that B.A.A. and I have had this argument before. You can scroll back and look up that discussion but here's a summary, Two reasons:
0. We're not in the business of training future Java programmers, so what they do shouldn't influence us.
1. Given prototyping OOP, it's trivial to simulate class/instance (hint: HIDE) but not the other way around.
2. Class/instance requires that you plan out your object hierarchy before you start coding. Prototyping is way more accommodating to exploration and tinkering, which is what our target audience is mostly doing; once a project is done you start another project.
EDIT: It makes me feel really old to think you're probably all too young to have gotten the reference to "Good idea, bad idea" on Animaniacs!, which didn't start until I was already an adult.
Last edited by bharvey (2012-12-28 13:54:57)
Offline
For anyone who wants to be enlightened.
Offline
bharvey wrote:
EDIT: It makes me feel really old to think you're probably all too young to have gotten the reference to "Good idea, bad idea" on Animaniacs!, which didn't start until I was already an adult.
I got the reference.
Offline
shadow_7283 wrote:
For anyone who wants to be enlightened.
Trust me, they're a lot funnier spread out over five years.
Offline
bharvey wrote:
technoboy10 wrote:
I got the reference.
Oh, good, maybe I'm not so old after all.
By the way, just so this subthread isn't totally off-topic, note that Animaniacs! and Snap! have something in common.
They have an exclamation mark at the end of them?
They also both have an s, an n, and an a.
Offline
joefarebrother wrote:
They have an exclamation mark at the end of them?
They also both have an s, an n, and an a.
Lots of words have those letters, but how many names end in exclamation points? It wasn't conscious, but I bet I wouldn't have thought of the exclamation point had it not been pioneered by Animaniacs!.
Offline