For those who have been interested in my public Zettelkasten wiki in the past (or might be interested in it now), I've just put up an extensive discussion of Zettelkasten and how I've implemented it in my TiddlyWiki on my YouTube channel:Here are the segments if you're curious:About Zettelkasten:0:00 Welcome and introduction1:00 Public and private versions of my Zettelkasten2:08 What is a Zettelkasten?4:16 What idea tiddlers look like and how we navigate through them6:28 Implementation evolves with the contentOrganizing my Zettelkasten and relating ideas:7:06 Why I use CamelCase names
8:12 Expressing relationships by linking9:40 Expressing memberships by tagging10:07 Tags serve in many roles – topics/indexes, publicity level, lists, types, pseudo-types, and maintenance15:42 Index tiddlers provide overviews of a topic area17:33 Transclusion can combine with the ‘description’ field to create overviews18:42 Why I don’t use tags for all overviews19:28 Stretchtext creates interactive, expandable overviews20:42 Subtiddlers aggregate tightly coupled content23:58 Bibliographies aggregate related sources
25:38 The Write tab highlights fruitful areas for further work (stubs, missing, needing attention, needing excision, to-dos, open questions)29:58 The Reference Explorer shows related tiddlers (backlinks and forward links) in a concise table
34:48 Graph theory and Zettelkästen; link graph37:11 Types of tiddlers; why I include non-idea tiddlers, unlike classic Zettelkasten
Plugins and custom TiddlyWiki logic:41:04 Interesting TiddlyWiki plugins I use47:17 Publishing only part of a TiddlyWiki (public/private switch): Marking tiddlers49:05 Public/private: The PrivateChunk51:28 Public/private: The build process (shell script)54:18 Custom copy-title and permalink buttons55:38 GIS (mapping) support for places57:55 The missing-tiddler helper58:36 Quick reading-list import by pasting a URL59:30 Reading inbox1:00:15 Simple Analytics and raw markup snippets1:01:05 Sorting tags by color and putting them in columnsPhilosophy:1:03:01 Just get started and then continuously improve1:05:20 The Three-Links Heuristic for determining whether ideas are effectively linked together1:07:02 A Zettelkasten never walks backwards: consistency doesn’t matter that much1:08:56 Why I default to open and publish my Zettelkasten1:11:25 Polyspecialize your Zettelkasten, include variety1:13:34 Prioritize; you won’t have time to write about everything1:14:55 Using the flexibility and user-programmability of TiddlyWiki to your advantage
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/836c46ea-f0ef-4ba9-adcc-641019205ca9n%40googlegroups.com.
Hi Soren,
Very impressive project and one really can learn alot both from Tiddlywiki point of view and also knowledge/information management.While I always have to change the pallet to something lighter (I cannot read some text or find some icons due to low contrast for me = this is partially because of issues in the official palette),
23:58 Bibliographies aggregate related sourcesYou know Refnotes! There we use the Bibtex plus APA7. The benefit is you can import Bibliography for different sources and there is no need to enter them manually (error prone, tedious)ViewTemplates can be used as you did, and one can decide what to show and how to show fields.While I think bibliography on the web and hypertext media can be totally different, do you think sticking to some standards is better or not?I do not have a specific opinion here and I want to see what is the best solution!
25:38 The Write tab highlights fruitful areas for further work (stubs, missing, needing attention, needing excision, to-dos, open questions)29:58 The Reference Explorer shows related tiddlers (backlinks and forward links) in a concise tableWonderful! While I think not all tiddlers need that! I saw it can be customized
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/56770607-6adf-42b5-bf01-74ec46ea6bd0n%40googlegroups.com.
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e98729e2-32d8-40a9-b6b8-572575feb1ecn%40googlegroups.com.
I really love the system overall, but just can't get the hang of this text editor variant, so if there's any way to make it revert to standard, i'd sure like to know how.
Curious – what tiddlers do you think don't need a link summary?
Haha, sorry, I forgot to turn off the vim keybindings. PMario has explained how to do that.
On Saturday, April 17, 2021 at 1:30:57 PM UTC-5 ludwa6 wrote:
OK, after struggling w/ this a bit, i have to stop and ask: is there something that would cause the editor widget to behave very differently from standard TW5?...
On Saturday, April 17, 2021 at 6:06:29 PM UTC+1 Soren Bjornstad wrote:
The public version lacks some functionality that is important for editing and has a bunch of settings changed that are a bit of a pain to change back, so it'll be much better if I do a second build off of the "real" private version. I've attached a first 15-minute attempt at this.Things that could use improvement here:
- There are no instructions at all, so you'll have to figure out how to get started on your own. Some of the conventions tiddlers are missing and would be nice to have.
- I included all the red, yellow, and black tag tiddlers, but since there is no content in this version, most of them are not tagging anything, so they don't show up in the tags list. Also, some of the tag tiddlers have content that probably won't be very useful for you in them.
- There's a button for the ReadingInbox on the toolbar, but said inbox is not included in the edition at present. You can hide or delete that button tiddler.
Please let me know what else does not work right – I'd love to add a build of this edition to my standard publish process in the future....
A manual option would be to go to $:/AdvancedSearch, type in the filter you want to export (e.g., [tag[Public]] [is[system]]), use the export button to the right of the search box to export as JSON, and then import that JSON file into a fresh empty.html and publish that HTML file.
That said, since you are already using Node.js, automating this with "command-line voodoo" isn't that hard, and then it will do everything for you with one command, without a chance of making mistakes. Here's a simplified version of what I use. I'm guessing you're using Windows, but if so and you have github.io set up, you probably already have Git for Windows installed, which will be enough to run a Bash script like the one below. Mac/Linux will run this script out of the box....
Looks like my filter missed the TODO tiddler, which should contain:\define todore() \[\[TODO\]\]:\define splitre() [\.\?!]To add a TODO item to this list, simply link to [[TODO]].<dl><$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer><$list filter="[<outer>get[text]splitregexp<todore>last[]splitregexp<splitre>first[]]" variable=inner><dt><$link to=<<outer>>/></dt><dd>''TODO:'' <<inner>>.</dd></$list></$list></dl>
...
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/cfKfrAzHZyg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/16e3c509-0abc-46f0-871b-e41762d9e43en%40googlegroups.com.
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/940599c1-da65-46a8-9e30-acb6115c2238n%40googlegroups.com.
There's one minor issue with the TiddlyStretch plugin, at least the stretch-links widget. There is an extra line break in the rendering in Firefox (Desktop version in Windows10). Should I report that as an issue on the GitHub page? - For me it's no big deal but I thought you might want to know.
Building my instance off this template, i'm now trying to develop a few topical Bibliographies, each with a list of Sources, but it's not working the way you show in the video, @Soren.When i click the "Sources" tool, it opens up a "New Source" tiddler that contains only the following set of fields by default; the "Bibliography" field that appears at top of the list in your video at min.24'54" does
not show up in mine -neither by default nor in the dropdown list of Field Names with which i might customise the tiddler (tho i suppose this should be done at the level of a View Template, right)?
Also: the "Bibliography" tab in SideBar appears rather enigmatic for the new user of this skeleton Zettelkasten,
who has no Bibliography as of yet, no bibtex entries to "Process," and no clue as to how to make one. I tried using the Search box in that widget, using pulldown param "Author" to search for the Source i created using the "New Source" tool, but it does not appear... And neither does it appear in the table on SourceList tiddler tho -being created via New Source tool- it is of course properly tagged.
This is amazing, Soren, thank you for sharing both the technical part and your interesting thoughts! I thought your actual name was Søren Bjørnstad, so I'm happy to have been corrected:)
For those who have been interested in my public Zettelkasten wiki ...
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/836c46ea-f0ef-4ba9-adcc-641019205ca9n%40googlegroups.com.
One question: How do you select the categories in the Write tab? I mean for Ztellkasten point of view?I watch the viedo but not quite understand your philosophy here!
Also the Explorer while we have the More Tab!
I like to adopt the tiddler reference explorer in minimal yet flexible form and sidebar extra tabs in a plugin (using a different taste).I cannot see any license in your wiki, so I want to get permission if I am allowed to use both these ideas in a new plugin!
On Monday, May 10, 2021 at 2:43:34 PM UTC-5 Mohammad wrote:One question: How do you select the categories in the Write tab? I mean for Ztellkasten point of view?I watch the viedo but not quite understand your philosophy here!I'm not sure I understand the question – are you asking how, technically, the contents of each tab are aggregated, or why I chose that list of "looking for attention" conditions?
Also the Explorer while we have the More Tab!The Explorer is intended to be a simplified version of the More tab for use in the public wiki. I just haven't bothered to hide it in the private one because it hasn't gotten in my way, but it would likely make sense to do so now that I've stopped making changes to it frequently.
I like to adopt the tiddler reference explorer in minimal yet flexible form and sidebar extra tabs in a plugin (using a different taste).I cannot see any license in your wiki, so I want to get permission if I am allowed to use both these ideas in a new plugin!
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/19af44e2-d653-4fb4-9c94-2d7e1f0b0267n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/26ec5e37-6f23-4dc7-95ae-278726c6afbbn%40googlegroups.com.
Hi all, and thanks Soren for so generously sharing your script and workflow here! I've got it mostly up and running on my Mac (macOS 10.14.6, Homebrew something-or-other), but not without running into a few issues - thought I'd note theme here for posterity (and anyone else who tries to get this up and running):
- After decompiling the flat file to Node version (tiddlywiki --load path/to/single/file.html --savewikifolder path/to/output/folder), I was getting an error message when starting the TiddlyWiki server locally with tiddlywiki --listen that read Warning: Plugins required for client-server operation ("tiddlywiki/filesystem" and "tiddlywiki/tiddlyweb") are missing from tiddlywiki.info file. Adding these lines to the plugins listed in tiddlywiki.info seemed to do the trick, though I've no idea what that did/does.
- should be 4) Finally, I was getting some errors auth'ing git/Github, which I was being prompted to do on the command line – this was because of having 2FA enabled, which meant creating a personal access token rather than using my password. I just gave it every scope, probably overkill…
If you --init a node-js server with the command tiddlywiki ./test --init server, the 2 plugins are added. The tiddlywiki/highlight plugin is also added, but not needed by the system. So you can safely remove it, if you don't need it.
Looks like my filter missed the TODO tiddler, which should contain:\define todore() \[\[TODO\]\]:\define splitre() [\.\?!]To add a TODO item to this list, simply link to [[TODO]].<dl><$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer><$list filter="[<outer>get[text]splitregexp<todore>last[]splitregexp<splitre>first[]]" variable=inner><dt><$link to=<<outer>>/></dt><dd>''TODO:'' <<inner>>.</dd></$list></$list></dl>On Sunday, April 18, 2021 at 10:23:28 AM UTC-5 ludwa6 wrote:Good to know, Soren, but first i have to get the basics under control, like: TODO items!About that, you say in your video at 28'47" : "Anywhere that i write the word todo in square brackets, so link to the tiddler todo, gets automatically pulled in here" -here being presumably TODO tab of "Write" feature, since that is the context. I have tried this a number of ways -with square brackets of both types: single (would have to be by some magic i don't see, but since you didn't say "DOUBLE"...) and double (creating a missing tiddler, which i then activated, tagged "Stub"), whether as TODO uppercase or lower... Nothing shows up as expected in that tab, at all.So what am i missing here, i wonder?/waltOn Sunday, April 18, 2021 at 3:31:11 PM UTC+1 Soren Bjornstad wrote:Oh, to convert a single-file wiki to Node.js, all you need is:tiddlywiki --load path/to/single/file.html --savewikifolder path/to/output/folderYou could even do this as a first step in the script above, if you wanted to normally edit in single-file mode but use the automated build.On Sunday, April 18, 2021 at 9:02:28 AM UTC-5 ludwa6 wrote:Thank-you Soren, but to be clear: I'm working in single-file mode, since i was unable to find a way to convert your file to node.js, though that would probably make for a more elegant solution [*]... But the "manual" method you propose below (with slight adaptation, see below) is sufficiently well-automated, it makes my workflow relatively painless, as follows:
- In TiddlyDesktop (where i am managing a fair mitt-full of TW5 instances), finish my days edits with a review to ensure tag "Public" is on all the right tiddlers, and none other;
- In $:/AdvancedSearch, run the filter- [tag[Public]!is[system]] -and upload the result set as .json, to...
- Drag & drop that .json file into the my local PUBLIC instance (subset of the above), which is they synced to...
- My github.io repo : pull from there (just to ensure there are no conflicting edits), then commit/comment/push changes online.
NB: I'm using Atom text editor (on Mac, b/t/w, not Windows) for the last step, just because i like its change management workflow, but there's a desktop app for Github that is probably the most intuitive GuI app for this purpose.[*] As to that more elegant solution: if it were a node.js instance i had in github, then i can see how it might be easier to manage a dataflow based on individual tiddlers, instead of one big .html file -especially if others were to be engaged in collaborative editing (via Github Pull Request)... But that's a bridge too far for me to even think about at this point. Gotta play with this for a while first IMCST (In My Copious Spare Time -ha!), in the hope that it will at some point save me more time than it costs me to manage it -the most important question to ask of any database app, i guess, yes?/waltOn Sunday, April 18, 2021 at 1:35:05 PM UTC+1 Soren Bjornstad wrote:A manual option would be to go to $:/AdvancedSearch, type in the filter you want to export (e.g., [tag[Public]] [is[system]]), use the export button to the right of the search box to export as JSON, and then import that JSON file into a fresh empty.html and publish that HTML file.That said, since you are already using Node.js, automating this with "command-line voodoo" isn't that hard, and then it will do everything for you with one command, without a chance of making mistakes. Here's a simplified version of what I use. I'm guessing you're using Windows, but if so and you have github.io set up, you probably already have Git for Windows installed, which will be enough to run a Bash script like the one below. Mac/Linux will run this script out of the box....