[tw5] Re: Bug in TW 5.2.0 in zoomin view.

[Soren Bjornstad]

This issue I was experiencing might be the same thing or related:
https://groups.google.com/g/tiddlywiki/c/7HPSS67j4uU/m/kOgsG8YQBAAJ


On Tuesday, November 9, 2021 at 10:57:29 AM UTC-6 jeremy...@gmail.com wrote:

> Hi Siniy-Kit,
>
> I can confirm the problem with v5.2.0. I also checked v5.1.23 and it seems 
> to have the same problem.
>
> Do you know when the problem was introduced? Did it indeed ever work 
> properly?
>
> Best wishes
>
> Jeremy
>
> On Tuesday, November 9, 2021 at 4:45:33 PM UTC Jeremy Ruston wrote:
>
>> Hi Siniy-Kit
>>
>> Thanks for the report, I'll investigate.
>>
>> Best wishes
>>
>> Jeremy
>>
>> On Sunday, November 7, 2021 at 9:40:19 AM UTC Siniy-Kit wrote:
>>
>>> Jeremy, help me please. I want to update my template to  new version, 
>>> but it works only with zoomin view. 
>>>
>>> четверг, 28 октября 2021 г. в 15:52:49 UTC+3, Siniy-Kit: 
>>>
 Old TW5 works good. But now it has bad auto scroll while navigating 
 between tiddlers 
 For example open this tiddler 
 https://tiddlywiki.com/#Filter%20Operators then make zoomin view
 [image: Снимок экрана 2021-10-28 154440.png]
  then go back to Filter Operators tiddler and press "range"
 [image: Снимок экрана 2021-10-28 154716.png]

 after click you will see this
 [image: Снимок экрана 2021-10-28 154853.png]

 I want to see the top of this tiddler, but it autoscroll to middle. Can 
 we fix this bug? 

>>>

-- 
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/7fdf9810-6ef8-428d-94a6-8692e5d9cf71n%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

[Soren Bjornstad]

The page that's linked in the Talk TW thread explains where you can get it:
https://sobjornstad.github.io/tzk/

On Tuesday, October 5, 2021 at 10:20:42 PM UTC-5 James wrote:

> Hi Soren,
> Do you have an empty Tiddly Zettelkasten that we could download and use?
>
> On Thursday, 23 September 2021 at 00:51:25 UTC+8 Soren Bjornstad wrote:
>
>> The Zettelkasten edition I talked about wanting to get together is public 
>> now. It's still alpha-ish, but in much better shape than the version I 
>> published here. You can find a link and continue discussion of it on this 
>> thread:
>>
>>
>> https://talk.tiddlywiki.org/t/introducing-tzk-tiddlyzettelkasten-edition/834
>>
>> On Monday, June 28, 2021 at 12:51:14 PM UTC-5 Soren Bjornstad wrote:
>>
>>> Probably did, but right now that one is more or less just <>> "[[OpenQuestion]backlinks[]]">> -- there's no special functionality for 
>>> selecting questions out of the tiddlers. That's something I'd like to 
>>> improve in the future.
>>>
>>> On Monday, June 28, 2021 at 12:12:30 PM UTC-5 mark.cu...@gmail.com 
>>> wrote:
>>>
>>>> Is there any chance your filter missed the OpenQuestions tiddler as 
>>>> well?
>>>>
>>>> On Sunday, April 18, 2021 at 11:55:35 AM UTC-4 Soren Bjornstad wrote:
>>>>
>>>>> Looks like my filter missed the TODO tiddler, which should contain:
>>>>>
>>>>> \define todore() \[\[TODO\]\]:
>>>>> \define splitre() [\.\?!]
>>>>>
>>>>> To add a TODO item to this list, simply link to [[TODO]].
>>>>>
>>>>> 
>>>>> <$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer>
>>>>>   <$list 
>>>>> filter="[get[text]splitregexplast[]splitregexpfirst[]]"
>>>>>  
>>>>> variable=inner>
>>>>>   <$link to=<>/>
>>>>> ''TODO:'' <>.
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>> On Sunday, April 18, 2021 at 10:23:28 AM UTC-5 ludwa6 wrote:
>>>>>
>>>>>> Good to know, Soren, but first i have to get the basics under 
>>>>>> control, like: TODO items!  
>>>>>>
>>>>>> About that, you say in your video at 28'47" 
>>>>>> <https://youtu.be/GjpjE5pMZMI?t=1727> : "*Anywhere that i write the 
>>>>>> word todo in square brackets, so link to the tiddler todo, gets 
>>>>>> automatically pulled in here"* -here being presumably TODO tab of 
>>>>>> "Write" feature, since that is the context.  I have tried this a number 
>>>>>> of 
>>>>>> ways -with square brackets of both types: single (would have to be by 
>>>>>> some 
>>>>>> magic i don't see, but since you didn't say "DOUBLE"...) and double 
>>>>>> (creating a missing tiddler, which i then activated, tagged "Stub"), 
>>>>>> whether as TODO uppercase or lower... Nothing shows up as expected in 
>>>>>> that 
>>>>>> tab, at all.
>>>>>>
>>>>>> So what am i missing here, i wonder?
>>>>>>
>>>>>> /walt
>>>>>>
>>>>>> On Sunday, April 18, 2021 at 3:31:11 PM UTC+1 Soren Bjornstad wrote:
>>>>>>
>>>>>>> Oh, to convert a single-file wiki to Node.js, all you need is:
>>>>>>>
>>>>>>> tiddlywiki --load path/to/single/file.html --savewikifolder 
>>>>>>> path/to/output/folder
>>>>>>>
>>>>>>> You could even do this as a first step in the script above, if you 
>>>>>>> wanted to normally edit in single-file mode but use the automated build.
>>>>>>>
>>>>>>> On Sunday, April 18, 2021 at 9:02:28 AM UTC-5 ludwa6 wrote:
>>>>>>>
>>>>>>>> Thank-you Soren, but to be clear: I'm working in single-file mode, 
>>>>>>>> since i was unable to find a way to convert your file to node.js, 
>>>>>>>> though 
>>>>>>>> that would probably make for a more elegant solution [*]... But the 
>>>>>>>> "manual" method you propose below (with slight adaptation, see below) 
>>>>>>>> is 
>>>&g

[tw5] Re: Adding ' tabindex="-1" ' via template?

[Soren Bjornstad]

Petri,

Are you aware you can use the down arrow key to select items in that list? 
(You need 5.1.23 or higher I think.)

On Monday, September 27, 2021 at 5:16:56 AM UTC-5 Petri M. wrote:

> I am trying to remove some extra tabbing when I do ctrl+L and search for a 
> tiddler and try to link to it. Now it tabs through the search "tabs" first 
> and then goes to the list. I think I can just remove that with the CSS 
> attribute tabindex="-1" but I have no idea how to actually do it. I tried 
> to set buttonTemplate so transclude my own template which would then have 
> this command in it but I can't seem to get it to work. I don't think the 
> template adds the attribute to the button itself, just to the content 
> inside of the button.
>
> How can I achieve this?
>
> Thanks,
> Petri
>

-- 
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/96c5f928-d691-479f-9c02-83964fbee202n%40googlegroups.com.

[tw5] Re: Question about styling tags

[Soren Bjornstad]

On Saturday, September 25, 2021 at 9:00:53 AM UTC-5 ju...@gmail.com wrote:

> So, just a few questions, first one being is, how could I change the x for 
> removing a tag to match the font color of the text inside the tag? 


Try this in a tiddler tagged $:/tags/Stylesheet:

svg.tc-image-close-button {
fill: <>;
}

(Note: there's a color in the palette called `tag-foreground`, but it 
doesn't appear to actually be used for the tag foreground, rather 
`foreground` is. The <> macro retrieves the hex code of a color by 
name from the current palette; go to $:/PaletteManager to see the list of 
colors.)

Also, would it be possible to add a border around the tags with the same 
> color as the tag itself, but with say, 50% opacity, so the background would 
> make the border darker or lighter to prevent the tag from blending in with 
> the tiddler background?
>

I don't know enough CSS to know how to do this kind of border off the top 
of my head, but you would apply a similar styling rule to the class of the 
tag. I would start with tc-tag-label. The trick is to open your browser's 
devtools and click on the thing you want to style on the "Elements" tab, 
and you should be able to poke around from there to figure out what to 
style. Then it's just any tiddler tagged $:/tags/Stylesheet to get it 
included in the global stylesheet for the page.

-- 
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/38a575bf-76f0-4844-91c6-db6705a4af2dn%40googlegroups.com.

[tw5] Re: List not working anymore when I enter // into the text

[Soren Bjornstad]

The immediate solution is to use *ext* for your Steam link:

[ext[steam://rungameid/251570]]

This syntax is described in Linking in WikiText 
.

If you didn't want a link, another solution would be to use `single 
backticks` around the text containing the //.

This problem actually doesn't have anything to do with the fact that you're 
writing a list. //, outside of a few situations where TiddlyWiki recognizes 
a URL (the steam: protocol is evidently not one of them) starts italics, as 
you've found. Italics are an inline-mode element (that is, they can't 
continue across multiple paragraphs, list items, and so on). With an 
inline-mode element open, other block-level formatting (list, code block, 
paragraph, etc.) is suspended until the italics are closed. See Block Mode 
and Inline Mode 
 for 
details on this.

On Wednesday, September 22, 2021 at 4:32:53 PM UTC-5 heusmich wrote:

> Hi @all,
>
> I´m currently creating a guideline with the help of the list function in a 
> tiddler. That means I use this formatting:
>
> * Item 1
> ** Subitem 1
> ** Subitem 2
> * Item 2
> * Item 3
> ...
>
> Now I want to enter a path to start a steam game as an example (for 
> example the path steam://rungameid/251570). But when I enter this into the 
> text, the list function is not working anymore. This means that all list 
> items above of this link are working but after the link they are all 
> written as text in italic and I can´t see the dots of the list.
> I found out that the two // are the problem. When I remove one of them, 
> the list is working again.
> So my question is, can I prevent somehow that the two // are deactivating 
> the list function and creating an italic text? A link to a website 
> (https://...) can be entered everywhere in the text without any problems...
>
> Best regards
> heusmich
>

-- 
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/4f87d879-d9ec-45ad-beb9-00e0a4f8a3edn%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

[Soren Bjornstad]

The Zettelkasten edition I talked about wanting to get together is public 
now. It's still alpha-ish, but in much better shape than the version I 
published here. You can find a link and continue discussion of it on this 
thread:

https://talk.tiddlywiki.org/t/introducing-tzk-tiddlyzettelkasten-edition/834

On Monday, June 28, 2021 at 12:51:14 PM UTC-5 Soren Bjornstad wrote:

> Probably did, but right now that one is more or less just < "[[OpenQuestion]backlinks[]]">> -- there's no special functionality for 
> selecting questions out of the tiddlers. That's something I'd like to 
> improve in the future.
>
> On Monday, June 28, 2021 at 12:12:30 PM UTC-5 mark.cu...@gmail.com wrote:
>
>> Is there any chance your filter missed the OpenQuestions tiddler as well?
>>
>> On Sunday, April 18, 2021 at 11:55:35 AM UTC-4 Soren Bjornstad wrote:
>>
>>> Looks like my filter missed the TODO tiddler, which should contain:
>>>
>>> \define todore() \[\[TODO\]\]:
>>> \define splitre() [\.\?!]
>>>
>>> To add a TODO item to this list, simply link to [[TODO]].
>>>
>>> 
>>> <$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer>
>>>   <$list 
>>> filter="[get[text]splitregexplast[]splitregexpfirst[]]"
>>>  
>>> variable=inner>
>>>   <$link to=<>/>
>>> ''TODO:'' <>.
>>> 
>>> 
>>> 
>>>
>>> On Sunday, April 18, 2021 at 10:23:28 AM UTC-5 ludwa6 wrote:
>>>
>>>> Good to know, Soren, but first i have to get the basics under control, 
>>>> like: TODO items!  
>>>>
>>>> About that, you say in your video at 28'47" 
>>>> <https://youtu.be/GjpjE5pMZMI?t=1727> : "*Anywhere that i write the 
>>>> word todo in square brackets, so link to the tiddler todo, gets 
>>>> automatically pulled in here"* -here being presumably TODO tab of 
>>>> "Write" feature, since that is the context.  I have tried this a number of 
>>>> ways -with square brackets of both types: single (would have to be by some 
>>>> magic i don't see, but since you didn't say "DOUBLE"...) and double 
>>>> (creating a missing tiddler, which i then activated, tagged "Stub"), 
>>>> whether as TODO uppercase or lower... Nothing shows up as expected in that 
>>>> tab, at all.
>>>>
>>>> So what am i missing here, i wonder?
>>>>
>>>> /walt
>>>>
>>>> On Sunday, April 18, 2021 at 3:31:11 PM UTC+1 Soren Bjornstad wrote:
>>>>
>>>>> Oh, to convert a single-file wiki to Node.js, all you need is:
>>>>>
>>>>> tiddlywiki --load path/to/single/file.html --savewikifolder 
>>>>> path/to/output/folder
>>>>>
>>>>> You could even do this as a first step in the script above, if you 
>>>>> wanted to normally edit in single-file mode but use the automated build.
>>>>>
>>>>> On Sunday, April 18, 2021 at 9:02:28 AM UTC-5 ludwa6 wrote:
>>>>>
>>>>>> Thank-you Soren, but to be clear: I'm working in single-file mode, 
>>>>>> since i was unable to find a way to convert your file to node.js, though 
>>>>>> that would probably make for a more elegant solution [*]... But the 
>>>>>> "manual" method you propose below (with slight adaptation, see below) is 
>>>>>> sufficiently well-automated, it makes my workflow relatively painless, 
>>>>>> as 
>>>>>> follows:
>>>>>>
>>>>>>1. In TiddlyDesktop (where i am managing a fair mitt-full of TW5 
>>>>>>instances), finish my days edits with a review to ensure tag "Public" 
>>>>>> is on 
>>>>>>all the right tiddlers, and none other;
>>>>>>2. In $:/AdvancedSearch, run the filter-  
>>>>>>[tag[Public]!is[system]]  -and upload the result set as .json, to...
>>>>>>3. Drag & drop that .json file into the my local PUBLIC instance 
>>>>>>(subset of the above), which is they synced to...
>>>>>>4. My github.io repo <https://ludwa6.github.io/> : pull from 
>>>>>>there (just to ensure there are no conflicting edits), then 
>>>>>>commit/comment/push changes online.
>>>>>>
>>>>>> NB: I'm using Atom 

[tw5] Re: List sort by count field operator

[Soren Bjornstad]

Can you maybe upload a small wiki with some tiddlers that could serve as an 
example? It's pretty difficult to go into more depth without any data to 
try it on.

On Friday, August 27, 2021 at 9:47:27 PM UTC-5 barro...@gmail.com wrote:

> Thank you for your response, you have always been helpful.
>
> I'm still working on it and studying your thread (Retrieving the number of 
> link paths to a tiddler, 
> https://groups.google.com/g/tiddlywiki/c/c_f9bfnp2KY/m/lMfu_WIpBAAJ ) 
> where you ranked tiddlers by number of backlinks.
>
> Where I'm going wrong-- I don't think a single list/filter (without a 
> subfilter or second filter) will  let me sort by the count I'm aiming for, 
> since the count of the root filter would just be the number of different 
> values of the field being filtered, not the count of tiddlers having each 
> different value.  Putting in the each[]get[]count[] in the sortsub with any 
> of the suffixes is producing any result.
>
> What I'm starting out with, this gives an alphabetical listing (rather 
> than the default listing without a sort which I assume is by field creation 
> time but not sure if that's so):
>
>
>
> \define fldcntvar() [:filter[count[]]
>
> <$list 
> filter="[tag[zz@]each[zztopic]get[zztopic]subsort:integer]"><$view
>  
> field="title"/> - <$count 
> filter="[tag[zz@]zztopic]"/>
>
> I also tried $set and $var for the sortsub filter but stuck with macro 
> definition after seeing your work.
> On Wednesday, August 25, 2021 at 9:16:08 AM UTC-4 Soren Bjornstad wrote:
>
>> Unless I'm misunderstanding, sortsub[] with a filter containing count[] 
>> should do what you need. You might need to add the *integer* suffix to 
>> it though, or else it will sort the numbers alphabetically and not produce 
>> a very useful sort.
>>
>> On Wednesday, August 25, 2021 at 6:05:57 AM UTC-5 barro...@gmail.com 
>> wrote:
>>
>>> I saw references to sorting list results by the count operator but 
>>> didn't find the actual threads/posts about the method.
>>>
>>> I assume it will require a subfilter, because in a root list filter the 
>>> count just returns the count of the list results, not counts for each of 
>>> the list results.  
>>>
>>> The sortsub operation worked with anything involving the titles of the 
>>> list results (such as length) but not the count operator.
>>>
>>> What I'm aiming for is ranking/sorting results (greatest to lowest 
>>> counts) of such lists as tags and tiddlers tagged with each or
>>>
>>> fields and how many tiddlers have each value of a particular field such 
>>> as below:
>>>
>>> <$list filter="[tag[zz]each[zzfield1]get[zzfield1]]"><$view 
>>> field="title"/> - <$count filter="[tag[zz] 
>>> zzfield1]"/>
>>>
>>> Any directions to threads about such esoteric wikiery would be greatly 
>>> appreciated...
>>>
>>

-- 
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/d00d1016-3899-4886-9c4c-5eae92328a51n%40googlegroups.com.

[tw5] Re: Transclusion through template --- preserve wikitex formatting

[Soren Bjornstad]

For background on what's going on here, see Block Mode and Inline Mode 
 in *Grok 
TiddlyWiki.*

On Thursday, August 26, 2021 at 4:16:21 AM UTC-5 Sandip Deshmukh wrote:

> Thanks. That worked perfectly.
>
>
> On Thursday, August 26, 2021 at 12:04:46 PM UTC+5:30 Eric Shulman wrote:
>
>> On Wednesday, August 25, 2021 at 10:39:54 PM UTC-7 Sandip Deshmukh wrote:
>>
>>> My `ContactInformation'  tiddler contains:
>>> <$list filter="[contains:participants!sort[on]]">
>>>   <$link />
>>>   {{!!text}}
>>>  
>>>
>> The wikitex formatting in 'KG More1' is lost when transcluded.
>>>
>> How do I ensure that it is preserved?
>>>
>>
>> replace {{!!text}} with <$transclude mode="block"/>
>>
>> enjoy,
>> -e
>>
>

-- 
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/957f279a-7517-448b-acf7-fdb7b2b705f5n%40googlegroups.com.

[tw5] Re: List sort by count field operator

[Soren Bjornstad]

Unless I'm misunderstanding, sortsub[] with a filter containing count[] 
should do what you need. You might need to add the *integer* suffix to it 
though, or else it will sort the numbers alphabetically and not produce a 
very useful sort.

On Wednesday, August 25, 2021 at 6:05:57 AM UTC-5 barro...@gmail.com wrote:

> I saw references to sorting list results by the count operator but didn't 
> find the actual threads/posts about the method.
>
> I assume it will require a subfilter, because in a root list filter the 
> count just returns the count of the list results, not counts for each of 
> the list results.  
>
> The sortsub operation worked with anything involving the titles of the 
> list results (such as length) but not the count operator.
>
> What I'm aiming for is ranking/sorting results (greatest to lowest counts) 
> of such lists as tags and tiddlers tagged with each or
>
> fields and how many tiddlers have each value of a particular field such as 
> below:
>
> <$list filter="[tag[zz]each[zzfield1]get[zzfield1]]"><$view 
> field="title"/> - <$count filter="[tag[zz] 
> zzfield1]"/>
>
> Any directions to threads about such esoteric wikiery would be greatly 
> appreciated...
>

-- 
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/6e1630c7-9ee1-42fd-8a5f-e5012a12fd82n%40googlegroups.com.

Re: [tw5] Talk TiddlyWiki and the "discobot"

[Soren Bjornstad]

That worked, thanks.

On Friday, August 20, 2021 at 9:33:09 AM UTC-5 PMario wrote:

> Hi Soren
> That's strange. You have to send it a new message like so: 
>
> [image: new-message-01_.gif]
>
> Then add the user, a subject and some text. The text has to be more than 
> 20 chars ;)
> *The important part it the "start tutorial" text*
>
> [image: new-message-02_.gif]
>
> have fun!
> 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/869e80be-8837-4dfa-8971-acb247c97ccen%40googlegroups.com.

[tw5] Re: seeing what the transfering of tiddlywiki to a more self-coded platform can look like

[Soren Bjornstad]

On Thursday, August 19, 2021 at 4:23:05 PM UTC-5 jamm... wrote:

> Thanks for clarifying, Tones and Soren. I had the impression that 
> TiddlyWiki was more cookie cutter, or could be if I didn't add or alter 
> code. "A no-code personal wiki system," I heard TW called. But yes, I was 
> seeing this as a future-proofing mechanism where I might want to migrate 
> some- or everything stored in TiddlyWiki to a different platform in the 
> future.


There is a bit of a dilemma here in that the more of TiddlyWiki's features 
you take advantage of, the harder it will be to migrate to another system – 
but if you don't take advantage of all TiddlyWiki's features, then you 
might be misled into thinking it won't meet your needs by itself when it 
actually will.

On the other hand, I don't think “cookie-cutter” is a good characterization 
of TiddlyWiki at all. In fact I would say it's exactly the opposite…the 
cool thing about TW is that without having to go into a “real” programming 
language, you can make it do essentially whatever you want. You might check 
out my Zettelkasten , for 
instance, which I've built up from empty.html to a powerful custom platform 
over time. I have written only a couple of tiny snippets of JavaScript for 
that wiki, everything else is just wikitext. And since both the code and 
the data are within a single system, it is extremely easy to tweak things 
as you go along.

I'm with Tones in that you're probably best off diving into TiddlyWiki and 
not worrying about portability. Your stuff certainly isn't getting *trapped* in 
TiddlyWiki, you might just have to figure out how to manually translate 
some TiddlyWiki idioms to a new medium. And you'll probably be pleasantly 
surprised what you can do with the TiddlyWiki medium – if you let yourself 
dive in and take advantage of everything it has to offer.

-- 
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/e80f317d-4702-441c-a935-e876de71d3b4n%40googlegroups.com.

Re: [tw5] Talk TiddlyWiki and the "discobot"

[Soren Bjornstad]

Mario, I checked and I never received this message for some reason. I have 
0 messages and I'm pretty sure I never went in and deleted it. Is there 
another way to get to the tutorial?

On Thursday, August 19, 2021 at 2:51:28 PM UTC-5 PMario wrote:

> On Thursday, August 19, 2021 at 9:43:13 PM UTC+2 Folke Hermansson Snickars 
> wrote:
>
>>
>> How can I come back to the discobot  tutorial if I missed it when I 
>> joined?
>>
>
> You should still have the message in your in-box. 
>
> You can restart the "conversation" when you reply with : start tutorial 
>
> [image: discobot-01.gif]
>
> -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/9d8cef09-61d3-4221-9708-39ee48ae7d76n%40googlegroups.com.

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

[Soren Bjornstad]

Posted here <https://github.com/Jermolene/TiddlyWiki5/issues/5964>, thanks 
everyone.

On Thursday, August 19, 2021 at 2:08:23 AM UTC-5 PMario wrote:

> On Thursday, August 19, 2021 at 12:33:29 AM UTC+2 Soren Bjornstad wrote:
>
> If I'm misunderstanding, please correct me (and can you link the 
>> discussions on GitHub?).
>>
>
> Sorry, I was talking about field values. 
>
> You are right, we should trim field names. There is some time left to do 
> so. But this question should be raised as a github issue. 
>
> -m
>

-- 
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/1f1cadce-63b1-43c1-9bc6-1f3399f770can%40googlegroups.com.

[tw5] Re: seeing what the transfering of tiddlywiki to a more self-coded platform can look like

[Soren Bjornstad]

As Tones said, I think we need a bit more information about what you're 
hoping to accomplish to give a complete answer. Are you seeing this as a 
future-proofing mechanism where you *might* want to migrate something 
stored in TiddlyWiki to a different platform in the future? Or you want to 
use TiddlyWiki as a CMS and then publish using a different tool? Or 
something else?

On a straightforward level, it's possible to quickly render some or all 
tiddlers to HTML, at which point you can post-process them using whatever 
tooling you want. I've been using this to crosspost my sabbatical updates 
from my Zettelkasten 
 to my 
Jekyll blog 
, 
using the following rule in my Makefile:

sabbatical_updates := $(wildcard 
zettelkasten_dir/tiddlers/SabbaticalUpdate*)
sabbatical_files: $(sabbatical_updates)
rm -rf /tmp/twout
cd $(zettelkasten_dir) && tiddlywiki --output /tmp/twout --render 
"[prefix[SabbaticalUpdate/]]" "[is[tiddler]addsuffix[.html]]" "text/html" 
'$$:/sib/Templates/Export/SabbaticalUpdateCabCrosspost'
python3 automation/crosspost-sabbatical-updates.py 
/tmp/twout/SabbaticalUpdate/*

The Python script is about 70 lines and primarily sets up a YAML header 
with appropriate metadata so Jekyll understands what to do with the post. 
This is also the purpose of the 
$:/sib/Templates/Export/SabbaticalUpdateCabCrosspost template -- it embeds 
certain fields in the HTML where this script can retrieve it. If you 
preferred, I think you could use pandoc at this point to convert back to 
Markdown or a similar format; since I'm keeping my source of record in 
TiddlyWiki, I'm fine just leaving the posts as HTML in Jekyll.

Of course, if you take advantage of dynamic features of TiddlyWiki that 
can't be represented as HTML with 100% fidelity, e.g. dynamic lists based 
on filters or displays of backlinks, you'll end up losing some 
functionality when you do this.

On Wednesday, August 18, 2021 at 2:31:10 PM UTC-5 jamm...@gmail.com wrote:

> I'm looking to see what the transfering of tiddlywiki to a more self-coded 
> platform, such as jekyll, gatsby, or others, can look like. My concern is 
> the transition being difficult, long, etc. Any resources?
>

-- 
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/9fd19361-30fe-4222-b642-7aaf923c9154n%40googlegroups.com.

[tw5] Re: Import tiddlers w/ json including custom fields

[Soren Bjornstad]

By the way, when I said that the example "imported correctly" for me, it 
indeed did not include some of the fields...for some reason I foolishly 
decided not to mention that when I imported it even though I noticed. I am 
not however seeing the message jkm was where $:/Import said there were no 
tiddlers to import. So I think there are two separate problems here, the 
existence of duplicate tiddlers *and* some of the fields not being strings.

On Wednesday, August 18, 2021 at 6:46:35 PM UTC-5 TW Tones wrote:

> I can totally recommend Joshua's JSON mangler in cases likele this and csv.
>
>
>
> On Thursday, 19 August 2021 at 04:22:26 UTC+10 jkm...@gmail.com wrote:
>
>> New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23
>>
>> I'm able to import tiddlers from json with the title and text fields.  
>> But when I try to do it with a custom field the import tiddler shows no 
>> items to import.  All my custom fields begin with *kba* and some 
>> additional alphanumeric characters.  The json is valid according to 
>> jsonchecker.com.  Is this permitted?  Do I need to enable a feature or 
>> preconfigure a system component?  I've done a few searches in the group but 
>> didn't see anything that applied.  All help is appreciated.
>>
>> Imports:
>> [
>>   {
>> "title": "19464",
>> "text": "How to change the default root password"
>>   },
>>   {
>> "title": "20508",
>> "text": "Best Practices"
>>   }
>> ]
>>
>> Doesn't import:
>> [
>>   {
>> "title": "19464",
>> "text": "How to change the default root password",
>> "kbalink": " https://www.someplace.net/ 19464",
>> "kbarating": 3,
>> "kbasev": 0,
>> "kbasource": "LKBA",
>> "kbastale": 0,
>> "kbatweak": "",
>> "kbatype": "How To"
>>   },
>>   {
>> "title": "20508",
>> "text": "Best Practices",
>> "kbalink": "https://www.someplace.net/20508;,
>> "kbarating": 5,
>> "kbasev": 0,
>> "kbasource": "LKBA",
>> "kbastale": 0,
>> "kbatweak": "",
>> "kbatype": "Info"
>>   }
>> ]
>>
>

-- 
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/1332b6a2-37ab-4d59-a7a0-dc626f78394en%40googlegroups.com.

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

[Soren Bjornstad]

Mario,

I don't think the thread you linked is relevant. I'm talking about field 
*names*, not field values. And I don't see how it would break backwards 
compatibility with 5.1.x, because 5.1.x didn't allow *any* spaces in field 
names.

If I'm misunderstanding, please correct me (and can you link the 
discussions on GitHub?).

On Wednesday, August 18, 2021 at 3:57:26 PM UTC-5 PMario wrote:

> On Wednesday, August 18, 2021 at 10:38:29 PM UTC+2 Soren Bjornstad wrote:
>
>> I'll preface this by saying this probably belongs in a GitHub issue, and 
>> I'll be happy to create one over there if we want one. But wanted to get 
>> people's thoughts first, and ASAP because now is our last chance to do this 
>> without breaking backwards compatibility (once 5.2.0 is released, it would 
>> be pretty hard to change).
>>
>
> I think this won't happen because of backwards compatibility with 5.1.x. 
> There have been some discussions on github already. The conclusion was, we 
> keep the status quo and live with it. 
>
> There has been a discussion recently, where a user needed to be able to 
> add whitespace as needed. And the description of the usecase made sense. So 
> there are usecases. ... See: 
> https://groups.google.com/g/tiddlywiki/c/Cjy074MsfzM
>
> -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/6a244024-a0e2-4ff4-a855-cd72c190672en%40googlegroups.com.

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

[Soren Bjornstad]

Just realized some people might not be familiar with the term "leading and 
trailing whitespace"...I mean whitespace at the very beginning or end of 
the name. In the current prerelease, these are valid and distinct field 
names (with the quotes removed):

"my field"
" my field"
"my field "
"   my field  "

On Wednesday, August 18, 2021 at 3:38:29 PM UTC-5 Soren Bjornstad wrote:

> I'll preface this by saying this probably belongs in a GitHub issue, and 
> I'll be happy to create one over there if we want one. But wanted to get 
> people's thoughts first, and ASAP because now is our last chance to do this 
> without breaking backwards compatibility (once 5.2.0 is released, it would 
> be pretty hard to change).
>
> Would it make sense to *prohibit leading and trailing whitespace in field 
> names*, even though we now allow whitespace elsewhere? In the prerelease, 
> it's not possible to add such fields within the GUI, but you can import 
> tiddlers that contain such fields, or create them with an action or 
> $edit-text widget. Fields with leading or trailing whitespace are almost 
> impossible to distinguish within the GUI, since there is already whitespace 
> before and after the name when it's displayed.
>
> In addition, if we continue to prohibit leading and trailing whitespace, I 
> think we would be able to allow whitespace in between filter steps, which 
> is a common annoyance for new users (but maybe I'm missing something there).
>
> I can't think of any situation in which someone would *want* leading or 
> trailing whitespace in a field name, except maybe to integrate with another 
> system which allowed it for some reason – as evidenced by the fact that the 
> GUI doesn't even let you create such a field. At any rate, it seems much 
> more confusing than helpful. Unix filenames have suffered enormously 
> <https://dwheeler.com/essays/fixing-unix-linux-filenames.html> from being 
> overly permissive in what characters they allow, including leading and 
> trailing whitespace; my instinct tells me this is likely to be a continuing 
> irritation.
>
> On the minus side, someone would of course have to implement checks to 
> prevent these fields from being added.
>

-- 
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/70fbf57f-0f24-47f5-9170-427da36ac297n%40googlegroups.com.

[tw5] Should we prohibit leading and trailing whitespace in field names in 5.2.0?

[Soren Bjornstad]

I'll preface this by saying this probably belongs in a GitHub issue, and 
I'll be happy to create one over there if we want one. But wanted to get 
people's thoughts first, and ASAP because now is our last chance to do this 
without breaking backwards compatibility (once 5.2.0 is released, it would 
be pretty hard to change).

Would it make sense to *prohibit leading and trailing whitespace in field 
names*, even though we now allow whitespace elsewhere? In the prerelease, 
it's not possible to add such fields within the GUI, but you can import 
tiddlers that contain such fields, or create them with an action or 
$edit-text widget. Fields with leading or trailing whitespace are almost 
impossible to distinguish within the GUI, since there is already whitespace 
before and after the name when it's displayed.

In addition, if we continue to prohibit leading and trailing whitespace, I 
think we would be able to allow whitespace in between filter steps, which 
is a common annoyance for new users (but maybe I'm missing something there).

I can't think of any situation in which someone would *want* leading or 
trailing whitespace in a field name, except maybe to integrate with another 
system which allowed it for some reason – as evidenced by the fact that the 
GUI doesn't even let you create such a field. At any rate, it seems much 
more confusing than helpful. Unix filenames have suffered enormously 
 from being 
overly permissive in what characters they allow, including leading and 
trailing whitespace; my instinct tells me this is likely to be a continuing 
irritation.

On the minus side, someone would of course have to implement checks to 
prevent these fields from being added.

-- 
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/20fec6b1-1604-407b-9637-e11f1d749144n%40googlegroups.com.

[tw5] Re: Import tiddlers w/ json including custom fields

[Soren Bjornstad]

Your second example imports as expected for me. Is it possible tiddlers 
with the titles in your JSON already exist in the wiki? I believe there is 
a bug in 5.1.23 where it doesn't explain that to you in the import dialog 
and just silently skips them.

On Wednesday, August 18, 2021 at 1:22:26 PM UTC-5 jkm...@gmail.com wrote:

> New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23
>
> I'm able to import tiddlers from json with the title and text fields.  But 
> when I try to do it with a custom field the import tiddler shows no items 
> to import.  All my custom fields begin with *kba* and some additional 
> alphanumeric characters.  The json is valid according to jsonchecker.com.  
> Is this permitted?  Do I need to enable a feature or preconfigure a system 
> component?  I've done a few searches in the group but didn't see anything 
> that applied.  All help is appreciated.
>
> Imports:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password"
>   },
>   {
> "title": "20508",
> "text": "Best Practices"
>   }
> ]
>
> Doesn't import:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password",
> "kbalink": " https://www.someplace.net/ 19464",
> "kbarating": 3,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "How To"
>   },
>   {
> "title": "20508",
> "text": "Best Practices",
> "kbalink": "https://www.someplace.net/20508;,
> "kbarating": 5,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "Info"
>   }
> ]
>

-- 
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/1be11b96-c2e4-4985-aa3c-d8f364fcdd14n%40googlegroups.com.

[tw5] Re: Seeking common misunderstandings

[Soren Bjornstad]

Maybe this is derailing the thread, but I'm disinclined to post on 
Discourse when I'm looking for a broad audience (like in this post) since 
only a few people are over there so far. Is there anything we can do to to 
ease that? Is it possible to crosspost new threads from Discourse to GG for 
instance?

On Wednesday, August 18, 2021 at 9:35:14 AM UTC-5 saq.i...@gmail.com wrote:

> Yes that is exactly what I mean. The GG threads in Discourse are read only.
>
> It would help if people started new threads on Discourse, hopefully we 
> will see more of that in the next days.
> The plan is to migrate to Discourse and make this group read only after a 
> short period where we test out Discourse. So anyone that doesn't try using 
> Discourse in anger now will likely miss their chance to have a say in that 
> final decision.
> On Wednesday, August 18, 2021 at 4:30:33 PM UTC+2 Stobot wrote:
>
>> @saqimtiaz - I might be doing it wrong, but I haven't found a way to 
>> reply in Discourse to a GG thread, I assume you mean you'll start a new 
>> 'topic' in Discourse, or am I missing something? I only see the reply 
>> button in Discourse for Discourse-native conversations.
>>
>> This is making the "conversion" pretty painful. I'm monitoring Discourse, 
>> but for all replies I'm going into GG and finding the thread to reply to 
>> (like now).
>>
>> On Wednesday, August 18, 2021 at 10:16:04 AM UTC-4 saq.i...@gmail.com 
>> wrote:
>>
>>> Hi Soren,
>>>
>>> I posted a small list an hour ago but due to the vagaries of GG it 
>>> doesn't seem to have been posted. Re-writing is never fun but will do so 
>>> and post as a reply on Discourse a little later.
>>> Regards,
>>> Saq
>>>
>>> On Wednesday, August 18, 2021 at 3:30:43 PM UTC+2 Soren Bjornstad wrote:
>>>
>>>> I'm working on adding a chapter (or back-matter section, not sure yet) 
>>>> called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I 
>>>> have two sections:
>>>>
>>>>- Macros are not function calls
>>>>- Constant strings cannot be combined with transclusions
>>>>
>>>> Are there other common misunderstandings – in terms of incorrect mental 
>>>> models of how TiddlyWiki operates, or things one might expect to work that 
>>>> don't – that come up here or elsewhere that you'd like to see documented 
>>>> in 
>>>> such a section?
>>>>
>>>> Feedback on the drafts of the two existing sections would be welcome as 
>>>> well:
>>>>
>>>>
>>>> https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
>>>>   
>>>> <https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings>
>>>
>>>

-- 
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/b14548d5-e4b4-41cf-b9be-8e668cce1193n%40googlegroups.com.

[tw5] Seeking common misunderstandings

[Soren Bjornstad]

I'm working on adding a chapter (or back-matter section, not sure yet) 
called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I have 
two sections:

   - Macros are not function calls
   - Constant strings cannot be combined with transclusions

Are there other common misunderstandings – in terms of incorrect mental 
models of how TiddlyWiki operates, or things one might expect to work that 
don't – that come up here or elsewhere that you'd like to see documented in 
such a section?

Feedback on the drafts of the two existing sections would be welcome as 
well:

https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
  


-- 
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/af072926-33d7-4414-840e-e0741671f52bn%40googlegroups.com.

[tw5] Re: I Think I Hacked TiddlyWiki

[Soren Bjornstad]

On Tuesday, August 17, 2021 at 9:53:28 AM UTC-5 flanc...@gmail.com wrote:

> Mark, 
>
> The scenario I had in mind was: Person A (attacker), adds malicious code 
> to his TW instance, which is accessible via the web through GitHub pages, 
> or something similar. He then shares his wiki link with Person B, who 
> unknowingly goes to take a look at Person A's wiki. On doing this, Person B 
> then has this malicious JS execute on his end, thereby hacking/infecting 
> him.
>

I'm still confused about this scenario. If we're not talking about 
inserting the code into someone else's wiki via XSS or something, how does 
TiddlyWiki allow anything here that an arbitrary website wouldn't? If a 
malicious user can post a page on the web and make the target go to it, 
then surely anything that a browser allows is fair game, and if there's 
fault here it should lie with the web browser, not TiddlyWiki. Because even 
if TW changed to disallow this, surely the malicious user could just revert 
that change in their own fork of TiddlyWiki and build their malicious wiki 
on that TW edition?

I'd be more concerned about people being tricked into importing a tiddler 
that contained code like this.

-- 
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/6b8a8e85-5545-4812-a266-b4fdffbe9937n%40googlegroups.com.

[tw5] Re: how to set a global variable with a tiddler field value

[Soren Bjornstad]

vpl,

First of all, the syntax for incorporating a variable into a filter 
expression is not <> but :

\define test_project() {{{ [get[projectId]] }}}

However, this still may not work, depending on how you use the macro. It's 
tempting to think of macro transclusions as "function calls", where when 
you say <> you get the result of evaluating their contents as 
wikitext. But this is not how macros work – instead, *the exact text of the 
macro* (with any $text substitutions$ the macro might include) is inserted 
wherever the <> is used, which in this case is a filter 
expression in triple curly braces.

Now, this will still work fine if you just say, for instance:

<>

In this case, TW replaces <> with {{{ 
[get[projectId]] }}}, then sees that wikitext in the body of a 
tiddler, evaluates it, and gets the project ID. But it won't work if you 
try to use it within another filter expression, or as the value of an HTML 
or widget attribute, e.g., suppose you had a tiddler whose title was this 
project ID and wanted to transclude it:

<$transclude tiddler=<>/>

In this case, TW will be looking for a tiddler called "{{{ 
[get[projectId]] }}}", and it presumably won't find it.

If you need to, you can get around this with the $wikify widget:

<$wikify name="myProjectId" text=<>>
  <$transclude tiddler="myProjectId"/>


In this case, you explicitly tell TW to evaluate the wikitext "{{{ 
[get[projectId]] }}}", then use the result to transclude the 
appropriate tiddler.

You can read more on this in the Wikification section 
 of *Grok TiddlyWiki*.
On Tuesday, August 17, 2021 at 9:56:51 AM UTC-5 vpl wrote:

> Hi,
>
> I want to define a global variable in my script with the value contained 
> into a tiddler field
> When I hard code the global variable like
>
> \define test_project() project-1
>
> I can use the <> variable without issue 
>
> But when I want this <> to be initialised to a tiddler's  
> field like the following this does not work
>
> \define test_project() {{{ [<>get[projectId]] }}}
>
> Any "magic" idea ..??
>
> Thanks a lot for your support
>
> Regards vpl
>

-- 
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/0cdcb9ac-2f0a-4f50-a6a8-fd9dfac7819cn%40googlegroups.com.

Re: [tw5] Better indexes through semantic modeling

[Soren Bjornstad]

On Friday, August 13, 2021 at 3:08:36 AM UTC-5 Mohammad wrote:

>  What do you think if we use a small section in a tiddler to store tiddler 
> summary or description in the text field (tiddler body)?
>

I guess I have too much of a programmer mind to like manually yanking 
things out of somewhere instead of just putting it in a separate field. But 
it's great to have the option.
 

> 3. no need to duplicate text
>

Maybe I'm being dense, but how would this help us avoid duplicating text? 
Couldn't we just as easily transclude the separate field into the text 
field if the summary sentence made sense as part of that text? I do that 
all the time.

-- 
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/13e0aef0-0daa-4be8-8721-432c34e13759n%40googlegroups.com.

Re: [tw5] Better indexes through semantic modeling

[Soren Bjornstad]

On Friday, August 13, 2021 at 6:39:04 AM UTC-5 Mohammad wrote:

> Soren
> Please check the filters in given examples, there are some other cases of 
> imbalanced square brackets!
>

Thanks, I found two (the $list one you quoted in another post and one other 
one) and these will be fixed when I rebuild the site later today. To be 
clear, these are intended to give a rough idea of how the system would 
work, not be fully functional examples, so that's why I obviously haven't 
tested them. :)

>
>1. Why is there not anything about tags? Entries replicate tags in 
>Tiddlywiki (but not necessarily)
>
> You certainly could use tags to implement entries, but I think links are 
easier to type and provide more context about why we're linking to the 
entry, which is part of the benefit of this system. Plus there could be 
thousands of entries in a large document, and nobody likes having thousands 
of tags in one TiddlyWiki.

Other options would be totally feasible, though! But the post isn't really 
about TiddlyWiki, and it was already 6,000 words, so I didn't think it was 
a good place to get into this kind of implementation detail.

>
>1. Some concepts with given scripts are confusing like Nearby lists
>
> Example
>
> We can similarly replicate Tabularium’s Nearby list on loci. On the locus 
> view template, we simply list all of the index entries that link to the 
> current locus:
>
> <>
>
>
>
> So this means we have a view template for locus, means command is only 
> works with tiddler tagged Locus
> Then [all[current]backlinks[]tag[Entry]] will list all entries (e.g tag 
> with Entry refer (has link) to current Locus!
> This means, an Entry shall have a link to a Locus?! Means in a tag tiddler 
> we refer to a Locus tiddler! This is confusing!
>

Yep, this example is wrong – it was supposed to say links[]. I will correct 
that as well.
 

> By the way, I enjoyed your writeup and I think it needs some working 
> example to be better understood!
>

I hope this will be a preview for a working system later!

-- 
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/810d53b9-225a-4755-818e-2ca9b762793cn%40googlegroups.com.

[tw5] Re: Better indexes through semantic modeling

[Soren Bjornstad]

*Springer*, that's really cool, I don't think I've ever seen that 
particular layout before! I do a similar thing to your “tldr” in my 
Zettelkasten, extending the “description” field to non-system tiddlers and 
displaying it at the top next to the gem icon if present:

[image: ksnip_20210812-125810.png]

*TT*, I'm puzzled where you got the idea that I think book indexes were/are 
a poor tool, or lacking in either authorial effort or utility. Are you able 
to point to location(s) in the post which are “inaccurate” or give you that 
impression? If so, I would like to correct it, as that is the exact 
opposite of what I think. I've been compiling and using keyword indexes 
almost daily myself for about twelve years (almost half my life), and they 
are a powerful tool – not to mention thesauruses, concordances, 
encyclopedias, etc., as you point out. I wrote a guide on using indexes for 
your notes 
<https://thetechnicalgeekery.com/2013/06/the-complete-guide-to-indexing-your-paper-notes/>
 back 
in 2013. It's exactly because they're so good (and, I think, neglected 
nowadays) that I'm interested in expanding them.

And I think many of us today are too “computer exceptionalist”. Good ideas 
are mostly independent of medium, it's just that sometimes they're really 
hard, or a comparatively bad intuitive fit, in one medium, so they don't 
make a lot of sense there. Or to put it another way, a system like what I'm 
proposing would be totally doable even on paper...just *way* more 
time-consuming to create and maintain.

On Thursday, August 12, 2021 at 12:34:08 PM UTC-5 TiddlyTweeter wrote:

> Soren Bjornstad wrote:
>
>> Some of you all might be interested in this new post on my blog:
>>
>>
>> https://controlaltbackspace.org/notes/better-indexes-through-semantic-modeling/
>
>
>  It was well worth reading!
>
> *THE GOOD*
>
> Great example of logical working through to a satisfactory outcome.
>
> I complimented you before that your use of *visual illustrations* helps 
> earth the discussion really well!
> I think they definitely help folk who are not so versed in the conceptual 
> matrix you lay out.
>
> *THE BAD*
>
> TBH your comments about the Old Media of Books are simply inaccurate. 
>
> The Book has had (when required) very *good *indexing where authors chose 
> to do it.
> Think about the richness of the indices of Roget's Thesaurus. 
> Think about all those Biblical things that Dave Gifford and several 
> million other Christians sweat over. 
> Their  CONCORDANCES has been a venerable partner in print works for a very 
> long time.
>
> *THE UGLY*
>
> Nothing. Your basic thing is additive.
>
>
> The Good the Bad & The Ugly <https://youtu.be/aJCSNIl2Pls?t=164>
>
> Best wishes 
> TT
>

-- 
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/3a15ef51-dafb-49f5-ad0f-9f9ec743f128n%40googlegroups.com.

Re: [tw5] Re: Help with hovering tiddler pop-up in list

[Soren Bjornstad]

Not offhand. I've never used that plugin and didn't actually try the code 
after making the syntax change, so if what you were initially trying to do 
wasn't the right thing, it wouldn't work now either. :-)

You might create a small wiki that demonstrates what you're trying to do 
and what the problem is and upload it here – then we can take a look at the 
problem without having to do a bunch of extra setup work on our end and 
worrying about what small details we might have missed.
On Wednesday, August 11, 2021 at 5:14:47 PM UTC-5 n...@noanoa.space wrote:

> Thank you so much. (I’m still adjusting to this syntax!) I just tried 
> copying and pasting your code, but only a blank white box comes up when I 
> hover. Any idea what could be going wrong?
>
> Noa,
>
> You want:
>
> <$list filter="[tag[control]]">
> <$macrocall $name="hoverTiddler" tiddler1={{!!title}} 
> tiddler2={{!!text}}/> 
> 
>
> You can only use constant values, not {{field transclusions}}, with the 
> double-angle bracket <>. For {{field}} or 
> <> transclusion support, you need the full widget as shown above. 
> Note that for this form, you need to specify the names of the macro 
> parameters, in this case *tiddler1* and *tiddler2.* You can find those in 
> the macro definition if you don't know them:
>
> \define hoverTiddler(*tiddler1*,*tiddler2*)
>   ...
> \end
>
> On Monday, August 9, 2021 at 7:47:42 PM UTC-5 n...@noanoa.space wrote:
>
>> Hello, everyone,
>>
>> I just started using tiddlywiki today and I'm loving it! I'm trying to 
>> use this macro 
>> 
>>  
>> with dynamic lists to make a list or tiddlers where when you hover over 
>> each title, it shows a preview of the text inside that tiddler. I was 
>> trying it like this: 
>>
>> <$list filter="[tag[control]]">
>> <> 
>> 
>>
>> but that doesn't work (creates two new tiddler links: {{!!title}}, and 
>> {!!title}})
>>
>> Does anyone have any solutions to this? Thanks so much and please let me 
>> know if I can clarify anything (I'm obviously still learning how to use all 
>> of this)!
>>
>> -Noa
>>
> -- 
> 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/_S7bUO_GTTM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> tiddlywiki+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/6f972e8c-7e72-48c4-92ea-b1481d19f139n%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/00635ba4-2d1c-40f8-8e49-609035762e2fn%40googlegroups.com.

[tw5] Better indexes through semantic modeling

[Soren Bjornstad]

Some of you all might be interested in this new post on my blog:

https://controlaltbackspace.org/notes/better-indexes-through-semantic-modeling/

It's a proposal for a system for indexing large documents based on a 
hypertext graph, including a discussion of a possible TiddlyWiki prototype. 
Warning: 6,000+ words.

-- 
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/99f6944e-75a7-4e40-a768-795c6cd98934n%40googlegroups.com.

[tw5] Re: Help with hovering tiddler pop-up in list

[Soren Bjornstad]

Noa,

You want:

<$list filter="[tag[control]]">
<$macrocall $name="hoverTiddler" tiddler1={{!!title}} tiddler2={{!!text}}/> 



You can only use constant values, not {{field transclusions}}, with the 
double-angle bracket <>. For {{field}} or 
<> transclusion support, you need the full widget as shown above. 
Note that for this form, you need to specify the names of the macro 
parameters, in this case *tiddler1* and *tiddler2.* You can find those in 
the macro definition if you don't know them:

\define hoverTiddler(*tiddler1*,*tiddler2*)
  ...
\end

On Monday, August 9, 2021 at 7:47:42 PM UTC-5 n...@noanoa.space wrote:

> Hello, everyone,
>
> I just started using tiddlywiki today and I'm loving it! I'm trying to use 
> this 
> macro 
> 
>  
> with dynamic lists to make a list or tiddlers where when you hover over 
> each title, it shows a preview of the text inside that tiddler. I was 
> trying it like this: 
>
> <$list filter="[tag[control]]">
> <> 
> 
>
> but that doesn't work (creates two new tiddler links: {{!!title}}, and 
> {!!title}})
>
> Does anyone have any solutions to this? Thanks so much and please let me 
> know if I can clarify anything (I'm obviously still learning how to use all 
> of this)!
>
> -Noa
>

-- 
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/6f972e8c-7e72-48c4-92ea-b1481d19f139n%40googlegroups.com.

[tw5] Re: cannot transclude a tiddler name built from inside a macro

[Soren Bjornstad]

The links I gave you were to my TiddlyWiki textbook, not the TW 
documentation. It might not be "self-contained" since it's intended to be 
in the context of the whole course, but I think you'll find it more useful 
than the TW documentation at your skill level.

On Sunday, August 8, 2021 at 1:27:08 PM UTC-5 CarloGgi wrote:

> Yes Soren, you are right: I have little understanding of the inner gears 
> of text substitution and wikification in TW, nor did I find a thorough, 
> comprehensive and self-contained guide to the matter so far: all the TW 
> documentation I went through is a mess of scantly-explained (if ever), 
> loosely-consistent, scattered bits of information, and this is a pity 
> because the software has tremendous potentiality. Maybe you can point me to 
> some good documentation anyway, of which I would be grateful.
>
> Thanks and regards,
> CG
>
>
> On Sunday, August 8, 2021 at 8:22:13 PM UTC+3 Soren Bjornstad wrote:
>
>> I second CJ in saying that the {{{ [addsuffix[whatever]] 
>> }}} route is usually a better way to concatenate text, especially when you 
>> don't know much TiddlyWiki.
>>
>> You're getting bitten by not understanding text substitution 
>> <https://groktiddlywiki.com/read/#Text%20Substitution> and wikification 
>> <https://groktiddlywiki.com/read/#Wikification>, which are both quite 
>> complex and require you to understand how TiddlyWiki actually goes about 
>> processing macros and rendering tiddlers. In contrast, your intuition will 
>> usually work fine with filters.
>>
>> On Sunday, August 8, 2021 at 11:08:29 AM UTC-5 CarloGgi wrote:
>>
>>>
>>> Hallo,
>>> quite new to TW and I love it, though it is dramatically underdocumented 
>>> and the whole docs are an almost unusable mess.
>>>
>>> To my biggest astonishment, when I try to dynamically build the name of 
>>> a tiddler from inisde a macro, that macro output cannot be used from within 
>>> a transclude widget.
>>>
>>> \define getMeTiddlerName(a_suffix) <>$a_suffix$ 
>>>
>>> <$list filter="whateveFilterHere">
>>> <$transclude tiddler=<> /> 
>>> 
>>>
>>> In the example above, I obtain the tiddler's name by adding suffix 'EN' 
>>> to current tiddler, which the macro DOES, but then its output 
>>> <> doesn't make transclude widget behave as expected.
>>>
>>> I also tried many combinations of single/double quotes, as for instance 
>>> in:
>>>
>>> <$transclude tiddler="<>" /> 
>>>
>>> but no result at all: the transclude widget DOESN'T transclude the 
>>> dynamically-built tiddler SOMETIDDLERNAME_EN
>>>
>>> Not even the simpler version with hard-coded suffix works:
>>>
>>> \define getMeTiddlerName() <>_EN 
>>>
>>> <$list filter="whateveFilterHere">
>>> <$transclude tiddler=<> /> 
>>> 
>>>
>>> Nor does it using double quotes for 'tiddler' parameter inside 
>>> transclude widget:
>>>
>>> \define getMeTiddlerName() <>_EN 
>>>
>>> <$list filter="whateveFilterHere">
>>> <$transclude tiddler="<>" /> 
>>> 
>>>
>>> Thanks for helping, s frustrated!
>>>
>>> CG
>>>
>>

-- 
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/26075d79-3081-4fb1-a390-c25e1a112365n%40googlegroups.com.

[tw5] Re: Does anyone import Tailwind CSS into tiddlywiki?

[Soren Bjornstad]

Somewhat off-topic, but:
 

> BTW, the "period" in front of class names always confuses me, sometimes I 
> need it, and other times no - ?
>

Class names don't include a period, but you need a period when you're using 
it in a CSS selector (the start of a CSS rule in a stylesheet that comes 
before the {) to indicate that it's a class name rather than an HTML tag 
name. So it's 'class="whatever"' but '.whatever { color: blue; }'. If you 
said 'whatever { color: blue; }', then you would be trying to style all the 
'whatever' tags in the document instead of all tags of any kind that have 
the 'whatever' class assigned.

You also need the . for the @@ syntax in TiddlyWiki (e.g., '@@.whatever 
(text) @@') for similar reasons (otherwise you couldn't tell the difference 
between a style attribute like "color" and a class called "color").

-- 
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/7e0decf1-e9ae-4d70-8324-8cbc2029cb9fn%40googlegroups.com.

[tw5] Re: Notes from the Coalface: Pasting URL's with pretty title

[Soren Bjornstad]

>
> Um, there was no disagreement in this thread with Tones.
>
> Tones' initial post was about getting pretty links when the URL encoding 
> are ugly.  I think that's great.  *(Already a usual habit of mine, just 
> grabbing them links from the "Open" sidebar tab instead.)* 
>

It sounded to me like Tones also had an opinion on the existence of "ugly 
URLs," which is why I responded from back there, but maybe that was just me 
misreading the post.
  

> [A]re you both suggesting that it would be better to instead change URL 
> encoding so they don't have things like "#" and "%20" in them ?
>

No, I'm suggesting that when one has an opportunity to choose the format of 
a URL, one should choose one that uses as few internal IDs and special 
characters (since those turn into %-encoding) as possible. (I don't see any 
problem with # in itself, that has a clearly defined meaning and isn't 
ugly.) I do not think that TiddlyWiki is doing anything wrong here – I was 
just trying to explain what some people might consider an ugly URL.

-- 
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/783f4716-b5a2-4093-b5de-6484edbbb0a5n%40googlegroups.com.

[tw5] Re: cannot transclude a tiddler name built from inside a macro

[Soren Bjornstad]

I second CJ in saying that the {{{ [addsuffix[whatever]] 
}}} route is usually a better way to concatenate text, especially when you 
don't know much TiddlyWiki.

You're getting bitten by not understanding text substitution 
 and wikification 
, which are both quite 
complex and require you to understand how TiddlyWiki actually goes about 
processing macros and rendering tiddlers. In contrast, your intuition will 
usually work fine with filters.

On Sunday, August 8, 2021 at 11:08:29 AM UTC-5 CarloGgi wrote:

>
> Hallo,
> quite new to TW and I love it, though it is dramatically underdocumented 
> and the whole docs are an almost unusable mess.
>
> To my biggest astonishment, when I try to dynamically build the name of a 
> tiddler from inisde a macro, that macro output cannot be used from within a 
> transclude widget.
>
> \define getMeTiddlerName(a_suffix) <>$a_suffix$ 
>
> <$list filter="whateveFilterHere">
> <$transclude tiddler=<> /> 
> 
>
> In the example above, I obtain the tiddler's name by adding suffix 'EN' to 
> current tiddler, which the macro DOES, but then its output 
> <> doesn't make transclude widget behave as expected.
>
> I also tried many combinations of single/double quotes, as for instance in:
>
> <$transclude tiddler="<>" /> 
>
> but no result at all: the transclude widget DOESN'T transclude the 
> dynamically-built tiddler SOMETIDDLERNAME_EN
>
> Not even the simpler version with hard-coded suffix works:
>
> \define getMeTiddlerName() <>_EN 
>
> <$list filter="whateveFilterHere">
> <$transclude tiddler=<> /> 
> 
>
> Nor does it using double quotes for 'tiddler' parameter inside transclude 
> widget:
>
> \define getMeTiddlerName() <>_EN 
>
> <$list filter="whateveFilterHere">
> <$transclude tiddler="<>" /> 
> 
>
> Thanks for helping, s frustrated!
>
> CG
>

-- 
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/b17503a1-f60e-449c-ad1c-a811eb9f8238n%40googlegroups.com.

[tw5] Re: Notes from the Coalface: Pasting URL's with pretty title

[Soren Bjornstad]

I agree with Tones, URLs should be human-readable when possible...if 
they're not, they're ugly. That means they consist of actual words, not 
internal IDs and random strings of characters, when possible, and you can 
tell what each component in the path represents. A bunch of URL-encoded 
nonsense with %20 and so on is only human-readable if you know a lot about 
text encoding, and even then it's going to slow you down. There was a time 
in maybe the early aughts when most URLs were an unreadable mess, post 
titles used their ID numbers in the database, there were usually giant 
strings of query parameters after ?, etc. Then people got wise and started 
prioritizing URLs that people can understand and type again (maybe partly 
because search engines started taking that into account for ranking 
purposes).

But I think we're mixing up two concerns in this thread, the link text and 
the actual URL. Raw URLs are uglier than text explaining where they go in 
most cases, but that's a different question from the URL itself. In Tones' 
example, the actual URL is the same in both links (though I'll note my 
browser does convert the %20's to actual spaces on mouseover). 

On Sunday, August 8, 2021 at 1:15:19 AM UTC-5 cj.v...@gmail.com wrote:

> *"Although the link text looks nice, hover over it and look at the URL. 
> Yuck!"*
>
> Thanks, but I still don't understand where The Islander was going with 
> that.
>
> A URL is a URL.  Not quite sure how it could be made prettier, or why it 
> would matter when the link is pretty.
>
>
>
>
>
> On Sunday, August 8, 2021 at 2:50:41 AM UTC-3 TW Tones wrote:
>
>> Charlie;
>>
>> Use the permalink button you get 
>> https://tiddlywiki.com/prerelease/#Sort%20Filter%20Run%20Prefix thats 
>> Yuk in my view
>> Now control Panel, settings > tiddlywiki >  Display tiddler titles as 
>> links
>>
>> Now open the tiddler and highlight the title and copy, then past here Sort 
>> Filter Run Prefix 
>> 
>> Thats not yuck
>>
>> I think you may see it aint the beholder, its universal. Especially if 
>> you want to see the yuck one just mouse over.
>>
>> Regards
>> Tones
>>
>>
>> On Sunday, 8 August 2021 at 03:57:06 UTC+10 cj.v...@gmail.com wrote:
>>
>>> Yuck how?  What's a non-yuck URL?
>>>
>>> Understanding, of course, that yuck is in the eye of the beholder, and 
>>> that URL's are first about being successful at getting to something on the 
>>> web.
>>>
>>> I ask because of the potential for me to gain a new insight into how 
>>> different people see things.
>>>
>>> On Friday, August 6, 2021 at 12:42:44 AM UTC-3 The Islander wrote:
>>>
 Although the link text looks nice, hover over it and look at the URL. 
 Yuck!

 On Wednesday, August 4, 2021 at 6:12:40 PM UTC-7 TW Tones wrote:

> Folks,
>
> I just stumbled upon something helpful. You may know how to copy a 
> permalink to a tiddler, this results in URL, and using the to clipboard 
> option is help full. the only problem is the result is an ugly URL with 
> encoding.
>
> I discovered today however if you have Control Panel > Settings > Tiddler 
> Titles 
> 
>  set 
> to Display tiddler titles as links, there is a a better choice. Or where 
> every you see a link in a tiddler eg  Learning 
>  [[Learning  |
> https://tiddlywiki.com/#Learning]] copt that with you mouse.
>
> If the titles are displayed as links highlight and copy the title with 
> your mouse. The result if pasted is well formatted link eg; Navigation 
> History 
> .
>  
> It is not helpful pasting into tiddlywiki,  I will raise an issue on 
> this. 
> But it is helpful pasting links into email and forum posts. As I have 
> done 
> here.
>
> Regards
> Tones
>


-- 
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/91dedf37-c63e-490b-b429-7c3128ae445an%40googlegroups.com.

[tw5] Re: Retrieving the number of link paths to a tiddler

[Soren Bjornstad]

Thanks Tones!

Looks like I may have been overthinking this – just :filter, working 
backwards from the match found and seeing when you hit the current tiddler, 
is sufficient:

\define xcor-sort() [backlinks[]tag[Use]] 
:filter[links[]field:title] +[count[]]
\define xcor-count() [backlinks[]tag[Use]] 
:filter[links[]field:title] +[count[]]

...

<$list 
filter="[all[current]backlinks[]tag[Use]links[]!tag[Use]!field:titlesort[]!sortsub]"
 
variable="crossRef">
  <$set name=numPaths filter=<>>
<$link to=<>/> (<$text text=<>/> occurrence(s))
  


(A different subfilter is needed for the sort than to populate the count 
variable in 5.2.3 since the tiddler being processed by a subfilter can't be 
retrieved through a variable. This could probably be tweaked in prerelease 
so you only need one subfilter.)
On Sunday, August 8, 2021 at 12:45:51 AM UTC-5 TW Tones wrote:

> Soren
>
> Without working through this requirement of yours, I suspect some of the 
> code patterns in my recent reply to another thread 
> <https://groups.google.com/g/tiddlywiki/c/ahbcnXqVgl8/m/eYbVchcRBAAJ>could 
> help you.
>
>1. Your could make a list of all tiddler links (as a variable) without 
>removing duplicates, then listing a given tiddler you could count how many 
>mentions it has.
>2. With the prerelease Sort Filter Run Prefix 
><https://tiddlywiki.com/prerelease/#Sort%20Filter%20Run%20Prefix> should 
>allow you to sortby the count of mentions as per the filter in 1.
>
> Regards
> Tones
>
>
> On Sunday, 8 August 2021 at 12:12:51 UTC+10 Soren Bjornstad wrote:
>
>> I have a wiki where I want to cross-correlate *concepts *across *uses *of 
>> these concepts. (A concept, in this example, can be defined as any tiddler 
>> *not* tagged Use, while a use is obviously any tiddler tagged Use.) By 
>> "cross-correlate", I mean that given the current tiddler is a concept 
>> tiddler, find all the other concept tiddlers that are used on any use 
>> tiddler that links to the current tiddler (that is, they are often used 
>> together).
>>
>> I can do this with the following filter:
>>
>> [all[current]backlinks[]tag[Use]links[]!tag[Use]]
>>
>> However, I would now like to retrieve (and sort by) the number of 
>> discrete link paths by which you can reach each concept (i.e., the number 
>> of times the current tiddler and this other concept are used together on a 
>> use tiddler). So if 5 use tiddlers which link to the current tiddler also 
>> link to a particular other concept tiddler, the number 5 should be 
>> accessible in a variable when $list'ing through that concept tiddler, to be 
>> used in sortsub[] or the like and the template displaying each match.
>>
>> I haven't been able to think of any way to do this – I tried using the = 
>> filter prefix, but this evidently does not work when you're not adding the 
>> results *to* anything (and probably tag[] and links[] already 
>> deduplicate before they start).
>>
>> Since I'm sure what I want is absolutely clear as mud at this point, 
>> here's a diagram of a toy example, with arrows representing links and the 
>> green numbers showing how many “matches” there would be for my search 
>> criteria:
>>
>> [image: ksnip_20210807-210609.png]
>>
>> As always, thanks for any suggestions!
>>
>

-- 
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/3d62062d-7fb7-4706-9491-5121b7d4fcd2n%40googlegroups.com.

[tw5] Re: Best way to cite the source of WikiText snippets?

[Soren Bjornstad]

I use a comment with the link:



Currently you can't use comments until you reach the end of the pragmas in 
a tiddler, but that's slated to be fixed in 5.2.0.

On Wednesday, July 28, 2021 at 8:09:59 AM UTC-5 Si wrote:

> Much of my wiki is made up of snippets of WikiText that I have taken from 
> other sources, in particular public wikis (e.g. 
> https://zettelkasten.sorenbjornstad.com/) and from threads in this group.
>
> I want to make sure that I keep track of where I get these snippets from 
> for two reasons:
>
>- to make my life easier if I ever want to look at the original source 
>of some code in my wiki.
>- in case I ever publish something online, I want to ensure that I 
>have property attributed the original author of any code that I use.
>
> *So I'm just wondering what is the best practice here? *I can't link to 
> the source within the text because most of the time we are talking about 
> system tiddlers, but at the same time using a "source" field does not make 
> it clear exactly which part of the source came from where.
>
> Example: I have a style-sheet tiddler with loads of rulesets, and just one 
> of those many rulesets was taken from Soren's wiki, and it's not clear to 
> me what the best way to keep track of this is.
>

-- 
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/3569dbd8-6aa0-49f1-952f-b2c9283c5a3dn%40googlegroups.com.

[tw5] Re: Introducing TiddlyRemember, a tool for integrating TiddlyWiki with Anki spaced-repetition flashcards

[Soren Bjornstad]

Update: I just released version 1.2.3 
<https://github.com/sobjornstad/TiddlyRemember/releases/tag/v1.2.3>, which 
should fix this problem for real. If you're not on the Anki 2.1.45 release 
candidate, you'll have to switch to that to get this update (or just wait 
until the end of the month when it's planned for full release).

On Sunday, July 11, 2021 at 7:29:23 AM UTC-5 Soren Bjornstad wrote:

> Haha, no problem. I would have wanted to check anyway.
>
> On Saturday, July 10, 2021 at 5:36:16 PM UTC-5 Si wrote:
>
>> Thanks a lot Soren!
>>
>> >>> I was not able to reproduce this with the *rememberq* macro, nor do 
>> I see anything in that macro definition that would be able to cause a 
>> similar issue, so if you're still seeing problems with that, please provide 
>> an example of something that doesn't work. 
>>
>> My appologies, I meant to say "I have done something similar with 
>> question and answer cards and *do not *seem to experience the same 
>> problem". I guess I had a brain-fart. I'm really sorry for wasting your 
>> time. 
>> On Saturday, 10 July 2021 at 21:47:36 UTC+1 Soren Bjornstad wrote:
>>
>>> Si,
>>>
>>> It looks like I have a $list widget that is being used to choose which 
>>> macro call variant to use, and I forgot to set the *variable *parameter 
>>> to something other than currentTiddler. I'll include a fix for this in the 
>>> next version.
>>>
>>> In the meantime, you can apply the fix yourself by overriding the shadow 
>>> tiddler $:/plugins/sobjornstad/TiddlyRemember/macros/remember and adding 
>>> the appropriate *variable* parameters -- here's a diff:
>>>
>>> diff --git a/tw-plugin/macros/remember.tid 
>>> b/tw-plugin/macros/remember.tid
>>> index bfb6359..7dbb052 100644
>>> --- a/tw-plugin/macros/remember.tid
>>> +++ b/tw-plugin/macros/remember.tid
>>> @@ -47,10 +47,10 @@ type: text/vnd.tiddlywiki
>>>  \end
>>>  
>>>  \define remembercz(id, text, mode: "block", reference: "")
>>> *-   <$list filter="[[$mode$]match[inline]]">*
>>> *+   <$list filter="[[$mode$]match[inline]]" variable=_>*
>>> <$macrocall $name=twRememberClozeInline id=<<__id__>> 
>>> text=<<__text__>> reference=<<__reference__>>/>
>>> 
>>> *-   <$list filter="[[$mode$]!match[inline]]">*
>>> *+   <$list filter="[[$mode$]!match[inline]]" variable=_>*
>>> <$macrocall $name=twRememberClozeBlock id=<<__id__>> 
>>> text=<<__text__>> reference=<<__reference__>>/>
>>> 
>>>  \end
>>>
>>> I was not able to reproduce this with the *rememberq* macro, nor do I 
>>> see anything in that macro definition that would be able to cause a similar 
>>> issue, so if you're still seeing problems with that, please provide an 
>>> example of something that doesn't work.
>>>
>>> On Saturday, July 10, 2021 at 11:30:27 AM UTC-5 Si wrote:
>>>
>>>> Hi Soren.
>>>>
>>>> I've run into a bit of trouble trying to create a custom cloze-macro 
>>>> using TiddlyRemember. I have tiddlers with the fields cloze and context, 
>>>> and am trying to create a global macro that will generate cloze cards 
>>>> based 
>>>> on those fields. Here is the code:
>>>>
>>>> \define cloze-text()
>>>> {{!!context}}
>>>> 
>>>> {{!!cloze}}
>>>> \end
>>>>
>>>> \define cloze()
>>>> <$macrocall $name=remembercz id={{!!created}} text=<> />
>>>> \end
>>>>
>>>> I am finding that the macro is unable to get the current tiddler. If I 
>>>> change the code for cloze-text to the following I get the output 
>>>> "block":
>>>>
>>>> \define cloze-text()
>>>> <
>>>> \end
>>>>
>>>> I have done something similar with question and answer cards and seem 
>>>> to experience the same problem. Do you know what is going on here?
>>>>
>>>> I hope I have explained myself clearly enough, but that's not always 
>>>> easy so please let me know if I'm not making any sense!
>>>> On Monday, 25 May 2020 at 03:26:29 UTC+1 Soren Bjornstad wrote:
>>>>
>>>>> I'm pleased to announ

[tw5] Re: Simplest way to list all tiddlers that transclude the current tiddler?

[Soren Bjornstad]

Ah. The behavior of that filter operator changed in Relink 2.0.0, so that 
was probably your issue.

On Saturday, July 24, 2021 at 2:48:14 PM UTC-5 evanwh...@gmail.com wrote:

> Just wanted to update: I got things working by updating my TW version as 
> well as my Relink version. Now I'm on TW 5.2.0-prerelease and Relink 2.0.0.
>
> So my issue is resolved! Thanks everyone!
>  
>
> On Friday, July 23, 2021 at 8:43:48 PM UTC-7 Evan Hackett wrote:
>
>> Really? I just tried the snippet again to double check, and it isn't 
>> working for me. Yes I saved the tiddler, nothing shows up.
>>
>> Do you think there could be some other reason it isn't working? Perhaps 
>> incompatible versions or something?
>>
>> Here's more info in case it helps:
>>
>> TW version: 5.1.23-prerelease
>> Relink version: 1.10.0
>> Other plugins: Core, Filesystem, Highlight, TiddlyWeb
>> Browser: Brave Version 1.26.74 Chromium: 91.0.4472.124 (Official Build) 
>> (x86_64)
>> Computer: Macbook Pro
>>
>> On Friday, July 23, 2021 at 11:06:30 AM UTC-7 Soren Bjornstad wrote:
>>
>>> Your snippet works for me when placed in a tiddler that has links or 
>>> transclusions to it from other tiddlers.
>>>
>>> Just to be sure, did you try saving the tiddler rather than just looking 
>>> at the preview? all[current] will be a draft tiddler if you're looking at 
>>> the preview, so it probably won't find anything.
>>>
>>> BTW, the !is[system] in your filter isn't doing anything because 
>>> all[current] completely ignores its input.
>>>
>>> On Friday, July 23, 2021 at 11:46:39 AM UTC-5 evanwh...@gmail.com wrote:
>>>
>>>> I had a feeling it wasn't supported, because I looked through all the 
>>>> filter operators and nothing stuck out at me as being what I wanted. So 
>>>> since I am using the relink plugin, does that mean I can call its 
>>>> operators 
>>>> in my own tiddler? So far I've been unsuccessful getting something to 
>>>> work, 
>>>> but I'm probably just doing it wrong.
>>>>
>>>> Looking at that thread that was linked, I copied some code and tried to 
>>>> get it to work but so far unsuccessful. I tried this along with various 
>>>> tweaks:
>>>>
>>>> <$list filter=" 
>>>> [!is[system]all[current]relink:backreferences[]!title[$:/StoryList]sort[title]]">
>>>> <$link to={{!!title}}><$view field="title"/>
>>>> 
>>>>
>>>> Nothing shows up. Does anyone have a snippet that they could share?
>>>>
>>>> On Thursday, July 22, 2021 at 1:35:10 PM UTC-7 saq.i...@gmail.com 
>>>> wrote:
>>>>
>>>>>  If I get some time in the next couple months and nobody else does it, 
>>>>>> maybe I will take a look at how to get started with TW core development.
>>>>>>
>>>>>>
>>>>> Would be happy to answer any questions you might have along those 
>>>>> lines.
>>>>>
>>>>

-- 
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/eb209f6a-491d-4321-aa13-3b037bdd8cedn%40googlegroups.com.

[tw5] Re: Simplest way to list all tiddlers that transclude the current tiddler?

[Soren Bjornstad]

Your snippet works for me when placed in a tiddler that has links or 
transclusions to it from other tiddlers.

Just to be sure, did you try saving the tiddler rather than just looking at 
the preview? all[current] will be a draft tiddler if you're looking at the 
preview, so it probably won't find anything.

BTW, the !is[system] in your filter isn't doing anything because 
all[current] completely ignores its input.

On Friday, July 23, 2021 at 11:46:39 AM UTC-5 evanwh...@gmail.com wrote:

> I had a feeling it wasn't supported, because I looked through all the 
> filter operators and nothing stuck out at me as being what I wanted. So 
> since I am using the relink plugin, does that mean I can call its operators 
> in my own tiddler? So far I've been unsuccessful getting something to work, 
> but I'm probably just doing it wrong.
>
> Looking at that thread that was linked, I copied some code and tried to 
> get it to work but so far unsuccessful. I tried this along with various 
> tweaks:
>
> <$list filter=" 
> [!is[system]all[current]relink:backreferences[]!title[$:/StoryList]sort[title]]">
> <$link to={{!!title}}><$view field="title"/>
> 
>
> Nothing shows up. Does anyone have a snippet that they could share?
>
> On Thursday, July 22, 2021 at 1:35:10 PM UTC-7 saq.i...@gmail.com wrote:
>
>>  If I get some time in the next couple months and nobody else does it, 
>>> maybe I will take a look at how to get started with TW core development.
>>>
>>>
>> Would be happy to answer any questions you might have along those lines.
>>
>

-- 
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/92715a37-75b5-4cf2-950b-aa572c24ad51n%40googlegroups.com.

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

[Soren Bjornstad]

Tones,

Here's the reference explorer tiddler, as mentioned earlier in the thread: 
https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2Frefexplorer%2FReferenceExplorer

Most of the data set is public in the same wiki…if you just click around in 
some random non-system tiddlers, they all have the Ideas section of the 
Reference Explorer showing. The public version may perform just a little 
better than my private one since it has about a third fewer tiddlers, but 
won't be too far off.

I had not remembered to look at the #Performance tiddler, but I don't 
believe any of the suggestions in there are applicable here.
On Friday, July 23, 2021 at 12:18:06 AM UTC-5 TW Tones wrote:

> Soren,
>
> Can you share the data set, or a dummy one for us to look at performance 
> improvements?
>
> I presume you have reviewed you filters in respect of their performance 
> here <https://tiddlywiki.com/#Performance>?
> Tones
>
> On Friday, 23 July 2021 at 10:17:24 UTC+10 Soren Bjornstad wrote:
>
>> Tones, thanks for putting this together, but your solution is slower than 
>> mine as far as I can tell (no easy way to instrument that since it has a 
>> very different number of filters, but the difference is apparent from 
>> clicking around a bit).
>>
>> Saq, I can't get your filter to work and I can't see how it would work in 
>> theory either now that I look at it – the !!condition in the subfilter is 
>> getting the condition field on the tiddler in which the tab list is being 
>> rendered, whereas it needs to be the *tab* tiddler that's coming in on 
>> the input of the subfilter operator…right? Or am I just being dense? In my 
>> :reduce version it has a different meaning because :reduce actually 
>> resets the currentTiddler variable to match the input value currently being 
>> processed <https://tiddlywiki.com/#reduce%20Operator>.
>>
>> With the additional optimization work I did the other night, including 
>> optimizing the filters on each tab as Saq pointed out, I would say it's now 
>> performing acceptably with my current version, if only barely on a slower 
>> computer. So if nobody has any other ideas, I think I can leave it where it 
>> is for now.
>>
>>
>> On Wednesday, July 21, 2021 at 8:58:05 AM UTC-5 TW Tones wrote:
>>
>>> Oops;
>>>
>>> I must add
>>> the tab template contains
>>>
>>> <$tiddler tiddler=<>>
>>> <$transclude mode="block" />
>>> 
>>>
>>> and each tab contains 
>>> <$list filter={{!!filter}}>
>>>
>>> 
>>>
>>> The tabs work stand alone
>>>
>>> Tones
>>>
>>> On Wednesday, 21 July 2021 at 23:55:11 UTC+10 TW Tones wrote:
>>>
>>>> Soren,
>>>>
>>>> Given this thread, I am not sure if I am on track here, but reading 
>>>> your Original post it seems so.
>>>>
>>>> As I understand it you want to use a filter in a tab tiddler to 
>>>> determine if it should have the tab displayed.
>>>>
>>>> The thing is the tabs macro is not designed for conditional tab 
>>>> display, it simply wants a list of tiddlers. If this could all be rammed 
>>>> into a single filter then all would be fine. However you not only want to 
>>>> make use of another variable or in this case a field but that field 
>>>> contains a filter. This is asking too much of the filter syntax.
>>>>
>>>> What I have done in my solution was to generate the list of tiddlers 
>>>> that would be tabs according to you conditions and feed only the result to 
>>>> the tabs macro.
>>>>
>>>>- In my small test not performance issues, and I do not expect 
>>>>their to be
>>>>- I think what is happening in your case if the reduce etc... is 
>>>>adding unnecessary complexity to the performance of the tabs macro.
>>>>
>>>>
>>>> Here is the core logic tested on tiddlywiki.com and pre-release 
>>>> incidentally.
>>>>
>>>> \define tabs-with-content()
>>>> <$list filter="[tag[Tag]]" >
>>>><$list filter="[all[current]get[filter]]" variable=found-filter>
>>>>   <$list 
>>>> filter="[subfiltercount[]!match[0]then]">
>>>>
>>>>
>>>>
>>>> 
>>>> \end
>>>>
>>>> <$wikify name=tabs-with-content text="<>">

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

[Soren Bjornstad]

Ah, got it. I'll give it a try when I upgrade, thanks.

On Friday, July 23, 2021 at 12:31:53 AM UTC-5 saq.i...@gmail.com wrote:

> Hi Soren, I mentioned this when I suggested the filter and explained in a 
> bit more detail in  a follow up reply which seems to never have been posted.
>
>  You will need the 5.2.0 pre-release for that filter to work, as one of 
> the changes is greater consistency in setting the value of currentTiddler 
> for :filter, :reduce and :sort and their operator equivalents.  See  
> https://tiddlywiki.com/prerelease/#Filter%20Expression
>
> On Friday, July 23, 2021 at 2:17:24 AM UTC+2 Soren Bjornstad wrote:
>
>> Tones, thanks for putting this together, but your solution is slower than 
>> mine as far as I can tell (no easy way to instrument that since it has a 
>> very different number of filters, but the difference is apparent from 
>> clicking around a bit).
>>
>> Saq, I can't get your filter to work and I can't see how it would work in 
>> theory either now that I look at it – the !!condition in the subfilter is 
>> getting the condition field on the tiddler in which the tab list is being 
>> rendered, whereas it needs to be the *tab* tiddler that's coming in on 
>> the input of the subfilter operator…right? Or am I just being dense? In my 
>> :reduce version it has a different meaning because :reduce actually 
>> resets the currentTiddler variable to match the input value currently being 
>> processed <https://tiddlywiki.com/#reduce%20Operator>.
>>
>> With the additional optimization work I did the other night, including 
>> optimizing the filters on each tab as Saq pointed out, I would say it's now 
>> performing acceptably with my current version, if only barely on a slower 
>> computer. So if nobody has any other ideas, I think I can leave it where it 
>> is for now.
>>
>>
>> On Wednesday, July 21, 2021 at 8:58:05 AM UTC-5 TW Tones wrote:
>>
>>> Oops;
>>>
>>> I must add
>>> the tab template contains
>>>
>>> <$tiddler tiddler=<>>
>>> <$transclude mode="block" />
>>> 
>>>
>>> and each tab contains 
>>> <$list filter={{!!filter}}>
>>>
>>> 
>>>
>>> The tabs work stand alone
>>>
>>> Tones
>>>
>>> On Wednesday, 21 July 2021 at 23:55:11 UTC+10 TW Tones wrote:
>>>
>>>> Soren,
>>>>
>>>> Given this thread, I am not sure if I am on track here, but reading 
>>>> your Original post it seems so.
>>>>
>>>> As I understand it you want to use a filter in a tab tiddler to 
>>>> determine if it should have the tab displayed.
>>>>
>>>> The thing is the tabs macro is not designed for conditional tab 
>>>> display, it simply wants a list of tiddlers. If this could all be rammed 
>>>> into a single filter then all would be fine. However you not only want to 
>>>> make use of another variable or in this case a field but that field 
>>>> contains a filter. This is asking too much of the filter syntax.
>>>>
>>>> What I have done in my solution was to generate the list of tiddlers 
>>>> that would be tabs according to you conditions and feed only the result to 
>>>> the tabs macro.
>>>>
>>>>- In my small test not performance issues, and I do not expect 
>>>>their to be
>>>>- I think what is happening in your case if the reduce etc... is 
>>>>adding unnecessary complexity to the performance of the tabs macro.
>>>>
>>>>
>>>> Here is the core logic tested on tiddlywiki.com and pre-release 
>>>> incidentally.
>>>>
>>>> \define tabs-with-content()
>>>> <$list filter="[tag[Tag]]" >
>>>><$list filter="[all[current]get[filter]]" variable=found-filter>
>>>>   <$list 
>>>> filter="[subfiltercount[]!match[0]then]">
>>>>
>>>>
>>>>
>>>> 
>>>> \end
>>>>
>>>> <$wikify name=tabs-with-content text="<>">
>>>> <$macrocall $name=tabs tabsList=<> 
>>>> template="tabtemplate"/>
>>>> 
>>>>
>>>> If this does not make sense I will package the tiddlers in this test 
>>>> for you.
>>>>
>>>> The above example may be a good test case if we wanted to invent a 
&

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

[Soren Bjornstad]

Also, my comment should definitely say “vertical space,” not “horizontal 
space,” haha.

On Thursday, July 22, 2021 at 7:26:02 PM UTC-5 Soren Bjornstad wrote:

> Paul,
>
> 1. No matter what I do and what I've searched for has been able to explain 
>> why some things render differently for me. This has often caused me to stop 
>> and spend large quantities of time trying to figure out what is wrong. For 
>> example. In no version of TiddlyWiki (or browser or operating system) that 
>> I've downloaded does Heading 2 render with an underline. Doesn't happen. 
>> Ever. But it does in Grok TiddlyWiki. 
>>
>
> Ah! This is just because Grok TiddlyWiki has custom CSS rules that make 
> some things look different. In $:/sib/Stylesheet, you'll find:
>
> /* Add more horizontal space and a border for headings, except the title. 
> */
> h2:not(.tc-title) {
>   /*margin-top: 6ex; -- for some bizarre reason Firefox and Chrome are 
> calculating ex-height differently, so eyeballed an appropriate number of 
> inches*/
>   margin-top: 0.4in;
>   padding-bottom: 5px;
>   *border-bottom: 0.05px solid <>;*
> }
>
> Are you able to give some more examples of this? You're not the first 
> person who's been confused by the fact that Grok TiddlyWiki doesn't look 
> exactly like a stock TiddlyWiki because I've configured it differently. 
> Maybe I need to point that out somewhere.
>  
>
>> BTW, an article on where spaces are ignored and where they break things 
>> and why would be AMAZING.
>>
>
> Does block mode and inline mode 
> <https://groktiddlywiki.com/read/#Block%20Mode%20and%20Inline%20Mode> help 
> at all? That's specifically about carriage returns, but those are usually 
> more confusing than actual spaces in my experience.
>

-- 
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/aaf42348-d1c1-49b9-beee-b60390c8bf2bn%40googlegroups.com.

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

[Soren Bjornstad]

Paul,

1. No matter what I do and what I've searched for has been able to explain 
> why some things render differently for me. This has often caused me to stop 
> and spend large quantities of time trying to figure out what is wrong. For 
> example. In no version of TiddlyWiki (or browser or operating system) that 
> I've downloaded does Heading 2 render with an underline. Doesn't happen. 
> Ever. But it does in Grok TiddlyWiki. 
>

Ah! This is just because Grok TiddlyWiki has custom CSS rules that make 
some things look different. In $:/sib/Stylesheet, you'll find:

/* Add more horizontal space and a border for headings, except the title. */
h2:not(.tc-title) {
  /*margin-top: 6ex; -- for some bizarre reason Firefox and Chrome are 
calculating ex-height differently, so eyeballed an appropriate number of 
inches*/
  margin-top: 0.4in;
  padding-bottom: 5px;
  *border-bottom: 0.05px solid <>;*
}

Are you able to give some more examples of this? You're not the first 
person who's been confused by the fact that Grok TiddlyWiki doesn't look 
exactly like a stock TiddlyWiki because I've configured it differently. 
Maybe I need to point that out somewhere.
 

> BTW, an article on where spaces are ignored and where they break things 
> and why would be AMAZING.
>

Does block mode and inline mode 
 help 
at all? That's specifically about carriage returns, but those are usually 
more confusing than actual spaces in my experience.

-- 
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/d3b0f9f9-431a-46bb-8da0-fd303bd19fdcn%40googlegroups.com.

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

[Soren Bjornstad]

Tones, thanks for putting this together, but your solution is slower than 
mine as far as I can tell (no easy way to instrument that since it has a 
very different number of filters, but the difference is apparent from 
clicking around a bit).

Saq, I can't get your filter to work and I can't see how it would work in 
theory either now that I look at it – the !!condition in the subfilter is 
getting the condition field on the tiddler in which the tab list is being 
rendered, whereas it needs to be the *tab* tiddler that's coming in on the 
input of the subfilter operator…right? Or am I just being dense? In my 
:reduce version it has a different meaning because :reduce actually resets 
the currentTiddler variable to match the input value currently being 
processed .

With the additional optimization work I did the other night, including 
optimizing the filters on each tab as Saq pointed out, I would say it's now 
performing acceptably with my current version, if only barely on a slower 
computer. So if nobody has any other ideas, I think I can leave it where it 
is for now.


-- 
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/d31f9d76-26f9-4c63-8e12-167e42ae11a9n%40googlegroups.com.

[tw5] Re: TiddlyWiki Community Call and File Uploads Plugin

[Soren Bjornstad]

Saq,

To clarify for those of us who are not as familiar with European time 
zones, is this UTC+2 because it is summer?
On Thursday, July 22, 2021 at 2:33:18 PM UTC-5 saq.i...@gmail.com wrote:

> We will be having a *TiddlyWiki Community call* with Jeremy, Boris and 
> myself on August 17th at 6pm CET: TiddlyWiki Community: Core Savers & 
> Syncers, Upload Plugin, & Community Forum - Zoom 
>
> I hope some of you will be able to join us for what I think will be a very 
> interesting discussion. Please register for the event at the link above.
>
> The call will include:
>
>- a progress update on my work on the *Uploads plugin* funded by Open 
>Collective
>- a summary of some rather exciting and promising avenues for core 
>development in the areas of *Savers and Syncers* that has come out of 
>discussions around the Uploads plugin
>- an update on the *Open Collective* model for funding TiddlyWiki work 
>and what we have learned from it thus far
>- some news from Jeremy and Boris regarding improvements to TiddlyWiki 
> *community 
>infrastructure*.
>
> I have been slowly working away on the TiddlyWiki file uploads plugin as 
> was previously announced 
> . 
> The majority of the work thus far has consisted of brainstorming around the 
> architecture and some very involved but promising and productive 
> discussions with Jeremy around how such a plugin would integrate with the 
> core, and the direction that the core might take in the future with regards 
> to saving and syncing mechanisms. 
>
> In particular we have identified some exciting opportunities to explore in 
> due course for a rethinking of the saver and syncer mechanisms that may 
> amongst other things eventually make file uploads a core TiddlyWiki ability 
> alongside saving and syncing and static file publishing.
>
> This has necessitated a change in approach to the File Uploads plugin so 
> as to not introduce changes to the TiddlyWiki core at this time which may 
> clash with the long term direction of development, and still make the 
> Uploads plugin available in a timely manner for those that need this 
> functionality today. I currently have a minimal working prototype that 
> uploads images imported into TiddlyWiki to Fission, though with no UI or 
> error handling as of yet and desperately in need of some heavy refactoring 
> to better be able to support different storage back ends. I hope to present 
> a demo of an early version of the plugin on the call.
>
> I would like to take the opportunity here to thank Boris and Fission. 
> Despite Boris having chipped in for the vast majority of the funding for 
> this plugin as it is something he needs in his own TiddlyWiki usage, not 
> only has he been patient and supportive as we focus on long term core 
> planning first, but Fission has actively been facilitating those 
> discussions.
>
> Regards,
> Saq
>

-- 
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/7d2a6672-464d-453b-bedd-74006c636b5cn%40googlegroups.com.

[tw5] Re: Simplest way to list all tiddlers that transclude the current tiddler?

[Soren Bjornstad]

This isn't supported in core currently, though there's a pull request about 
it that needs a bunch of work to be mergeable that I keep harping on 
because I want this too. :-) If I get some time in the next couple months 
and nobody else does it, maybe I will take a look at how to get started 
with TW core development.

In the meantime, the relink plugin implements its own filter operator for 
this, though as I understand, it is undocumented and might change behavior 
in future versions of Relink. See this recent thread 
.

On Thursday, July 22, 2021 at 12:29:24 PM UTC-5 evanwh...@gmail.com wrote:

> Hey everyone, this is my first post here, sorry if I'm asking a common 
> question.
>
> Basically I have constructed a footer that displays all backlinks of the 
> current tiddler, and I want to extend it to also display all transclusions 
> as well. 
>
> I know this is possible because I use the relink plugin, and it seems to 
> have similar functionality. I just can't figure out how to harness it for 
> myself!
>
> My footer currently looks like this:
>
> 
>   Backlinks: 
>   
>
>   
> <$list filter="[all[current]backlinks[]sort[title]]" emptyMessage="">
>   <$link to={{!!title}}><$view field="title"/>
>   
> 
>   
> 
>
> Let me know what you think. Thanks everyone!
>

-- 
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/40f121b2-e315-402e-92e7-745c09771619n%40googlegroups.com.

[tw5] Re: tidders created this week

[Soren Bjornstad]

On Wednesday, July 21, 2021 at 9:58:33 PM UTC-5 TW Tones wrote:

> From the pre-release this feature should make it even simpler
>  New in: 5.2.0 Literal macro parameters are supported 
> . For example: 
> [].
>

Ooh, that's slick, looking forward to it!

-- 
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/3d4101b7-8352-4406-8004-479caae473c4n%40googlegroups.com.

[tw5] Seeking general feedback on Grok TiddlyWiki

[Soren Bjornstad]

Hi everyone,

I know quite a few people on here have been reading at least some of my 
book Grok TiddlyWiki . While I've gotten 
quite a bit of specific feedback submitted through the built-in feedback 
mechanism, I've been coming up short on overall impressions and 
significance beyond "thanks so much for this book." If you've looked at the 
book and you have a few moments, I'd love to know what you think. For 
instance:

   - Is the book organized effectively?
   - What parts have you read/worked through?
   - How have you been using the book? Have you done some of the exercises 
   and flashcards? Do they work? (I'm particularly interested in this question 
   because I'd love to iterate and build more resources like this one in the 
   future.)
   - How have your TiddlyWiki skills improved, if they have?
   - Any other thoughts?

If there's anything you don't want to share publicly, feel free to email it 
directly to me at contact (at) sorenbjornstad.com.

Much appreciated,
Soren

-- 
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/fa5876c6-515b-4be3-a5c1-92bf28e8fc4an%40googlegroups.com.

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

[Soren Bjornstad]

Saq, the intermittent refresh every 5 seconds updates a clock and Pomodoro 
timer. The reason it's puzzling is that it doesn't appear by default in the 
public edition. If you're curious, tick the "clock" checkbox in the 
FeatureFlags tiddler.

I'll give the :filter version a try later. I suspect I didn't think to use 
filter and subfilter together in one run!

On Wednesday, July 21, 2021 at 5:57:42 AM UTC-5 saq.i...@gmail.com wrote:

