search

jmoenig / Snap

a visual programming language inspired by Scratch
http://snap.berkeley.edu
GNU Affero General Public License v3.0
1.49k stars 743 forks source link

Resizing images #692

Open geaplanet opened 9 years ago

geaplanet commented 9 years ago

The editor of costumes (PNG or JPEG) has a poor shrink/grow function, quickly images get blur. On the contrary, resizing with blocks has a much better result.

cycomachead commented 9 years ago

When you are trying to resize images -- are you doing it only 1 using the costume editor, or multiple times?

The two work slightly differently, but the results shouldn't be all that different. Could you share a few more details or images?

studej commented 9 years ago

It is really like that. I can confirm @geaplanet words.

deader69 commented 9 years ago

Shrink is a 'lossy' transformation, inside the paint program. That's a good thing, because I'm pretty sure it reduces data size.

You can also keep the art at it's original resolution, and shrink it at run time with the 'set/change size' Looks blocks.

They're both good techniques, each with pros/cons. I wouldn't consider it a bug.

I teach kids to filter their google image searches by size, so they're not loading HUGE bitmaps.

geaplanet commented 9 years ago

I don't think it reduces data size, simply is a brutal lossy transformation. It should be work equal set/change size blocks. Now is useless and the results are horrible even if you only want reduce data size.

introlinux commented 6 years ago

I agree with @geaplanet, my pupils have to resize with GIMP previously the images becase shrink/grow function are unusable are they are now. In my opinion, it is nonsense because having an editor in Snap!, why go out simply to resize images? We could use blocks to resize, but it get the code dirty unnecessarily. Here a little video comparing resizing with editor and with blocks.

resinzing