Charles Parnot

@lultimouomo Good one, and something I had in mind as well. The lock example is a case where having the keyhole transparent could be useful for instance. But indeed, one...

@Memnarch Yeah, my goal is that the extra stuff is completely optional, and human-readable without documentation. Markdown-like simplicity.

@Memnarch Wow, nice! Regarding the file extension, it's final. Regarding the format, unfortunately, it's not something I am actively working on. The above discussion sets up the YAML basics already...

Sorry I don't really have time to put into the project :( Happy for anyone to work on it.

My main concern in forcing to split everything in multiple paths is that something like this becomes suddenly more tedious: ``` @"· · · · 1 1 1 · ·...

> Fair enough though I would argue in for that particular icon, you want a composite path as the X should be clear and not painted white. Yes, and that's...

Ah, very nice, thanks for pointing that out! That's indeed one more strong argument for coumpound paths. In this particular case,the X is not a closed path, though: just 2...

Ah, got it: CGContextReplacePathWithStrokedPath() http://stackoverflow.com/questions/2737973/on-osx-how-do-i-gradient-fill-a-path-stroke/2770034#2770034

iOS too?

> So technically the iOS and Mac implementations are inconsistent It's more subtle that this. On iOS, the scaling has to be done by your code based on the device...