date:20210721

Keep is popular.

I did look into getting tiddlywiki into a browser side bar in the past. I 
believed it worked in FireFox, but if not universal it is less interesting. 
That is the advantage of keep if you use a few of googles tools.

Tones

On Thursday, 22 July 2021 at 13:34:37 UTC+10 cj.v...@gmail.com wrote:

> I'm thinking it largely depends on the "ecosystem" one may be living in.
>
> Seeing as I've sold my soul to Google, Google Keep is my goto quick note 
> taker.
>
> I can access the full screen Google Keep, sidebar Google Keep when I'm in 
> the other Google Apps, and have the Google Keep Chrome Extension, to 
> quickly take notes while viewing some web page.
>
> So quick note taking for some heavy-duty note making in TiddlyWiki later.
>
> Mind you, I only ever use my Chromebook.  I never use my "smart" phone for 
> anything other than text and phone.
>
> Well, it is always a work-in-progress.
>
> On Wednesday, July 21, 2021 at 4:10:04 PM UTC-3 Si wrote:
>
>> This question was prompted by a discussion over in the thread on 
>> incremental note-taking 
>> .
>>
>> In my opinion a major weakness of TiddlyWiki is that it is not well 
>> suited to quickly capturing information on the fly with minimal friction.
>>
>> For this reason I use another app as an "inbox" for quick ideas and 
>> tasks, which I process later on. Currently I use Evernote, but I'm 
>> currently in the process of looking for something else (would love to hear 
>> suggestions for a good replacement). The number one contender at the moment 
>> is Joplin , but I'm tempted by the 
>> purity of using text/markdown files if I can find a good way to handle them 
>> on Android.
>>
>> Anyway I thought it would be interesting to prompt a discussion by asking 
>> the more general question: *What apps or tools do you use that you feel 
>> compliment TiddlyWiki well?* *What does your workflow look like?*
>>
>> It doesn't matter the domain - note-taking and productivity are the 
>> obvious categories, but please be free to share any tool you use in tandem 
>> with TiddlyWiki.
>>
>

-- 
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/c2b59147-58cd-4604-a373-7fd01027a7c5n%40googlegroups.com.

[tw5] Re: Getting relink to prevent obsolete permalinks

Charlie,

Yes that is a very good idea if we build a search based permalink button, 
if could even be called a 404 tiddler with search or "did you mean" list 
(to match the missing page in html error code). But when I think about it 
if one uses the share button will there ever be a not found tiddler? 
perhaps if it is deleted!

I have build what I call delete or edit inhibited tiddlers by replacing the 
edit and delete buttons with my own (hiding the existing ones behind more) 
that will not even display if the tiddler has a field edit-inhibit or 
delete-inhibit = yes

Shall I go ahead and make it the share button, or can we find "prior art"?

Tones

On Thursday, 22 July 2021 at 14:22:42 UTC+10 cj.v...@gmail.com wrote:

> Yeah, I only meant the building of that part you mentioned in the early 
> part of your post, i.e.:
> *a tiddler with the "permalink" field=1*
> *the url wiki-url.html#:[permalink[1]] *
>
> That was the only thing I had previously played with, and I thought you 
> meant to only build that, not all of the rest of the goodies you mention 
> further down your post.
>
> Aside: as a mesure to handle in case a tiddler gets deleted, the permalink 
> could look like wiki-url.html#:[permalink[1]else[not-found-alternative]] ; 
> something like that?
> On Thursday, July 22, 2021 at 1:11:30 AM UTC-3 TW Tones wrote:
>
>> Charlie,
>>
>> Yes, very similar, It is less about that working example which 
>> illustrates why we need not put much effort to obtain what is being 
>> discussed, but I do go on to discuss related issues and opportunities, such 
>> as creating bookmarks, did your reference solution include a share button 
>> for this? It should be quite easy. I also describe how to hide the field 
>> and discuss Further developments but yes it is the same use of the search 
>> on the URL.
>>
>> I did not mention but it can be used instead of the permaview as well.
>>
>> Regards
>> Tones
>>
>>
>>
>> On Thursday, 22 July 2021 at 13:38:20 UTC+10 cj.v...@gmail.com wrote:
>>
>>> I've never used that link (to a specific post) feature.  That's a new 
>>> trick for me.  Thanks!
>>>
>>> https://groups.google.com/g/tiddlywiki/c/nEDB3zRBALY/m/z0BXBncwBAAJ
>>>
>>> Well, I didn't' spend any time making it pretty ...
>>>
>>> On Thursday, July 22, 2021 at 12:29:08 AM UTC-3 TW Tones wrote:
>>>
 Charlie,

 I am not sure. I can't find that specific reply in this thread. Can you 
 give me a link from the actual reply please?

 I expect its something similar but with a different scope.

 Thanks
 Tones

 On Thursday, 22 July 2021 at 13:12:58 UTC+10 cj.v...@gmail.com wrote:

> Silly question:  are you suggesting you are going to build what I 
> already built and mentioned a little earlier in this thread (Jul 20, 
> 2021, 
> 10:09:07 AM) ?
>
> On Wednesday, July 21, 2021 at 10:17:10 PM UTC-3 TW Tones wrote:
>
>> Springer et al,
>>
>> Forgive me for repeating myself, although a lot of interesting ideas, 
>> I believe these to be *non-problems.* 
>>
>> A simple solution is available here. an Example would be an alternate 
>> button to simple permalinks, I think someone else used a share icon. 
>> When 
>> clicking this on a given tiddler, it would assign a next number to a 
>> field 
>> in the tiddler (basically issuing a unique value field - not a UID or 
>> serial or GUID) then use this field/number to uniquely identify the 
>> tiddler 
>> shared, so it does not matter if it's title is renamed. Then generate a 
>> url 
>> that instead searches for any (but only one) tiddler with that field 
>> value.
>>
>> If *anyone asks* I will build this share button soon.
>>
>> That is if someone wants to publish a robust permalink for a tiddler 
>> who's title may change they use a built for purpose alternative to 
>> permalinks. Perhaps the existing name permalinks is misleading, perhaps 
>> they should be impermalinks.
>>
>> Here is a working example
>> a tiddler with the "permalink" field=1
>> the url wiki-url.html#:[permalink[1]] 
>> In the wiki Open target 
>> this can be dragged to bookmarks/favourites
>>
>> However I personally choose my tiddler names well enough when needed 
>> so they need not change in future, and if I am publishing a link 
>> somewhere 
>> it is to access specific content. the link has a purpose, and once 
>> someone 
>> has the link the purpose is fixed in time and should always honour its 
>> original share.
>>
>> A version of the above method where the link filter 
>> is [has[permalink]last[]] will always link to the largest permalink 
>> value, 
>> so one is sharing a link to the latest permalink tiddler or post.
>>
>> Another supportive trick is to hide the field from the editor with a 
>> tiddler of the form

Re: [tw5] I broke the json pre-release :|

Mario,

I am glad someone concurs. For me with my de facto standards and the new 
freedom, if a field name looks like a tiddler title it possibly is.

Do you think many ancient and / or unsupported plugins will break?,. if 
they use fields even extensively the issue will only be if they are used 
against new fieldname standards. And until now at least we tended to honour 
any values if not fieldnames.

I will be honest though few if any system tiddlers I create have spaces or 
quotes of any kind. even tags are usually single text strings, and I do 
think I will stick to this, as it simplifies code. but yes, use it when the 
exception makes sense.

I have not yet considered what we may achieve by having field names that 
can be wikified into something else, but again I personally intend to 
proceed with caution. Perhaps the documentation can give some advice to 
this effect, for example currently the fieldname restrictions help us when 
generating csv files and if field names (and values) contain spaces, or 
commas and quotes this may no longer be true. The documentation should 
continue to list the previous limited naming standards as well. 

I must say I also have de facto naming standards for titles even although 
they are quite flexible, in fact most that I code follow a simple and 
limited range. I like to leave the flexibility for when its needed. The one 
exception is when a title is also textual content like a sentence or 
paragraph.

Regards
Tones
On Thursday, 22 July 2021 at 13:56:18 UTC+10 PMario wrote:

> On Thursday, July 22, 2021 at 3:24:54 AM UTC+2 TW Tones wrote:
>  
>
>> However am I the only one who still intends to keep field names to a 
>> defacto naming standard such as i-am-afield no caps or spaces? so It is 
>> easy for me to tell field names apart from text and titles!
>>
>
> No -- you are not.
>  
>
>> Of course I look forward to naming fields using tiddler titles (and the 
>> value a relationship type etc..). and to contain special prefixes or 
>> suffixes such as "-link" or (link)  but as a rule I would like a little 
>> structure and naming rules. 
>>
>
> You wrote, you want to have tiddler titles as field names. So your 
> field-rules have to be the same or a superset of your title rules. I would 
> be surprised, if "no caps or spaces" is one of them. 
>  
>
>> This always helps retain a degree of simplicity when managing lots of 
>> complexity.
>>
>
> Oh it will be funny, to deal with all the support requests here in the 
> group, because some ancient and / or unsupported plugins will break. ... 
> I'm not even sure, what my own plugins will do with "spaces" in field 
> names. ...  I will have to check that. 
>
> 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/41eefacb-fc35-482a-9f3d-533fc3c370a3n%40googlegroups.com.

[tw5] Re: Getting relink to prevent obsolete permalinks

Yeah, I only meant the building of that part you mentioned in the early 
part of your post, i.e.:
*a tiddler with the "permalink" field=1*
*the url wiki-url.html#:[permalink[1]] *

That was the only thing I had previously played with, and I thought you 
meant to only build that, not all of the rest of the goodies you mention 
further down your post.

Aside: as a mesure to handle in case a tiddler gets deleted, the permalink 
could look like wiki-url.html#:[permalink[1]else[not-found-alternative]] ; 
something like that?
On Thursday, July 22, 2021 at 1:11:30 AM UTC-3 TW Tones wrote:

> Charlie,
>
> Yes, very similar, It is less about that working example which illustrates 
> why we need not put much effort to obtain what is being discussed, but I do 
> go on to discuss related issues and opportunities, such as creating 
> bookmarks, did your reference solution include a share button for this? It 
> should be quite easy. I also describe how to hide the field and 
> discuss Further developments but yes it is the same use of the search on 
> the URL.
>
> I did not mention but it can be used instead of the permaview as well.
>
> Regards
> Tones
>
>
>
> On Thursday, 22 July 2021 at 13:38:20 UTC+10 cj.v...@gmail.com wrote:
>
>> I've never used that link (to a specific post) feature.  That's a new 
>> trick for me.  Thanks!
>>
>> https://groups.google.com/g/tiddlywiki/c/nEDB3zRBALY/m/z0BXBncwBAAJ
>>
>> Well, I didn't' spend any time making it pretty ...
>>
>> On Thursday, July 22, 2021 at 12:29:08 AM UTC-3 TW Tones wrote:
>>
>>> Charlie,
>>>
>>> I am not sure. I can't find that specific reply in this thread. Can you 
>>> give me a link from the actual reply please?
>>>
>>> I expect its something similar but with a different scope.
>>>
>>> Thanks
>>> Tones
>>>
>>> On Thursday, 22 July 2021 at 13:12:58 UTC+10 cj.v...@gmail.com wrote:
>>>
 Silly question:  are you suggesting you are going to build what I 
 already built and mentioned a little earlier in this thread (Jul 20, 2021, 
 10:09:07 AM) ?

 On Wednesday, July 21, 2021 at 10:17:10 PM UTC-3 TW Tones wrote:

> Springer et al,
>
> Forgive me for repeating myself, although a lot of interesting ideas, 
> I believe these to be *non-problems.* 
>
> A simple solution is available here. an Example would be an alternate 
> button to simple permalinks, I think someone else used a share icon. When 
> clicking this on a given tiddler, it would assign a next number to a 
> field 
> in the tiddler (basically issuing a unique value field - not a UID or 
> serial or GUID) then use this field/number to uniquely identify the 
> tiddler 
> shared, so it does not matter if it's title is renamed. Then generate a 
> url 
> that instead searches for any (but only one) tiddler with that field 
> value.
>
> If *anyone asks* I will build this share button soon.
>
> That is if someone wants to publish a robust permalink for a tiddler 
> who's title may change they use a built for purpose alternative to 
> permalinks. Perhaps the existing name permalinks is misleading, perhaps 
> they should be impermalinks.
>
> Here is a working example
> a tiddler with the "permalink" field=1
> the url wiki-url.html#:[permalink[1]] 
> In the wiki Open target 
> this can be dragged to bookmarks/favourites
>
> However I personally choose my tiddler names well enough when needed 
> so they need not change in future, and if I am publishing a link 
> somewhere 
> it is to access specific content. the link has a purpose, and once 
> someone 
> has the link the purpose is fixed in time and should always honour its 
> original share.
>
> A version of the above method where the link filter 
> is [has[permalink]last[]] will always link to the largest permalink 
> value, 
> so one is sharing a link to the latest permalink tiddler or post.
>
> Another supportive trick is to hide the field from the editor with a 
> tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
> eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
> thus once set you have to go out of your way to alter the permalink 
> value, that is its more permanent.
>
> Further developments (optional reading)
>
>- Since the addition of the unused title operator, it is possible 
>(more to the point easier) to use this to generate a unique and 
> incremented 
>tiddler title and serial number. 
>- Rather than shadow tiddlers I am using this not only to generate 
>a tiddler Serial Number (TSN) but a "ghost tiddler" that follows any 
>tiddler and provides a way to save metadata for any tiddler or field 
> there 
>in (regardless of the title)
>- My only issues left are 
>   - Finding a way to generate/assign such TSN

[tw5] Re: Getting relink to prevent obsolete permalinks

Charlie,

Yes, very similar, It is less about that working example which illustrates 
why we need not put much effort to obtain what is being discussed, but I do 
go on to discuss related issues and opportunities, such as creating 
bookmarks, did your reference solution include a share button for this? It 
should be quite easy. I also describe how to hide the field and 
discuss Further developments but yes it is the same use of the search on 
the URL.

I did not mention but it can be used instead of the permaview as well.

Regards
Tones

On Thursday, 22 July 2021 at 13:38:20 UTC+10 cj.v...@gmail.com wrote:

> I've never used that link (to a specific post) feature.  That's a new 
> trick for me.  Thanks!
>
> https://groups.google.com/g/tiddlywiki/c/nEDB3zRBALY/m/z0BXBncwBAAJ
>
> Well, I didn't' spend any time making it pretty ...
>
> On Thursday, July 22, 2021 at 12:29:08 AM UTC-3 TW Tones wrote:
>
>> Charlie,
>>
>> I am not sure. I can't find that specific reply in this thread. Can you 
>> give me a link from the actual reply please?
>>
>> I expect its something similar but with a different scope.
>>
>> Thanks
>> Tones
>>
>> On Thursday, 22 July 2021 at 13:12:58 UTC+10 cj.v...@gmail.com wrote:
>>
>>> Silly question:  are you suggesting you are going to build what I 
>>> already built and mentioned a little earlier in this thread (Jul 20, 2021, 
>>> 10:09:07 AM) ?
>>>
>>> On Wednesday, July 21, 2021 at 10:17:10 PM UTC-3 TW Tones wrote:
>>>
 Springer et al,

 Forgive me for repeating myself, although a lot of interesting ideas, I 
 believe these to be *non-problems.* 

 A simple solution is available here. an Example would be an alternate 
 button to simple permalinks, I think someone else used a share icon. When 
 clicking this on a given tiddler, it would assign a next number to a field 
 in the tiddler (basically issuing a unique value field - not a UID or 
 serial or GUID) then use this field/number to uniquely identify the 
 tiddler 
 shared, so it does not matter if it's title is renamed. Then generate a 
 url 
 that instead searches for any (but only one) tiddler with that field value.

 If *anyone asks* I will build this share button soon.

 That is if someone wants to publish a robust permalink for a tiddler 
 who's title may change they use a built for purpose alternative to 
 permalinks. Perhaps the existing name permalinks is misleading, perhaps 
 they should be impermalinks.

 Here is a working example
 a tiddler with the "permalink" field=1
 the url wiki-url.html#:[permalink[1]] 
 In the wiki Open target 
 this can be dragged to bookmarks/favourites

 However I personally choose my tiddler names well enough when needed so 
 they need not change in future, and if I am publishing a link somewhere it 
 is to access specific content. the link has a purpose, and once someone 
 has 
 the link the purpose is fixed in time and should always honour its 
 original 
 share.

 A version of the above method where the link filter 
 is [has[permalink]last[]] will always link to the largest permalink value, 
 so one is sharing a link to the latest permalink tiddler or post.

 Another supportive trick is to hide the field from the editor with a 
 tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
 eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
 thus once set you have to go out of your way to alter the permalink 
 value, that is its more permanent.

 Further developments (optional reading)

- Since the addition of the unused title operator, it is possible 
(more to the point easier) to use this to generate a unique and 
 incremented 
tiddler title and serial number. 
- Rather than shadow tiddlers I am using this not only to generate 
a tiddler Serial Number (TSN) but a "ghost tiddler" that follows any 
tiddler and provides a way to save metadata for any tiddler or field 
 there 
in (regardless of the title)
- My only issues left are 
   - Finding a way to generate/assign such TSN and Ghost tiddler in 
   bulk.
   - rebuild a parallel solution - system serial number, to assign 
   a serial number to core and shadow tiddlers without touching them
- Actually I have found you need only assign serial number where to 
need them, say for these permalinks or compound tiddlers, that is with 
subtiddlers that use the serial number for the parent rather than the 
 title 
or a tag.

 Regards
 Tones

 On Thursday, 22 July 2021 at 06:50:01 UTC+10 springer wrote:

> About obsolete permalinks: 
>
> Surely a variant of the relink plugin could help maintain bread-crumbs 
> for obsolete links:
>
> Whenever

Re: [tw5] I broke the json pre-release :|

2021-07-21 Thread PMario

On Thursday, July 22, 2021 at 3:24:54 AM UTC+2 TW Tones wrote:

> However am I the only one who still intends to keep field names to a 
> defacto naming standard such as i-am-afield no caps or spaces? so It is 
> easy for me to tell field names apart from text and titles!
>

No -- you are not.

> Of course I look forward to naming fields using tiddler titles (and the 
> value a relationship type etc..). and to contain special prefixes or 
> suffixes such as "-link" or (link)  but as a rule I would like a little 
> structure and naming rules. 
>

You wrote, you want to have tiddler titles as field names. So your 
field-rules have to be the same or a superset of your title rules. I would 
be surprised, if "no caps or spaces" is one of them. 

