- Dec 2022
-
blog.dornea.nu blog.dornea.nu
-
David Alfonso has done a great job and put together a repository that helps you with the export of tiddlers. All you need is to export all your tiddlers bundled as one single HTML and then follow the instructions in the README.
TiddlyWikiPharo is capable of similar exportation and we start from the single HTML TW file that we can de/recompose almost at will, because we can manipulate the tiddlers inside a data narrative. As shown in the malleable systems wiki example, we're mostly focused in conversions from Markdown to WikiText (TW's format) as it is our most felt necessity, but migrations from WikiText to Markdown are in the radar, combining/extending TiddlyWikiPharo with Pandoc (future needs/funding will tell if/when is implemented).
-
After going down the Emacs rabbit hole, I’ve adopted ORG mode as my main file format for writing documents, exporting these to other formats (PDF, markdown, Confluence, Jira and many others), creating diagrams (mainly plantuml), presentations, writing technical documentation and hopefully some day for publishing a whole book. For the note-taking phase I write my notes in ORG mode and create a rudimentary outline sorted by chapters/sections. Usually I use the same structure to create my blog posts from (like I did in the book summaries). Extracting pieces of information for individual tiddlers, however, tends to be a time-intensive process. I’ve managed to use the Tiddlywiki API within Emacs but my Elisp skills are still not good for doing more advanced stuff like:
We, at the Grafoscopio community create a lot of projects (including presentations, book(lets) writing/republishing, workshops/reading notes) by connecting diverse contexts instead of keeping ourselves inside a single one. Of course, this single context would be possible on an individual level, but connecting different contexts gives account of the diversity of participants in our community and workshops. So we keep contexts limited, minimal and well connected (TW, Fossil, Pharo/GToolkit and Markdown tools like Zettlr or HedgeDoc) but not a single one.
It is the creation of fluent workflows between different tools, that account for different experiences and participants our way to deal with context friction instead of keeping ourselves inside a single context.
All the advanced usages of TW in the list items after this highlight are done inside the data narratives from TiddlyWikiPharo, as told in a previous note with a novice friendlier syntax (Smalltalk instead of Lisp).
-
It became not only my primary editor, but also my RSS feeds reader, mail client, YouTube video player, IDE, API client… I basically live in Emacs Here is my config.org and try to avoid as many context switches as possible.
My context switching friction decrease is related with the way I connect the contexts (for example TW + Glamorous Toolkit vía custom packages like TiddlyWikiPharo instead of being inside a unique context, particularly a text oriented one, with a pretty limited definition of text as it limits what our visual cortex is able to convey with richer text/visuals.
-