[tw5] Re: Incremental note-taking (article/discussion)

[TW Tones]

Yes, Dictate directly into tiddlywiki.com from my android works after 
hitting the mic icon on the keyboards. 

Must see now If I can get it working on my Windows desktop. Voice 
recognition without training is great now days.

I wonder if we could trigger actions like a keyboard shortcut, to open a 
tiddler as well. eg "new tiddler" or "new task", even rather than "ok 
google" try "ok tiddlywiki", or tab to move from title to text.
Unfortunately we need to say tiddly and wiki. 

Tones


On Wednesday, 21 July 2021 at 12:27:00 UTC+10 TW Tones wrote:

> Charlie,
>
> I think I may be able to dictate directly into tiddlywiki on my android. I 
> must recheck.
>
> tones
>
> On Wednesday, 21 July 2021 at 12:21:26 UTC+10 cj.v...@gmail.com wrote:
>
>> G'day Si,
>>
>> You've got me thinking about "fleeting notes", and don't think I've ever 
>> really thought about that much.
>>
>> Seeing as I've sold my soul to Google, you've got me thinking about using 
>> dictation to throw quick notes into Google Keep as a way to take fleeting 
>> notes.
>>
>> For fleeting notes, I'm thinking of more often making use of my 
>> Chromebook's dictation accessibility feature so that I can dictate my notes 
>> in Keep when it makes sense to have individual notes, or maybe just add 
>> notes in a Google Doc so that I don't have to futz around with creating a 
>> new "whatever" for each note.
>>
>> Thanks to all for the good stuff in this thread.  You've got me 
>> thinking/rethinking things.
>>
>> On Tuesday, July 20, 2021 at 2:28:40 PM UTC-3 Si wrote:
>>
>>> @Soren
>>>
>>> Interestingly your description of Random Thoughts has made me realize 
>>> that there are a couple of ways in which I already do something kind of 
>>> similar.
>>>
>>> First is just capturing fleeting notes while reading, which I later link 
>>> to evergreen notes (see here 
>>>  for 
>>> my rough workflow). While notes are in the fleeting note stage of their 
>>> life cycle they are pretty similar to RT. In fact my the only heuristic I 
>>> use for deciding what to capture is just "whatever strikes me as 
>>> interesting". Some of these notes will not relate to any larger ideas, and 
>>> I will keep them just as quotes or something, very much like RT, but the 
>>> rest will evolve and move elsewhere.
>>>
>>> The other thing I do is use Evernote as a kind of GTD inbox. This 
>>> basically is also just a way to capture fleeting thoughts, but also tasks, 
>>> links etc. I use Evernote for quick capture of ideas, then later act on 
>>> them, or copy them to a more permanent home, archiving the original note.
>>>
>>> I've only just realised that this does automatically give me a kind of 
>>> random-thoughts-list, though it's kind of a mess since my random thoughts 
>>> are split between Evernote and TiddlyWiki, and the ones in TiddlyWiki are 
>>> often not permanent.
>>>
>>> > So IMO the best option is two complementary systems (or parts of one 
>>> system) where you can move things from the quick-write one to the 
>>> flexible-thinking one when they become important.
>>>
>>> Yes this is very well-put. I feel like what I have (described above) 
>>> could be converted into such a system, but it's not quite coming together 
>>> in my mind just yet.
>>>
>>> I definitely want to move away from Evernote though. Ideally I would 
>>> like to use TiddlyWiki for both sub-systems, but as you point out the most 
>>> important thing is the ability to capture stuff with zero friction, and IMO 
>>> this is one of the major weaknesses of TiddlyWiki. I'm tempted by your 
>>> approach of using a text file. Do you have a good way to add stuff to it on 
>>> mobile?
>>> On Tuesday, 20 July 2021 at 13:04:07 UTC+1 Soren Bjornstad wrote:
>>>
 *Walt,* the thing that bugs me most about the “immutable title/ID” 
 idea is that unless your notes are also going to be immutable, the 
 *content* of a note can still change so much as to make the reference 
 not effective anymore. So I don't see much point in bothering, as long as 
 you can avoid having links break. Presumably the thing you were looking 
 for 
 won't move so far away from the updated note that you'll be unable to find 
 it, anyway (probably not more than one link away).

 It is a good point on external links breaking, though. It would be cool 
 if you could set up redirects within TW, so that you could at least have 
 an 
 incoming link to an old title go somewhere somewhat relevant. I guess you 
 could just leave the old title with a link to the new one, but without an 
 obvious way to distinguish redirect tiddlers from other tiddlers, they 
 would probably get in your way and make you think they were the “real” 
 tiddlers all the time.

 *TT,* I like your phrasing of the “category error” involved in 
 applying one notes system to everything. There are likely very few people 
 who 

[tw5] Re: Incremental note-taking (article/discussion)

[TW Tones]

Charlie,

I think I may be able to dictate directly into tiddlywiki on my android. I 
must recheck.

tones

On Wednesday, 21 July 2021 at 12:21:26 UTC+10 cj.v...@gmail.com wrote:

> G'day Si,
>
> You've got me thinking about "fleeting notes", and don't think I've ever 
> really thought about that much.
>
> Seeing as I've sold my soul to Google, you've got me thinking about using 
> dictation to throw quick notes into Google Keep as a way to take fleeting 
> notes.
>
> For fleeting notes, I'm thinking of more often making use of my 
> Chromebook's dictation accessibility feature so that I can dictate my notes 
> in Keep when it makes sense to have individual notes, or maybe just add 
> notes in a Google Doc so that I don't have to futz around with creating a 
> new "whatever" for each note.
>
> Thanks to all for the good stuff in this thread.  You've got me 
> thinking/rethinking things.
>
> On Tuesday, July 20, 2021 at 2:28:40 PM UTC-3 Si wrote:
>
>> @Soren
>>
>> Interestingly your description of Random Thoughts has made me realize 
>> that there are a couple of ways in which I already do something kind of 
>> similar.
>>
>> First is just capturing fleeting notes while reading, which I later link 
>> to evergreen notes (see here 
>>  for 
>> my rough workflow). While notes are in the fleeting note stage of their 
>> life cycle they are pretty similar to RT. In fact my the only heuristic I 
>> use for deciding what to capture is just "whatever strikes me as 
>> interesting". Some of these notes will not relate to any larger ideas, and 
>> I will keep them just as quotes or something, very much like RT, but the 
>> rest will evolve and move elsewhere.
>>
>> The other thing I do is use Evernote as a kind of GTD inbox. This 
>> basically is also just a way to capture fleeting thoughts, but also tasks, 
>> links etc. I use Evernote for quick capture of ideas, then later act on 
>> them, or copy them to a more permanent home, archiving the original note.
>>
>> I've only just realised that this does automatically give me a kind of 
>> random-thoughts-list, though it's kind of a mess since my random thoughts 
>> are split between Evernote and TiddlyWiki, and the ones in TiddlyWiki are 
>> often not permanent.
>>
>> > So IMO the best option is two complementary systems (or parts of one 
>> system) where you can move things from the quick-write one to the 
>> flexible-thinking one when they become important.
>>
>> Yes this is very well-put. I feel like what I have (described above) 
>> could be converted into such a system, but it's not quite coming together 
>> in my mind just yet.
>>
>> I definitely want to move away from Evernote though. Ideally I would like 
>> to use TiddlyWiki for both sub-systems, but as you point out the most 
>> important thing is the ability to capture stuff with zero friction, and IMO 
>> this is one of the major weaknesses of TiddlyWiki. I'm tempted by your 
>> approach of using a text file. Do you have a good way to add stuff to it on 
>> mobile?
>> On Tuesday, 20 July 2021 at 13:04:07 UTC+1 Soren Bjornstad wrote:
>>
>>> *Walt,* the thing that bugs me most about the “immutable title/ID” idea 
>>> is that unless your notes are also going to be immutable, the *content* of 
>>> a note can still change so much as to make the reference not effective 
>>> anymore. So I don't see much point in bothering, as long as you can avoid 
>>> having links break. Presumably the thing you were looking for won't move so 
>>> far away from the updated note that you'll be unable to find it, anyway 
>>> (probably not more than one link away).
>>>
>>> It is a good point on external links breaking, though. It would be cool 
>>> if you could set up redirects within TW, so that you could at least have an 
>>> incoming link to an old title go somewhere somewhat relevant. I guess you 
>>> could just leave the old title with a link to the new one, but without an 
>>> obvious way to distinguish redirect tiddlers from other tiddlers, they 
>>> would probably get in your way and make you think they were the “real” 
>>> tiddlers all the time.
>>>
>>> *TT,* I like your phrasing of the “category error” involved in applying 
>>> one notes system to everything. There are likely very few people who have 
>>> needed to work with notes of such a wide variety of types that they can 
>>> speak confidently on all of them. We've found some general patterns, but 
>>> they don't all work well for every purpose.
>>>
>>> On the topic of places where the author's mechanism would be good, I've 
>>> wondered if it would be handy for project or work diaries…almost like a 
>>> more general Git commit log. I used a custom PowerShell script called 
>>> “Daylog” at work for a year or two that worked kind of like this – you 
>>> wrote a text file with a bunch of chronological entries in it and could 
>>> chain them together into topics, responsibilities, todo items and 

[tw5] Re: Incremental note-taking (article/discussion)

[Charlie Veniot]

G'day Si,

You've got me thinking about "fleeting notes", and don't think I've ever 
really thought about that much.

Seeing as I've sold my soul to Google, you've got me thinking about using 
dictation to throw quick notes into Google Keep as a way to take fleeting 
notes.

For fleeting notes, I'm thinking of more often making use of my 
Chromebook's dictation accessibility feature so that I can dictate my notes 
in Keep when it makes sense to have individual notes, or maybe just add 
notes in a Google Doc so that I don't have to futz around with creating a 
new "whatever" for each note.

Thanks to all for the good stuff in this thread.  You've got me 
thinking/rethinking things.

On Tuesday, July 20, 2021 at 2:28:40 PM UTC-3 Si wrote:

> @Soren
>
> Interestingly your description of Random Thoughts has made me realize that 
> there are a couple of ways in which I already do something kind of similar.
>
> First is just capturing fleeting notes while reading, which I later link 
> to evergreen notes (see here 
>  for 
> my rough workflow). While notes are in the fleeting note stage of their 
> life cycle they are pretty similar to RT. In fact my the only heuristic I 
> use for deciding what to capture is just "whatever strikes me as 
> interesting". Some of these notes will not relate to any larger ideas, and 
> I will keep them just as quotes or something, very much like RT, but the 
> rest will evolve and move elsewhere.
>
> The other thing I do is use Evernote as a kind of GTD inbox. This 
> basically is also just a way to capture fleeting thoughts, but also tasks, 
> links etc. I use Evernote for quick capture of ideas, then later act on 
> them, or copy them to a more permanent home, archiving the original note.
>
> I've only just realised that this does automatically give me a kind of 
> random-thoughts-list, though it's kind of a mess since my random thoughts 
> are split between Evernote and TiddlyWiki, and the ones in TiddlyWiki are 
> often not permanent.
>
> > So IMO the best option is two complementary systems (or parts of one 
> system) where you can move things from the quick-write one to the 
> flexible-thinking one when they become important.
>
> Yes this is very well-put. I feel like what I have (described above) could 
> be converted into such a system, but it's not quite coming together in my 
> mind just yet.
>
> I definitely want to move away from Evernote though. Ideally I would like 
> to use TiddlyWiki for both sub-systems, but as you point out the most 
> important thing is the ability to capture stuff with zero friction, and IMO 
> this is one of the major weaknesses of TiddlyWiki. I'm tempted by your 
> approach of using a text file. Do you have a good way to add stuff to it on 
> mobile?
> On Tuesday, 20 July 2021 at 13:04:07 UTC+1 Soren Bjornstad wrote:
>
>> *Walt,* the thing that bugs me most about the “immutable title/ID” idea 
>> is that unless your notes are also going to be immutable, the *content* of 
>> a note can still change so much as to make the reference not effective 
>> anymore. So I don't see much point in bothering, as long as you can avoid 
>> having links break. Presumably the thing you were looking for won't move so 
>> far away from the updated note that you'll be unable to find it, anyway 
>> (probably not more than one link away).
>>
>> It is a good point on external links breaking, though. It would be cool 
>> if you could set up redirects within TW, so that you could at least have an 
>> incoming link to an old title go somewhere somewhat relevant. I guess you 
>> could just leave the old title with a link to the new one, but without an 
>> obvious way to distinguish redirect tiddlers from other tiddlers, they 
>> would probably get in your way and make you think they were the “real” 
>> tiddlers all the time.
>>
>> *TT,* I like your phrasing of the “category error” involved in applying 
>> one notes system to everything. There are likely very few people who have 
>> needed to work with notes of such a wide variety of types that they can 
>> speak confidently on all of them. We've found some general patterns, but 
>> they don't all work well for every purpose.
>>
>> On the topic of places where the author's mechanism would be good, I've 
>> wondered if it would be handy for project or work diaries…almost like a 
>> more general Git commit log. I used a custom PowerShell script called 
>> “Daylog” at work for a year or two that worked kind of like this – you 
>> wrote a text file with a bunch of chronological entries in it and could 
>> chain them together into topics, responsibilities, todo items and notes on 
>> their completion, etc.
>>
>> *Si,* I realized I never responded to your characterization of my Random 
>> Thoughts as kind of like incremental note-taking way up-thread. I think it 
>> might be a little dangerous to attribute too much intentionality to that 
>> structure, 

[tw5] Re: Building a list of tabs dynamically in a performant manner

[Soren Bjornstad]

Thanks Saq, that view is super useful and I never knew it existed!