> Hi Soren, glad that was helpful. When I worked on performance improvements 
> for Streams a few months ago, the biggest gains were from simplifying the 
> widget and DOM structure, and replacing macros with transclusions, rather 
> than from optimizing filters.
>
> I took a brief look at your wiki just now and the one odd thing I see is 
> that there seems to be an intermittent refresh being triggered every few 
> seconds. Any idea what that is about? To see what I mean, create a new 
> tiddler with the following in the text and then observe the developer 
> console:
> <$log t=<>/>
>
> This should work on the current pre-release but probably isn't any faster:
> [tag[$:/sib/refexplorer/tabs]] :filter[subfilter{!!condition}] +[join[ ]]
>
> I suspect that any real gains would come from optimizing the condition 
> filters, as they likely make up the bulk of the time needed for the above 
> filter expression. For filter operators that are indexed, the first time 
> they run they will take a while but subsequent runs should be faster. 
> https://tiddlywiki.com/#Performance
>
> On Wednesday, July 21, 2021 at 4:20:13 AM UTC+2 Soren Bjornstad wrote:
>
>> 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.
>>>>>
>>>>

[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=<

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: 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)

[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 

[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] Building a list of tabs dynamically in a performant manner

[Soren Bjornstad]

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/56301178-d4b7-4a46-8c87-12da5ed5cd27n%40googlegroups.com.

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

[Soren Bjornstad]

I think the author's first principle contradicts the article: it says that 
"good notes should behave like memory." But actual human memory is *not* 
immutable, 
not even close; memories are changed somewhat every time we recall them. So 
it seems to me that a system that actually matched memory would update over 
time, but also retain some traces of previous versions.

On the topic of "time is essential to how we remember," at least for me it 
depends on the *type* of information. If it is naturally autobiographical, 
or there was a particularly salient moment at which I learned the 
information, or it happened during a particular project or class, sure. 
When the thoughts are more abstract and developing over time, I absolutely 
cannot remember a thing about the time I had them or added to them, nor is 
that information particularly relevant.

As I recall, Ted Nelson talked about adding a time dimension to hypertext, 
where you could easily go back and forth between different versions and see 
exactly what has changed in a graphical manner. Google Docs and Git both 
kind of do this, but I don't think they've figured out all the 
possibilities here...you still have to go into a separate system to browse 
through the different versions, and it's hard to see several at the same 
time. The diff between versions is also probably not the best visualization 
-- perhaps for instance a stream of different additions (as in the *inc* idea 
the author mentions!) would be better for many types of notes. So overall, 
this would seem like a more productive direction to me -- you can see the 
latest state of the art, or you can quickly and easily look at previous 
"versions", whatever makes the most sense.

I do think TiddlyWiki's tools in this area are currently somewhat 
impoverished.

On Thursday, July 15, 2021 at 2:18:48 PM UTC-5 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/61ffa220-c49c-42ec-91c2-86d0cdd069d7n%40googlegroups.com.

[tw5] Re: First edition of Grok TiddlyWiki (TW textbook) is live

[Soren Bjornstad]

David and TT, I've made notes of both of these suggestions, thanks!

On Saturday, July 10, 2021 at 11:46:56 AM UTC-5 David Gifford wrote:

> Hi Soren, I am enjoying the Grok! One possible fix: the Miscellaneous 
> Widgets > $radio example doesn't seem to work.
>
> On Saturday, July 10, 2021 at 4:28:07 AM UTC-5 TiddlyTweeter wrote:
>
>> Ciao Soren
>>
>> This is an updated comment. Your Grok is *very good*. I learned a lot 
>> from it. 
>>
>> Basically I think it is a go-to resource/reference for learning TW-ese.
>>
>> I have one REQUEST. *Could you include an SVG of this fish icon?* which 
>> is  currently only a bitmap ...
>>
>> [image: Screenshot 2021-07-10 112257.jpg]
>>
>> WHY? Because if I had it I'd use an SVG version in nice  links to 
>> direct readers to precise places your wiki.
>>
>> Very best wishes
>> TT
>>
>>
>> On Sunday, 16 May 2021 at 16:43:44 UTC+2 Soren Bjornstad wrote:
>>
>>> I'm excited to announce that the first public edition of my TiddlyWiki 
>>> textbook, *Grok TiddlyWiki*, is live at https://groktiddlywiki.com/read
>>> . *Grok TiddlyWiki* is (from the book) “a textbook that helps you build 
>>> a deep, lasting understanding of and proficiency with TiddlyWiki through a 
>>> combination of detailed explanations, practical exercises, 
>>> and spaced-repetition reviews of prompts called *takeaways*.”
>>>
>>> I am hoping this book will fill in many of the gaps in TiddlyWiki's 
>>> documentation / learning ecosystem – right now we have lots of beginner 
>>> tutorials, and mostly good documentation for experts (with a few gaps), but 
>>> almost nothing for people in between. GTW is what I wished I had when I was 
>>> in that position: complete lessons on the features and idioms of TiddlyWiki 
>>> needed to bring someone from beginner to expert.
>>>
>>> The book is free to read and CC BY-NC-ND licensed (you can redistribute 
>>> it for noncommercial purposes). I am accepting donations 
>>> <https://groktiddlywiki.com/donate/> to support my continued work on 
>>> GTW and other TiddlyWiki learning resources. I would also appreciate your 
>>> help spreading the word about the book, e.g., on TW links sites, 
>>> notes-related resources, or social media.
>>>
>>> A huge thanks to everyone from this community who provided feedback on 
>>> the prerelease (see the acknowledgments section for details). Barring me 
>>> getting run over by a bus, there will be updated editions in the future, so 
>>> please keep the feedback and suggestions coming.
>>
>>

-- 
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/c397ebed-ea25-40c2-b80d-3718c89de8c0n%40googlegroups.com.

[tw5] Re: Introducing TiddlyRemember, a tool for integrating TiddlyWiki with Anki spaced-repetition flashcards

[Soren Bjornstad]

Haha, no problem. I would have wanted to check anyway.

On Saturday, July 10, 2021 at 5:36:16 PM UTC-5 Si wrote:

> Thanks a lot Soren!
>
> >>> I was not able to reproduce this with the *rememberq* macro, nor do I 
> see anything in that macro definition that would be able to cause a similar 
> issue, so if you're still seeing problems with that, please provide an 
> example of something that doesn't work. 
>
> My appologies, I meant to say "I have done something similar with question 
> and answer cards and *do not *seem to experience the same problem". I 
> guess I had a brain-fart. I'm really sorry for wasting your time. 
> On Saturday, 10 July 2021 at 21:47:36 UTC+1 Soren Bjornstad wrote:
>
>> Si,
>>
>> It looks like I have a $list widget that is being used to choose which 
>> macro call variant to use, and I forgot to set the *variable *parameter 
>> to something other than currentTiddler. I'll include a fix for this in the 
>> next version.
>>
>> In the meantime, you can apply the fix yourself by overriding the shadow 
>> tiddler $:/plugins/sobjornstad/TiddlyRemember/macros/remember and adding 
>> the appropriate *variable* parameters -- here's a diff:
>>
>> diff --git a/tw-plugin/macros/remember.tid b/tw-plugin/macros/remember.tid
>> index bfb6359..7dbb052 100644
>> --- a/tw-plugin/macros/remember.tid
>> +++ b/tw-plugin/macros/remember.tid
>> @@ -47,10 +47,10 @@ type: text/vnd.tiddlywiki
>>  \end
>>  
>>  \define remembercz(id, text, mode: "block", reference: "")
>> *-   <$list filter="[[$mode$]match[inline]]">*
>> *+   <$list filter="[[$mode$]match[inline]]" variable=_>*
>> <$macrocall $name=twRememberClozeInline id=<<__id__>> 
>> text=<<__text__>> reference=<<__reference__>>/>
>> 
>> *-   <$list filter="[[$mode$]!match[inline]]">*
>> *+   <$list filter="[[$mode$]!match[inline]]" variable=_>*
>> <$macrocall $name=twRememberClozeBlock id=<<__id__>> 
>> text=<<__text__>> reference=<<__reference__>>/>
>> 
>>  \end
>>
>> I was not able to reproduce this with the *rememberq* macro, nor do I 
>> see anything in that macro definition that would be able to cause a similar 
>> issue, so if you're still seeing problems with that, please provide an 
>> example of something that doesn't work.
>>
>> On Saturday, July 10, 2021 at 11:30:27 AM UTC-5 Si wrote:
>>
>>> Hi Soren.
>>>
>>> I've run into a bit of trouble trying to create a custom cloze-macro 
>>> using TiddlyRemember. I have tiddlers with the fields cloze and context, 
>>> and am trying to create a global macro that will generate cloze cards based 
>>> on those fields. Here is the code:
>>>
>>> \define cloze-text()
>>> {{!!context}}
>>> 
>>> {{!!cloze}}
>>> \end
>>>
>>> \define cloze()
>>> <$macrocall $name=remembercz id={{!!created}} text=<> />
>>> \end
>>>
>>> I am finding that the macro is unable to get the current tiddler. If I 
>>> change the code for cloze-text to the following I get the output 
>>> "block":
>>>
>>> \define cloze-text()
>>> <
>>> \end
>>>
>>> I have done something similar with question and answer cards and seem to 
>>> experience the same problem. Do you know what is going on here?
>>>
>>> I hope I have explained myself clearly enough, but that's not always 
>>> easy so please let me know if I'm not making any sense!
>>> On Monday, 25 May 2020 at 03:26:29 UTC+1 Soren Bjornstad wrote:
>>>
>>>> I'm pleased to announce the release of version 1.0 of TiddlyRemember, a 
>>>> tool to make it easy to remember the most important bits of your notes. 
>>>> You 
>>>> call out specific bits of your tiddlers that you want to remember using 
>>>> TiddlyWiki macros, and an associated Anki <https://apps.ankiweb.net> 
>>>> add-on then pulls these snippets into Anki where you can review them 
>>>> regularly. The Anki cards link back to the tiddler they came from so you 
>>>> can find the context if you need it, and if you edit the content in 
>>>> TiddlyWiki or move it around, your Anki collection gets updated to match 
>>>> on 
>>>> your next sync, maintaining your review history.
>>

[tw5] Re: Introducing TiddlyRemember, a tool for integrating TiddlyWiki with Anki spaced-repetition flashcards

[Soren Bjornstad]

Si,

It looks like I have a $list widget that is being used to choose which 
macro call variant to use, and I forgot to set the *variable *parameter to 
something other than currentTiddler. I'll include a fix for this in the 
next version.

In the meantime, you can apply the fix yourself by overriding the shadow 
tiddler $:/plugins/sobjornstad/TiddlyRemember/macros/remember and adding 
the appropriate *variable* parameters -- here's a diff:

diff --git a/tw-plugin/macros/remember.tid b/tw-plugin/macros/remember.tid
index bfb6359..7dbb052 100644
--- a/tw-plugin/macros/remember.tid
+++ b/tw-plugin/macros/remember.tid
@@ -47,10 +47,10 @@ type: text/vnd.tiddlywiki
 \end
 
 \define remembercz(id, text, mode: "block", reference: "")
*-   <$list filter="[[$mode$]match[inline]]">*
*+   <$list filter="[[$mode$]match[inline]]" variable=_>*
<$macrocall $name=twRememberClozeInline id=<<__id__>> 
text=<<__text__>> reference=<<__reference__>>/>

*-   <$list filter="[[$mode$]!match[inline]]">*
*+   <$list filter="[[$mode$]!match[inline]]" variable=_>*
<$macrocall $name=twRememberClozeBlock id=<<__id__>> 
text=<<__text__>> reference=<<__reference__>>/>

 \end

I was not able to reproduce this with the *rememberq* macro, nor do I see 
anything in that macro definition that would be able to cause a similar 
issue, so if you're still seeing problems with that, please provide an 
example of something that doesn't work.

On Saturday, July 10, 2021 at 11:30:27 AM UTC-5 Si wrote:

> Hi Soren.
>
> I've run into a bit of trouble trying to create a custom cloze-macro using 
> TiddlyRemember. I have tiddlers with the fields cloze and context, and am 
> trying to create a global macro that will generate cloze cards based on 
> those fields. Here is the code:
>
> \define cloze-text()
> {{!!context}}
> 
> {{!!cloze}}
> \end
>
> \define cloze()
> <$macrocall $name=remembercz id={{!!created}} text=<> />
> \end
>
> I am finding that the macro is unable to get the current tiddler. If I 
> change the code for cloze-text to the following I get the output "block":
>
> \define cloze-text()
> <
> \end
>
> I have done something similar with question and answer cards and seem to 
> experience the same problem. Do you know what is going on here?
>
> I hope I have explained myself clearly enough, but that's not always easy 
> so please let me know if I'm not making any sense!
> On Monday, 25 May 2020 at 03:26:29 UTC+1 Soren Bjornstad wrote:
>
>> I'm pleased to announce the release of version 1.0 of TiddlyRemember, a 
>> tool to make it easy to remember the most important bits of your notes. You 
>> call out specific bits of your tiddlers that you want to remember using 
>> TiddlyWiki macros, and an associated Anki <https://apps.ankiweb.net> 
>> add-on then pulls these snippets into Anki where you can review them 
>> regularly. The Anki cards link back to the tiddler they came from so you 
>> can find the context if you need it, and if you edit the content in 
>> TiddlyWiki or move it around, your Anki collection gets updated to match on 
>> your next sync, maintaining your review history.
>>
>> Here's a little snip of the syntax, the rendering in a TiddlyWiki, and 
>> the card in Anki (permalink to this page in the docs 
>> <https://sobjornstad.github.io/TiddlyRemember/#Question-and-answer%20notes>
>> ):
>>
>> [image: syntax.png]
>>
>> There are cloze deletion cards too (if you're not a memory geek, you 
>> might call these "fill in the blanks cards").
>>
>> Credit for this idea goes to Andy Matuschak, who reported building a 
>> private tool that worked similarly for his notes system 
>> <https://notes.andymatuschak.org/>. I cannot for the life of me find 
>> this note now (if someone knows where it is, please post the link!).
>>
>> Check it out and install from here: 
>> https://sobjornstad.github.io/TiddlyRemember/.
>>
>> I'm hoping this is a reasonably stable and functional version (thus the 
>> 1.0.0 moniker), but I've only been using it myself for a couple of weeks as 
>> I've been developing, and there are definitely improvements possible, so 
>> suggestions and pull requests are welcome! The two biggest areas for 
>> improvement I see that I'm not sure how to attack are:
>>
>>- You have to have TiddlyWiki installed on Node on your system to use 
>>TiddlyRemember. (You can use TiddlyRemember fine with a single-file wiki 
>>th

[tw5] Re: add hour to field

[Soren Bjornstad]

Mystery solved! I needed to look up the syntax of compare the other day and 
thought I was just being dense when I couldn't find it in the list.

On Sunday, July 4, 2021 at 6:34:36 PM UTC-5 Eric Shulman wrote:

> <<.group-heading "String Operators">>
> <<.operator-rows "[tag[Filter Operators]!tag[Order 
> Operators]!tag[Mathematics Operators]tag[String Operators]!tag[Tag 
> Operators]!tag[Special Operators]sort[]]">>
> <<.group-heading "Mathematics Operators">>
> <<.operator-rows "[tag[Filter Operators]!tag[Order 
> Operators]tag[Mathematics Operators]!tag[String Operators]!tag[Tag 
> Operators]!tag[Special Operators]sort[]]">>
>
> On Sunday, July 4, 2021 at 4:22:07 PM UTC-7 Brian Radspinner wrote:
>
>> The compare operator should be added to the Mathematics section of the 
>> Filter 
>> Operators  table, I had no 
>> idea it existed until I saw Eric's answer above.
>>
>
> https://tiddlywiki.com/#compare%20Operator works for both numeric and 
> string comparisons, and is thus tagged as both "Mathematics Operator" and 
> "String Operator".  However, in https://tiddlywiki.com/#Filter%20Operators, 
> each of those tag categories excludes the all other categories, so 
> "compare" does not appear in either table
>
> -e
>
>

-- 
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/deba7e33-7586-4e06-8cbf-5103c3fe8d3bn%40googlegroups.com.

[tw5] Re: What is this weird error in "define"?

[Soren Bjornstad]

That's just how macros work in TiddlyWiki. Any pragmas (things beginning 
with a \), including \define, have to come before all non-pragma content in 
a tiddler.

On Sunday, July 4, 2021 at 7:41:42 AM UTC-5 miket...@gmail.com wrote:

> I want to make a list of pictures with an address.
> https://i.imgur.com/zRhtrSo.jpg
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *\define 
> image-picker2(actions,filter:"[all[tiddlers+shadows]tag[$:/tags/Image]]",subfilter:"")  
> class="tc-image-chooser"><$vars state-system=< "$:/state/image-picker/system">>><$reveal type="match" text="hide" 
> default="hide" tag="div"><$macrocall $name="image-picker-list" 
> filter="""$filter$""" actions="""$actions$"""/><$reveal 
> state=<> type="nomatch" text="hide" default="hide" 
> tag="div"><$macrocall $name="image-picker-list" filter="""$filter$""" 
> actions="""$actions$"""/>\end<$button 
> message="tm-open-external-window" param={{!!url}}>Источник* 
> {{!!url}}* https://tiddlywiki.com/#image-picker%20Macro 
> <$edit-text 
> tiddler='$:/_MyImage' tag='input' placeholder='(unset)' 
> default=''/><$transclude tiddler={{$:/_MyImage}}/>---<$macrocall 
> $name='image-picker2' actions="<$action-setfield $tiddler='$:/_MyImage' 
> $value=<>/>"/>*
>
> But if you add something to the beginning, then everything breaks down!
> https://i.imgur.com/6zb4df6.jpg
>
> And even the old code doesn't work anymore. Why? What am I doing wrong?

-- 
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/a1940dc8-9daf-4720-b00f-417c816a0582n%40googlegroups.com.

[tw5] Re: Menubar Customization / Sticky Titles

[Soren Bjornstad]

I don't use the menubar plugin, but I did add a custom top bar of my own 
and got this working, so I'm guessing the same thing would work here. Edit 
the shadow tiddler $:/themes/tiddlywiki/vanilla/sticky. In the rule 
.tc-tiddler-title, change the *top* property to however tall the menu bar 
is.
 
On Saturday, July 3, 2021 at 5:20:32 PM UTC-5 miket...@gmail.com wrote:

> How did you solve this problem? I also ran into it and I haven’t gotten 
> anything good yet.
> The panel overlaps the buttons I want.
> https://i.imgur.com/86gVY7s.jpg
> понедельник, 1 июня 2020 г. в 13:54:53 UTC+3, Stobot: 
>
>> Birthe - thanks, the padding setting you suggested worked great. 
>>
>

-- 
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/6095d190-0f94-42b3-b17c-f06e8ecb07bcn%40googlegroups.com.

[tw5] Re: [TW5] Open all the tiddlers with a particular tag

[Soren Bjornstad]

This isn't the correct filter syntax for transcluding a field into the 
filter:

*<>*

You probably want:

*<>*


On Sunday, July 4, 2021 at 8:24:55 AM UTC-5 miket...@gmail.com wrote:

> Please tell me pls why these buttons do not work?
>
>
>
> *\define openByFilter(filter)<$button>open filtered tiddlers $filter$*
>
>
>
>
>
>
>
>
> *<$list filter=$filter$><$action-navigate 
> $to={{!!title}}/><$action-sendmessage 
> $message="tm-unfold-all-tiddlers"/>\end*
>
>
> *\define closeByFilter(filter)<$button>close filtered tiddlers $filter$*
>
>
>
>
>
>
>
> *<$list filter=$filter$><$action-sendmessage 
> $message="tm-close-tiddler"/>\end*
>
>
> *<$select field="target" default='(none)'> value="null">(none)*
> *<$list filter="[tags[]!is[system]sort[title]]">*
>
>
>
>
>
> *>><$view 
> field="title"/>*
>
>
> *<>< "[tag[{{!!target}}]]">>*
>
> пятница, 28 июля 2017 г. в 16:41:14 UTC+3, Andrew: 
>
>> Check out my button 
>> http://t5a.tiddlyspot.com/#%24%3A%2Fplugins%2Fajh%2Fopenall plugin that 
>> can be installed from my library 
>> http://t5a.tiddlyspot.com/#Plugin%20Library
>
>

-- 
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/640972d0-0d68-4842-a910-cffde504f67cn%40googlegroups.com.

[tw5] Re: How can you display a list at the click of a button?

[Soren Bjornstad]

Mike,

An action cannot directly contain wikitext that should appear -- it can 
generally only contain action widgets (there are a few exceptions, like you 
can use a list widget to create a bunch of actions matching some pattern). 
The general pattern for creating a button that hides/shows content is to 
create a field that contains information about whether or not to show the 
content, then use a $reveal or $list widget to control whether it appears. 
For instance, to use a field called "show-content" on the current tiddler 
to control the display:

\define show-actions() <$action-setfield show-content="yes"/>
\define hide-actions() <$action-setfield show-content="no"/>

<$reveal state="show-content" type="match" text="yes">
  <$list filter="[tag[About]]">
<$link/>
{{||$:/core/templates/static-tiddler}}
  
  <$button actions=<>>Hide me again

<$reveal state="!!show-content" type="nomatch" text="yes">
  <$button actions=<>>
Click me!
  


(Note that unlike in your example, I've included an action and button to 
hide the content again. You can of course take that out if you don't want 
it...but the only way to get the content to go away again will be to go in 
and manually change the field on the current tiddler.)

You might also like to use a temporary tiddler, rather than a field on the 
current tiddler, to store whether the content should be open. If so, you 
would do something like:

\define show-actions() <$action-setfield $tiddler=<> show-content="yes"/>

<$reveal state=<> type="match" 
text="yes">

<> may not be necessary depending on your use case -- it prevents 
name collisions if you use this as a template on multiple tiddlers 
(otherwise, clicking the "show" button on one tiddler that uses the 
template will result in the content showing on all of them).

More information: Hiding and Showing Things 
 (Grok 
TiddlyWiki), action widgets  (TW 
docs), $reveal widget  (TW docs), qualify 
macro  (Grok TiddlyWiki).
On Sunday, July 4, 2021 at 7:47:10 AM UTC-5 miket...@gmail.com wrote:

> For the button I want to make an Action. I took the example from the help 
> as a basis, but of course it does not work :)
>
>
>
>
>
>
>
>
>
>
> *\define my-actions()<$list filter="[tag[About]]"><$link/>   
>  {{||$:/core/templates/static-tiddler}}\end<$button 
> actions=<>>Click me!*

-- 
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/5f8b9f90-8c60-4225-9873-a59dcfdd2ce5n%40googlegroups.com.

[tw5] Re: How do I clear a text field?

[Soren Bjornstad]

I wonder if your shell is trying to interpret the [is[image]] as a glob and 
passing a bad filter to TiddlyWiki – have you tried putting that parameter 
in quotes? (It appears to work right in Bash, but not sure what shell 
you're using.)

Also, can you run other commands against *mynewwiki* successfully?

I use this command line myself in a build script that runs every day and it 
works fine for me, so I don't think the instructions are wrong in the 
general case.

On Friday, July 2, 2021 at 6:30:39 PM UTC-5 miket...@gmail.com wrote:

> In the ExternalImages documentation, I need to enter a command to clear 
> old information.
> *--setfield [is[image]] text "" text/plain* 
> https://tiddlywiki.com/static/ExternalImages.html
>
> But this command doesn't work! And it throws an error 
> *ERR_INVALID_ARG_TYPE*
> https://i.imgur.com/UThaiys.jpg
>
> This is written about the setfield command.
> *templatetitle* - the tiddler to wikify into the specified field. If 
> blank or missing then the specified *field is deleted *
> https://tiddlywiki.com/static/SetFieldCommand.html
>
> What should be the command to remove old information in this case?
>

-- 
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/9f9444bd-c7d3-43c2-9fbe-ed05db455775n%40googlegroups.com.

[tw5] Re: List with tags and links to topics

[Soren Bjornstad]

Generally, the only time you should use an  tag in TiddlyWiki is for 
external links. Otherwise, <$link> makes more sense, as this handles some 
functionality for you, like adding the # and applying appropriate styles if 
the tiddler is missing, a shadow tiddler, etc.

As for why what you did didn't work, this is never valid syntax in 
TiddlyWiki:

attribute="text{{transclusion}}"

Within attributes, transclusions are not evaluated within quotes. Thus, the 
value of an attribute can be either a constant value in quotes, *or* a 
transclusion (<>, {{field}}, or {{{filtered}}}) -- not both. If 
you need to concatenate several things in the value of an attribute, you 
can use either a macro with text substitution:

\define concat() text$(transclusion)$

<$set transclusion={{transclusion}}>
<$widget attribute=<>/>


Or a filtered transclusion:

<$widget attribute={{{ [[text]addsuffix{transclusion}] }}}/>

On Saturday, July 3, 2021 at 10:18:15 AM UTC-5 miket...@gmail.com wrote:

> I love this kind of list I found in the documentation.
> https://i.imgur.com/4Hh7Rcs.jpg
>
>
>
>
>
>
> *<$list 
> filter="[tag[Features]sort[title]]"><>{{||$:/core/ui/ViewTemplate/tags}}*
>
> But I want to be able to click on the headings to navigate. And it just 
> doesn't work (only Camel case on example).
> I tried to put it inside the HTML but it doesn't work.
>
>
> * href="#<>"><> href="#{{!!title}}">{{!!title}}*
>
> Variables <> {{!!title}} are not readable inside the HTML 
> tag <> and no links are received.
>
> https://i.imgur.com/QD3MXR1.jpg

-- 
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/114d0bc9-cb08-42a2-a48b-6e2b3a447708n%40googlegroups.com.

[tw5] Re: How to make a tree structure of the notes?

[Soren Bjornstad]

On Wednesday, June 30, 2021 at 11:14:11 AM UTC-5 Mark S. wrote:

>  My current note taking system uses tags for the big "trunk" picture and 
> then uses titles for the finer, "leaf" structure so as not to create excess 
> tags.
>

This is a really cool idea! I don't think I've seen this one before, I'll 
have to give it a try. 

-- 
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/856d4cc6-61f3-481e-9666-25418bdb8e36n%40googlegroups.com.

[tw5] Re: How to make a tree structure of the notes?

[Soren Bjornstad]

In TiddlyWiki, you can create a tree structure with tags (TW documentation 
; Grok TiddlyWiki 
). Then you can make a table of 
contents to display them (TW documentation 
;
 
Grok TiddlyWiki 

).

I would caution that trying to organize your whole wiki into a tree 
structure can be limiting. Hierarchies where everything goes in one place 
are nice and orderly, but they make it harder to reuse ideas in different 
contexts. So I tend to prefer linking as a primary means of organizing 
content, and then creating smaller clusters of tree-structured notes within 
the wiki where needed.

On Wednesday, June 30, 2021 at 1:32:08 AM UTC-5 imleg...@gmail.com wrote:

> When I use tiddly I find it is easy to make a small piece of knowledge? 
> But I really need to make a tree structure of the notes, because the notes 
> I took are too scattered which make it hard to build a summary view of the 
> knowledge

-- 
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/b36a9957-ef42-427a-8ebf-d14502093478n%40googlegroups.com.

[tw5] Re: Number of conversations by contact

[Soren Bjornstad]

Hi JJ,

On Wednesday, June 30, 2021 at 6:18:58 AM UTC-5 JJ wrote:

> Now I'd like to create a table, which shows me the People I talked to with 
> the amount of conversations I had with them. Sometimes, the conversation is 
> with more than one person, so I write two names in the contact-field, like 
> "PersonOne PersonTwo". I understood that separating those, I should use the 
> enlist-operator.
>

I don't see you using the enlist operator in the snippet above? Anyway, I 
would use contains , not 
*enlist* – it's possible to do it with *enlist*, but makes things 
unnecessarily trickier.
 

> I tried the following, but I cannot find out, what to write in the space 
> marked with . If I try to enter one Persons name manually, the correct 
> count shows up in all rows, as expected. Somehow, I need to reference the 
> currentTiddler, but I don't know how.
>

You need to use a *soft parameter* with <> or {} instead of [], which fill 
in the value of a variable or field respectively. So your filter would look 
like:

[tag[Conversation]contains:contact]

Or equivalently:

[tag[Conversation]contains:contact{!!title}]

See Filters and Transclusions 
 for more 
on this.

It's worth noting you can take advantage of the $count widget and some 
default parameters of $link to simplify all this:

<$list filter="[tag[Person]sort[caption]]">

  <$link />
  <$count 
filter="[tag[Conversation]contains:contact]"/>



(But did you really want the title to display for each person after you 
sorted by the caption? You might prefer:

<$link to={{!!title}}><$transclude 
field="caption">{{!!title}}

...which will show the caption if it exists and the title otherwise, 
linking to the title in either case.)

-- 
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/7f9762a1-5ba9-4e3d-8c5c-d88ed5b04bf0n%40googlegroups.com.

[tw5] Re: Date In "Title of new tiddlers" Setting

[Soren Bjornstad]

*$:/core/ui/Actions/new-journal* contains:

<$wikify name="journalTitle" text="""<$macrocall $name="now" 
format=<>/>""">
[...]
<$action-sendmessage $message="tm-new-tiddler" title=<> 
tags=<> text=<>/>

*$:/core/ui/Actions/new-tiddler* contains no such wikify, just:

<$action-sendmessage $message="tm-new-tiddler" tags=<>/>

I haven't tried it, but I would think it would be relatively 
straightforward to override this tiddler and add an appropriate wikify 
widget and a *title* parameter to $action-sendmessage.

On Tuesday, June 29, 2021 at 3:37:26 PM UTC-5 iamdar...@gmail.com wrote:

> Is there a way to add a formatted date to the "Title of new tiddlers" 
> field like you can in the "Title of new journal tiddlers" field?
>
> I'm trying to add *MM/DD -* to the front of each new tiddler based on how 
> I am using it. I can always just delete it if I don't need the MM/DD - in 
> the title but prefer to have it if I did. 
>
> However, it doesn't seem that the field accepts any time of code so I'm 
> not sure if it is even possible. 
>
> Thanks!
> DM
>

-- 
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/d59f2ab1-18fe-4207-b68b-e0ab68e1fed6n%40googlegroups.com.

[tw5] Re: template: where is the widget???

[Soren Bjornstad]

On Monday, June 28, 2021 at 6:15:35 PM UTC-5 jn.pierr...@gmail.com wrote:

> Thank you to both of you for your explanation. The information on the 
> system tag was very helpful.
>
> @Soren: you write tgis in your textbook:
> [...]
>

I think PMario covered everything you asked very well, let me know if 
there's anything you still wanted to know. :)

-- 
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/dbef86b1-fe52-42c8-a504-12fa7299bee3n%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

[Soren Bjornstad]

Probably did, but right now that one is more or less just <> -- there's no special functionality for 
selecting questions out of the tiddlers. That's something I'd like to 
improve in the future.

On Monday, June 28, 2021 at 12:12:30 PM UTC-5 mark.cu...@gmail.com wrote:

> Is there any chance your filter missed the OpenQuestions tiddler as well?
>
> On Sunday, April 18, 2021 at 11:55:35 AM UTC-4 Soren Bjornstad wrote:
>
>> Looks like my filter missed the TODO tiddler, which should contain:
>>
>> \define todore() \[\[TODO\]\]:
>> \define splitre() [\.\?!]
>>
>> To add a TODO item to this list, simply link to [[TODO]].
>>
>> 
>> <$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer>
>>   <$list 
>> filter="[get[text]splitregexplast[]splitregexpfirst[]]"
>>  
>> variable=inner>
>>   <$link to=<>/>
>> ''TODO:'' <>.
>> 
>> 
>> 
>>
>> On Sunday, April 18, 2021 at 10:23:28 AM UTC-5 ludwa6 wrote:
>>
>>> Good to know, Soren, but first i have to get the basics under control, 
>>> like: TODO items!  
>>>
>>> About that, you say in your video at 28'47" 
>>> <https://youtu.be/GjpjE5pMZMI?t=1727> : "*Anywhere that i write the 
>>> word todo in square brackets, so link to the tiddler todo, gets 
>>> automatically pulled in here"* -here being presumably TODO tab of 
>>> "Write" feature, since that is the context.  I have tried this a number of 
>>> ways -with square brackets of both types: single (would have to be by some 
>>> magic i don't see, but since you didn't say "DOUBLE"...) and double 
>>> (creating a missing tiddler, which i then activated, tagged "Stub"), 
>>> whether as TODO uppercase or lower... Nothing shows up as expected in that 
>>> tab, at all.
>>>
>>> So what am i missing here, i wonder?
>>>
>>> /walt
>>>
>>> On Sunday, April 18, 2021 at 3:31:11 PM UTC+1 Soren Bjornstad wrote:
>>>
>>>> Oh, to convert a single-file wiki to Node.js, all you need is:
>>>>
>>>> tiddlywiki --load path/to/single/file.html --savewikifolder 
>>>> path/to/output/folder
>>>>
>>>> You could even do this as a first step in the script above, if you 
>>>> wanted to normally edit in single-file mode but use the automated build.
>>>>
>>>> On Sunday, April 18, 2021 at 9:02:28 AM UTC-5 ludwa6 wrote:
>>>>
>>>>> Thank-you Soren, but to be clear: I'm working in single-file mode, 
>>>>> since i was unable to find a way to convert your file to node.js, though 
>>>>> that would probably make for a more elegant solution [*]... But the 
>>>>> "manual" method you propose below (with slight adaptation, see below) is 
>>>>> sufficiently well-automated, it makes my workflow relatively painless, as 
>>>>> follows:
>>>>>
>>>>>1. In TiddlyDesktop (where i am managing a fair mitt-full of TW5 
>>>>>instances), finish my days edits with a review to ensure tag "Public" 
>>>>> is on 
>>>>>all the right tiddlers, and none other;
>>>>>2. In $:/AdvancedSearch, run the filter-  
>>>>>[tag[Public]!is[system]]  -and upload the result set as .json, to...
>>>>>3. Drag & drop that .json file into the my local PUBLIC instance 
>>>>>(subset of the above), which is they synced to...
>>>>>4. My github.io repo <https://ludwa6.github.io/> : pull from there 
>>>>>(just to ensure there are no conflicting edits), then 
>>>>> commit/comment/push 
>>>>>changes online.
>>>>>
>>>>> NB: I'm using Atom text editor (on Mac, b/t/w, not Windows) for the 
>>>>> last step, just because i like its change management workflow, but 
>>>>> there's 
>>>>> a desktop app for Github that is probably the most intuitive GuI app for 
>>>>> this purpose.
>>>>>
>>>>> [*] As to that more elegant solution: if it were a node.js instance i 
>>>>> had in github, then i can see how it might be easier to manage a dataflow 
>>>>> based on individual tiddlers, instead of one big .html file -especially 
>>>>> if 
>>>>> others were to be engaged in collaborative editing (via Github Pull 
>>>>> Request)... But that's a bridge t

[tw5] Re: template: where is the widget???

[Soren Bjornstad]

>
> I've read in the doc that widgets are the fundamental part of tiddlywiki 
> and that all wiki syntax sugar is finally resolved as a number of widgets.
>
> Use of template is only described with transclusion as {{||template}} 
> (with tiddler or field or index before ||).
>
> the transclude widget has no template attribute.
>
> How then is done the transclusion? Shouldn't the transclude widget have a 
> template attribute?
>

Actually, the *template *is what's being transcluded during a transclusion, 
not the tiddler. When you transclude a tiddler through a template, the 
current tiddler is set to that tiddler and then the template is transcluded.

{{Tiddler||Template}} evaluates to:

<$tiddler tiddler=Tiddler>
  <$transclude tiddler=Template/>


{{||Template}} doesn't change the current tiddler and so evaluates to 
simply:

<$transclude tiddler=Template/>

{{Tiddler1}} is shorthand for {{Tiddler1||Tiddler1}}, and evaluates to:

<$tiddler tiddler=Tiddler1>
  <$transclude tiddler=Tiddler1/>


More on templates and current tiddlers 
 
from 
my TiddlyWiki textbook.
 

> Also, I've come across $:/tags/ViewTemplate which is only described as: 
> "The system tag  $:/tags/ViewTemplate 
> marks the view template." which is not very telling.
>
I've done tenplates tgat work fine. They are not 
> tagged $:/tags/ViewTemplate. If I tag them as scuch, they act aout as if 
> their content was twice included. What does $:/tags/ViewTemplate really do? 
> How should it be used?
>

Haha, some of those tag explanations could use some work. TiddlyWiki just 
transcludes all the tiddlers with that tag in sequence when it is rendering 
each tiddler:

<$list
 filter="[all[shadows+tiddlers]tag[$:/tags/ViewTemplate]!has[draft.of]]" 
variable="listItem">
  <$transclude tiddler=<>/>


So the view template is essentially a list of templates that get 
*automatically* transcluded for every tiddler without mentioning them in 
your wikitext. This includes things like the title, the tags bar, and so on.

More on the view template 
.

-- 
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/bf3dcb60-76bd-4685-a4fd-643418e3d8c5n%40googlegroups.com.

[tw5] Re: Restyling a drop zone

[Soren Bjornstad]

Yes, $:/sib/Templates/Automatic/OpenTopBar 
<https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2FTemplates%2FAutomatic%2FOpenTopBar>.
 
I tagged it $:/tags/TopLeftBar, but I think one could instead use the 
PageTemplate or several other tags as well since the location on screen is 
fixed via CSS.

<$list filter=<> variable=_>

<>



(ff <https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2FMacros%2Fff> 
is a *feature flag *conditional, which makes it possible to show and hide 
it on the fly, and separately for the public and private editions. I don't 
have it on in public, but if you search for FeatureFlags and turn the "Open 
top bar" checkbox on, you can see this in action.)

On Sunday, June 27, 2021 at 12:06:14 PM UTC-5 iamdar...@gmail.com wrote:

> Hello Soren!
>
> As always awesome solution/work!
>
> I just had a quick question; is it safe to assume that you need a tiddler, 
> with the following code, open in the storylist for your code to work? Or 
> did you add it to a template?
>
> 
> <>
> 
>
> Thanks!
>
> On Sunday, June 27, 2021 at 12:41:25 PM UTC-4 Soren Bjornstad wrote:
>
>> Maki, yeah, I had previously tried inline-block along with a bunch of 
>> other things in that rule. It didn't help because I hadn't targeted the 
>> item underneath it as well.
>>
>> Saq, thanks, that was *very* helpful. (For anyone else who comes along, 
>> that should be "tc-dragover", with a dash, not a dot.)
>>
>> The selector I had missed targeting was *.tc-droppable.tc-dragover > 
>> .tc-droppable-placeholder*. (Both the droppable divs and the placeholder 
>> divs beneath them need to be inline-block.) I also needed this goofy rule:
>>
>> div.sib-quick-tiddler-jump ul > div.tc-droppable 
>> div.tc-droppable-placeholder svg {
>> height: 0;
>> width: 1rem;
>> }
>>
>> Yes, that's an *svg*, because TiddlyWiki uses a blank image within a 
>> *div* for the placeholder after the last *li* in list-links-draggable. I 
>> assume there is a good reason for this. :-)
>>
>> Final version for anyone interested:
>>
>> div.sib-quick-tiddler-jump {
>> background-color: <>;
>> position: fixed;
>> z-index: 850;
>> display: inline-block;
>> top: 0;
>> right: 0;
>> left: 0;
>> text-align: center;
>> height: 30px;
>> overflow: auto;
>> border-bottom: 1px solid <>;
>> padding-bottom: 3px;
>> padding-top: 3px;
>> font-size: 12px;
>> }
>>
>> div.sib-quick-tiddler-jump a {
>> color: <>;
>> }
>>
>> div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
>> font-weight: normal;
>> }
>>
>> div.sib-quick-tiddler-jump ul {
>> list-style-type: none;
>> margin: 0;
>> padding: 0;
>> }
>>
>> /* Droppable placeholders take up no space until we drag something there. 
>> */
>> div.sib-quick-tiddler-jump ul li.tc-droppable 
>> div.tc-droppable-placeholder {
>> height: 0;
>> }
>>
>> /* TW inserts this as a placeholder after the last item. We have to 
>> resize it to match the rest. */
>> div.sib-quick-tiddler-jump ul > div.tc-droppable 
>> div.tc-droppable-placeholder svg {
>> height: 0;
>> width: 1rem;
>> }
>>
>> div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
>> display: inline-block;
>> }
>>
>> div.sib-quick-tiddler-jump ul > li.tc-droppable div,
>> div.sib-quick-tiddler-jump ul > div.tc-droppable div {
>> display: inline-block;
>> }
>>
>> div.sib-quick-tiddler-jump .tc-droppable.tc-dragover > 
>> .tc-droppable-placeholder {
>> display: inline-block;
>> background-color: green;
>> border: 0px;
>> width: 1rem;
>> height: 1rem;
>> margin-bottom: 0;
>> margin-top: 0;
>> padding-bottom: 0;
>> padding-top: 0;
>> }
>>
>> div.sib-quick-tiddler-jump ul li, div.sib-quick-tiddler-jump ul > 
>> div.tc-droppable {
>> display: inline-block;
>> }
>>
>> .sib-quick-tiddler-jump ul li div:nth-child(2):after {
>> padding-left: 5px;
>> content: "·";
>> padding-right: 5px;
>> }
>>
>> /* not last-child because there's a dropzone after it */
>> .sib-quick-tiddler-jump ul li:nth-last-child(2) div:after {
>> content: "";
>> }
>>
>>
>> On Sunday, June 27, 2021 at 4:11:05 AM UTC-5 saq.i...@gmail.com wrote:
>>
>>> Inspect the dropzone DOM node with the browser dev tools and add the 
>>> class "tc.dragover". This will allow you

[tw5] Re: Refresh tiddler automatically

[Soren Bjornstad]

OK, I started having a major problem which took me a good hour to debug…but 
I have a fix. When I tried to use the TiddlyWiki CLI (for instance, with a 
--savewikifolder), it would hang indefinitely, because it is waiting on the 
timer to be torn down before terminating. Fortunately, there is a tag 
$:/tags/StartupAction/Browser 
<https://tiddlywiki.com/#SystemTag%3A%20%24%3A%2Ftags%2FStartupAction%2FBrowser>
 which 
invokes the timer setup only when viewing the wiki in the browser. So I 
just removed $:/tags/StartupAction and added that one, and now it's working 
fine again.

On Sunday, June 27, 2021 at 10:45:26 AM UTC-5 Soren Bjornstad wrote:

> Eric,
>
> This worked perfectly! Thanks for the widget and the instructions.
>
> On Saturday, June 26, 2021 at 11:57:27 PM UTC-5 Eric Shulman wrote:
>
>> On Saturday, June 26, 2021 at 8:05:15 PM UTC-7 Soren Bjornstad wrote:
>>
>>> Has anyone found a way to make TiddlyWiki re-render a part of the page 
>>> template periodically?
>>
>> I'd like to have a section in my page template that does a calculation 
>>> based on the current time, and would love if I didn't have to click a 
>>> button all the time to update it. 
>>
>> Maybe some kind of event that's scheduled in JavaScript and fires every 
>>> minute?
>>
>>
>> My TiddlyTools Timer functions can do this.
>>
>> 1) Copy the $action-timeout widget from 
>>   
>>  http://tiddlytools.com/timer.html#TiddlyTools%2FTime%2Faction-timeout.js 
>> <http://tiddlytools.com/timer.html#TiddlyTools%2FTime%2Faction-timeout.js>
>>
>> 2) Create a "MinuteTickerStartup" tiddler, tagged with 
>> *$:/tags/StartupAction*, containing:
>> \define minute_ticker() <$action-setfield 
>> $tiddler="$:/temp/time/minuteticker" text=<> />
>> <$action-timeout interval=6 actions=<> />
>>
>> 3) In a tiddler tagged with *$:/tags/PageTemplate*, put the content you 
>> want to automatically re-render each minute, like this:
>> <$vars ticker={{$:/temp/time/minuteticker}}>
>>*** content you want to re-render ***
>> 
>>
>> Notes:
>> 1) MinuteTickerStartup is invoked *once* when you load your TiddlyWiki 
>> and sets up an javascript "interval" timer that is triggered every minute 
>> (6 milliseconds)
>> 2) The ticker action updates the contents of *$:/temp/time/minuteticker* to 
>> contain the current time (0hh0mm0ss)
>> 3) The $vars "wrapper" in the page template tiddler creates a refresh 
>> dependency associated with the current value in 
>> *$:/temp/time/minuteticker*
>>
>> The result is that whatever content is in your page template will be 
>> re-rendered once per minute.  Q.E.D.
>>
>> enjoy,
>> -e
>>
>

-- 
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/b880880e-77f1-460a-b604-93f833cff211n%40googlegroups.com.

[tw5] Re: Restyling a drop zone

[Soren Bjornstad]

Maki, yeah, I had previously tried inline-block along with a bunch of other 
things in that rule. It didn't help because I hadn't targeted the item 
underneath it as well.

Saq, thanks, that was *very* helpful. (For anyone else who comes along, 
that should be "tc-dragover", with a dash, not a dot.)

The selector I had missed targeting was *.tc-droppable.tc-dragover > 
.tc-droppable-placeholder*. (Both the droppable divs and the placeholder 
divs beneath them need to be inline-block.) I also needed this goofy rule:

div.sib-quick-tiddler-jump ul > div.tc-droppable 
div.tc-droppable-placeholder svg {
height: 0;
width: 1rem;
}

Yes, that's an *svg*, because TiddlyWiki uses a blank image within a *div* for 
the placeholder after the last *li* in list-links-draggable. I assume there 
is a good reason for this. :-)

Final version for anyone interested:

div.sib-quick-tiddler-jump {
background-color: <>;
position: fixed;
z-index: 850;
display: inline-block;
top: 0;
right: 0;
left: 0;
text-align: center;
height: 30px;
overflow: auto;
border-bottom: 1px solid <>;
padding-bottom: 3px;
padding-top: 3px;
font-size: 12px;
}

div.sib-quick-tiddler-jump a {
color: <>;
}

div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
font-weight: normal;
}

div.sib-quick-tiddler-jump ul {
list-style-type: none;
margin: 0;
padding: 0;
}

/* Droppable placeholders take up no space until we drag something there. */
div.sib-quick-tiddler-jump ul li.tc-droppable div.tc-droppable-placeholder {
height: 0;
}

/* TW inserts this as a placeholder after the last item. We have to resize 
it to match the rest. */
div.sib-quick-tiddler-jump ul > div.tc-droppable 
div.tc-droppable-placeholder svg {
height: 0;
width: 1rem;
}

div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
display: inline-block;
}

div.sib-quick-tiddler-jump ul > li.tc-droppable div,
div.sib-quick-tiddler-jump ul > div.tc-droppable div {
display: inline-block;
}

div.sib-quick-tiddler-jump .tc-droppable.tc-dragover > 
.tc-droppable-placeholder {
display: inline-block;
background-color: green;
border: 0px;
width: 1rem;
height: 1rem;
margin-bottom: 0;
margin-top: 0;
padding-bottom: 0;
padding-top: 0;
}

div.sib-quick-tiddler-jump ul li, div.sib-quick-tiddler-jump ul > 
div.tc-droppable {
display: inline-block;
}

.sib-quick-tiddler-jump ul li div:nth-child(2):after {
padding-left: 5px;
content: "·";
padding-right: 5px;
}

/* not last-child because there's a dropzone after it */
.sib-quick-tiddler-jump ul li:nth-last-child(2) div:after {
content: "";
}


On Sunday, June 27, 2021 at 4:11:05 AM UTC-5 saq.i...@gmail.com wrote:

