top | item 41101504 (no title) mrled | 1 year ago Oh man, you're right, I didn't realize they worked this way. This basically means there is no compromise at all, I'm going to update the post. Thanks! discuss order hn newest panstromek|1 year ago Well, there's still a compromise to be fair. It's defintely more work to manage these sprites and it's especially annoying when there's more than one state. I think it's possible to write some tool to automate it, but I haven't found one. unknown|1 year ago [deleted] douglee650|1 year ago There are preprocessors that will do this. Conceptually, we would: include sprite-1.snippet include sprite-2.snippet and it would write the defs into the page. Then later in the page, `<use>` the defs you included.
panstromek|1 year ago Well, there's still a compromise to be fair. It's defintely more work to manage these sprites and it's especially annoying when there's more than one state. I think it's possible to write some tool to automate it, but I haven't found one. unknown|1 year ago [deleted] douglee650|1 year ago There are preprocessors that will do this. Conceptually, we would: include sprite-1.snippet include sprite-2.snippet and it would write the defs into the page. Then later in the page, `<use>` the defs you included.
douglee650|1 year ago There are preprocessors that will do this. Conceptually, we would: include sprite-1.snippet include sprite-2.snippet and it would write the defs into the page. Then later in the page, `<use>` the defs you included.
panstromek|1 year ago
unknown|1 year ago
[deleted]
douglee650|1 year ago