Discuss Scratch

MinecraftM153
Scratcher
100+ posts

Scratch 3.0 Technical Discussion

-Simplify- wrote:

I think you should add an Else - If block.

No, you can already replicate it using normal means
Greenduck54
Scratcher
500+ posts

Scratch 3.0 Technical Discussion

MinecraftM153 wrote:

-Simplify- wrote:

I think you should add an Else - If block.

No, you can already replicate it using normal means
Yes, it's workaroundable, but which is clearer to read?
This:
if <...> then 
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
...
end
end
end
end
end
end
end
end
end
end
end
end
Or This:
//same script as above
if <...> then //couldn't make else if go into the block itself :P
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else
...
end
I'd prefer the second one for long scripts like that. This is why people suggest else if. Not because they need it for something, but so they can more easily read their code.

Last edited by Greenduck54 (April 27, 2018 17:16:54)

77Tigers
Scratcher
62 posts

Scratch 3.0 Technical Discussion

Greenduck54 wrote:

I'd prefer the second one for long scripts like that. This is why people suggest else if. Not because they need it for something, but so they can more easily read their code.
Here's a more readable workaround:
define workaround (input)    
if <(input)... ::operators> then
...
stop [this script v]
end
if <(input)... ::operators> then
...
stop [this script v]
end
(Also:
if <> then {
} else if <> {
} else {
}::control
)

Last edited by 77Tigers (April 27, 2018 18:13:43)

_nix
Scratcher
1000+ posts

Scratch 3.0 Technical Discussion

77Tigers wrote:

Here's a more readable workaround:
define workaround (input)    
if <(input)... ::operators> then
...
stop [this script v]
end
if <(input)... ::operators> then
...
stop [this script v]
end
That's a good workaround, except for when you want to put a “stop this script” into the elseif itself – then you have to do something like this:

define my block
say [hello!!!!]
workaround
if <(stop this script) = [yes]> then
stop [this script v]
end
say [whee]

define workaround
set [stop this script v] to [no]
if <some condition :: grey> then
...
stop [this script v]
end
if <some condition :: grey> then
set [stop this script v] to [yes]
stop [this script v]
end
if <some condition :: grey> then
...
stop [this script v]
end

But this discussion is really better fit for a discussion thread specifically dedicated to else-if.
NitroCipher
Scratcher
500+ posts

Scratch 3.0 Technical Discussion

Just a reminder, this thread is meant to be focused on information, discussion, and questions.
This is not a place for suggestions, for that go here
ACE009
Scratcher
100+ posts

Scratch 3.0 Technical Discussion

s_federici wrote:

I found a bug. When you have several extensions loaded, or you are maybe using a small screen, the scroll bar of the category list goes above the blocks in the palette.
I saw this too. The main problem is that variable check-boxes are completely hidden.
ACE009
Scratcher
100+ posts

Scratch 3.0 Technical Discussion

Another problem: broadcast and variable drop down menus don't have a data-argument-type tag like the rest of the inputs do, messing up CSS styles for the editor.
LEGAMER4665
Scratcher
84 posts

Scratch 3.0 Technical Discussion

In the 3.0 version (not just the gui), It will be the
for each [ v] in (10) :: variables
block?
_nix
Scratcher
1000+ posts

Scratch 3.0 Technical Discussion

LEGAMER4665 wrote:

In the 3.0 version (not just the gui), It will be the
for each [ v] in (10) :: variables
block?
That hacked block will be supported, so projects that use it will still work, but it won't be in the block palette (i.e. the list of blocks).
MrMeowington
Scratcher
100+ posts

Scratch 3.0 Technical Discussion

infinitytec wrote:

A bunch of people wrote:

-snip-
The new style is going to extend to every page.
I'm not sure there will be many other tweaks. As far as I know the homepage will be staying the same.
I don't know; this part

seems pretty 2.0ish and should probably be changed. Also, the entirety of the discussion forums just SCREAMS 2013.

Last edited by MrMeowington (April 28, 2018 03:17:58)

Sheep_maker
Scratcher
1000+ posts

Scratch 3.0 Technical Discussion

MrMeowington wrote:

I don't know; this part

seems pretty 2.0ish and should probably be changed.
Why should it be changed? There's nothing wrong with it. Just because the website underwent a rewrite between 1.4 and 2.0 doesn't mean it has to happen for every major update of the Scratch editor.

MrMeowington wrote:

Also, the entirety of the discussion forums just SCREAMS 2013.
They haven't started the redesign of the discussion forums yet assuming they decide to keep it
MrMeowington
Scratcher
100+ posts

Scratch 3.0 Technical Discussion

thisandagain wrote:

-snip-
List monitors are scheduled for implementation in March / April.

Ummm… April is almost over, and we still don't have list monitors…
(I checked here, and you should too so you can see them as soon as they add them.)
MrMeowington
Scratcher
100+ posts

Scratch 3.0 Technical Discussion

Sheep_maker wrote:

MrMeowington wrote:

I don't know; this part

seems pretty 2.0ish and should probably be changed.
Why should it be changed? There's nothing wrong with it. Just because the website underwent a rewrite between 1.4 and 2.0 doesn't mean it has to happen for every major update of the Scratch editor.
True, I just think that Helvectia Bold wouldn't look the best in that context for 3.0.

Sheep_maker wrote:

MrMeowington wrote:

Also, the entirety of the discussion forums just SCREAMS 2013.
They haven't started the redesign of the discussion forums yet assuming they decide to keep it
Did you mean "assuming they decide to change it?"
NickyNouse
Scratcher
1000+ posts

Scratch 3.0 Technical Discussion

MrMeowington wrote:

thisandagain wrote:

-snip-
List monitors are scheduled for implementation in March / April.
Ummm… April is almost over, and we still don't have list monitors…
(I checked here, and you should too so you can see them as soon as they add them.)
It looks like they rescheduled it for May, but yeah I'm not seeing any development on it yet

MrMeowington wrote:

Sheep_maker wrote:

MrMeowington wrote:

Also, the entirety of the discussion forums just SCREAMS 2013.
They haven't started the redesign of the discussion forums yet assuming they decide to keep it
Did you mean "assuming they decide to change it?"
They did recently remove Discuss from the toolbar, it's not too crazy to imagine that they might be phasing the forums out (don't freak out though, I don't think the ST has said anything like that). Honestly to me it looks like they're just downplaying the forums but are totally gonna leave them up. They're still using them for announcements and stuff, after all.
Roseyfurby_Aj
Scratcher
100+ posts

Scratch 3.0 Technical Discussion



chexbox
Scratcher
100+ posts

Scratch 3.0 Technical Discussion

Roseyfurby_Aj wrote:



No more ‘tips’ page?
That'd be great!
follingeneric17
Scratcher
41 posts

Scratch 3.0 Technical Discussion

Seems like that with the bitmap editor, they add the next feature every so often. You can only use the line and paintbrush tools right now.
ACE009
Scratcher
100+ posts

Scratch 3.0 Technical Discussion

follingeneric17 wrote:

Seems like that with the bitmap editor, they add the next feature every so often. You can only use the line and paintbrush tools right now.
Although neither control or shift make the lines adhere to 45 or 90 degree increments. (45 is better)
PumpkinBear111
Scratcher
68 posts

Scratch 3.0 Technical Discussion

What is Scratch 3.0 going to be made in? Is it still going to need flash even though flash will be dead by 2020?
PumpkinBear111
Scratcher
68 posts

Scratch 3.0 Technical Discussion

Is there going to be a Scratch 2.0 to Scratch 3.0 converter?

Powered by DjangoBB