> This always helps retain a degree of simplicity when managing lots of 
> complexity.
>

Oh it will be funny, to deal with all the support requests here in the 
group, because some ancient and / or unsupported plugins will break. ... 
I'm not even sure, what my own plugins will do with "spaces" in field 
names. ...  I will have to check that. 

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/8cfa30df-32f9-4e3b-8076-b6917c918efcn%40googlegroups.com.

[tw5] Re: Getting relink to prevent obsolete permalinks

I've never used that link (to a specific post) feature.  That's a new trick 
for me.  Thanks!

https://groups.google.com/g/tiddlywiki/c/nEDB3zRBALY/m/z0BXBncwBAAJ

Well, I didn't' spend any time making it pretty ...

On Thursday, July 22, 2021 at 12:29:08 AM UTC-3 TW Tones wrote:

> Charlie,
>
> I am not sure. I can't find that specific reply in this thread. Can you 
> give me a link from the actual reply please?
>
> I expect its something similar but with a different scope.
>
> Thanks
> Tones
>
> On Thursday, 22 July 2021 at 13:12:58 UTC+10 cj.v...@gmail.com wrote:
>
>> Silly question:  are you suggesting you are going to build what I already 
>> built and mentioned a little earlier in this thread (Jul 20, 2021, 10:09:07 
>> AM) ?
>>
>> On Wednesday, July 21, 2021 at 10:17:10 PM UTC-3 TW Tones wrote:
>>
>>> Springer et al,
>>>
>>> Forgive me for repeating myself, although a lot of interesting ideas, I 
>>> believe these to be *non-problems.* 
>>>
>>> A simple solution is available here. an Example would be an alternate 
>>> button to simple permalinks, I think someone else used a share icon. When 
>>> clicking this on a given tiddler, it would assign a next number to a field 
>>> in the tiddler (basically issuing a unique value field - not a UID or 
>>> serial or GUID) then use this field/number to uniquely identify the tiddler 
>>> shared, so it does not matter if it's title is renamed. Then generate a url 
>>> that instead searches for any (but only one) tiddler with that field value.
>>>
>>> If *anyone asks* I will build this share button soon.
>>>
>>> That is if someone wants to publish a robust permalink for a tiddler 
>>> who's title may change they use a built for purpose alternative to 
>>> permalinks. Perhaps the existing name permalinks is misleading, perhaps 
>>> they should be impermalinks.
>>>
>>> Here is a working example
>>> a tiddler with the "permalink" field=1
>>> the url wiki-url.html#:[permalink[1]] 
>>> In the wiki Open target this 
>>> can be dragged to bookmarks/favourites
>>>
>>> However I personally choose my tiddler names well enough when needed so 
>>> they need not change in future, and if I am publishing a link somewhere it 
>>> is to access specific content. the link has a purpose, and once someone has 
>>> the link the purpose is fixed in time and should always honour its original 
>>> share.
>>>
>>> A version of the above method where the link filter 
>>> is [has[permalink]last[]] will always link to the largest permalink value, 
>>> so one is sharing a link to the latest permalink tiddler or post.
>>>
>>> Another supportive trick is to hide the field from the editor with a 
>>> tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
>>> eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
>>> thus once set you have to go out of your way to alter the permalink 
>>> value, that is its more permanent.
>>>
>>> Further developments (optional reading)
>>>
>>>- Since the addition of the unused title operator, it is possible 
>>>(more to the point easier) to use this to generate a unique and 
>>> incremented 
>>>tiddler title and serial number. 
>>>- Rather than shadow tiddlers I am using this not only to generate a 
>>>tiddler Serial Number (TSN) but a "ghost tiddler" that follows any 
>>> tiddler 
>>>and provides a way to save metadata for any tiddler or field there in 
>>>(regardless of the title)
>>>- My only issues left are 
>>>   - Finding a way to generate/assign such TSN and Ghost tiddler in 
>>>   bulk.
>>>   - rebuild a parallel solution - system serial number, to assign a 
>>>   serial number to core and shadow tiddlers without touching them
>>>- Actually I have found you need only assign serial number where to 
>>>need them, say for these permalinks or compound tiddlers, that is with 
>>>subtiddlers that use the serial number for the parent rather than the 
>>> title 
>>>or a tag.
>>>
>>> Regards
>>> Tones
>>>
>>> On Thursday, 22 July 2021 at 06:50:01 UTC+10 springer wrote:
>>>
 About obsolete permalinks: 

 Surely a variant of the relink plugin could help maintain bread-crumbs 
 for obsolete links:

 Whenever relink does its thing, have it offer to create a 
 dictionary-tiddler entry pairing old-name and new-name; then have a 
 filter-condition ViewTemplate element show up at the bottom of old-name 
 tiddlers, where the new-name tiddler is transcluded (or linked-to) -- 
 perhaps pre-pending a note explaining that the old "Bombay" is now called 
 "Mumbai"...

 At first, I was worried about the case where I change tiddler title 
 from "Bombay" to "Mumbai" and then later generate a different one called 
 "Bombay" -- but there, too, I might be interested in seeing such a 
 ViewTemplate addition! After all, if I ever had shared a permalink to 
 #Bombay, some signposts around the changing namescape could be

[tw5] Re: What other tools compliment TiddlyWiki well? [discussion]

I'm thinking it largely depends on the "ecosystem" one may be living in.

Seeing as I've sold my soul to Google, Google Keep is my goto quick note 
taker.

I can access the full screen Google Keep, sidebar Google Keep when I'm in 
the other Google Apps, and have the Google Keep Chrome Extension, to 
quickly take notes while viewing some web page.

So quick note taking for some heavy-duty note making in TiddlyWiki later.

Mind you, I only ever use my Chromebook.  I never use my "smart" phone for 
anything other than text and phone.

Well, it is always a work-in-progress.

On Wednesday, July 21, 2021 at 4:10:04 PM UTC-3 Si wrote:

> This question was prompted by a discussion over in the thread on 
> incremental note-taking 
> .
>
> In my opinion a major weakness of TiddlyWiki is that it is not well suited 
> to quickly capturing information on the fly with minimal friction.
>
> For this reason I use another app as an "inbox" for quick ideas and tasks, 
> which I process later on. Currently I use Evernote, but I'm currently in 
> the process of looking for something else (would love to hear suggestions 
> for a good replacement). The number one contender at the moment is Joplin 
> , but I'm tempted by the purity of 
> using text/markdown files if I can find a good way to handle them on 
> Android.
>
> Anyway I thought it would be interesting to prompt a discussion by asking 
> the more general question: *What apps or tools do you use that you feel 
> compliment TiddlyWiki well?* *What does your workflow look like?*
>
> It doesn't matter the domain - note-taking and productivity are the 
> obvious categories, but please be free to share any tool you use in tandem 
> with TiddlyWiki.
>

-- 
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/3df60578-9d63-4ae4-8254-73bd3df0eb9en%40googlegroups.com.

[tw5] Re: Getting relink to prevent obsolete permalinks

Charlie,

I am not sure. I can't find that specific reply in this thread. Can you 
give me a link from the actual reply please?

I expect its something similar but with a different scope.

Thanks
Tones

On Thursday, 22 July 2021 at 13:12:58 UTC+10 cj.v...@gmail.com wrote:

> Silly question:  are you suggesting you are going to build what I already 
> built and mentioned a little earlier in this thread (Jul 20, 2021, 10:09:07 
> AM) ?
>
> On Wednesday, July 21, 2021 at 10:17:10 PM UTC-3 TW Tones wrote:
>
>> Springer et al,
>>
>> Forgive me for repeating myself, although a lot of interesting ideas, I 
>> believe these to be *non-problems.* 
>>
>> A simple solution is available here. an Example would be an alternate 
>> button to simple permalinks, I think someone else used a share icon. When 
>> clicking this on a given tiddler, it would assign a next number to a field 
>> in the tiddler (basically issuing a unique value field - not a UID or 
>> serial or GUID) then use this field/number to uniquely identify the tiddler 
>> shared, so it does not matter if it's title is renamed. Then generate a url 
>> that instead searches for any (but only one) tiddler with that field value.
>>
>> If *anyone asks* I will build this share button soon.
>>
>> That is if someone wants to publish a robust permalink for a tiddler 
>> who's title may change they use a built for purpose alternative to 
>> permalinks. Perhaps the existing name permalinks is misleading, perhaps 
>> they should be impermalinks.
>>
>> Here is a working example
>> a tiddler with the "permalink" field=1
>> the url wiki-url.html#:[permalink[1]] 
>> In the wiki Open target this 
>> can be dragged to bookmarks/favourites
>>
>> However I personally choose my tiddler names well enough when needed so 
>> they need not change in future, and if I am publishing a link somewhere it 
>> is to access specific content. the link has a purpose, and once someone has 
>> the link the purpose is fixed in time and should always honour its original 
>> share.
>>
>> A version of the above method where the link filter 
>> is [has[permalink]last[]] will always link to the largest permalink value, 
>> so one is sharing a link to the latest permalink tiddler or post.
>>
>> Another supportive trick is to hide the field from the editor with a 
>> tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
>> eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
>> thus once set you have to go out of your way to alter the permalink 
>> value, that is its more permanent.
>>
>> Further developments (optional reading)
>>
>>- Since the addition of the unused title operator, it is possible 
>>(more to the point easier) to use this to generate a unique and 
>> incremented 
>>tiddler title and serial number. 
>>- Rather than shadow tiddlers I am using this not only to generate a 
>>tiddler Serial Number (TSN) but a "ghost tiddler" that follows any 
>> tiddler 
>>and provides a way to save metadata for any tiddler or field there in 
>>(regardless of the title)
>>- My only issues left are 
>>   - Finding a way to generate/assign such TSN and Ghost tiddler in 
>>   bulk.
>>   - rebuild a parallel solution - system serial number, to assign a 
>>   serial number to core and shadow tiddlers without touching them
>>- Actually I have found you need only assign serial number where to 
>>need them, say for these permalinks or compound tiddlers, that is with 
>>subtiddlers that use the serial number for the parent rather than the 
>> title 
>>or a tag.
>>
>> Regards
>> Tones
>>
>> On Thursday, 22 July 2021 at 06:50:01 UTC+10 springer wrote:
>>
>>> About obsolete permalinks: 
>>>
>>> Surely a variant of the relink plugin could help maintain bread-crumbs 
>>> for obsolete links:
>>>
>>> Whenever relink does its thing, have it offer to create a 
>>> dictionary-tiddler entry pairing old-name and new-name; then have a 
>>> filter-condition ViewTemplate element show up at the bottom of old-name 
>>> tiddlers, where the new-name tiddler is transcluded (or linked-to) -- 
>>> perhaps pre-pending a note explaining that the old "Bombay" is now called 
>>> "Mumbai"...
>>>
>>> At first, I was worried about the case where I change tiddler title from 
>>> "Bombay" to "Mumbai" and then later generate a different one called 
>>> "Bombay" -- but there, too, I might be interested in seeing such a 
>>> ViewTemplate addition! After all, if I ever had shared a permalink to 
>>> #Bombay, some signposts around the changing namescape could be useful!
>>>
>>> -Springer
>>>
>>> On Tuesday, July 20, 2021 at 9:09:07 AM UTC-4 cj.v...@gmail.com wrote:
>>>
 This is such an awesome thread.

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

> *Walt,* the thing that bugs me most about the “immutable title/ID” 
> idea is that unless your notes are also going to be immutable, the 
> *content*

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

Soren,

I have not used it much yet as I am already a super user so possibly not in 
the target audience. Although I am sure I can learn a lot from it, why it 
may be good for less expert users is its "narrative quality", which may not 
help me. 

Users of you manual  can read through the story relating to different 
subjects getting a comprehensive introduction and hanging all the pieces 
together. I think this is fantastic.

Perhaps most valuable to me is being able to delegate some support to new 
users to your manual, where they can take time and learn rather than me 
writing new lessons to explain. As a result I still need to get to know it 
well.

   - However from my super user perspective it is not so easy to stick with 
   the story to find the Easter eggs in a lot of sections and search is 
   somewhat overwhelmed by amount of content.
   - There are however subject areas where I may as well be a new user and 
   I am likely to get the full benefit, yet they do not (yet?) go into the 
   detail I now need.
   - What is critical here is I think it is very well done and appropriate 
   for a broad audience, perhaps it is I that have outgrown some of its focus, 
   I do not think it needs to be modified for people like me.
   - At most, perhaps in future it could have some index or additional 
   notes that lead the more advanced user to other resources.

Thanks so much for this substantial contribution to the Community
Regards
Tones
 

On Wednesday, 21 July 2021 at 23:56:56 UTC+10 Soren Bjornstad wrote:

> 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/59880fdd-0c55-4753-978e-e7328a7cd944n%40googlegroups.com.

[tw5] Re: Getting relink to prevent obsolete permalinks

Silly question:  are you suggesting you are going to build what I already 
built and mentioned a little earlier in this thread (Jul 20, 2021, 10:09:07 
AM) ?

On Wednesday, July 21, 2021 at 10:17:10 PM UTC-3 TW Tones wrote:

> Springer et al,
>
> Forgive me for repeating myself, although a lot of interesting ideas, I 
> believe these to be *non-problems.* 
>
> A simple solution is available here. an Example would be an alternate 
> button to simple permalinks, I think someone else used a share icon. When 
> clicking this on a given tiddler, it would assign a next number to a field 
> in the tiddler (basically issuing a unique value field - not a UID or 
> serial or GUID) then use this field/number to uniquely identify the tiddler 
> shared, so it does not matter if it's title is renamed. Then generate a url 
> that instead searches for any (but only one) tiddler with that field value.
>
> If *anyone asks* I will build this share button soon.
>
> That is if someone wants to publish a robust permalink for a tiddler who's 
> title may change they use a built for purpose alternative to permalinks. 
> Perhaps the existing name permalinks is misleading, perhaps they should be 
> impermalinks.
>
> Here is a working example
> a tiddler with the "permalink" field=1
> the url wiki-url.html#:[permalink[1]] 
> In the wiki Open target this 
> can be dragged to bookmarks/favourites
>
> However I personally choose my tiddler names well enough when needed so 
> they need not change in future, and if I am publishing a link somewhere it 
> is to access specific content. the link has a purpose, and once someone has 
> the link the purpose is fixed in time and should always honour its original 
> share.
>
> A version of the above method where the link filter 
> is [has[permalink]last[]] will always link to the largest permalink value, 
> so one is sharing a link to the latest permalink tiddler or post.
>
> Another supportive trick is to hide the field from the editor with a 
> tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
> eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
> thus once set you have to go out of your way to alter the permalink value, 
> that is its more permanent.
>
> Further developments (optional reading)
>
>- Since the addition of the unused title operator, it is possible 
>(more to the point easier) to use this to generate a unique and 
> incremented 
>tiddler title and serial number. 
>- Rather than shadow tiddlers I am using this not only to generate a 
>tiddler Serial Number (TSN) but a "ghost tiddler" that follows any tiddler 
>and provides a way to save metadata for any tiddler or field there in 
>(regardless of the title)
>- My only issues left are 
>   - Finding a way to generate/assign such TSN and Ghost tiddler in 
>   bulk.
>   - rebuild a parallel solution - system serial number, to assign a 
>   serial number to core and shadow tiddlers without touching them
>- Actually I have found you need only assign serial number where to 
>need them, say for these permalinks or compound tiddlers, that is with 
>subtiddlers that use the serial number for the parent rather than the 
> title 
>or a tag.
>
> Regards
> Tones
>
> On Thursday, 22 July 2021 at 06:50:01 UTC+10 springer wrote:
>
>> About obsolete permalinks: 
>>
>> Surely a variant of the relink plugin could help maintain bread-crumbs 
>> for obsolete links:
>>
>> Whenever relink does its thing, have it offer to create a 
>> dictionary-tiddler entry pairing old-name and new-name; then have a 
>> filter-condition ViewTemplate element show up at the bottom of old-name 
>> tiddlers, where the new-name tiddler is transcluded (or linked-to) -- 
>> perhaps pre-pending a note explaining that the old "Bombay" is now called 
>> "Mumbai"...
>>
>> At first, I was worried about the case where I change tiddler title from 
>> "Bombay" to "Mumbai" and then later generate a different one called 
>> "Bombay" -- but there, too, I might be interested in seeing such a 
>> ViewTemplate addition! After all, if I ever had shared a permalink to 
>> #Bombay, some signposts around the changing namescape could be useful!
>>
>> -Springer
>>
>> On Tuesday, July 20, 2021 at 9:09:07 AM UTC-4 cj.v...@gmail.com wrote:
>>
>>> This is such an awesome thread.
>>>
>>> On Tuesday, July 20, 2021 at 9:04:07 AM UTC-3 Soren Bjornstad wrote:
>>>
 *Walt,* the thing that bugs me most about the “immutable title/ID” 
 idea is that unless your notes are also going to be immutable, the 
 *content* of a note can still change so much as to make the reference 
 not effective anymore. So I don't see much point in bothering, as long as 
 you can avoid having links break. Presumably the thing you were looking 
 for 
 won't move so far away from the updated note that you'll be unable to find 
 it, anyway (probably not more than one link away).


>>>

[tw5] Re: tidders created this week

Mohamad,

Yes, I have used the days(-7) before but that is a sliding last 7 days. 
useful in its own right, but not always what you want.

Consider using the view date format  as 
barro said, or with the more recent versions the format operator  
 including titlelist in 
prerelease 

<$view field=due format=date template="0WW"/>

*WW* ISO-8601 week number of year *0WW* Adds a leading zero

   - Thus for any given date you can place it in a particular week, 
   - list all with a date in the same week including current week - 1 for 
   last week, or +1 for next week
   - Once you have a week of tiddlers you can use 
  - DDD Day of week in full (eg, "Monday")
  - ddd Short day of week (eg, "Mon")
   
The following works for modified and non-system tiddlers, on 5.1.23, I am 
not sure why other variations such as system tiddlers and created date do 
not list in DOW order, it should be the same.

<$set name=this-week value=<> >
<$set name=last-week filter="[subtract[1]]" >

this-week=<> last-week=<>

;Modified last week
<$list filter="[all[tiddlers]!is[system]has[modified]sort[modified]]">
   <$list 
filter="[all[current]get[modified]format:date[0WW]match]" 
variable=last-week-number>
<$text text={{{ [all[current]get[modified]format:date[DDD]] }}}/> 
<$link/>
   




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

Regards
Tones



On Thursday, 22 July 2021 at 02:12:08 UTC+10 mohamed...@hotmail.com wrote:

