Add post-save hooks #138
Comments
|
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? |
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. |
Added a new Events object with :on() and :off() methods to start or stop listening to a specific event respectively. This also allows to add several callbacks for the same event. Replaced the temporal Site.onChange & Sprite.onChange implementations. Related to several issues (enable more possibilities for): #138, #1403, #1949, #2965, #2980
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:
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-datafile (e.g.test.png.aseprite-data), we will load/save data in that XML file depending on the content. For example, if we have:Slices should be saved in the
.aseprite-datafile. The same might be true for other elements like<frames>,<layers>,<cels>, etc.The text was updated successfully, but these errors were encountered: