Debug Window in project editor

ninjaMAR

I have an idea for a debug editor which would be an area of the screen the acts like a console.
The editor would have a new block which would take its input and log it to the console.

log () ::control

This is good so the project does not have to stop and log using the say block.

Last edited by ninjaMAR (March 4, 2021 14:14:11)

Prime689

It may be unclear in terms of functionality to minors, the main users of Scratch. Therefore, we can't determine how this will be helpful for Scratch. Furthermore, using advanced terminology isn't ideal for being comprehensible for minors. So with the points I introduced, no support.

Ihatr

Prime689 wrote:
It may be unclear in terms of functionality to minors, the main users of Scratch.

There are features already in Scratch that I don't think “minors” would understand, that's not a reason to throw this down the drain.

CST1229

Ihatr wrote:
Prime689 wrote:
It may be unclear in terms of functionality to minors, the main users of Scratch.
There are features already in Scratch that I don't think “minors” would understand, that's not a reason to throw this down the drain.

That said, it puts stuff in a place that certainly no minor would understand or go in.
oh, didn't read post, thought it would go to the browser console

Last edited by CST1229 (Feb. 28, 2021 14:21:48)

Prime689

Ihatr wrote:
Prime689 wrote:
It may be unclear in terms of functionality to minors, the main users of Scratch.
There are features already in Scratch that I don't think “minors” would understand, that's not a reason to throw this down the drain.

By what example(s)?

ninjaMAR

Prime689 wrote:
Ihatr wrote:
Prime689 wrote:
It may be unclear in terms of functionality to minors, the main users of Scratch.
There are features already in Scratch that I don't think “minors” would understand, that's not a reason to throw this down the drain.
By what example(s)?

([sin v] of (9))

Prime689

ninjaMAR wrote:
Prime689 wrote:
Ihatr wrote:
Prime689 wrote:
It may be unclear in terms of functionality to minors, the main users of Scratch.
There are features already in Scratch that I don't think “minors” would understand, that's not a reason to throw this down the drain.
By what example(s)?
([sin v] of (9))

Ok, but Scratch is supposed to be an introductory language; so there's a possibility that it will be complex for minors when in coding.

ninjaMAR

Prime689 wrote:
ninjaMAR wrote:
Prime689 wrote:
Ihatr wrote:
Prime689 wrote:
It may be unclear in terms of functionality to minors, the main users of Scratch.
There are features already in Scratch that I don't think “minors” would understand, that's not a reason to throw this down the drain.
By what example(s)?
([sin v] of (9))
Ok, but Scratch is supposed to be an introductory language; so there's a possibility that it will be complex for minors when in coding.

All of the math blocks are complex

ScratchCatHELLO

Prime689 wrote:
ninjaMAR wrote:
Prime689 wrote:
Ihatr wrote:
Prime689 wrote:
It may be unclear in terms of functionality to minors, the main users of Scratch.
There are features already in Scratch that I don't think “minors” would understand, that's not a reason to throw this down the drain.
By what example(s)?
([sin v] of (9))
Ok, but Scratch is supposed to be an introductory language; so there's a possibility that it will be complex for minors when in coding.

why do you use “minors” to describe children
is a textbox that you can write to in the editor really that hard to understand?

ninjaMAR

bump

ninjaMAR

bump

samq64

I do this using lists, but this would be easier Simi-Support.

Last edited by samq64 (March 4, 2021 01:05:09)

Futurebot5

Support! This could be used to see which scripts ran and which didn't.

ninjaMAR

samq64 wrote:
I do this using lists, but this would be easier Simi-Support.

If you support you say support and why

the2000

ninjaMAR wrote:
samq64 wrote:
I do this using lists, but this would be easier Simi-Support.
If you support you say support and why

I'm not sure why they chose to "semi simi-support“ either. That post is like, almost a perfect example of why I think the current ”support" conventions are still annoying.

Steve0Greatness

am I the only one annoyed by the grammar mistake in the op?

Anyways, I'm not too sure how this would work… but I think that it may work as a list, am I correct on that assumption?
I'm also not too sure why you chose the “variables” category for the block, wouldn't it make sense if it were to be:

log () ::control

ninjaMAR

Steve0Greatness wrote:
am I the only one annoyed by the grammar mistake in the op?

Anyways, I'm not too sure how this would work… but I think that it may work as a list, am I correct on that assumption?
I'm also not too sure why you chose the “variables” category for the block, wouldn't it make sense if it were to be:
log () ::control

Whats the grammar mistake? It works like a list but instead it is inside the project editor

gosoccerboy5

A good example of this is println in the Khan Academy code editor. Try it out.

Steve0Greatness

ninjaMAR wrote:
Steve0Greatness wrote:
am I the only one annoyed by the grammar mistake in the op?

Anyways, I'm not too sure how this would work… but I think that it may work as a list, am I correct on that assumption?
I'm also not too sure why you chose the “variables” category for the block, wouldn't it make sense if it were to be:
log () ::control
Whats the grammar mistake? It works like a list but instead it is inside the project editor

ninjaMAR wrote:
a area

should be

ninjaMAR wrote:
an area

misteray

Prime689 wrote:
It may be unclear in terms of functionality to minors, the main users of Scratch. Therefore, we can't determine how this will be helpful for Scratch. Furthermore, using advanced terminology isn't ideal for being comprehensible for minors. So with the points I introduced, no support.

Yes because children below 13 aren't smart enough to use google

Discuss Scratch