Add post-save hooks

[aseprite-bot]

From davidcapello on July 16, 2012 00:25:07

What do you need to do? Sometimes, after saving a file (e.g. the original .ase file), we want to export it automatically to other format (.png), or export to a sprite sheet, or export it with a larger size. How would you like to do it? Specifying in a configuration dialog what are the post-save hooks for a specific file. There are some options:

• Save a resized version (it's a very common case to publish pixel art on the web)
• Save with other color mode (convert from RGB to Indexed with a specific palette).
• Export sprite sheet (we should be able to configure the sheet parameters as "File > Export Sprite Sheet" command)
  See that all these actions can be combined.
  In the best case, the available/possible actions could be configured in gui.xml file.

Note: The real implementation could be done using a scripting language. Anyway this is for a future issue.

Original issue: http://code.google.com/p/aseprite/issues/detail?id=138

---

Some of this will be available with slices tool #721, the idea is quite simple: If we load/save a file (e.g. test.png) and there is a corresponding .aseprite-data file (e.g. test.png.aseprite-data), we will load/save data in that XML file depending on the content. For example, if we have:

<sprite>
  <slices />
</sprite>

Slices should be saved in the .aseprite-data file. The same might be true for other elements like <frames>, <layers>, <cels>, etc.

[whizzter]

I was pondering about this (and with other tools also) since i often find myself iterating things in different projects with different needs usually resorting to a makefile or batch file so my flow typically becomes: editor -> run batchfile -> test (or go over if i forgot to run the batchfile!).

Maybe aseprite could look for a specially named file in the target directory and then run it on save/export if it exists.

F.ex. saving blah.ase somewhere would run "aseprite_auto_export.bat blah.ase" (or aseprite_auto_export.sh on non-windows). That way people could write their own batch export rules or tools in their own languages regardless of whatever scripting language you look into in the future?

[dacap]

Maybe aseprite could look for a specially named file in the target directory and then run it on save/export if it exists.

Some time ago I was thinking about the same possibility to customize save behavior/some kind of plugin for each sprite. But I think #126 (planed for v1.2) will include a better opportunity to add code snippets to create post-save hooks for a set of sprites.