> Hi,
>
> not exactly following , can you please clarify more what you mean?
> On Wednesday, July 21, 2021 at 8:07:20 AM UTC+2 barro...@gmail.com wrote:
>
>> I'm thinking of the  SO-8601 week number of year of one the date formats 
>> ( https://tiddlywiki.com/#DateFormat ) which would allow working with 
>> actual calendar weeks.  Does filter operators and search work with the 
>> different date formats or would week number have to be an user created 
>> field for the filter operators to work with.
>>
>> On Tuesday, July 20, 2021 at 1:48:22 PM UTC-4 mohamed...@hotmail.com 
>> wrote:
>>
>>> Hi ,
>>>
>>> is it possible to list all tiddlers created this week, that would 
>>> include past tiddlers  created 
>>> yesterday"Monday" , tiddlers created today " Tuesday". and future 
>>> tiddlers to be created in Wednesday ,Thursday and Friday.
>>>
>>> i know i can use something like this 
>>> {{{[all[tiddlers]] :filter[get[created]compare:date:gt[20210719]]}}}
>>>
>>> but then the date i am comparing against is static, and will need to be 
>>> changed manually every week
>>>
>>> I really like it , if only the date can be replaced with some kind of 
>>> dynamic value that is defined as the first day of the current week
>>>
>>> i know there is the days operator IE , [days[-1]]  , but then again its 
>>> not what i want and will also need manual adjustment every day
>>>
>>> is there any easy way around this ?
>>>
>>> thanks in advance
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d671439b-fad2-43f9-9205-e560a659452bn%40googlegroups.com.

[tw5] Re: What other tools compliment TiddlyWiki well? [discussion]

Me too like Brian, Keep/tiddlywiki however I expect this to change to 
return to my DS Notes, or mobile tiddlywikis.

A worthy discussion, and I am keen to hear others response's.

I don't concur with your statement Si, as I think I said before  *In my 
opinion a major weakness of TiddlyWiki is that it is not well suited to 
quickly capturing information on the fly with minimal friction.*
The only exception would be large volumes of media.

   - One way I support quick entry is to use projectify "quick add todo", 
   even if the only thing todo, is to later reclassify the tiddler as a 
   reference an idea etc...
   - Alternatively I use streams or just open a tag for collecting 
   information together eg shopping and do a new here then type. Use <> 
   in the tag tiddler to create a pill to see all so tagged.
   - Or I may assign a project name tag where the project is elsewhere, I 
   move these to the project wiki when working on the project.
   - I also use drag and drop or copy and paste found information a lot, 
   especially onto and into projectify tasks and stream nodes.
  - I can then drag these and drop them on projects, wikis etc..
   - I now use a tiddler inline edit tool to edit the text field without 
   going into edit mode.
   - My main supporting tools are other for purpose tiddlywikis like one 
   with JSON mangle as my data conversion wiki, or sources of icons and system 
   tags etc...
   - Another is I save all my macros and plugins below a folder and use 
   windows explorer to search my "TiddlyWiki intranet" to import tools a 
   tweeks.
   - I also make use of bookmarklets in browsers to drop a bundle of 
   tiddlers or settings on a wiki with a click. 



Tones
On Thursday, 22 July 2021 at 05:22:15 UTC+10 Brian Radspinner wrote:

> I use Google Keep to capture thoughts on the fly on my phone. When I get 
> back to my laptop, it's easy to copy and paste from the Keep web interface 
> into TW
>
> On Wednesday, July 21, 2021 at 12:10:04 PM UTC-7 Si wrote:
>
>> This question was prompted by a discussion over in the thread on 
>> incremental note-taking 
>> .
>>
>> In my opinion a major weakness of TiddlyWiki is that it is not well 
>> suited to quickly capturing information on the fly with minimal friction.
>>
>> For this reason I use another app as an "inbox" for quick ideas and 
>> tasks, which I process later on. Currently I use Evernote, but I'm 
>> currently in the process of looking for something else (would love to hear 
>> suggestions for a good replacement). The number one contender at the moment 
>> is Joplin , but I'm tempted by the 
>> purity of using text/markdown files if I can find a good way to handle them 
>> on Android.
>>
>> Anyway I thought it would be interesting to prompt a discussion by asking 
>> the more general question: *What apps or tools do you use that you feel 
>> compliment TiddlyWiki well?* *What does your workflow look like?*
>>
>> It doesn't matter the domain - note-taking and productivity are the 
>> obvious categories, but please be free to share any tool you use in tandem 
>> with TiddlyWiki.
>>
>

-- 
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/330f17ea-e38c-4a46-90f1-7d1cac70b2c8n%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

I am glad you are onto this bug, spaces in fieldnames,

However am I the only one who still intends to keep field names to a 
defacto naming standard such as i-am-afield no caps or spaces? so It is 
easy for me to tell field names apart from text and titles!

Of course I look forward to naming fields using tiddler titles (and the 
value a relationship type etc..). and to contain special prefixes or 
suffixes such as "-link" or (link)  but as a rule I would like a little 
structure and naming rules. 
This always helps retain a degree of simplicity when managing lots of 
complexity.

Regards
Tones


On Thursday, 22 July 2021 at 06:11:52 UTC+10 Saq Imtiaz wrote:

> I believe this check for field names is the cause:
>
>
> https://github.com/Jermolene/TiddlyWiki5/blob/d455072f13dd00955ae82d62d2d6e44581bdba9e/boot/boot.js#L1606
>
> On Wednesday, July 21, 2021 at 9:34:54 PM UTC+2 Saq Imtiaz wrote:
>
>> @Jeremy regarding this bug, I think it is related to having a space 
>> character in a field name.
>>
>> At https://tiddlywiki.com/prerelease/empty.html
>>
>> Create a new tiddler called "test" with a field name "my field" with a 
>> value of "hello".
>> Save and open the resultant file.
>>
>> You get a blank white screen, no errors in the console.
>>
>> On Friday, July 16, 2021 at 6:32:46 PM UTC+2 Saq Imtiaz wrote:
>>
>>> I don't have the opportunity to debug this at the moment but I believe 
>>> this is the commit responsible:
>>>
>>> https://github.com/springerspandrel/tw/commit/49a0b1ef1ef37d79e514c0a9cf7685e8f4baa75f#diff-81fd67dbd185daf4f0208c57ff40d029e2c72509417aec3bcb2f651900573431R265
>>>
>>> Seems like the boot process just doesn't load anything and we get a 
>>> blank screen.
>>>
>>> On Friday, July 16, 2021 at 6:30:19 PM UTC+2 Jeremy Ruston wrote:
>>>
 Hi Springer 

 Was it a "red screen of embarrassment" crash? It would certainly be 
 helpful to pin it down if we can. 

 > I'd also welcome tips on how to get github to actually download files 
 from the history (When I try, I just get html within a new browser tab). 

 It's a bit convoluted: first, click on the three dots at the top right 
 of the file in the commit listing: 



-- 
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/15a5a245-f830-474e-99d6-1e0323f5ae1fn%40googlegroups.com.

[tw5] Re: Getting relink to prevent obsolete permalinks

Springer et al,

Forgive me for repeating myself, although a lot of interesting ideas, I 
believe these to be *non-problems.* 

A simple solution is available here. an Example would be an alternate 
button to simple permalinks, I think someone else used a share icon. When 
clicking this on a given tiddler, it would assign a next number to a field 
in the tiddler (basically issuing a unique value field - not a UID or 
serial or GUID) then use this field/number to uniquely identify the tiddler 
shared, so it does not matter if it's title is renamed. Then generate a url 
that instead searches for any (but only one) tiddler with that field value.

If *anyone asks* I will build this share button soon.

That is if someone wants to publish a robust permalink for a tiddler who's 
title may change they use a built for purpose alternative to permalinks. 
Perhaps the existing name permalinks is misleading, perhaps they should be 
impermalinks.

Here is a working example
a tiddler with the "permalink" field=1
the url wiki-url.html#:[permalink[1]] 
In the wiki Open target this 
can be dragged to bookmarks/favourites

However I personally choose my tiddler names well enough when needed so 
they need not change in future, and if I am publishing a link somewhere it 
is to access specific content. the link has a purpose, and once someone has 
the link the purpose is fixed in time and should always honour its original 
share.

A version of the above method where the link filter 
is [has[permalink]last[]] will always link to the largest permalink value, 
so one is sharing a link to the latest permalink tiddler or post.

Another supportive trick is to hide the field from the editor with a 
tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
thus once set you have to go out of your way to alter the permalink value, 
that is its more permanent.

Further developments (optional reading)

   - Since the addition of the unused title operator, it is possible (more 
   to the point easier) to use this to generate a unique and incremented 
   tiddler title and serial number. 
   - Rather than shadow tiddlers I am using this not only to generate a 
   tiddler Serial Number (TSN) but a "ghost tiddler" that follows any tiddler 
   and provides a way to save metadata for any tiddler or field there in 
   (regardless of the title)
   - My only issues left are 
  - Finding a way to generate/assign such TSN and Ghost tiddler in bulk.
  - rebuild a parallel solution - system serial number, to assign a 
  serial number to core and shadow tiddlers without touching them
   - Actually I have found you need only assign serial number where to need 
   them, say for these permalinks or compound tiddlers, that is with 
   subtiddlers that use the serial number for the parent rather than the title 
   or a tag.

Regards
Tones

On Thursday, 22 July 2021 at 06:50:01 UTC+10 springer wrote:

> About obsolete permalinks: 
>
> Surely a variant of the relink plugin could help maintain bread-crumbs for 
> obsolete links:
>
> Whenever relink does its thing, have it offer to create a 
> dictionary-tiddler entry pairing old-name and new-name; then have a 
> filter-condition ViewTemplate element show up at the bottom of old-name 
> tiddlers, where the new-name tiddler is transcluded (or linked-to) -- 
> perhaps pre-pending a note explaining that the old "Bombay" is now called 
> "Mumbai"...
>
> At first, I was worried about the case where I change tiddler title from 
> "Bombay" to "Mumbai" and then later generate a different one called 
> "Bombay" -- but there, too, I might be interested in seeing such a 
> ViewTemplate addition! After all, if I ever had shared a permalink to 
> #Bombay, some signposts around the changing namescape could be useful!
>
> -Springer
>
> On Tuesday, July 20, 2021 at 9:09:07 AM UTC-4 cj.v...@gmail.com wrote:
>
>> This is such an awesome thread.
>>
>> On Tuesday, July 20, 2021 at 9:04:07 AM UTC-3 Soren Bjornstad wrote:
>>
>>> *Walt,* the thing that bugs me most about the “immutable title/ID” idea 
>>> is that unless your notes are also going to be immutable, the *content* of 
>>> a note can still change so much as to make the reference not effective 
>>> anymore. So I don't see much point in bothering, as long as you can avoid 
>>> having links break. Presumably the thing you were looking for won't move so 
>>> far away from the updated note that you'll be unable to find it, anyway 
>>> (probably not more than one link away).
>>>
>>>
>> Hence why I have an awful lot of love for relink.  I would have a rough 
>> time without it.  No broken (internal links) with Relink.
>>  
>>
>>> It is a good point on external links breaking, though. It would be cool 
>>> if you could set up redirects within TW, so that you could at least have an 
>>> incoming link to an old title go somewhere somewhat relevant. I guess you 
>>> could just leave the

[tw5] Re: RFC: Building a macro solution for top-to-botton

2021-07-21 Thread springer

Tones,

I look forward to checking out the focus tiddler tool. Does it already 
exist in some public form? (If so, sorry I missed it.)

I agree that there are lots of different workflows that might call for 
variations / different priorities.

-Springer



On Monday, July 19, 2021 at 8:04:21 PM UTC-4 TW Tones wrote:

> Springer,
>
> Thanks for that insight. I built a separate tool called focus tiddler ie 
> the tiddler with user focus, it included something like Erics History tab, 
> but also as I mentioned in the original post allow us "navigate to the last 
> opened or edited tiddler". In my (as yet unpublished) focus tiddler 
> solution (not that I was proposing here) I had a viewToolbar button (could 
> be in edit as well) to override the last opened or edited tiddler, that is 
> make any tiddler in the story the focused tiddler. Your feed back makes me 
> ask if perhaps allow selecting secondary tiddler as say the "focused work 
> tiddler" and that what ever the navigation activity "the last opened or 
> edited tiddler", that it would be easy to return to the "focused work 
> tiddler". ie the one where one is taking notes or reading to manage your 
> work flow (eg syllabus or class notes).
>
> I too use the classic story view as a rule, finding the others 
> frustrating, as a result I know little about their use. 
>
> My learnings from your reply include
>
>- Your desire to go back - I will look at incorporating that.
>   - the history tab helps here.
>   - I wonder the best way to select the tiddler to go back to (not 
>   just the last)
>- Getting keyboard shortcuts for any navigational component )inc top 
>and bottom story and sidebar)
>   - I would like to add a keyboard short cut to wikitext buttons I 
>   define - not sure how yet.
>- Would it be important to reopen a  "focused work tiddler" if closed?
>   - Then you could close all, display something then return.
>- Perhaps use a modifier to a shortcut to open/reopen a  "focused work 
>tiddler" for edit, 
>
> In closing, my focused tiddler method will go some way to meeting your 
> requirement, using the history tab will help even further, but you need 
> that tab displayed on the sidebar. The history tab is refreshed each Wiki 
> session (reload), this is something to do before a "class or presentation" 
> because you can easily return to a tiddler you opened during the session, 
> the list is limited to those you have opened or edited which is helpful.
>
> Regards
> Tones
>
> On Tuesday, 20 July 2021 at 06:03:12 UTC+10 springer wrote:
>
>> Tones,
>>
>> For "top to bottom": The most useful navigational add-ins, for my 
>> use-cases, are keyboard-driven. When desired tiddlers are scrolled out of 
>> view *and* this feels like an especially distracting obstacle (say, because 
>> I'm teaching, and wish to resume the prior discussion after jumping to a 
>> tangent), having to coordinate with the cursor is half the battle. 
>>
>> For various reasons, the "classic" story view (rather than pop or zoomin) 
>> is what I usually choose... but I wonder whether it would be possible to 
>> get the best of both worlds: allow multiple tiddlers in the story view, but 
>> "go back" to most recently active place in the story-river (other open 
>> tiddler in which most recent click happened if possible, or most recently 
>> opened from sidebar if not) when I close something? That's probably beyond 
>> what you're developing, but just one related hankering.
>>
>> -Springer
>>
>> On Monday, July 19, 2021 at 9:44:22 AM UTC-4 TW Tones wrote:
>>
>>>
>>> Folks,
>>>
>>> I just wanted to share that as I happen to be under a "stay at home" 
>>> order in Sydney because of a covid-19 D strain outbreak, I have being 
>>> focusing on some tiddlywiki tools development. I have one large project, 
>>> but while working on that it spawns a lot of little tools, born from the 
>>> innovation and my experience using tiddlywiki a lot, that tiddlywiki always 
>>> inspires in me.
>>>
>>> I thought I would issue an RFC or "request for comment" on my little 
>>> project called "top to bottom"
>>>
>>> I am designing a set of tools so you can easily navigate from the top to 
>>> bottom, also bottom to top, of the story with a single click, also to the 
>>> top of the side bar if you have a long one. It also uses a little trick to 
>>> ensure the last tiddler (especially if little) appears at the top of the 
>>> page if you navigate to it (rather than appearing at the bottom with 
>>> previous tiddler above it.
>>>
>>> These seem trivial but they can improve your work flow and navigation 
>>> speed if you have a number of tiddlers open.
>>>
>>> However this is where the request for comment comes in, can you suggest 
>>> any related features I could include so the macros are even more useful and 
>>> fit into the title top-to-bottom.
>>>
>>> Please let me know if you have a desire for other related features
>>>
>>> Finally shall I include the

[tw5] Re: RFC: Building a macro solution for top-to-botton

2021-07-21 Thread springer

Eric,

Wow, having the history in the toolbar (without needing sidebar open) is 
likely to do most of what I need, though it's still mouse-driven. I could 
even imagine making a variant that *closes* the current tiddler while 
returning to some prior tiddler. So I'm likely to include it in 
presentation-oriented solutions, where it's important to minimize those 
fumbling moments, however brief, of scrolling and muttering "So... as we 
were saying just a moment ago ..." To some extent, the "jump" menu (stashed 
up near sidebar-collapse button) was filling this gap for me, though it 
only includes open tiddlers, and sometimes I waver over whether or not I 
had actually closed some tidbit that we suddenly need to re-visit. 

-Springer

On Monday, July 19, 2021 at 5:05:37 PM UTC-4 Eric Shulman wrote:

> On Monday, July 19, 2021 at 1:03:12 PM UTC-7 springer wrote:
>
>> I wonder whether it would be possible to get the best of both worlds: 
>> allow multiple tiddlers in the story view, but "go back" to most recently 
>> active place in the story-river (other open tiddler in which most recent 
>> click happened if possible, or most recently opened from sidebar if not) 
>>
>
> Give this a try:
> http://tiddlytools.com/InsideTW/#TiddlyTools%2FHistory
> which adds a "History" command button to the tiddler toolbar.
>
> To install, just grab the tiddler's title, then drag-and drop it into your 
> document.  Although the interaction doesn't exactly match your wish list 
> (it uses a popup dialog and has no keyboard control... yet), it *does* make 
> it much easier to jump around in the Story view without having to manually 
> scroll back to where you were.  There's also these two extra toolbar 
> buttons that bypass the the popup dialog and simply navigate to the 
> corresponding tiddler with just one click.
> http://tiddlytools.com/InsideTW/#TiddlyTools%2FHistory%2FPrevious
> http://tiddlytools.com/InsideTW/#TiddlyTools%2FHistory%2FNext
>
> 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/e1b13113-edc5-4ab4-9b0a-208b7fb0a817n%40googlegroups.com.

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

On Wednesday, July 21, 2021 at 10:38:28 PM UTC+2 Mark S. wrote:

> So, you have to add manual config even though it's set up in the relink 
> plugin config?

Since your rename is happening outside of the Streams UI, yes. If you 
trigger a rename using the built in affordances, it is handled 
automatically if Relink is installed.  $:/config/RelinkOnRename is the 
default configuration tiddler which controls for both the core and relink 
what happens when renaming a tiddler via the edit template. It would be an 
overreach for Streams to change that behaviour that for users who rename 
outside of the Streams UI.

> It might be helpful if this was mentioned in the installation tiddler. 
> Most people are going to assume that if they have the relink tiddler that 
> they're good to go.

 Have not had any reports of this being a problem since the very first 