Armed with that information, I spent most of this evening tinkering on 
improving some of the other things that have been slowing my wiki down, 
including adding an Idea tag so I don't have to define it as the negation 
of a dozen other tags and replacing TiddlyTables with a similar HTML table 
that needs fewer filters, macros, and transclusions in the most critical 
paths. (More work needs to be done to bring the rest of the Reference 
Explorer in line and refactor it to catch it up with a bunch of other 
changes I've made recently.)

The tabs filter discussed above was and remains the #1 contributor to 
filter processing time when clicking around the wiki, often something like 
30% of the total time, so I'm still interested in suggestions others may 
have for improving that. I didn't want to publish the wiki in its present 
state previously since it was so slow it would be difficult for people to 
use, but I've ameliorated that enough that I am now comfortable 
republishing it. As mentioned in my previous post, you can start looking at 
$:/sib/refexplorer/ReferenceExplorer, but now it is a working example 
rather than something you would have to tweak into a working example by 
yourself.

On Tuesday, July 20, 2021 at 9:29:49 AM UTC-5 saq.i...@gmail.com wrote:

> @Soren I recommend enabling performance instrumentation and checking to 
> see which filter runs are the culprits.
>
>
> https://tiddlywiki.com/#%24%3A%2Fconfig%2FPerformance%2FInstrumentation:%24%3A%2Fconfig%2FPerformance%2FInstrumentation%20%5B%5BPerformance%20Instrumentation%5D%5D
>
> Note that you need to enable it by setting the config tiddler to "yes", 
> then save and reload.
>
> Also suggest posting a public wiki where the issue (and the condition 
> filters) can be seen to facilitate debugging.
> On Tuesday, July 20, 2021 at 4:05:15 PM UTC+2 Soren Bjornstad wrote:
>
>> Important note, the condition fields aren't defined in the current public 
>> version, so you'd have to add them in to get a working test.
>>
>> On Tuesday, July 20, 2021 at 9:03:42 AM UTC-5 Soren Bjornstad wrote:
>>
>>> Tones,
>>>
>>> :filter was my first thought, but I couldn't figure out how the data 
>>> would flow through it. Perhaps I was missing something, looking forward to 
>>> seeing your version.
>>>
>>> If it helps to see the context, have a peek at 
>>> https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2Frefexplorer%2FReferenceExplorer.
>>>  
>>> The snippet above (or a replacement) would go inside the ref-explorer macro 
>>> definition.
>>>
>>>
>>> On Tuesday, July 20, 2021 at 8:07:09 AM UTC-5 TW Tones wrote:
>>>
 Soren,

 Its late here but I have done something similar in the past without a 
 performance hit, and will try and create a solution tomorrow, However I 
 think the answer best answer may be through the use of a filter run as in 
 5.3.23+ however I am sure I succeeded in something similar a few versions 
 ago.

 No need for reduce and accumulators I think.

 Regards
 Tones

 On Tuesday, 20 July 2021 at 13:09:18 UTC+10 Soren Bjornstad wrote:

> Hi all,
>
> I want to determine what tabs of the Reference Explorer in my 
> Zettelkasten to show on a template, such that if there aren't any results 
> on that tab, the tab doesn't appear at all. The results of the tab are 
> produced based on a filter (of course), so I figured I would also 
> determine 
> whether the tab appears by running a filter. The filter is stored in a 
> field in the tab tiddler.
>
> That is, I have a series of tiddlers with a certain tag (say *Tab*), 
> and each of these tiddlers contains a filter in some field (say 
> *condition*). For each Tiddler tagged Tab, if and only if the filter 
> Tiddler!!condition, run with the current tiddler as input, has more than 
> zero results, I want to display the tab.
>
> I came up with the following:
>
> <$set name="tabList" value={{{ [tag[Tab]] 
> :reduce[subfilter{!!condition}thenaddprefix[
>  
> ]addprefix] }}}>
> <$macrocall $name="tabs" tabsList=<>/>
> 
>
> This produces the correct result (well, as long as there are no spaces 
> in the titles of the tiddlers tagged *Tab*; I'm OK assuming that 
> since there indeed aren't any). The problem is that it is horrendously 
> slow 
> to run all these filters. On my dev machine it is tolerable, but this is 
> a 
> machine specced for serious processing power. On my MacBook Air it now 
> takes 1–2 seconds to open a new tiddler, even without anything currently 
> open!
>
> Probably I am just asking TW to do too much on the fly here, but 
> before I start rethinking the project too hard, can anyone think of 
> obvious 
> optimizations I might be missing here? The filters involved are 
> moderately 
> 

[tw5] Re: Two problems with macro: displaying and refreshing

[TW Tones]

Thanks for sharing your result back here Misterel, it is great community 
participation.

Yup, TiddlyWiki is so awesome.

With the name Misterel, makes me think of thew Mistrals and "Pas de" in 
your code I imagine you may be in the south of France? We have friends in a 
place called Castries not far from Montpelier, it was there I saw the 
result of the Mistrals (winds) in their back yard with every tree leaning 
away from the wind. Strangely whilst their house was a modern Spanish 
style, their pool and barbeque area was quite similar to nice homes here in 
Australia.

We miss France terribly, and can't wait to visit again. My partner 
Isabelle's mother remains in Paris and we have family all over 
France/Portugal.

Tones/Tony

On Wednesday, 21 July 2021 at 04:56:03 UTC+10 Misterel85 wrote:

> Hi everyone,
>
> With Springer's help and and bit of googling around, I finally found a 
> (basic) working solution. Yay!
> It is much simpler to use a ViewTemplate instead of a macro and it should 
> satisfy most of my needs.
>
> Should it be useful to anybody, here is the code I used in the 
> ViewTemplate to replace the macro:
>
> ```
> <$list 
> filter="[all[current]field:tiddler-type[exercice]field:displaysource[yes]]">
> <$set name="fieldCount" filter="[all[current]fields[]prefix[ref_]count[]]">
> <$text text={{{ [match[0]then[Pas de ]else] }}} />
> <$text text={{{ [!match[1]then[sources :]else[source :]]  }}} 
> />
> 
> <$list filter="[all[current]fields[]prefix[ref_]sort[title]]" 
> variable="fieldName">
> @@color:grey; 
> 
> <$transclude field=<>/>
> @@
> 
> 
> 
> ```
> I can't believe how great and versatile TiddlyWiki is!!
>
> Regards
>
>
> Le mardi 20 juillet 2021 à 18:35:59 UTC+2, Misterel85 a écrit :
>
>> Springer,
>> Thanks a lot for taking the time to reply and for your help.
>>
>> You're exactly right: I'd like my macro to count (and then display one 
>> summary line for) each of the fields that start with ref_ in every tiddler 
>> in the story river.
>>
>> I have tried your solution to add `all[current]` in my macro but 
>> unfortunately it doesn't work.
>> Actually because the macro is in its own tiddler, I think `all[current]` 
>> tries to find the ref_ fields in the macro's tiddler. But I may be wrong.
>>
>> Grok TiddlyWiki is a great tool to learn, but I haven't finished reading 
>> it, and it needs time to figure out all the intricacies of (TW) programming 
>> when your coding knowledge amounts to next to nothing.
>>
>> Regards
>>
>>
>> Le mardi 20 juillet 2021 à 17:32:35 UTC+2, springer a écrit :
>>
>>> Misterel,
>>>
>>> I am *not* the expert; others could probably write the code you need in 
>>> 60 seconds. But since nobody else has answered, and understanding your task 
>>> and its problems demands some time and attention, I'll offer one nudge to 
>>> start...
>>>
>>> It seems you want your macro to count (and then display one summary line 
>>> for) each of the CURRENT tiddler's fields that start with ref_ -- Is that 
>>> correct?
>>>
>>> Instead, your macro is counting (and then displaying one summary line 
>>> for) every field in your whole wiki that begins with ref_
>>>
>>> Try pasting your code (with the variable filled in) and this alternate 
>>> code, into your Exercice1 tiddler. Your code yields 5, because the whole 
>>> project had five ref_ fields; but beginning your filter with 
>>> [all[current] gets you the number you want.
>>>
>>> First segment of your existing macro's code (specifying the prefix):
>>> <$set name="fieldCount" filter="[fields[]prefix[ref_]count[]]">
>>> <$text text={{{ [match[0]then[Pas de ]else] }}} 
>>> />
>>> <$text text={{{ [!match[1]then[sources :]else[source :]] }}} 
>>> />
>>> 
>>>
>>> Better:
>>> <$set name="fieldCount" 
>>> filter="[all[current]fields[]prefix[ref_]count[]]">
>>> <$text text={{{ [match[0]then[Pas de ]else] }}} 
>>> />
>>> <$text text={{{ [!match[1]then[sources :]else[source :]]  
>>> }}} />
>>> 
>>>
>>> All I'm doing here is the technique in https://groktiddlywiki.com/read/
>>>
>>> That is: breaking down a complex problem into smaller bits, and getting 
>>> your macro to count right *before* trying to set it up in the ViewTemplate 
>>> with an additional variable for the prefix and an additional condition for 
>>> displaysource[yes].  
>>>
>>> Alas, I need to switch to other tasks, but I hope you're on the road to 
>>> getting the behavior you need.
>>>
>>> -Springer
>>>
>>> On Monday, July 19, 2021 at 11:08:53 AM UTC-4 Misterel85 wrote:
>>>
 Hi,
 I'm back to work on a TiddlyWiki to manage my collection of drama 
 exercises, but I came across 2 problems with displaying their sources and 
 refreshing that display.

 Problem #1:

 My 'exercises' tiddlers all refer to a 'SourceDisplay' macro to show 
 the sources.
 If I use a field to trigger the macro to show or hide the sources, they 
 appear in 'Exercise1' tiddler, but not in 'Exercise2'. If I paste 
 <> in the text field of each of the 

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Frédéric Demers]

@saq
quick question: am trying to package my addon, am a bit of a newbie
unfortunately.
is it possible we need to modify this line (bold insert)
<$list filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]"
variable="btnTiddler">

in $:/plugins/sq/streams/nodes-list-template ?
otherwise, it feels like my new button does not take when it is contained
within a plugineven with the $:/tags/streams/root-buttons tag

thanks much...

On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  wrote:

> a quick update to everyone;
>
> I am making steady progress on packaging this merging solution, hoping to
> release as a Streams plugin addon. I have repurposed the button from
> https://szen.io/stream/. I now have it also working as a Streams context
> menu, with keyboard shortcuts, and it can export sub-trees correctly by
> adjusting the depth levels of the bulleted/numbered lists.
>
> A few ideas I am going to try to roll in and release a beta by the end of
> this week
>
> Cheers
>
> On Sat, 17 Jul 2021 at 09:06, Frédéric Demers 
> wrote:
>
>> with capture:
>>
>> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers 
>> wrote:
>>
>>> nevermind, I think I solved it at least, significant progress
>>>
>>> here's the wikitext for the challenging nodes; renders pretty well:
>>>
>>> * 
>>>
>>> ''Streams'' uses the following tiddler fields to maintain the structure
>>> of a stream:
>>>
>>> * each node tiddler has a field `stream-type`
>>> * each node that has children, contains their titles in a list in the
>>> field `stream-list`
>>> * each node that has a parent, contains the parent's title in the field
>>> `parent`
>>>
>>> ''You can manipulate these tiddlers just as you would any other
>>> tiddlers, with filters and list and action widgets''
>>>
>>> 
>>> * To make it easier to work with Streams tiddlers and their nodes, two
>>> filters have been introduced. See [[Streams 0.2 improvements/Filters]]
>>> * 
>>>
>>> This is an example of a button that can export the content of the nodes
>>> of a tiddler whose title is in the variable `myTiddler` and save the
>>> combined text to a single tiddler:
>>>
>>> ```
>>> <$button> save to a single tiddler
>>> <$vars lb="
>>>
>>> ">
>>> <$action-setfield $tiddler="report" text={{{
>>> [get-stream-nodes[]]
>>>  :reduce[get[text]addprefixaddprefix] }}}/>
>>> 
>>> 
>>> ```
>>> Note that this disregards the node hierarchy.
>>> * 
>>>
>>> Similarly to export the combined text of the nodes as HTML you can use
>>> the `<$wikify>` widget:
>>>
>>> ```
>>> <$button> export as HTML
>>> <$wikify name="text" text="""<$list
>>> filter="[get-stream-nodes[]]">
>>> <$transclude mode=block/>
>>> """ output="html">
>>> <$action-setfield $tiddler="report" text=<>/>
>>> 
>>> 
>>> ```
>>>
>>> 
>>> * 
>>>
>>> Here is an example of a macro that can be used to export a stream using
>>> a custom HTML structure:
>>>
>>> ```
>>> \define print-row()
>>> \whitespace trim
>>> <$(innerTag)$>{{!!text}}
>>> <$list filter="[has[stream-list]]" variable="_NULL">
>>> <$(outerTag)$>
>>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>>> <>
>>> 
>>> 
>>> 
>>> 
>>> \end
>>>
>>> \define print-stream()
>>> \whitespace trim
>>> <$(outerTag)$>
>>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>>> <>
>>> 
>>> 
>>> \end
>>>
>>> \define export-stream(tiddler:"" outerTag:"article" innerTag:"section")
>>> \whitespace trim
>>> <$vars outerTag="$outerTag$" innerTag="$innerTag$"
>>> currentTiddler="$tiddler$">
>>> <>
>>> 
>>> \end
>>>
>>> ```
>>>
>>> Try the following:
>>>
>>> * `<>` to export using article and
>>> section tags
>>> * `<>` to export
>>> as a list in HTML
>>>
>>> If you need a copy to clipboard button it would look something like this:
>>>
>>> ```
>>> <$button>
>>> <$wikify name="stream-html" text=<>
>>> output="html" >
>>> <$action-sendmessage $message="tm-copy-to-clipboard"
>>> $param=<>/>
>>> 
>>> Copy stream to clipboard as HTML
>>> 
>>> ```
>>>
>>> Similarly you can write recursive macros to output as just flat text
>>> (with no structure or hierarchy) or wiki text list syntax (assuming you
>>> have no multi-line content).
>>>
>>> On Sat, 17 Jul 2021 at 09:01, Saq Imtiaz  wrote:
>>>
 @fred


> I noticed my solution does not work so well for complex node content,
> as those in:
> https://saqimtiaz.github.io/streams/#Working%20with%20streams%20tiddlers
>
>
> The reason is that wrapping in  tags mangles them badly; I tried
> a few alternatives (, more white space, ..), no success yet. Any
> suggestions?
>

 This is actually the real challenge and why there currently isn't a
 default export option from Streams. Depending on the nature of the content,
 it seems difficult to generalize a single export format that will work and
 one of the common pitfalls is to think of Streams nodes as a list,*
 which they are not.*

 A stream node is a tiddler which can contain any kind of content, and
 not all kinds of content can 

Re: [tw5] Export to html while excluding some transclusions

[Soren Bjornstad]

For my Zettelkasten, I create a separate wiki every time I build, 
containing only the tiddlers that are currently public. Transcluding a 
tiddler that doesn't exist is invisible in the output in TW in most cases, 
so while you can see in the wikitext that something is referenced, the 
content is left out within the public wiki. My main build output is a 
single-file TiddlyWiki, but you could use this as the first step for a 
static site, too.

 I discussed the whole system in my demo back in April 
.

On Tuesday, July 20, 2021 at 9:12:28 AM UTC-5 davou...@gmail.com wrote:

> Jeremy offered a solution that works as advertised - thank you Jeremy. 
> Unfortunately there a 2 pain points with this method and was wondering if 
> there are solutions for those. 
>
> 1. Over time I want to make some private tiddlers public. Is there 
> currently a means to easily move a tiddler from one wiki to another (in my 
> case both run under node on same machine)? If not, could I create a plugin 
> to do so? What is the basic algorithm or basic things to keep in mind? Is 
> it simply a matter of moving the tiddler file from one directory to another?
>
> 2. In order to see any changes made in a tiddler in the public wiki it 
> appears I need to restart the private wiki and refresh the browser if 
> browser is viewing the private wiki. If this is the case, is there a way to 
> at least remotely restart server? In my case, I interact via browser with 
> my wikis from one machine while the wikis run on another machine. Both are 
> behind a firewall and I don't expose either of my wikis to the public. So 
> I'm not too concerned about someone externally restarting my wikis. I could 
> remote desktop, but for reasons, if an alternative exists I'd like to know. 
> I know first-world problems but if this ability already exists, I'd like to 
> take advantage of it.
>
> A completely different alternative solution occurred to me: create a 
> custom command like render but one which doesn't transclude if tiddler to 
> transclude is not public. But looking at the code, I'm not sure I want to 
> go down that rabbit hole.
>
> Thanks.
> On Monday, May 3, 2021 at 12:55:10 PM UTC-4 jeremy...@gmail.com wrote:
>
>> Hi Louis
>>
>> If you're running under Node.js, you could setup two separate wiki 
>> folders, one "private" and one "public". Then the private wiki can use the 
>> "includeWiki" property to include the tiddlers from the public wiki. When 
>> exporting the public content, you'd reference the public wiki, thus 
>> excluding all the private content.
>>
>> Best wishes
>>
>> Jeremy
>> 
>>
>> Hi, 
>>
>> I'm wondering if the following is possible either in the base wiki or 
>> with a plugin.
>>
>> Say I have a tag 'Public'. I want to export all tiddlers and only those 
>> tiddlers with the tag 'Public'. Simple enough with filter [tag[Public]]. 
>> But say some of the 'Public' tiddlers have 
>> transclusions of tiddlers that do not have the 'Public' tag. In my html 
>> output I don't want the content of the transclusions included unless 
>> transclused tiddler also has the 'Public' tag.
>>
>> Thanks
>>
>> Example
>> *topic1 with tag Public*
>> start
>>
>> {{topic2}}
>>
>> {{topic3}}
>>
>> end
>>
>> *topic2 without tag Public*
>> private
>>
>> *topic3 with tag Public*
>> show me
>>
>> *the desired html output*
>> start
>>
>> show me 
>>
>> end
>>
>> -- 
>> 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/0ddc64cc-58f3-497c-a514-d4d39292b1b9n%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0a7e7725-1b3d-49d0-98a6-18537e12b03bn%40googlegroups.com.

[tw5] Re: Incremental note-taking (article/discussion)

[Soren Bjornstad]

On Tuesday, July 20, 2021 at 12:28:40 PM UTC-5 Si wrote:

> Ideally I would like to use TiddlyWiki for both sub-systems, but as you 
> point out the most important thing is the ability to capture stuff with 
> zero friction, and IMO this is one of the major weaknesses of TiddlyWiki. 
> I'm tempted by your approach of using a text file. Do you have a good way 
> to add stuff to it on mobile?
>
I still use paper for this -- I carry a little pocket notebook with me next 
to my phone and write down anything I need to save in there, then every 
couple of days I transcribe it. It's still faster and less frustrating for 
me than trying to open an app and type something in with two fingers.

You could look at something like Simplenote  for 
cloud-hosted and mobile-accessible text files.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/116de2b8-0a19-4e38-82a5-f7c061898526n%40googlegroups.com.

[tw5] Re: OpenAPI Explorer in TW

[ludwa6]

Sorry @Mario, i forgot: to browse an instance of the v2 farmOS API, here's 
mine: https://vdl.farmos.dev/api/ 

Viewed in Firefox (tho not in Chrome or Safari, which fail to render this 
in human-readable form), one can pull out links to the available endponts, 
and then use those to browse details, tho not easily. 

Is this all the info that would be needed to build a UI with filters and 
dropdowns, etc. -like that TiddlyWeb API Explorer you shared?

/walt


On Tuesday, July 20, 2021 at 7:11:09 PM UTC+1 PMario wrote:

> Hi, 
>
> >SO @Mario: do you think as i do that an API Explorer in TW could be a 
> useful tool in this pursuit? and, if so, then is it something that might be 
> built w/ relative ease? 
>
> I think, it would be a useful tool. .. The problem creating it from 
> scratch with TW is, that it would be like "reverse engineering".  The 
> programmers that create the API should be able to create an API explorer 
> with ease. .. It may be a possible "side-product" of the API unit tests ... 
> (just a guess!)
>
> From my point of view the farmOS.py library is a user-level library 
> already. It abstracts the API - URL building process away, so imo it can't 
> be used to create an API explorer. 
>
> The info needed for an API explorer would come from 
> https://github.com/farmOS/farmOS/blob/2.x/docs/development/api/changes.md#resource-endpoints
>  
> ... 
>
> An API explorer would know the different "entity-type" and "bundle" names 
> and replace them with some dropdowns to build a valid URL eg: 
> /api/[entity-type]/[bundle]  would result in /api/log/activity and so on. 
>
> The different possible schemas may be seen at: 
> https://github.com/farmOS/farmOS/blob/2.x/docs/development/api/index.md 
> ... Since there is no link to a demo API, I don't know how this looks like. 
>
> -mario
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b1e6a937-e6e3-45c1-b4b1-1a1a3e9498aan%40googlegroups.com.

[tw5] Re: Two problems with macro: displaying and refreshing

[Misterel85]

Hi everyone,

With Springer's help and and bit of googling around, I finally found a 
(basic) working solution. Yay!
It is much simpler to use a ViewTemplate instead of a macro and it should 
satisfy most of my needs.

Should it be useful to anybody, here is the code I used in the ViewTemplate 
to replace the macro:

```
<$list 
filter="[all[current]field:tiddler-type[exercice]field:displaysource[yes]]">
<$set name="fieldCount" filter="[all[current]fields[]prefix[ref_]count[]]">
<$text text={{{ [match[0]then[Pas de ]else] }}} />
<$text text={{{ [!match[1]then[sources :]else[source :]]  }}} />

<$list filter="[all[current]fields[]prefix[ref_]sort[title]]" 
variable="fieldName">
@@color:grey; 

<$transclude field=<>/>
@@



```
I can't believe how great and versatile TiddlyWiki is!!

Regards


Le mardi 20 juillet 2021 à 18:35:59 UTC+2, Misterel85 a écrit :

> Springer,
> Thanks a lot for taking the time to reply and for your help.
>
> You're exactly right: I'd like my macro to count (and then display one 
> summary line for) each of the fields that start with ref_ in every tiddler 
> in the story river.
>
> I have tried your solution to add `all[current]` in my macro but 
> unfortunately it doesn't work.
> Actually because the macro is in its own tiddler, I think `all[current]` 
> tries to find the ref_ fields in the macro's tiddler. But I may be wrong.
>
> Grok TiddlyWiki is a great tool to learn, but I haven't finished reading 
> it, and it needs time to figure out all the intricacies of (TW) programming 
> when your coding knowledge amounts to next to nothing.
>
> Regards
>
>
> Le mardi 20 juillet 2021 à 17:32:35 UTC+2, springer a écrit :
>
>> Misterel,
>>
>> I am *not* the expert; others could probably write the code you need in 
>> 60 seconds. But since nobody else has answered, and understanding your task 
>> and its problems demands some time and attention, I'll offer one nudge to 
>> start...
>>
>> It seems you want your macro to count (and then display one summary line 
>> for) each of the CURRENT tiddler's fields that start with ref_ -- Is that 
>> correct?
>>
>> Instead, your macro is counting (and then displaying one summary line 
>> for) every field in your whole wiki that begins with ref_
>>
>> Try pasting your code (with the variable filled in) and this alternate 
>> code, into your Exercice1 tiddler. Your code yields 5, because the whole 
>> project had five ref_ fields; but beginning your filter with 
>> [all[current] gets you the number you want.
>>
>> First segment of your existing macro's code (specifying the prefix):
>> <$set name="fieldCount" filter="[fields[]prefix[ref_]count[]]">
>> <$text text={{{ [match[0]then[Pas de ]else] }}} />
>> <$text text={{{ [!match[1]then[sources :]else[source :]] }}} 
>> />
>> 
>>
>> Better:
>> <$set name="fieldCount" 
>> filter="[all[current]fields[]prefix[ref_]count[]]">
>> <$text text={{{ [match[0]then[Pas de ]else] }}} />
>> <$text text={{{ [!match[1]then[sources :]else[source :]]  }}} 
>> />
>> 
>>
>> All I'm doing here is the technique in https://groktiddlywiki.com/read/
>>
>> That is: breaking down a complex problem into smaller bits, and getting 
>> your macro to count right *before* trying to set it up in the ViewTemplate 
>> with an additional variable for the prefix and an additional condition for 
>> displaysource[yes].  
>>
>> Alas, I need to switch to other tasks, but I hope you're on the road to 
>> getting the behavior you need.
>>
>> -Springer
>>
>> On Monday, July 19, 2021 at 11:08:53 AM UTC-4 Misterel85 wrote:
>>
>>> Hi,
>>> I'm back to work on a TiddlyWiki to manage my collection of drama 
>>> exercises, but I came across 2 problems with displaying their sources and 
>>> refreshing that display.
>>>
>>> Problem #1:
>>>
>>> My 'exercises' tiddlers all refer to a 'SourceDisplay' macro to show the 
>>> sources.
>>> If I use a field to trigger the macro to show or hide the sources, they 
>>> appear in 'Exercise1' tiddler, but not in 'Exercise2'. If I paste 
>>> <> in the text field of each of the 
>>> Exercise tiddlers, it works fine.
>>> I suppose something like 'qualify' might solve the trick, but I don't 
>>> know how to use it. Perhaps any of you has a better solution to suggest 
>>> anyway, but I can make do with copying-pasting the macro call.
>>>
>>> Problem #2 (more serious to me):
>>> I changed the contents and title of tiddler "source1" to a more 
>>> realistic name ('Dramaction' here) and contents and updated the the fields 
>>> accordingly.
>>>
>>> I made 4 dummy source tiddlers. When I deleted the 'ref_source1' field 
>>> in 'Exercise1' and replaced it with a 'ref_dramaction' field, I also 
>>> noticed that there were now 4 sources in the list instead of 3. One line is 
>>> blank, which I suppose is the ghost of 'source1', without any data, of 
>>> course, since that content doesn't exist any more. It's as if old 'source1' 
>>> data wasn't purged, or TW still expected that content to exist alongside 
>>> the new 'dramaction' 

[tw5] Re: OpenAPI Explorer in TW

[PMario]

Hi, 

>SO @Mario: do you think as i do that an API Explorer in TW could be a 
useful tool in this pursuit? and, if so, then is it something that might be 
built w/ relative ease? 

I think, it would be a useful tool. .. The problem creating it from scratch 
with TW is, that it would be like "reverse engineering".  The programmers 
that create the API should be able to create an API explorer with ease. .. 
It may be a possible "side-product" of the API unit tests ... (just a 
guess!)

>From my point of view the farmOS.py library is a user-level library 
already. It abstracts the API - URL building process away, so imo it can't 
be used to create an API explorer. 

The info needed for an API explorer would come from 
https://github.com/farmOS/farmOS/blob/2.x/docs/development/api/changes.md#resource-endpoints
 
... 

An API explorer would know the different "entity-type" and "bundle" names 
and replace them with some dropdowns to build a valid URL eg: 
/api/[entity-type]/[bundle]  would result in /api/log/activity and so on. 

The different possible schemas may be seen at: 
https://github.com/farmOS/farmOS/blob/2.x/docs/development/api/index.md ... 
Since there is no link to a demo API, I don't know how this looks like. 

-mario

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f2d1347d-3bb6-48e0-821c-b07d597f356dn%40googlegroups.com.

[tw5] tidders created this week

[paulgilbert2000]

Hi ,

is it possible to list all tiddlers created this week, that would include 
past tiddlers  created 
yesterday"Monday" , tiddlers created today " Tuesday". and future tiddlers 
to be created in Wednesday ,Thursday and Friday.

i know i can use something like this 
{{{[all[tiddlers]] :filter[get[created]compare:date:gt[20210719]]}}}

but then the date i am comparing against is static, and will need to be 
changed manually every week

I really like it , if only the date can be replaced with some kind of 
dynamic value that is defined as the first day of the current week

i know there is the days operator IE , [days[-1]]  , but then again its not 
what i want and will also need manual adjustment every day

is there any easy way around this ?

thanks in advance

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ded297d0-342b-4304-9a1a-64a5d89c604dn%40googlegroups.com.

[tw5] Re: Incremental note-taking (article/discussion)

[Si]

 

@Soren

Interestingly your description of Random Thoughts has made me realize that 
there are a couple of ways in which I already do something kind of similar.

First is just capturing fleeting notes while reading, which I later link to 
evergreen notes (see here 
 for 
my rough workflow). While notes are in the fleeting note stage of their 
life cycle they are pretty similar to RT. In fact my the only heuristic I 
use for deciding what to capture is just "whatever strikes me as 
interesting". Some of these notes will not relate to any larger ideas, and 
I will keep them just as quotes or something, very much like RT, but the 
rest will evolve and move elsewhere.

The other thing I do is use Evernote as a kind of GTD inbox. This basically 
is also just a way to capture fleeting thoughts, but also tasks, links etc. 
I use Evernote for quick capture of ideas, then later act on them, or copy 
them to a more permanent home, archiving the original note.

I've only just realised that this does automatically give me a kind of 
random-thoughts-list, though it's kind of a mess since my random thoughts 
are split between Evernote and TiddlyWiki, and the ones in TiddlyWiki are 
often not permanent.

> So IMO the best option is two complementary systems (or parts of one 
system) where you can move things from the quick-write one to the 
flexible-thinking one when they become important.

Yes this is very well-put. I feel like what I have (described above) could 
be converted into such a system, but it's not quite coming together in my 
mind just yet.

I definitely want to move away from Evernote though. Ideally I would like 
to use TiddlyWiki for both sub-systems, but as you point out the most 
important thing is the ability to capture stuff with zero friction, and IMO 
this is one of the major weaknesses of TiddlyWiki. I'm tempted by your 
approach of using a text file. Do you have a good way to add stuff to it on 
mobile?
On Tuesday, 20 July 2021 at 13:04:07 UTC+1 Soren Bjornstad wrote:

> *Walt,* the thing that bugs me most about the “immutable title/ID” idea 
> is that unless your notes are also going to be immutable, the *content* of 
> a note can still change so much as to make the reference not effective 
> anymore. So I don't see much point in bothering, as long as you can avoid 
> having links break. Presumably the thing you were looking for won't move so 
> far away from the updated note that you'll be unable to find it, anyway 
> (probably not more than one link away).
>
> It is a good point on external links breaking, though. It would be cool if 
> you could set up redirects within TW, so that you could at least have an 
> incoming link to an old title go somewhere somewhat relevant. I guess you 
> could just leave the old title with a link to the new one, but without an 
> obvious way to distinguish redirect tiddlers from other tiddlers, they 
> would probably get in your way and make you think they were the “real” 
> tiddlers all the time.
>
> *TT,* I like your phrasing of the “category error” involved in applying 
> one notes system to everything. There are likely very few people who have 
> needed to work with notes of such a wide variety of types that they can 
> speak confidently on all of them. We've found some general patterns, but 
> they don't all work well for every purpose.
>
> On the topic of places where the author's mechanism would be good, I've 
> wondered if it would be handy for project or work diaries…almost like a 
> more general Git commit log. I used a custom PowerShell script called 
> “Daylog” at work for a year or two that worked kind of like this – you 
> wrote a text file with a bunch of chronological entries in it and could 
> chain them together into topics, responsibilities, todo items and notes on 
> their completion, etc.
>
> *Si,* I realized I never responded to your characterization of my Random 
> Thoughts as kind of like incremental note-taking way up-thread. I think it 
> might be a little dangerous to attribute too much intentionality to that 
> structure, because I started it when I was 14 years old (!) and 
> chronological bits was just the obvious structure to put it in since I 
> didn't really know much about notes at the time. But that said, it has 
> turned out to work well over the following 11+ years, at least once I went 
> back and added ID numbers to it so I could cross-reference things, so it 
> can't be too bad of a system. Perhaps the main difference between it and 
> evergreen notes is that it's optimized for ease of insertion, while 
> evergreen notes are optimized for ease of later use and flexibility of 
> thinking. Those are, I think, fundamentally irreconcilable; you can reduce 
> the weaknesses of one system in the opposite area, but nothing is ever 
> going to be great at both. So IMO the best option is two complementary 
> systems (or parts of one system) where you can move 

[tw5] Re: Two problems with macro: displaying and refreshing

[Misterel85]

Springer,
Thanks a lot for taking the time to reply and for your help.

You're exactly right: I'd like my macro to count (and then display one 
summary line for) each of the fields that start with ref_ in every tiddler 
in the story river.

I have tried your solution to add `all[current]` in my macro but 
unfortunately it doesn't work.
Actually because the macro is in its own tiddler, I think `all[current]` 
tries to find the ref_ fields in the macro's tiddler. But I may be wrong.

Grok TiddlyWiki is a great tool to learn, but I haven't finished reading 
it, and it needs time to figure out all the intricacies of (TW) programming 
when your coding knowledge amounts to next to nothing.

Regards


Le mardi 20 juillet 2021 à 17:32:35 UTC+2, springer a écrit :

> Misterel,
>
> I am *not* the expert; others could probably write the code you need in 60 
> seconds. But since nobody else has answered, and understanding your task 
> and its problems demands some time and attention, I'll offer one nudge to 
> start...
>
> It seems you want your macro to count (and then display one summary line 
> for) each of the CURRENT tiddler's fields that start with ref_ -- Is that 
> correct?
>
> Instead, your macro is counting (and then displaying one summary line for) 
> every field in your whole wiki that begins with ref_
>
> Try pasting your code (with the variable filled in) and this alternate 
> code, into your Exercice1 tiddler. Your code yields 5, because the whole 
> project had five ref_ fields; but beginning your filter with [all[current] 
> gets you the number you want.
>
> First segment of your existing macro's code (specifying the prefix):
> <$set name="fieldCount" filter="[fields[]prefix[ref_]count[]]">
> <$text text={{{ [match[0]then[Pas de ]else] }}} />
> <$text text={{{ [!match[1]then[sources :]else[source :]] }}} />
> 
>
> Better:
> <$set name="fieldCount" filter="[all[current]fields[]prefix[ref_]count[]]">
> <$text text={{{ [match[0]then[Pas de ]else] }}} />
> <$text text={{{ [!match[1]then[sources :]else[source :]]  }}} 
> />
> 
>
> All I'm doing here is the technique in https://groktiddlywiki.com/read/
>
> That is: breaking down a complex problem into smaller bits, and getting 
> your macro to count right *before* trying to set it up in the ViewTemplate 
> with an additional variable for the prefix and an additional condition for 
> displaysource[yes].  
>
> Alas, I need to switch to other tasks, but I hope you're on the road to 
> getting the behavior you need.
>
> -Springer
>
> On Monday, July 19, 2021 at 11:08:53 AM UTC-4 Misterel85 wrote:
>
>> Hi,
>> I'm back to work on a TiddlyWiki to manage my collection of drama 
>> exercises, but I came across 2 problems with displaying their sources and 
>> refreshing that display.
>>
>> Problem #1:
>>
>> My 'exercises' tiddlers all refer to a 'SourceDisplay' macro to show the 
>> sources.
>> If I use a field to trigger the macro to show or hide the sources, they 
>> appear in 'Exercise1' tiddler, but not in 'Exercise2'. If I paste 
>> <> in the text field of each of the Exercise 
>> tiddlers, it works fine.
>> I suppose something like 'qualify' might solve the trick, but I don't 
>> know how to use it. Perhaps any of you has a better solution to suggest 
>> anyway, but I can make do with copying-pasting the macro call.
>>
>> Problem #2 (more serious to me):
>> I changed the contents and title of tiddler "source1" to a more realistic 
>> name ('Dramaction' here) and contents and updated the the fields 
>> accordingly.
>>
>> I made 4 dummy source tiddlers. When I deleted the 'ref_source1' field in 
>> 'Exercise1' and replaced it with a 'ref_dramaction' field, I also noticed 
>> that there were now 4 sources in the list instead of 3. One line is blank, 
>> which I suppose is the ghost of 'source1', without any data, of course, 
>> since that content doesn't exist any more. It's as if old 'source1' data 
>> wasn't purged, or TW still expected that content to exist alongside the new 
>> 'dramaction' content. It also happens every time I delete one of those 
>> fields.
>>
>> Also, when I delete the 'ref_source1' field in 'Exercise2', the list of 
>> sources gets updated in 'Exercise1', but not in Exercise2, which showed the 
>> same problem as in the previous paragraph.
>>
>> Thanks in advance for your help.
>>
>>
>> Here is the link to a MWE you can download, to see what I mean:
>>
>>
>> https://u.pcloud.link/publink/show?code=XZmdnCXZmtUJk3s4tCfxvYwlXQmYnXrL8RJV
>>
>> And below is the macro I am talking about:
>>
>> ```
>> \define SourceDisplay(prefix:"")
>> <$set name="fieldCount" filter="[fields[]prefix[$prefix$]count[]]">
>> <$text text={{{ [match[0]then[Pas de ]else] }}} />
>> <$text text={{{ [!match[1]then[sources :]else[source :]]  }}} 
>> />
>> 
>> 
>> 
>> <$list filter="[fields[]prefix[$prefix$]sort[title]]" 
>> variable="fieldName">
>> 
>> <$transclude field=<>/>
>> 
>> 
>> 
>> 
>> \end
>> ```
>>
>>

-- 
You received this message because you are subscribed 

[tw5] Re: Two problems with macro: displaying and refreshing

[springer]

Misterel,

I am *not* the expert; others could probably write the code you need in 60 
seconds. But since nobody else has answered, and understanding your task 
and its problems demands some time and attention, I'll offer one nudge to 
start...

It seems you want your macro to count (and then display one summary line 
for) each of the CURRENT tiddler's fields that start with ref_ -- Is that 
correct?

Instead, your macro is counting (and then displaying one summary line for) 
every field in your whole wiki that begins with ref_

Try pasting your code (with the variable filled in) and this alternate 
code, into your Exercice1 tiddler. Your code yields 5, because the whole 
project had five ref_ fields; but beginning your filter with [all[current] 
gets you the number you want.

First segment of your existing macro's code (specifying the prefix):
<$set name="fieldCount" filter="[fields[]prefix[ref_]count[]]">
<$text text={{{ [match[0]then[Pas de ]else] }}} />
<$text text={{{ [!match[1]then[sources :]else[source :]] }}} />


Better:
<$set name="fieldCount" filter="[all[current]fields[]prefix[ref_]count[]]">
<$text text={{{ [match[0]then[Pas de ]else] }}} />
<$text text={{{ [!match[1]then[sources :]else[source :]]  }}} />


All I'm doing here is the technique in https://groktiddlywiki.com/read/

That is: breaking down a complex problem into smaller bits, and getting 
your macro to count right *before* trying to set it up in the ViewTemplate 
with an additional variable for the prefix and an additional condition for 
displaysource[yes].  

Alas, I need to switch to other tasks, but I hope you're on the road to 
getting the behavior you need.

-Springer

On Monday, July 19, 2021 at 11:08:53 AM UTC-4 Misterel85 wrote:

> Hi,
> I'm back to work on a TiddlyWiki to manage my collection of drama 
> exercises, but I came across 2 problems with displaying their sources and 
> refreshing that display.
>
> Problem #1:
>
> My 'exercises' tiddlers all refer to a 'SourceDisplay' macro to show the 
> sources.
> If I use a field to trigger the macro to show or hide the sources, they 
> appear in 'Exercise1' tiddler, but not in 'Exercise2'. If I paste 
> <> in the text field of each of the Exercise 
> tiddlers, it works fine.
> I suppose something like 'qualify' might solve the trick, but I don't know 
> how to use it. Perhaps any of you has a better solution to suggest anyway, 
> but I can make do with copying-pasting the macro call.
>
> Problem #2 (more serious to me):
> I changed the contents and title of tiddler "source1" to a more realistic 
> name ('Dramaction' here) and contents and updated the the fields 
> accordingly.
>
> I made 4 dummy source tiddlers. When I deleted the 'ref_source1' field in 
> 'Exercise1' and replaced it with a 'ref_dramaction' field, I also noticed 
> that there were now 4 sources in the list instead of 3. One line is blank, 
> which I suppose is the ghost of 'source1', without any data, of course, 
> since that content doesn't exist any more. It's as if old 'source1' data 
> wasn't purged, or TW still expected that content to exist alongside the new 
> 'dramaction' content. It also happens every time I delete one of those 
> fields.
>
> Also, when I delete the 'ref_source1' field in 'Exercise2', the list of 
> sources gets updated in 'Exercise1', but not in Exercise2, which showed the 
> same problem as in the previous paragraph.
>
> Thanks in advance for your help.
>
>
> Here is the link to a MWE you can download, to see what I mean:
>
>
> https://u.pcloud.link/publink/show?code=XZmdnCXZmtUJk3s4tCfxvYwlXQmYnXrL8RJV
>
> And below is the macro I am talking about:
>
> ```
> \define SourceDisplay(prefix:"")
> <$set name="fieldCount" filter="[fields[]prefix[$prefix$]count[]]">
> <$text text={{{ [match[0]then[Pas de ]else] }}} />
> <$text text={{{ [!match[1]then[sources :]else[source :]]  }}} 
> />
> 
> 
> 
> <$list filter="[fields[]prefix[$prefix$]sort[title]]" variable="fieldName">
> 
> <$transclude field=<>/>
> 
> 
> 
> 
> \end
> ```
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fb3d9584-3602-42c8-ab3b-2da919ff4371n%40googlegroups.com.

[tw5] Katex and TiddlyWiki: Some syntax does not work

[Atronoush Parsi]

Testing in Tiddlywiki 5.1.23

https://tiddlywiki.com/plugins/tiddlywiki/katex/

Some example of KaTex:Supported Functions · KaTeX


like

\begin{align}
   a&=b+c \\
   d+e&=f
\end{align}


return errors! Is there any setting I missed or Tiddlywiki does not support
these features?

Mor example which do not work:

$$
\begin{equation}
\begin{split}   a &=b+c\\
  &=e+f
\end{split}
\end{equation}
$$

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAKHVXmp%3DpZjWH2_-O1i0fz0W5d7%2B5q03ROugoB_rE1wkigq4Jg%40mail.gmail.com.

[tw5] Re: Building a list of tabs dynamically in a performant manner

[Saq Imtiaz]

@Soren I recommend enabling performance instrumentation and checking to see 
which filter runs are the culprits.

https://tiddlywiki.com/#%24%3A%2Fconfig%2FPerformance%2FInstrumentation:%24%3A%2Fconfig%2FPerformance%2FInstrumentation%20%5B%5BPerformance%20Instrumentation%5D%5D

Note that you need to enable it by setting the config tiddler to "yes", 
then save and reload.

Also suggest posting a public wiki where the issue (and the condition 
filters) can be seen to facilitate debugging.
On Tuesday, July 20, 2021 at 4:05:15 PM UTC+2 Soren Bjornstad wrote:

> Important note, the condition fields aren't defined in the current public 
> version, so you'd have to add them in to get a working test.
>
> On Tuesday, July 20, 2021 at 9:03:42 AM UTC-5 Soren Bjornstad wrote:
>
>> Tones,
>>
>> :filter was my first thought, but I couldn't figure out how the data 
>> would flow through it. Perhaps I was missing something, looking forward to 
>> seeing your version.
>>
>> If it helps to see the context, have a peek at 
>> https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2Frefexplorer%2FReferenceExplorer.
>>  
>> The snippet above (or a replacement) would go inside the ref-explorer macro 
>> definition.
>>
>>
>> On Tuesday, July 20, 2021 at 8:07:09 AM UTC-5 TW Tones wrote:
>>
>>> Soren,
>>>
>>> Its late here but I have done something similar in the past without a 
>>> performance hit, and will try and create a solution tomorrow, However I 
>>> think the answer best answer may be through the use of a filter run as in 
>>> 5.3.23+ however I am sure I succeeded in something similar a few versions 
>>> ago.
>>>
>>> No need for reduce and accumulators I think.
>>>
>>> Regards
>>> Tones
>>>
>>> On Tuesday, 20 July 2021 at 13:09:18 UTC+10 Soren Bjornstad wrote:
>>>
 Hi all,

 I want to determine what tabs of the Reference Explorer in my 
 Zettelkasten to show on a template, such that if there aren't any results 
 on that tab, the tab doesn't appear at all. The results of the tab are 
 produced based on a filter (of course), so I figured I would also 
 determine 
 whether the tab appears by running a filter. The filter is stored in a 
 field in the tab tiddler.

 That is, I have a series of tiddlers with a certain tag (say *Tab*), 
 and each of these tiddlers contains a filter in some field (say 
 *condition*). For each Tiddler tagged Tab, if and only if the filter 
 Tiddler!!condition, run with the current tiddler as input, has more than 
 zero results, I want to display the tab.

 I came up with the following:

 <$set name="tabList" value={{{ [tag[Tab]] 
 :reduce[subfilter{!!condition}thenaddprefix[ 
 ]addprefix] }}}>
 <$macrocall $name="tabs" tabsList=<>/>
 

 This produces the correct result (well, as long as there are no spaces 
 in the titles of the tiddlers tagged *Tab*; I'm OK assuming that since 
 there indeed aren't any). The problem is that it is horrendously slow to 
 run all these filters. On my dev machine it is tolerable, but this is a 
 machine specced for serious processing power. On my MacBook Air it now 
 takes 1–2 seconds to open a new tiddler, even without anything currently 
 open!

 Probably I am just asking TW to do too much on the fly here, but before 
 I start rethinking the project too hard, can anyone think of obvious 
 optimizations I might be missing here? The filters involved are moderately 
 complex (the basic pattern for each is to gather together links[], 
 backlinks[], and tagging[] for the story tiddler, then filter some things 
 out of that using + and !*operator*[]'s).

>>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/591dd4e2-d6e5-4b77-8be6-5e95588e3e95n%40googlegroups.com.

Re: [tw5] Export to html while excluding some transclusions

[Louis Davout]

 Jeremy offered a solution that works as advertised - thank you Jeremy. 
Unfortunately there a 2 pain points with this method and was wondering if 
there are solutions for those. 

1. Over time I want to make some private tiddlers public. Is there 
currently a means to easily move a tiddler from one wiki to another (in my 
case both run under node on same machine)? If not, could I create a plugin 
to do so? What is the basic algorithm or basic things to keep in mind? Is 
it simply a matter of moving the tiddler file from one directory to another?

2. In order to see any changes made in a tiddler in the public wiki it 
appears I need to restart the private wiki and refresh the browser if 
browser is viewing the private wiki. If this is the case, is there a way to 
at least remotely restart server? In my case, I interact via browser with 
my wikis from one machine while the wikis run on another machine. Both are 
behind a firewall and I don't expose either of my wikis to the public. So 
I'm not too concerned about someone externally restarting my wikis. I could 
remote desktop, but for reasons, if an alternative exists I'd like to know. 
I know first-world problems but if this ability already exists, I'd like to 
take advantage of it.

A completely different alternative solution occurred to me: create a custom 
command like render but one which doesn't transclude if tiddler to 
transclude is not public. But looking at the code, I'm not sure I want to 
go down that rabbit hole.

Thanks.
On Monday, May 3, 2021 at 12:55:10 PM UTC-4 jeremy...@gmail.com wrote:

> Hi Louis
>
> If you're running under Node.js, you could setup two separate wiki 
> folders, one "private" and one "public". Then the private wiki can use the 
> "includeWiki" property to include the tiddlers from the public wiki. When 
> exporting the public content, you'd reference the public wiki, thus 
> excluding all the private content.
>
> Best wishes
>
> Jeremy
> 
>
> Hi, 
>
> I'm wondering if the following is possible either in the base wiki or with 
> a plugin.
>
> Say I have a tag 'Public'. I want to export all tiddlers and only those 
> tiddlers with the tag 'Public'. Simple enough with filter [tag[Public]]. 
> But say some of the 'Public' tiddlers have 
> transclusions of tiddlers that do not have the 'Public' tag. In my html 
> output I don't want the content of the transclusions included unless 
> transclused tiddler also has the 'Public' tag.
>
> Thanks
>
> Example
> *topic1 with tag Public*
> start
>
> {{topic2}}
>
> {{topic3}}
>
> end
>
> *topic2 without tag Public*
> private
>
> *topic3 with tag Public*
> show me
>
> *the desired html output*
> start
>
> show me 
>
> end
>
> -- 
> 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/0ddc64cc-58f3-497c-a514-d4d39292b1b9n%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/baa41e5c-32b4-4e2c-a25c-f695586b6180n%40googlegroups.com.

[tw5] Re: Building a list of tabs dynamically in a performant manner

[Soren Bjornstad]

Important note, the condition fields aren't defined in the current public 
version, so you'd have to add them in to get a working test.

On Tuesday, July 20, 2021 at 9:03:42 AM UTC-5 Soren Bjornstad wrote:

> Tones,
>
> :filter was my first thought, but I couldn't figure out how the data would 
> flow through it. Perhaps I was missing something, looking forward to seeing 
> your version.
>
> If it helps to see the context, have a peek at 
> https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2Frefexplorer%2FReferenceExplorer.
>  
> The snippet above (or a replacement) would go inside the ref-explorer macro 
> definition.
>
>
> On Tuesday, July 20, 2021 at 8:07:09 AM UTC-5 TW Tones wrote:
>
>> Soren,
>>
>> Its late here but I have done something similar in the past without a 
>> performance hit, and will try and create a solution tomorrow, However I 
>> think the answer best answer may be through the use of a filter run as in 
>> 5.3.23+ however I am sure I succeeded in something similar a few versions 
>> ago.
>>
>> No need for reduce and accumulators I think.
>>
>> Regards
>> Tones
>>
>> On Tuesday, 20 July 2021 at 13:09:18 UTC+10 Soren Bjornstad wrote:
>>
>>> Hi all,
>>>
>>> I want to determine what tabs of the Reference Explorer in my 
>>> Zettelkasten to show on a template, such that if there aren't any results 
>>> on that tab, the tab doesn't appear at all. The results of the tab are 
>>> produced based on a filter (of course), so I figured I would also determine 
>>> whether the tab appears by running a filter. The filter is stored in a 
>>> field in the tab tiddler.
>>>
>>> That is, I have a series of tiddlers with a certain tag (say *Tab*), 
>>> and each of these tiddlers contains a filter in some field (say 
>>> *condition*). For each Tiddler tagged Tab, if and only if the filter 
>>> Tiddler!!condition, run with the current tiddler as input, has more than 
>>> zero results, I want to display the tab.
>>>
>>> I came up with the following:
>>>
>>> <$set name="tabList" value={{{ [tag[Tab]] 
>>> :reduce[subfilter{!!condition}thenaddprefix[ 
>>> ]addprefix] }}}>
>>> <$macrocall $name="tabs" tabsList=<>/>
>>> 
>>>
>>> This produces the correct result (well, as long as there are no spaces 
>>> in the titles of the tiddlers tagged *Tab*; I'm OK assuming that since 
>>> there indeed aren't any). The problem is that it is horrendously slow to 
>>> run all these filters. On my dev machine it is tolerable, but this is a 
>>> machine specced for serious processing power. On my MacBook Air it now 
>>> takes 1–2 seconds to open a new tiddler, even without anything currently 
>>> open!
>>>
>>> Probably I am just asking TW to do too much on the fly here, but before 
>>> I start rethinking the project too hard, can anyone think of obvious 
>>> optimizations I might be missing here? The filters involved are moderately 
>>> complex (the basic pattern for each is to gather together links[], 
>>> backlinks[], and tagging[] for the story tiddler, then filter some things 
>>> out of that using + and !*operator*[]'s).
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e5654fb8-89c1-4570-8314-0eb6173221f2n%40googlegroups.com.

[tw5] Re: Building a list of tabs dynamically in a performant manner

[Soren Bjornstad]

Tones,

:filter was my first thought, but I couldn't figure out how the data would 
flow through it. Perhaps I was missing something, looking forward to seeing 
your version.

If it helps to see the context, have a peek 
at 
https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2Frefexplorer%2FReferenceExplorer.
 
The snippet above (or a replacement) would go inside the ref-explorer macro 
definition.


On Tuesday, July 20, 2021 at 8:07:09 AM UTC-5 TW Tones wrote:

> Soren,
>
> Its late here but I have done something similar in the past without a 
> performance hit, and will try and create a solution tomorrow, However I 
> think the answer best answer may be through the use of a filter run as in 
> 5.3.23+ however I am sure I succeeded in something similar a few versions 
> ago.
>
> No need for reduce and accumulators I think.
>
> Regards
> Tones
>
> On Tuesday, 20 July 2021 at 13:09:18 UTC+10 Soren Bjornstad wrote:
>
>> Hi all,
>>
>> I want to determine what tabs of the Reference Explorer in my 
>> Zettelkasten to show on a template, such that if there aren't any results 
>> on that tab, the tab doesn't appear at all. The results of the tab are 
>> produced based on a filter (of course), so I figured I would also determine 
>> whether the tab appears by running a filter. The filter is stored in a 
>> field in the tab tiddler.
>>
>> That is, I have a series of tiddlers with a certain tag (say *Tab*), and 
>> each of these tiddlers contains a filter in some field (say *condition*). 
>> For each Tiddler tagged Tab, if and only if the filter Tiddler!!condition, 
>> run with the current tiddler as input, has more than zero results, I want 
>> to display the tab.
>>
>> I came up with the following:
>>
>> <$set name="tabList" value={{{ [tag[Tab]] 
>> :reduce[subfilter{!!condition}thenaddprefix[ 
>> ]addprefix] }}}>
>> <$macrocall $name="tabs" tabsList=<>/>
>> 
>>
>> This produces the correct result (well, as long as there are no spaces in 
>> the titles of the tiddlers tagged *Tab*; I'm OK assuming that since 
>> there indeed aren't any). The problem is that it is horrendously slow to 
>> run all these filters. On my dev machine it is tolerable, but this is a 
>> machine specced for serious processing power. On my MacBook Air it now 
>> takes 1–2 seconds to open a new tiddler, even without anything currently 
>> open!
>>
>> Probably I am just asking TW to do too much on the fly here, but before I 
>> start rethinking the project too hard, can anyone think of obvious 
>> optimizations I might be missing here? The filters involved are moderately 
>> complex (the basic pattern for each is to gather together links[], 
>> backlinks[], and tagging[] for the story tiddler, then filter some things 
>> out of that using + and !*operator*[]'s).
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ac745270-a6b8-47e4-aa3c-504357732e3an%40googlegroups.com.

[tw5] Re: Incremental note-taking (article/discussion)

[Charlie Veniot]

This is such an awesome thread.

On Tuesday, July 20, 2021 at 9:04:07 AM UTC-3 Soren Bjornstad wrote:

> *Walt,* the thing that bugs me most about the “immutable title/ID” idea 
> is that unless your notes are also going to be immutable, the *content* of 
> a note can still change so much as to make the reference not effective 
> anymore. So I don't see much point in bothering, as long as you can avoid 
> having links break. Presumably the thing you were looking for won't move so 
> far away from the updated note that you'll be unable to find it, anyway 
> (probably not more than one link away).
>
>
Hence why I have an awful lot of love for relink.  I would have a rough 
time without it.  No broken (internal links) with Relink.
 

> It is a good point on external links breaking, though. It would be cool if 
> you could set up redirects within TW, so that you could at least have an 
> incoming link to an old title go somewhere somewhat relevant. I guess you 
> could just leave the old title with a link to the new one, but without an 
> obvious way to distinguish redirect tiddlers from other tiddlers, they 
> would probably get in your way and make you think they were the “real” 
> tiddlers all the time.
>
>
Link rot.  Redirects is a possibility.  I much prefer UID fields and 
providing links to a Tiddler in some TiddlyWiki with a "UID" reference.  
(related thread: A Prototype of UID's for stable permalinks 
)

So if I want to provide folk with a link to a specific tiddler in some 
TiddlyWiki, in a way that allows me to change the tiddler title willy-nilly 
without breaking the link, I would give folk this:
 
https://tiddlywiki-programming.neocities.org/CJ_TiddlyWikiProgramming.html#:[uid[2]]
 


For some reason, I prefer this than setting up redirects.  

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a06e5603-9288-4153-bf71-068a022fd267n%40googlegroups.com.

[tw5] Re: Building a list of tabs dynamically in a performant manner

[TW Tones]

Soren,

Its late here but I have done something similar in the past without a 
performance hit, and will try and create a solution tomorrow, However I 
think the answer best answer may be through the use of a filter run as in 
5.3.23+ however I am sure I succeeded in something similar a few versions 
ago.

No need for reduce and accumulators I think.

Regards
Tones

On Tuesday, 20 July 2021 at 13:09:18 UTC+10 Soren Bjornstad wrote:

> Hi all,
>
> I want to determine what tabs of the Reference Explorer in my Zettelkasten 
> to show on a template, such that if there aren't any results on that tab, 
> the tab doesn't appear at all. The results of the tab are produced based on 
> a filter (of course), so I figured I would also determine whether the tab 
> appears by running a filter. The filter is stored in a field in the tab 
> tiddler.
>
> That is, I have a series of tiddlers with a certain tag (say *Tab*), and 
> each of these tiddlers contains a filter in some field (say *condition*). 
> For each Tiddler tagged Tab, if and only if the filter Tiddler!!condition, 
> run with the current tiddler as input, has more than zero results, I want 
> to display the tab.
>
> I came up with the following:
>
> <$set name="tabList" value={{{ [tag[Tab]] 
> :reduce[subfilter{!!condition}thenaddprefix[ 
> ]addprefix] }}}>
> <$macrocall $name="tabs" tabsList=<>/>
> 
>
> This produces the correct result (well, as long as there are no spaces in 
> the titles of the tiddlers tagged *Tab*; I'm OK assuming that since there 
> indeed aren't any). The problem is that it is horrendously slow to run all 
> these filters. On my dev machine it is tolerable, but this is a machine 
> specced for serious processing power. On my MacBook Air it now takes 1–2 
> seconds to open a new tiddler, even without anything currently open!
>
> Probably I am just asking TW to do too much on the fly here, but before I 
> start rethinking the project too hard, can anyone think of obvious 
> optimizations I might be missing here? The filters involved are moderately 
> complex (the basic pattern for each is to gather together links[], 
> backlinks[], and tagging[] for the story tiddler, then filter some things 
> out of that using + and !*operator*[]'s).
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a17374a3-ecb3-47a2-aaed-05a617f5ff9fn%40googlegroups.com.

Re: [tw5] Re: An interactive questionnaire in TiddlyWiki

['elizabeth...@googlemail.com' via TiddlyWiki]

Hi all

I wanted to add some reflections from the Anna Freud centre. We are very 
excited about this development, for two main reasons: 

1. It helps us to directly connect outcomes measurement to the evidence 
base for what works for different types of problem. 

The interactive AIM sits within our tiddlywiki treatment manual, which 
means that the suggested interventions list generated by the questionnaire 
links directly into content on how to deliver the most appropriate 
evidence-based intervention. We will easily be able to update this as the 
evidence-base evolves. 

2. It helps us to overcome a major barrier to using outcomes measures in 
practice: feasibility/ practically 

Generally outcome measures like this are valued by health and social care 
workers in principle, but the impracticality of scoring and recording the 
data often results in low use of the measures in practice. 

We want to encourage services working with young people to use the AIM to 
plan care and assess outcome for individual young people, but also to to 
collate the data to evaluate their service as a whole. Here is a paper 
evaluating outcomes of a young person's substance use service that looks at 
a series of pre- and post-treatment AIM scores for 100 young 
people: 
https://journals.sagepub.com/doi/abs/10.1177/1359104521994875?journalCode=ccpa 

Jeremy's interactive AIM, with its different options for saving the 
results, makes it easy for workers to save the results for multiple 
purposes - perhaps saving the .doc file to the young person's health 
record, then copying the data into a spreadsheet capturing the whole team's 
outcomes. 

Thanks, Jeremy!

Liz
On Friday, 16 July 2021 at 08:14:00 UTC+1 TiddlyTweeter wrote:

> Ciao Jeremy
>
> Thanks for that! It helps clarify what I am trying to do!
>
> I will post an update note in the original thread about how I look at the 
> issue now.
>
> Best wishes
> TT
>
> On Thursday, 15 July 2021 at 10:39:57 UTC+2 jeremy...@gmail.com wrote:
>
>> Hi TT
>>
>> Thank you – I was hoping you might find the translation mechanism 
>> interesting too, does it fit your needs discussed in that other thread?
>>
>> You can try out the translation mechanism in the demo by switching the 
>> language to "Spanish" in the sidebar tab; you'll get gobbledegook that 
>> isn't Spanish, but it illustrates the difference. (Note that in the demo 
>> only the UI is translated, the questions themselves there are only in 
>> English).
>>
>> Best wishes
>>
>> Jeremy.
>>
>> Very interesting to see! Thanks.
>> I ran through the whole thing and completed all questions. It is a 
>> seriously real application! :-)
>>
>> As a side note: The Anna Freud people designed the questions really well. 
>> It is extremely difficult to design such questionnaires in a way that makes 
>> sense in normal English AND can produce operational,  quantitative, 
>> meaningful, results.  Hats off to them!
>>
>> Best wishes
>> TT
>>
>> On Wednesday, 14 July 2021 at 12:46:02 UTC+2 jeremy...@gmail.com wrote:
>>
>>> I’ve recently completed a small project for the Anna Freud National 
>>> Centre for Children and Families in London (see https://annafreud.org/) 
>>> to make an interactive questionnaire that has some interesting features:
>>>
>>>
>>>- Fairly sophisticated scoring of the answers to multiple choice 
>>>questions
>>>- Generating spreadsheet files that can be downloaded and opened in 
>>>Excel, and .DOC files that open in Microsoft Word
>>>- Copying spreadsheet data to the clipboard for pasting directly 
>>>into Excel
>>>
>>>
>>> In its current form, the questionnaire is not directly reusable for 
>>> other purposes, but I hope some of the techniques will prove useful to 
>>> others.
>>>
>>> The context for this work is that the AFNCCF trains teams of care 
>>> workers in Britain and around the world to work with the most troubled, 
>>> hard to reach young people and their families.  For more than a decade, 
>>> they have been working on the Adolescent Integrative Measure (AIM) to help 
>>> care workers make a systematic, objective record of the problems affecting 
>>> a particular young person, and to make suggestions of the interventions 
>>> that are indicated by the answers. By repeating the questionnaire after an 
>>> interval of months, workers can track a young persons progress. For the 
>>> last few years, the questionnaire has been filled out on paper but there 
>>> has long been a desire to simplify the process by moving it online.
>>>
>>> You can try out the questionnaire in a demo here:
>>>
>>> https://federatial.github.io/afnccf-aim-questionnaire/
>>>
>>> You can also see the questionnaire in AFNNCF's own site here:
>>>
>>> https://manuals.annafreud.org/ambit/#AIM%20Questionnaire
>>>
>>> The code is on GitHub:
>>>
>>> https://github.com/Federatial/afnccf-aim-questionnaire
>>>
>>> AIM is a series of multiple choice questions that measure the severity 
>>> of a particular problem. The spectrum of 

[tw5] Re: Incremental note-taking (article/discussion)

[Soren Bjornstad]

*Walt,* the thing that bugs me most about the “immutable title/ID” idea is 
that unless your notes are also going to be immutable, the *content* of a 
note can still change so much as to make the reference not effective 
anymore. So I don't see much point in bothering, as long as you can avoid 
having links break. Presumably the thing you were looking for won't move so 
far away from the updated note that you'll be unable to find it, anyway 
(probably not more than one link away).

It is a good point on external links breaking, though. It would be cool if 
you could set up redirects within TW, so that you could at least have an 
incoming link to an old title go somewhere somewhat relevant. I guess you 
could just leave the old title with a link to the new one, but without an 
obvious way to distinguish redirect tiddlers from other tiddlers, they 
would probably get in your way and make you think they were the “real” 
tiddlers all the time.

*TT,* I like your phrasing of the “category error” involved in applying one 
notes system to everything. There are likely very few people who have 
needed to work with notes of such a wide variety of types that they can 
speak confidently on all of them. We've found some general patterns, but 
they don't all work well for every purpose.

On the topic of places where the author's mechanism would be good, I've 
wondered if it would be handy for project or work diaries…almost like a 
more general Git commit log. I used a custom PowerShell script called 
“Daylog” at work for a year or two that worked kind of like this – you 
wrote a text file with a bunch of chronological entries in it and could 
chain them together into topics, responsibilities, todo items and notes on 
their completion, etc.

*Si,* I realized I never responded to your characterization of my Random 
Thoughts as kind of like incremental note-taking way up-thread. I think it 
might be a little dangerous to attribute too much intentionality to that 
structure, because I started it when I was 14 years old (!) and 
chronological bits was just the obvious structure to put it in since I 
didn't really know much about notes at the time. But that said, it has 
turned out to work well over the following 11+ years, at least once I went 
back and added ID numbers to it so I could cross-reference things, so it 
can't be too bad of a system. Perhaps the main difference between it and 
evergreen notes is that it's optimized for ease of insertion, while 
evergreen notes are optimized for ease of later use and flexibility of 
thinking. Those are, I think, fundamentally irreconcilable; you can reduce 
the weaknesses of one system in the opposite area, but nothing is ever 
going to be great at both. So IMO the best option is two complementary 
systems (or parts of one system) where you can move things from the 
quick-write one to the flexible-thinking one when they become important.

I have a vague draft on the principles of RT as I've accidentally 
discovered them here: 
https://zettelkasten.sorenbjornstad.com/#SketchOnCommonplacing

On Tuesday, July 20, 2021 at 5:52:20 AM UTC-5 ludwa6 wrote:

> That's an important point @TT about the WHY of "Luhmann's Rule," i would 
> say, regarding immutability of the index field.  
> In the world of hard-copy artifacts he was designing, this makes perfect 
> sense... And also on the WWW, still today, where the problem of link-rot is 
> a serious PITA. 
>
> BUT in the domain of a standalone TW instance with the Relink plugin -e.g. 
> my own desktop Digital Garden- that rule becomes a serious impediment to 
> the kind of refactoring that is wanted. 
>
> OTOH: In case of a public TW instance, where you want to encourage content 
> sharing & reuse via permalinks, this is where one might do well to apply 
> Luhmann's Rule. 
> Still: i find it hard to forbear from changing names to reflect changes in 
> my thinking and/or popular usage.  A constant struggle!
>
> /walt
>
>
> On Tuesday, July 20, 2021 at 9:36:12 AM UTC+1 TiddlyTweeter wrote:
>
>> Ciao Si,
>>
>> FOOTNOTE ON ZETTELKASTEN
>>
>> Luhmann's Zettelkasten were, of course, only on paper. He was very 
>> dedicated to NEVER changing the INDEX to an entry. 
>> He never said, or implied, you could not UPDATE an entry if you wanted 
>> too. 
>> The Zettelkasten thing is about NOT spawning clone entities, rather 
>> fixing the Index of one forever. 
>>
>> Best wishes
>> TT
>>
>>
>> On Thursday, 15 July 2021 at 21:18:48 UTC+2 Si wrote:
>>
>>> I just came across this post: https://thesephist.com/posts/inc/, and it 
>>> challenges a lot of my own views on effective note-taking practices, so I 
>>> thought it was worth sharing here.
>>>
>>> The author advocates for a kind of chronological system, where as a rule 
>>> notes are never updated after they are made, meaning that they retain a 
>>> fixed position in time. It kind of reminded me of Soren's random thoughts: 
>>> https://randomthoughts.sorenbjornstad.com/
>>>
>>> Anyway this approach 

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Frédéric Demers]

a quick update to everyone;

I am making steady progress on packaging this merging solution, hoping to
release as a Streams plugin addon. I have repurposed the button from
https://szen.io/stream/. I now have it also working as a Streams context
menu, with keyboard shortcuts, and it can export sub-trees correctly by
adjusting the depth levels of the bulleted/numbered lists.

A few ideas I am going to try to roll in and release a beta by the end of
this week

Cheers

On Sat, 17 Jul 2021 at 09:06, Frédéric Demers  wrote:

> with capture:
>
> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers 
> wrote:
>
>> nevermind, I think I solved it at least, significant progress
>>
>> here's the wikitext for the challenging nodes; renders pretty well:
>>
>> * 
>>
>> ''Streams'' uses the following tiddler fields to maintain the structure
>> of a stream:
>>
>> * each node tiddler has a field `stream-type`
>> * each node that has children, contains their titles in a list in the
>> field `stream-list`
>> * each node that has a parent, contains the parent's title in the field
>> `parent`
>>
>> ''You can manipulate these tiddlers just as you would any other tiddlers,
>> with filters and list and action widgets''
>>
>> 
>> * To make it easier to work with Streams tiddlers and their nodes, two
>> filters have been introduced. See [[Streams 0.2 improvements/Filters]]
>> * 
>>
>> This is an example of a button that can export the content of the nodes
>> of a tiddler whose title is in the variable `myTiddler` and save the
>> combined text to a single tiddler:
>>
>> ```
>> <$button> save to a single tiddler
>> <$vars lb="
>>
>> ">
>> <$action-setfield $tiddler="report" text={{{
>> [get-stream-nodes[]]
>>  :reduce[get[text]addprefixaddprefix] }}}/>
>> 
>> 
>> ```
>> Note that this disregards the node hierarchy.
>> * 
>>
>> Similarly to export the combined text of the nodes as HTML you can use
>> the `<$wikify>` widget:
>>
>> ```
>> <$button> export as HTML
>> <$wikify name="text" text="""<$list
>> filter="[get-stream-nodes[]]">
>> <$transclude mode=block/>
>> """ output="html">
>> <$action-setfield $tiddler="report" text=<>/>
>> 
>> 
>> ```
>>
>> 
>> * 
>>
>> Here is an example of a macro that can be used to export a stream using a
>> custom HTML structure:
>>
>> ```
>> \define print-row()
>> \whitespace trim
>> <$(innerTag)$>{{!!text}}
>> <$list filter="[has[stream-list]]" variable="_NULL">
>> <$(outerTag)$>
>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>> <>
>> 
>> 
>> 
>> 
>> \end
>>
>> \define print-stream()
>> \whitespace trim
>> <$(outerTag)$>
>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>> <>
>> 
>> 
>> \end
>>
>> \define export-stream(tiddler:"" outerTag:"article" innerTag:"section")
>> \whitespace trim
>> <$vars outerTag="$outerTag$" innerTag="$innerTag$"
>> currentTiddler="$tiddler$">
>> <>
>> 
>> \end
>>
>> ```
>>
>> Try the following:
>>
>> * `<>` to export using article and section
>> tags
>> * `<>` to export
>> as a list in HTML
>>
>> If you need a copy to clipboard button it would look something like this:
>>
>> ```
>> <$button>
>> <$wikify name="stream-html" text=<>
>> output="html" >
>> <$action-sendmessage $message="tm-copy-to-clipboard"
>> $param=<>/>
>> 
>> Copy stream to clipboard as HTML
>> 
>> ```
>>
>> Similarly you can write recursive macros to output as just flat text
>> (with no structure or hierarchy) or wiki text list syntax (assuming you
>> have no multi-line content).
>>
>> On Sat, 17 Jul 2021 at 09:01, Saq Imtiaz  wrote:
>>
>>> @fred
>>>
>>>
 I noticed my solution does not work so well for complex node content,
 as those in:
 https://saqimtiaz.github.io/streams/#Working%20with%20streams%20tiddlers


 The reason is that wrapping in  tags mangles them badly; I tried a
 few alternatives (, more white space, ..), no success yet. Any
 suggestions?

>>>
>>> This is actually the real challenge and why there currently isn't a
>>> default export option from Streams. Depending on the nature of the content,
>>> it seems difficult to generalize a single export format that will work and
>>> one of the common pitfalls is to think of Streams nodes as a list,*
>>> which they are not.*
>>>
>>> A stream node is a tiddler which can contain any kind of content, and
>>> not all kinds of content can be mapped to a list item. It might be easier
>>> to set limitations in one's usage as to what to put inside of a node and
>>> have an export format that works accordingly, rather than trying to come up
>>> with a universal export format that works for all content. Hence my
>>> suggestion of gathering real world user data to drive the process.
>>>
>>> --
>>> 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/-xTFWPwzq6g/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> 

[tw5] Re: Random tiddler viewer tiddler

[Soren Bjornstad]

You might be interested in the shuffle operator plugin 
, which can 
accept a seed parameter to avoid this unexpected-change problem. You would 
do, e.g.,

<$list filter="[tag[*poem]shuffle{$:/seed}first[]]">

...and then have a random button that updates the seed. The order of the 
inputs will stay the same as long as the seed is the same.

On Tuesday, July 20, 2021 at 3:07:06 AM UTC-5 barro...@gmail.com wrote:

> Amusing, any using the tiddler's upper right icon (fold, info, etc) and 
> sidebar activity causes it change to the next random tiddler, but nothing 
> to prevent it from being used to read randomly selected tiddlers.  Will 
> have to think of an active trigger or pause button.
>
> On Tuesday, July 20, 2021 at 1:46:27 AM UTC-4 A Gloom wrote:
>
>> Why?  Why not?
>>
>> Based off the random filter idea of SS found at TW-Scripts...
>>
>> It is a tiddler designed to be used in the story river as the main focus 
>> (for reading), so I haven't seen any issues with it being triggered by 
>> other wiki activity that would cause a tiddler refresh and a new random 
>> tiddler display (since it wouldn't be open during any editing).  The 
>> tiddler gets opened by a button with a tm-navigate message in the top or 
>> sidebar. The two buttons in the tiddler itself cause a new random tiddler 
>> to display by writing "Next poem" to a field ( zzdatesort ) of the tiddler 
>> which it is transcluded in the buttons text, causing a refresh of the 
>> tiddler and triggering the random filter of the list widget controlling the 
>> random tiddler display.
>>
>>
>> \define randpoem()
>> <$set name=r1 value=<>>
>> <$set name=r2 filter="[splitregexp:title[]rest[]join[]]" >
>> <$set name=nth filter="[tag[*poem]count[]multiplydivide[100]ceil[]]">
>> <$list filter="[tag[*poem]nth]">
>> <$view field="title"/>
>> <$transclude field="text" mode="block"/>
>> 
>> 
>> 
>> 
>> \end
>> <$button set="!!zzdatesort" setTo="Next poem" 
>> >{{!!zzdatesort}}
>> <>
>> <$button set="!!zzdatesort" setTo="Next poem" >{{!!zzdatesort}}
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dd0f14b0-3a6d-4a9c-bd14-2c0b71f7189an%40googlegroups.com.

[tw5] Re: Incremental note-taking (article/discussion)

[ludwa6]

That's an important point @TT about the WHY of "Luhmann's Rule," i would 
say, regarding immutability of the index field.  
In the world of hard-copy artifacts he was designing, this makes perfect 
sense... And also on the WWW, still today, where the problem of link-rot is 
a serious PITA. 

BUT in the domain of a standalone TW instance with the Relink plugin -e.g. 
my own desktop Digital Garden- that rule becomes a serious impediment to 
the kind of refactoring that is wanted. 

OTOH: In case of a public TW instance, where you want to encourage content 
sharing & reuse via permalinks, this is where one might do well to apply 
Luhmann's Rule. 
Still: i find it hard to forbear from changing names to reflect changes in 
my thinking and/or popular usage.  A constant struggle!

/walt


On Tuesday, July 20, 2021 at 9:36:12 AM UTC+1 TiddlyTweeter wrote:

> Ciao Si,
>
> FOOTNOTE ON ZETTELKASTEN
>
> Luhmann's Zettelkasten were, of course, only on paper. He was very 
> dedicated to NEVER changing the INDEX to an entry. 
> He never said, or implied, you could not UPDATE an entry if you wanted 
> too. 
> The Zettelkasten thing is about NOT spawning clone entities, rather fixing 
> the Index of one forever. 
>
> Best wishes
> TT
>
>
> On Thursday, 15 July 2021 at 21:18:48 UTC+2 Si wrote:
>
>> I just came across this post: https://thesephist.com/posts/inc/, and it 
>> challenges a lot of my own views on effective note-taking practices, so I 
>> thought it was worth sharing here.
>>
>> The author advocates for a kind of chronological system, where as a rule 
>> notes are never updated after they are made, meaning that they retain a 
>> fixed position in time. It kind of reminded me of Soren's random thoughts: 
>> https://randomthoughts.sorenbjornstad.com/
>>
>> Anyway this approach seems completely counter to my current approach to 
>> note-taking, where I want my notes to represent ideas that I am building 
>> over time with little regard to where or when they originally came from.
>>
>> I'm not particularly convinced, but I'm curious if anyone here has any 
>> thoughts? Do you see any advantages to this approach? Disadvantages? Do you 
>> think it could gel with the zettelkasten philosophy, or are they polar 
>> opposites?
>>
>> Just interested in hearing other peoples thoughts.
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fc8951aa-f331-473b-902d-924817e54f9fn%40googlegroups.com.

Re: [tw5] Artwork for v5.2.0

[Jeremy Ruston]

After de-duplication, there are now 13 entries. I started a new thread for the 
voting here:

https://groups.google.com/g/tiddlywiki/c/QULnFJm9A8k/m/OCA3uyYoBAAJ 


I’d like to thank everyone again for putting so much into this competition, 
it’s great to see so many high quality entries.

Best wishes

Jeremy

> On 19 Jul 2021, at 21:41, Jeremy Ruston  wrote:
> 
>> Although I haven't done any further design work, I did replace the existing 
>> green "tw-mask" graphic with a variant sitting on my desktop that represents 
>> my "lightest and leanest" graphic attempt, coming in at 10K, and pasted 
>> below. For what it's worth, I see 20 candidates, rather than 18, though some 
>> are fairly redundant. I'm happy to tweak the gallery site 
>> (https://tw-logo-contest.tiddlyhost.com/ 
>> ) to display only your winnowed 
>> batch on the HelloThere tiddler, assuming everyone's ok with that proposal. 
> 
> Thank you, I will also transfer the images over to Google Forms, which I have 
> previously used for voting. Hopefully tomorrow, and I'll make a new post 
> announcing the voting.
> 
> Many thanks,
> 
> Jeremy
> 
> 
> 
>> 
>> -Springer
>> 
>> 
>> 
>> 
>> 
>> 
>> On Monday, July 19, 2021 at 8:11:12 AM UTC-4 jeremy...@gmail.com 
>>  wrote:
>> As is the way of these things, it took a little longer to get v5.2.0 ready 
>> for release, but now I think we’re ready to run the voting part of the 
>> competition, and close the competition to new submissions.
>> 
>> Thank you to everyone who has entered. The results are impressive, and the 
>> discussion here has been interesting, and I hope will bear fruit in other 
>> projects in the future.
>> 
>> There are currently 18 entries listed at 
>> https://tw-logo-contest.tiddlyhost.com 
>> , a lot more than we’ve had before.
>> 
>> In some cases we’ve got some very similar variants which risks splitting the 
>> vote for a design.
>> 
>> So, unless anybody has a better suggestion, I will choose my preferred 
>> variant of each design as I prepare the voting form.
>> 
>> Best wishes
>> 
>> Jeremy
>> 
>> 
>> 
>>> On 2 Jul 2021, at 01:45, TW Tones >> > wrote:
>>> 
>> 
>>> All especially those with competition entries,
>>> 
>>> Love all this work, wish I had these image design skills. Whatever wins it 
>>> would be nice to collect the final submissions (and previous ones) as 
>>> collateral people building a wiki could use, on there home tiddler, as 
>>> icons, favicons (sometimes), Wiki or tiddler backgrounds, or images 
>>> especially when demonstrating a feature of that release.
>>> 
>>> When you drag and drop a tiddler to a valid location you see a mouse 
>>> pointer and a little box with a plus, on my browsers at least. Perhaps 
>>> stamping your design with this would promote the drag features of the new 
>>> version. I suggest a different color just to stop people confusing with 
>>> their own mouse pointer.
>>> 
>>> Regards
>>> Tones
>>> 
>>> 
>>> On Wednesday, 30 June 2021 at 07:30:50 UTC+10 james.w@gmail.com 
>>>  wrote:
>>> I meant @springer, not whoever skinner is :)
>>> 
>>> On Tuesday, 29 June 2021 at 22:29:33 UTC+1 James Anderson wrote:
>>> Hi Frank,
>>> 
>>> I asked skinner to remove the alts, I was just playing on the same idea and 
>>> didn't want to flood the list of choices.
>>> 
>>> Thanks,
>>> James
>>> 
>>> On Tuesday, 29 June 2021 at 21:03:12 UTC+1 f.brunsb...@gmail.com <> wrote:
>>> Dear all,
>>> 
>>> @springer: 
>>> Really cool your last picture ... and now in RGB style like the picture of 
>>> James "chroma-b-alt.png"... By the way, 
>>> I'm missing some pictures on tw-logo-contest.tiddlyhost.com 
>>>  What's going on?
>>> 
>>> @James.W: Have I mentioned that I like your RGB series? I also like the 
>>> spirit of "emoji-field-title.png". 
>>> There might be more hints of new features swimming in the background ...
>>> 
>>> 
>>> My favourites so far are (excluding my pictures) and without ranking:
>>> 3D twisted version white.png (springer)
>>> dark-fields.png (springer)
>>> json-file-icon-semi-alpha.png (Mohammad)
>>> chroma-b-alt.png (James W)
>>> emoji-field-title.png (James W)
>>> and even if its shine is slowly fading:
>>> iamdar-1.png (IAmDarthMole)
>>> 
>>> I agree with Jeremy, perhaps such a contest would be useful for an 
>>> advertising banner. For a simple release number, the effort is great, 
>>> because unfortunately it will soon be replaced again. An advertising 
>>> banner, if without a number, can at least be used for longer.
>>> 
>>> A fixed scheme (e.g. logo on the left side, release number on the right 
>>> side, colours fixed in advance) and ... instead an advertising banner on 
>>> "HelloThere" in the background? I would, I like that.
>>> 
>>> Here for this competition I would have liked something like 

[tw5] Voting for the v5.2.0 banner artwork

[Jeremy Ruston]

I’d like to invite everyone to vote for the banner artwork for the upcoming 
v5.2.0 release. (The banner is shown in the splash screen for 
https://tiddlywiki.com/ , and within the HelloThere 
tiddler).

To take part, please visit this link and choose which one of the 13 entries you 
think would look best:

https://forms.gle/CWhnVMwumq4pNzoJ6 

No sign in is required.

The thread where we discussed and gathered the entries is here:

https://forms.gle/CWhnVMwumq4pNzoJ6 

Best wishes,

Jeremy.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4A81EA1B-A760-43D4-A54D-E208789BE4BB%40gmail.com.

[tw5] Re: Incremental note-taking (article/discussion)

[TiddlyTweeter]

Ciao Si,

FOOTNOTE ON ZETTELKASTEN

Luhmann's Zettelkasten were, of course, only on paper. He was very 
dedicated to NEVER changing the INDEX to an entry. 
He never said, or implied, you could not UPDATE an entry if you wanted too. 
The Zettelkasten thing is about NOT spawning clone entities, rather fixing 
the Index of one forever. 

Best wishes
TT


On Thursday, 15 July 2021 at 21:18:48 UTC+2 Si wrote:

> I just came across this post: https://thesephist.com/posts/inc/, and it 
> challenges a lot of my own views on effective note-taking practices, so I 
> thought it was worth sharing here.
>
> The author advocates for a kind of chronological system, where as a rule 
> notes are never updated after they are made, meaning that they retain a 
> fixed position in time. It kind of reminded me of Soren's random thoughts: 
> https://randomthoughts.sorenbjornstad.com/
>
> Anyway this approach seems completely counter to my current approach to 
> note-taking, where I want my notes to represent ideas that I am building 
> over time with little regard to where or when they originally came from.
>
> I'm not particularly convinced, but I'm curious if anyone here has any 
> thoughts? Do you see any advantages to this approach? Disadvantages? Do you 
> think it could gel with the zettelkasten philosophy, or are they polar 
> opposites?
>
> Just interested in hearing other peoples thoughts.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0d20575f-b33a-4a11-b482-65c6ed0ead1dn%40googlegroups.com.

[tw5] Re: List: fieldname = tiddlername currentTiddler

[A Gloom]

1) Make a tiddler with that code above to act as your transclusion 
"template".  Start it with <$tiddler tiddler=<>> and end it 
with .  Name it, you will need its name for step 2.
2) in any tiddler you want to reuse it in, use 
{{||templatetiddlernamefromstep1}}

On Saturday, June 12, 2021 at 5:25:09 AM UTC-4 vinvi...@gmail.com wrote:

> Hello,
>
> The following is listing the values out of field "*warning*" of tiddler "
> *@fields*". The name of the listed field bears the same name as the 
> tiddler containing the list-code:
>
> In tiddler warning: 
> *<$list 
> filter="[list[@fields!!warning]search:title{$:/temp/search@fields}]" 
> variable=warning-value>*
>
>
> I want to transclude this code in different tiddlers.
> How do I avoid having to specify the field name every time?
> $tiddler="@fields" $field=<>
>
> Thank you,
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/645ffaa5-4a1f-4fd7-8701-3f896021c1a7n%40googlegroups.com.

[tw5] Re: Incremental note-taking (article/discussion)

[TiddlyTweeter]

Ciao Si,

Interesting thread! 

I read  the article on  Incremental note-taking 
 ...

I'm not so negative about it as maybe some feel. To me it illustrates a 
generic issue on the internet. That we UNDER-conceptualize what the whole 
thing is about.

On the POSITIVE side the writer has an explicit NARROW brief that they are 
pursing. 
In that I think it is informative & useful for certain types of 
apps/purposes.

On the NEGATIVE side it falls into a basic trap. 
In philosophy you'd call it a "*category error*". 
What happens is that the writer *conflates *AN objective of their own with 
A GLOBAL *universal rule*., as if they were co-terminus. They aren't.
So the "reach" is just not credible!

However, it has to be said, that, generally, the internet tends to foster 
such errors as *we have no agreed shared understanding* of the 
technological ramifications of meaning-making yet.

My 2 cents
TT

On Thursday, 15 July 2021 at 21:18:48 UTC+2 Si wrote:

> I just came across this post: https://thesephist.com/posts/inc/, and it 
> challenges a lot of my own views on effective note-taking practices, so I 
> thought it was worth sharing here.
>
> The author advocates for a kind of chronological system, where as a rule 
> notes are never updated after they are made, meaning that they retain a 
> fixed position in time. It kind of reminded me of Soren's random thoughts: 
> https://randomthoughts.sorenbjornstad.com/
>
> Anyway this approach seems completely counter to my current approach to 
> note-taking, where I want my notes to represent ideas that I am building 
> over time with little regard to where or when they originally came from.
>
> I'm not particularly convinced, but I'm curious if anyone here has any 
> thoughts? Do you see any advantages to this approach? Disadvantages? Do you 
> think it could gel with the zettelkasten philosophy, or are they polar 
> opposites?
>
> Just interested in hearing other peoples thoughts.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/95fd30eb-f3d8-45c5-8c0b-f2f81abc2e92n%40googlegroups.com.

[tw5] Re: Random tiddler viewer tiddler

[A Gloom]

Amusing, any using the tiddler's upper right icon (fold, info, etc) and 
sidebar activity causes it change to the next random tiddler, but nothing 
to prevent it from being used to read randomly selected tiddlers.  Will 
have to think of an active trigger or pause button.

On Tuesday, July 20, 2021 at 1:46:27 AM UTC-4 A Gloom wrote:

> Why?  Why not?
>
> Based off the random filter idea of SS found at TW-Scripts...
>
> It is a tiddler designed to be used in the story river as the main focus 
> (for reading), so I haven't seen any issues with it being triggered by 
> other wiki activity that would cause a tiddler refresh and a new random 
> tiddler display (since it wouldn't be open during any editing).  The 
> tiddler gets opened by a button with a tm-navigate message in the top or 
> sidebar. The two buttons in the tiddler itself cause a new random tiddler 
> to display by writing "Next poem" to a field ( zzdatesort ) of the tiddler 
> which it is transcluded in the buttons text, causing a refresh of the 
> tiddler and triggering the random filter of the list widget controlling the 
> random tiddler display.
>
>
> \define randpoem()
> <$set name=r1 value=<>>
> <$set name=r2 filter="[splitregexp:title[]rest[]join[]]" >
> <$set name=nth filter="[tag[*poem]count[]multiplydivide[100]ceil[]]">
> <$list filter="[tag[*poem]nth]">
> <$view field="title"/>
> <$transclude field="text" mode="block"/>
> 
> 
> 
> 
> \end
> <$button set="!!zzdatesort" setTo="Next poem" 
> >{{!!zzdatesort}}
> <>
> <$button set="!!zzdatesort" setTo="Next poem" >{{!!zzdatesort}}
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8022e04d-e847-49d5-9b17-f276547f3975n%40googlegroups.com.

[tw5] Re: tiddlywiki structured like https://ibnishak.github.io/Timimi/

[Sapphireslinger]

++, thank you!

On Tuesday, July 20, 2021 at 3:33:39 PM UTC+8 R² wrote:

> The author also released it as a theme. It's called the CleverNote theme. 
> You can find it both at 
> https://ibnishak.github.io/Tesseract/projects/CleverNote%20Beta.html, and 
> within the Timini  TW itself at 
> https://ibnishak.github.io/Timimi/#%24%3A%2Fplugins%2Ftesseract%2FCleverNote
>
> ++
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/495f1826-7d25-473b-9984-8d3222c0a865n%40googlegroups.com.

[tw5] Re: tiddlywiki structured like https://ibnishak.github.io/Timimi/

[R²]

The author also released it as a theme. It's called the CleverNote theme. 
You can find it both at 
https://ibnishak.github.io/Tesseract/projects/CleverNote%20Beta.html, and 
within the Timini  TW itself at 
https://ibnishak.github.io/Timimi/#%24%3A%2Fplugins%2Ftesseract%2FCleverNote

++

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c823f3e7-f5a0-44f1-a82e-5ac91c23f1f0n%40googlegroups.com.

[tw5] Re: OpenAPI Explorer in TW

[ludwa6]

@Mario: It's the v2 API of farmOS that i'm trying to understand right now, 
so that is the focus.  

As compared w/ the 1.x version, v2 is said to be more powerful -and, i am 
finding, more exacting in its requirements.  In trying to .GET data from 
both (all that i've done so far[1]), using the farmOS.py library 
, there are some interesting methods 
available for client 2.x 
 -iterate, 
for example- but i've been having real trouble getting some of them to run 
(in fact, when i passed the traceback on my .iterate fail to developer, he 
admitted i may have found a bug).

[1] As a volunteer tester for the data migration program, all i've done so 
far is download .csv exports from those tables in the database most of 
interest to me, and try to spot any diffs in the downloads from v1.x and v2 
instances, so i've been avoiding the PUT, POST and DELETE methods for now.  
But i've got a bigger challenge, once this phase of testing is complete, to 
load a bunch of data from spreadsheets where we do our crop planning, which 
process will be greatly facilitated by API scripts... So i'm feeling the 
need to understand this API, what we can and can't do with it, just as 
quick as i can get up the learning curve!

SO @Mario: do you think as i do that an API Explorer in TW could be a 
useful tool in this pursuit? and, if so, then is it something that might be 
built w/ relative ease?

/walt

On Monday, July 19, 2021 at 10:47:58 PM UTC+1 PMario wrote:

> Hi Walt,
>
> After I did send my last post, I did find the new docs for version 2 of 
> farmOS. I can see your dilemma 
>  now. 
>
> The question is, do you want to explore the V2 API or the V1.x API. It 
> seems they are fundamentally different. 
>
> -mario
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2d1a6e7b-a27d-4dcf-891c-41dbf1b8f275n%40googlegroups.com.

Re: [tw5] Re: Just the UI of tiddlywiki

[A Gloom]

@Joshua

Definitely interested in multi-player functionality.  I still have my 
interactive novel TW with interactive SVG mapping and quasi first person 
perspective video game interface to work with the SVG mapping.

On Sunday, July 18, 2021 at 11:24:00 PM UTC-4 joshua@gmail.com wrote:

> I am getting very close to a "multiplayer" solution. It's definitely one 
> of the "Hard Problems": 
> https://gigaom.com/2009/05/10/why-sync-is-so-difficult/
>
> Best,
> Joshua Fontany
>
> On Friday, July 16, 2021 at 5:59:57 AM UTC-7 ludwa6 wrote:
>
>> @PMario: just to say thanks (again!) for sharing another treasure of the 
>> TW world -TiddlyWeb API Explorer 
>>  in this case. 
>> As per my post to this other thread 
>> ,  it opened my 
>> eyes to the possibility of an OpenAPI Explorer in TW -and i'd love to know 
>> what you think about that, either in that other thread or via DM (this 
>> one's really not about that).
>>
>> On this topic, i can only say: i share Xavier's interest in the idea of 
>> connecting TW as front end to a backend server with muli-user / multi-edit 
>> capability.  Of course that old problem of edit conflict avoidance/ 
>> resolution would need to be solved, but i have trouble accepting that as a 
>> real stopper in this day -although from what i gather (from email 
>> exchange with dev Chris Dent), TiddlyWeb is not likely to be the place 
>> where such functionality will emerge.   If there be some other place to 
>> look for solutions, it'd be great if someone could share info about that 
>> here!
>>
>> /walt
>>
>>
>> On Wednesday, July 14, 2021 at 1:51:49 PM UTC+1 PMario wrote:
>>
>>> On Wednesday, July 14, 2021 at 1:38:46 PM UTC+2 somen...@gmail.com 
>>> wrote:
>>> ...
>>>
 I will look into the code but it's a pitty to be TW2. Perhaps someone 
 could point to me where is the code of the UI in the code of official 
 tiddlywiki5. 

>>>
>>> Hi Xavier,
>>>
>>> I think there is a bit of a misunderstanding how TiddlyWiki works. ... 
>>> TiddlyWiki is a self-contained single file wiki. ... No server is needed 
>>> other than for serving a 
>>> single file resource. 
>>>
>>> TLDR;
>>> I think it would be good, if you explain a bit closer what you want to 
>>> do. 
>>>
>>> --
>>>
>>> If you open tiddlywiki.com it's served from a github page as a single 
>>> 6MByte index.html file. ... Since github does server side compression only 
>>> about 2Mbyte are sent to the client. 
>>>
>>> Everything you see UI wise is rendered on the client. ... It would be 
>>> the same experience if I would send you myWiki.hmtl by e-mail. 
>>>
>>> If I "permalink" to eg: https://tiddlywiki.com/#HelloThere  the browser 
>>> will open the HelloThere tiddler, because the whole content is already in 
>>> the client. No server is involved, the core code "catches" the URI fragment 
>>> and displays the tiddler.
>>>
>>> -
>>>
>>> A TiddlyWeb server will also "only" create a single resource if you 
>>> request https: //your-uri/index.html ... It will build the html file server 
>>> side and send it as 1 file, that contains code, UI and data to the client. 
>>>
>>> The advantage of TiddlyWeb is, that you also have some API routes that 
>>> will let you request recipes, bags and single tiddlers, without any TW UI 
>>> as text or JSON. There is a query language with which you can do server 
>>> side search. 
>>>
>>> The TW UI is about 2100 elements. If you download empty.html form 
>>> tiddlywiki.com you can open the *$:/ControlPanel : Info : Basic* : tab 
>>> and have a look a the "*Number of shadow tiddlers*": 2088 ... Most of 
>>> them are responsible for the TW js core and UI. The whole TW UI is built 
>>> using TW wikitext and tiddlers. 
>>>
>>> -mario
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0cbeea10-a3d4-4ff8-bcf0-e0754e98e130n%40googlegroups.com.