Discuss Scratch

Alex5002
Scratcher
100+ posts

Transformations Extension Suggestion

Since Scratch is HTML 5, it would be easy for this to get implemented by the developers of Scratch. And, I mean, this would allow for actually fast, accurate and performant 3D ! Also, rather than ratio, there should be global coordinates-wise too, so positionning a corner directly somwhere whatever is the sprite position would be cool. It would work by mapping an origin point from the srpite, generally on the borders or the corners of this sprite, and “stick” this point to where we want in the scene.

Last edited by Alex5002 (Nov. 9, 2025 09:07:02)

d016
Scratcher
100+ posts

Transformations Extension Suggestion

Alex5002 wrote:

Since Scratch is HTML 5, it would be easy for this to get implemented by the developers of Scratch.

What does that have to do with easy implementation? I think Scratch uses WebGL for it's project rendering.
the_remix_pal
Scratcher
13 posts

Transformations Extension Suggestion

I support this
CoolLock
Scratcher
100+ posts

Transformations Extension Suggestion

the_remix_pal wrote:

I support this
Please explain why you support.
Nameorus
Scratcher
21 posts

Transformations Extension Suggestion

CoolLock wrote:

the_remix_pal wrote:

I support this
Please explain why you support.
probably because its cool. do you want him to write a whole essay?
d016
Scratcher
100+ posts

Transformations Extension Suggestion

Nameorus wrote:

CoolLock wrote:

the_remix_pal wrote:

I support this
Please explain why you support.
probably because its cool. do you want him to write a whole essay?

Yeah, people should say “hey, write a little about why you support” instead of “explain why” out of nowhere.
Cade_MM
Scratcher
41 posts

Transformations Extension Suggestion

By the way, I personally think for easiest use with new scratchers it could simply just be "Move corner to (Relative X coordinate) (Relative Y coordinate)" as this would respect rotation and scale, or you could just incorporate this into the functions the original post recommends.
BW_CA_24
Scratcher
41 posts

Transformations Extension Suggestion

The biggest problem with this is that you can replicate it with pen with the following steps.

1. Get a list of points on the sprite by scanning the screen and using “touching” blocks.
2. Get the colors of those points by scanning through all possible colors and using “touching color” at that location.
3. Use transformations on the points listed, linearly interpolate where needed.
4. Render the result.

I myself would prefer this were made, though, as such methods are much more convoluted compared to how they first appear.
d016
Scratcher
100+ posts

Transformations Extension Suggestion

BW_CA_24 wrote:

The biggest problem with this is that you can replicate it with pen with the following steps.

1. Get a list of points on the sprite by scanning the screen and using “touching” blocks.
2. Get the colors of those points by scanning through all possible colors and using “touching color” at that location.
3. Use transformations on the points listed, linearly interpolate where needed.
4. Render the result.

I myself would prefer this were made, though, as such methods are much more convoluted compared to how they first appear.

Yeah, but do you really want to do all that, just for stretching a sprite?
Just because there's are workaround doesn't mean the suggestion is invalid
Cade_MM
Scratcher
41 posts

Transformations Extension Suggestion

d016 wrote:

BW_CA_24 wrote:

The biggest problem with this is that you can replicate it with pen with the following steps.

1. Get a list of points on the sprite by scanning the screen and using “touching” blocks.
2. Get the colors of those points by scanning through all possible colors and using “touching color” at that location.
3. Use transformations on the points listed, linearly interpolate where needed.
4. Render the result.

I myself would prefer this were made, though, as such methods are much more convoluted compared to how they first appear.

Yeah, but do you really want to do all that, just for stretching a sprite?
Just because there's are workaround doesn't mean the suggestion is invalid

I can see why they would think this, but also its WAY slower and bulkier just for the same effect. Scanning a costume and manually performing interpolation just to make it 10% wider isnt the best.
jmdzti_0-0
Scratcher
1000+ posts

Transformations Extension Suggestion

d016 wrote:

Alex5002 wrote:

Since Scratch is HTML 5, it would be easy for this to get implemented by the developers of Scratch.

What does that have to do with easy implementation? I think Scratch uses WebGL for it's project rendering.
webgl is the api that renders <canvas> elements in html

Last edited by jmdzti_0-0 (Nov. 11, 2025 18:00:19)

Kanyata
Scratcher
55 posts

Transformations Extension Suggestion

Support! this is a really good idea! I hope ST adds this!

Powered by DjangoBB