Streams release. Contributions to the documentation are always welcome.

-- 
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/dc3ac1af-c0d1-4b2c-9085-ca8682d427fdn%40googlegroups.com.

[tw5] Getting relink to prevent obsolete permalinks

2021-07-21 Thread springer

About obsolete permalinks: 

Surely a variant of the relink plugin could help maintain bread-crumbs for 
obsolete links:

Whenever relink does its thing, have it offer to create a 
dictionary-tiddler entry pairing old-name and new-name; then have a 
filter-condition ViewTemplate element show up at the bottom of old-name 
tiddlers, where the new-name tiddler is transcluded (or linked-to) -- 
perhaps pre-pending a note explaining that the old "Bombay" is now called 
"Mumbai"...

At first, I was worried about the case where I change tiddler title from 
"Bombay" to "Mumbai" and then later generate a different one called 
"Bombay" -- but there, too, I might be interested in seeing such a 
ViewTemplate addition! After all, if I ever had shared a permalink to 
#Bombay, some signposts around the changing namescape could be useful!

-Springer

On Tuesday, July 20, 2021 at 9:09:07 AM UTC-4 cj.v...@gmail.com wrote:

> This is such an awesome thread.
>
> On Tuesday, July 20, 2021 at 9:04:07 AM UTC-3 Soren Bjornstad wrote:
>
>> *Walt,* the thing that bugs me most about the “immutable title/ID” idea 
>> is that unless your notes are also going to be immutable, the *content* of 
>> a note can still change so much as to make the reference not effective 
>> anymore. So I don't see much point in bothering, as long as you can avoid 
>> having links break. Presumably the thing you were looking for won't move so 
>> far away from the updated note that you'll be unable to find it, anyway 
>> (probably not more than one link away).
>>
>>
> Hence why I have an awful lot of love for relink.  I would have a rough 
> time without it.  No broken (internal links) with Relink.
>  
>
>> It is a good point on external links breaking, though. It would be cool 
>> if you could set up redirects within TW, so that you could at least have an 
>> incoming link to an old title go somewhere somewhat relevant. I guess you 
>> could just leave the old title with a link to the new one, but without an 
>> obvious way to distinguish redirect tiddlers from other tiddlers, they 
>> would probably get in your way and make you think they were the “real” 
>> tiddlers all the time.
>>
>>
> Link rot.  Redirects is a possibility.  I much prefer UID fields and 
> providing links to a Tiddler in some TiddlyWiki with a "UID" reference.  
> (related thread: A Prototype of UID's for stable permalinks 
> )
>
> So if I want to provide folk with a link to a specific tiddler in some 
> TiddlyWiki, in a way that allows me to change the tiddler title willy-nilly 
> without breaking the link, I would give folk this:
>
>  
> https://tiddlywiki-programming.neocities.org/CJ_TiddlyWikiProgramming.html#:[uid[2]]
>  
> 
>
> For some reason, I prefer this than setting up redirects.  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c4a1eeb4-d9db-4766-ae18-67dc82a0dbc7n%40googlegroups.com.

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

So, you have to add manual config even though it's set up in the relink 
plugin config? It might be helpful if this was mentioned in the 
installation tiddler. Most people are going to assume that if they have the 
relink tiddler that they're good to go.

Thanks! 

On Wednesday, July 21, 2021 at 1:17:49 PM UTC-7 saq.i...@gmail.com wrote:

> @Mark S
>
> $:/config/RelinkOnRename is in fact not enabled by default on the Streams 
> site. I'll ensure that is next time I push an update.
>
> For now create  $:/config/RelinkOnRename with a text field value of yes
>
> On Wednesday, July 21, 2021 at 10:12:02 PM UTC+2 Mark S. wrote:
>
>> Yes. I'm using direct from your site.
>>
>> On Wednesday, July 21, 2021 at 11:46:06 AM UTC-7 saq.i...@gmail.com 
>> wrote:
>>
>>> @Mark S
>>>
>>> Is  $:/config/RelinkOnRename set to yes?
>>>
>>> Streams does add configuration for Relink to act on the stream-list 
>>> field:
>>> [image: Screenshot 2021-07-21 204538.png]
>>>
>>> On Wednesday, July 21, 2021 at 7:35:24 PM UTC+2 Mark S. wrote:
>>>
 Trying streams. I notice that when I change the name of a tiddler, it 
 drops out of the original list, apparently because *relink* doesn't 
 operate on the streams-list field. Is there a tweak to fix that?

 On Wednesday, July 21, 2021 at 7:46:03 AM UTC-7 fred@gmail.com 
 wrote:

> I think I'll go ahead and change my icon in my next release for users 
> who may want to use both. 
> Would I get away with just changing the colour? Any SVG artist out 
> there?
>
>
> On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:
>
>> Hi Walt, thanks for the kind words.
>>
>> The only side effect of running both in parallel would be the 
>> appearance of two identical buttons that don't behave the same way... (I 
>> think)
>> This problem could easily be avoided if I used a different icon, but 
>> I am not super creative and Jan's icon is just perfect .
>>
>> The plugin does not do any house-cleaning; that would be rude, would 
>> it not?
>>
>>
>>
>> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>>
>>> Nice job, @Fred; it renders outlines from Streams not only 
>>> faithfully, but beautifully! 
>>>
>>> One question, before i install this in my primary desktop wiki: you 
>>> say in your Credits that it borrows from -and is incompatible with- 
>>> Jan's 
>>> streams-to-text addon ... Does this mean i 
>>> should first remove the several bits that make up that addon before 
>>> installing streams-fusion plugin?  Or does your plugin do its own 
>>> proper 
>>> house-cleaning?
>>>
>>> /walt
>>>
>>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
>>> wrote:
>>>
 ok, here's a beta streams-fusion addon: 
 https://fastfreddy.gitlab.io/streams-fusion/
 please note the troubleshooting step is required until the next 
 Streams release; beta users beware

 very open to constructive feedback; and/or different ways of 
 shipping such as rolled in the Streams plugin itself if it is good 
 enough.

 On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  
 wrote:

> That is definitely an oversight from when I added that at Jan's 
> request. If you open an issue on Github, it will be resolved for the 
> next 
> release.
>
> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com 
> wrote:
>
>> @saq
>> quick question: am trying to package my addon, am a bit of a 
>> newbie unfortunately. 
>> is it possible we need to modify this line (bold insert)
>> <$list 
>> filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
>> variable="btnTiddler">
>>
>> in $:/plugins/sq/streams/nodes-list-template ?
>> otherwise, it feels like my new button does not take when it is 
>> contained within a plugineven with the 
>> $:/tags/streams/root-buttons 
>> tag 
>>
>> thanks much...
>>
>> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  
>> wrote:
>>
>>> a quick update to everyone;
>>>
>>> I am making steady progress on packaging this merging solution, 
>>> hoping to release as a Streams plugin addon. I have repurposed the 
>>> button 
>>> from https://szen.io/stream/. I now have it also working as a 
>>> Streams context menu, with keyboard shortcuts, and it can export 
>>> sub-trees 
>>> correctly by adjusting the depth levels of the bulleted/numbered 
>>> lists.
>>>
>>> A few ideas I am going to try to roll in and release a beta by 
>>> the end of this week

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

@Mark S

$:/config/RelinkOnRename is in fact not enabled by default on the Streams 
site. I'll ensure that is next time I push an update.

For now create  $:/config/RelinkOnRename with a text field value of yes

On Wednesday, July 21, 2021 at 10:12:02 PM UTC+2 Mark S. wrote:

> Yes. I'm using direct from your site.
>
> On Wednesday, July 21, 2021 at 11:46:06 AM UTC-7 saq.i...@gmail.com wrote:
>
>> @Mark S
>>
>> Is  $:/config/RelinkOnRename set to yes?
>>
>> Streams does add configuration for Relink to act on the stream-list field:
>> [image: Screenshot 2021-07-21 204538.png]
>>
>> On Wednesday, July 21, 2021 at 7:35:24 PM UTC+2 Mark S. wrote:
>>
>>> Trying streams. I notice that when I change the name of a tiddler, it 
>>> drops out of the original list, apparently because *relink* doesn't 
>>> operate on the streams-list field. Is there a tweak to fix that?
>>>
>>> On Wednesday, July 21, 2021 at 7:46:03 AM UTC-7 fred@gmail.com 
>>> wrote:
>>>
 I think I'll go ahead and change my icon in my next release for users 
 who may want to use both. 
 Would I get away with just changing the colour? Any SVG artist out 
 there?


 On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:

> Hi Walt, thanks for the kind words.
>
> The only side effect of running both in parallel would be the 
> appearance of two identical buttons that don't behave the same way... (I 
> think)
> This problem could easily be avoided if I used a different icon, but I 
> am not super creative and Jan's icon is just perfect .
>
> The plugin does not do any house-cleaning; that would be rude, would 
> it not?
>
>
>
> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>
>> Nice job, @Fred; it renders outlines from Streams not only 
>> faithfully, but beautifully! 
>>
>> One question, before i install this in my primary desktop wiki: you 
>> say in your Credits that it borrows from -and is incompatible with- 
>> Jan's 
>> streams-to-text addon ... Does this mean i 
>> should first remove the several bits that make up that addon before 
>> installing streams-fusion plugin?  Or does your plugin do its own proper 
>> house-cleaning?
>>
>> /walt
>>
>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
>> wrote:
>>
>>> ok, here's a beta streams-fusion addon: 
>>> https://fastfreddy.gitlab.io/streams-fusion/
>>> please note the troubleshooting step is required until the next 
>>> Streams release; beta users beware
>>>
>>> very open to constructive feedback; and/or different ways of 
>>> shipping such as rolled in the Streams plugin itself if it is good 
>>> enough.
>>>
>>> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>>>
 That is definitely an oversight from when I added that at Jan's 
 request. If you open an issue on Github, it will be resolved for the 
 next 
 release.

 On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com 
 wrote:

> @saq
> quick question: am trying to package my addon, am a bit of a 
> newbie unfortunately. 
> is it possible we need to modify this line (bold insert)
> <$list 
> filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
> variable="btnTiddler">
>
> in $:/plugins/sq/streams/nodes-list-template ?
> otherwise, it feels like my new button does not take when it is 
> contained within a plugineven with the 
> $:/tags/streams/root-buttons 
> tag 
>
> thanks much...
>
> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  
> wrote:
>
>> a quick update to everyone;
>>
>> I am making steady progress on packaging this merging solution, 
>> hoping to release as a Streams plugin addon. I have repurposed the 
>> button 
>> from https://szen.io/stream/. I now have it also working as a 
>> Streams context menu, with keyboard shortcuts, and it can export 
>> sub-trees 
>> correctly by adjusting the depth levels of the bulleted/numbered 
>> lists.
>>
>> A few ideas I am going to try to roll in and release a beta by 
>> the end of this week
>>
>> Cheers
>>
>> On Sat, 17 Jul 2021 at 09:06, Frédéric Demers  
>> wrote:
>>
>>> with capture:
>>>
>>> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers <
>>> fred@gmail.com> wrote:
>>>
 nevermind, I think I solved it at least, significant 
 progress

 here's the wikitext for the challenging nodes; renders pretty 
 well:

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

Yes. I'm using direct from your site.

On Wednesday, July 21, 2021 at 11:46:06 AM UTC-7 saq.i...@gmail.com wrote:

> @Mark S
>
> Is  $:/config/RelinkOnRename set to yes?
>
> Streams does add configuration for Relink to act on the stream-list field:
> [image: Screenshot 2021-07-21 204538.png]
>
> On Wednesday, July 21, 2021 at 7:35:24 PM UTC+2 Mark S. wrote:
>
>> Trying streams. I notice that when I change the name of a tiddler, it 
>> drops out of the original list, apparently because *relink* doesn't 
>> operate on the streams-list field. Is there a tweak to fix that?
>>
>> On Wednesday, July 21, 2021 at 7:46:03 AM UTC-7 fred@gmail.com wrote:
>>
>>> I think I'll go ahead and change my icon in my next release for users 
>>> who may want to use both. 
>>> Would I get away with just changing the colour? Any SVG artist out there?
>>>
>>>
>>> On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:
>>>
 Hi Walt, thanks for the kind words.

 The only side effect of running both in parallel would be the 
 appearance of two identical buttons that don't behave the same way... (I 
 think)
 This problem could easily be avoided if I used a different icon, but I 
 am not super creative and Jan's icon is just perfect .

 The plugin does not do any house-cleaning; that would be rude, would it 
 not?



 On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:

> Nice job, @Fred; it renders outlines from Streams not only faithfully, 
> but beautifully! 
>
> One question, before i install this in my primary desktop wiki: you 
> say in your Credits that it borrows from -and is incompatible with- Jan's 
> streams-to-text addon ... Does this mean i 
> should first remove the several bits that make up that addon before 
> installing streams-fusion plugin?  Or does your plugin do its own proper 
> house-cleaning?
>
> /walt
>
> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
> wrote:
>
>> ok, here's a beta streams-fusion addon: 
>> https://fastfreddy.gitlab.io/streams-fusion/
>> please note the troubleshooting step is required until the next 
>> Streams release; beta users beware
>>
>> very open to constructive feedback; and/or different ways of shipping 
>> such as rolled in the Streams plugin itself if it is good enough.
>>
>> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>>
>>> That is definitely an oversight from when I added that at Jan's 
>>> request. If you open an issue on Github, it will be resolved for the 
>>> next 
>>> release.
>>>
>>> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com 
>>> wrote:
>>>
 @saq
 quick question: am trying to package my addon, am a bit of a newbie 
 unfortunately. 
 is it possible we need to modify this line (bold insert)
 <$list 
 filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
 variable="btnTiddler">

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

 thanks much...

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

> a quick update to everyone;
>
> I am making steady progress on packaging this merging solution, 
> hoping to release as a Streams plugin addon. I have repurposed the 
> button 
> from https://szen.io/stream/. I now have it also working as a 
> Streams context menu, with keyboard shortcuts, and it can export 
> sub-trees 
> correctly by adjusting the depth levels of the bulleted/numbered 
> lists.
>
> A few ideas I am going to try to roll in and release a beta by the 
> end of this week
>
> Cheers
>
> On Sat, 17 Jul 2021 at 09:06, Frédéric Demers  
> wrote:
>
>> with capture:
>>
>> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers  
>> wrote:
>>
>>> nevermind, I think I solved it at least, significant progress
>>>
>>> here's the wikitext for the challenging nodes; renders pretty 
>>> well:
>>>
>>> * 
>>>
>>> ''Streams'' uses the following tiddler fields to maintain the 
>>> structure of a stream:
>>>
>>> * each node tiddler has a field `stream-type`
>>> * each node that has children, contains their titles in a list 
>>> in the field `stream-list`
>>> * each node that has a parent, contains the parent's title in 
>>> the field `parent`
>>>
>>> ''You can

Re: [tw5] I broke the json pre-release :|

I believe this check for field names is the cause:

https://github.com/Jermolene/TiddlyWiki5/blob/d455072f13dd00955ae82d62d2d6e44581bdba9e/boot/boot.js#L1606

On Wednesday, July 21, 2021 at 9:34:54 PM UTC+2 Saq Imtiaz wrote:

> @Jeremy regarding this bug, I think it is related to having a space 
> character in a field name.
>
> At https://tiddlywiki.com/prerelease/empty.html
>
> Create a new tiddler called "test" with a field name "my field" with a 
> value of "hello".
> Save and open the resultant file.
>
> You get a blank white screen, no errors in the console.
>
> On Friday, July 16, 2021 at 6:32:46 PM UTC+2 Saq Imtiaz wrote:
>
>> I don't have the opportunity to debug this at the moment but I believe 
>> this is the commit responsible:
>>
>> https://github.com/springerspandrel/tw/commit/49a0b1ef1ef37d79e514c0a9cf7685e8f4baa75f#diff-81fd67dbd185daf4f0208c57ff40d029e2c72509417aec3bcb2f651900573431R265
>>
>> Seems like the boot process just doesn't load anything and we get a blank 
>> screen.
>>
>> On Friday, July 16, 2021 at 6:30:19 PM UTC+2 Jeremy Ruston wrote:
>>
>>> Hi Springer 
>>>
>>> Was it a "red screen of embarrassment" crash? It would certainly be 
>>> helpful to pin it down if we can. 
>>>
>>> > I'd also welcome tips on how to get github to actually download files 
>>> from the history (When I try, I just get html within a new browser tab). 
>>>
>>> It's a bit convoluted: first, click on the three dots at the top right 
>>> of the file in the commit listing: 
>>>
>>>

-- 
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/4a45238f-904b-4e3b-8c42-cae6b10a8e64n%40googlegroups.com.

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

a new icon, improved readme, everything else is the same ->
http://fastfreddy.gitlab.io/streams-fusion/ .
should help interoperability with streams-to-text addon; though will only
be able to test later

@saq agreed; not ideal. That is the reason my plugin only inserts the 
wrappers in case a node is multi-line or starts with !!, in order to
preserve the structure when nodes are converted to list items. This
deliberate but inconsistent behaviour annoys me too, but wrapping
everything in  tags felt excessive as many streams probably won't need
it.

The approach overall does have many limitations. Additionally, any
locally-only-relevant wikitext (fields/macros/filters) may fail when it is
copied, out of context, into a new tiddler with a different name and
structure.

I have been using the space-space-newline plugin myself of late; didn't
think it could have a role here, but I'll investigate.

On Wed, 21 Jul 2021 at 15:47, Saq Imtiaz  wrote:

> With regards to exporting a stream as a wikitext list, I have never
> pursued the option involving wrapping things in DIVs because the resultant
> output is quite difficult to read and edit, at which point just outputting
> HTML might be cleaner.
>
> However one option that might be worth investigating is using @pmario's
> "space space newline" plugin as a dependency, and prefixing every
> line-break in a node with two space characters. Problem is that this will
> interfere with multiline constructs like wikitext tables.
>
> https://wikilabs.github.io/editions/space-space-newline/
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/75d57208-8942-4c2e-806f-db4846a16775n%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/CAAY2DnMo-r5n_u2yspBdLFf2RdByB3Jq2SYZ0UZ-hQnh8vXGGQ%40mail.gmail.com.

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

2021-07-21 Thread ludwa6

Yes @Fred : this does indeed work... Though there is no streams-to-text 
addon in Saq's instance, so i'm guessing that's where the conflict lies.  
Anyway: i think i can deal w/ this conflict, so... All good Fred; your 
plugin's a real gem!

Walt

