Ekoserin wrote:

You mean like this? I made it in Inkscape to describe what I think xe's trying to suggest. There is also this Wikipedia article on it.

Pretty Much.

20btheilmanngohr wrote:

I think that scratch should support atlas's. In case you don't know what an atlas is, it's basically a bunch a textures/graphics/etc stored on one sheet.
The costume editor would have two boxes: Tile x/Tile y. These would divide each costume part. The block below would then show a certain section.

snip

It could be implemented in other ways, but this was the one I though of.
EDIT:
The way this works is, Tile X/Y are rows and columns. They could pretty much be called rows and columns, which would make it easier to understand. Anyway, if you had an atlas with 5 rows and 3 columns, Tile X would be 5, and Tile Y would be 3. The section blocks show specific parts of the atlas, so A might be the top left part, B the one after, and etc. Since these blocks only show one section, these blocks should also be added.

snip

One last thing: It really helps to be specific, so at least make your response more than one sentence.

What's the difference between an atlas and a costume? The Scratch Team might have already used the atlas method to store and render costumes.

iamunknown2 wrote:

What's the difference between an atlas and a costume? The Scratch Team might have already used the atlas method to store and render costumes.

Atlas's are basically multiple costumes inside on costume. costumes can hold one texture, while atlas's hold many. As for your other sentence, I'm pretty sure they use png and svg, if that's what you mean.

iamunknown2 wrote:

20btheilmanngohr wrote:

~snip~

What's the difference between an atlas and a costume? The Scratch Team might have already used the atlas method to store and render costumes.

Yeah… I don't see why you can't just use costumes…

If your making something like custom text, you'll need all 24 letters plus punctuation E.G , . / etc. With atlas's you could get a pre-made sheet with everything I just listed, and use it without making too many costumes. Besides, it saves time.

20btheilmanngohr wrote:

If your making something like custom text, you'll need all 24 letters plus punctuation E.G , . / etc. With atlas's you could get a pre-made sheet with everything I just listed, and use it without making too many costumes. Besides, it saves time.

Whike I understand what you are saying, new scratchers might not.

DaSpudLord wrote:

20btheilmanngohr wrote:

If your making something like custom text, you'll need all 24 letters plus punctuation E.G , . / etc. With atlas's you could get a pre-made sheet with everything I just listed, and use it without making too many costumes. Besides, it saves time.

Whike I understand what you are saying, new scratchers might not.

So what if it was toggle-able? You could turn it on, and off if it's confusing.

dude341 wrote:

MathlyCat wrote:

PrincessPanda_test_ wrote:

No support, people might be confused.

How? Just interested, it's a simple concept, have all your art on a singular page, less storage space taken, better efficiency, etc.

I support! I've seen atlas used for games like Minecraft, but that's due to their 3D texturing through 2D graphics.

Minecraft does not work like that. In fact, that insulting to Mojang's hard work on there 3D blocks engine used in Minecraft.

dude341 wrote:

MathlyCat wrote:

PrincessPanda_test_ wrote:

No support, people might be confused.

How? Just interested, it's a simple concept, have all your art on a singular page, less storage space taken, better efficiency, etc.

I support! I've seen atlas used for games like Minecraft, but that's due to their 3D texturing through 2D graphics.

Minecraft does not work like that. In fact, that insulting to Mojang's hard work on there 3D blocks engine used in Minecraft.

You are wrong, all of minecraft's graphics are 2D, their engine creates an illusion/3D effect to make everything 3D, they have multiple layers of 2D to make 3D, you are the one insulting Microsoft. The actual graphics are 3D, but the original textures are all 2D. Minecraft also uses Atlases for their skin feature. Don't be so hasty to point out the facts.

I do know what this suggestion is about mostly, but I'm mainly confused about how the implementation is suggested. When you show/hide a section, does it display it in the same position as the section is relative to the center of its respective costume, or does it somehow center it?

TheMonsterOfTheDeep wrote:

I do know what this suggestion is about mostly, but I'm mainly confused about how the implementation is suggested. When you show/hide a section, does it display it in the same position as the section is relative to the center of its respective costume, or does it somehow center it?

I think it should be centered. It could have different options, but this is probably the most useful one.

20btheilmanngohr wrote:

TheMonsterOfTheDeep wrote:

I do know what this suggestion is about mostly, but I'm mainly confused about how the implementation is suggested. When you show/hide a section, does it display it in the same position as the section is relative to the center of its respective costume, or does it somehow center it?

I think it should be centered. It could have different options, but this is probably the most useful one.

Okay - that makes sense, but then this implementation:

show section [hax v] :: looks
hide section [hax v] :: looks

Doesn't really work - if I show multiple sections, will they simply be drawn over each other? Or will they be displayed with their relative position to each other and still centered?

A better implementation would probably be something like:

switch section to [... v] :: looks

Although that might easily be confusing because of its similarity to costumes…

Another possibility could be something like this:

focus on (0),(0) to (20),(20) of my costume :: looks

But that seems a bit complicated, especially for newer Scratchers…

I think I support this now, I'm just pondering the best way to implement it….

I support, this could save storage space in projects.

20btheilmanngohr wrote:

