Replies: 1 comment 5 replies
-
Hi @linonetwo a challenge here is transclusions of other tiddlers, or macro calls. They all require an entire wiki, not the single tiddler on its own. So perhaps your browser extension would need to walk up the tree to load the other tiddlers from the repo before trying to render the target tiddler. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In #6565 (comment) :
Let's discuss here, I actually mean render
*.tid
file anywhere in the network, for example, https://github.com/Jermolene/TiddlyWiki5/tree/master/plugins/tiddlywiki/codemirrorI hope we can have this tid file rendered correctly. I think we can make a browser extension or userscript, if TiddlyWiki npm package can get rid of the node part and work completely in the browser.
This requires npm package exports a pure function, that have a tid file string as input, and HTML as output, this is what I mean by Headless mode, (but is for render 3rd party content...) like in #6141 (comment)
Server side rendering
Or maybe I can write a plugin that provides a server route
/rendering
that receives any string send from a browser extension or userscript, and render this string in the nodejs server, then send back the result...There may be some security issues, but I think I can manage to create a sandbox before calling any API from
$tw.wiki
...Beta Was this translation helpful? Give feedback.
All reactions