On Wednesday, July 21, 2021 at 8:02:04 PM UTC+1 fred@gmail.com wrote:

> well, Saq releases faster than I can type.
>
> @walt again: can you confirm that doing these steps directly on Streams' 
> page work for you?
>
>
>1. drag the streams-fusion plugin from 
>http://fastfreddy.gitlab.io/streams-fusion/ onto 
>https://saqimtiaz.github.io/streams/ and install
>2. (removed -> thanks Saq!)
>
> when I try (from work), I get the merge icon at the bottom of the tiddlers 
> that contain nodes 
>
>
>
> On Wed, 21 Jul 2021 at 14:57, Frédéric Demers  wrote:
>
>> @walt again: can you confirm that doing these steps direclty on Streams' 
>> page work for you?
>>
>>
>>1. drag teh streams-fusion plugin from 
>>http://fastfreddy.gitlab.io/streams-fusion/ onto 
>>https://saqimtiaz.github.io/streams/ and install
>>2. move the Streams-fusion shadow tiddler 
>>$:/plugins/phiv/streams-fusion/fuse-button 
>>
>> 
>>  out 
>>of the shadows by editing it and saving it
>>
>> when I try (from work), I get the merge icon at the bottom of the 
>> tiddlers that contain nodes
>>
>>
>> On Wed, 21 Jul 2021 at 14:49, Frédéric Demers  wrote:
>>
>>> @walt; hmm I'll have to experiment a bit more this evening. I have not 
>>> tried to run both Jan and mine in parallel, though I will. my next version 
>>> will have a different icon. I found a nice one on flaticon.
>>>
>>> Streams 1.2.22 is a future version, tongue-in-cheek, based on the github 
>>> issue I put in at Saq's request 
>>> https://github.com/saqimtiaz/streams/issues/30
>>> In the meantime, maybe try adjusting the filter in Stream's 
>>> $:/plugins/sq/streams/nodes-list-template tiddler as per the github 
>>> issue recommendation and see if that helps. Failing that, there may be 
>>> something else I am overlooking.
>>>
>>> On Wed, 21 Jul 2021 at 13:40, ludwa6  wrote:
>>>
 Hey @Fred: I've tried to install in my desktop TW instance, and am 
 having some trouble.  What i did was:

1. Installed your plugin (it's there and active, according to 
control panel);
2. Upgraded my Streams plugin from v1.2.19 to 1.2.22 (/notetoself: 
must keep closer tabs on Saq's developments!);
3. Moved the Streams-fusion shadow tiddler 
$:/plugins/phiv/streams-fusion/fuse-button 

 
  out 
of the shadows by editing it and saving it.

 After each of these steps i saved and reloaded... And still i have just 
 one of those neat flatten icons below my Streams, which opens Jan's 
 streams-to-text modal instead of yours when i click on it.
 NB: i do also have Relink v2.0.0 installed, so it seems i have the 
 dependencies covered.
 Now i'm wondering if these steps need to be taken in a different order? 
 or if there is in fact some interference between your code and Jan's?
 (if so, i dunno what is proper dev etiquette in a case like this -but 
 i'll do whatever admin housecleaning is needed, if given idiot-proof 
 instructions <8-)

 Can you please advise?

 /walt

 On Wednesday, July 21, 2021 at 2:42:05 PM UTC+1 fred@gmail.com 
 wrote:

> Hi Walt, thanks for the kind words.
>
> The only side effect of running both in parallel would be the 
> appearance of two identical buttons that don't behave the same way... (I 
> think)
> This problem could easily be avoided if I used a different icon, but I 
> am not super creative and Jan's icon is just perfect .
>
> The plugin does not do any house-cleaning; that would be rude, would 
> it not?
>
>
>
> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>
>> Nice job, @Fred; it renders outlines from Streams not only 
>> faithfully, but beautifully! 
>>
>> One question, before i install this in my primary desktop wiki: you 
>> say in your Credits that it borrows from -and is incompatible with- 
>> Jan's 
>> streams-to-text addon ... Does this mean i 
>> should first remove the several bits that make up that addon before 
>> installing streams-fusion plugin?  Or does your plugin do its own proper 
>> house-cleaning?
>>
>> /walt
>>
>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
>> wrote:
>>
>>> ok, here's a beta streams-fusion addon: 
>>> https://fastfreddy.gitlab.io/streams-fusion/
>>> please note the troubleshooting step is

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

With regards to exporting a stream as a wikitext list, I have never pursued 
the option involving wrapping things in DIVs because the resultant output 
is quite difficult to read and edit, at which point just outputting HTML 
might be cleaner.

However one option that might be worth investigating is using @pmario's 
"space space newline" plugin as a dependency, and prefixing every 
line-break in a node with two space characters. Problem is that this will 
interfere with multiline constructs like wikitext tables.

https://wikilabs.github.io/editions/space-space-newline/

-- 
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/75d57208-8942-4c2e-806f-db4846a16775n%40googlegroups.com.

[tw5] Re: Excising Large Outlines in TW

2021-07-21 Thread Mark Cubberley

@David
I have been keeping my eye on the Subsume threads and this plugin may be 
what I'm looking for. Between my naiveté of TW and, for the moment, a 
rather nebulous pedagogical project, I am not convinced I know what I'm 
asking, but I appreciate the reply nonetheless.

@ Mark S.
You are correct. More often than not, there IS too much material and I my 
intent is not to add more to an already dense curriculum. I see systems 
thinking as pedagogical strategy/framework for my teaching. (Systems 
thinking in chemical education is new to me and to chemical education for 
that matter.) I do not yet know what content I may have to sacrifice to use 
this pedagogy, nor if the loss of this content compromises the learning 
objectives of the course(s). I am hoping to figure all this out in a public 
facing TW using these concept outlines as a knowledge base.
On Wednesday, July 21, 2021 at 2:04:41 PM UTC-4 Mark S. wrote:

