Two new things for your enjoyment in the tiles world. First, Tiles Protocols: dasl.ing/tiles-protoc... This provides a basic framework explaining how tiles communicate with their hosts. It also serves as a registry for tile protocols.
Post
dasl.ingDASL: Tiles ProtocolsTiles ([[tiles]]) are intended for use in a diversity of environements. Depending on the environment that they find themselves embedded in, they will have access to different capabilit...
And the first such protocol, Data Passing: dasl.ing/tp-data.html. This is to pass structured clone data between tile and host. It provides a simple protocol to do that, as well as a model for other protocols that will also pass data (which they will).
dasl.ingDASL: Tiles Protocol: Data PassingPasssing data to and from tiles is key to integrating tiles in arbitrary environments. This protocol specifies precisely that.
The latest @dasl/tiles libraries already support this: npmx.dev/package/@das.... Notably, the webtil.es tile loading source supports the data protocol, so anything that embeds on that basis can use it right away.
npmx.dev@dasl/tiles - npmxAll-purpose web tiles library (meta-package re-exporting the @dasl/tile-* libraries)
If you want to play with the data protocol, you can use Blastile 💥💥💥: tangled.org/robin.berjon.... It's a (vibed) deno desktop app that can run local tiles, watch a directory to auto-refresh a tile as you're building it, emulate passing data, publish a tile to AT, etc.
tangled.orgrobin.berjon.com/blastileA repository on Tangled