search

alpine-alpaca / asefile

Library for loading Aseprite files. Directly reads binary Aseprite files and does not require you to export files to JSON.
MIT License
40 stars 15 forks source link

Combine forces with ggez/aseprite crate #18

Open tversteeg opened 1 year ago

tversteeg commented 1 year ago

Since yesterday I've become a maintainer for the ggez/aseprite crate.

Since the aseprite crate is purely focused on parsing exported JSON, and this crate is focussed on parsing .aseprite files, I think it would be nice to somehow combine them or at least collaborate.

From a user's perspective, I think a workflow where you can work with the .aseprite files directly, ideally with hot reloading, and during a release build the JSON with a sprite sheet can be exported and bundled. I'm not sure how exactly this would look.

What are your thoughts on this?

feelingsonice commented 6 months ago

@tversteeg any idea what are the differences between the two? Besides the format for which it's parsed?

tversteeg commented 6 months ago

Aseprite only loads the exported JSON, and this crate loads the .aseprite binary files.

alpine-alpaca commented 4 months ago

The goal of this crate is only to be able to parse .asesprite files. The utils is kind of an exception to this and should probably be moved into another crate eventually. Things that integrate this into a more full-featured asset pipeline / workflow should live in other crates.

I'm currently not using this crate myself, and my gamedev time is very limited these days. Therefore, I currently don't have any meaningful thoughts on this.