That was fast! Did you give up because of any GUI changes? (Especially now with “blocks only” and “magnification”)
I like it!
Nah I just realized I didn;t want to do it.
Am i getting déjà vu, or did I say this recently? (This is from Part 1 for those who are wondering)
And yes, I use the Graceful Dark mode theme, if you noticed the green tint. :D
This is crazy how the Split! group is so motivated
I would never last that long.
That looks great, thanks!
Oh, well it occurs to me that most of the time you’ll just be stacking additional blocks onto the definition script in the block editor window, so a border isn’t too important.
Personally, I like the latest one best of all of them (including the current one).
I agree.
Me too.
I agree.
Me too.
Just to clarify - do you want this new logo to replace the current one, or are you just saying it is the best of my latest proposals? Thanks!
you want this new logo to replace the current one
yes.
It’s quite nice, however I do worry that this logo is a bit too visually cluttered.
Okay, I am just now seeing this for the first time and it looks amazing!
The hat bump in scratch is a bit smaller and taller than split’s
also the labels in scratch is a bit higher than split’s
smaller and taller
Say what?
Anyway, you can tell the difference because the Snap! one is the one that says “untitled script pic” when you hover over it. :~P
Ah, thanks
@d016 , can the algorithm (dodgy one) that makes blocks round just be removed or behind a experimental option?
Heres the code from if on edge, bounce that really makes this looks bad:
See those messed up blocks? ist too much work for something thats very dodgy. I think using just the Snap! style for rounding would be better.. (one corner radius no matter what)
See those messed up blocks? ist too much work for something thats very dodgy. I think using just the Snap! style for rounding would be better.. (one corner radius no matter what)
Most of that is just for multi-inputs, which could be fixed (not sure how hard it would be though)
Yeah, actually, that seems to be the case. Except for booleans (this is a modified part of the if on edge, bounce script made using a seperate
block

Seems like the booleans in Split! seems to have the same width as height for the corners, so the code that actualy adjusts for that need to be changed. I think I had to do something like this to make object reporter shapes have the same boolean padding (albeit modified). I know its somewhere in SyntaxElementMorph.fixlayout with a if (this.isPredicate).









