-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lynx knowledge navigator #1733
Comments
Hi @Adapts I'm not sure what you are referring to by "Lynx"; do you mean the text-based browser? Anyhow, if you've got data that you want to appear in a tree you should look at the core table of contents macro: |
Hi @Jermolene, thanks for jumping in. and yes, i use lynx. pretty much because browsers as i know them make for bad knowlede trackers. tiddlywiki comes in because .tids can perfectly encapsulate knowledge .. and with the jump you've made to a no-database client-server architecture i want to port my link-pages into your wiki. so far I use a mime-type handler to control lynx and another to populate my bookmark tracker from ffox. lynx can exec shell links directly so that ffox gets told what to show. this way i can use a full screen browser on a side monitor controlled from a split terminal via keyboard and lynx. this lets me use 'link' text pages to interact with the web instead of using search or bookmarks. its like having the web in an iframe or frameset, just different. ok.. so now i want to get a M:1:M navigator going that works on dynamic javascript-free pages - without driving --rendertiddlers from the outside for every change in the generated .tids collection. tl:dr; is there a design document / api -reference that can help me understand how you're thinking about the capabilities of the current server .. does it have a full knowledge representation in memory which can --rendertiddler a single thing statically on demand? |
Hi @Adapts Just to be clear, am I right in understanding that you'd like to maintain your links as a bunch of static .tid files, and be able to run a script that generates a separate HTML file for each link tiddler, with links in between the HTML files?
TW works by loading tiddlers into memory at startup so that they are available to subsequent renderings. If you're producing static renderings, the usual approach would be to load up the wiki with the required tiddlers, and then use rendertiddler(s) to generate the required static HTML files. You should also be able to use the |
@Jermolene yes. its 20 years later and i'm still inspired by Jorn Barger's robotwisdom.com. example here: i have ~7700 links/hosts/topics/tags &snippets curated around ~80 topic pages like the above. some of the content is added by hand @ around 5 links a day. some is auto-generated from places.sqlite, .history, /usr/share/doc, org-mode & dpkg. right now it splices .tids into a tiddlywiki template and uses git-hooks/diffs to poke changes back into the fs. its all rendered into the file-system. often using empty files with extensions to indicate actions. this gives me density and speed, but not looks and hints. my project refuses to go db/rest/xhtmlrequest exclusively as i want it support ext2/file-system/html2/text-browsing on ancient devices going forward also. tl;dr: thanks for giving me a piece of your mind - and putting the server into place! i hope it was fun to see how my work wants to bridge back to the static world. i might yet have a 404_to_wayback, lynxExec, and render2ext plugin for you before the decade is out. /close |
Very interesting. I like the ability to stitch TiddlyWiki HTML files together using standard text tools; it takes the web back to the Unix command line. |
stitching is fine but the workflow of maintaining a tiddlywiki through a tiddlywiki has never been my thing. that's probably why i've lurked on your list for so long. its all about org mode now. look at these options http://orgmode.org/manual/External-links.html#External-links .. i've used less than half of them but 99% of my bookmarks land in org, with captured text that winds up curated and dumped back out to disk so that i can haz lynx execute and/or open things. see: http://lynx.isc.org/lynx2.8.6/lynx2-8-6/lynx_help/lynx_url_support.html#cgi_url (best feature ever) org-mode export isn't my cup of tea though. that's why i write the tids and jump pages into the ln -s hyperlinked file-system with the goal of having tiddly make it pretty as can be .. both static - when used with mc (lol, seriously) or a no js html 2 browser .. and dynamic through tw5. as software is becoming saner, wikis (for me) need to document the edge where fact & experience turn into learning/references. cause there are too many simple pieces to keep in mind in the time between vacations. :) |
@Jermolene ... label: "discussion" |
+1 (Very interesting. ) ... could +https://github.com/ericchiang/pup - Parsing HTML at the command line |
@dubiouscript tiddlywiki.js is/has a CLI (command line interface). Every TW edition can be built with eg: The "tiddlers" directory contains all the content as text "dot-tid" files. |
@pmario thanks |
@dubiouscript There would be a possibility to concatenate html files together. ... There is an ancient .tiddler format. |
im currently i am
...and trying a little to better understand : TiddlyWiki5/core/modules/filters.js , Macros 🤔 and perhaps [0]"mock" some similar sort of functionality 🎩 🐰 https://tiddlywiki.com/#Filters |
https://lynx.invisible-island.net/lynx_help/lynx_url_support.html#cgi_url 🕶️ |
'pologies in advance if this is only my issue.
ok, i have thousands of .tid files in a tree representing bookmarks. i'd like to use '5' to generate densly linked pages usable with lynx -- lynx controlling what i see in ffox. these should update as i dump more .tids into the tree from the outside - and when new .tids are created by node through the interface.
its not clear to me how to realize this. how can i reach enlightenment?
The text was updated successfully, but these errors were encountered: