Thanks @Jay_Lefebvre. The demo is just a proof of concept showing that a valid SVG can be rendered in Coda ā but the SVGs themselves are copied from wherever I found those samples (Wikipedia etc).
Now, the way you compose that SVG is up to you.
You can make a <g><rect ... /><text ...>...</text></g> for a bubble for each task, for example, and calculate X/Y positions of each bubble with some algorithm to position those on the mind map. Then append all groups together inside the <svg> tag and feed to the URL encoder and to Image().
If Iām sober enough tomorrow after the New Year, maybe Iāll compose some rudimentary mind map impl myself.
Whatās important here is that virtually any report output is now available in Coda. Not just images, but custom styled tables too (as a vector image).
This is exciting. Very exciting. For the sake of this community, please be sober enough tomorrow Happy new year to you, your help has been very precious and lots of our projects were inspired by your templates & ideas. Thank you
I remember you were quitting Coda because of pricing ā didnāt the update change your mind?
The way you hacked stuff together in those gradient generators and music players ā if you put that kind of creativity and dedication to the SVG capability, it would be da bomb
I didnāt so much āquitā Coda as I decided on a different tool for now to accommodate different priorities. I like Coda, and will come back to it.
As for the āgradient generators and music players,ā I must admit that you are thinking of someone else. Time to update the post with the real hero!
@Paul_Danyliuk , this is amazing! Above and beyond. Congrats! This is gonna take a while to process. But canāt wait to work with these capabilities.
The pricing announcement was an emotional time for everyone. Who was I kidding! I could never leave coda. I just think about my docs a little differently now to keep em at the free tier.
Hey! Itās on the last column, youāll see it if you scroll to the right.
This is more of a pro trick though. Youāll benefit more if you get comfortable with the āout of the boxā stuff first I think Welcome to Coda, and weāre here to help.
Thanks, I watch a few tut itās all about spreadsheet like features, so I was not very interested, until I see this svg. But what kind of doc or template to use then to be able to create SVG in coda ?
Well, hereās one working example / proof of concept:
Here Iām using the table of tasks to calculate the X/Y coordinates of each node, then generating SVG for individual nodes and connector lines to parents (as simple as center X/Y of one node to center X/Y of another), and finally combining that all together into something that can be fed to Image(). I had to figure out the algorithm to calculate node position myself (and itās a pretty naive one, although it gives good-enough results). You can do something similar for your needs. This said, you either need to know how to compose SVG code, or use an editor and then strip out all the bloat that editors usually put inside exported SVG.
I know SVG, Javascript, what I donāt understand is how coda.io works documentation seems non existant for that kind of stuffs. You talk about table and formulas, that I understand but I canāt see how youād use them to generate SVG: in excel you cannot use formulas to generate images so how coda.io allows it?
To put shortly, Iām simply leveraging standard browser functionality.
Coda translates function Image(url) directly into <img src="url" ā¦ />. Well, it removes whitespaces, but nothing beyond that.
Browsers support Data URI ā i.e. capability where instead of resource link (URL) youāre providing the data encoded right there. You may have encountered this with Base64 mostly.
So the task was ultimately to compose data URI to feed to the Image tag that would be rendered as a valid image. SVG is a text format (i.e. easy to compose by simply concatenating strings and filling in parameters with Format(), so it was an obvious first choice.
Since Coda strips out spaces from the data URI and SVG needs them, I went with URI encoded format. Since Codaās own EncodeForUrl() was far too eager and encoded more than it should have (and the output wasnāt rendering at all), I kinda implemented my own.
In the very end, Iām composing SVG elements out of data rows, concatenating them together, URI encoding, prepending with data:image/svg+xml;, and feeding to Image()