I am actually trying to do what you achieved, sans the actually specifying the content as a macro parameter part. Imagine the possibilities. If we are able to encode the rendered content, we would be able to share the content of a tiddler with any site that accepts prefilled posting of content. (basically almost all social networks except facebook and google plus.) the same way you did for twitter.
On Tuesday, 27 December 2016 23:39:02 UTC+5:30, Thomas Elmiger wrote: > > Hm, what *exactly* are you trying to do, Riz? > > Could be you would have to send your tiddler through the view widget > twice: render the plain text/html, save that in a field (e.g. of a temp > tiddler) and urlencode it from there (that’s why my macro needs the button > first, it saves the text in a field). Or have a look at the qr code > machinery here: > http://tiddlywiki.com/prerelease/#%24%3A%2Fplugins%2Ftiddlywiki%2Fqrcode > – it seems it can output a tiddler as raw or rendered output. > > All the best! > Thomas > > Am Dienstag, 27. Dezember 2016 18:11:52 UTC+1 schrieb Riz: >> >> @Thomas, actually this whole rabbit hole started with your macro. It was >> excellent that I wanted to adapt it to a wider area. If we use the >> text-urlencode macro in a tiddler like "About", the output is >> Information%20about%20the%20making%20of%20TiddlyWiki%3A%0A%0A%3C%3Clist- >> links%20%22%5Btag%5BAbout%5D%5D%22%3E%3E%0A >> it is encoding the list-links macro as if it was a piece of text. >> >> >> >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e56b9eab-f235-466c-9625-5819ed15e5cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
