Here I talked about the benefits of a more accessable source code so more suggestions can get implemented:

HTML-Fan wrote:

I think that maybe the community could do more, for example I can code JS, HTML and CSS and I would really like to use my knowledge for improving Scratch. I want that everyone can code, I think that everyone should code, and I think that we should improve scratch so beginners can code really easy and more advanced users don't have the problem that a bunch of important blocks are missing.
So I looked at scratch on GitHub and found that there were hundreds of files and it looked like 90% of the files only included other files. Well …
I think that scratch could really benefit from a great community, because if every more advanced programmer who uses scratch more as a challenge and a way to reach a huge community who has a problem could just open a suggestion topic, asks other people what they think and then go to scratch's GitHub page and implement what he wants, make a pull request and solve the problem this way, that would be completely awesome and it would make sure that scratch will always be one of the coolest block based programming languages around.
But how it is currently, I would most likely spend 10 hours just figuring out what 1% of the files does.
What I would really like to see is a document on GitHub where every document is explained with a few words, so I can just get a quick overview in 20 minutes and find the file I have to modify or add in 5 minutes.

I think that that would be a way to implement more suggestions.

Just realized that it's pretty much a suggestion on its own.

semi-support
It is a little confusing. However, maybe you can make a remix of scratch, and suggest features of it and maybe it will be implemented.

scratchmaster295 wrote:

semi-support
It is a little confusing.

What exactly do you mean? Is my grammar awful? It isn't really good, I know that.

HTML-Fan wrote:

scratchmaster295 wrote:

semi-support
It is a little confusing.

What exactly do you mean? Is my grammar awful? It isn't really good, I know that.

I think they do not understand how github works and/or what you are talking about. Anyways support. It would be great if scratchers were encouraged to develop scratch!

There is already an overview near the beginning of each or most of the source files. It shouldn't be very difficult to find which source file to edit because they have descriptive names and the source of each module is seperated into folders with appropriate names.

Jonathan50 wrote:

There is already an overview near the beginning of each or most of the source files. It shouldn't be very difficult to find which source file to edit because they have descriptive names and the source of each module is seperated into folders with appropriate names.

But I would like to have a document in the root where the separate folders are explained and then each file or file group with a few words explained. Here's the scratch gui on scratch - I couldn't tell where, for example, the sprite editor is.

No support. If you want to edit something, you need to understand. A short (maybe 3 page) document at the root cannot possibly cover every little detail, every dependency required to change up Scratch effectively. I presume this is really advanced scripting – it's not the kind of thing that can be picked up in a few hours.

ResExsention wrote:

If you want to edit something, you need to understand.

Well, that's new to me. I edited a library for the Arduino without knowing what it exactly does. If you want to change the circle algorithm, then you don't have to understand the init sequence for the display.
And I really want to understand the scratch code. I want to build a real synthesizer extension, I've done something similar with an ESP32. But when I want to add an extension, I don't have to understand how the top loved algorithm works. I want to know where extensions are and first just copy them and make one small change after another.
And who said that it should be only 3 pages long? A PDF with 30-50 pages would be nice, with chapters for every part of scratch, and then maybe an additional small PDF in larger directorys, explaining where which parts of this small part of scratch are.

ResExsention wrote:

I presume this is really advanced scripting – it's not the kind of thing that can be picked up in a few hours.

The Arduino display lib wasn't too, but I just looked at the circle algorithm, looked at another one and found that a line is missing somewhere. I didn't understand what I was actually doing, but I didn't care. You don't have to understand everything to make something with the code. And slowly, while editing other things, I understood what the lib does. And now I don't understand everything, but I know how the graphics part of the lib works. That's enough for me.

Bro, this isn't Arduino. I have two of them, and I've made some things with it.

My friend, this simply isn't a good idea. For example, have a look at LLK/scratch-blocks/core/block.js. Right from the top, it's already requiring some Blockly stuff from whatever goog is. Good luck. I expect the required libraries are HUGE.

Let's scroll down to line 192. If some isEnabled value in Blockly.Events is true, then do some stuff, which I have no idea what it is about, simply because I haven't read the Blockly libraries.

Hmm. The lines around 218 look interesting. Colours?

Look, seriously. The Scratch code (and most other software in general) is spread across multiple files. You'd have to read them all in order to understand what you're even doing. If you make a mistake, then oof: you have no idea what went wrong because you don't happen to know what that particular function call does. This isn't an Arduino library, which probably won't be split a hundred times.

Well, that's the kind of think I want to have explained in a document: What's goog? Where's the file with goog in it?

HTML-Fan wrote:

Well, that's the kind of think I want to have explained in a document: What's goog? Where's the file with goog in it?

Now we're getting somewhere. Problem is, you have to read goog to understand what you're doing. A directory is actually a good idea, but there can be no shortcut for properly reading the files.

Yes, I really want to get into it and I would really like to do it, but I don't know where to find stuff. That's my problem. I want to know where what is. That would make the source code more understandable.

HTML-Fan wrote:

Yes, I really want to get into it and I would really like to do it, but I don't know where to find stuff. That's my problem. I want to know where what is. That would make the source code more understandable.

mk. Support for a directory and a short summary. No support for a 50 page document that'll explain literally every aspect of a file. The latter is virtually useless.

Okay. It would be nice if it would be like a reference where to find which object like goog.

wut iz goog
It would be helpful to have some documentation though, but as ResExtension said, sometimes you need to read EVERYTHING to understand one part.

Yes, but if I just want to make a modded version of scratch with every block being red, then I don't want to read hundreds of files.

HTML-Fan wrote:

Yes, but if I just want to make a modded version of scratch with every block being red, then I don't want to read hundreds of files.

Then you can just ask someone like Sheep_Tester, Pulljosh, CatsUnited, MegaApUuTurkUltra or LastContinue who have read all the documentation.

--Explosion-- wrote:

LastContinue

They're gone.

--Explosion-- wrote:

wut iz goog
It would be helpful to have some documentation though, but as ResExtension said, sometimes you need to read EVERYTHING to understand one part.

O_O

--Explosion-- wrote:

who have read all the documentation.

Documentation?