https://groups.google.com/g/tiddlywiki/c/RIAVUIgvLh0
@Mark_S is there an outliner version of notowritey available as mentioned in the above linked post?
I think the final version does have outlining in it ?
https://marxsal.github.io/various/notowritey.html
Notowritey is one of those projects that kind of became an “also-ran”, fading away to the likes of Streams and Mohammad 's Sections.
I was thinking of a streams like outliner but based on tags like in toc macro.
Notowritey is based on tags rite. But it doesn’t have collapsible nodes like streams rite?
May be a fusion of Outlier and notowritey is needed.
Don’t the nodes collapse when you click on +/- ?
It does work. I was little confused regarding its working.
Now I can see that the level of each node can be changed in the popup menu. Any reason why you didn’t used the toc tree or tag tree structure for determining the level of each node
Toc with streams like UI. Is it possible in notowritey?
Tried it on mobile. When I tap on a node, I get the edit window and I can change its content. How do I switch back to view mode when changes are made?
There is a tick button on the right side of the editor. It may not be visible in mobile unless you scroll to the right side
That was not obvious, thank you! Slightly zooming the page also makes those buttons visible. Worth adding this to docs (which seem to be out of sync: the dialog in the wiki has a Close button which the actual wiki doesn’t have).
The whole idea to avoid the taggly-tag thing was to not pollute tag-space. When you use tags for structuring a document, you end up with lots of long tag names, many of which are only used once or twice. Imagine then if you have a tiddlywiki with multiple contained documents. Tags will be almost meaningless.
And with taggly-tagging you’re going to have cross-contamination. Think of the tiddler “Introduction”, and how you might want it in every single document. The only way that would work would be to make each a unique introduction tiddler for every tiddler (“Introduction to thermodynamics”).
The other problem with taggly-tagging is that of transferring tiddlers between TW files. With tags-as-structure you can’t simply drag and drop a tag like you can with Notowritey. You would have to use some other tool to collect all the tiddlers involved with the structure.
All of these issues could probably be resolved with other approaches (like hiding structural tags) but this seemed like the cleanest approach.
It’s been 4.5 years since I worked on NW. I kind of figured that by now everyone who wanted an outliner was using Streams.
1 Like
Right.
As an averaged wo/man I’d love to see more discussion on the (poor) consequences of structural taggery and how to obviate it.
Mark_S mentioned that separate tags lead to too many tagged nodes corresponding to a single tag, while combined tags like tag1/tag2 lead to no easy editing. In fact, this problem can be solved by using field instead of tag. The tool for this solution is locator plugin. An outline is essentially a combination of tags.
I may be guilty of having too many philosophies. Maybe I should call them “design patterns”.
With NotoWritey (a nod towards “notoriety”, an IOS app I was impressed by) I wanted:
- No javascript
- Completely self-standing
Javascript apps tend to be more brittle, needing updates when TW updates. An app without dependencies is easier to install. Also, if the dependency is javascript-based, then it also going to be brittle.
As for the locator plugin, I’m not sure where the most-recent link is. The link searcher (above) gives two sources. One of them is missing a URl. The other (mine, actually) leads to gitlab. Gitlab wants me to have a login with them before letting me see the project, which I consider unfriendly.
I could find another reference on github using Google, but it’s 4 years old, so I don’t know if it or the Gitlab reference is the most-recent.
Never ever, Trevor (whatever) you do get 101 — at least on Schopenhauer parts.
…
Self-standing
ACE is the TW aim.
Knock me down with a feather if I am wrong.