Maybe we should just call it Snap. I like that better than 'First Snap' or 'Second Snap'.
Offline
rubiks_cube_guy238 wrote:
'Objective Scratch'.
We can't use "Scratch" in the name -- that would violate the source code license. (Someone at the conference here suggested "Itch" but that would kind of be getting it backwards. )
Offline
fullmoon wrote:
Maybe "Change Blocks By 1" would be a better fit.
Maybe we could call it Snap or something? It's simple at least.
I like it. It would even fit in the same space as the BYOB in the corner. Of course it ruins my idea of a logo with a Reporter slot for the "O." But it'll reassure people that programming in it is still a snap!
Offline
I think it's good. Now to change EVERYTHING.
Offline
bharvey wrote:
Maybe we could call it Snap or something? It's simple at least.
Of course it ruins my idea of a logo with a Reporter slot for the "O." But it'll reassure people that programming in it is still a snap!
Why not SNOP, to keep a reporter slot for the O (it reminds Snoopy the well-known cartoon character )
Offline
xly wrote:
bharvey wrote:
Maybe we could call it Snap or something? It's simple at least.
Of course it ruins my idea of a logo with a Reporter slot for the "O." But it'll reassure people that programming in it is still a snap!
Why not SNOP, to keep a reporter slot for the O (it reminds Snoopy the well-known cartoon character )
I don't like it. It sounds to much like 'Snot'.
And for a new 'Snap' logo, it could show the blocks
SNAP(the script [imagine][program][share])
where SNAP would be a custom block. I know it isn't acurate because there isn't really a good way to share 'Snap' projects, but its just an idea.
Last edited by rubiks_cube_guy238 (2010-08-17 20:14:00)
Offline
xly wrote:
bharvey wrote:
Maybe we could call it Snap or something? It's simple at least.
Of course it ruins my idea of a logo with a Reporter slot for the "O." But it'll reassure people that programming in it is still a snap!
Why not SNOP, to keep a reporter slot for the O (it reminds Snoopy the well-known cartoon character )
Ooh! That's a good idea! And then we could make a snoopy mock-up as the main mascot xD. But ignoring that second part, it seriously sounds good!
Offline
SNOP? Nah. It doesn't really have Snap's elegance.
Offline
*looks at signatures* O_o BYOB3 is complete!? *downloads* *plays with it*
Time to update Scratch Wiki...
Offline
bharvey wrote:
xly wrote:
Hey, are you at Eurologo? I don't think I've seen you.
I'm to attend your conference and others to-morrow .
In the meantime I give you my last view on your projects : considering the high-level of possibilities attained of Byob today - thanks to the mixing of powerful capabilities of Scratch+Logo+Lisp+High Class - I can hardly imagine you accepting now to limit your project to a small unambitious cosmetic extension of Scratch whose team agenda - although highly respectable - is very far from yours.
In the meantime hat do you think of SMOP ?
Offline
xly wrote:
What do you think of SMAP, you lose the O but you gain an acronym : "SMArt Programming"
I like the acronym, but it sort of reminds me of "SPAM" ;D. I think Snap is better.
Offline
I like Snap, the name itself stands out (well at least to me) just like Scratch. (In a good way) Something that is easy to remember and not something that would end up making people confused like what Shadow said:
shadow_7283 wrote:
I've had trouble communicating the name when telling other people about BYOB.
"So there is this new program called BYOB-"
"What?!"
"It's Build Your Own Blocks."
"Oh."
Lol, now you see.
Offline
fg123 wrote:
So, snap it is?
We're leaning that way, although we'd need some time to relabel every document on the web site (and the web site itself), etc., before we could make an announcement.
And, sadly, "snap.berkeley.edu" is already taken, which would be a serious obstacle. (Yeah I know, "snapprogramming" or something, but that makes it much harder for people to find.)
It just occurred to me last night that maybe we want to make it "SNAP!" including the exclamation point. But anyway this web site question may make us rethink it.
Offline
bharvey wrote:
fg123 wrote:
So, snap it is?
It just occurred to me last night that maybe we want to make it "SNAP!" including the exclamation point. But anyway this web site question may make us rethink it.
Why not SMAP which is not - as far as know - an english depreciated word
@bharvey & jens
Congratulations for your presentation this morning which has risen an immense interest amongst the "high-level" audience. The time for questions/answers was too short. Just an extract of Q/A :
Q to Mitch Resnick - "Why have you not implemented procedures into Scratch ?"
A of MR - "Because kids don't like procedures."
So if kids don't like literature, math, biology...school, give them a ball and let them play on the schoolground.
Offline
bharvey wrote:
And, sadly, "snap.berkeley.edu" is already taken, which would be a serious obstacle. (Yeah I know, "snapprogramming" or something, but that makes it much harder for people to find.)
You could register snaplang.org or snap-lang.org, after Ruby which uses ruby-lang.org. This would simply redirect to the Berkeley site you already have set up, which could then have as obscure a name as you like.
Offline
It's been a quiet week.
Offline
Which is why....
*BUMP*
I think this is the first time we've had to bump this topic...
Offline
I have a BYOB 3.1 idea.
We should have a checkbox instead of a slider for boolean variables! (If you set a variable to <true> or <false> then it becomes boolean)
EDIT: I just noticed you can insert regular reporters in boolean reporter spaces! Which would be an awesome feature, but why do I get a red outline when I do this?
[blocks]
<if> <not> <{ boolean }> >>
[/blocks]
Last edited by shadow_7283 (2010-08-22 11:25:49)
Offline
shadow_7283 wrote:
I have a BYOB 3.1 idea.
We should have a checkbox instead of a slider for boolean variables! (If you set a variable to <true> or <false> then it becomes boolean)
Yes, that'd be a nice UI feature. I think it'd have to be something you explicitly ask for, though, same as you can ask for a slider, because the type of a variable is just the type of whatever value it happens to have right now. You could set a variable to FALSE and then later set it to 17.
EDIT: I just noticed you can insert regular reporters in boolean reporter spaces! Which would be an awesome feature, but why do I get a red outline when I do this?
This is much the same issue, actually. BYOB doesn't know what value your reporter will report. It might happen to be TRUE or FALSE, in which case you can use that reporter meaningfully in a Predicate slot. But on some other occasion it might return 17. So it's syntactically legal to put any custom reporter in a Predicate slot, but when the program actually runs, if the reporter doesn't report TRUE or FALSE, eventually some primitive block such as IF will signal an error.
P.S. It may have been a quiet week for the rest of you, but Jens and I have spent it short on sleep at the Logo conference (Constructionism 2010) in Paris! I just got home last night, still not unpacked.
P.P.S. Maybe the world will survive if BYOB isn't on the front page.
Offline