> The official slicer edition does pretty much what you describe 
> https://tiddlywiki.com/editions/text-slicer/ .
> But it uses a complicated relationship between the resulting tiddlers that 
> may be difficult to manipulate.
>
> Notowritey (https://marxsal.github.io/various/notowritey.html) allows you 
> to split large texts using a regular expression. You can then manipulate 
> items into a hierarchical arrangement in a manner similar to a regular 
> outliner. The relationship is based on simple listing and tagging.
>
> I would imagine for a systems approach, you would have to add a great deal 
> more of material. What I remember about chemistry is that they already give 
> you too much material to remember and often assume you are familiar with 
> processes and techniques that you have never encountered anywhere. As if 
> someone just ripped pages out of your textbook and threw them away. Trying 
> to see how you could fit MORE into the curriculum seems somewhat unkind.
>
> Another Mark
>
> On Wednesday, July 21, 2021 at 10:06:42 AM UTC-7 mark.cu...@gmail.com 
> wrote:
>
>> I have been using Soren’s Grok TiddlyWiki and his Zettelkasten shell over 
>> the last several weeks. Most of this time has been just getting stuff into 
>> TW and seeing what happens (or doesn't and trying to figure out why). I 
>> have not spent any time creating, connecting, etc.. The product of my work 
>> thus far is here.
>>
>> I have two large outlines (GeneralChemistryACCMOutline and 
>> OrganicChemistryACCMOutline) that delineate anchoring concept content 
>> maps  for most of the 
>> undergraduate chemistry I teach. The hierarchy of these outlines is 
>> identical at Level 1 (Big Ideas) and Level 2 (Enduring Understandings) and 
>> differ at Level 3 (Subdisciplinary Articulations) and Level 4 (Content 
>> Details).
>>
>> I need to excise these outlines and then add open educational resources 
>> (text, links to videos, images, and simulations, exercises, etc.) to the 
>> resulting tiddlers.
>>
>> I am interested in your thoughts on how I might excise these outlines in 
>> a (unique?) way that leverages TW’s utility/flexibility as a 
>> content-management system considering:
>>
>>1. The order of Level 1 Big Ideas is consistent with the sequence of 
>>instruction.
>>2. I would like to somehow leverage TW and the connected, 
>>context-free facts derived from these outlines to move away from a 
>>reductionist approach to teaching and learning to a systems approach 
>> to teaching and 
>>learning. 
>>3. I do not yet know specifically how I am going to use this resource 
>>in a teaching setting.
>>4. I am new to TW…
>>
>> Thanks for your help.
>>
>> Mark
>>
>

-- 
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/793e6ad4-26b4-4e64-aa37-15312db21e61n%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

@Jeremy regarding this bug, I think it is related to having a space 
character in a field name.

At https://tiddlywiki.com/prerelease/empty.html

Create a new tiddler called "test" with a field name "my field" with a 
value of "hello".
Save and open the resultant file.

You get a blank white screen, no errors in the console.

On Friday, July 16, 2021 at 6:32:46 PM UTC+2 Saq Imtiaz wrote:

> I don't have the opportunity to debug this at the moment but I believe 
> this is the commit responsible:
>
> https://github.com/springerspandrel/tw/commit/49a0b1ef1ef37d79e514c0a9cf7685e8f4baa75f#diff-81fd67dbd185daf4f0208c57ff40d029e2c72509417aec3bcb2f651900573431R265
>
> Seems like the boot process just doesn't load anything and we get a blank 
> screen.
>
> On Friday, July 16, 2021 at 6:30:19 PM UTC+2 Jeremy Ruston wrote:
>
>> Hi Springer
>>
>> Was it a "red screen of embarrassment" crash? It would certainly be 
>> helpful to pin it down if we can.
>>
>> > I'd also welcome tips on how to get github to actually download files 
>> from the history (When I try, I just get html within a new browser tab).
>>
>> It's a bit convoluted: first, click on the three dots at the top right of 
>> the file in the commit listing:
>>
>>

-- 
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/2a2f4b2e-0148-40e0-912b-88c2bbd41b2dn%40googlegroups.com.

[tw5] Re: What other tools compliment TiddlyWiki well? [discussion]

2021-07-21 Thread Brian Radspinner

I use Google Keep to capture thoughts on the fly on my phone. When I get 
back to my laptop, it's easy to copy and paste from the Keep web interface 
into TW

On Wednesday, July 21, 2021 at 12:10:04 PM UTC-7 Si wrote:

> This question was prompted by a discussion over in the thread on 
> incremental note-taking 
> .
>
> In my opinion a major weakness of TiddlyWiki is that it is not well suited 
> to quickly capturing information on the fly with minimal friction.
>
> For this reason I use another app as an "inbox" for quick ideas and tasks, 
> which I process later on. Currently I use Evernote, but I'm currently in 
> the process of looking for something else (would love to hear suggestions 
> for a good replacement). The number one contender at the moment is Joplin 
> , but I'm tempted by the purity of 
> using text/markdown files if I can find a good way to handle them on 
> Android.
>
> Anyway I thought it would be interesting to prompt a discussion by asking 
> the more general question: *What apps or tools do you use that you feel 
> compliment TiddlyWiki well?* *What does your workflow look like?*
>
> It doesn't matter the domain - note-taking and productivity are the 
> obvious categories, but please be free to share any tool you use in tandem 
> with TiddlyWiki.
>

-- 
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/396fdb25-5428-4fd0-86aa-e629be4f9212n%40googlegroups.com.

[tw5] What other tools compliment TiddlyWiki well? [discussion]

2021-07-21 Thread Si

This question was prompted by a discussion over in the thread on 
incremental note-taking 
.

In my opinion a major weakness of TiddlyWiki is that it is not well suited 
to quickly capturing information on the fly with minimal friction.

For this reason I use another app as an "inbox" for quick ideas and tasks, 
which I process later on. Currently I use Evernote, but I'm currently in 
the process of looking for something else (would love to hear suggestions 
for a good replacement). The number one contender at the moment is Joplin 
, but I'm tempted by the purity of 
using text/markdown files if I can find a good way to handle them on 
Android.

Anyway I thought it would be interesting to prompt a discussion by asking 
the more general question: *What apps or tools do you use that you feel 
compliment TiddlyWiki well?* *What does your workflow look like?*

It doesn't matter the domain - note-taking and productivity are the obvious 
categories, but please be free to share any tool you use in tandem with 
TiddlyWiki.

-- 
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/f630d2d4-1fcb-4d7e-84dd-ad42f923bb27n%40googlegroups.com.

[tw5] What other tools do you use that you feel compliment TiddlyWiki well? [discussion]

2021-07-21 Thread Si

This question was prompted by a discussion over in the thread on 
incremental note-taking 
.

In my opinion a major weakness of TiddlyWiki is that it is not well suited 
to quickly capturing information on the fly with minimal friction.

For this reason I use another app as an "inbox" for quick ideas and tasks, 
which I process later on. Currently I use Evernote, but I'm currently in 
the process of looking for something else (would love to hear suggestions 
for a good replacement). The number one contender at the moment is Joplin 
, but I'm tempted by the purity of 
using text/markdown files if I can find a good way to handle them on 
Android.

Anyway I thought it would be interesting to prompt a discussion by asking 
the more general question: *What apps or tools do you use that you feel 
compliment TiddlyWiki well?* *What does your workflow look like?*

It doesn't matter the domain - note-taking and productivity are the obvious 
categories, but please feel free to share any tool you use in tandem with 
TiddlyWiki.

-- 
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/f1544119-e7d1-4862-bb66-a47aa2f5b33cn%40googlegroups.com.

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

2021-07-21 Thread Brian Radspinner

To start: I don't have any coding background. I've been using TiddlyWiki 
on-and-off for a few years with Classic and TW5 from a fairly strict 
end-user perspective while only messing with stylesheets and others' 
plugins. Over the last year I've started trying to understand more of the 
program beyond just entering and organizing notes: using filters and macros 
to customize how tiddlers' information is displayed.

*Is the book organized effectively?*
I think it is. The book was easy to get an overview of when I started and 
was comfortable to work through and feel like I was building steadily on 
the information. I can't speak for a complete TW noob, and I''m glad to 
have started getting under the hood on my own before the book was released 
so that most of the concepts were not foreign to me.

*What parts have you read/worked through?*
I've followed along through Chapter 7. Javascript macros and Node.js is 
above my ability, and my needs, at this point. This includes the text, 
exercises, and take-aways.

*How have you been using the book? *
I read the book through from the start and followed along with an empty 
wiki to work through the exercises. After finishing as far as I wanted, I 
started trying to expand on your creation to start adding additional 
customization for practice.I would also experiment with my normal working 
wiki to incorporate some of the content (your simple take on the 
bi-directional links was an example that was added and tweaked for my own 
wiki).

*Have you done some of the exercises and flashcards? Do they work?*
I've through all the chapter exercises and some of the Supplemental 
exercises. I was reviewing with the Take-aways for a few weeks regularly. I 
do believe they have helped to cement some ideas for me.

*How have your TiddlyWiki skills improved, if they have?*
I'm now much more comfortable diving into the Tiddlywiki.com documentation 
for widgets and filter operators after going through the book. I've been 
able to start solving my own problems and have more of a chance to wrap my 
head around some of the problems others have presented in this forum. I've 
started building some of my own customizations to get what I want done 
instead of just hoping I can find someone else's version online already 
made.

*Any other thoughts?*
I'm currently working on my own Project Manager (some inspiration has come 
from the Projectify project) as a way to put more of the book's teaching in 
practice. It may not ever reach a publishable state, but I'm making 
something that I can see myself using regularly. I would not be able to 
have gotten this far without the knowledge gained from working through a 
structured book with concrete knowledge and practical examples to follow 
along with. 

On Wednesday, July 21, 2021 at 6:56:56 AM UTC-7 Soren Bjornstad wrote:

> 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/20e52e18-cd81-4ad9-9760-ec40566acf38n%40googlegroups.com.

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

well, Saq releases faster than I can type.

@walt again: can you confirm that doing these steps directly on Streams'
page work for you?


   1. drag the streams-fusion plugin from
   http://fastfreddy.gitlab.io/streams-fusion/ onto
   https://saqimtiaz.github.io/streams/ and install
   2. (removed -> thanks Saq!)

when I try (from work), I get the merge icon at the bottom of the tiddlers
that contain nodes



On Wed, 21 Jul 2021 at 14:57, Frédéric Demers  wrote:

> @walt again: can you confirm that doing these steps direclty on Streams'
> page work for you?
>
>
>1. drag teh streams-fusion plugin from
>http://fastfreddy.gitlab.io/streams-fusion/ onto
>https://saqimtiaz.github.io/streams/ and install
>2. move the Streams-fusion shadow tiddler
>$:/plugins/phiv/streams-fusion/fuse-button
>
> 
>  out
>of the shadows by editing it and saving it
>
> when I try (from work), I get the merge icon at the bottom of the tiddlers
> that contain nodes
>
>
> On Wed, 21 Jul 2021 at 14:49, Frédéric Demers 
> wrote:
>
>> @walt; hmm I'll have to experiment a bit more this evening. I have not
>> tried to run both Jan and mine in parallel, though I will. my next version
>> will have a different icon. I found a nice one on flaticon.
>>
>> Streams 1.2.22 is a future version, tongue-in-cheek, based on the github
>> issue I put in at Saq's request
>> https://github.com/saqimtiaz/streams/issues/30
>> In the meantime, maybe try adjusting the filter in Stream's
>> $:/plugins/sq/streams/nodes-list-template tiddler as per the github
>> issue recommendation and see if that helps. Failing that, there may be
>> something else I am overlooking.
>>
>> On Wed, 21 Jul 2021 at 13:40, ludwa6  wrote:
>>
>>> Hey @Fred: I've tried to install in my desktop TW instance, and am
>>> having some trouble.  What i did was:
>>>
>>>1. Installed your plugin (it's there and active, according to
>>>control panel);
>>>2. Upgraded my Streams plugin from v1.2.19 to 1.2.22 (/notetoself:
>>>must keep closer tabs on Saq's developments!);
>>>3. Moved the Streams-fusion shadow tiddler
>>>$:/plugins/phiv/streams-fusion/fuse-button
>>>
>>> 
>>>  out
>>>of the shadows by editing it and saving it.
>>>
>>> After each of these steps i saved and reloaded... And still i have just
>>> one of those neat flatten icons below my Streams, which opens Jan's
>>> streams-to-text modal instead of yours when i click on it.
>>> NB: i do also have Relink v2.0.0 installed, so it seems i have the
>>> dependencies covered.
>>> Now i'm wondering if these steps need to be taken in a different order?
>>> or if there is in fact some interference between your code and Jan's?
>>> (if so, i dunno what is proper dev etiquette in a case like this -but
>>> i'll do whatever admin housecleaning is needed, if given idiot-proof
>>> instructions <8-)
>>>
>>> Can you please advise?
>>>
>>> /walt
>>>
>>> On Wednesday, July 21, 2021 at 2:42:05 PM UTC+1 fred@gmail.com
>>> wrote:
>>>
 Hi Walt, thanks for the kind words.

 The only side effect of running both in parallel would be the
 appearance of two identical buttons that don't behave the same way... (I
 think)
 This problem could easily be avoided if I used a different icon, but I
 am not super creative and Jan's icon is just perfect .

 The plugin does not do any house-cleaning; that would be rude, would it
 not?



 On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:

> Nice job, @Fred; it renders outlines from Streams not only faithfully,
> but beautifully!
>
> One question, before i install this in my primary desktop wiki: you
> say in your Credits that it borrows from -and is incompatible with- Jan's
> streams-to-text addon ... Does this mean i
> should first remove the several bits that make up that addon before
> installing streams-fusion plugin?  Or does your plugin do its own proper
> house-cleaning?
>
> /walt
>
> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com
> wrote:
>
>> ok, here's a beta streams-fusion addon:
>> https://fastfreddy.gitlab.io/streams-fusion/
>> please note the troubleshooting step is required until the next
>> Streams release; beta users beware
>>
> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "TiddlyWiki" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> tiddlywiki+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>>

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

Streams 1.2.22 is now live and should allow other plugins to add buttons at 
the end of a stream.

-- 
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/5467a988-6882-40b9-9408-7a942247085fn%40googlegroups.com.

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

@walt again: can you confirm that doing these steps direclty on Streams'
page work for you?


   1. drag teh streams-fusion plugin from
   http://fastfreddy.gitlab.io/streams-fusion/ onto
   https://saqimtiaz.github.io/streams/ and install
   2. move the Streams-fusion shadow tiddler
   $:/plugins/phiv/streams-fusion/fuse-button
   

out
   of the shadows by editing it and saving it

when I try (from work), I get the merge icon at the bottom of the tiddlers
that contain nodes


On Wed, 21 Jul 2021 at 14:49, Frédéric Demers  wrote:

> @walt; hmm I'll have to experiment a bit more this evening. I have not
> tried to run both Jan and mine in parallel, though I will. my next version
> will have a different icon. I found a nice one on flaticon.
>
> Streams 1.2.22 is a future version, tongue-in-cheek, based on the github
> issue I put in at Saq's request
> https://github.com/saqimtiaz/streams/issues/30
> In the meantime, maybe try adjusting the filter in Stream's
> $:/plugins/sq/streams/nodes-list-template tiddler as per the github issue
> recommendation and see if that helps. Failing that, there may be something
> else I am overlooking.
>
> On Wed, 21 Jul 2021 at 13:40, ludwa6  wrote:
>
>> Hey @Fred: I've tried to install in my desktop TW instance, and am having
>> some trouble.  What i did was:
>>
>>1. Installed your plugin (it's there and active, according to control
>>panel);
>>2. Upgraded my Streams plugin from v1.2.19 to 1.2.22 (/notetoself:
>>must keep closer tabs on Saq's developments!);
>>3. Moved the Streams-fusion shadow tiddler
>>$:/plugins/phiv/streams-fusion/fuse-button
>>
>> 
>>  out
>>of the shadows by editing it and saving it.
>>
>> After each of these steps i saved and reloaded... And still i have just
>> one of those neat flatten icons below my Streams, which opens Jan's
>> streams-to-text modal instead of yours when i click on it.
>> NB: i do also have Relink v2.0.0 installed, so it seems i have the
>> dependencies covered.
>> Now i'm wondering if these steps need to be taken in a different order?
>> or if there is in fact some interference between your code and Jan's?
>> (if so, i dunno what is proper dev etiquette in a case like this -but
>> i'll do whatever admin housecleaning is needed, if given idiot-proof
>> instructions <8-)
>>
>> Can you please advise?
>>
>> /walt
>>
>> On Wednesday, July 21, 2021 at 2:42:05 PM UTC+1 fred@gmail.com wrote:
>>
>>> Hi Walt, thanks for the kind words.
>>>
>>> The only side effect of running both in parallel would be the appearance
>>> of two identical buttons that don't behave the same way... (I think)
>>> This problem could easily be avoided if I used a different icon, but I
>>> am not super creative and Jan's icon is just perfect .
>>>
>>> The plugin does not do any house-cleaning; that would be rude, would it
>>> not?
>>>
>>>
>>>
>>> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>>>
 Nice job, @Fred; it renders outlines from Streams not only faithfully,
 but beautifully!

 One question, before i install this in my primary desktop wiki: you say
 in your Credits that it borrows from -and is incompatible with- Jan's
 streams-to-text addon ... Does this mean i
 should first remove the several bits that make up that addon before
 installing streams-fusion plugin?  Or does your plugin do its own proper
 house-cleaning?

 /walt

 On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com
 wrote:

> ok, here's a beta streams-fusion addon:
> https://fastfreddy.gitlab.io/streams-fusion/
> please note the troubleshooting step is required until the next
> Streams release; beta users beware
>
 --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/1d281b7c-c2de-4aaf-93e1-c752dd4fdb8fn%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/CAAY2DnPBkM6WEH9jUE18OtMh__2RH4h%3D3RBXKz1OThvAUm0Erw%40mail.gmail.com.

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

@walt; hmm I'll have to experiment a bit more this evening. I have not
tried to run both Jan and mine in parallel, though I will. my next version
will have a different icon. I found a nice one on flaticon.

Streams 1.2.22 is a future version, tongue-in-cheek, based on the github
issue I put in at Saq's request
https://github.com/saqimtiaz/streams/issues/30
In the meantime, maybe try adjusting the filter in Stream's
$:/plugins/sq/streams/nodes-list-template tiddler as per the github issue
recommendation and see if that helps. Failing that, there may be something
else I am overlooking.

On Wed, 21 Jul 2021 at 13:40, ludwa6  wrote:

> Hey @Fred: I've tried to install in my desktop TW instance, and am having
> some trouble.  What i did was:
>
>1. Installed your plugin (it's there and active, according to control
>panel);
>2. Upgraded my Streams plugin from v1.2.19 to 1.2.22 (/notetoself:
>must keep closer tabs on Saq's developments!);
>3. Moved the Streams-fusion shadow tiddler
>$:/plugins/phiv/streams-fusion/fuse-button
>
> 
>  out
>of the shadows by editing it and saving it.
>
> After each of these steps i saved and reloaded... And still i have just
> one of those neat flatten icons below my Streams, which opens Jan's
> streams-to-text modal instead of yours when i click on it.
> NB: i do also have Relink v2.0.0 installed, so it seems i have the
> dependencies covered.
> Now i'm wondering if these steps need to be taken in a different order? or
> if there is in fact some interference between your code and Jan's?
> (if so, i dunno what is proper dev etiquette in a case like this -but i'll
> do whatever admin housecleaning is needed, if given idiot-proof
> instructions <8-)
>
> Can you please advise?
>
> /walt
>
> On Wednesday, July 21, 2021 at 2:42:05 PM UTC+1 fred@gmail.com wrote:
>
>> Hi Walt, thanks for the kind words.
>>
>> The only side effect of running both in parallel would be the appearance
>> of two identical buttons that don't behave the same way... (I think)
>> This problem could easily be avoided if I used a different icon, but I am
>> not super creative and Jan's icon is just perfect .
>>
>> The plugin does not do any house-cleaning; that would be rude, would it
>> not?
>>
>>
>>
>> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>>
>>> Nice job, @Fred; it renders outlines from Streams not only faithfully,
>>> but beautifully!
>>>
>>> One question, before i install this in my primary desktop wiki: you say
>>> in your Credits that it borrows from -and is incompatible with- Jan's
>>> streams-to-text addon ... Does this mean i
>>> should first remove the several bits that make up that addon before
>>> installing streams-fusion plugin?  Or does your plugin do its own proper
>>> house-cleaning?
>>>
>>> /walt
>>>
>>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com
>>> wrote:
>>>
 ok, here's a beta streams-fusion addon:
 https://fastfreddy.gitlab.io/streams-fusion/
 please note the troubleshooting step is required until the next Streams
 release; beta users beware

>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/1d281b7c-c2de-4aaf-93e1-c752dd4fdb8fn%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/CAAY2DnM%3DC%2BKt-ipsO2i32bOqf62gLH9nw0CGCva_AeWT4Jy62w%40mail.gmail.com.

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

@Mark S

Is  $:/config/RelinkOnRename set to yes?

Streams does add configuration for Relink to act on the stream-list field:
[image: Screenshot 2021-07-21 204538.png]

On Wednesday, July 21, 2021 at 7:35:24 PM UTC+2 Mark S. wrote:

> Trying streams. I notice that when I change the name of a tiddler, it 
> drops out of the original list, apparently because *relink* doesn't 
> operate on the streams-list field. Is there a tweak to fix that?
>
> On Wednesday, July 21, 2021 at 7:46:03 AM UTC-7 fred@gmail.com wrote:
>
>> I think I'll go ahead and change my icon in my next release for users who 
>> may want to use both. 
>> Would I get away with just changing the colour? Any SVG artist out there?
>>
>>
>> On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:
>>
>>> Hi Walt, thanks for the kind words.
>>>
>>> The only side effect of running both in parallel would be the appearance 
>>> of two identical buttons that don't behave the same way... (I think)
>>> This problem could easily be avoided if I used a different icon, but I 
>>> am not super creative and Jan's icon is just perfect .
>>>
>>> The plugin does not do any house-cleaning; that would be rude, would it 
>>> not?
>>>
>>>
>>>
>>> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>>>
 Nice job, @Fred; it renders outlines from Streams not only faithfully, 
 but beautifully! 

 One question, before i install this in my primary desktop wiki: you say 
 in your Credits that it borrows from -and is incompatible with- Jan's 
 streams-to-text addon ... Does this mean i 
 should first remove the several bits that make up that addon before 
 installing streams-fusion plugin?  Or does your plugin do its own proper 
 house-cleaning?

 /walt

 On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
 wrote:

> ok, here's a beta streams-fusion addon: 
> https://fastfreddy.gitlab.io/streams-fusion/
> please note the troubleshooting step is required until the next 
> Streams release; beta users beware
>
> very open to constructive feedback; and/or different ways of shipping 
> such as rolled in the Streams plugin itself if it is good enough.
>
> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>
>> That is definitely an oversight from when I added that at Jan's 
>> request. If you open an issue on Github, it will be resolved for the 
>> next 
>> release.
>>
>> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com 
>> wrote:
>>
>>> @saq
>>> quick question: am trying to package my addon, am a bit of a newbie 
>>> unfortunately. 
>>> is it possible we need to modify this line (bold insert)
>>> <$list 
>>> filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
>>> variable="btnTiddler">
>>>
>>> in $:/plugins/sq/streams/nodes-list-template ?
>>> otherwise, it feels like my new button does not take when it is 
>>> contained within a plugineven with the $:/tags/streams/root-buttons 
>>> tag 
>>>
>>> thanks much...
>>>
>>> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  
>>> wrote:
>>>
 a quick update to everyone;

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

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

 Cheers

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

> with capture:
>
> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers  
> wrote:
>
>> nevermind, I think I solved it at least, significant progress
>>
>> here's the wikitext for the challenging nodes; renders pretty 
>> well:
>>
>> * 
>>
>> ''Streams'' uses the following tiddler fields to maintain the 
>> structure of a stream:
>>
>> * each node tiddler has a field `stream-type`
>> * each node that has children, contains their titles in a list in 
>> the field `stream-list`
>> * each node that has a parent, contains the parent's title in the 
>> field `parent`
>>
>> ''You can manipulate these tiddlers just as you would any other 
>> tiddlers, with filters and list and action widgets''
>>
>> 
>> * To make it easier to work with Streams tiddlers and their 
>> nodes, two filters have been introduced. See

[tw5] Re: NoteTaking in Streams



On Thursday, July 15, 2021 at 10:22:33 AM UTC-7 ludwa6 wrote:

> @Saq: As shared in another post 
>  i've 
> been too busy farming lately to think about this -but when i do get a 
> chanc, the focus Q is: how can i use this software to simplify the 
> crazy-making challenge of keeping track of all my crops and animals and 
> machines and markets and all the other moving targets there are swirling 
> about the complex open dynamical ecosystem that is the farm -this one, or 
> any other.
>
>
A classic systems analysis approach would  get you to that objective. 
Collect or list all your inputs (documents, sheets, etc.) and all your 
desired outputs. Create a database structure that relates all the bits of 
information (TW can emulate a database if you think of Tags as being 
"tables") in a formal manner. Write an app (probably a series of special 
tiddlers and macros) in TW that can be used to input your source 
information and creates the output producibles (reports, CSV files, etc.)  
I doubt any simple note-taking software can get you to your unified goal 
without some sort of conscious design process 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/db62c467-c9bc-4677-98b6-7a921613084cn%40googlegroups.com.

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

@Mark: probably want the
https://flibbles.github.io/tw5-relink/#%24%3A%2Fplugins%2Fflibbles%2Frelink-titles
add on also.

On Wed, 21 Jul 2021 at 13:35, 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> Trying streams. I notice that when I change the name of a tiddler, it
> drops out of the original list, apparently because *relink* doesn't
> operate on the streams-list field. Is there a tweak to fix that?
>
> On Wednesday, July 21, 2021 at 7:46:03 AM UTC-7 fred@gmail.com wrote:
>
>> I think I'll go ahead and change my icon in my next release for users who
>> may want to use both.
>> Would I get away with just changing the colour? Any SVG artist out there?
>>
>>
>> On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:
>>
>>> Hi Walt, thanks for the kind words.
>>>
>>> The only side effect of running both in parallel would be the appearance
>>> of two identical buttons that don't behave the same way... (I think)
>>> This problem could easily be avoided if I used a different icon, but I
>>> am not super creative and Jan's icon is just perfect .
>>>
>>> The plugin does not do any house-cleaning; that would be rude, would it
>>> not?
>>>
>>>
>>>
>>> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>>>
 Nice job, @Fred; it renders outlines from Streams not only faithfully,
 but beautifully!

 One question, before i install this in my primary desktop wiki: you say
 in your Credits that it borrows from -and is incompatible with- Jan's
 streams-to-text addon ... Does this mean i
 should first remove the several bits that make up that addon before
 installing streams-fusion plugin?  Or does your plugin do its own proper
 house-cleaning?

 /walt

 On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com
 wrote:

> ok, here's a beta streams-fusion addon:
> https://fastfreddy.gitlab.io/streams-fusion/
> please note the troubleshooting step is required until the next
> Streams release; beta users beware
>
> very open to constructive feedback; and/or different ways of shipping
> such as rolled in the Streams plugin itself if it is good enough.
>
> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>
>> That is definitely an oversight from when I added that at Jan's
>> request. If you open an issue on Github, it will be resolved for the next
>> release.
>>
>> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com
>> wrote:
>>
>>> @saq
>>> quick question: am trying to package my addon, am a bit of a newbie
>>> unfortunately.
>>> is it possible we need to modify this line (bold insert)
>>> <$list 
>>> filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]"
>>> variable="btnTiddler">
>>>
>>> in $:/plugins/sq/streams/nodes-list-template ?
>>> otherwise, it feels like my new button does not take when it is
>>> contained within a plugineven with the $:/tags/streams/root-buttons
>>> tag
>>>
>>> thanks much...
>>>
>>> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers 
>>> wrote:
>>>
 a quick update to everyone;

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

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

 Cheers

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

> with capture:
>
> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers 
> wrote:
>
>> nevermind, I think I solved it at least, significant progress
>>
>> here's the wikitext for the challenging nodes; renders pretty
>> well:
>>
>> * 
>>
>> ''Streams'' uses the following tiddler fields to maintain the
>> structure of a stream:
>>
>> * each node tiddler has a field `stream-type`
>> * each node that has children, contains their titles in a list in
>> the field `stream-list`
>> * each node that has a parent, contains the parent's title in the
>> field `parent`
>>
>> ''You can manipulate these tiddlers just as you would any other
>> tiddlers, with filters and list and action widgets''
>>
>> 
>> * To make it easier to work with Streams tiddlers and their
>> nodes, two filters have been introduced. See [[Streams 0.2
>> improvements/Filters]]
>> * 
>>

[tw5] Re: Excising Large Outlines in TW

The official slicer edition does pretty much what you 
describe https://tiddlywiki.com/editions/text-slicer/ .
But it uses a complicated relationship between the resulting tiddlers that 
may be difficult to manipulate.

Notowritey (https://marxsal.github.io/various/notowritey.html) allows you 
to split large texts using a regular expression. You can then manipulate 
items into a hierarchical arrangement in a manner similar to a regular 
outliner. The relationship is based on simple listing and tagging.

I would imagine for a systems approach, you would have to add a great deal 
more of material. What I remember about chemistry is that they already give 
you too much material to remember and often assume you are familiar with 
processes and techniques that you have never encountered anywhere. As if 
someone just ripped pages out of your textbook and threw them away. Trying 
to see how you could fit MORE into the curriculum seems somewhat unkind.

Another Mark

On Wednesday, July 21, 2021 at 10:06:42 AM UTC-7 mark.cu...@gmail.com wrote:

> I have been using Soren’s Grok TiddlyWiki and his Zettelkasten shell over 
> the last several weeks. Most of this time has been just getting stuff into 
> TW and seeing what happens (or doesn't and trying to figure out why). I 
> have not spent any time creating, connecting, etc.. The product of my work 
> thus far is here.
>
> I have two large outlines (GeneralChemistryACCMOutline and 
> OrganicChemistryACCMOutline) that delineate anchoring concept content maps 
>  for most of the 
> undergraduate chemistry I teach. The hierarchy of these outlines is 
> identical at Level 1 (Big Ideas) and Level 2 (Enduring Understandings) and 
> differ at Level 3 (Subdisciplinary Articulations) and Level 4 (Content 
> Details).
>
> I need to excise these outlines and then add open educational resources 
> (text, links to videos, images, and simulations, exercises, etc.) to the 
> resulting tiddlers.
>
> I am interested in your thoughts on how I might excise these outlines in a 
> (unique?) way that leverages TW’s utility/flexibility as a 
> content-management system considering:
>
>1. The order of Level 1 Big Ideas is consistent with the sequence of 
>instruction.
>2. I would like to somehow leverage TW and the connected, context-free 
>facts derived from these outlines to move away from a reductionist 
> approach 
>to teaching and learning to a systems approach 
> to teaching and 
>learning. 
>3. I do not yet know specifically how I am going to use this resource 
>in a teaching setting.
>4. I am new to TW…
>
> Thanks for your help.
>
> Mark
>

-- 
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/50d34cab-2ada-4414-95f9-9244e4338a07n%40googlegroups.com.

[tw5] Re: Excising Large Outlines in TW

2021-07-21 Thread Mark Cubberley

My apologies. A cut-and-paste error compromised a link in my original post. 
My public TW is here 
 (https://markcubberley.github.io).

On Wednesday, July 21, 2021 at 1:06:42 PM UTC-4 Mark Cubberley wrote:

> I have been using Soren’s Grok TiddlyWiki and his Zettelkasten shell over 
> the last several weeks. Most of this time has been just getting stuff into 
> TW and seeing what happens (or doesn't and trying to figure out why). I 
> have not spent any time creating, connecting, etc.. The product of my work 
> thus far is here.
>
> I have two large outlines (GeneralChemistryACCMOutline and 
> OrganicChemistryACCMOutline) that delineate anchoring concept content maps 
>  for most of the 
> undergraduate chemistry I teach. The hierarchy of these outlines is 
> identical at Level 1 (Big Ideas) and Level 2 (Enduring Understandings) and 
> differ at Level 3 (Subdisciplinary Articulations) and Level 4 (Content 
> Details).
>
> I need to excise these outlines and then add open educational resources 
> (text, links to videos, images, and simulations, exercises, etc.) to the 
> resulting tiddlers.
>
> I am interested in your thoughts on how I might excise these outlines in a 
> (unique?) way that leverages TW’s utility/flexibility as a 
> content-management system considering:
>
>1. The order of Level 1 Big Ideas is consistent with the sequence of 
>instruction.
>2. I would like to somehow leverage TW and the connected, context-free 
>facts derived from these outlines to move away from a reductionist 
> approach 
>to teaching and learning to a systems approach 
> to teaching and 
>learning. 
>3. I do not yet know specifically how I am going to use this resource 
>in a teaching setting.
>4. I am new to TW…
>
> Thanks for your help.
>
> Mark
>

-- 
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/be235a6a-0ee6-4a40-b8ab-49fc08988c14n%40googlegroups.com.

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

2021-07-21 Thread ludwa6

Hey @Fred: I've tried to install in my desktop TW instance, and am having 
some trouble.  What i did was:

   1. Installed your plugin (it's there and active, according to control 
   panel);
   2. Upgraded my Streams plugin from v1.2.19 to 1.2.22 (/notetoself: must 
   keep closer tabs on Saq's developments!);
   3. Moved the Streams-fusion shadow tiddler 
   $:/plugins/phiv/streams-fusion/fuse-button 

 out 
   of the shadows by editing it and saving it.

After each of these steps i saved and reloaded... And still i have just one 
of those neat flatten icons below my Streams, which opens Jan's 
streams-to-text modal instead of yours when i click on it.
NB: i do also have Relink v2.0.0 installed, so it seems i have the 
dependencies covered.
Now i'm wondering if these steps need to be taken in a different order? or 
if there is in fact some interference between your code and Jan's?
(if so, i dunno what is proper dev etiquette in a case like this -but i'll 
do whatever admin housecleaning is needed, if given idiot-proof 
instructions <8-)

Can you please advise?

/walt

On Wednesday, July 21, 2021 at 2:42:05 PM UTC+1 fred@gmail.com wrote:

> Hi Walt, thanks for the kind words.
>
> The only side effect of running both in parallel would be the appearance 
> of two identical buttons that don't behave the same way... (I think)
> This problem could easily be avoided if I used a different icon, but I am 
> not super creative and Jan's icon is just perfect .
>
> The plugin does not do any house-cleaning; that would be rude, would it 
> not?
>
>
>
> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>
>> Nice job, @Fred; it renders outlines from Streams not only faithfully, 
>> but beautifully! 
>>
>> One question, before i install this in my primary desktop wiki: you say 
>> in your Credits that it borrows from -and is incompatible with- Jan's 
>> streams-to-text addon ... Does this mean i 
>> should first remove the several bits that make up that addon before 
>> installing streams-fusion plugin?  Or does your plugin do its own proper 
>> house-cleaning?
>>
>> /walt
>>
>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
>> wrote:
>>
>>> ok, here's a beta streams-fusion addon: 
>>> https://fastfreddy.gitlab.io/streams-fusion/
>>> please note the troubleshooting step is required until the next Streams 
>>> release; beta users beware
>>>
>>

-- 
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/1d281b7c-c2de-4aaf-93e1-c752dd4fdb8fn%40googlegroups.com.

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

Trying streams. I notice that when I change the name of a tiddler, it drops 
out of the original list, apparently because *relink* doesn't operate on 
the streams-list field. Is there a tweak to fix that?

On Wednesday, July 21, 2021 at 7:46:03 AM UTC-7 fred@gmail.com wrote:

> I think I'll go ahead and change my icon in my next release for users who 
> may want to use both. 
> Would I get away with just changing the colour? Any SVG artist out there?
>
>
> On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:
>
>> Hi Walt, thanks for the kind words.
>>
>> The only side effect of running both in parallel would be the appearance 
>> of two identical buttons that don't behave the same way... (I think)
>> This problem could easily be avoided if I used a different icon, but I am 
>> not super creative and Jan's icon is just perfect .
>>
>> The plugin does not do any house-cleaning; that would be rude, would it 
>> not?
>>
>>
>>
>> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>>
>>> Nice job, @Fred; it renders outlines from Streams not only faithfully, 
>>> but beautifully! 
>>>
>>> One question, before i install this in my primary desktop wiki: you say 
>>> in your Credits that it borrows from -and is incompatible with- Jan's 
>>> streams-to-text addon ... Does this mean i 
>>> should first remove the several bits that make up that addon before 
>>> installing streams-fusion plugin?  Or does your plugin do its own proper 
>>> house-cleaning?
>>>
>>> /walt
>>>
>>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
>>> wrote:
>>>
 ok, here's a beta streams-fusion addon: 
 https://fastfreddy.gitlab.io/streams-fusion/
 please note the troubleshooting step is required until the next Streams 
 release; beta users beware

 very open to constructive feedback; and/or different ways of shipping 
 such as rolled in the Streams plugin itself if it is good enough.

 On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:

> That is definitely an oversight from when I added that at Jan's 
> request. If you open an issue on Github, it will be resolved for the next 
> release.
>
> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com 
> wrote:
>
>> @saq
>> quick question: am trying to package my addon, am a bit of a newbie 
>> unfortunately. 
>> is it possible we need to modify this line (bold insert)
>> <$list 
>> filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
>> variable="btnTiddler">
>>
>> in $:/plugins/sq/streams/nodes-list-template ?
>> otherwise, it feels like my new button does not take when it is 
>> contained within a plugineven with the $:/tags/streams/root-buttons 
>> tag 
>>
>> thanks much...
>>
>> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  
>> wrote:
>>
>>> a quick update to everyone;
>>>
>>> I am making steady progress on packaging this merging solution, 
>>> hoping to release as a Streams plugin addon. I have repurposed the 
>>> button 
>>> from https://szen.io/stream/. I now have it also working as a 
>>> Streams context menu, with keyboard shortcuts, and it can export 
>>> sub-trees 
>>> correctly by adjusting the depth levels of the bulleted/numbered lists.
>>>
>>> A few ideas I am going to try to roll in and release a beta by the 
>>> end of this week
>>>
>>> Cheers
>>>
>>> On Sat, 17 Jul 2021 at 09:06, Frédéric Demers  
>>> wrote:
>>>
 with capture:

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

> nevermind, I think I solved it at least, significant progress
>
> here's the wikitext for the challenging nodes; renders pretty well:
>
> * 
>
> ''Streams'' uses the following tiddler fields to maintain the 
> structure of a stream:
>
> * each node tiddler has a field `stream-type`
> * each node that has children, contains their titles in a list in 
> the field `stream-list`
> * each node that has a parent, contains the parent's title in the 
> field `parent`
>
> ''You can manipulate these tiddlers just as you would any other 
> tiddlers, with filters and list and action widgets''
>
> 
> * To make it easier to work with Streams tiddlers and their nodes, 
> two filters have been introduced. See [[Streams 0.2 
> improvements/Filters]]
> * 
>
> This is an example of a button that can export the content of the 
> nodes of a tiddler whose title is in the variable `myTiddler` and 
> save the 
> combined text to a single tiddler:
>
> ```
> <$button> save to a single tiddler
> <$vars lb="

[tw5] Re: Excising Large Outlines in TW

2021-07-21 Thread David Gifford

I doubt this fully addresses your question, but just so you are aware: my 
new Subsume plugin allows you to excise items as both links and detail 
elements, and thus create an outline in which you can view any number of 
levels from the top level, or "zoom in" to any level using the link. There 
is also a video tutorial. https://giffmex.org/gifts/subsume.html

On Wednesday, July 21, 2021 at 1:06:42 PM UTC-4 mark.cu...@gmail.com wrote:

> I have been using Soren’s Grok TiddlyWiki and his Zettelkasten shell over 
> the last several weeks. Most of this time has been just getting stuff into 
> TW and seeing what happens (or doesn't and trying to figure out why). I 
> have not spent any time creating, connecting, etc.. The product of my work 
> thus far is here.
>
> I have two large outlines (GeneralChemistryACCMOutline and 
> OrganicChemistryACCMOutline) that delineate anchoring concept content maps 
>  for most of the 
> undergraduate chemistry I teach. The hierarchy of these outlines is 
> identical at Level 1 (Big Ideas) and Level 2 (Enduring Understandings) and 
> differ at Level 3 (Subdisciplinary Articulations) and Level 4 (Content 
> Details).
>
> I need to excise these outlines and then add open educational resources 
> (text, links to videos, images, and simulations, exercises, etc.) to the 
> resulting tiddlers.
>
> I am interested in your thoughts on how I might excise these outlines in a 
> (unique?) way that leverages TW’s utility/flexibility as a 
> content-management system considering:
>
>1. The order of Level 1 Big Ideas is consistent with the sequence of 
>instruction.
>2. I would like to somehow leverage TW and the connected, context-free 
>facts derived from these outlines to move away from a reductionist 
> approach 
>to teaching and learning to a systems approach 
> to teaching and 
>learning. 
>3. I do not yet know specifically how I am going to use this resource 
>in a teaching setting.
>4. I am new to TW…
>
> Thanks for your help.
>
> Mark
>

-- 
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/894cd22c-19b9-44d1-8682-aa7ff467728en%40googlegroups.com.

[tw5] Excising Large Outlines in TW

2021-07-21 Thread Mark Cubberley

I have been using Soren’s Grok TiddlyWiki and his Zettelkasten shell over
the last several weeks. Most of this time has been just getting stuff into
TW and seeing what happens (or doesn't and trying to figure out why). I
have not spent any time creating, connecting, etc.. The product of my work
thus far is here .

I have two large outlines (GeneralChemistryACCMOutline and
OrganicChemistryACCMOutline) that delineate anchoring concept content maps
for most of the undergraduate
chemistry I teach. The hierarchy of these outlines is identical at Level 1
(Big Ideas) and Level 2 (Enduring Understandings) and differ at Level 3
(Subdisciplinary Articulations) and Level 4 (Content Details).

I need to excise these outlines and then add open educational resources
(text, links to videos, images, and simulations, exercises, etc.) to the
resulting tiddlers.

I am interested in your thoughts on how I might excise these outlines in a
(unique?) way that leverages TW’s utility/flexibility as a
content-management system considering:

1. The order of Level 1 Big Ideas is consistent with the sequence of
instruction.
2. I would like to somehow leverage TW and the connected, context-free
facts derived from these outlines to move away from a reductionist approach
to teaching and learning to a systems approach
to teaching and
learning.
3. I do not yet know specifically how I am going to use this resource in
a teaching setting.
4. I am new to TW…

Thanks for your help.

Mark

--
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/7be2e9cb-3110-46d8-bc8e-72489d7fe79dn%40googlegroups.com.

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

TW Tones wrote:

> Have you tried post it notes in software on the desktop? even google keep 
> starts you down a path which eventually overwhelms you.. You quickly 
> discover why they (post it notes) are the wrong tool in many cases, and its 
> not because they are hand written or on paper. 
>

YOU are always a great *sport! *(Australian-English meaning intended, like 
"mateship".)

Yeah, I tested everything software & net from a to z. 
*On paper *post-it notes are much more flexible. 
That topped any computer attempt to be them. 
To me they are just sticky paper.

*A Glue-Stick will dance me to the end of paper (<-- A song)*

To be honest the Post-It (3M) of putative Fry 1974 vintage 
 kinda anticipated "chunkology" 
in nascent webology: mainly fostering the option to slice to discrete data 
small for the necessary going from paper to "data chunks." 

> If I were seeking the ultimate truth I would not use them. But it is all 
> about how we each operate and think. If you can use them effectively do it. 
> But me thinks they a very flawed.
>

RIGHT. *That actually was my point. *We STILL need some kind of OVERVIEW of 
real stratagems to begin typing into (entrusting) a computer ... *Will this 
gizmo do my need?*

Everything is flawed. Just so long as the light (eventually) gets through 
... A Crack In Everything ...  

Very 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/273e60a6-5f34-4a87-a258-e14515125af4n%40googlegroups.com.

[tw5] Re: tidders created this week

2021-07-21 Thread paulgilbert2000

Hi,

not exactly following , can you please clarify more what you mean?
On Wednesday, July 21, 2021 at 8:07:20 AM UTC+2 barro...@gmail.com wrote:

> I'm thinking of the  SO-8601 week number of year of one the date formats ( 
> https://tiddlywiki.com/#DateFormat ) which would allow working with 
> actual calendar weeks.  Does filter operators and search work with the 
> different date formats or would week number have to be an user created 
> field for the filter operators to work with.
>
> On Tuesday, July 20, 2021 at 1:48:22 PM UTC-4 mohamed...@hotmail.com 
> wrote:
>
>> Hi ,
>>
>> is it possible to list all tiddlers created this week, that would include 
>> past tiddlers  created 
>> yesterday"Monday" , tiddlers created today " Tuesday". and future 
>> tiddlers to be created in Wednesday ,Thursday and Friday.
>>
>> i know i can use something like this 
>> {{{[all[tiddlers]] :filter[get[created]compare:date:gt[20210719]]}}}
>>
>> but then the date i am comparing against is static, and will need to be 
>> changed manually every week
>>
>> I really like it , if only the date can be replaced with some kind of 
>> dynamic value that is defined as the first day of the current week
>>
>> i know there is the days operator IE , [days[-1]]  , but then again its 
>> not what i want and will also need manual adjustment every day
>>
>> is there any easy way around this ?
>>
>> thanks in advance
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f1c25504-cdef-4e5f-bf11-ed0e69fc8a6fn%40googlegroups.com.

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

I think I'll go ahead and change my icon in my next release for users who 
may want to use both. 
Would I get away with just changing the colour? Any SVG artist out there?


On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:

> Hi Walt, thanks for the kind words.
>
> The only side effect of running both in parallel would be the appearance 
> of two identical buttons that don't behave the same way... (I think)
> This problem could easily be avoided if I used a different icon, but I am 
> not super creative and Jan's icon is just perfect .
>
> The plugin does not do any house-cleaning; that would be rude, would it 
> not?
>
>
>
> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>
>> Nice job, @Fred; it renders outlines from Streams not only faithfully, 
>> but beautifully! 
>>
>> One question, before i install this in my primary desktop wiki: you say 
>> in your Credits that it borrows from -and is incompatible with- Jan's 
>> streams-to-text addon ... Does this mean i 
>> should first remove the several bits that make up that addon before 
>> installing streams-fusion plugin?  Or does your plugin do its own proper 
>> house-cleaning?
>>
>> /walt
>>
>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
>> wrote:
>>
>>> ok, here's a beta streams-fusion addon: 
>>> https://fastfreddy.gitlab.io/streams-fusion/
>>> please note the troubleshooting step is required until the next Streams 
>>> release; beta users beware
>>>
>>> very open to constructive feedback; and/or different ways of shipping 
>>> such as rolled in the Streams plugin itself if it is good enough.
>>>
>>> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>>>
 That is definitely an oversight from when I added that at Jan's 
 request. If you open an issue on Github, it will be resolved for the next 
 release.

 On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com 
 wrote:

> @saq
> quick question: am trying to package my addon, am a bit of a newbie 
> unfortunately. 
> is it possible we need to modify this line (bold insert)
> <$list 
> filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
> variable="btnTiddler">
>
> in $:/plugins/sq/streams/nodes-list-template ?
> otherwise, it feels like my new button does not take when it is 
> contained within a plugineven with the $:/tags/streams/root-buttons 
> tag 
>
> thanks much...
>
> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  
> wrote:
>
>> a quick update to everyone;
>>
>> I am making steady progress on packaging this merging solution, 
>> hoping to release as a Streams plugin addon. I have repurposed the 
>> button 
>> from https://szen.io/stream/. I now have it also working as a 
>> Streams context menu, with keyboard shortcuts, and it can export 
>> sub-trees 
>> correctly by adjusting the depth levels of the bulleted/numbered lists.
>>
>> A few ideas I am going to try to roll in and release a beta by the 
>> end of this week
>>
>> Cheers
>>
>> On Sat, 17 Jul 2021 at 09:06, Frédéric Demers  
>> wrote:
>>
>>> with capture:
>>>
>>> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers  
>>> wrote:
>>>
 nevermind, I think I solved it at least, significant progress

 here's the wikitext for the challenging nodes; renders pretty well:

 * 

 ''Streams'' uses the following tiddler fields to maintain the 
 structure of a stream:

 * each node tiddler has a field `stream-type`
 * each node that has children, contains their titles in a list in 
 the field `stream-list`
 * each node that has a parent, contains the parent's title in the 
 field `parent`

 ''You can manipulate these tiddlers just as you would any other 
 tiddlers, with filters and list and action widgets''

 
 * To make it easier to work with Streams tiddlers and their nodes, 
 two filters have been introduced. See [[Streams 0.2 
 improvements/Filters]]
 * 

 This is an example of a button that can export the content of the 
 nodes of a tiddler whose title is in the variable `myTiddler` and save 
 the 
 combined text to a single tiddler:

 ```
 <$button> save to a single tiddler
 <$vars lb="

 ">
 <$action-setfield $tiddler="report" text={{{ 
 [get-stream-nodes[]] 
  :reduce[get[text]addprefixaddprefix] }}}/>
 
 
 ```
 Note that this disregards the node hierarchy.
 * 

 Similarly to export the combined text of the nodes as HTML you can 
 use the `<$wikify>` widget:

 ```

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

Ha Ha,

A photo frame may have being better and cheaper.

Have you tried post it notes in software on the desktop? even google keep 
starts you down a path which eventually overwhelms you.. You quickly 
discover why they (post it notes) are the wrong tool in many cases, and its 
not because they are hand written or on paper. If I were seeking the 
ultimate truth I would not use them. But it is all about how we each 
operate and think. If you can use them effectively do it. But me thinks 
they a very flawed.

Where is my reference to the last time I hade a rant about post it notes?, 
is it there, or over there, could it have fallen off, dam those cheap post 
it notes, or did someone come in to my room and take it, am I getting 
paranoid? ahh I am sitting on it, no that one is years old, and faded, dam 
those cheap pens...

but then there was tiddlywiki.

Tones

On Wednesday, 21 July 2021 at 22:35:01 UTC+10 TiddlyTweeter wrote:

> Soren & Si
>
> Regarding Old World notes ... I'm a great adherent of the imperative that 
> a computer is merely an auxiliary.
>
> For example here is a snapshot of my Luddite Computer ...
>
> [image: WIN_20210721_14_31_36_Pro.jpg]
>
> TBH, I think we actually need better ANTHROPOLOGY of actual usage of 
> systems of meaning ordering to ensure that when you go computer-typist it 
> is additive, not reductive.
>
> Merely passing thoughts ... best
> TT.
>
> On Tuesday, 20 July 2021 at 23:04:48 UTC+2 Soren Bjornstad wrote:
>
>> 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/0a00bfb3-6d30-4bd8-b43b-cef884b3fed4n%40googlegroups.com.

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

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 method 
> to make filters more sophisticated basically permit ones that allow you to 
> avoid the nested lists I used, however as stated previously dont be shy 
> using nested lists, because each level of nesting allows to generate a new 
> variable and keep the old ones in this case found-filter while keeping 
> currentTiddler from the first filter.
>
> My preference would be a shorthand method when presenting variables as a 
> parameter, in this case <> such that it is first 
> wikified rather than using the ungainly wikify widget and its need to wrap 
> the macro call. Eg a a parameter ((tabs-with-content)) or in filters 
> (tabs-with-content)
> Alternatively TiddlyWiki would detect the need for wikification of that 
> variable/macro and do it itself.
>
>
> Regards
> tones
>
>
> On Wednesday, 21 July 2021 at 22:15:12 UTC+10 Soren Bjornstad wrote:
>
>> 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

[tw5] Seeking general feedback on Grok TiddlyWiki

2021-07-21 Thread 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,

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 method 
to make filters more sophisticated basically permit ones that allow you to 
avoid the nested lists I used, however as stated previously dont be shy 
using nested lists, because each level of nesting allows to generate a new 
variable and keep the old ones in this case found-filter while keeping 
currentTiddler from the first filter.

My preference would be a shorthand method when presenting variables as a 
parameter, in this case <> such that it is first 
wikified rather than using the ungainly wikify widget and its need to wrap 
the macro call. Eg a a parameter ((tabs-with-content)) or in filters 
(tabs-with-content)
Alternatively TiddlyWiki would detect the need for wikification of that 
variable/macro and do it itself.

Regards
tones

On Wednesday, 21 July 2021 at 22:15:12 UTC+10 Soren Bjornstad wrote:

> 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

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

Hi Walt, thanks for the kind words.

The only side effect of running both in parallel would be the appearance of
two identical buttons that don't behave the same way... (I think)
This problem could easily be avoided if I used a different icon, but I am
not super creative and Jan's icon is just perfect .

The plugin does not do any house-cleaning; that would be rude, would it not?



On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:

> Nice job, @Fred; it renders outlines from Streams not only faithfully, but
> beautifully!
>
> One question, before i install this in my primary desktop wiki: you say in
> your Credits that it borrows from -and is incompatible with- Jan's
> streams-to-text addon ... Does this mean i
> should first remove the several bits that make up that addon before
> installing streams-fusion plugin?  Or does your plugin do its own proper
> house-cleaning?
>
> /walt
>
> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com wrote:
>
>> ok, here's a beta streams-fusion addon:
>> https://fastfreddy.gitlab.io/streams-fusion/
>> please note the troubleshooting step is required until the next Streams
>> release; beta users beware
>>
>> very open to constructive feedback; and/or different ways of shipping
>> such as rolled in the Streams plugin itself if it is good enough.
>>
>> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>>
>>> That is definitely an oversight from when I added that at Jan's request.
>>> If you open an issue on Github, it will be resolved for the next release.
>>>
>>> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com
>>> wrote:
>>>
 @saq
 quick question: am trying to package my addon, am a bit of a newbie
 unfortunately.
 is it possible we need to modify this line (bold insert)
 <$list filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]"
 variable="btnTiddler">

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

 thanks much...

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

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

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

2021-07-21 Thread ludwa6

Nice job, @Fred; it renders outlines from Streams not only faithfully, but 
beautifully! 

One question, before i install this in my primary desktop wiki: you say in 
your Credits that it borrows from -and is incompatible with- Jan's 
streams-to-text addon ... Does this mean i should 
first remove the several bits that make up that addon before installing 
streams-fusion plugin?  Or does your plugin do its own proper 
house-cleaning?

/walt

On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com wrote:

> ok, here's a beta streams-fusion addon: 
> https://fastfreddy.gitlab.io/streams-fusion/
> please note the troubleshooting step is required until the next Streams 
> release; beta users beware
>
> very open to constructive feedback; and/or different ways of shipping such 
> as rolled in the Streams plugin itself if it is good enough.
>
> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>
>> That is definitely an oversight from when I added that at Jan's request. 
>> If you open an issue on Github, it will be resolved for the next release.
>>
>> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com wrote:
>>
>>> @saq
>>> quick question: am trying to package my addon, am a bit of a newbie 
>>> unfortunately. 
>>> is it possible we need to modify this line (bold insert)
>>> <$list filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
>>> variable="btnTiddler">
>>>
>>> in $:/plugins/sq/streams/nodes-list-template ?
>>> otherwise, it feels like my new button does not take when it is 
>>> contained within a plugineven with the $:/tags/streams/root-buttons 
>>> tag 
>>>
>>> thanks much...
>>>
>>> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  
>>> wrote:
>>>
 a quick update to everyone;

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

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

 Cheers

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

> with capture:
>
> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers  
> wrote:
>
>> nevermind, I think I solved it at least, significant progress
>>
>> here's the wikitext for the challenging nodes; renders pretty well:
>>
>> * 
>>
>> ''Streams'' uses the following tiddler fields to maintain the 
>> structure of a stream:
>>
>> * each node tiddler has a field `stream-type`
>> * each node that has children, contains their titles in a list in the 
>> field `stream-list`
>> * each node that has a parent, contains the parent's title in the 
>> field `parent`
>>
>> ''You can manipulate these tiddlers just as you would any other 
>> tiddlers, with filters and list and action widgets''
>>
>> 
>> * To make it easier to work with Streams tiddlers and their nodes, 
>> two filters have been introduced. See [[Streams 0.2 
>> improvements/Filters]]
>> * 
>>
>> This is an example of a button that can export the content of the 
>> nodes of a tiddler whose title is in the variable `myTiddler` and save 
>> the 
>> combined text to a single tiddler:
>>
>> ```
>> <$button> save to a single tiddler
>> <$vars lb="
>>
>> ">
>> <$action-setfield $tiddler="report" text={{{ 
>> [get-stream-nodes[]] 
>>  :reduce[get[text]addprefixaddprefix] }}}/>
>> 
>> 
>> ```
>> Note that this disregards the node hierarchy.
>> * 
>>
>> Similarly to export the combined text of the nodes as HTML you can 
>> use the `<$wikify>` widget:
>>
>> ```
>> <$button> export as HTML
>> <$wikify name="text" text="""<$list 
>> filter="[get-stream-nodes[]]">
>> <$transclude mode=block/>
>> """ output="html">
>> <$action-setfield $tiddler="report" text=<>/>
>> 
>> 
>> ```
>>
>> 
>> * 
>>
>> Here is an example of a macro that can be used to export a stream 
>> using a custom HTML structure:
>>
>> ```
>> \define print-row()
>> \whitespace trim
>> <$(innerTag)$>{{!!text}}
>> <$list filter="[has[stream-list]]" variable="_NULL">
>> <$(outerTag)$>
>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>> <>
>> 
>> 
>> 
>> 
>> \end
>>
>> \define print-stream()
>> \whitespace trim
>> <$(outerTag)$>
>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>> <>
>> 
>> 
>> \end
>>
>> \define export-stream(tiddler:"" outerTag:"article" 
>> innerTag:"section")
>> \whitespace trim

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

2021-07-21 Thread 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.
>
>
> 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,

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

ok, here's a beta streams-fusion addon:
https://fastfreddy.gitlab.io/streams-fusion/
please note the troubleshooting step is required until the next Streams
release; beta users beware

very open to constructive feedback; and/or different ways of shipping such
as rolled in the Streams plugin itself if it is good enough.

On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:

> That is definitely an oversight from when I added that at Jan's request.
> If you open an issue on Github, it will be resolved for the next release.
>
> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com wrote:
>
>> @saq
>> quick question: am trying to package my addon, am a bit of a newbie
>> unfortunately.
>> is it possible we need to modify this line (bold insert)
>> <$list filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]"
>> variable="btnTiddler">
>>
>> in $:/plugins/sq/streams/nodes-list-template ?
>> otherwise, it feels like my new button does not take when it is contained
>> within a plugineven with the $:/tags/streams/root-buttons tag
>>
>> thanks much...
>>
>> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  wrote:
>>
>>> a quick update to everyone;
>>>
>>> I am making steady progress on packaging this merging solution, hoping
>>> to release as a Streams plugin addon. I have repurposed the button from
>>> https://szen.io/stream/. I now have it also working as a Streams
>>> context menu, with keyboard shortcuts, and it can export sub-trees
>>> correctly by adjusting the depth levels of the bulleted/numbered lists.
>>>
>>> A few ideas I am going to try to roll in and release a beta by the end
>>> of this week
>>>
>>> Cheers
>>>
>>> On Sat, 17 Jul 2021 at 09:06, Frédéric Demers 
>>> wrote:
>>>
 with capture:

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

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

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

That is definitely an oversight from when I added that at Jan's request. If 
you open an issue on Github, it will be resolved for the next release.

On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com wrote:

> @saq
> quick question: am trying to package my addon, am a bit of a newbie 
> unfortunately. 
> is it possible we need to modify this line (bold insert)
> <$list filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
> variable="btnTiddler">
>
> in $:/plugins/sq/streams/nodes-list-template ?
> otherwise, it feels like my new button does not take when it is contained 
> within a plugineven with the $:/tags/streams/root-buttons tag 
>
> thanks much...
>
> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  wrote:
>
>> a quick update to everyone;
>>
>> I am making steady progress on packaging this merging solution, hoping to 
>> release as a Streams plugin addon. I have repurposed the button from 
>> https://szen.io/stream/. I now have it also working as a Streams context 
>> menu, with keyboard shortcuts, and it can export sub-trees correctly by 
>> adjusting the depth levels of the bulleted/numbered lists.
>>
>> A few ideas I am going to try to roll in and release a beta by the end of 
>> this week
>>
>> Cheers
>>
>> On Sat, 17 Jul 2021 at 09:06, Frédéric Demers  wrote:
>>
>>> with capture:
>>>
>>> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers  
>>> wrote:
>>>
 nevermind, I think I solved it at least, significant progress

 here's the wikitext for the challenging nodes; renders pretty well:

 * 

 ''Streams'' uses the following tiddler fields to maintain the structure 
 of a stream:

 * each node tiddler has a field `stream-type`
 * each node that has children, contains their titles in a list in the 
 field `stream-list`
 * each node that has a parent, contains the parent's title in the field 
 `parent`

 ''You can manipulate these tiddlers just as you would any other 
 tiddlers, with filters and list and action widgets''

 
 * To make it easier to work with Streams tiddlers and their nodes, two 
 filters have been introduced. See [[Streams 0.2 improvements/Filters]]
 * 

 This is an example of a button that can export the content of the nodes 
 of a tiddler whose title is in the variable `myTiddler` and save the 
 combined text to a single tiddler:

 ```
 <$button> save to a single tiddler
 <$vars lb="

 ">
 <$action-setfield $tiddler="report" text={{{ 
 [get-stream-nodes[]] 
  :reduce[get[text]addprefixaddprefix] }}}/>
 
 
 ```
 Note that this disregards the node hierarchy.
 * 

 Similarly to export the combined text of the nodes as HTML you can use 
 the `<$wikify>` widget:

 ```
 <$button> export as HTML
 <$wikify name="text" text="""<$list 
 filter="[get-stream-nodes[]]">
 <$transclude mode=block/>
 """ output="html">
 <$action-setfield $tiddler="report" text=<>/>
 
 
 ```

 
 * 

 Here is an example of a macro that can be used to export a stream using 
 a custom HTML structure:

 ```
 \define print-row()
 \whitespace trim
 <$(innerTag)$>{{!!text}}
 <$list filter="[has[stream-list]]" variable="_NULL">
 <$(outerTag)$>
 <$list filter="[enlist{!!stream-list}is[tiddler]]">
 <>
 
 
 
 
 \end

 \define print-stream()
 \whitespace trim
 <$(outerTag)$>
 <$list filter="[enlist{!!stream-list}is[tiddler]]">
 <>
 
 
 \end

 \define export-stream(tiddler:"" outerTag:"article" innerTag:"section")
 \whitespace trim
 <$vars outerTag="$outerTag$" innerTag="$innerTag$" 
 currentTiddler="$tiddler$">
 <>
 
 \end

 ```

 Try the following:

 * `<>` to export using article and 
 section tags
 * `<>` to export 
 as a list in HTML

 If you need a copy to clipboard button it would look something like 
 this:

 ```
 <$button>
 <$wikify name="stream-html" text=<> 
 output="html" >
 <$action-sendmessage $message="tm-copy-to-clipboard" 
 $param=<>/>
 
 Copy stream to clipboard as HTML
 
 ```

 Similarly you can write recursive macros to output as just flat text 
 (with no structure or hierarchy) or wiki text list syntax (assuming you 
 have no multi-line content).

 On Sat, 17 Jul 2021 at 09:01, Saq Imtiaz  wrote:

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

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

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.


 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

[tw5] Please raise my baby (Subsume)

2021-07-21 Thread David Gifford

Hi everyone,

As many of you know, I am a pastor. The few things I have done for
TiddlyWiki have been side projects, cobbled together with what limited
knowledge I have (and with lots of help from all of you, thank you very
much!). And I have undertaken them for my own needs, and shared freely with
others when I thought them helpful. But it has never been my intention to
be a TiddlyWiki developer.

Getting to my main point, I see ways in which my latest project, Subsume,
could be more versatile, but I need to move on and USE Subsume to develop
materials, and channel my energy into other projects and other parts of my
life. If anyone would like to either adopt Subsume or create your own
copycat version and develop it more, please feel free do so. Here are the
items I see that would be valuable:

1. A control panel tab with radials or checkboxes that allow the user to
select to display or hide the link (that is, either display the link as an
asterisk, or display the link as three so it is invisible when
reading and printing, but still accessible.)

2. On the same tab, another way of choosing whether the link opens the
subsumed tiddler in edittemplate or viewtemplate mode.

3. Figure out a way for subsumes to be recognized as backlinks by
TiddlyWiki. They are currently recognized as relink references, but not as
backlinks properly.

4. A way for the details summary of subsumes to display the caption field
of a tiddler first, then the title field if there is no caption (in other
words, they should display titles in the way tabs do).

Again, my goal is to extract myself from the picture and move on, not to
ask for help. I am just identifying possibilities for the future in case
anyone would like to develop this further.

If you do develop something, let me know. Both so I can use it myself, and
so I can redirect people to your souped up version.

Thanks for your consideration!

--
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/a4dc91e6-2aed-4390-af12-66296973e31bn%40googlegroups.com.

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

ludwa6 wrote:

> Still: i find it hard to forbear from changing names to reflect changes in 
> my thinking and/or popular usage.  A constant struggle!
>

The whole PERMALINK thing is a bit of a nightmare.

A factor is "social evolution". The first book was printed in 1454 
.

The ISBN, an unique identification system for publicly printed books was 
created 
in 1966 .
Only 512 years to get that working well!

SO-CALLED "Permalinks", I think come in many different guises. 
And it IS confusing knowing what is what.

At on point there came, and now very much waning, the BLOGGER movement went 
for permanence. 
They added also copious TRACKBACKS, often mediated vis RSS and PINGS.
The thing was they evaporated, despite the intent.
>From deaths, neglect, and server non-persistence.

For longevity on permalinks there are SOME sites like IMBD that have done 
well. They assign unique UIDs to every newly RELEASED MOVIE. (Example: the 
short  Tiddlywink, which is "tt3337220" 
 in IMDB ).

The Internet Archive  is very interesting. A kind of  
"Preservation Society For The Lost" .

Regarding YOUR posts! I do think using, in TW, since we CAN do it, a UID as 
the initiation point, rather than server (or internal TW) REDIRECTS, is a 
pretty neat solution.

Just rambling thoughts
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/bedb36f3-d540-43d9-bcaf-d8a09f08abcan%40googlegroups.com.

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

cj.v...@gmail.com wrote:

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

 Right! 
What is interesting to ME is getting to the point that whatever platform 
I'm on, and wherever I be, I want ONE system that just works for FLEETING 
NOTES that will SYNCHRO to the other, other systems I'm on. 
A big advantage of a real Universal Bucket is that you have (1) one easily 
remembered method to get to it; and, (2) it becomes possible to communicate 
how to use it to newbie idiots (like me).  

At base all one needs is something BETTER than PAPER. 
It is interesting that STILL using the net is more of a tribulation than a 
simple trial.
Paper it is not!

Just thoughts
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/d760b610-9991-40e3-bb3b-8875ce82188cn%40googlegroups.com.

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

Ciao TW Tones

Tones wrote:

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

Right! 

I think you will find recent Android/Chrome very good at both VOICE and 
WRITING directly into TW.
It is actually becoming usable. At last!
Windows seems a Tad behind.

Personally I use WRITING via pen a lot now in a Chromebook directly into TW.

Side note
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/cb4d5876-208e-4217-8ba6-94b339b5f1e5n%40googlegroups.com.

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