If your making something like custom text, you'll need all 24 letters plus punctuation E.G , . / etc. With atlas's you could get a pre-made sheet with everything I just listed, and use it without making too many costumes. Besides, it saves time.

There are 26 letters in the alphabet

Cosmicstars- wrote:

Support!

Why not?

CatsUnited wrote:

I support, this could save storage space in projects.

20btheilmanngohr wrote:

If your making something like custom text, you'll need all 24 letters plus punctuation E.G , . / etc. With atlas's you could get a pre-made sheet with everything I just listed, and use it without making too many costumes. Besides, it saves time.

There are 26 letters in the alphabet

*facepalm*

There's 24 in Greek. Unless accents count as separate letters.

TheHockeyist wrote:

CatsUnited wrote:

I support, this could save storage space in projects.

20btheilmanngohr wrote:

If your making something like custom text, you'll need all 24 letters plus punctuation E.G , . / etc. With atlas's you could get a pre-made sheet with everything I just listed, and use it without making too many costumes. Besides, it saves time.

There are 26 letters in the alphabet

*facepalm*

There's 24 in Greek. Unless accents count as separate letters.

I think accents do count as letters, maybe sub-letters. I know a few languages that count their accents as letters.

MathlyCat wrote:

TheHockeyist wrote:

CatsUnited wrote:

I support, this could save storage space in projects.

20btheilmanngohr wrote:

If your making something like custom text, you'll need all 24 letters plus punctuation E.G , . / etc. With atlas's you could get a pre-made sheet with everything I just listed, and use it without making too many costumes. Besides, it saves time.

There are 26 letters in the alphabet

*facepalm*

There's 24 in Greek. Unless accents count as separate letters.

I think accents do count as letters, maybe sub-letters. I know a few languages that count their accents as letters.

I think I did mean 26. English is pretty much the only thing I can speak XD.

TheMonsterOfTheDeep wrote:

20btheilmanngohr wrote:

TheMonsterOfTheDeep wrote:

I do know what this suggestion is about mostly, but I'm mainly confused about how the implementation is suggested. When you show/hide a section, does it display it in the same position as the section is relative to the center of its respective costume, or does it somehow center it?

I think it should be centered. It could have different options, but this is probably the most useful one.

Okay - that makes sense, but then this implementation:

show section [hax v] :: looks
hide section [hax v] :: looks

Doesn't really work - if I show multiple sections, will they simply be drawn over each other? Or will they be displayed with their relative position to each other and still centered?

A better implementation would probably be something like:

switch section to [... v] :: looks

Although that might easily be confusing because of its similarity to costumes…

Another possibility could be something like this:

focus on (0),(0) to (20),(20) of my costume :: looks

But that seems a bit complicated, especially for newer Scratchers…

I think I support this now, I'm just pondering the best way to implement it….

I agree with the section block. Although if it were called show section, it might be sligthly easier to understand. I don't support the other one though, it definitely would be too complex.

20btheilmanngohr wrote:

Pot-of-Gold wrote:

thelucariokid wrote:

DaSpudLord wrote:

Cosmicstars- wrote:

PrincessPanda_test_ wrote:

No support, people might be confused.

No support because for this.

That

this

Could everyone here please be more specific? This post is confusing. Besides, how am I going to to adjust this to make everybody happy

No support. It might confuse remixers. To make everyone happy, it makes it look like an atlas for the creator but uses the normal art system for remixers.

ElectroElectro2004 wrote:

20btheilmanngohr wrote:

Pot-of-Gold wrote:

thelucariokid wrote:

DaSpudLord wrote:

Cosmicstars- wrote:

PrincessPanda_test_ wrote:

No support, people might be confused.

No support because for this.

That

this

Could everyone here please be more specific? This post is confusing. Besides, how am I going to to adjust this to make everybody happy

No support. It might confuse remixers. To make everyone happy, it makes it look like an atlas for the creator but uses the normal art system for remixers.

Umm…I don't understand your reason for no support nor solution. Could you please elaborate a little more? And what's different between remixers and creators? Pretty sure I mentioned this being a toggle-able feature somewhere…

20btheilmanngohr wrote:

TheMonsterOfTheDeep wrote:

-snip-

I agree with the section block. Although if it were called show section, it might be sligthly easier to understand. I don't support the other one though, it definitely would be too complex.

The reason the “show section” block is kind of confusing is because I don't understand what would happen if multiple sections where shown at once.

But I'm still not sure of the best wording - here's a new option I thought of based on my previous ones:

focus on section [section v] :: looks

“focus on” is the best description I could come up with for only displaying part of the sprite - can anyone think of something better? Because I don't think the blocks should be analogous to costume blocks as the sections are rather different and are in fact parts of costumes.

TheMonsterOfTheDeep wrote:

20btheilmanngohr wrote:

TheMonsterOfTheDeep wrote:

-snip-

-snoop-

The reason the “show section” block is kind of confusing is because I don't understand what would happen if multiple sections where shown at once.

But I'm still not sure of the best wording - here's a new option I thought of based on my previous ones:

focus on section [section v] :: looks

“focus on” is the best description I could come up with for only displaying part of the sprite - can anyone think of something better? Because I don't think the blocks should be analogous to costume blocks as the sections are rather different and are in fact parts of costumes.

set shown section to [A1 v] :: looks

A1 being rows (a) and columns (1)