thisandagain wrote:

frodewin wrote:

ok, thanks, I will write it as follows:

Scratch 3.0 will rely on a new implementation of an html5 player instead of being based on the community created html5 players like the abandoned HTML5 player, Phosphorus or Sulfurous.

Thanks for helping maintain the Wiki!

I'm not 100% sure if I agree with the way this is being represented. The earlier HTML5 player was also created by the Scratch Team. Also, there is a big difference between what we have built (a full Scratch interpreter and editor) vs. other explorations like Phosphorus and Sulfurous which convert an SB2 into JavaScript and so I'm worried that both this and the English language wiki are comparing apples to oranges (interpreters to converters) which is misleading.

IgDegOo wrote:

What happened to all the posts?

frodewin wrote:

thisandagain wrote:

frodewin wrote:

ok, thanks, I will write it as follows:

Scratch 3.0 will rely on a new implementation of an html5 player instead of being based on the community created html5 players like the abandoned HTML5 player, Phosphorus or Sulfurous.

Thanks for helping maintain the Wiki!

I'm not 100% sure if I agree with the way this is being represented. The earlier HTML5 player was also created by the Scratch Team. Also, there is a big difference between what we have built (a full Scratch interpreter and editor) vs. other explorations like Phosphorus and Sulfurous which convert an SB2 into JavaScript and so I'm worried that both this and the English language wiki are comparing apples to oranges (interpreters to converters) which is misleading.

Thanks for this info, I have changed now the text as follows, is this fine?

Scratch 3.0 will be a new implementation of a full Scratch interpreter and editor, which will be different from previous implementations of Scratch project players for html5, most notably the HTML5 Player, the Phosphorus Player and the Sulfurous Player.

Everything is handled with props passing. This is a good place for redux, but I needed it to be done for the play test tomorrow.

_nix wrote:

Here's an interesting issue: (#152)



Particularly:

Everything is handled with props passing. This is a good place for redux, but I needed it to be done for the play test tomorrow.

I'm curious about who that play test is targeted towards – it could really be anyone, such as Scratch users, but also anybody they'd like to present the future of the Scratch editor to – but in any case play tests are always nice!

..PS, in case anybody doesn't know, you can try scratch-gui on its official GitHub page (add “#PROJECT_ID” to view a 2.0 project in it).

thisandagain wrote:

_nix wrote:

Here's an interesting issue: (#152)



Particularly:

Everything is handled with props passing. This is a good place for redux, but I needed it to be done for the play test tomorrow.

I'm curious about who that play test is targeted towards – it could really be anyone, such as Scratch users, but also anybody they'd like to present the future of the Scratch editor to – but in any case play tests are always nice!

..PS, in case anybody doesn't know, you can try scratch-gui on its official GitHub page (add “#PROJECT_ID” to view a 2.0 project in it).

We are doing an “internal” test with almost every member of the Scratch Team tomorrow which is what that is referring to. We do internal tests like this before we do testing with kids / teens. Our third such test for 3.0 is in about two weeks!

DeleteThisAcount wrote:

thisandagain wrote:

_nix wrote:

Here's an interesting issue: (#152)



Particularly:

Everything is handled with props passing. This is a good place for redux, but I needed it to be done for the play test tomorrow.

I'm curious about who that play test is targeted towards – it could really be anyone, such as Scratch users, but also anybody they'd like to present the future of the Scratch editor to – but in any case play tests are always nice!

..PS, in case anybody doesn't know, you can try scratch-gui on its official GitHub page (add “#PROJECT_ID” to view a 2.0 project in it).

We are doing an “internal” test with almost every member of the Scratch Team tomorrow which is what that is referring to. We do internal tests like this before we do testing with kids / teens. Our third such test for 3.0 is in about two weeks!

Can't wait for the Scratcher test

stickfiregames wrote:

Switching to a non-existent costume name now switches to the last costume, previously it didn't switch at all. This breaks some case sensing and possibly other projects.

thisandagain wrote:

stickfiregames wrote:

Switching to a non-existent costume name now switches to the last costume, previously it didn't switch at all. This breaks some case sensing and possibly other projects.

That is a really good catch. Thanks!

<[hello world] exactly equals [HELLO WORLD]? :: operators>
([hello world] to uppercase :: operators)
([HELLO WORLD] to lowercase :: operators)

(letters (1) to (5) of [hello world] :: operators)

djdolphin wrote:

thisandagain wrote:

stickfiregames wrote:

Switching to a non-existent costume name now switches to the last costume, previously it didn't switch at all. This breaks some case sensing and possibly other projects.

That is a really good catch. Thanks!

Is there any chance of getting a proper method of case detection? String manipulation in Scratch is currently a bit ridiculous, especially if you aren't familiar with the program.

Something like

<[hello world] exactly equals [HELLO WORLD]? :: operators>
([hello world] to uppercase :: operators)
([HELLO WORLD] to lowercase :: operators)

would be nice, and much more understandable than using a quirk in costume switching.

I think a block like

(letters (1) to (5) of [hello world] :: operators)

is also long overdue. The workaround of reading each letter individually isn't that difficult to figure out, but it's pretty annoying.

(letters (1) to (5) of [hello world] :: operators)

• Buttons - Buttons, including the zoom feature, just appear “stale” and don't reflect the fact that they're pushed. (If you don't have any scripts inside, and click the button, it appears like nothing has happened.)
  
• Cut-off Sprite Library Design - When selecting a sprite costume, and scrolling all the way down, you see a sprite in the center, but the bottom half of it is cut off/not visible. This also applies with a background.
  
• Continuously Unaligned - When interacting with the script editor, according to the scrollbars at the bottom and right, you have space up left. When you drag the script(s) to the suggested top-left, it continues this effect.
  

• Is the player now 272x217? Honestly, not quite satisfying in terms of equilibrium.
  
• Why are there red/blue squares on the left of reporter blocks?
  

Austinato wrote:

Questions

• Is the player now 272x217? Honestly, not quite satisfying in terms of equilibrium.
  
• Why are there red/blue squares on the left of reporter blocks?
  

NickyNouse wrote:

Austinato wrote:

Questions

• Is the player now 272x217? Honestly, not quite satisfying in terms of equilibrium.
  
• Why are there red/blue squares on the left of reporter blocks?
  

1- It's showing as 480x360 for me at different window sizes

MegaApuTurkUltra wrote:

NickyNouse wrote:

Austinato wrote:

Questions

• Is the player now 272x217? Honestly, not quite satisfying in terms of equilibrium.
  
• Why are there red/blue squares on the left of reporter blocks?
  

1- It's showing as 480x360 for me at different window sizes

Can we have a 4k stage in Scratch 3 please?

infinitytec wrote:

MegaApuTurkUltra wrote:

NickyNouse wrote:

Austinato wrote:

Questions

• Is the player now 272x217? Honestly, not quite satisfying in terms of equilibrium.
  
• Why are there red/blue squares on the left of reporter blocks?
  

1- It's showing as 480x360 for me at different window sizes

Can we have a 4k stage in Scratch 3 please?

And widescreen!