paddle2see wrote:

*** Note from the Scratch Team ***

Please don't add links to browser extensions, userstyles or userscripts - that's going against this policy

wikibro300000 wrote:

I like the idea, and I see that you wanted to link the nono word, that lets you already do it

paddle2see wrote:

*** Note from the Scratch Team ***

Please don't add links to browser extensions, userstyles or userscripts - that's going against this policy

Lukia26 wrote:

My question is simple (so sorry if someone already asked about this). Will Scratch ever add onion skins? If they did, that would be so awesome XD lol…just saying. You should be able to turn it on and off. For those who don't know what an onion skin is, it's the option to show a ghost image of the previous costume on the drawing screen, without it actually being part of that costume. It's very useful for animation. I've tried to use Pencil and import files into Scratch, but it never seems to work, the formatting is weird, etc. I'm not trying to ask too much, but this addition would make a huge difference to me.
Thanks for listening,

~Luki

*** Note from the Scratch Team ***

Please don't add links to browser extensions, userstyles or userscripts - that's going against this policy

1. For onion skins to work, they need users to understand and manipulate multiple frames at the same time. This'll cause a learning curve for people who are beginners (Scratch's target audience) or people who don't know what they are, making the animation process harder and longer.
   
2. Being able to store and manage multiple frames takes alot of file size. Since projects already have small size, this'd be really really bad.
   
3. It needs more processing power and also memory, so it'd be a lot slower and kill performance on some devices.
   
4. It can clutter up the editor, which'd distract and confuse people.
   
5. Feature creep: https://www.productplan.com/glossary/feature-creep/#:~:text=What%20is%20Feature%20Creep%3F,find%20the%20functionality%20they%20need.
   

indigofunny wrote:

(#451)
Feature creep: https://www.productplan.com/glossary/feature-creep/#:~:text=What%20is%20Feature%20Creep%3F,find%20the%20functionality%20they%20need.

bobcat0701 wrote:

I wouldn't consider this feature because animation is such a big part of Scratch…

indigofunny wrote:

bobcat0701 wrote:

I wouldn't consider this feature because animation is such a big part of Scratch…

Still it'll confuse new people and will overwhelm them with all the options.

yadayadayadagoodbye wrote:

Not exactly, this option would be pretty easy to understand if they named it something that doesn't sound so much like a food.

indigofunny wrote:

yadayadayadagoodbye wrote:

Not exactly, this option would be pretty easy to understand if they named it something that doesn't sound so much like a food.

But that's what it's called. Calling it something else would confuse people especially if they know it's actually called an onion skin.

yadayadayadagoodbye wrote:

indigofunny wrote:

yadayadayadagoodbye wrote:

Not exactly, this option would be pretty easy to understand if they named it something that doesn't sound so much like a food.

But that's what it's called. Calling it something else would confuse people especially if they know it's actually called an onion skin.

It is also viable to add a description for it, just like the descriptions for the blocks in 2.0
And you could always just called it “show previous costume as overlay”, which is straightforward enough that it can be understood via common sense and a bit of expirementation atmost

1. That's even longer!!! That'd confuse many kids.
   
2. Most kids don't know what overlay is so it would be very confusing.
   

indigofunny wrote:

There are alot of reasons to not add onion skins.

1. For onion skins to work, they need users to understand and manipulate multiple frames at the same time. This'll cause a learning curve for people who are beginners (Scratch's target audience) or people who don't know what they are, making the animation process harder and longer.
   
2. Being able to store and manage multiple frames takes alot of file size. Since projects already have small size, this'd be really really bad.
   
3. It needs more processing power and also memory, so it'd be a lot slower and kill performance on some devices.
   
4. It can clutter up the editor, which'd distract and confuse people.
   
5. Feature creep: https://www.productplan.com/glossary/feature-creep/#:~:text=What%20is%20Feature%20Creep%3F,find%20the%20functionality%20they%20need.
   

I hope you understand

indigofunny wrote:

yadayadayadagoodbye wrote:

indigofunny wrote:

yadayadayadagoodbye wrote:

Not exactly, this option would be pretty easy to understand if they named it something that doesn't sound so much like a food.

But that's what it's called. Calling it something else would confuse people especially if they know it's actually called an onion skin.

It is also viable to add a description for it, just like the descriptions for the blocks in 2.0
And you could always just called it “show previous costume as overlay”, which is straightforward enough that it can be understood via common sense and a bit of expirementation atmost

1. That's even longer!!! That'd confuse many kids.
   
2. Most kids don't know what overlay is so it would be very confusing.
   

