NotoWritey is a text editor and outliner for TiddlyWiki that allows you to concentrate on writing documents one section (tiddler) at a time. By breaking documents down into their components, it makes it easier to follow the Philosophy of tiddlers and to reference individual sections of your document for use in references and quote extraction.
The outliner feature means that you can "fold" away sections of your writing that you're not working on so that you can concentrate just on your current writing.
I've added the tag pill, although, as I understand it, you want to use it to add sorting. So that doesn't sound like you're using it for a text document. Eventually I should add a sorting feature to the hamburg menu similar to other outliners. It would likely sort by the contents (or first line of contents) of the associated tiddlers.
Do you mean a special saver function, or ?? You can already save a set of tiddlers by saving everything marked with the document tag plus the document tag tiddler itself. But I suspect you mean something else.
Thanks for considering this. No need to go out of your way. Once an outline is captured by any means and naming standards, we can use, read, transform it in many ways. I believe the more fundamental a solution the more adaptable it is. Also streams is offering post entry title changes. Eventualy I would like to allow your two tools share data but I will do it for myself.
A one liner info that explains how the subtiddler s are organised would help people.
You have answered questions I had not yet worked out how to ask with this tool.
Love your work
Tony
Well, we could certainly make a tool that would rename tiddlers that way, but I'm afraid that it might blow up some documents. Take TT's "Crusoe" document as a case in point -- I'm pretty sure some of those entries would have the same name, and the outcome would be unpredictable. So the tool might be available as a separate entity, but not part of the distribution, since the user will really need to understand backups and the way that tags and list fields work in case something goes awry.
Just thinking, maybe what's really needed is a different tag button that would show the first line of text.
But, for myself, just from the bottom edit bar to have an "up" arrow and a "down" arrow (I assume it would work by transposing the positions of two adjacent tiddlers in list field?) would be enough.
I.e. any place in addition to <<noto tagname>>
Question: On indent & StylingI been trying understand how the indents work in the Outliner Version. Am I right in thinking its done using styles that indent the content of the Tiddler? With styles set by the level number set in a field of each Tiddler? If so its an ingenious approach that gets round the nesting problem of <li> spanning Tiddlers (they break). Right?
I think your framework idea is nice. But, how, practically, to do it?
<h3> ``Introduction``</h3>
<<noto intro>>
<h3> ``Body``</h3>
<<noto body>>
<h3> ``Conclusion``</h3>
<<noto conclusion>>
Not sure. I got in a mess with unpopulated non-existant tag Tiddlers confusing the issue.I will check out reliability on only extant populated tag Tiddlers & report back.
<div class="nw-settings">
Possible Problem With Larger Numbers?? arose for me In testing the two "Various" editions. I cannot get either to work with the 500+ Crusoes. The wiki & browser (FF) freeze totally, restart required. This is with exactly the same data used as the prior version with the "Crusoe" test I posted that worked.
Mark. S
I have a version with dynaview wrapped around. You can see if that helps:
https://marxsal.github.io/various/notowritey-dynaview.html
Let me know!
Possible Problem With Larger Numbers?? arose for me In testing the two "Various" editions. I cannot get either to work with the 500+ Crusoes. The wiki & browser (FF) freeze totally, restart required. This is with exactly the same data used as the prior version with the "Crusoe" test I posted that worked.
Thanks!
Test in Noto Outliner ...
Test in Noto Outliner + Dynaview
Ciao MarkI'm doing some experiments with Splitology in Noto. I can't find the pre-outliner version? One with the global "splitting" off? I can find 3 versions of Outliner.
UPDATE: ignore stuff in Red. I found what I needed in a version I saved before.
It seems like for your purposes the "flat" editor is proving more useful, even though it's older and lacking some of the new editor features (join next x tiddlers, reset changes).
I'm wondering if I could rig the editor to switch between the two modes, so you could do larger, flatter documents in the plain editor but then have the outliner available when editing smaller, or more folded, documents.
16 - Allow User To Dynamically Define Split Point Regex
... I was hoping there would be more interest in either the outliner or the editor. Perhaps I misjudged the need.
Currently there is no separate project for the plain editor vs. the outliner -- it's all outliner. I probably won't be pursuing the dynaview option, since that didn't seem to improve performance.
As a reminder, the NW file can be found at:
https://marxsal.github.io/various/notowritey.html
I have being trying to replicate your buttons to take snapshots of other tiddlers as html, wikitext to clipboard and tiddler. I am however foundering.If you ever feel so inclined I would love toolbar icons to do this for any tiddler, this is a most impressive feature and it could be used in many places including streams. No pressure, and yes I am saying it again, in different words.
\define compile-h2()
<$transclude mode=block/>
\end
\define compile-w2()
<$view field="text"/>
\end
\define exportButtonFilename(baseFilename)
$baseFilename$$(extension)$
\end
\define exportButton(exportFilter:"[!is[system]sort[title]]",lingoBase,baseFilename:"tiddlers")
<span class="tc-popup-keep"><$button popup=<<qualify "$:/state/popup/export">> tooltip={{$lingoBase$Hint}} aria-label={{$lingoBase$Caption}} class=<<tv-config-toolbar-class>> selectedClass="tc-selected">
<$list filter="[<tv-config-toolbar-icons>match[yes]]">
{{$:/core/images/export-button}}
</$list>
<$list filter="[<tv-config-toolbar-text>match[yes]]">
<span class="tc-btn-text"><$text text={{$lingoBase$Caption}}/></span>
</$list>
</$button></span><$reveal state=<<qualify "$:/state/popup/export">> type="popup" position="below" animate="yes">
<div class="tc-drop-down">
<$list filter="[all[shadows+tiddlers]tag[$:/tags/Exporter]]">
<$set name="extension" value={{!!extension}}>
<$button class="tc-btn-invisible">
<$action-sendmessage $message="tm-download-file" $param=<<currentTiddler>> exportFilter="""$exportFilter$""" filename=<<exportButtonFilename """$baseFilename$""">>/>
<$action-deletetiddler $tiddler=<<qualify "$:/state/popup/export">>/>
<$transclude field="description"/>
</$button>
</$set>
</$list>
<hr/>
<$wikify text="""<<compile-h2>>""" name="compiled" output="html">
<$button class="tc-btn-invisible" message="tm-copy-to-clipboard" param=<<compiled>> >
HTML -> clip
</$button>
</$wikify>
<$wikify text={{!!text}} name="compiled">
<$vars regexp="\n{2,}" regexp2="\s{1,}\n" lf="""
"""
lf2="""
"""
>
<$vars compressed={{{[<compiled>splitregexp<regexp2>join<lf>splitregexp<regexp>join<lf>splitregexp[\n]join<lf2>]}}} >
<$button class="tc-btn-invisible" message="tm-copy-to-clipboard" param=<<compressed>> >
Text -> clipboard
</$button>
</$vars>
</$vars>
</$wikify>
</div>
</$reveal>
\end
Below is a modified
$:/core/macros/exporttiddler. Now when you click on the "export tiddler" option, you get two more choices. One copies the rendered tiddler to HTML, and the other copies to plain text.I don't think copying the all-up wikitext would be easy. There are no tools for collecting the rendered output of a tiddler as wikitext. You can get the parsetree(s), but then you'd have to turn them back into wikitext, which is likely to be non-trivial. You could capture the exact wikitext for the single tiddler, but that wouldn't be very useful.
I probably won't be pursuing the dynaview option, since that didn't seem to improve performance.
Hi TT,In order to fulfil some of the user interface requirements, like keeping track of the current reading location or creating annotations anywhere inside the text, Jeremy introduced Dynaview, then Dynannotate. In the context of ePub reading, Dynaview's aim is to reveal on demand the little chunks that have been produced at ePub parse time, along with their possible annotations. Once you have this collection of chunks (aka tiddlers), the performance, while still subject to optimisation, is not much of a worry: these chunks are not tangled nor even weaved together through any complex cross-references system. At the time Dynaview comes into play, the list of chunks is already sorted, waiting to be displayed at reading pace. That's because ePub is a much poorer and linear format than TiddlyWiki of course. Fortunately, what can do more, can do less.By the way, being able to split any ePub into chunks is probably the hardest part of the project. Not only because choosing the chunks limits can be hard, but also because styles are often used very loosely by publishers : for instance, you may find paragraphs that are expressed as <span style="font-size: 11pt;display: block;text-indent: 0pt;">The first paragraph of a section, as you have to guess.</span> because the WYSIWYG tools that helped producing the ePub are generally misleading. I spare you the table and images issues :-)Cheers,-- Xavier CazinOn Sat, Jun 27, 2020 at 6:43 PM TiddlyTweeter <Tiddly...@assays.tv> wrote:--XavierThere is interest in it growing.I think the very good PERFORMANCE aspect is particularly interesting since eBooks are large documents.Over in GG we did some tests with Dynaview but still hitting issues which the eBook version does not have. I think better understanding the eBook edition of TW will help a lot.Fingers crossed xBest wishesTTXavier wrote:Not yet ready because of some pressing redesign, but it will eventually be released as a normal plugin
https://tidbits.wiki/noto/notoGIFFORD.html
A few quick observations. Note that I work on a very high end desktop that makes it difficult to gauge performance accurately. For example, the second Noto document from TT loads in a few seconds for me. However, comparing the performance of Streams and Noto might be insightful.
What is interesting here is that Streams is much faster when the items are collapsed. Note that streams has a lot of complexity added in the way of filter runs for determining collapse state and drag and drag state, so I would expect Noto to be as fast if not faster. So are the sub levels in Noto rendered even if they are not shown?
Also crucially, the editing experience in Streams seems normal, not any slower than with just one tiddler in the stream. Even if the faster hardware is masking some of the problem, it shows that Noto is suffering far more of a performance hit when editing.
I think it is important to distinguish between rendering performance, when first opening the tiddler, versus refresh performance, when typing etc.
The slow performance in Noto reminds me of what happens when editing forces a refresh of the containing tiddler or widget. This could be as simple as a set or vars widget that is being refreshed due to a containing tiddler being changed, which refreshes all the content inside those widgets. One way to resolve this is to rework the logic for filters used to avoid such a situation.
On Tuesday, June 30, 2020 at 7:37:00 AM UTC-7, Saq Imtiaz wrote:The slow performance in Noto reminds me of what happens when editing forces a refresh of the containing tiddler or widget. This could be as simple as a set or vars widget that is being refreshed due to a containing tiddler being changed, which refreshes all the content inside those widgets. One way to resolve this is to rework the logic for filters used to avoid such a situation.
As far as I know, nothing should be changing when typing into a tiddler. If TW is refreshing with every key stroke, then that is a problem. On Gifford #2, if you open a separate tiddler by itself, it also types slow. So even if I changed the logic to work with a temporary tiddler, it doesn't seem like there would be an improvement.
My goals when making the outliner were:* Use a simple data structure (tag and list) for portability* Use only core widgets and wikitext
"GE Chapter IV" is split to ...
"GE Chapter IV 1" thru to "GE Chapter IV 49"
Each number being a paragraph number.
... backwards recursive logic is probably too much for large documents. It is possible that my two original goals are inconsistent with large-scale performance.
Hmm. Now I'm thinking that I need to restructure the logic so that it runs "forward", rather than climbing backwards.
Per request, starting a new thread here.As always, make backups because the State department will disavow all knowledge of your activities.Although I think you can start using NW now, future changes (like field names) might cause various features (like outline levels) to break. Also, there is a new "Backup Tag Order" feature under settings that you might want to use from time to time. Various operations can corrupt tag order (hopefully only by other 3rd party apps, but who knows?), so having a copy handy will make it easier to patch up in that eventuality.------------------------------------------------------------------------------------------What is NotoWritey ?
NotoWritey is a text editor and outliner for TiddlyWiki that allows you to concentrate on writing documents one section (tiddler) at a time. By breaking documents down into their components, it makes it easier to follow the Philosophy of tiddlers and to reference individual sections of your document for use in references and quote extraction.
The outliner feature means that you can "fold" away sections of your writing that you're not working on so that you can concentrate just on your current writing.
Do you mean a view mode as straight text, or a view mode that retains the outline indenting?
A reading mode would be nice, but it would probably take a bit of thought. When the "hamburg" menu disappears, a lot of the CSS is likely to need tweaking.
And, where would the toggle view button itself go?
Maybe the question is, how many distractions on screen are allowable?
Thanks!
I have a build a Generic snapshot inspired by your copy to clipboard/tiddler. It is only version 0.1 but not far from completion. If you install this on a fresh copy of noto you can see its functionality.
- If you could provide a way to make the noto view be in a read mode, I can just snapshot that read mode view.
An alternative way for you to present the copy wiki and html buttons on noto, is similar to my camera button. I tried to do it for you, but something is missing in my understanding.
You and I are on opposite day/night schedules, so I'm keeping my response short.
That looks pretty neat! I could be wrong, but I think the 2nd click is capturing an image of the snapshot. But I only played briefly.
So that mode would be basically removing the hamburger menus and the bottom settings?
An alternative way for you to present the copy wiki and html buttons on noto, is similar to my camera button. I tried to do it for you, but something is missing in my understanding.So, basically if I make the icons small enough it might pass the Gifford test? ;-)
Have fun!
TW Tones wrote:
- If you could provide a way to make the noto view be in a read mode, I can just snapshot that read mode view.
So that mode would be basically removing the hamburger menus and the bottom settings?An alternative way for you to present the copy wiki and html buttons on noto, is similar to my camera button. I tried to do it for you, but something is missing in my understanding.So, basically if I make the icons small enough it might pass the Gifford test? ;-)
Mark S. wrote:
New release! Now you can edit in a nearly distraction-free way.
I think the view/copy the wiki text version may deserve a special button, one I wonder if we could make a generic one, or is it too tool specific?