search

kilianc / adobe-generator

The missing link
3 stars 0 forks source link

New output option: spritesheet #90

Open timriot opened 11 years ago

timriot commented 11 years ago

A spritesheet can be defined in 2 ways (Would be ideal to support both)

1) Super Easy, which assumes that every layer corresponds to a sprite, ignores groups

Wicked Cool.spritesheet/
  group 1/
    something5
  layer1
  layer2
 ...
 layer100

2) More complex, but much finer control

Wicked Cool.spritesheet/
  group1.sprite/
    layer1
    layer2
  layer5.sprite
  group2.sprite/
    layer20.sprite
  ...
  layer9000.sprite

Basically, I'm thinking ML will assume that it's in easy mode unless it finds the .sprite tag within .spritesheet.

Output

Stylesheet and corresponding image asset. Class names are based on layer/ group names as usual.

Check out: http://draeton.github.com/stitches/

What say you, Christmas Kilian?

timriot commented 11 years ago

I spoke w/Kilian and he (rightly) pointed out that this tagging method is limiting and does not cover the instance where elements would be placed in situ of a layout.

K's proposal is simply:

.spr to denote a sprite for a layer or group

This will be even more natural and unobtrusive to the design process, as well as reinforce the pattern of "if you want it to be something, tag it."

SOLID.

kilianc commented 11 years ago

the "dot" notation doesn't cover the multiple tagging, what if I want to .jpg and .spr a layer? we can't control what people are going to use tags for…

I suggest to use the multiple tagging and consider the ".jpg/png/gif" including the dot a tag, and multiple tags can be separated by spaces.

my_awesome layer.pn8 spr

The problem with it is when we omit the asset dump tag, the word "layer" could be considered a tag. Do we need a Starting tags area token? Also how about multiple sprites? How do I define their names?

In that case a .spr@filename that defaults to .spr@spritesheet and spritesheet.css could work.

Multiple tagging still an issue though.--
Kilian C.

On Friday, December 14, 2012 at 2:59 AM, Tim Riot wrote:

I spoke w/Kilian and he (rightly) pointed out that this tagging method is limiting and does not cover the instance where elements would be placed in situ of a layout. K's proposal is simply: .spr to denote a sprite for a layer or group This will be even more natural and unobtrusive to the design process, as well as reinforce the pattern of "if you want it to be something, tag it."
SOLID.

— Reply to this email directly or view it on GitHub (https://github.com/kilianc/motherlover/issues/90#issuecomment-11362436).