indigofunny wrote:

yadayadayadagoodbye wrote:

indigofunny wrote:

yadayadayadagoodbye wrote:

Not exactly, this option would be pretty easy to understand if they named it something that doesn't sound so much like a food.

But that's what it's called. Calling it something else would confuse people especially if they know it's actually called an onion skin.

It is also viable to add a description for it, just like the descriptions for the blocks in 2.0
And you could always just called it “show previous costume as overlay”, which is straightforward enough that it can be understood via common sense and a bit of expirementation atmost

1. That's even longer!!! That'd confuse many kids.
   
2. Most kids don't know what overlay is so it would be very confusing.
   

The-Sushi-Cat wrote:

indigofunny wrote:

There are alot of reasons to not add onion skins.

1. For onion skins to work, they need users to understand and manipulate multiple frames at the same time. This'll cause a learning curve for people who are beginners (Scratch's target audience) or people who don't know what they are, making the animation process harder and longer.
   
2. Being able to store and manage multiple frames takes alot of file size. Since projects already have small size, this'd be really really bad.
   
3. It needs more processing power and also memory, so it'd be a lot slower and kill performance on some devices.
   
4. It can clutter up the editor, which'd distract and confuse people.
   
5. Feature creep: https://www.productplan.com/glossary/feature-creep/#:~:text=What%20is%20Feature%20Creep%3F,find%20the%20functionality%20they%20need.
   

I hope you understand

1. I'm an animator! Trust me, it's not too complicated. And it makes animating WORLDS easier! Currently, I have to copy my previous sprite, paste it into another costume, change the color, convert it to vector, trace it with vector lines with slight variation, remove the old costume, and convert it to bitmap. That sounds more complicated than say, hitting a button.
2. It's a simple overlay and opacity change
3. You can turn it off if it's really ruining your device, but my tablet can't handle a lot of things, but onion skin is definitely something it can
4. It's a very small add-on. As big as the other buttons. We're not changing the whole editor. It's one thing. Not many people will be confused, and it'll only take kids a few seconds to realize that it turns on an outline for the previous frame
5. This would be adding to the value! It helps people be more creative on the website! Besides, ST doesn't update too often and they aren't cluttering the site

1. I mean I trust you about you understanding the feature. But like, I don't know if little kids would.
   
2. I know what I'm talking about, it takes up space to store multiple.
   
3. Ok ok fair fair
   
4. The wiki said there was a really simple sound feature (I think called echo) that was really really easy but was removed anyway because it overwhelmed alot of kids–
   
5. I believe you but it would be too confusing.
   

The-Sushi-Cat wrote:

indigofunny wrote:

yadayadayadagoodbye wrote:

indigofunny wrote:

yadayadayadagoodbye wrote:

Not exactly, this option would be pretty easy to understand if they named it something that doesn't sound so much like a food.

But that's what it's called. Calling it something else would confuse people especially if they know it's actually called an onion skin.

It is also viable to add a description for it, just like the descriptions for the blocks in 2.0
And you could always just called it “show previous costume as overlay”, which is straightforward enough that it can be understood via common sense and a bit of expirementation atmost

1. That's even longer!!! That'd confuse many kids.
   
2. Most kids don't know what overlay is so it would be very confusing.
   

Kids are clever and can be pretty smart! If a kid turns it on and sees an outline of their previous costume, they'd immediately understand what the button does! They may not entirely understand it's purpose yet, but I didn't understand what the “bitmap” button did, yet Scratch still has it on there and I figured it out pretty quickly!

And they don't need to know the definition of every word. I had no idea what vector, bitmap, variables, functions, or any of that stuff was or what it meant! I wasn't too confused. I could still navigate the site and create!

mcsquaggle wrote:

indigofunny wrote:

yadayadayadagoodbye wrote:

indigofunny wrote:

yadayadayadagoodbye wrote:

Not exactly, this option would be pretty easy to understand if they named it something that doesn't sound so much like a food.

But that's what it's called. Calling it something else would confuse people especially if they know it's actually called an onion skin.

It is also viable to add a description for it, just like the descriptions for the blocks in 2.0
And you could always just called it “show previous costume as overlay”, which is straightforward enough that it can be understood via common sense and a bit of expirementation atmost

1. That's even longer!!! That'd confuse many kids.
   
2. Most kids don't know what overlay is so it would be very confusing.
   

ok so onionskins are very simple in scratch. click a button. pretty easy to understand. so that version would be added. not what i would have. a whole chart with a bunch of checkboxes and stuff.