rooob

Tables


I think a much needed feature in scratch is tables. They would be like lists, but you can add multiple columns to them. Some block examples would be:
add [thing] to [table v] at row (1) column (1) ::list

add [column v] to [table v] ::list

remove [row v] from [table v] ::list

remove [column v] from [table v] ::list
please consider adding these items scratch team.

EDIT:
Scratch - Array
The settings for the rows, columns, and dimensions may be confusing as I made this in 5 minutes, but I hope you understand the main layout.

ResExsention

You're using a different term for “arrays”, right?

Even though it's workaroundable, support. Multidimensional arrays are extremely useful (such as in a board game where you need to store information on the pieces).

Also, this is a duplicate of something I think…

VFDan

I support, they are extremely useful (for similar reasons that RexExsention said). Even though it is workaroundable, it takes a lot of code.

15-MinuteGaming

This has a very simple workaround. However, the feature is important. Therefore, support.

bybb

For support this would have to be generic N dimensional arrays rather than simply 2D tables.

ResExsention

bybb wrote:

For support this would have to be generic N dimensional arrays rather than simply 2D tables.

Yeah, I agree. Occassionally 2D arrays are too limited.

Troyer_Kem

Support. This would be a big feature.

BlueStarPort

Support, even though I don't fully grasp the suggestion, this would definitely benefit scoreboards and things like that.

ResExsention

BlueStarPort wrote:

even though I don't fully grasp the suggestion

Essentially, tables are sort of like lists. The difference is that lists are only one dimensional, but tables are two dimensional. With lists, you would refer to information using an index, but with tables you can use coordinates. I like to think of tables and lists like chessboards. Lists only have one row, but tables can have as many as you want.

BlueStarPort

ResExsention wrote:

BlueStarPort wrote:

even though I don't fully grasp the suggestion

Essentially, tables are sort of like lists. The difference is that lists are only one dimensional, but tables are two dimensional. With lists, you would refer to information using an index, but with tables you can use coordinates. I like to think of tables and lists like chessboards. Lists only have one row, but tables can have as many as you want.
OK.

ResExsention

BlueStarPort wrote:

ResExsention wrote:

BlueStarPort wrote:

even though I don't fully grasp the suggestion

Essentially, tables are sort of like lists. The difference is that lists are only one dimensional, but tables are two dimensional. With lists, you would refer to information using an index, but with tables you can use coordinates. I like to think of tables and lists like chessboards. Lists only have one row, but tables can have as many as you want.
OK.

???

It's kind of difficult to comprehend “OK” by itself… That's alright though.

rooob

bybb wrote:

For support this would have to be generic N dimensional arrays rather than simply 2D tables.
I agree that you should be able to have N dimensional arrays as this would be very useful in storing data for 3D games.

rooob

BlueStarPort wrote:

Support, even though I don't fully grasp the suggestion, this would definitely benefit scoreboards and things like that.
Here is an example of what they might look like
Scratch - Array
The settings for the rows, columns, and dimensions may be confusing as I made this in 5 minutes, but I hope you understand the main layout.

CatsUnited

rooob wrote:

BlueStarPort wrote:

Support, even though I don't fully grasp the suggestion, this would definitely benefit scoreboards and things like that.
Here is an example of what they might look like
Scratch - Array
The settings for the rows, columns, and dimensions may be confusing as I made this in 5 minutes, but I hope you understand the main layout.
Link gives a 403 error. We don't have permission to see it.