Building offline TurboWarp for win, linux and macOS with addons

[sfederici]

I followed the instructions at https://github.com/TurboWarp/desktop and everything went really smoothly with my Mac.

Now I have two questions:

• in order to build offline versions for Windows and Linux too, should I do the same on a Windows and a Linux machine? Or there is the possibility to cross-compile TurboWarp for other platforms?
• I found an "addons" folder inside the scratch-gui folder. If I want to develop/modify an addon, so that it is available in my customized version of TurboWarp, is it enough to put my addon in the addons folder? I couldn't find the addons.json file described at https://scratchaddons.com/docs/develop/getting-started/creating-an-addon/

[GarboMuffin]

in order to build offline versions for Windows and Linux too, should I do the same on a Windows and a Linux machine?

Yes, you will need a physical or virtual machine with those operating systems. TurboWarp Desktop uses a custom GitHub Actions script (https://github.com/TurboWarp/desktop/blob/master/.github/workflows/release.yml) to run builds on all platforms whenever a tag is pushed, you could do something similar.

I found an "addons" folder inside the scratch-gui folder. If I want to develop/modify an addon, so that it is available in my customized version of TurboWarp, is it enough to put my addon in the addons folder?

Modifying them is fine. Adding new addons is significantly less trivial and currently undocumented.

[sfederici]

Thanks a lot for your answer. I noticed that the code of the desktop app is mainly a downloader and compiler of code that is somewhere else. I have found in the code many instructions referring to several URLs but I wasn't able to locate the URL where the forked code should reside. Where should I change the downloader code in order to build a customized forked version? Thanks in advance.

[CST1229]

If your fork of scratch-gui imports your forks of scratch-vm, etc. in its package.json I think it will work.

[sfederici]

I tried the following:

• changed motion-primary color in my fork of scratch-gui https://github.com/scratchdesignstudio/scratch-gui/blob/develop/src/css/colors.css back (as suggested at https://scratch.mit.edu/discuss/topic/289503/?page=11#post-4551389) to Scratch's primary "blue" color
• changed "scratch-gui" to "github:scratchdesignstudio/scratch-gui#desktop" in package.json, as you suggested
• removed package-lock.json
• used "npm i" instead of "npm ci" so to rebuild package-lock.json
  package-lock.json.zip
• used "npm start"
  The GUI is still red instead of blue

Any other suggestion? Thanks in advance

[GarboMuffin]

TurboWarp Desktop uses a special branch of scratch-gui with changes related to desktop support. You should merge your scratch-gui/develop branch into your scratch-gui/desktop branch and push to your fork, and if you do those steps again it should work.

[sfederici]

You should merge your scratch-gui/develop branch into your scratch-gui/desktop branch and push to your fork

Unfortunately I'm not an expert of repositories (and their fork/merge/push operations). So what I did was the following (and it worked!):
- updated https://github.com/scratchdesignstudio/scratch-gui/blob/DESKTOP/src/css/colors.css instead of https://github.com/scratchdesignstudio/scratch-gui/blob/DEVELOP/src/css/colors.css
- left "github:scratchdesignstudio/scratch-gui#desktop" assigned to "scratch-gui" in my package.json (as it is already referring to the #desktop branch, right?)
- removed again package-lock.json
- run "npm i"
- run "npm start"
- RESULT: the main color of the GUI is now Scratch "blue"!!

Before going on tweaking the TurboWarp desktop code for my needs, I need to know if this is going to be enough even when I will be modifying my own forks of the other repositories, like
- scratch-blocks
- scratch-vm
- etc
Or do I have to change something else in the main package.json (or in other package(s).json)?

Thanks in advance for your invaluable help!

[GarboMuffin]

If you want to modify scratch-vm, scratch-blocks, etc., modify the package.json in scratch-gui to point to your forks and the desktop app will notice those changes on its own when you update it

[sfederici]

Thanks a lot. So, as the only reference to my scratchdesignstudio repository (the one where I forked Turbowarp/scratch-gui, Turbowarp/scratch-vm, Turbowarp/scratch-blocks, etc) is the line

"scratch-gui": "github:scratchdesignstudio/scratch-gui#desktop"

in package.json, I don't have to apply any further change to package.json. Is that right? (sorry for asking, but, as I said, I'm working on something completely new for me)

[GarboMuffin]

correct

[scratchforsccom]

I'm trying now to work on scratch-blocks in my new account scratchforsccom.

First thing I noticed, reading the package-lock.json in TurboWarp/desktop, I see that the referred branch is "develop-builds". So I made a very slight modification (changed "forever" to "for1ever") in my https://github.com/scratchforsccom/scratch-blocks/blob/develop-builds/msg/messages.js file that, if I correctly understood, should change the name of the forever block.

Then I have run the usual steps:

• changed "scratch-gui" value to "github:scratchforsccom/scratch-gui#desktop" in package.json in my new account
• git clone https://github.com/scratchforsccom/desktop
• cd desktop
• removed package-lock.json
• npm i
• npm run fetch
• npm start

At the end, my forever blocks is still called "forever", not "for1ever".

I noticed, in the newly created package-block.json, that the account for scratch-blocks (and the other repositories) is still TurboWarp and not scratchforsccom:

"scratch-blocks": "github:TurboWarp/scratch-blocks#develop-builds",
"scratch-paint": "github:TurboWarp/scratch-paint#develop",
etc

So, I suppose I must change or update something in order to create a package-lock.json that refers to my scratchforsccom account.

Any help, as always, is welcome

[GarboMuffin]

Try editing https://github.com/scratchforsccom/scratch-blocks/blob/develop-builds/msg/scratch_msgs.js#L4891 instead. messages.js is used for... something else? I'm not really sure either, but you want to modify scratch_msgs.js instead.

Changing these translations is relatively simple, but modifying other parts of scratch-blocks is very non-trivial and requires installing python 2 and running npm run prepublish. It's quite a disaster.

[scratchforsccom]

I guess I didn't do everything the right way. I changed "forever" to "for1ever" at line 4891 of file https://github.com/scratchforsccom/scratch-blocks/blob/develop-builds/msg/scratch_msgs.js, then did the usual steps:

• git clone https://github.com/scratchforsccom/desktop
• cd desktop
• removed package-lock.json
• npm i
• npm run fetch
• npm start

But when the language of the GUI is English, the forever block is still called "forever", not "for1ever". What did I miss?

[scratchforsccom]

Maybe, even in the following lines of package.json, TurboWarp must be replaced by my scratchforsccom account?

"repository": {
"type": "git",
"url": "https://github.com/TurboWarp/desktop.git"
},
...
"publish": [
{
"provider": "github",
"repo": "desktop",
"owner": "TurboWarp"
}

[GarboMuffin]

https://github.com/scratchforsccom/scratch-gui/blob/39ddaa9cb90ed06f15a56d12e0d783d75b5c7634/package.json#L79 still points to TurboWarp, you need to update it to point to your fork, eg github:scratchforsccom/scratch-blocks#develop-builds and then you probably also need to delete scratch-gui's package-lock.json and npm install to regenerate it.

[scratchforsccom]

https://github.com/scratchforsccom/scratch-gui/blob/39ddaa9cb90ed06f15a56d12e0d783d75b5c7634/package.json#L79 still points to TurboWarp, you need to update it to point to your fork

It worked!!! Thank you very very much!

Now I'll try to create a new block, as described at https://scratch.mit.edu/discuss/topic/289503/

[scratchforsccom]

I'm stuck. I tried again the following steps:

• forking, to my scratchforsccom account, the desktop, scratch-gui, scratch-blocks and scratch-vm repositories from TurboWarp
• updating all references to the TurboWarp account (only for the desktop, scratch-gui, scratch-blocks and scratch-vm repositories) in the package.json files of the desktop, scratch-gui, scratch-blocks and scratch-vm repositories (BTW: I couldn't find any reference in the scratch-blocks and scratch-vm repositories)
• removed the package-lock.json files from the desktop, scratch-gui, scratch-blocks and scratch-vm repositories
• finally the usual steps:

1. git clone https://github.com/scratchforsccom/desktop
2. cd desktop
3. npm install
4. npm run fetch
5. npm start ==> red block in the motion category of the TurboWarp app that opens automatically (instead of the "move 100 steps" block that was expected to show up, as described at https://scratch.mit.edu/discuss/topic/289503/, where I skipped the clone and link steps described there)
6. npm run dist ==> red block in the motion category of the TurboWarp app that I found in the /dist/mac-universal folder (same when I have run the installer in /dist)

To be sure they were correct, I tried all the steps described at https://scratch.mit.edu/discuss/topic/289503/ on the Scratch source code to create the block "move 100 steps". I got the correct blue block with the correct text until I have run the "npm link scratch-vm" step. After that step the block gets red and without any text, even if, when clicked, it correctly moves the sprite of 100 steps. So, the block works, but it is wrong for shape, color and text (no text at all). Same happens in TurboWarp.

Do you have a sequence of steps to create a simple block in a fork of your TurboWarp Desktop app? Thanks in advance

[scratchforsccom]

I tried all the steps described at https://scratch.mit.edu/discuss/topic/289503/ on the Scratch source code to create the block "move 100 steps". I got the correct blue block with the correct text until I have run the "npm link scratch-vm" step. After that step the block gets red and without any text, even if, when clicked, it correctly moves the sprite of 100 steps. So, the block works, but it is wrong for shape, color and text (no text at all)

I tried a terrible hack in the Scratch source code, and it worked (at least locally; further tests coming):

• I didn't run "npm link scratch-vm" in the scratch-gui local folder
• I moved the scratch3_motions.js file (where I added the behavior of the new block) from the scratch-vm/src/blocks folder to the scratch-gui/node_modules/scratch-vm/src/blocks local folder

Now the new "move 100 steps" block in the motion category is still blue, and by clicking it the sprite moves.

same happens in TurboWarp.

Is there something similar I can try with the TurboWarp Desktop code? As there are no explicit "link" steps in the compilation steps, I don't know what I could try.

[GarboMuffin]

Your scratch-gui fork uses your scratch-vm fork, this is good: https://github.com/scratchforsccom/scratch-gui/blob/develop/package.json#L86

However, when I look at your scratch-vm fork, I don't actually see any changes: https://github.com/scratchforsccom/scratch-vm. Perhaps you forgot to push? So when you npm install inside scratch-gui (which the desktop app sortof does indirectly), your scratch-vm changes don't get applied

I will advise that you may want to reconsider modifying scratch-blocks and instead implement your blocks as an extension in scratch-vm, which the editor will automatically support. Custom extensions implemented directly inside scratch-vm are completely unsandboxed and have as much power as the builtin blocks (because they effectively are builtin blocks). Places to start:

• https://github.com/TurboWarp/scratch-vm/blob/04e5c2bd4ace1a309e2393551cd90292535837a7/src/extension-support/extension-manager.js#L27-L28
• https://github.com/TurboWarp/scratch-gui/blob/fd675d80e7664146ec7fa4f918454d21a777506e/src/lib/libraries/extensions/index.jsx#L325-L345
• https://github.com/TurboWarp/scratch-vm/blob/04e5c2bd4ace1a309e2393551cd90292535837a7/src/extensions/tw/index.js

[scratchforsccom]

Your scratch-gui fork uses your scratch-vm fork, this is good: https://github.com/scratchforsccom/scratch-gui/blob/develop/package.json#L86. However, when I look at your scratch-vm fork, I don't actually see any changes: https://github.com/scratchforsccom/scratch-vm.

Thanks for your answer. Yes, you are right. I did all the steps in the Scratch 3 source code, but I didn't update the https://github.com/scratchforsccom/scratch-vm/blob/develop/src/blocks/scratch3_motion.js file in my fork of TurboWarp Desktop as the new red block was already showing up after updating the package.json files and the files in scratch-gui and scratch-blocks repositories and recompiling.

Just to understand if there is a right way of doing the updating, If you run the following steps

• git clone https://github.com/scratchforsccom/desktop
• cd desktop
• npm install
• npm run fetch
• npm start

do you see a red block in the motion category? If you think that updating the scratch3_motion.js file in scratch-vm could solve the problem I can certainly try that (I compiled and recompiled the source code at least 30-40 times in this weekend; a further test won't hurt).

I will advise that you may want to reconsider modifying scratch-blocks and instead implement your blocks as an extension in scratch-vm, which the editor will automatically support. Custom extensions implemented directly inside scratch-vm are completely unsandboxed and have as much power as the builtin blocks (because they effectively are builtin blocks)

I had considered that, but I want that the new block I need (I'm testing it now in the Scratch 3 source code) be for my students a "regular" Scratch block, as it was in Scratch 1.4. What I want to add back is indeed the "forever if" block from Scratch 1.4 (plus I want to get rid of some blocks that are not useful to them, such as the "clone" blocks; but this shouldn't be difficult).

I noticed now that the TurboWarp blocks I thought you had already added (such as "is compiled?") are "backpack" blocks. You didn't add new blocks to Scratch categories yet, did you?

Thanks again for your help

[scratchforsccom]

However, when I look at your scratch-vm fork, I don't actually see any changes: https://github.com/scratchforsccom/scratch-vm. Perhaps you forgot to push? So when you npm install inside scratch-gui (which the desktop app sortof does indirectly), your scratch-vm changes don't get applied

I redid the whole process for both the "move 100 steps" block (in the motion category, as explained in the Scratch modding tutorial) and my new "forever if" block in the control category. They both work in Scratch 3, if I don't "npm link scratch-vm" and I manually move the scratch3_motion.js and scratch3_control.js files to scratch-gui/node_modules/scratch-vm/src/blocks. The relevant changes for TurboWarp Desktop are in the following files of my https://github.com/scratchforsccom account (note: all changes are identified by "SF:"):

• scratch-gui/src/lib/make-toolbox-xml.js (DESKTOP branch)
• scratch-blocks/blocks_vertical/motion.js (DEVELOP-BUILDS branch)
• scratch-blocks/blocks_vertical/control.js (DEVELOP-BUILDS branch)
• scratch-blocks/msg/messages.js (DEVELOP-BUILDS branch)
• scratch-blocks/msg/scratch_msgs.js (DEVELOP-BUILDS branch)
• scratch-vm/src/blocks/scratch3_motion.js (DEVELOP branch)
• scratch-vm/src/blocks/scratch3_control.js (DEVELOP branch)

Then I did the usual steps:

• git clone https://github.com/scratchforsccom/desktop
• cd desktop
• npm install
• npm run fetch
• npm start

The two blocks are both red, without text. The "move 100 steps" block works (when I click it I see the sprite move by 100 steps). As for the "forever if" block (that works in Scratch 3) I do not know if it works, as there is no visible c-shaped arg where I can put code inside.

Any idea on how to make the "forever if" block of the control category work? Thanks in advance

[scratchforsccom]

I noticed now that the TurboWarp blocks I thought you had added (such as "is compiler") are "backpack" blocks. Just to avoid to bother you, you didn't add new blocks to the standard Scratch categories, did you?

Thanks again for your help

[scratchforsccom]

BTW, the code for the "forever if" block works very well in Scratch 3 (with the usual strategy of not to "npm link scratch-vm" but manually coping the Scratch3_....js scripts to the scratch-gui/node_modules/scratch-vm/src/blocks folder instead)

[scratchforsccom]

To sum up:

• on Scratch 3, the new blocks look fine and work fine (they are available at https://sfederici.github.io/scratch-gui/)
• on TurboWarp Desktop, the two new blocks are red (without text) and, at least the “move 100 steps” block, works fine

To get the correct result on Scratch 3, I have not to run “npm link scratch-vm” and I have to manually move the scratch3_motion.js and the scratch3_control.js files to the node_modules/scratch-vm /src/blocks folder of scratch-gui.

Is there a way to get the same result in TurboWarp Desktop?

[GarboMuffin]

If you've done everything properly then you shouldn't need to be manually copying files over. An npm install should just download your scratch-vm fork and everything just works.

You could try manually copying that file to turbowarp-desktop/node_modules/scratch-gui/node_modules/scratch-vm/... and see if it works

[scratchforsccom]

If you've done everything properly then you shouldn't need to be manually copying files over.

I guess I did everything properly. I have redone those steps again and again both in Scratch 3 and in TurboWarp. In Scratch 3 they work when I do something manually. In TurboWarp the same steps (except that for Scratch 3 I make all the changes locally, while in TurboWarp I make them on the GitHub website) don't work.

An npm install should just download your scratch-vm fork and everything just works.

This is what I hoped. But the steps that I listed above (on the revised source code available on my scratchforsccom account) give me a red hat block.

You could try manually copying that file to turbowarp-desktop/node_modules/scratch-gui/node_modules/scratch-vm/... and see if it works

I couldn't find a node_modules/scratch-gui/node_modules/scratch-vm/src/blocks in node_modules after installing and building the code. So:

• I created the path and copied the scratch3...js files there
• I copied the scratch3...js files to the node_modules/scratch-vm/src/blocks path that I found inside node_modules

The result in both cases is the same: the new blocks are just red hats with no text.
Now I'm trying to look inside node_modules for all the files I have changed. Just to see if they are really there as expected.

[scratchforsccom]

I compared the files that I have changed in GitHub (in the same repositories and branches listed in the package.json files) and the local files I found in desktop/node_modules after I run npm install (without any manual intervertion). There are no mismatches. Indeed what I find is (note: the links are to the files in my scratchforsccom account):

• the make-toolbox-xml.js file in desktop/node_modules/scratch-gui/src/lib/make-toolbox-xml.js (NOTE: the TurboWarp file is slightly different from the one in the Scratch source code; I verified that I changed it by keeping the TurboWarp file as a base)
• the motion.js and control.js files in desktop/node_modules/scratch-blocks/blocks_vertical/
• the messages.js and scratch_msgs.js files in /desktop/node_modules/scratch-blocks/msg/
• the scratch3_motion.js and scratch3_control.js files in desktop/node_modules/scratch-vm/src/blocks/

So, if there are no alternative folders to which the files should be copied (as I said, I couldn't find the node_modules/scratch-gui/node_modules/scratch-vm/src/blocks path you mentioned), every file after running npm install is where it supposed to be. But the new blocks, even if they work (this is sure for "move 100 steps"; likely for "forever if"), are still red hat blocks with no text either when I run npm start after npm install and npm run fetch, or when I run the TurboWarp.app file in desktop/dist/mac-universal/ after running npm run dist too.

Anything else I can try? Thanks in advance

[stefanofederici]

Alternative attempt (failed): in my new stefanofederici account I changed all the relevant code (that is messages.js, scratch_msgs.js, control.js, scratch3_control.js) of the WHILE block (that I don't need) and I followed again the usual steps (clone, install, fetch, start, run dist). I found all the new code in the local node_modules folder, but the only thing that worked is scratch_msgs.js: the block has the "forever if" name, but it still has the shape_statement shape (instead of the shape_end shape that I changed in scratch-blocks/blocks_vertical/control.js) and, when clicked, it doesn't loop forever (the block stops the very first time the condition is meet).

Next attempt (last thing I can think of): as it seems that to add working blocks to Scratch 3 the crucial step is "npm run prepublish" (a step that could be missing in the Desktop version of the code) I will try to run "npm run prepublish" in a local clone of the scratch-blocks repository and then merge it (I hope a simple copy will work) in node_modules of TurboWarp desktop. I will let you know how this worked

[stefanofederici]

I guess for now you could just use the node_modules copy trick until you can get proper building working.

You mean using Scratch 3 where I copied the scratch3...js files in node_modules/scratch-vm? I could. But TurboWarp is so much better.

Also, you could just teach students to use FOREVER {IF} instead of IF {FOREVER} as a replacement for FOREVER IF.

That is exactly why I spent almost two weeks just attempting to create a working version of TurboWarp Desktop with the "forever if" block. My non-tech-savvy students, as soon as they see something that requires an "effort" (in this case remembering the correct order of the forever and if blocks), and it is not "linguistically" justified, will drop the subject and they will try to pass my exam at the end of their degree (something that, unfortunately, in Italy you can do). So, to finish in time their degree, they will just try to get the minimum score. This is very frustrating to me as, since I moved to Scratch, I had a large part of these students create incredibly cool projects right after my 3-month course.

[CST1229]

You mean using Scratch 3 where I copied the scratch3...js files in node_modules/scratch-vm? I could. But TurboWarp is so much better.

Doesn't doing that work with TWDesktop too?

Also, you could always just distribute the compiled html+js files for the web version, either hosted on a website somewhere or offline.

[stefanofederici]

Doesn't doing that work with TWDesktop too?

No, unfortunately it doesn't. That is why I'm still struggling to make it work.

Also, you could always just distribute the compiled html+js files for the web version

What do you mean? I thought the "compiled" version of TurboWarp was TurboWarp Desktop. Or it isn't?

either hosted on a website somewhere or offline

That is a possibility. But it would be good if the students could use the tool when they are studying offline, and, morever, they need an offline version of the tool for their exams (the have to use local versions of tools, as they are not going to have Internet access).

[CST1229]

What do you mean? I thought the "compiled" version of TurboWarp was TurboWarp Desktop. Or it isn't?

The compiled version of the web version is the files you get after running npm run build on scratch-gui.

[stefanofederici]

I made it. Partially.

I made the block "move 100 steps" work. I was concentrated on the "forever if" block that I got by changing the "while" block. So I don't know exactly when the "move 100 steps" started working. So I'm now going to redo all the steps and see when the correct look of the "move 100 steps" block shows up. I still need help to make the "forever if" block work.

In the meantime, the sequence of steps I applied is the following (basically, installing TurboWarp desktop as a first step and then reinstalling the scratch-blocks and scratch-vm repositories of TurboWarp inside it, as described in the https://scratch.mit.edu/discuss/topic/289503/ tutorial):

forked https://github.com/turbowarp/desktop to stefanofederici account
updated the following files:

• make-toolbox-xml.js
• motion.js and control.js
• messages.js and scratch_msgs.js
• scratch3_motion.js and scratch3_control.js

git clone https://github.com/stefanofederici/desktop
cd desktop
npm install
npm run fetch
cd node_modules
mv scratch-blocks scratch-blocks-ORIG
git clone -b develop-builds https://github.com/stefanofederici/scratch-blocks
cd scratch-blocks
npm install
npm link
cd ../scratch-gui
npm link scratch-blocks (it raises an ERESOLVE error: ignored)
cd ../scratch-blocks
npm run prepublish
cd ..
mv scratch-vm scratch-vm-ORIG
git clone https://github.com/stefanofederici/scratch-vm
cd scratch-vm
npm install
npm link
cd ../scratch-gui
COPIED desktop/node_modules/scratch-blocks/media TO desktop/node_modules/scratch-gui/node_modules/scratch-blocks
npm start

[stefanofederici]

I made it. Partially.

Almost. Some errors showed up in the "warning sign" menu

1. "some script could not be compiled"
2. "Sprite1: Error: IR: Unknown stacked block: motion_move100steps"

Furthermore, the "start recording" button is missing.

Then, when I clicked the addon menu after having clicked the "move 100 steps" and "move 10 steps" blocks and having duplicated the Sprite1 sprite, tw crashed.

[stefanofederici]

Ok, I had missed something in the scratch3_control.js file in the repository. By adding the "control_foreverif: this.foreverIf," line in the following code under //SF:NEW: to desktop/node_modules/scratch-vm/src/blocks/scratch3_control.js, the "forever if" block works as expected:

getPrimitives () {
       return {
           control_repeat: this.repeat,
           control_repeat_until: this.repeatUntil,
           control_while: this.repeatWhile,
           // SF: NEW:
           control_foreverif: this.foreverIf,

           control_for_each: this.forEach,
           ...
       };
   }

The only remaining problems are now:

• the errors "Sprite1: Error: IR: Unknown stacked block: motion_move100steps" and "Sprite1: Error: IR: Unknown stacked block: control_foreverif" showing up in the "warning" menu every time that I run the "move 100 steps" and "forever if" blocks
• the missing "start recording" button in the menu
• the previous crash of the GUI when I clicked the "Addon" menu (that I couldn't replicate yet)

[stefanofederici]

• the missing "start recording" button in the menu

I npm installed the original TurboWarp/scratch-gui repository, and it seems to me that the "start recording" button is missing in the original TurboWarp source code too. Is there a reason for this part not being available in the source code?

[stefanofederici]

I'm now trying to create a custom online version of TurboWarp with the "forever if" block. I have run

git clone --depth=1 https://github.com/stefanofederici/scratch-gui

but with npm install I get an error that I don't get when running npm install after

git clone --depth=1 https://github.com/turbowarp/scratch-gui

I diff'ed the two scratch-gui folders and, except for updates to scripts that (I guess) should not impact, the only real differences are between the package.json and make-toolbox-xml.js, as expected. Is there something intrinsically new in TurboWarp so that I should refork the repositories?

The result of my diff -rq is the following:

Files online-sf/scratch-gui/.git/config and online-tw/scratch-gui/.git/config differ
Files online-sf/scratch-gui/.git/index and online-tw/scratch-gui/.git/index differ
Files online-sf/scratch-gui/.git/logs/HEAD and online-tw/scratch-gui/.git/logs/HEAD differ
Files online-sf/scratch-gui/.git/logs/refs/heads/develop and online-tw/scratch-gui/.git/logs/refs/heads/develop differ
Files online-sf/scratch-gui/.git/logs/refs/remotes/origin/HEAD and online-tw/scratch-gui/.git/logs/refs/remotes/origin/HEAD differ
Only in online-tw/scratch-gui/.git/objects/pack: pack-bad78778e33cf8935b7b60e5bef1fb0644162c8e.idx
Only in online-tw/scratch-gui/.git/objects/pack: pack-bad78778e33cf8935b7b60e5bef1fb0644162c8e.pack
Only in online-sf/scratch-gui/.git/objects/pack: pack-bc98449101fed7a23c6d1bf4776c1c37fca49db3.idx
Only in online-sf/scratch-gui/.git/objects/pack: pack-bc98449101fed7a23c6d1bf4776c1c37fca49db3.pack
Files online-sf/scratch-gui/.git/packed-refs and online-tw/scratch-gui/.git/packed-refs differ
Files online-sf/scratch-gui/.git/refs/heads/develop and online-tw/scratch-gui/.git/refs/heads/develop differ
Files online-sf/scratch-gui/.git/shallow and online-tw/scratch-gui/.git/shallow differ
Only in online-tw/scratch-gui: package-lock.json
Files online-sf/scratch-gui/package.json and online-tw/scratch-gui/package.json differ
Files online-sf/scratch-gui/src/addons/addons/debugger/module.js and online-tw/scratch-gui/src/addons/addons/debugger/module.js differ
Files online-sf/scratch-gui/src/addons/addons/editor-theme3/_manifest_entry.js and online-tw/scratch-gui/src/addons/addons/editor-theme3/_manifest_entry.js differ
Files online-sf/scratch-gui/src/addons/addons/fullscreen/resizeWindow_noToolbar.css and online-tw/scratch-gui/src/addons/addons/fullscreen/resizeWindow_noToolbar.css differ
Files online-sf/scratch-gui/src/addons/addons/gamepad/gamepadlib.js and online-tw/scratch-gui/src/addons/addons/gamepad/gamepadlib.js differ
Files online-sf/scratch-gui/src/addons/addons/gamepad/userscript.js and online-tw/scratch-gui/src/addons/addons/gamepad/userscript.js differ
Files online-sf/scratch-gui/src/addons/addons-l10n/es.json and online-tw/scratch-gui/src/addons/addons-l10n/es.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n/fr.json and online-tw/scratch-gui/src/addons/addons-l10n/fr.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n/pl.json and online-tw/scratch-gui/src/addons/addons-l10n/pl.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n/ru.json and online-tw/scratch-gui/src/addons/addons-l10n/ru.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n/tr.json and online-tw/scratch-gui/src/addons/addons-l10n/tr.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/de.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/de.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/es.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/es.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/fr.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/fr.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/it.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/it.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/ja.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/ja.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/ko.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/ko.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/pl.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/pl.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/pt.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/pt.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/ru.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/ru.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/sl.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/sl.json differ
Files online-sf/scratch-gui/src/addons/addons-l10n-settings/tr.json and online-tw/scratch-gui/src/addons/addons-l10n-settings/tr.json differ
Files online-sf/scratch-gui/src/addons/api.js and online-tw/scratch-gui/src/addons/api.js differ
Files online-sf/scratch-gui/src/addons/generated/translators.json and online-tw/scratch-gui/src/addons/generated/translators.json differ
Files online-sf/scratch-gui/src/addons/generated/upstream-meta.json and online-tw/scratch-gui/src/addons/generated/upstream-meta.json differ
Files online-sf/scratch-gui/src/addons/pull.js and online-tw/scratch-gui/src/addons/pull.js differ
Files online-sf/scratch-gui/src/addons/settings/translations.json and online-tw/scratch-gui/src/addons/settings/translations.json differ
Files online-sf/scratch-gui/src/css/colors.css and online-tw/scratch-gui/src/css/colors.css differ
Files online-sf/scratch-gui/src/lib/file-uploader.js and online-tw/scratch-gui/src/lib/file-uploader.js differ
Files online-sf/scratch-gui/src/lib/make-toolbox-xml.js and online-tw/scratch-gui/src/lib/make-toolbox-xml.js differ

[GarboMuffin]

You don't need to "refork" the repositories, just pull the latest upstream changes. If you go to your fork on GitHub there should be a "Fetch upstream" button that lets you do that.

Errors like "Sprite1: Error: IR: Unknown stacked block: motion_move100steps" are related to the compiler. My suggestion is to disable the compiler entirely because making your new blocks compatible with it is non-trivial and having true live script editing may be valuable in a learning environment. After this: https://github.com/TurboWarp/scratch-gui/blob/542aed15f1d65a7d2c891a53e5068363710d4ac5/src/lib/vm-manager-hoc.jsx#L36 add vm.setCompilerOptions({ enabled: false })

If the "Start recording" button doesn't appear then you probably haven't enabled the "Project video recorder" addon yet. You should be able to enable it by default by changing this: https://github.com/TurboWarp/scratch-gui/blob/542aed15f1d65a7d2c891a53e5068363710d4ac5/src/addons/addons/mediarecorder/_manifest_entry.js#L18 to true

[scratchforsccom]

You don't need to "refork" the repositories, just pull the latest upstream changes. If you go to your fork on GitHub there should be a "Fetch upstream" button that lets you do that.

When I use the "Fetch upstream" button, it says

This branch is XX commits behind the upstream and has conflicts that must be resolved
Open a pull request to fetch upstream and review changes or resolve conflicts.

The same happens in all my scratchforsccom repositories (from where I forked the stefanofederici repositories that I use to create my custom TW Desktop)

I don't think you want to merge my customizations. Anyway, I can't make a pull request as the "Create pull request" button is grayed out.

My suggestion is to disable the compiler entirely because making your new blocks compatible with it is non-trivial and having true live script editing may be valuable in a learning environment.

I agree. I will try that.

If the "Start recording" button doesn't appear then you probably haven't enabled the "Project video recorder" addon yet

Thank you. Sorry for asking. I didn't remember it was an Addon (I guess I had enabled it in the TurboWarp website and then forgot about it)

Last question: I need the updated Debugger addon, where you can step through the code. Is this something that will be updated soon in the TW website? Thanks in advance

[CST1229]

When I use the "Fetch upstream" button, it says

This branch is XX commits behind the upstream and has conflicts that must be resolved
Open a pull request to fetch upstream and review changes or resolve conflicts.

I think if you merge upstream from GitHub Desktop (in your repo, Current branch -> Choose a branch to merge into XX -> upstream/develop -> Create a merge commit), it shows a dialog where you can see all conflicts and fix them in a text editor.

[stefanofederici]

When I use the "Fetch upstream" button, it says
This branch is XX commits behind the upstream and has conflicts that must be resolved
Open a pull request to fetch upstream and review changes or resolve conflicts.

I think if you merge upstream from GitHub Desktop (in your repo, Current branch -> Choose a branch to merge into XX -> upstream/develop -> Create a merge commit), it shows a dialog where you can see all conflicts and fix them in a text editor.

Thank you for your suggestion. I'm pretty new to using GitHub for more than downloading repositories, so my fear is that I will do something irremediably wrong. I created the scratchforsccom account to fork TurboWarp's repositories, then I created the stefanofederici account to fork the scratchforsccom repositories. I'm very confused even about the real difference between branches and forks.

I would like to be able to create updated versions of my repositories but still keeping the old versions, so to be able to go back to the old version just by discarding the new version if it doesn't work as expected.

I just know how to fork a repository, but I don't know how to create "branches", and if they can be good for my goals. I downloaded a few days ago and tried to use GitHub Desktop, but I don't even understand if the repositories that I clone and change can then easily reloaded to the GitHub website.

Do you happen to have by any chance a simple but complete tutorial on using the GihHub website (and GitHub Desktop) that I can go through? Thanks again.

[stefanofederici]

I need now to compile my custom TW for Windows.

I tried following the instructions on the usual tutorial https://scratch.mit.edu/discuss/topic/289503/ that said I needed to use Windows Subsystem for Linux. So I installed WSL. But even the tw's original source code raises an error when I npm install (compilation error npm install.txt).

So I tried to use the command prompt, and I was able to run and build tw's original source code. But when I try to add and compile the scratch-blocks repository and I npm install, it raises a "cmd line is too long" error. So I tried to move the scratch-blocks folder to c:\scratch-blocks, but even running npm install there raises the same "cmd line is too long" error.

I also tried (I guess it isn't logical, but I don't know much about npm) to run npm start inside the already build macOS custom TW, but it complains about the command "webpack-dev-server" being unknown.

Is there a way to create a windows executable in WSL (that, if I correctly understood, has a longer path limit)?

Thanks in advance

[CST1229]

You can apply the changes made in this PR to your fork of scratch-blocks and I think building on Windows will work.

[stefanofederici]

I guess that made the trick. I revised again all the steps, but in the end I got a working installer for Windows by running everything in command prompt. I hope tomorrow, when I'm going to clean and redo everything, it will work again. Thanks a lot.

[GarboMuffin]

I don't know how much I can help you at this point. You're quite far into the weeds now.

I need the updated Debugger addon, where you can step through the code. Is this something that will be updated soon in the TW website?

It won't be updated soon. Since it sounds like you don't care about the compiler you can try to manually revert TurboWarp/addons@069aadc by editing scratch-gui/src/addons/addons/debugger/userscript.js but I can't guarantee it'll work.

I created the scratchforsccom account to fork TurboWarp's repositories, then I created the stefanofederici account to fork the scratchforsccom repositories. I'm very confused even about the real difference between branches and forks.

Having multiple "layers" of forks will make things more annoying. You don't need to be doing that.

A fork is just a branch owned by someone else.

I downloaded a few days ago and tried to use GitHub Desktop, but I don't even understand if the repositories that I clone and change can then easily reloaded to the GitHub website.

Yes, that is the point

Regrading that npm build error, downgrade Node.js to v14.x and it'll probably work in WSL. Recent versions are apparently problematic.

Modding Scratch is very messy right now.

[stefanofederici]

Since it sounds like you don't care about the compiler you can try to manually revert TurboWarp/addons@069aadc by editing scratch-gui/src/addons/addons/debugger/userscript.js but I can't guarantee it'll work.

I will certainly try that tomorrow

Having multiple "layers" of forks will make things more annoying. You don't need to be doing that.

Ok

A fork is just a branch owned by someone else.

I see

Regarding that npm build error, downgrade Node.js to v14.x and it'll probably work in WSL. Recent versions are apparently problematic.
Modding Scratch is absolutely miserable right now.

I noticed!!!! Anyway, having get a -hopefully- stable process to add new blocks and rebuild turbowarp, I'm going to stick with that.

Thanks a lot

[turbowarpORIG]

you can try to manually revert TurboWarp/addons@069aadc by editing scratch-gui/src/addons/addons/debugger/userscript.js but I can't guarantee it'll work.

(This is just another account to test the debugger addon)

I tried. The userscript.js file in the scratch-gui#desktop repository is completely different from the file I see In the change (and that I fully see when I click "view file" at TurboWarp/addons@069aadc). So I just replaced it with the full file at https://github.com/TurboWarp/addons/blob/069aadc73ff3a7250d272f1abcc03c0b02bdb975/addons/debugger/userscript.js. Is that what you meant?

Now I see the blocks of the debugger extension (that I don't see instead in the TurboWarp website when I enable the debugger addon) but I don't see the button to open the debugger window.

[stefanofederici]

Which repository are you primarily using right now?

I'm using the stefanofederici account and the 4 repositories desktop, scratch-gui, scratch-blocks and scratch-vm. I disabled the compiler, as you suggested.

I'll try to do it myself if I have time.

That would be really great, as I'm not clear enough what to do. If you can, I need the fully working debugger extension, with the step by step execution button, at most by thursday morning, when I will be giving my lesson to the students.

Is there any chance that, having disabled the compiler, I could just replace all addons with their current ScratchAddons version?

Thanks in advance for your help

[GarboMuffin]

stefanofederici/scratch-gui#1

[GarboMuffin]

You'll also want stefanofederici#1

[stefanofederici]

I tried yesterday, and today again, but I cannot get rid of the "infamous" red block problem, again: everything is there, the foreverif block is there (if I click it, the yellow "running" border stays until I click the stop sign) but it is a textless red hat: no blue color, no correct shape, no text, no arguments.

I checked the first commit before clicking the green button, and I'm sure it said there were no conflicts. I didn't before I accepted the second commit. I suppose there were no conflicts there too?

I'm going to try again for the third time to git clone and npm install and npm link and np run build everything again. I will let you now soon how it worked (if it worked).

[stefanofederici]

I redid everything from "scratch" and everything works as it is supposed to work... Unfortunately what doesn't work is the debugger addon itself. At least it doesn't work for the "wait" blocks I needed it. It doesn't work on my "forever if" block, but it doesn't work on the "wait until" block either. If you try it on the attached scratch 3 project, when it gets to the "wait until" block it gets stuck, no matter how many times you click the step button. I'm sorry that you have spent time in something that I cannot use. But thanks a lot for your support.
staToccandoSprite.sb3.zip

NOTE: the same wrong behaviour happens also when using the debbuger addon in ScratchAddons for Scratch 3

[stefanofederici]

It's always me. Do you know of any problem when importing gif images with the code I have forked at the beginning of February to create my custom TurboWarp Desktop? I discovered that I can import jpeg and png image, but no gif images. Instead, I can import even gif images by using turbowarp desktop 1.1.3. Any help is appreciated.

[GarboMuffin]

TurboWarp/scratch-gui@2322538

[sfederici]

Excellent! It worked immediately, without reinstalling everything, I had just to rebuild

[GarboMuffin]

You may be interested to hear that the next release of TurboWarp Desktop and the current version of the TurboWarp website include full support for the threads tab in the debugger addon when the compiler is disabled.

[sfederici]

This is excellent news! Thanks for letting me know