I really enjoy blade. Really like it because it's easy to create a build phase and have everything run automatically, never worry about that stuff anymore.

Though, I do have a question. When I supply an @3x image, this is what my result looks like: As you can see, it seems that the @3x image is used as an @2x image. This can be a misunderstanding on my side, but I would expect that I have to supply the biggest possible image.

Also, I learned that it's best practice to design @1x images using vector formats. When slicing you just slice everything and than resize your canvas @2x and @3x to make sure you don't get "half pixels" with the @1x images. I know it has been suggested here, but it might be a useful addition to support one (or more vector formats). Those vector files would be the @1x images, and then automate the steps described above.

In Apple Watch, size of the icon of 42mm for NotificationCenter is "27.5x27.5":

    {
      "size" : "27.5x27.5",
      "idiom" : "watch",
      "filename" : "[email protected]",
      "scale" : "2x",
      "role" : "notificationCenter",
      "subtype" : "42mm"
   },

GetSize, therefore, should return floating point.

It would be incredibly useful to be able to set the output resolution in points for an image, because you could store the massive full resolution files and only export low resolution images, which gives you the flexibility of later changing the export resolution as needed.

Hi all!

I've been planning to make Blade more powerful for a long while. Since interest has been growing tremendously for this tool recently, I think that is enough motivation to kick off the next iteration of Blade. I've been requested many times to also have Android support (in addition to updating Blade to recent Apple products), and that is something I plan to have.

You can help! Please comment below of what features you'd like to have the most.

@eralpkaraduman @Dschee @huafeng1992 @ntnmrndn @martinprot @emilwojtaszek please feel free to chime in 🥇

Xcode version 8.3.3,OS 10.12.6

I use the following command: "blade -s icon.png -o AppIcon.appiconset -c" AppIcon.appiconset is a empty directory. A new Contents.json file and all size icons are automatically generated in AppIcon.appiconset directory . That's greate. But the iPhone and iPad Notification sizes are still missing.

Then,I use the following command: "blade -s icon.png -o AppIcon.appiconset -c -t AppIcon.appiconset/Contents.json" Nothing happened.

But I open the Xcode project, which uses the AppIcon.appiconset above,use the following command again. "blade -s icon.png -o AppIcon.appiconset -c -t AppIcon.appiconset/Contents.json"

The iPhone Notification and iPad Notification are both automatically generated.

Is there any way to generate all icons (especially notification) without opening Xcode project?

Hello, I have a problem with blade. I can't find the reason. If you know the question, please reply to me. Thank you How can I get your failure status and terminate shell?

error image:

Let's support icon sizes for iMessage iMessage extensions & sticker packs.

Guidelines

Discussed under iMessage App and Sticker Pack Icons https://developer.apple.com/ios/human-interface-guidelines/extensions/messaging/

By the time I'm writing this, it required variations in sizes:

• 1024px by 768px
• 120px by 90px
• 64px by 48px
• 180px by 135px
• 96px by 72px
• 58px by 58px
• 148px by 110px
• 87px by 87px
• 54px by 40px
• 134px by 100px
• 81px by 60px

When blade is integrated as a build script to automatically be run on each build then build times can become quite long because blade is generating all images – even if nothing has changed. Therefore it would be great if blade could detect when it has to rebuild images and otherwise just keep things as is and skip images that didn't change.

I think in order to achieve this there are several possibilities. The easiest could be that blade simply checks the last change dates of the source file and the destination file and compares those. If the destination file was last changed after the source file was changed then it could skip rebuilding the image, otherwise it would behave like now.

Alternatively blade could also generate a file (something like Bladefile.lock) which lists the date the source images were last built and check if that date is after the source images last change date and the Bladefiles last change date then it would skip the image if both cases were given.

If implemented there should also be a possibility to force rebuilding all images, something like blade --no-skip-unchanged is what I'm thinking of. We could also make it opt-in like so: blade --skip-unchanged.

What do you think? Unfortunately I can't do these changes myself since I don't speak Go (yet).