> Inspect the dropzone DOM node with the browser dev tools and add the class 
> "tc.dragover". This will allow you see what CSS is active during the drag 
> over and make it easier to arrive at a solution.
>
> On Sunday, June 27, 2021 at 1:18:07 AM UTC+2 Soren Bjornstad wrote:
>
>> I'm creating a horizontal list of my open tiddlers that runs across the 
>> top of the wiki, like this:
>>
>> [image: Screenshot from 2021-06-26 18-13-01.png]
>>
>> It's based on *list-links-draggable* and works great except for when I 
>> try to drag something to a different position. When I try, the bar scrolls 
>> to fit the dropzone on a separate line, so that I can no longer see where 
>> I'm moving the tiddler to:
>>
>> [image: 2.png]
>>
>> I tried poking through the theme CSS for a bit, but wasn't able to find 
>> anything that worked. It doesn't help that it's impossible to carefully 
>> inspect the DOM with the browser devtools since the mouse is tied up with 
>> the drag. Can someone point me to how I'd make the dropzone end up 
>> horizontally inline with the items, instead of above/below them?
>>
>> Here's the code of the tiddler/CSS that I currently have:
>>
>> 
>> <>
>> 
>>
>> 
>> div.sib-quick-tiddler-jump {
>> background-color: <<color menubar-background>>;
>> position: fixed;
>> z-index: 850;
>> display: inline-block;
>> top: 0;
>> right: 0;
>> left: 0;
>> text-align: center;
>> height: 25px;
>> overflow: auto;
>> border-bottom: 1px solid <<color muted-foreground>>;
>> padding-bottom: 3px;
>> padding-top: 3px;
>> font-size: 12px;
>> }
>>
>> div.sib-quick-tiddler-jump a {
>> color: <<color menubar-foreground>>;
>> }
>>
>> div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
>> font-weight: normal;
>> }
>>
>> div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
>> display: block;
>> position: relative;
>> top: 0;
>> left: 0;
>> right: 0;
>> }
>>
>> div.sib-quick

[tw5] Re: Refresh tiddler automatically

[Soren Bjornstad]

Eric,

This worked perfectly! Thanks for the widget and the instructions.

On Saturday, June 26, 2021 at 11:57:27 PM UTC-5 Eric Shulman wrote:

> On Saturday, June 26, 2021 at 8:05:15 PM UTC-7 Soren Bjornstad wrote:
>
>> Has anyone found a way to make TiddlyWiki re-render a part of the page 
>> template periodically?
>
> I'd like to have a section in my page template that does a calculation 
>> based on the current time, and would love if I didn't have to click a 
>> button all the time to update it. 
>
> Maybe some kind of event that's scheduled in JavaScript and fires every 
>> minute?
>
>
> My TiddlyTools Timer functions can do this.
>
> 1) Copy the $action-timeout widget from 
>   
>  http://tiddlytools.com/timer.html#TiddlyTools%2FTime%2Faction-timeout.js 
> <http://tiddlytools.com/timer.html#TiddlyTools%2FTime%2Faction-timeout.js>
>
> 2) Create a "MinuteTickerStartup" tiddler, tagged with 
> *$:/tags/StartupAction*, containing:
> \define minute_ticker() <$action-setfield 
> $tiddler="$:/temp/time/minuteticker" text=<> />
> <$action-timeout interval=6 actions=<> />
>
> 3) In a tiddler tagged with *$:/tags/PageTemplate*, put the content you 
> want to automatically re-render each minute, like this:
> <$vars ticker={{$:/temp/time/minuteticker}}>
>*** content you want to re-render ***
> 
>
> Notes:
> 1) MinuteTickerStartup is invoked *once* when you load your TiddlyWiki 
> and sets up an javascript "interval" timer that is triggered every minute 
> (6 milliseconds)
> 2) The ticker action updates the contents of *$:/temp/time/minuteticker* to 
> contain the current time (0hh0mm0ss)
> 3) The $vars "wrapper" in the page template tiddler creates a refresh 
> dependency associated with the current value in 
> *$:/temp/time/minuteticker*
>
> The result is that whatever content is in your page template will be 
> re-rendered once per minute.  Q.E.D.
>
> enjoy,
> -e
>

-- 
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/5d586d13-48f6-4e44-b06c-be92e55b8461n%40googlegroups.com.

[tw5] Re: Soren Bjornstad’s reading list tutorial

[Soren Bjornstad]

And you're very welcome for the tutorial!

On Sunday, June 27, 2021 at 8:28:04 AM UTC-5 Soren Bjornstad wrote:

> Rehali,
>
> I see two problems here:
>
> 1. You have a typo in your transclusion syntax – it should be *{!!title}*, 
> not *{!title}*.
> 2. If the author field contains a link in [[double square brackets]] or is 
> a list of several authors, like I did in the video, then you need to use 
> *contains:*, not *field: *– *field: *does an exact match on the text 
> contents of the field, and this won't be an exact match because the field 
> contains extra square brackets. (Alternatively, if you only ever want to 
> have one author, you could just remove the brackets and not treat it as a 
> list.)
>
> On Saturday, June 26, 2021 at 11:21:13 PM UTC-5 Rehali wrote:
>
>> Before the question, first of all if you read this Soren then many thanks 
>> for your excellent tutorial on YouTube - it’s what got me started with 
>> tiddlywiki.
>>
>> Now the question. If you’ve seen the tutorial, what I would like to do is 
>> to display a list of the books on the tiddly belonging to their author. The 
>> author field for each book is a link, as in [[Charles Dickens]]
>>
>> I was hoping to use a filter on each Author tiddler like:
>>
>> [tag[Source]field:author{!title}]
>>
>> but I can’t get anything to work.
>>
>> Any help would be much appreciated.
>>
>

-- 
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/2899304f-4b81-4b1d-82c6-6b48bc986c25n%40googlegroups.com.

[tw5] Re: Soren Bjornstad’s reading list tutorial

[Soren Bjornstad]

Rehali,

I see two problems here:

1. You have a typo in your transclusion syntax – it should be *{!!title}*, 
not *{!title}*.
2. If the author field contains a link in [[double square brackets]] or is 
a list of several authors, like I did in the video, then you need to use 
*contains:*, not *field: *– *field: *does an exact match on the text 
contents of the field, and this won't be an exact match because the field 
contains extra square brackets. (Alternatively, if you only ever want to 
have one author, you could just remove the brackets and not treat it as a 
list.)

On Saturday, June 26, 2021 at 11:21:13 PM UTC-5 Rehali wrote:

> Before the question, first of all if you read this Soren then many thanks 
> for your excellent tutorial on YouTube - it’s what got me started with 
> tiddlywiki.
>
> Now the question. If you’ve seen the tutorial, what I would like to do is 
> to display a list of the books on the tiddly belonging to their author. The 
> author field for each book is a link, as in [[Charles Dickens]]
>
> I was hoping to use a filter on each Author tiddler like:
>
> [tag[Source]field:author{!title}]
>
> but I can’t get anything to work.
>
> Any help would be much appreciated.
>

-- 
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/d67282a0-eb82-40c1-8ec1-d5c938f4f72en%40googlegroups.com.

[tw5] Refresh tiddler automatically

[Soren Bjornstad]

Has anyone found a way to make TiddlyWiki re-render a part of the page 
template periodically? I'd like to have a section in my page template that 
does a calculation based on the current time, and would love if I didn't 
have to click a button all the time to update it. Maybe some kind of event 
that's scheduled in JavaScript and fires every minute?

I did find this interesting thread 
, but it doesn't 
offer any kind of timer-based refresh.

-- 
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/181be645-98aa-4470-8d0a-b0aa2e1ab81cn%40googlegroups.com.

[tw5] Re: Linking to Field Values

[Soren Bjornstad]

Hi Merry,

This isn't valid XML/HTML/wikitext:

<$link to=<$view field=birthcountry/>

You can never nest widgets within attributes of other widgets like this 
(side note: notice that even if this was allowable, you would be missing a 
closing > after the /> to finish the opening $link tag). More generally, it 
might be worth learning now that in an attribute like to=, you can do 
exactly one of four things in TW:

   - to="constant value" [see note 1]
   - to={{field transclusion}}
   - to={{{filtered transclusion}}}
   - to=<>

Any combination of these, or any other content, won't work. Here's a summary 
of the available transclusion syntax 

.

Fortunately, there's no need to use a $view widget here – you can just 
transclude the field with the double-brace syntax:

<$link to={{!!birthcountry}}/>

[1] There are three other ways you can quote the value: """triple 
quotes""", 'single quotes', and sometimes no quotes at all (if there aren't 
any spaces or special characters in the value).
On Saturday, June 26, 2021 at 6:10:43 PM UTC-5 merry.ma...@gmail.com wrote:

> Hello, I think this is a pretty basic problem, but I've not been able to 
> figure out how to do it. 
>
> Within tiddlywiki, I have profiles for made-up individuals. I have 
> birthcountry of each individual recorded as a field. I also have 
> wikipedia-style sideboxes with individuals date of birth, date of death, 
> parentage, childrenetc and birthcountry as well.
>
> All I want to do is have it so that I can use the birthcountry field to 
> supply a value that I can use as both text and a link to another tiddler.
>
> For example: 
> John Smith
> Born - 04/05/1872 - Fantasyshire, MadeupLand (with "MadeupLand" value 
> drawn from the field and also used link to a tiddler with the title 
> "MadeupLand")
>
> Currently, I can retrieve the field value:
>
> <$view field=birthcountry/>
>
> And I can manually link to 'MadeupLand':
>
> <$link to="MadeupLand">
>
> But putting them together like this: 
>
> <$link to=<$view field=birthcountry/>
>
> Does not work, I just get "true"
>
> Any help would be much appreciated!
>

-- 
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/9d2b6680-e9e2-4307-87e6-875e7fd1dd69n%40googlegroups.com.

[tw5] Re: change color of field / tag when selected

[Soren Bjornstad]

Note: On line 5, I switched the field from *published *to *modified* so I 
could test on TiddlyWiki.com and forgot to change it back. You probably 
want it to be *published*.

On Wednesday, June 23, 2021 at 11:29:59 AM UTC-5 Soren Bjornstad wrote:

> If you switch to using a CSS class rather than the inline style to handle 
> your coloring, you can use an a:hover selector to apply different styling 
> when the cursor is over the link, like this:
>
> 
> <$link to={{!!title}} tooltip="Titel: {{!!title}}">
> <$view field="caption"><$view field="title"/>
>  --- 
> <$view field="modified" />
>  aus Gruppe: 
> <$view field="tags"/>
> 
> 
>
> 
> .myclass {
>   color: rgba(255, 201, 102, 0.8)
> }
> a:hover .myclass {
>   color: red;
> }
> 
>
> You can also use *.myclass:hover *as the selector instead of 
> *a:hover.myclass*, but then you have to hover directly over the text for 
> the color to change, rather than anywhere on the link.
>
> I am not sure if this would work with a drop-down and keyboard selection.
>
> On Wednesday, June 23, 2021 at 10:39:19 AM UTC-5 S² wrote:
>
>>
>> Hello,
>>
>> is it possible to change the color of "published" and "tags" when 
>> selecting an entry in the search list:
>> (for "title" it is working fine...)
>> [image: search.png]
>>
>> my Code:
>>
>> 
>> <$link to={{!!title}} tooltip="Titel: {{!!title}}">
>> <$view field="caption"><$view field="title"/>
>>  --- 
>> <$view field="published" 
>> />
>>  aus Gruppe:  
>> <$view 
>> field="tags"/> 
>> 
>> 
>>
>> Thanks for feedback
>> Stefan
>>
>

-- 
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/ca102a22-10e5-4389-9ddf-f44622609503n%40googlegroups.com.

[tw5] Re: change color of field / tag when selected

[Soren Bjornstad]

If you switch to using a CSS class rather than the inline style to handle 
your coloring, you can use an a:hover selector to apply different styling 
when the cursor is over the link, like this:


<$link to={{!!title}} tooltip="Titel: {{!!title}}">
<$view field="caption"><$view field="title"/>
 --- 
<$view field="modified" />
 aus Gruppe: 
<$view field="tags"/>




.myclass {
  color: rgba(255, 201, 102, 0.8)
}
a:hover .myclass {
  color: red;
}


You can also use *.myclass:hover *as the selector instead of 
*a:hover.myclass*, but then you have to hover directly over the text for 
the color to change, rather than anywhere on the link.

I am not sure if this would work with a drop-down and keyboard selection.

On Wednesday, June 23, 2021 at 10:39:19 AM UTC-5 S² wrote:

>
> Hello,
>
> is it possible to change the color of "published" and "tags" when 
> selecting an entry in the search list:
> (for "title" it is working fine...)
> [image: search.png]
>
> my Code:
>
> 
> <$link to={{!!title}} tooltip="Titel: {{!!title}}">
> <$view field="caption"><$view field="title"/>
>  --- 
> <$view field="published" 
> />
>  aus Gruppe:  
> <$view 
> field="tags"/> 
> 
> 
>
> Thanks for feedback
> Stefan
>

-- 
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/bf069b5c-8002-4e11-b157-fd36d3abde23n%40googlegroups.com.

[tw5] Re: Filter request: "except those transcluded in the" current tiddler

[Soren Bjornstad]

I'd like to draw attention to this PR that's been sitting for about a year 
due to needed improvements:
https://github.com/Jermolene/TiddlyWiki5/pull/4766

By making transclusion into a first-class citizen that TiddlyWiki keeps 
track of, it would produce an elegant solution for this problem and many 
others. 

On Wednesday, June 16, 2021 at 11:20:37 AM UTC-5 David Gifford wrote:

> I added this to my "documenting.tw" file:  
> https://giffmex.org/gifts/documenting.tw.html#Filter%3A%20All%20tagging%20except%20those%20transcluded%20here
>
> On Wednesday, June 16, 2021 at 9:27:16 AM UTC-5 Si wrote:
>
>> Hi David,
>>
>> I've been planning to do something similar in my own wiki. I can't think 
>> of a way to do it with a single filter expression, but here is a very 
>> clunky approach:
>>
>> <$list filter="[tag] [tag{!!draft.of}]" 
>> variable=tagged-tiddler>
>> <$vars search-term={{{ [addprefix[{{]addsuffix[}}]] 
>> }}}>
>> <$list filter="[!search]">
>> <$link to=<>><>
>> 
>> 
>> 
>> 
>>
>> This should work in both edit and view mode, but you can easily simplify 
>> the first filter expression if you only need it to work in edit mode.
>>
>> There's probably a more elegant approach out there but this seems to work.
>>
>> On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:
>>
>>> Hi all
>>>
>>> I need another list filter:
>>>
>>> ...minus any tiddlers transcluded in the" current tiddler.
>>>
>>> Use case: I plan to use transclusions to build long "article" tiddlers, 
>>> with section headers and specific ordering of the transclusions. But as I 
>>> take notes, I want to tag note tiddlers with the article(s) they will be 
>>> transcluded in. 
>>>
>>> So in edit template, I want a list at the bottom of the tiddlers tagged 
>>> to the current tiddler [all[current]tagging[]], minus the tiddlers I have 
>>> already transcluded in the current tiddler. That way I can see which 
>>> tiddlers still need transcluding.
>>>
>>> Thanks for any help with this. It doesn't look very straightforward. 
>>> There doesn't seem to be a way to do -[all[current]transcluding[]] yet. 
>>> Maybe in 5.1.25?
>>>
>>> Blessings,
>>>
>>

-- 
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/8ca8ae51-49c6-4674-8a2b-0cd11e6bee0fn%40googlegroups.com.

Re: [tw5] Re: .tid file format

[Soren Bjornstad]

Aha, you've accidentally solved the mystery of why I have two tiddlers 
stored as JSON in my Zettelkasten wiki! They have newlines in fields. 
Thanks. :-)

On Wednesday, June 16, 2021 at 9:32:37 AM UTC-5 jeremy...@gmail.com wrote:

> Just to add that the .tid file format really is as simple as it looks, 
> with the constraints implied by that simplicity:
>
> * Field names cannot contain colons
> * Field values (apart from the "text" field) cannot contain newlines
>
> The core works around these limitations by saving tiddlers in JSON format 
> if they don't meet the criteria for .tid files.
>
> Best wishes
>
> Jeremy
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 16 Jun 2021, at 13:31, Soren Bjornstad  wrote:
>
> To be clear since it sounds like you might be trying to create them from 
> scratch without any reference to look off, you probably want to include at 
> least the fields *created*, *modified*, *tags*, *title*, and *type. *Type 
> is *text/vnd.tiddlywiki* for standard wikitext, and created/modified are 
> MMDDHHMMSSXXX timestamps (normalized to UTC).
>
> On Wednesday, June 16, 2021 at 7:29:11 AM UTC-5 Soren Bjornstad wrote:
>
>> David,
>>
>> I parse them all the time and there's not really much to it – most of the 
>> fields are at the top separated from their values by a colon and a space, 
>> and then after the first blank line is the *text* field.
>>
>> I imagine this may change slightly in the upcoming version 5.2 since 
>> field names are going to be allowed to contain more characters than they 
>> currently do (not sure what would happen if you put a colon in a field name 
>> in 5.2, for instance).
>>
>> On Wednesday, June 16, 2021 at 3:12:56 AM UTC-5 David Shaw wrote:
>>
>>> Is the format of a .tid file available anywhere?
>>>
>>> I ask because I am using Python to pull information from the Web, which 
>>> I then want to get into a Tiddlywiki and, for reasons that are far too 
>>> long, complicated and boring to go into here, I am having to do all this on 
>>> an Android device and can't get JSON import to work in Tiddloid. 
>>>
>>> Many thanks,
>>>
>>> David Shaw
>>>
>> -- 
> 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/c0a69b7a-3d77-479e-af4a-98722feb3d85n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywiki/c0a69b7a-3d77-479e-af4a-98722feb3d85n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>

-- 
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/7197e295-7719-41f6-8f57-2accfa23f190n%40googlegroups.com.

[tw5] Re: .tid file format

[Soren Bjornstad]

To be clear since it sounds like you might be trying to create them from 
scratch without any reference to look off, you probably want to include at 
least the fields *created*, *modified*, *tags*, *title*, and *type. *Type 
is *text/vnd.tiddlywiki* for standard wikitext, and created/modified are 
MMDDHHMMSSXXX timestamps (normalized to UTC).

On Wednesday, June 16, 2021 at 7:29:11 AM UTC-5 Soren Bjornstad wrote:

> David,
>
> I parse them all the time and there's not really much to it – most of the 
> fields are at the top separated from their values by a colon and a space, 
> and then after the first blank line is the *text* field.
>
> I imagine this may change slightly in the upcoming version 5.2 since field 
> names are going to be allowed to contain more characters than they 
> currently do (not sure what would happen if you put a colon in a field name 
> in 5.2, for instance).
>
> On Wednesday, June 16, 2021 at 3:12:56 AM UTC-5 David Shaw wrote:
>
>> Is the format of a .tid file available anywhere?
>>
>> I ask because I am using Python to pull information from the Web, which I 
>> then want to get into a Tiddlywiki and, for reasons that are far too long, 
>> complicated and boring to go into here, I am having to do all this on an 
>> Android device and can't get JSON import to work in Tiddloid. 
>>
>> Many thanks,
>>
>> David Shaw
>>
>

-- 
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/c0a69b7a-3d77-479e-af4a-98722feb3d85n%40googlegroups.com.

[tw5] Re: .tid file format

[Soren Bjornstad]

David,

I parse them all the time and there's not really much to it – most of the 
fields are at the top separated from their values by a colon and a space, 
and then after the first blank line is the *text* field.

I imagine this may change slightly in the upcoming version 5.2 since field 
names are going to be allowed to contain more characters than they 
currently do (not sure what would happen if you put a colon in a field name 
in 5.2, for instance).

On Wednesday, June 16, 2021 at 3:12:56 AM UTC-5 David Shaw wrote:

> Is the format of a .tid file available anywhere?
>
> I ask because I am using Python to pull information from the Web, which I 
> then want to get into a Tiddlywiki and, for reasons that are far too long, 
> complicated and boring to go into here, I am having to do all this on an 
> Android device and can't get JSON import to work in Tiddloid. 
>
> Many thanks,
>
> David Shaw
>

-- 
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/d8b79596-679a-4c4d-a8c4-41da0e26069dn%40googlegroups.com.

[tw5] Re: empty.html should start with a "Centered story, fixed sidebar" setting.

[Soren Bjornstad]

Absolute positioning strikes me as likely to confuse TiddlyWiki's layout, 
but I'm mostly a “guess and check” CSS user so I can't explain why, except 
that I've tried to do it in the past and it hasn't worked very well. But 
your situation may be different.

Also, wouldn't that be applying the same absolute positioning to *every* 
tiddler 
in the story river, which could include both the details and the 
entry/chapter? You might be able to use data-tags 
<https://tiddlywiki.com/#Custom%20styles%20by%20data-tags> to apply the 
special positioning/sizing only to one of the items.

On Tuesday, June 15, 2021 at 11:01:32 PM UTC-5 iamdar...@gmail.com wrote:

> @Soren,
>
> I have been trying to make a two column view for my World Building 
> project. The idea was that someone could be editing a Tiddler (entry) or 
> writing a chapter (again a Tiddler) and then have the world details above 
> in an isolated row that scrolled. Kind of like Stroll but instead of two 
> columns it would have two rows to switch the Tiddlers between. 
>
> However, your CSS gave me an idea and my question is, as I sit here 
> shaking and jittering like I have wy too much sugar, can you tell 
> me if my changes to the edit-frame css breaks anything in your mind? 
>
> I think I figured out how I can, and now want to, have the edit and 
> viewing breakdown. Again, I just want to make sure I'm not butchering 
> something else without realizing it. Thank you so much if you can and for 
> your CSS/idea!
>
> div.tc-tiddler-frame { max-width: 60em; margin-left: auto; margin-right: 
> auto; } 
> div.tc-tiddler-edit-frame { max-width: 90em; margin-left: auto; 
> margin-right: auto; max-height: 500px; overflow:auto; position: fixed; 
> bottom: 0; z-index:2; } 
> div.tc-tiddler-body { max-width: 50em; margin: auto; }  
> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor { width: 69%; } 
> div.tc-tiddler-preview-preview { width: 29%; }
>
> On Tuesday, June 15, 2021 at 10:44:00 PM UTC-4 Soren Bjornstad wrote:
>
>> While we're discussing story river layouts, I've been playing with the 
>> following odd-looking but surprisingly functional layout for a couple of 
>> days, in an attempt to make optimal use of the 24" monitors where I do most 
>> of my editing:
>>
>> [image: widening.png]
>>
>> As you can see, the story river is centered, but tiddlers get wider when 
>> you go into edit mode, so there's additional space for a side-by-side 
>> preview when editing but lines don't get too long to comfortably read when 
>> viewing. I also changed the division between the editor and the preview to 
>> 70/30 instead of 50/50, which usually gets the paragraphs on the left and 
>> right to almost exactly line up, rather than the wikitext rapidly getting 
>> longer than the preview (a smaller difference like 60/40 might be a better 
>> compromise if you edit with a lot of images or transclusions).
>>
>> CSS on top of the default theme and fluid-fixed layout:
>>
>> div.tc-tiddler-frame { max-width: 60em; margin-left: auto; margin-right: 
>> auto; }
>> div.tc-tiddler-edit-frame { max-width: 90em; margin-left: auto; 
>> margin-right: auto; }
>> div.tc-tiddler-body { max-width: 50em; margin: auto; }
>> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor { width: 69%; }
>> div.tc-tiddler-preview-preview { width: 29%; }
>>
>> Still in alpha stages, and probably much too odd to implement in core, 
>> but maybe interesting to somebody. :-)
>>
>> On Tuesday, June 15, 2021 at 4:39:02 PM UTC-5 f.brunsb...@gmail.com 
>> wrote:
>>
>>> Hi Mario, we just had the pleasure, but others are welcome to read my 
>>> opinion as well.
>>>
>>> Not a bad idea as far as it goes. Better than the original alignment of 
>>> the empty.html.
>>> But I would like to see another variant "All centered". Of course, both 
>>> side by side but shown together in the center. 
>>> [image: Eg_centered.png]
>>>
>>> PMario schrieb am Dienstag, 15. Juni 2021 um 21:28:21 UTC+2:
>>>
>>>>
>>>> Hi folks, 
>>>> According to the feedback from empty.html should start with 
>>>> "fluid-fixed" layout 
>>>> <https://groups.google.com/g/tiddlywiki/c/m0XycQ8DrI0/m/2A3qssqDAQAJ> 
>>>> I did create a new setting in the ControlPanel : Appearance : Theeme Tweaks
>>>>
>>>>  - Centered story, fixed sidebar
>>>>
>>>> If the option is set, the metrics elements, that can't be used are 
>>>> "grayd out". 
>>>>
>>>> The PR is at: https://github.com/Jermolene/TiddlyWiki5/pull/5800
>>>>
>>>> [image: centered-fixed-01.gif]
>>>>
>>>> Feedback is welcome.
>>>> -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/e136e8df-a009-4cd8-95ac-5dc278203defn%40googlegroups.com.

