You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One approach to animations is to build your own "driver" to replace svgtiler, which instead imports the API and calls it to load mappings, build the drawings, and render frames. (#34) On the web, we have renderDOM for this; need a similarly simple API call for command-line usage.
For smooth animations like this example, I think this approach might be best. We'd just need to offer a nice API like findTile({key: /foo/, origY: 5, newX: 2}) (searching by key and/or old/new coordinates) and translate/rotate/etc. helpers.
On the web, this could render smooth animations, which would be great for slides with renderDOM. On the command line, we could ask for snapshot frames at various times that get saved as SVG. Something like:
But potentially we could integrate animations into the svgtiler command line. For example, a JavaScript/CoffeeScript file could export a new name like drawings which could look like this:
Generator for multiple frames, instead of needing to wrap in Drawings
replaceAll API feature (and presumably other helpers like findFirst, replaceFirst, findAll)
Maybe there's a way to specify the subname of the drawing. Otherwise use a counter?
Input.recognize isn't very convenient way to specify files; should enable maybe new ASCIIDrawing '''...'''.
Of course, we'd also want a .coffee file to be able to generate a single Drawing, maybe via export drawing. This is the first-level thing that would be cool!
DSL
Another option would be to invent a DSL for specifying animations, something like:
parallel
move (1,2) -> (3,4)
move (3,4) -> (5,6)
replace all 'A' with 'B'
But this might not be worthwhile / flexible enough.
The text was updated successfully, but these errors were encountered:
One approach to animations is to build your own "driver" to replace
svgtiler
, which instead imports the API and calls it to load mappings, build the drawings, and render frames. (#34) On the web, we haverenderDOM
for this; need a similarly simple API call for command-line usage.For smooth animations like this example, I think this approach might be best. We'd just need to offer a nice API like
findTile({key: /foo/, origY: 5, newX: 2})
(searching by key and/or old/new coordinates) andtranslate
/rotate
/etc. helpers.On the web, this could render smooth animations, which would be great for slides with
renderDOM
. On the command line, we could ask for snapshot frames at various times that get saved as SVG. Something like:Older delta encoding approach
But potentially we could integrate animations into the
svgtiler
command line. For example, a JavaScript/CoffeeScript file could export a new name likedrawings
which could look like this:Ideas here:
Drawings
replaceAll
API feature (and presumably other helpers likefindFirst
,replaceFirst
,findAll
)Input.recognize
isn't very convenient way to specify files; should enable maybenew ASCIIDrawing '''...'''
..coffee
file to be able to generate a singleDrawing
, maybe viaexport drawing
. This is the first-level thing that would be cool!DSL
Another option would be to invent a DSL for specifying animations, something like:
But this might not be worthwhile / flexible enough.
The text was updated successfully, but these errors were encountered: