Za-Chary wrote:

2.5 Official Scratch to EXE converter
On Scratch, an important goal is to have anyone be able to look at the code for any project. This philosophy is not only important for learning code and remixing, but is also important for moderation purposes; for more information, see #3.2 and #4.1 on this list. Converting to EXE (or any other black box executables) will prevent users from looking at the code, and hence goes against this philosophy. Third-party converters do exist, and you are allowed to use those, but the Scratch Team will not make an official converter.

there will be a page that lets you decompress the EXE into an sb3 (the exe will really just contain the sb3 file), allowing you to view the code for it, thus solving the reason for rejection.

I think this is still rejected- according to the post that rejects it that TOLORS links:

Paddle2See wrote:

Porting a Scratch project to an EXE doesn't really align with our goals for Scratch. Scratch is designed to be an educational language, with the “source code” always accessible for viewing and tinkering (remixing). Locking the code up in an EXE format runs counter to those goals.

BigNate469 wrote:

I think this is still rejected- according to the post that rejects it that TOLORS links:

Paddle2See wrote:

Porting a Scratch project to an EXE doesn't really align with our goals for Scratch. Scratch is designed to be an educational language, with the “source code” always accessible for viewing and tinkering (remixing). Locking the code up in an EXE format runs counter to those goals.

it is always accessible

8to16 wrote:

BigNate469 wrote:

I think this is still rejected- according to the post that rejects it that TOLORS links:

Paddle2See wrote:

Porting a Scratch project to an EXE doesn't really align with our goals for Scratch. Scratch is designed to be an educational language, with the “source code” always accessible for viewing and tinkering (remixing). Locking the code up in an EXE format runs counter to those goals.

it is always accessible

No- it isn't: while it's an EXE it is not accessible, unless you like to read binary.

BigNate469 wrote:

No- it isn't: while it's an EXE it is not accessible, unless you like to read binary.

Turbowarp has an unpackager

8to16 wrote:

BigNate469 wrote:

No- it isn't: while it's an EXE it is not accessible, unless you like to read binary.

Turbowarp has an unpackager

For HTML files
Edit: Nevermind, apparently not

8to16 wrote:

BigNate469 wrote:

No- it isn't: while it's an EXE it is not accessible, unless you like to read binary.

Turbowarp has an unpackager

You're evading my point.

Turbowarp is separate from Scratch and can do whatever they want. The Scratch Team only cares if it's appropriate enough to be mentioned here.

The fact that Turbowarp has an unpackager means nothing. Turbowarp also has a .sb3 to EXE converter, and .sb3 to APK converter. Guess what? Both are rejected. Again, just because Turbowarp has it doesn't mean anything other than it's possible.

And yes, it's possible. It's also possible to put [removed by me- definitely not safe for Scratch] all over the website. Does that mean the ST should? No.

bump

Also, I have to ask, how would one unpackage an Electron app (considering that that's probably the easiest way to implement this)?

And, furthermore, why not just use the offline editor? It's not like the offline editor would be slower than a packaged Scratch project- they would run about the same speed.

The only cases I can think of why you would actually need a .sb3 to EXE converter are where you wouldn't be sharing it on Scratch anyways.