[tw5] Re: logical AND for filter runs

[Soren Bjornstad]

I think you may be looking for :intersection?

   - named prefix :intersection replaces all filter output so far with 
   titles that are present in the output of this run, as well as the output 
   from previous runs. Forms the input for the next run.  NEW IN: 5.1.23

See the examples for filter runs 
 for a full 
explanation of the difference.

On Wednesday, June 16, 2021 at 3:36:47 AM UTC-5 jn.pierr...@gmail.com wrote:

> I've been into toying with run prefixes for my filters, to see what I can 
> now do with them.
>
> I've been able to have an equivalent of "if not A then B" but I've not 
> been able to get "if A then B". the + or :and prefix is not a logical AND 
> at all but just a way to replace all currents stuff in the pipe with new 
> contents.
>
> Part of the problem is I can't produce NOT A. I mean, see this example:
>
> {{{
> cobalt great gaz :filter[split[]match[r]] 
> +[!is[blank]then[]else["great" void]]
> ~Expected
> }}}
>
> {{{
> cobalt fox gaz :filter[split[]match[r]] 
> +[!is[blank]then[]else["fox" void]]
> ~Unexpected
> }}}
>
> The only output is "fox" void. I expected that the first filter output be 
> Expected.
>
> As a kind of check with
>
> {{{
> cobalt great gaz :filter[split[]match[r]] 
> ~Expected
> }}}
>
> {{{
> cobalt fox gaz :filter[split[]match[r]] 
> ~Unexpected
> }}}
>
> the output is
> great
> Unexpected
> which is totally what we thought we should have.
>
> The same also happens with
>
> cobalt great gaz :filter[split[]match[r]]
> +[!is[blank]]
> ~Expected
> }}}
>
> {{{
> cobalt fox gaz :filter[split[]match[r]]
> +[!is[blank]]
> ~Unexpected
> }}}
>
> Again, that's OK. Maybe that's because [] is not a blank input? But 
>
>
> {{{ [[]] +[!is[blank]then[Full]else[Empty]] }}}
>
> does indeed output Empty as expected so I'm really confused now...
>
> BTW, in real life, in "if A then B" my B is not a constant, in which case 
> I would have used [A]!is[blank]then[B] but a complex run. I know I can have 
> a function or variable as my B to get around the difficulty, but that is 
> not what I want to do here.
>
> -- 
> Jean-Pierre
>
>
>

-- 
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/438fc0c3-4fd7-4f15-8c5d-03440ce66fffn%40googlegroups.com.

[tw5] Re: Force re-save of tiddlers whose file system path has changed

[Soren Bjornstad]

On Tuesday, June 15, 2021 at 4:21:23 AM UTC-5 PMario wrote:

> Hi Soren, 
> IMO your code is a bit "dangerous". If copy pasted, it will modify the 
> modified field, if users don't read everything carefully.
>

Fair enough, but nobody should ever try something like this without a 
backup anyway!

-- 
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/128a0337-0d97-4b13-bf97-491aedfb24c5n%40googlegroups.com.

[tw5] Re: Force re-save of tiddlers whose file system path has changed

[Soren Bjornstad]

Thanks Joshua, this worked great!

For anyone else needing this, I switched off timestamps, then created a 
tiddler containing the following button:

<$button>
Do The Thing
<$list filter="[is[tiddler]]">
<$action-deletefield afieldthatdoesntexist="" />



Clicked the button, then turned timestamps back on, and all the changes 
showed up in Git as expected.

(For whatever reason the $action-deletefield form with 
$field="afieldthatdoesntexist" did not do anything when I clicked the 
button. Not sure what was up with that.)

On Monday, June 14, 2021 at 6:42:04 PM UTC-5 joshua@gmail.com wrote:

> Hi Soren,
>
> I wrote most of the recent Node file-handling logic.
>
> I found the easiest way to "touch" a batch of tiddlers in order to force a 
> re-save is to $action-deletefield a NON-EXISTANT field from within a $list 
> (triggered by a $button).
>
> This forces the tw core to re-save a tiddler over the existing one (even 
> tho its the same) & this triggers the Sync mechanism.
>
> (You can also use this to "unpack" shadow tiddlers from within plugins, 
> forcing a "normal" tiddler that is the same as the shadow-copy.)
>
> Best,
> Joshua F
>
> On Monday, June 14, 2021 at 3:53:42 PM UTC-7 Soren Bjornstad wrote:
>
>> Some time ago I tweaked the $:/config/FileSystemPaths in one of my wikis 
>> to place tiddlers into some different folders based on tags, as described 
>> here <https://tiddlywiki.com/#Customising%20Tiddler%20File%20Naming>. 
>> However, I haven't modified all of these tiddlers yet, so months later some 
>> of them are still in the default location, making the division not all that 
>> helpful since it's difficult to know which location each item is in.
>>
>> Is there a way I can get TiddlyWiki to re-save all my tiddlers into the 
>> location they would be placed today, in bulk (ideally without updating 
>> their timestamps)? I could rig up a shell script, but that feels like it 
>> could be a lot of work.
>>
>

-- 
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/ed62406c-5412-4ec3-b05a-878d76a236c2n%40googlegroups.com.

[tw5] Force re-save of tiddlers whose file system path has changed

[Soren Bjornstad]

Some time ago I tweaked the $:/config/FileSystemPaths in one of my wikis to 
place tiddlers into some different folders based on tags, as described here 
. However, I 
haven't modified all of these tiddlers yet, so months later some of them 
are still in the default location, making the division not all that helpful 
since it's difficult to know which location each item is in.

Is there a way I can get TiddlyWiki to re-save all my tiddlers into the 
location they would be placed today, in bulk (ideally without updating 
their timestamps)? I could rig up a shell script, but that feels like it 
could be a lot of work.

-- 
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/18cf989b-6d22-41f6-b97b-2e5166a896a3n%40googlegroups.com.

[tw5] Re: Building a book/blog webpage -- is TW5 right for it?

[Soren Bjornstad]

I wrote a TiddlyWiki book in TiddlyWiki, and people have liked the design: 
https://groktiddlywiki.com

I think this design badly fails your "should not present a TiddlyWikish 
face" criterion though.

On Thursday, June 10, 2021 at 8:17:41 PM UTC-5 Télumire wrote:

> I'm not a dev by any means so I probably can't help you much, but I think 
> these links may help you :
>
> In this thread, people have successfully managed to use tiddlywiki for 
> book publishing, with great results : 
> https://groups.google.com/g/tiddlywiki/c/_VLufc4Svp8/m/jALzYZ09BAAJ
> You can see a sample here : 
> https://tw5.immateriel.fr/wiki/7switch/book/aHR0cHM6Ly9jYXRhbG9ndWUuaW1tYXRlcmllbC5mci9yZXNvdXJjZXMvYTYvMTIvMDcyMDhkOTdhZjdmYWZkMjkyNzRhN2MwNDU1YS5lcHVi
> or make your own book from an epub : https://tw5.immateriel.fr/wiki
>
> It's possible to use TW as a blog platform : 
> https://tiddlywiki.com/static/Blog%2520Edition.html
>
> So it seems that it's possible. I'm guessing it will not be simple tho.. 
> maybe wordpress would be easier.
> Le jeudi 10 juin 2021 à 22:28:54 UTC+2, Kosmaton a écrit :
>
>> Hello Tiddly people,
>>  
>> I'm meaning to create a new website, and I'd like to ask your opinion 
>> whether TiddlyWiki is the right tool (or one of the tools) for it.
>>  
>> I used to have a pre-TW5 site on TiddlySpace back in the day. I'm 
>> semi-programming-and-webdesign-literate, in an ad hoc and rusty way. No 
>> experience with databases unfortunately, which may be relevant.
>>  
>> The website I have in mind would be a combination of a non-fiction book 
>> (already written, but expandable/changeable), and an associated blog. The 
>> book is organized as a big tree of numbered paragraphs/sections: 1, 1.1, 
>> 1.1.1, 1.2, 2, 2.1 etc. These sections frequently refer to one another; 
>> it's a hypertext in itself.
>>  
>> * The site would mainly need to have:
>>  
>> 1) a page that displays the book, with a Table of Contents.
>>   - The TOC should be hideable as a whole.
>>   - The branches of the TOC should be collapsible, i.e. click on 1 to 
>> show 1.1 and 1.2, click again to hide them, etc.
>>   - It may be excessive to load all the text of the book (all the 
>> sections) into the viewport (some 70,000 words). But it would be nice if 
>> the reader saw a bit more than just the section they're currently reading. 
>> Basically a pdf-reader-like experience would be good.
>>   - optional: Sections of the book may get revisions, and the visitor 
>> should be able to see the revisions. (This would probably get a lot more 
>> complicated if I want to allow for reordering, deletion and creation of 
>> sections...)
>>   - The book currently exists as a LibreOffice Writer .odt file, with 
>> sections actually organized as headings. Ideally I'd like to automate the 
>> process of getting them into the TiddlyWiki.
>>  
>> 2) a blog/news page
>>   - Blog posts are expected to regularly contain links to book sections, 
>> or entire transcluded sections.
>>   - Posts must be able to acommodate audio files; a regular HTML > controls> seems sufficient.
>>  
>> 3) a Home page that could e.g. display
>>   - the most recent blog post (truncated if necessary)
>>   - a sort of carousel widget with single sections from the book, with 
>> arrows left and right to flip through them. These sections could be either 
>> randomly taken from the whole book, or from a hand-picked subset of 
>> sections (which I should be able to adjust).
>>  
>> * The thing really ought to be 'responsive', i.e. look fine on small 
>> screens too. This might not be obvious for something like the TOC.
>>  
>> * Towards the visitor it should not present a very TiddlyWikish face. I'm 
>> keen to acknowledge/praise/recommend TW in the About page; but the casual 
>> visitor should not focus on the underlying tech.
>>  
>> * I don't intend to have a server of my own. The free webhost I've 
>> happily used before allows for up to 2 databases, with a choice between 
>> "5.7-MySQL . 10.5-MariaDB . 13.2-PgSQL".
>>  
>> So:
>>  
>> Does this sound feasible with TW5 as a base? (Or would you suggest some 
>> other framework? If it's /challenging/ with TW, but /easy/ with XYZ, 
>> I'd like to hear about XYZ too! :)
>>  
>> How would I set this up as far as server / databases etc. go?
>>  
>> If I go ahead with this, there's bound to be more detailed questions 
>> regarding the functionalities mentioned above; but if you already see any 
>> immediate solutions (plugins, say) please shout.
>>  
>> Apologies for the length of this post. I don't expect anyone to figure 
>> all this out for me, but any thoughts are very welcome. Many thanks in 
>> advance!
>>  
>> K.
>>
>

-- 
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 

[tw5] Re: Conversation About Wiki Data Presentation and Recollection

[Soren Bjornstad]

In my Zettelkasten  I use search, 
in combination with concise and memorable titles, if I already know exactly 
what I'm looking for, and occasionally to find references to a particular 
phrase or idea that I'm considering turning into a tiddler of its own. 
Otherwise, I rely mostly on *links* – search for or find in a tag list 
something that is vaguely related to the kind of thing I'm looking for and 
explore the links from there. This definitely works better with a good list 
of outbound links and backlinks like I have at the bottom of every tiddler, 
but it could be made to work even in stock TiddlyWiki.

As for others visiting the site, there are a few views (e.g., topical tags, 
bibliographies on specific topics, list of recently read books) that might 
give people a head start, but most people who have commented on it to me 
also like the links mechanism for exploring. That likely works particularly 
well with this use case because people tend not to be trying to find 
something in particular.


On Wednesday, June 9, 2021 at 7:40:08 PM UTC-5 iamdar...@gmail.com wrote:

> First I apologize if this is a taboo topic. I don't meant for it to be 
> flame war between respective camps if it is. I just tend to view/understand 
> things differently when it comes to paradigms or techniques. 
>
> I have seen many posts about workflows and data collection but this post 
> is about data presentation and recollection. 
>
> I don't know if my constant internal debate is normal for others as well, 
> or if I'm trying to bridge too many different concepts that are 
> fundamentally different, or something else but it personally drives me 
> crazy. 
>
> From what I can tell there are at least three main methods of presenting 
> wiki data:
>
> 1. Search feature that you enter keyword(s) into and review the results. 
> 2. Some kind of table of contents or index that shows all of the content, 
> most likely grouped by some type of categorization. 
> 3. Some kind of splash page that is similar in concept to #2 but acts more 
> as a guide with manual links embedded within a naturally written page to 
> almost create an interface. 
>
> In truth #3 might be just me creating some sort of perversion of #2 from 
> my experience with web design and game/anime wikia sites. 
>
> Also, my concerns about data "recollection" might be an example of me 
> trying to bridge wiki-ing and note taking. Perhaps the concept of 
> recollection isn't as important in a wiki because you are using it to 
> collect specific, related, and organized topics and as such it will display 
> accordingly? I guess like the details of a city or character under the 
> appropriate section (wiki) vs a random though entered on a random day about 
> a commercial you just saw (notes). I know you can use a wiki for note 
> taking and a note taking as a way to wiki-ing but are the underlying 
> processes easily interchangeable? Or do they cause a conflict?
>
> *tl;dr*: 
>
> How do you present your wiki data to yourself/others? Do you use the 
> search feature most of the time? Or do you use an index/table of contents 
> approach? Or something else entirely or in between the two?
>
> Thanks!
>

-- 
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/3cd16a63-f4ab-4ad6-91bf-48174f4c31a2n%40googlegroups.com.

[tw5] Re: TiddlyWiki strategies for discussing fiction?

[Soren Bjornstad]

iamdar, I had not seen that yet and it's got some cool workflows in it, so 
thanks for pointing it out, but it's not exactly what I was asking about…I 
am looking more for thoughts on the structure of tiddlers, metadata, and 
navigation options that I'll have when I'm *done* writing and relating 
notes, rather than an effective way to go about doing the writing.

Mat,

> You mention that Lolita gave you a lot of ideas, so how are those ideas 
different from what you get out of non-fiction?

The ideas may be different in that there are more layers of metaphor 
involved? Like, a lot of the ideas are not explicitly stated (and some of 
my tiddlers might explicitly state transformative readings, while others 
might not).

Mostly, though, my sense is that a different kind of organization may be 
required to make optimal sense of them. In non-fiction I generally do not 
care where the ideas came from once I've read the book, unless perhaps I am 
later trying to cite them in something I write, so a quick reference to the 
source is sufficient, and all the interlinking and classification happens 
between idea tiddlers. With fiction the context and the relationships with 
other things that happen in the source is much more important to 
understanding...a whole novel can't really be deconstructed into pieces in 
the same way that a textbook or even a thesis-driven book can. So I feel 
like some kind of cross-referencing and mechanism for tying things back to 
the text would be valuable. I do not know how exactly that would work or 
what it would do, which is why I'm curious if anyone else has developed 
something. Not afraid of trying some things myself either. :-)

> Do you have a goal with your reading? Maybe to write your own book, or to 
extract human wisdom, or to just remember as much of a good book as 
possible, or to write literary critique, or... etc,etc...

Yes? I think that's part of the problem, haha. But it's also why I use 
TiddlyWiki instead of something else, because it is capable of supporting 
these kind of mixed uses in a way that few other tools are. My immediate 
goal in writing notes in TiddlyWiki is to increase my understanding of what 
I just read, but I hope that this understanding will stick around and could 
be taken in any of those directions in the future if it later makes sense.


On Wednesday, June 9, 2021 at 5:10:20 PM UTC-5 Mat wrote:

> @Soren - what is it you want out of it? You mention that Lolita gave you a 
> lot of ideas, so how are those ideas different from what you get out of 
> non-fiction? Do you have a goal with your reading? Maybe to write your own 
> book, or to extract human wisdom, or to just remember as much of a good 
> book as possible, or to write literary critique, or... etc,etc...
>
> <:-)
>

-- 
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/97be42a6-73c0-4271-8cdd-4b8b8a28719bn%40googlegroups.com.

[tw5] TiddlyWiki strategies for discussing fiction?

[Soren Bjornstad]

I think I've mostly found an approach for tiddlifying notes and ideas I get 
out of nonfiction (basic approach: add short summary to a tiddler on the 
book or article, then use backlinks and occasionally forward links to 
connect ideas related to it), but I'm struggling with figuring out what 
works for literature, maybe because I just haven't done as much of it yet.

See this recent writeup 
, for 
instance, which is an awkward mix of ideas dumped into the book's tiddler 
and ideas placed in separate tiddlers. I could just write a linear 
discussion of the story, or a bunch of unrelated “paper”-like discussions, 
but those approaches feel like I'm not taking advantage of what TiddlyWiki 
has to offer.

I've just finished *Lolita* and have approximately 23,000 ideas rolling 
around in my head that I want to put somewhere, so am feeling like this is 
as good a time as any to start experimenting. Before I do, has anyone else 
used TiddlyWiki this way who might have some pointers for me so I don't 
start off in the entirely wrong direction?

Thanks!

-- 
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/2d84d0ea-e17f-47f6-946e-232414e4b5b5n%40googlegroups.com.

Re: [tw5] A tour through my Zettelkasten

[Soren Bjornstad]

#1 is because for some reason I don't understand, initing a new TiddlyWiki 
doesn't add those plugins. They basically implement the saver for the 
Node.js wiki.

#2 and #3 I believe you could fix by doing "npm init" in the directory one 
up from TiddlyWiki. For #2 you could also totally just remove the 
check...the purpose is just to make sure the script is being run from the 
right folder so that all the relative paths work correctly, and the 
*package.json* file being in that directory was a convenient way to check.

On Tuesday, June 8, 2021 at 7:16:13 PM UTC-5 Tully Hansen wrote:

> Hi all, and thanks Soren for so generously sharing your script and 
> workflow here! I've got it mostly up and running on my Mac (macOS 10.14.6, 
> Homebrew something-or-other), but not without running into a few issues - 
> thought I'd note theme here for posterity (and anyone else who tries to get 
> this up and running):
>
>
>1. After decompiling the flat file to Node version (tiddlywiki --load 
>path/to/single/file.html --savewikifolder path/to/output/folder), I 
>was getting an error message when starting the TiddlyWiki server locally 
>with tiddlywiki --listen that read Warning: Plugins required for 
>client-server operation ("tiddlywiki/filesystem" and 
>"tiddlywiki/tiddlyweb") are missing from tiddlywiki.info file. Adding 
>these lines to the plugins listed in *tiddlywiki.info 
><http://tiddlywiki.info> *seemed to do the trick, though I've no idea 
>what that did/does.
>2. After that (or perhaps even before?) I was getting an error when 
>running scripts/publish.sh --push saying cd to project root failed. 
>Please check script. The script seemed to be looking for a 
>*package.json* file in root that I… didn't have? I know enough only to 
>know/Google that this is some Node thing, so I created this file in the 
> *My 
>Zettelkasten* folder containing a pair of empty curly braces (per 
>https://nodejs.dev/learn/the-package-json-guide). Seemed to work, and 
>seems to fail if I get rid of it, so *package.json* lives there now 
>permanently.
>3. The next exciting error was scripts/publish.sh: line 27: 
>/Users/tully/Dropbox (Personal)/tid/My 
>Zettelkasten/node_modules/.bin/tiddlywiki: No such file or directory when 
>running scripts/publish.sh --push. Looked like Node looking for 
>something in the wrong place, Googled 
><https://docs.npmjs.com/cli/v7/commands/npm-bin>, poked at the script 
>some and ended up adding the --global flag to the three npm bins at 
>lines 27, 30, and 34. (Find npm bin and replace npm bin --global.)
>4. Finally, I was getting some errors auth'ing git/Github, which I was 
>being prompted to do on the command line – this was because of having 2FA 
>enabled, which meant creating a personal access token 
>
> <https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token>
>  
>rather than using my password. I just gave it every scope, probably 
>overkill…
>
> Hope this helps any future semitechnical Sorentiddlers get set up! And if 
> anyone wants to explain what I've done (or done wrong) above, I'm all ears. 
> Thanks again!
>
> On Thursday, 13 May 2021 at 15:05:01 UTC+10 Mohammad wrote:
>
>> Thank you for clarification! I myself use ideas/tasks and then extra tags 
>> like reading!
>> But your suggested categories make things more clear!
>> I think it is very important to get used to this new methodology and 
>> continuously do that!
>>
>>
>> On Thu, May 13, 2021 at 4:39 AM Soren Bjornstad  
>> wrote:
>>
>>> I walked through them in the video, but here's a quick summary of what 
>>> they're for:
>>>
>>>- Stubs – ideas that I haven't written about yet, usually with just 
>>>a title, or a quote, or a sentence or two describing what it will be 
>>> (items 
>>>tagged Stub)
>>>- Missing – same as in stock TW
>>>- Needing attention – some unspecified work needs to be done on the 
>>>tiddler, often I don't agree with the contents anymore, or it needs 
>>>reorganization
>>>- Needing excision – the tiddler turned into a bunch of confused 
>>>ideas put together and I need to think about what those are and split it 
>>> up 
>>>(items tagged NeedsExcision)
>>>- To-do items – anywhere I link to TODO, the tiddler is added to the 
>>>list, along with  the phrase after the link, so I get a nice list of 
>>>specific things that need to be fixed/added to
>>

Re: [tw5] Re: [Comment] My Ongoing Irritations with Google Groups

[Soren Bjornstad]

Tones, I think you are confusing Discord and Discourse as happened earlier 
up the thread 
. They 
are totally unrelated and Discourse is for long-form writing and discussions 
, not chat.

On Monday, June 7, 2021 at 6:32:51 PM UTC-5 TW Tones wrote:

> ha Ha "bad sMellers," Totally agree, I am one of them, not to mention typos
>
> Seriously being able to edit the top post was a great way of summarising 
> the results that come out in the thread. A Simple standard to update the 
> top post when a question is answered, and the answer etc... would add great 
> value.
>
> On discourse, Its A chat not likely to have longer more serious content, 
> thus fragmented and harder to read. Has its place but in my mode not as a 
> replacement to Git hub.
>
> I still hole a light for Yammer, but I do not want to waste my time 
> explaining why if few people even try it. As a knowledge curator it would 
> be ideal. Many little groups and blogs can be created with the owners 
> extracting links and even build collaborative documents. Its only gap was 
> code blocks.
>
> Tones
>
>
> \
>
> On Monday, 7 June 2021 at 22:28:09 UTC+10 TiddlyTweeter wrote:
>
>>  saq.i...@gmail.com wrote:
>>
>>> Jeremy just so you are aware, the issues with posting via the web 
 interface go beyond just difficulty in making monospaced blocks. 

>>>
>> IF you ONLY use this GG though EMAIL then you WON'T know what got LOST 
>> recently ... (and other functions too ...)
>>
>>- CODE sections 
>>- Ability to PRIVATELY REPLY to posters
>>- Ability to RE-EDIT for spelling errors (a serious disaster for bad 
>>sMellers, of which there are many, including me)
>>
>> Just observations
>> TT
>>  
>>
>

-- 
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/4b1ae780-20dd-4433-8769-f25bce92fecen%40googlegroups.com.