Re: [tw5] Re: [ Streams ] : feedback and issues

[arun babu]

Thanks Saq for the reply. CP works well with the current release of TW
except for a few small bugs.

On Wed, Apr 21, 2021 at 1:21 PM Saq Imtiaz  wrote:

> There should be no issue with using command palette even if it isn't being
> developed if it works well and provides utility.
>
>  Do you have any plans of releasing the Notation Editor which you had
>> showed in one of the TW hangout videos?
>>
>
> Realistically, no. It would require a complete rewrite for which I am
> unlikely to find the time. For what little time I can devote to TW related
> matters, there are higher priority items that need attention.
>
> --
> 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/8a7bfc68-cc23-4156-a204-96e4113c4c72n%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/CABSowt0SHG4EsAm4f41hmgJQf6rMoijqm2GwWuO%2BFTLkR0xhHw%40mail.gmail.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

There should be no issue with using command palette even if it isn't being 
developed if it works well and provides utility.

 Do you have any plans of releasing the Notation Editor which you had 
> showed in one of the TW hangout videos? 
>

Realistically, no. It would require a complete rewrite for which I am 
unlikely to find the time. For what little time I can devote to TW related 
matters, there are higher priority items that need attention. 

-- 
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/8a7bfc68-cc23-4156-a204-96e4113c4c72n%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[arun babu]

Saq,

It seems like the command palette plug-in is not being actively developed. 
Do you have any plans of releasing the Notation Editor which you had showed 
in one of the TW hangout videos? 

On Wednesday, April 21, 2021 at 11:56:14 AM UTC+5:30 arun babu wrote:

> Thanks Saq. Both of them works as intended. Now I can play with those 
> codes to suit my other use cases. Your help is much appreciated.
>
> Also I have been using Relinks-Titles plug-in for sometime. It has been 
> very useful while renaming Stream root tiddler by automatically renaming 
> the stream node tiddlers also
>
> Arun.
>
> On Wednesday, April 21, 2021 at 10:48:23 AM UTC+5:30 saq.i...@gmail.com 
> wrote:
>
>> @arun I am not familiar with CommandPalette (CP), so this might be a 
>> question better asked of the responsible developer or other users of the 
>> plugin, i.e. how to trigger action strings with CP.
>>
>> You could try adding this in a tiddler tagged with $:/tags/ViewTemplate, 
>> which should make the button to create the child nodes appear after you 
>> have created a new case with CP.
>>
>> \define myactions()
>> <$vars nodeSuffixes="Pathology [[X ray findings]] Treatment"
>> root=<>
>> >
>> <$list filter="[enlist]">
>> <$action-setfield 
>> $tiddler={{{ [addprefix[/]addprefix] }}} 
>> parent=<> 
>> text={{{ [addprefix[!!]]}}} 
>> stream-type="default" />
>> 
>> <$set name="new-nodes" 
>> filter="[enlistaddprefix[/]addprefix]">
>> <$action-listops $tiddler=<> $field="stream-list" 
>> $subfilter=<>/>
>> 
>> 
>> \end
>>
>> <$list filter="[all[current]what[case]!has[stream-list]]">
>> <$button actions=<>>
>> new case
>> 
>> 
>>
>> Also depending on your workflow, the plugin RelinkTitles may be of 
>> interest to you: https://flibbles.github.io/tw5-relink/#Plugins%2FTitles
>>
>> To change the Recent Sidebar to only show the root tiddlers for each 
>> node, try editing $:/core/ui/SideBar/Recent and changing the contents to:
>>
>> <$macrocall $name="timeline" 
>> format={{$:/language/RecentChanges/DateFormat}} 
>> subfilter="get-stream-root[]"/>
>>
>> Hope this helps,
>>
>> Saq
>>
>> On Tuesday, April 20, 2021 at 11:48:20 PM UTC+2 arunn...@gmail.com wrote:
>>
>>> Hi Saq,
>>>
>>> I can understand that you might have got busy with your work. No worries.
>>>
>>> I had 4 questions.
>>>
>>> 1. I will be happy if you can help me to make this template. I tried the 
>>> code which you gave and its what I want - but how to make the new case 
>>> button or the template appear automatically in every new case tiddlers. Or 
>>> can you help to incorporate the code given into the command palette command 
>>> I created.
>>>
>>> 2. Renaming the node is fine for me, although it can be quite a work if 
>>> there a many child nodes.
>>>
>>> 3. With the filter option given in the latest beta version, issue with 
>>> exporting of a single node tree has been solved.
>>>
>>> 4. I have modified my recents tiddler to limit number of entries shown. 
>>> Still I will be happy if there is a filter to show only the stream root 
>>> tiddlers.
>>>
>>>
>>> Thanks,
>>> Arun
>>> On Monday, April 19, 2021 at 7:07:06 AM UTC+5:30 rika.s...@gmail.com 
>>> wrote:
>>>
 I just made a note to update in ~1 week. Thanks, Saq! Really 
 appreciate the time you're spending on this. 

 Best,
 Rika Sukenik 


 On Sat, Apr 17, 2021 at 12:47 AM Saq Imtiaz  wrote:

> @arun apologies for the very delayed reply, I've had a hectic last 
> couple of months and this message slipped through the cracks. Let me know 
> if these questions are still relevant and if so, we can discuss them 
> further.
>
> Saq
>
> -- 
> 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/1jTwdmq8cgI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> tiddlywiki+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/80b9ff77-260e-4ea2-94d2-2120f9fe5189n%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/547b6491-1203-4b86-a0c7-f0321cb8d0f0n%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[arun babu]

Thanks Saq. Both of them works as intended. Now I can play with those codes 
to suit my other use cases. Your help is much appreciated.

Also I have been using Relinks-Titles plug-in for sometime. It has been 
very useful while renaming Stream root tiddler by automatically renaming 
the stream node tiddlers also

Arun.

On Wednesday, April 21, 2021 at 10:48:23 AM UTC+5:30 saq.i...@gmail.com 
wrote:

> @arun I am not familiar with CommandPalette (CP), so this might be a 
> question better asked of the responsible developer or other users of the 
> plugin, i.e. how to trigger action strings with CP.
>
> You could try adding this in a tiddler tagged with $:/tags/ViewTemplate, 
> which should make the button to create the child nodes appear after you 
> have created a new case with CP.
>
> \define myactions()
> <$vars nodeSuffixes="Pathology [[X ray findings]] Treatment"
> root=<>
> >
> <$list filter="[enlist]">
> <$action-setfield 
> $tiddler={{{ [addprefix[/]addprefix] }}} 
> parent=<> 
> text={{{ [addprefix[!!]]}}} 
> stream-type="default" />
> 
> <$set name="new-nodes" 
> filter="[enlistaddprefix[/]addprefix]">
> <$action-listops $tiddler=<> $field="stream-list" 
> $subfilter=<>/>
> 
> 
> \end
>
> <$list filter="[all[current]what[case]!has[stream-list]]">
> <$button actions=<>>
> new case
> 
> 
>
> Also depending on your workflow, the plugin RelinkTitles may be of 
> interest to you: https://flibbles.github.io/tw5-relink/#Plugins%2FTitles
>
> To change the Recent Sidebar to only show the root tiddlers for each node, 
> try editing $:/core/ui/SideBar/Recent and changing the contents to:
>
> <$macrocall $name="timeline" 
> format={{$:/language/RecentChanges/DateFormat}} 
> subfilter="get-stream-root[]"/>
>
> Hope this helps,
>
> Saq
>
> On Tuesday, April 20, 2021 at 11:48:20 PM UTC+2 arunn...@gmail.com wrote:
>
>> Hi Saq,
>>
>> I can understand that you might have got busy with your work. No worries.
>>
>> I had 4 questions.
>>
>> 1. I will be happy if you can help me to make this template. I tried the 
>> code which you gave and its what I want - but how to make the new case 
>> button or the template appear automatically in every new case tiddlers. Or 
>> can you help to incorporate the code given into the command palette command 
>> I created.
>>
>> 2. Renaming the node is fine for me, although it can be quite a work if 
>> there a many child nodes.
>>
>> 3. With the filter option given in the latest beta version, issue with 
>> exporting of a single node tree has been solved.
>>
>> 4. I have modified my recents tiddler to limit number of entries shown. 
>> Still I will be happy if there is a filter to show only the stream root 
>> tiddlers.
>>
>>
>> Thanks,
>> Arun
>> On Monday, April 19, 2021 at 7:07:06 AM UTC+5:30 rika.s...@gmail.com 
>> wrote:
>>
>>> I just made a note to update in ~1 week. Thanks, Saq! Really 
>>> appreciate the time you're spending on this. 
>>>
>>> Best,
>>> Rika Sukenik 
>>>
>>>
>>> On Sat, Apr 17, 2021 at 12:47 AM Saq Imtiaz  wrote:
>>>
 @arun apologies for the very delayed reply, I've had a hectic last 
 couple of months and this message slipped through the cracks. Let me know 
 if these questions are still relevant and if so, we can discuss them 
 further.

 Saq

 -- 
 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/1jTwdmq8cgI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 tiddlywiki+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/80b9ff77-260e-4ea2-94d2-2120f9fe5189n%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/a352d7ba-2ac1-44f7-b16c-a2edfb5e1c5cn%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@arun I am not familiar with CommandPalette (CP), so this might be a 
question better asked of the responsible developer or other users of the 
plugin, i.e. how to trigger action strings with CP.

You could try adding this in a tiddler tagged with $:/tags/ViewTemplate, 
which should make the button to create the child nodes appear after you 
have created a new case with CP.

\define myactions()
<$vars nodeSuffixes="Pathology [[X ray findings]] Treatment"
root=<>
>
<$list filter="[enlist]">
<$action-setfield 
$tiddler={{{ [addprefix[/]addprefix] }}} 
parent=<> 
text={{{ [addprefix[!!]]}}} 
stream-type="default" />

<$set name="new-nodes" 
filter="[enlistaddprefix[/]addprefix]">
<$action-listops $tiddler=<> $field="stream-list" 
$subfilter=<>/>


\end

<$list filter="[all[current]what[case]!has[stream-list]]">
<$button actions=<>>
new case



Also depending on your workflow, the plugin RelinkTitles may be of interest 
to you: https://flibbles.github.io/tw5-relink/#Plugins%2FTitles

To change the Recent Sidebar to only show the root tiddlers for each node, 
try editing $:/core/ui/SideBar/Recent and changing the contents to:

<$macrocall $name="timeline" 
format={{$:/language/RecentChanges/DateFormat}} 
subfilter="get-stream-root[]"/>

Hope this helps,

Saq

On Tuesday, April 20, 2021 at 11:48:20 PM UTC+2 arunn...@gmail.com wrote:

> Hi Saq,
>
> I can understand that you might have got busy with your work. No worries.
>
> I had 4 questions.
>
> 1. I will be happy if you can help me to make this template. I tried the 
> code which you gave and its what I want - but how to make the new case 
> button or the template appear automatically in every new case tiddlers. Or 
> can you help to incorporate the code given into the command palette command 
> I created.
>
> 2. Renaming the node is fine for me, although it can be quite a work if 
> there a many child nodes.
>
> 3. With the filter option given in the latest beta version, issue with 
> exporting of a single node tree has been solved.
>
> 4. I have modified my recents tiddler to limit number of entries shown. 
> Still I will be happy if there is a filter to show only the stream root 
> tiddlers.
>
>
> Thanks,
> Arun
> On Monday, April 19, 2021 at 7:07:06 AM UTC+5:30 rika.s...@gmail.com 
> wrote:
>
>> I just made a note to update in ~1 week. Thanks, Saq! Really 
>> appreciate the time you're spending on this. 
>>
>> Best,
>> Rika Sukenik 
>>
>>
>> On Sat, Apr 17, 2021 at 12:47 AM Saq Imtiaz  wrote:
>>
>>> @arun apologies for the very delayed reply, I've had a hectic last 
>>> couple of months and this message slipped through the cracks. Let me know 
>>> if these questions are still relevant and if so, we can discuss them 
>>> further.
>>>
>>> Saq
>>>
>>> -- 
>>> 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/1jTwdmq8cgI/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> tiddlywiki+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/80b9ff77-260e-4ea2-94d2-2120f9fe5189n%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/5393f070-9b6c-4f27-84a3-67aa97ed27bdn%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[arun babu]

Hi Saq,

I can understand that you might have got busy with your work. No worries.

I had 4 questions.

1. I will be happy if you can help me to make this template. I tried the 
code which you gave and its what I want - but how to make the new case 
button or the template appear automatically in every new case tiddlers. Or 
can you help to incorporate the code given into the command palette command 
I created.

2. Renaming the node is fine for me, although it can be quite a work if 
there a many child nodes.

3. With the filter option given in the latest beta version, issue with 
exporting of a single node tree has been solved.

4. I have modified my recents tiddler to limit number of entries shown. 
Still I will be happy if there is a filter to show only the stream root 
tiddlers.


Thanks,
Arun
On Monday, April 19, 2021 at 7:07:06 AM UTC+5:30 rika.s...@gmail.com wrote:

> I just made a note to update in ~1 week. Thanks, Saq! Really 
> appreciate the time you're spending on this. 
>
> Best,
> Rika Sukenik 
>
>
> On Sat, Apr 17, 2021 at 12:47 AM Saq Imtiaz  wrote:
>
>> @arun apologies for the very delayed reply, I've had a hectic last couple 
>> of months and this message slipped through the cracks. Let me know if these 
>> questions are still relevant and if so, we can discuss them further.
>>
>> Saq
>>
>> -- 
>> 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/1jTwdmq8cgI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/80b9ff77-260e-4ea2-94d2-2120f9fe5189n%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/c4e2eefb-b60a-45af-994a-6f0147a8882en%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[Rika Sukenik]

I just made a note to update in ~1 week. Thanks, Saq! Really appreciate the
time you're spending on this.

Best,
Rika Sukenik


On Sat, Apr 17, 2021 at 12:47 AM Saq Imtiaz  wrote:

> @arun apologies for the very delayed reply, I've had a hectic last couple
> of months and this message slipped through the cracks. Let me know if these
> questions are still relevant and if so, we can discuss them further.
>
> Saq
>
> --
> 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/1jTwdmq8cgI/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/80b9ff77-260e-4ea2-94d2-2120f9fe5189n%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/CALSoQA3e%3D0bogdrHH9YGa%2BTie9WhN5yKUgA9gW-gZd599HxiCw%40mail.gmail.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@arun apologies for the very delayed reply, I've had a hectic last couple 
of months and this message slipped through the cracks. Let me know if these 
questions are still relevant and if so, we can discuss them further.

Saq

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/80b9ff77-260e-4ea2-94d2-2120f9fe5189n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Rika: I would not recommend use that modified version of the plugin in your 
wiki permanently as you will likely have problems upgrading in the future. 
There should be a new version of the edit-comptext plugin available in the 
next week or so that includes these changes.
You can use this version if the meantime, but please make a note to delete 
this version and install the new release once it is available.

Saq
On Friday, April 16, 2021 at 1:23:24 AM UTC+2 rika.s...@gmail.com wrote:

> Hey Saq, the test version works great for me too. Is it safe to use it in 
> my wiki permanently, or is there an updated plugin available? 
>
> On Friday, September 18, 2020 at 9:38:40 AM UTC-7 saq.i...@gmail.com 
> wrote:
>
>> *Streams and the Edit-CompText plugin.*
>>
>> There have been several requests for compatibility between Streams and 
>> the Edit-CompText plugin which provides autocompletion for tiddler titles. 
>> This requires changes in the autocompletion plugin.
>>
>> I have a test version which requires feedback.
>>
>> If you are not already accustomed to the Edit-CompText plugin 
>>  and the features it 
>> provides, please familiarize yourself with it first before proceeding.
>>
>> Note that any issues or feedback for the features and behaviour of the 
>> Edit-CompText plugin itself should be directed towards its github page. The 
>> remit of the changes in this test version is only to enable the same 
>> features in Streams as are available via this plugin in editing regular 
>> tiddlers, and I will not be making any other changes to the autocomplete 
>> plugin.
>>
>> Please back up your wiki and use this version of the plugin for testing 
>> only:
>>
>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsnowgoon88%2Fedit-comptext
>>
>> I would appreciate feedback on whether the plugin works in Streams as it 
>> does when used in regular tiddlers.
>>
>> Cheers,
>> Saq
>>
>

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

[tw5] Re: [ Streams ] : feedback and issues

[Rika Sukenik]

Hey Saq, the test version works great for me too. Is it safe to use it in 
my wiki permanently, or is there an updated plugin available? 

On Friday, September 18, 2020 at 9:38:40 AM UTC-7 saq.i...@gmail.com wrote:

> *Streams and the Edit-CompText plugin.*
>
> There have been several requests for compatibility between Streams and the 
> Edit-CompText plugin which provides autocompletion for tiddler titles. This 
> requires changes in the autocompletion plugin.
>
> I have a test version which requires feedback.
>
> If you are not already accustomed to the Edit-CompText plugin 
>  and the features it 
> provides, please familiarize yourself with it first before proceeding.
>
> Note that any issues or feedback for the features and behaviour of the 
> Edit-CompText plugin itself should be directed towards its github page. The 
> remit of the changes in this test version is only to enable the same 
> features in Streams as are available via this plugin in editing regular 
> tiddlers, and I will not be making any other changes to the autocomplete 
> plugin.
>
> Please back up your wiki and use this version of the plugin for testing 
> only:
>
> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsnowgoon88%2Fedit-comptext
>
> I would appreciate feedback on whether the plugin works in Streams as it 
> does when used in regular tiddlers.
>
> Cheers,
> Saq
>

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

[tw5] Re: [ Streams ] : feedback and issues

[arun babu]

Hi Saq, Thanks for the reply. I will mention some of my doubts below.

1. I have a tiddler with title  "Case template for command palette" with 
code given below in the text field:

<$action-setfield $tiddler="New Case" what="case" case-number="" topic="" 
keywords="" topic="" source="" edit-later="" url="" />
<$action-sendmessage $message="tm-edit-tiddler" $param="New Case"/>
Create~New Case

I use command palette plug-in in my wiki. I have made a custom command to 
create new tiddlers for adding new cases easily. It's as given below:
Tiddler title - $:/plugins/souk21/commandpalette/New Case
tag -$:/tags/CommandPaletteCommand
text - {{Case template for command palette}}
field - command-palette-type - actionString

This help me to create new tiddlers using command palette plug in for 
adding new cases with fields auto populated.

Can you suggest a way to incorporate the code which you shared into the 
tiddler "Case template for command palette". I tried to do it, but failed. 

2. I am ok with renaming of nodes, if needed.

3. Regarding export of a single stream tree -  i asked it because one day i 
tried to export a few of my cases which i had created as seperate streams 
trees, in json format so that i could add them into another wiki of mine. 
But i couldn't find a way to get the entire stream tree (parent and child 
nodes)of those cases by filtering. 
I tried to understand what's told in this link 
 
about 
exporting, but it's beyond my current level of knowledge about TW i think.

4. Regarding customising Recents tab - Should i edit this tiddler for that 
-  "$:/core/Filters/RecentTiddlers". I tried to modify the filter field of 
that tiddler by adding has[parent] to this 
[!is[system]has[modified]!sort[modified]limit[50]]. But i couldnt find any 
change.

On Thursday, January 14, 2021 at 11:24:17 PM UTC+5:30 saq.i...@gmail.com 
wrote:

> @arun
>
> It is worth remembering that Streams is all about tiddlers and their 
> relationships. As such I think most of what you need can and should be done 
> without adding further complexity to the plugin.
>
>>
>>1. Templates - This is my use case. I am a radiology doctor. So when 
>>I take notes about the imaging findings of a certain topic, it usually 
>> have 
>>specific pattern. I will give an example. Name of the topic will form the 
>>title of parent streams tiddler / node. Then there will be headings like 
>>Definitions, Pathology, X ray findings, Ultrasound , CT, MRI findings, 
>>treatment etc. which will be made into separate child nodes. 
>>
>> There are several options available to you here. You could have a button 
> that prompts for a a new case name or topic and then creates that tiddler 
> and associated notes. Or you could create the root tiddler as usual and 
> have a button in it (via toolbar or view template) to create the starting 
> nodes as needed.
>
> For example, something like this in the root tiddler after having created 
> the root tiddler:
>
> \define myactions()
> <$vars nodeSuffixes="Pathology [[X ray findings]] Treatment"
> root=<>
> >
> <$list filter="[enlist]">
> <$action-setfield 
> $tiddler={{{ [addprefix[/]addprefix] }}} 
> parent=<> 
> text={{{ [addprefix[!!]]}}} 
> stream-type="default" />
> 
> <$set name="new-nodes" 
> filter="[enlistaddprefix[/]addprefix]">
> <$action-listops $tiddler=<> $field="stream-list" 
> $subfilter=<>/>
> 
> 
> \end
>
> <$button actions=<>>
> new case
> 
>
>>
>>1. As I said in the first point, in many of my streams trees, the 
>>first word or sentence in the child nodes will be usually the name of the 
>>headings or sub headings. Is there any way to incorporate this first word 
>>or sentence of the child nodes into the title of that particular child 
>> node 
>>in place of the timestamp. For example - <>/<>sentence of child node>>
>>
>>
> Nodes are created before you start writing any content. As such this 
> simply isn't possible. You can however rename nodes.
>  
>
>>
>>1. Ability to export a single streams tree in any of the available 
>>format. Currently I don’t know of a way to select a single parent streams 
>>tiddler with its entire child nodes and export them. I know only to use 
>> the 
>>filter [stream-type[default]] which will select all the streams tiddlers 
>> in 
>>my wiki. Am I missing something here?
>>
>>
> Have you looked at the docs:
> https://saqimtiaz.github.io/streams/#Working%20with%20streams%20tiddlers
>  
>
>>
>>1. When we use streams, our recents page will be over filled with the 
>>child nodes of each streams tree. Is there any way to hide the child 
>> nodes 
>>within the recents page. Or else create a separate recents page for 
>> streams 
>>in addition to the default one with only parent nodes as it’s contents.
>>
>> Streams is a plugin meant to integrate with our 

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@arun

It is worth remembering that Streams is all about tiddlers and their 
relationships. As such I think most of what you need can and should be done 
without adding further complexity to the plugin.

>
>1. Templates - This is my use case. I am a radiology doctor. So when I 
>take notes about the imaging findings of a certain topic, it usually have 
>specific pattern. I will give an example. Name of the topic will form the 
>title of parent streams tiddler / node. Then there will be headings like 
>Definitions, Pathology, X ray findings, Ultrasound , CT, MRI findings, 
>treatment etc. which will be made into separate child nodes. 
>
> There are several options available to you here. You could have a button 
that prompts for a a new case name or topic and then creates that tiddler 
and associated notes. Or you could create the root tiddler as usual and 
have a button in it (via toolbar or view template) to create the starting 
nodes as needed.

For example, something like this in the root tiddler after having created 
the root tiddler:

\define myactions()
<$vars nodeSuffixes="Pathology [[X ray findings]] Treatment"
root=<>
>
<$list filter="[enlist]">
<$action-setfield 
$tiddler={{{ [addprefix[/]addprefix] }}} 
parent=<> 
text={{{ [addprefix[!!]]}}} 
stream-type="default" />

<$set name="new-nodes" 
filter="[enlistaddprefix[/]addprefix]">
<$action-listops $tiddler=<> $field="stream-list" 
$subfilter=<>/>


\end

<$button actions=<>>
new case


>
>1. As I said in the first point, in many of my streams trees, the 
>first word or sentence in the child nodes will be usually the name of the 
>headings or sub headings. Is there any way to incorporate this first word 
>or sentence of the child nodes into the title of that particular child 
> node 
>in place of the timestamp. For example - <>/>
>
>
Nodes are created before you start writing any content. As such this simply 
isn't possible. You can however rename nodes.
 

>
>1. Ability to export a single streams tree in any of the available 
>format. Currently I don’t know of a way to select a single parent streams 
>tiddler with its entire child nodes and export them. I know only to use 
> the 
>filter [stream-type[default]] which will select all the streams tiddlers 
> in 
>my wiki. Am I missing something here?
>
>
Have you looked at the docs:
https://saqimtiaz.github.io/streams/#Working%20with%20streams%20tiddlers
 

>
>1. When we use streams, our recents page will be over filled with the 
>child nodes of each streams tree. Is there any way to hide the child nodes 
>within the recents page. Or else create a separate recents page for 
> streams 
>in addition to the default one with only parent nodes as it’s contents.
>
> Streams is a plugin meant to integrate with our customizations and plugins 
rather than a ready to use TiddlyWiki edition. As such it does not and 
should not try to change the Recent sidebar tab. However, you can customize 
this on your own to only show the parent or root tiddler for each node. 

>
>1. Option to select either wiki text or markdown format in the config 
>option of streams so that users who need it can make use of.
>
> You can currently set this via the template for new node tiddlers, I am 
unsure how well it will work after that in terms of rendering Markdown. 
Adding it as a separate configuration option would clash with the template 
configuration and I do not want to add further complexity unless I hear 
from more users that such a feature is needed.

Regards,
Saq


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

[tw5] Re: [ Streams ] : feedback and issues

[arun babu]

@Saq

I am a heavy streams user. It helps to organize my notes in a structured 
manner so that I can easily retrieve them when I need a quick reference. 
Given below are some of the features which I wish to see in streams in 
future.

   1. Templates - This is my use case. I am a radiology doctor. So when I 
   take notes about the imaging findings of a certain topic, it usually have 
   specific pattern. I will give an example. Name of the topic will form the 
   title of parent streams tiddler / node. Then there will be headings like 
   Definitions, Pathology, X ray findings, Ultrasound , CT, MRI findings, 
   treatment etc. which will be made into separate child nodes. Sometimes 
   there will be sub headings under some of the headings - for example under 
   MRI findings there may be sub headings like T1W, T2W sequences - these also 
   will be separate child nodes which will be indented under the corresponding 
   heading. These headings or sub headings name will be usually the first 
   sentence or word in the corresponding child nodes. Now I have to manually 
   do it for each topic ( I use text expander extensions of browsers to make 
   it easy for me). I would like this to happen automatically. That is when I 
   create a parent streams tiddler or node with the topic name as title and 
   add a particular tag or field to it, the child nodes should be created 
   automatically with name of each headings or sub headings as the first text 
   in that particular child node. So that I just have to fill in the contents 
   in each node. Is it possible to do like this? I saw the option called 
   template for new node in the streams settings. But I could configure only 
   the parent tiddler with that. Is it possible to configure child nodes along 
   with the parent using this template feature?
   2. As I said in the first point, in many of my streams trees, the first 
   word or sentence in the child nodes will be usually the name of the 
   headings or sub headings. Is there any way to incorporate this first word 
   or sentence of the child nodes into the title of that particular child node 
   in place of the timestamp. For example - <>/<>
   3. Ability to export a single streams tree in any of the available 
   format. Currently I don’t know of a way to select a single parent streams 
   tiddler with its entire child nodes and export them. I know only to use the 
   filter [stream-type[default]] which will select all the streams tiddlers in 
   my wiki. Am I missing something here?
   4. When we use streams, our recents page will be over filled with the 
   child nodes of each streams tree. Is there any way to hide the child nodes 
   within the recents page. Or else create a separate recents page for streams 
   in addition to the default one with only parent nodes as it’s contents.
   5. Option to select either wiki text or markdown format in the config 
   option of streams so that users who need it can make use of.
   


On Sunday, January 10, 2021 at 2:26:40 AM UTC+5:30 si wrote:

> Thanks a lot saq - I was able to do exactly what I needed.
> On Saturday, 9 January 2021 at 17:00:34 UTC saq.i...@gmail.com wrote:
>
>> @si All the macros that determine drag and drop as well as keyboard 
>> behaviour are in  $:/plugins/sq/streams/action-macros 
>>
>> Note that you can override any of the macros in that tiddler, by creating 
>> a macro with the same name in a tiddler that has the 
>> tag $:/tags/streams/user-actionmacros
>>
>> I do not recommend editing any of the plugin tiddlers.
>>
>> Please be aware that there are a lot of changes planned to these macros, 
>> so I wouldn't recommend trying to customize them at this time, otherwise 
>> you are looking at extra work when upgrading.
>>  
>>
>> On Friday, January 8, 2021 at 11:34:48 PM UTC+1 si wrote:
>>
>>> Thanks for sharing Saq it looks great at first glance. I'll give it a 
>>> more robust test tomorrow and come back with my feedback.
>>>
>>> This might be a good time to re-ask my question from before the release 
>>> of 5.23 
>>> :
>>>
>>> > Is there a way to edit Streams so that shift + drag-and-drop uses a 
>>> custom macro for transclusion instead of the regular curly brackets? I'm 
>>> imagining that this would be quite an easy tweak but I can't find the 
>>> relevant plug-in tiddler.
>>>
>>> Thanks again.
>>> On Friday, 8 January 2021 at 18:15:42 UTC saq.i...@gmail.com wrote:
>>>
 There is a preview available of an experimental branch of Streams 
 intended to explore optimizations and new ideas. 

 https://groups.google.com/g/tiddlywiki/c/Z54n90uM6ng

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

[tw5] Re: [ Streams ] : feedback and issues

[si]

Thanks a lot saq - I was able to do exactly what I needed.
On Saturday, 9 January 2021 at 17:00:34 UTC saq.i...@gmail.com wrote:

> @si All the macros that determine drag and drop as well as keyboard 
> behaviour are in  $:/plugins/sq/streams/action-macros 
>
> Note that you can override any of the macros in that tiddler, by creating 
> a macro with the same name in a tiddler that has the 
> tag $:/tags/streams/user-actionmacros
>
> I do not recommend editing any of the plugin tiddlers.
>
> Please be aware that there are a lot of changes planned to these macros, 
> so I wouldn't recommend trying to customize them at this time, otherwise 
> you are looking at extra work when upgrading.
>  
>
> On Friday, January 8, 2021 at 11:34:48 PM UTC+1 si wrote:
>
>> Thanks for sharing Saq it looks great at first glance. I'll give it a 
>> more robust test tomorrow and come back with my feedback.
>>
>> This might be a good time to re-ask my question from before the release 
>> of 5.23 
>> :
>>
>> > Is there a way to edit Streams so that shift + drag-and-drop uses a 
>> custom macro for transclusion instead of the regular curly brackets? I'm 
>> imagining that this would be quite an easy tweak but I can't find the 
>> relevant plug-in tiddler.
>>
>> Thanks again.
>> On Friday, 8 January 2021 at 18:15:42 UTC saq.i...@gmail.com wrote:
>>
>>> There is a preview available of an experimental branch of Streams 
>>> intended to explore optimizations and new ideas. 
>>>
>>> https://groups.google.com/g/tiddlywiki/c/Z54n90uM6ng
>>>
>>

-- 
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/9f912002-c249-4e03-9a64-eeb9f2b368d7n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@si All the macros that determine drag and drop as well as keyboard 
behaviour are in  $:/plugins/sq/streams/action-macros 

Note that you can override any of the macros in that tiddler, by creating a 
macro with the same name in a tiddler that has the 
tag $:/tags/streams/user-actionmacros

I do not recommend editing any of the plugin tiddlers.

Please be aware that there are a lot of changes planned to these macros, so 
I wouldn't recommend trying to customize them at this time, otherwise you 
are looking at extra work when upgrading.
 

On Friday, January 8, 2021 at 11:34:48 PM UTC+1 si wrote:

> Thanks for sharing Saq it looks great at first glance. I'll give it a more 
> robust test tomorrow and come back with my feedback.
>
> This might be a good time to re-ask my question from before the release 
> of 5.23 
> :
>
> > Is there a way to edit Streams so that shift + drag-and-drop uses a 
> custom macro for transclusion instead of the regular curly brackets? I'm 
> imagining that this would be quite an easy tweak but I can't find the 
> relevant plug-in tiddler.
>
> Thanks again.
> On Friday, 8 January 2021 at 18:15:42 UTC saq.i...@gmail.com wrote:
>
>> There is a preview available of an experimental branch of Streams 
>> intended to explore optimizations and new ideas. 
>>
>> https://groups.google.com/g/tiddlywiki/c/Z54n90uM6ng
>>
>

-- 
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/0d81f37c-cef1-4290-a643-f01a28ad1b37n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Scott Kingery]

Thanks, saq. I was probably trying to making harder than it is. 

On Friday, January 8, 2021 at 10:01:23 AM UTC-8 saq.i...@gmail.com wrote:

> [!is[shadow]!title[MainPage]]
>
> or
>
> [!is[shadow]!has[nostream]]
>
> with nostream field having any non-blank value.
>
> This is a subfilter that applies to the current tiddler, so you can test 
> any condition for that tiddler.
>
> On Friday, January 8, 2021 at 6:39:44 PM UTC+1 Scott Kingery wrote:
>
>> Is there a way to NOT have streams show up on a tiddler? 
>> It seems you could edit $:/config/sq/streams/stream-enable-filter to do 
>> this but I can't seem to get the syntax right. My wiki opens with MainPage 
>> as the default and I don't need the Stream icon on there because I use that 
>> page to launch other pages.
>>
>> Even handier might be a field called nostream (or something better) and 
>> entering yes would prevent the function.
>>
>> Thanks for the excellent plugin!
>> Scott
>>
>> On Thursday, December 24, 2020 at 7:50:48 AM UTC-8 saq.i...@gmail.com 
>> wrote:
>>
>>> *Streams users:*
>>>
>>> Please remember to upgrade to the latest version of Streams (0.1.20) 
>>> before upgrading to TW 5.1.23
>>>
>>> https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams
>>>
>>>
>>> On Thursday, December 10, 2020 at 10:17:39 AM UTC+1 Dominic Robinson 
>>> wrote:
>>>
 Ahh - that makes sense.  Obvious really :)

 On Wednesday, December 9, 2020 at 7:04:00 PM UTC saq.i...@gmail.com 
 wrote:

> @Dom: As Si points out, the Alt+Enter shortcut tries to split the text 
> at double line breaks. If you want to split at the cursor just press 
> Enter.
>
> However, thanks to your bug report I did manage to find and fix an 
> actual bug with the Alt+Enter handling.
>
> Cheers,
> Saq
>
> On Wednesday, December 9, 2020 at 7:07:38 PM UTC+1 si wrote:
>
>> Hi Dom,
>>
>> It looks like you are making the same error that I did 
>>  
>> and have misunderstood the purpose of the shortcut.
>>
>> Alt+Enter should split a node that has multiple lines into separate 
>> tiddlers, but in your GIF the text is all on one line, so there is 
>> nothing 
>> to split.
>>
>> If you want to split the text into two tiddlers at the place where 
>> your cursor is, just press Enter.
>>
>> On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:
>>
>>> @Saq - this is Chrome on Windows 10.
>>>
>>> Hopefully this gif will show you what you need.  The gif looping 
>>> doesn't help, but it shows an attempt to split the node with alt-enter 
>>> and 
>>> the creation of a new empty one.
>>>
>>> Cheers
>>> Dom
>>>
>>> [image: streams-split-repro.gif]
>>>
>>> On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com 
>>> wrote:
>>>
 @Dom I am unable to re-create the issue with Stream 0.1.20 on 
 Chrome or Firefox on Windows 10.

- What browser and OS are you using?
- Can you please provide step by step instruction for 
re-creating the issue on https://saqimtiaz.github.io/streams/ ?
   - Please include:
  - the exact text that you enter, 
  - a screenshot of the resultant nodes, 
  - and a screenshot of the *Recent* tab in the sidebar, so 
  I can see what tiddlers have been created.
   
 Thank you.
 Saq

 On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson 
 wrote:

> @Saq, 0.1.20 seems to have the same issue.
>
> Dom
>
> On Thursday, December 3, 2020 at 10:19:03 PM UTC 
> saq.i...@gmail.com wrote:
>
>> @Dom I have a fix. I want to give it until tomorrow to do some 
>> further testing before I push a new version. Thank you again for the 
>> bug 
>> report.
>
>

-- 
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/3578bae0-6d64-4a67-ac62-42e872b1f5f8n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[si]

Thanks for sharing Saq it looks great at first glance. I'll give it a more 
robust test tomorrow and come back with my feedback.

This might be a good time to re-ask my question from before the release of 
5.23 :

> Is there a way to edit Streams so that shift + drag-and-drop uses a 
custom macro for transclusion instead of the regular curly brackets? I'm 
imagining that this would be quite an easy tweak but I can't find the 
relevant plug-in tiddler.

Thanks again.
On Friday, 8 January 2021 at 18:15:42 UTC saq.i...@gmail.com wrote:

> There is a preview available of an experimental branch of Streams intended 
> to explore optimizations and new ideas. 
>
> https://groups.google.com/g/tiddlywiki/c/Z54n90uM6ng
>

-- 
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/bcbd0c0b-2cb6-4ff1-81d5-25ce46151cc3n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

There is a preview available of an experimental branch of Streams intended 
to explore optimizations and new ideas. 

https://groups.google.com/g/tiddlywiki/c/Z54n90uM6ng

-- 
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/9c10976e-0d44-4d26-adc2-e6aa8fe84f93n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

[!is[shadow]!title[MainPage]]

or

[!is[shadow]!has[nostream]]

with nostream field having any non-blank value.

This is a subfilter that applies to the current tiddler, so you can test 
any condition for that tiddler.

On Friday, January 8, 2021 at 6:39:44 PM UTC+1 Scott Kingery wrote:

> Is there a way to NOT have streams show up on a tiddler? 
> It seems you could edit $:/config/sq/streams/stream-enable-filter to do 
> this but I can't seem to get the syntax right. My wiki opens with MainPage 
> as the default and I don't need the Stream icon on there because I use that 
> page to launch other pages.
>
> Even handier might be a field called nostream (or something better) and 
> entering yes would prevent the function.
>
> Thanks for the excellent plugin!
> Scott
>
> On Thursday, December 24, 2020 at 7:50:48 AM UTC-8 saq.i...@gmail.com 
> wrote:
>
>> *Streams users:*
>>
>> Please remember to upgrade to the latest version of Streams (0.1.20) 
>> before upgrading to TW 5.1.23
>>
>> https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams
>>
>>
>> On Thursday, December 10, 2020 at 10:17:39 AM UTC+1 Dominic Robinson 
>> wrote:
>>
>>> Ahh - that makes sense.  Obvious really :)
>>>
>>> On Wednesday, December 9, 2020 at 7:04:00 PM UTC saq.i...@gmail.com 
>>> wrote:
>>>
 @Dom: As Si points out, the Alt+Enter shortcut tries to split the text 
 at double line breaks. If you want to split at the cursor just press Enter.

 However, thanks to your bug report I did manage to find and fix an 
 actual bug with the Alt+Enter handling.

 Cheers,
 Saq

 On Wednesday, December 9, 2020 at 7:07:38 PM UTC+1 si wrote:

> Hi Dom,
>
> It looks like you are making the same error that I did 
>  
> and have misunderstood the purpose of the shortcut.
>
> Alt+Enter should split a node that has multiple lines into separate 
> tiddlers, but in your GIF the text is all on one line, so there is 
> nothing 
> to split.
>
> If you want to split the text into two tiddlers at the place where 
> your cursor is, just press Enter.
>
> On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:
>
>> @Saq - this is Chrome on Windows 10.
>>
>> Hopefully this gif will show you what you need.  The gif looping 
>> doesn't help, but it shows an attempt to split the node with alt-enter 
>> and 
>> the creation of a new empty one.
>>
>> Cheers
>> Dom
>>
>> [image: streams-split-repro.gif]
>>
>> On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com 
>> wrote:
>>
>>> @Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome 
>>> or Firefox on Windows 10.
>>>
>>>- What browser and OS are you using?
>>>- Can you please provide step by step instruction for 
>>>re-creating the issue on https://saqimtiaz.github.io/streams/ ?
>>>   - Please include:
>>>  - the exact text that you enter, 
>>>  - a screenshot of the resultant nodes, 
>>>  - and a screenshot of the *Recent* tab in the sidebar, so 
>>>  I can see what tiddlers have been created.
>>>   
>>> Thank you.
>>> Saq
>>>
>>> On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson 
>>> wrote:
>>>
 @Saq, 0.1.20 seems to have the same issue.

 Dom

 On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com 
 wrote:

> @Dom I have a fix. I want to give it until tomorrow to do some 
> further testing before I push a new version. Thank you again for the 
> bug 
> report.



-- 
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/aebe9229-5e10-47fd-96c7-6dd93ffa0a09n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Michael Wiktowy]

Hi Scott,

I have added [!is[shadow]tag[Daily Log]] to 
'$:/config/sq/streams/stream-enable-filter' to only have it show up in my 
tiddlers tagged with 'Daily Log' (and restrict it to non-shadow tiddlers 
with the intent to speed things up but I don't think it makes a difference) 
and it works for me.

That config setting is used via a ViewTemplate located at 
'$:/plugins/sq/streams/stream-view-template' so maybe that got over-written 
or changed to ignore that config setting if it still doesn't work with 
valid subfilter. It will indicate that whether it is changed from the 
default plugin shadow tiddler.

/Mike

On Friday, January 8, 2021 at 1:39:44 PM UTC-4 Scott Kingery wrote:

> Is there a way to NOT have streams show up on a tiddler? 
> It seems you could edit $:/config/sq/streams/stream-enable-filter to do 
> this but I can't seem to get the syntax right. My wiki opens with MainPage 
> as the default and I don't need the Stream icon on there because I use that 
> page to launch other pages.
>
> Even handier might be a field called nostream (or something better) and 
> entering yes would prevent the function.
>
> Thanks for the excellent plugin!
> Scott
>
> On Thursday, December 24, 2020 at 7:50:48 AM UTC-8 saq.i...@gmail.com 
> wrote:
>
>> *Streams users:*
>>
>> Please remember to upgrade to the latest version of Streams (0.1.20) 
>> before upgrading to TW 5.1.23
>>
>> https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams
>>
>>
>> On Thursday, December 10, 2020 at 10:17:39 AM UTC+1 Dominic Robinson 
>> wrote:
>>
>>> Ahh - that makes sense.  Obvious really :)
>>>
>>> On Wednesday, December 9, 2020 at 7:04:00 PM UTC saq.i...@gmail.com 
>>> wrote:
>>>
 @Dom: As Si points out, the Alt+Enter shortcut tries to split the text 
 at double line breaks. If you want to split at the cursor just press Enter.

 However, thanks to your bug report I did manage to find and fix an 
 actual bug with the Alt+Enter handling.

 Cheers,
 Saq

 On Wednesday, December 9, 2020 at 7:07:38 PM UTC+1 si wrote:

> Hi Dom,
>
> It looks like you are making the same error that I did 
>  
> and have misunderstood the purpose of the shortcut.
>
> Alt+Enter should split a node that has multiple lines into separate 
> tiddlers, but in your GIF the text is all on one line, so there is 
> nothing 
> to split.
>
> If you want to split the text into two tiddlers at the place where 
> your cursor is, just press Enter.
>
> On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:
>
>> @Saq - this is Chrome on Windows 10.
>>
>> Hopefully this gif will show you what you need.  The gif looping 
>> doesn't help, but it shows an attempt to split the node with alt-enter 
>> and 
>> the creation of a new empty one.
>>
>> Cheers
>> Dom
>>
>> [image: streams-split-repro.gif]
>>
>> On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com 
>> wrote:
>>
>>> @Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome 
>>> or Firefox on Windows 10.
>>>
>>>- What browser and OS are you using?
>>>- Can you please provide step by step instruction for 
>>>re-creating the issue on https://saqimtiaz.github.io/streams/ ?
>>>   - Please include:
>>>  - the exact text that you enter, 
>>>  - a screenshot of the resultant nodes, 
>>>  - and a screenshot of the *Recent* tab in the sidebar, so 
>>>  I can see what tiddlers have been created.
>>>   
>>> Thank you.
>>> Saq
>>>
>>> On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson 
>>> wrote:
>>>
 @Saq, 0.1.20 seems to have the same issue.

 Dom

 On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com 
 wrote:

> @Dom I have a fix. I want to give it until tomorrow to do some 
> further testing before I push a new version. Thank you again for the 
> bug 
> report.



-- 
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/2388b073-e24e-4dc4-8ab3-b626195bec56n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Scott Kingery]

Is there a way to NOT have streams show up on a tiddler? 
It seems you could edit $:/config/sq/streams/stream-enable-filter to do 
this but I can't seem to get the syntax right. My wiki opens with MainPage 
as the default and I don't need the Stream icon on there because I use that 
page to launch other pages.

Even handier might be a field called nostream (or something better) and 
entering yes would prevent the function.

Thanks for the excellent plugin!
Scott

On Thursday, December 24, 2020 at 7:50:48 AM UTC-8 saq.i...@gmail.com wrote:

> *Streams users:*
>
> Please remember to upgrade to the latest version of Streams (0.1.20) 
> before upgrading to TW 5.1.23
>
> https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams
>
>
> On Thursday, December 10, 2020 at 10:17:39 AM UTC+1 Dominic Robinson wrote:
>
>> Ahh - that makes sense.  Obvious really :)
>>
>> On Wednesday, December 9, 2020 at 7:04:00 PM UTC saq.i...@gmail.com 
>> wrote:
>>
>>> @Dom: As Si points out, the Alt+Enter shortcut tries to split the text 
>>> at double line breaks. If you want to split at the cursor just press Enter.
>>>
>>> However, thanks to your bug report I did manage to find and fix an 
>>> actual bug with the Alt+Enter handling.
>>>
>>> Cheers,
>>> Saq
>>>
>>> On Wednesday, December 9, 2020 at 7:07:38 PM UTC+1 si wrote:
>>>
 Hi Dom,

 It looks like you are making the same error that I did 
  
 and have misunderstood the purpose of the shortcut.

 Alt+Enter should split a node that has multiple lines into separate 
 tiddlers, but in your GIF the text is all on one line, so there is nothing 
 to split.

 If you want to split the text into two tiddlers at the place where your 
 cursor is, just press Enter.

 On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:

> @Saq - this is Chrome on Windows 10.
>
> Hopefully this gif will show you what you need.  The gif looping 
> doesn't help, but it shows an attempt to split the node with alt-enter 
> and 
> the creation of a new empty one.
>
> Cheers
> Dom
>
> [image: streams-split-repro.gif]
>
> On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com 
> wrote:
>
>> @Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome 
>> or Firefox on Windows 10.
>>
>>- What browser and OS are you using?
>>- Can you please provide step by step instruction for re-creating 
>>the issue on https://saqimtiaz.github.io/streams/ ?
>>   - Please include:
>>  - the exact text that you enter, 
>>  - a screenshot of the resultant nodes, 
>>  - and a screenshot of the *Recent* tab in the sidebar, so I 
>>  can see what tiddlers have been created.
>>   
>> Thank you.
>> Saq
>>
>> On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson 
>> wrote:
>>
>>> @Saq, 0.1.20 seems to have the same issue.
>>>
>>> Dom
>>>
>>> On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com 
>>> wrote:
>>>
 @Dom I have a fix. I want to give it until tomorrow to do some 
 further testing before I push a new version. Thank you again for the 
 bug 
 report.
>>>
>>>

-- 
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/329a090c-df8e-4948-834b-3d99f69bdb7fn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

*Streams users:*

Please remember to upgrade to the latest version of Streams (0.1.20) before 
upgrading to TW 5.1.23

https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams


On Thursday, December 10, 2020 at 10:17:39 AM UTC+1 Dominic Robinson wrote:

> Ahh - that makes sense.  Obvious really :)
>
> On Wednesday, December 9, 2020 at 7:04:00 PM UTC saq.i...@gmail.com wrote:
>
>> @Dom: As Si points out, the Alt+Enter shortcut tries to split the text at 
>> double line breaks. If you want to split at the cursor just press Enter.
>>
>> However, thanks to your bug report I did manage to find and fix an actual 
>> bug with the Alt+Enter handling.
>>
>> Cheers,
>> Saq
>>
>> On Wednesday, December 9, 2020 at 7:07:38 PM UTC+1 si wrote:
>>
>>> Hi Dom,
>>>
>>> It looks like you are making the same error that I did 
>>>  
>>> and have misunderstood the purpose of the shortcut.
>>>
>>> Alt+Enter should split a node that has multiple lines into separate 
>>> tiddlers, but in your GIF the text is all on one line, so there is nothing 
>>> to split.
>>>
>>> If you want to split the text into two tiddlers at the place where your 
>>> cursor is, just press Enter.
>>>
>>> On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:
>>>
 @Saq - this is Chrome on Windows 10.

 Hopefully this gif will show you what you need.  The gif looping 
 doesn't help, but it shows an attempt to split the node with alt-enter and 
 the creation of a new empty one.

 Cheers
 Dom

 [image: streams-split-repro.gif]

 On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com 
 wrote:

> @Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome 
> or Firefox on Windows 10.
>
>- What browser and OS are you using?
>- Can you please provide step by step instruction for re-creating 
>the issue on https://saqimtiaz.github.io/streams/ ?
>   - Please include:
>  - the exact text that you enter, 
>  - a screenshot of the resultant nodes, 
>  - and a screenshot of the *Recent* tab in the sidebar, so I 
>  can see what tiddlers have been created.
>   
> Thank you.
> Saq
>
> On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson 
> wrote:
>
>> @Saq, 0.1.20 seems to have the same issue.
>>
>> Dom
>>
>> On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com 
>> wrote:
>>
>>> @Dom I have a fix. I want to give it until tomorrow to do some 
>>> further testing before I push a new version. Thank you again for the 
>>> bug 
>>> report.
>>
>>

-- 
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/f05aabd9-a57b-47a7-8df7-5c1f1856ca73n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Dominic Robinson]

Ahh - that makes sense.  Obvious really :)

On Wednesday, December 9, 2020 at 7:04:00 PM UTC saq.i...@gmail.com wrote:

> @Dom: As Si points out, the Alt+Enter shortcut tries to split the text at 
> double line breaks. If you want to split at the cursor just press Enter.
>
> However, thanks to your bug report I did manage to find and fix an actual 
> bug with the Alt+Enter handling.
>
> Cheers,
> Saq
>
> On Wednesday, December 9, 2020 at 7:07:38 PM UTC+1 si wrote:
>
>> Hi Dom,
>>
>> It looks like you are making the same error that I did 
>>  
>> and have misunderstood the purpose of the shortcut.
>>
>> Alt+Enter should split a node that has multiple lines into separate 
>> tiddlers, but in your GIF the text is all on one line, so there is nothing 
>> to split.
>>
>> If you want to split the text into two tiddlers at the place where your 
>> cursor is, just press Enter.
>>
>> On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:
>>
>>> @Saq - this is Chrome on Windows 10.
>>>
>>> Hopefully this gif will show you what you need.  The gif looping doesn't 
>>> help, but it shows an attempt to split the node with alt-enter and the 
>>> creation of a new empty one.
>>>
>>> Cheers
>>> Dom
>>>
>>> [image: streams-split-repro.gif]
>>>
>>> On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com wrote:
>>>
 @Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome or 
 Firefox on Windows 10.

- What browser and OS are you using?
- Can you please provide step by step instruction for re-creating 
the issue on https://saqimtiaz.github.io/streams/ ?
   - Please include:
  - the exact text that you enter, 
  - a screenshot of the resultant nodes, 
  - and a screenshot of the *Recent* tab in the sidebar, so I 
  can see what tiddlers have been created.
   
 Thank you.
 Saq

 On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson wrote:

> @Saq, 0.1.20 seems to have the same issue.
>
> Dom
>
> On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com 
> wrote:
>
>> @Dom I have a fix. I want to give it until tomorrow to do some 
>> further testing before I push a new version. Thank you again for the bug 
>> report.
>
>

-- 
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/9b2afc27-4bde-48ed-8548-69c7d380325cn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Dom: As Si points out, the Alt+Enter shortcut tries to split the text at 
double line breaks. If you want to split at the cursor just press Enter.

However, thanks to your bug report I did manage to find and fix an actual 
bug with the Alt+Enter handling.

Cheers,
Saq

On Wednesday, December 9, 2020 at 7:07:38 PM UTC+1 si wrote:

> Hi Dom,
>
> It looks like you are making the same error that I did 
>  and 
> have misunderstood the purpose of the shortcut.
>
> Alt+Enter should split a node that has multiple lines into separate 
> tiddlers, but in your GIF the text is all on one line, so there is nothing 
> to split.
>
> If you want to split the text into two tiddlers at the place where your 
> cursor is, just press Enter.
>
> On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:
>
>> @Saq - this is Chrome on Windows 10.
>>
>> Hopefully this gif will show you what you need.  The gif looping doesn't 
>> help, but it shows an attempt to split the node with alt-enter and the 
>> creation of a new empty one.
>>
>> Cheers
>> Dom
>>
>> [image: streams-split-repro.gif]
>>
>> On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com wrote:
>>
>>> @Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome or 
>>> Firefox on Windows 10.
>>>
>>>- What browser and OS are you using?
>>>- Can you please provide step by step instruction for re-creating 
>>>the issue on https://saqimtiaz.github.io/streams/ ?
>>>   - Please include:
>>>  - the exact text that you enter, 
>>>  - a screenshot of the resultant nodes, 
>>>  - and a screenshot of the *Recent* tab in the sidebar, so I 
>>>  can see what tiddlers have been created.
>>>   
>>> Thank you.
>>> Saq
>>>
>>> On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson wrote:
>>>
 @Saq, 0.1.20 seems to have the same issue.

 Dom

 On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com 
 wrote:

> @Dom I have a fix. I want to give it until tomorrow to do some further 
> testing before I push a new version. Thank you again for the bug report.



-- 
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/c6569820-ddc0-47f5-a9a6-f4911e18418fn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[si]

Hi Dom,

It looks like you are making the same error that I did 
 and 
have misunderstood the purpose of the shortcut.

Alt+Enter should split a node that has multiple lines into separate 
tiddlers, but in your GIF the text is all on one line, so there is nothing 
to split.

If you want to split the text into two tiddlers at the place where your 
cursor is, just press Enter.

On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:

> @Saq - this is Chrome on Windows 10.
>
> Hopefully this gif will show you what you need.  The gif looping doesn't 
> help, but it shows an attempt to split the node with alt-enter and the 
> creation of a new empty one.
>
> Cheers
> Dom
>
> [image: streams-split-repro.gif]
>
> On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com wrote:
>
>> @Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome or 
>> Firefox on Windows 10.
>>
>>- What browser and OS are you using?
>>- Can you please provide step by step instruction for re-creating the 
>>issue on https://saqimtiaz.github.io/streams/ ?
>>   - Please include:
>>  - the exact text that you enter, 
>>  - a screenshot of the resultant nodes, 
>>  - and a screenshot of the *Recent* tab in the sidebar, so I can 
>>  see what tiddlers have been created.
>>   
>> Thank you.
>> Saq
>>
>> On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson wrote:
>>
>>> @Saq, 0.1.20 seems to have the same issue.
>>>
>>> Dom
>>>
>>> On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com 
>>> wrote:
>>>
 @Dom I have a fix. I want to give it until tomorrow to do some further 
 testing before I push a new version. Thank you again for the bug report.
>>>
>>>

-- 
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/08937321-a01c-4712-9dda-63c5bef3bd3cn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome or 
Firefox on Windows 10.

   - What browser and OS are you using?
   - Can you please provide step by step instruction for re-creating the 
   issue on https://saqimtiaz.github.io/streams/ ?
  - Please include:
 - the exact text that you enter, 
 - a screenshot of the resultant nodes, 
 - and a screenshot of the *Recent* tab in the sidebar, so I can 
 see what tiddlers have been created.
  
Thank you.
Saq

On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson wrote:

> @Saq, 0.1.20 seems to have the same issue.
>
> Dom
>
> On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com wrote:
>
>> @Dom I have a fix. I want to give it until tomorrow to do some further 
>> testing before I push a new version. Thank you again for the bug report.
>
>

-- 
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/b2b57db5-4b49-4db3-bcfd-776d2771272bn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Dominic Robinson]

@Saq, 0.1.20 seems to have the same issue.

Dom

On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com wrote:

> @Dom I have a fix. I want to give it until tomorrow to do some further 
> testing before I push a new version. Thank you again for the bug report.

-- 
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/ab53e688-6821-4334-9698-bfdc5c82bc18n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[si]

@saq Will do. Thanks a lot for all your amazing contributions to TiddlyWiki!
On Sunday, 6 December 2020 at 17:56:33 UTC saq.i...@gmail.com wrote:

> @si busy times currently. Please remind me after the release of 5.1.23
>
> On Sunday, December 6, 2020 at 12:36:53 AM UTC+1 si wrote:
>
>> Hi Saq,
>>
>> Is there a way to edit Streams so that shift + drag-and-drop uses a 
>> custom macro for transclusion instead of the regular curly brackets?
>>
>> I'm imagining that this would be quite an easy tweak but I can't find the 
>> relevant plug-in tiddler.
>> On Friday, 4 December 2020 at 12:24:46 UTC saq.i...@gmail.com wrote:
>>
>>> *Streams update to 0.1.18*
>>> https://saqimtiaz.github.io/streams/
>>>
>>> This resolves the issue with saving multiple nodes with Alt+Enter. The 
>>> fix is a bit of a kludge but it will have to do until I have a chance to 
>>> re-think action-widget execution in general.
>>>
>>> Please remember that you need to update to Streams 0.1.17 or newer 
>>> before upgrading to the upcoming TiddlyWiki version 5.1.23
>>>
>>

-- 
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/c20d5c87-6e94-49e3-887e-baa310cac8d4n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@si busy times currently. Please remind me after the release of 5.1.23

On Sunday, December 6, 2020 at 12:36:53 AM UTC+1 si wrote:

> Hi Saq,
>
> Is there a way to edit Streams so that shift + drag-and-drop uses a custom 
> macro for transclusion instead of the regular curly brackets?
>
> I'm imagining that this would be quite an easy tweak but I can't find the 
> relevant plug-in tiddler.
> On Friday, 4 December 2020 at 12:24:46 UTC saq.i...@gmail.com wrote:
>
>> *Streams update to 0.1.18*
>> https://saqimtiaz.github.io/streams/
>>
>> This resolves the issue with saving multiple nodes with Alt+Enter. The 
>> fix is a bit of a kludge but it will have to do until I have a chance to 
>> re-think action-widget execution in general.
>>
>> Please remember that you need to update to Streams 0.1.17 or newer before 
>> upgrading to the upcoming TiddlyWiki version 5.1.23
>>
>

-- 
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/3a50fc99-2028-4a7e-8d47-0c9f6a5ffbaen%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

*Streams update to 0.1.19*
https://saqimtiaz.github.io/streams/

There was a bug that crept in with 0.1.18 with root titles that have spaces 
in them. Apologies. So please update.

As a bonus there are some performance optimizations included that reduce 
rendering time *significantly* for very large node trees.

-- 
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/7eaa6050-48fb-4a3e-bee8-a6d7b5a4eb91n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[si]

Hi Saq,

Is there a way to edit Streams so that shift + drag-and-drop uses a custom 
macro for transclusion instead of the regular curly brackets?

I'm imagining that this would be quite an easy tweak but I can't find the 
relevant plug-in tiddler.
On Friday, 4 December 2020 at 12:24:46 UTC saq.i...@gmail.com wrote:

> *Streams update to 0.1.18*
> https://saqimtiaz.github.io/streams/
>
> This resolves the issue with saving multiple nodes with Alt+Enter. The fix 
> is a bit of a kludge but it will have to do until I have a chance to 
> re-think action-widget execution in general.
>
> Please remember that you need to update to Streams 0.1.17 or newer before 
> upgrading to the upcoming TiddlyWiki version 5.1.23
>

-- 
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/63b1e891-d0f1-4844-9ccc-322eea114c1cn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

*Streams update to 0.1.18*
https://saqimtiaz.github.io/streams/

This resolves the issue with saving multiple nodes with Alt+Enter. The fix 
is a bit of a kludge but it will have to do until I have a chance to 
re-think action-widget execution in general.

Please remember that you need to update to Streams 0.1.17 or newer before 
upgrading to the upcoming TiddlyWiki version 5.1.23

-- 
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/c5cfc714-58b6-48d8-8275-f747415551b3n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[TW Tones]

Saq,

I do not care if they get out of sequence within a second, only that they 
are unique. I don't understand the issue you raise - but that is fine.

Tones

On Friday, 4 December 2020 at 09:17:12 UTC+11 saq.i...@gmail.com wrote:

> @Tones
>
> I have solved this problem in the past simply by including milliseconds in 
>> the time stamp however before using the "new title" check it does not 
>> exist, increment the milliseconds and check again. 
>>
>
> This isn't possible when executing action widgets in a loop, where the 
> previous action widgets have not always been executed before the current 
> one. It is a well known issue with action widgets and concurrency.
>

-- 
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/2a62d731-7f06-4d3b-bb0a-e03922d226ban%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Dom I have a fix. I want to give it until tomorrow to do some further 
testing before I push a new version. Thank you again for the bug report.

-- 
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/90298f56-f1f4-4a96-ac12-fdf50b20f7c5n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Tones

I have solved this problem in the past simply by including milliseconds in 
> the time stamp however before using the "new title" check it does not 
> exist, increment the milliseconds and check again. 
>

This isn't possible when executing action widgets in a loop, where the 
previous action widgets have not always been executed before the current 
one. It is a well known issue with action widgets and concurrency.

-- 
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/9fd4c861-4acf-4d49-8a20-e6f97f53bfc2n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[TW Tones]

Saq,

I have solved this problem in the past simply by including milliseconds in 
the time stamp however before using the "new title" check it does not 
exist, increment the milliseconds and check again. No one cares if the 
milliseconds are not totally accurate, you could even increment with a 
random number to reduce collisions ( at most they need only that they 
reflect chronological orde)r. Given 1000 per second are available this 
should not be an issue, and in fact 99.99% of the time the first title is 
usable, however it is important to ensure the timestamp value is 
re-evaluated at the last possible moment.

Personally I feel incrementing a value to obtain the next tiddlername is a 
better than timestamp method, but that just a view point. I am looking 
eventually to produce a generic solution for this as there are many ways to 
make use of this code patterns not only for unique serial numbers but 
initial set/queue order FIFO LIFO and more, with less bytes needed.

Regards
Tones

On Friday, 4 December 2020 at 04:27:48 UTC+11 saq.i...@gmail.com wrote:

> So the bug that Dom reported is very interesting and others may find it of 
> interest.
>
> The underlying problem is that we are creating several tiddlers at the 
> same time via action-widgets, and the tiddler titles rely on a timestamp to 
> make them unique. However, the tiddlers are sometimes created so quickly 
> that they are not unique!
>
> There have been discussions on this group in the past on the merits of 
> using timestamps for tiddler titles and this is a good reminder that they 
> just aren't specific enough to serve as a proper unique identifier.
>
> I am going to have take a moment and think about the best way to resolve 
> this. I know users prefer timestamps to randomly generated UUIDs so I have 
> to consider if there is a middle ground.
>
>

-- 
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/21b2fb69-d141-4c1f-8629-8389262346d9n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@si no worries, there are a lot of different options and features to keep 
track of. 

I have an idea for a new widget to solve the problem that might be helpful 
in other places too.

On Thursday, December 3, 2020 at 8:48:49 PM UTC+1 si wrote:

> Ahh my apologies I had misunderstood the purpose of the shortcut. I 
> thought it was supposed to create a new node from text following the caret, 
> but I realize now that that just happens when you press enter.
>
> On Thursday, 3 December 2020 at 19:38:35 UTC saq.i...@gmail.com wrote:
>
>> @si this bug relates to splitting a tiddler into multiple tiddlers by 
>> pressing Alt+Enter.
>>
>> So for instance the following results in 6 tiddlers if saved with 
>> Alt+Enter. The first keeps the original title but the 5 subsequent ones are 
>> new.
>>
>> "a
>>
>> b
>>
>> c
>>
>> d
>>
>> e
>>
>> f"
>>
>>
>>
>> On Thursday, December 3, 2020 at 8:33:37 PM UTC+1 si wrote:
>>
>>> >>> The underlying problem is that we are creating several tiddlers at 
>>> the same time via action-widgets, and the tiddler titles rely on a 
>>> timestamp to make them unique. However, the tiddlers are sometimes created 
>>> so quickly that they are not unique! 
>>>
>>> Just out of curiosity, why do you need to create two timestamped 
>>> tiddlers? Can't the text before the caret keep the title of the original 
>>> tiddler, and the rest of the text get a new timestamp?
>>> On Thursday, 3 December 2020 at 17:27:48 UTC saq.i...@gmail.com wrote:
>>>
 So the bug that Dom reported is very interesting and others may find it 
 of interest.

 The underlying problem is that we are creating several tiddlers at the 
 same time via action-widgets, and the tiddler titles rely on a timestamp 
 to 
 make them unique. However, the tiddlers are sometimes created so quickly 
 that they are not unique!

 There have been discussions on this group in the past on the merits of 
 using timestamps for tiddler titles and this is a good reminder that they 
 just aren't specific enough to serve as a proper unique identifier.

 I am going to have take a moment and think about the best way to 
 resolve this. I know users prefer timestamps to randomly generated UUIDs 
 so 
 I have to consider if there is a middle ground.



-- 
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/c244c763-1a33-46de-bdd1-5a787aefe1d5n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[si]

Ahh my apologies I had misunderstood the purpose of the shortcut. I thought 
it was supposed to create a new node from text following the caret, but I 
realize now that that just happens when you press enter.

On Thursday, 3 December 2020 at 19:38:35 UTC saq.i...@gmail.com wrote:

> @si this bug relates to splitting a tiddler into multiple tiddlers by 
> pressing Alt+Enter.
>
> So for instance the following results in 6 tiddlers if saved with 
> Alt+Enter. The first keeps the original title but the 5 subsequent ones are 
> new.
>
> "a
>
> b
>
> c
>
> d
>
> e
>
> f"
>
>
>
> On Thursday, December 3, 2020 at 8:33:37 PM UTC+1 si wrote:
>
>> >>> The underlying problem is that we are creating several tiddlers at 
>> the same time via action-widgets, and the tiddler titles rely on a 
>> timestamp to make them unique. However, the tiddlers are sometimes created 
>> so quickly that they are not unique! 
>>
>> Just out of curiosity, why do you need to create two timestamped 
>> tiddlers? Can't the text before the caret keep the title of the original 
>> tiddler, and the rest of the text get a new timestamp?
>> On Thursday, 3 December 2020 at 17:27:48 UTC saq.i...@gmail.com wrote:
>>
>>> So the bug that Dom reported is very interesting and others may find it 
>>> of interest.
>>>
>>> The underlying problem is that we are creating several tiddlers at the 
>>> same time via action-widgets, and the tiddler titles rely on a timestamp to 
>>> make them unique. However, the tiddlers are sometimes created so quickly 
>>> that they are not unique!
>>>
>>> There have been discussions on this group in the past on the merits of 
>>> using timestamps for tiddler titles and this is a good reminder that they 
>>> just aren't specific enough to serve as a proper unique identifier.
>>>
>>> I am going to have take a moment and think about the best way to resolve 
>>> this. I know users prefer timestamps to randomly generated UUIDs so I have 
>>> to consider if there is a middle ground.
>>>
>>>

-- 
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/7d014534-b16f-457a-b301-06707080c969n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@si this bug relates to splitting a tiddler into multiple tiddlers by 
pressing Alt+Enter.

So for instance the following results in 6 tiddlers if saved with 
Alt+Enter. The first keeps the original title but the 5 subsequent ones are 
new.

"a

b

c

d

e

f"



On Thursday, December 3, 2020 at 8:33:37 PM UTC+1 si wrote:

> >>> The underlying problem is that we are creating several tiddlers at the 
> same time via action-widgets, and the tiddler titles rely on a timestamp to 
> make them unique. However, the tiddlers are sometimes created so quickly 
> that they are not unique! 
>
> Just out of curiosity, why do you need to create two timestamped tiddlers? 
> Can't the text before the caret keep the title of the original tiddler, and 
> the rest of the text get a new timestamp?
> On Thursday, 3 December 2020 at 17:27:48 UTC saq.i...@gmail.com wrote:
>
>> So the bug that Dom reported is very interesting and others may find it 
>> of interest.
>>
>> The underlying problem is that we are creating several tiddlers at the 
>> same time via action-widgets, and the tiddler titles rely on a timestamp to 
>> make them unique. However, the tiddlers are sometimes created so quickly 
>> that they are not unique!
>>
>> There have been discussions on this group in the past on the merits of 
>> using timestamps for tiddler titles and this is a good reminder that they 
>> just aren't specific enough to serve as a proper unique identifier.
>>
>> I am going to have take a moment and think about the best way to resolve 
>> this. I know users prefer timestamps to randomly generated UUIDs so I have 
>> to consider if there is a middle ground.
>>
>>

-- 
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/896fb938-dcf4-4299-ade1-cdfaeec36fc6n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[si]

>>> The underlying problem is that we are creating several tiddlers at the 
same time via action-widgets, and the tiddler titles rely on a timestamp to 
make them unique. However, the tiddlers are sometimes created so quickly 
that they are not unique! 

Just out of curiosity, why do you need to create two timestamped tiddlers? 
Can't the text before the caret keep the title of the original tiddler, and 
the rest of the text get a new timestamp?
On Thursday, 3 December 2020 at 17:27:48 UTC saq.i...@gmail.com wrote:

> So the bug that Dom reported is very interesting and others may find it of 
> interest.
>
> The underlying problem is that we are creating several tiddlers at the 
> same time via action-widgets, and the tiddler titles rely on a timestamp to 
> make them unique. However, the tiddlers are sometimes created so quickly 
> that they are not unique!
>
> There have been discussions on this group in the past on the merits of 
> using timestamps for tiddler titles and this is a good reminder that they 
> just aren't specific enough to serve as a proper unique identifier.
>
> I am going to have take a moment and think about the best way to resolve 
> this. I know users prefer timestamps to randomly generated UUIDs so I have 
> to consider if there is a middle ground.
>
>

-- 
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/1c57c9f9-9541-4782-ac36-1b434bcb9620n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

So the bug that Dom reported is very interesting and others may find it of 
interest.

The underlying problem is that we are creating several tiddlers at the same 
time via action-widgets, and the tiddler titles rely on a timestamp to make 
them unique. However, the tiddlers are sometimes created so quickly that 
they are not unique!

There have been discussions on this group in the past on the merits of 
using timestamps for tiddler titles and this is a good reminder that they 
just aren't specific enough to serve as a proper unique identifier.

I am going to have take a moment and think about the best way to resolve 
this. I know users prefer timestamps to randomly generated UUIDs so I have 
to consider if there is a middle ground.

-- 
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/a1c5e069-3a52-4208-898b-381c9df9d4den%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Hi Dom,

Thank you for the bug report. Turns out this bug (in the exact same way of 
similar variations) has actually been there for quite some time! Will 
investigate.

Cheers,
Saq

On Thursday, December 3, 2020 at 3:16:56 PM UTC+1 Dominic Robinson wrote:

> Hi Saq
>
> In the v 0.1.17 you have linked above, the alt-Enter shortcut to split and 
> save as multiple nodes creates a new empty node but does not seem to split 
> the content.
>
> Regards
> Dom
> On Thursday, November 26, 2020 at 10:30:09 PM UTC saq.i...@gmail.com 
> wrote:
>
>> Streams update to v 0.1.17: https://saqimtiaz.github.io/streams/
>>
>> This is a compatibility update for the upcoming release of TiddlyWiki 
>> 5.1.23
>> You will need to update Streams before upgrading to the new TW release.
>>
>> I would appreciate some testing and feedback in case there are any 
>> unexpected issues.
>>
>> Regards,
>> Saq
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f24c8610-f01e-44fc-8d42-f2278e59e880n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Dominic Robinson]

Hi Saq

In the v 0.1.17 you have linked above, the alt-Enter shortcut to split and 
save as multiple nodes creates a new empty node but does not seem to split 
the content.

Regards
Dom
On Thursday, November 26, 2020 at 10:30:09 PM UTC saq.i...@gmail.com wrote:

> Streams update to v 0.1.17: https://saqimtiaz.github.io/streams/
>
> This is a compatibility update for the upcoming release of TiddlyWiki 
> 5.1.23
> You will need to update Streams before upgrading to the new TW release.
>
> I would appreciate some testing and feedback in case there are any 
> unexpected issues.
>
> Regards,
> Saq
>

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

Re: [tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

I gathered it was mostly behind the scenes components. I am very much
looking forward to the new release and continued progress on Streams. It's
become my daily drive for research and writing at this point. You (and the
large pool of contributors) have created a wonderful tool!

On Mon, Nov 30, 2020 at 6:19 AM Saq Imtiaz  wrote:

> @keelan thank you for the feedback. There are only small changes but they
> are essential to a problem free upgrade to the upcoming TiddlyWiki 5.1.23
> release, as a lot of the tweaks that Streams relied on have been introduced
> into the core.
>
> On Monday, November 30, 2020 at 2:04:50 AM UTC+1 keela...@gmail.com wrote:
>
>> I've done some initial testing, Saq, with my regular workflows and I've
>> not ran into any snags as of yet. I'll keep doing so and let you know if I
>> stumble across something.
>>
>> On Thursday, November 26, 2020 at 4:30:09 PM UTC-6 saq.i...@gmail.com
>> wrote:
>>
>>> Streams update to v 0.1.17: https://saqimtiaz.github.io/streams/
>>>
>>> This is a compatibility update for the upcoming release of TiddlyWiki
>>> 5.1.23
>>> You will need to update Streams before upgrading to the new TW release.
>>>
>>> I would appreciate some testing and feedback in case there are any
>>> unexpected issues.
>>>
>>> Regards,
>>> Saq
>>>
>> --
> 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/1jTwdmq8cgI/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/1d9134c5-558b-4582-ae8e-d2cdc87007e5n%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/CACaamT%3D7cbx3Od2p3xcf_XP7M8dQSN%2B8HQsm60bZcgDCSvLnMA%40mail.gmail.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@keelan thank you for the feedback. There are only small changes but they 
are essential to a problem free upgrade to the upcoming TiddlyWiki 5.1.23 
release, as a lot of the tweaks that Streams relied on have been introduced 
into the core.

On Monday, November 30, 2020 at 2:04:50 AM UTC+1 keela...@gmail.com wrote:

> I've done some initial testing, Saq, with my regular workflows and I've 
> not ran into any snags as of yet. I'll keep doing so and let you know if I 
> stumble across something.
>
> On Thursday, November 26, 2020 at 4:30:09 PM UTC-6 saq.i...@gmail.com 
> wrote:
>
>> Streams update to v 0.1.17: https://saqimtiaz.github.io/streams/
>>
>> This is a compatibility update for the upcoming release of TiddlyWiki 
>> 5.1.23
>> You will need to update Streams before upgrading to the new TW release.
>>
>> I would appreciate some testing and feedback in case there are any 
>> unexpected issues.
>>
>> Regards,
>> Saq
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1d9134c5-558b-4582-ae8e-d2cdc87007e5n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

I've done some initial testing, Saq, with my regular workflows and I've not 
ran into any snags as of yet. I'll keep doing so and let you know if I 
stumble across something.

On Thursday, November 26, 2020 at 4:30:09 PM UTC-6 saq.i...@gmail.com wrote:

> Streams update to v 0.1.17: https://saqimtiaz.github.io/streams/
>
> This is a compatibility update for the upcoming release of TiddlyWiki 
> 5.1.23
> You will need to update Streams before upgrading to the new TW release.
>
> I would appreciate some testing and feedback in case there are any 
> unexpected issues.
>
> Regards,
> Saq
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/765c724d-420a-47b6-8f40-c29f22f5732cn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Streams update to v 0.1.17: https://saqimtiaz.github.io/streams/

This is a compatibility update for the upcoming release of TiddlyWiki 5.1.23
You will need to update Streams before upgrading to the new TW release.

I would appreciate some testing and feedback in case there are any 
unexpected issues.

Regards,
Saq

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b82b5bfa-2b0b-40d2-b978-9bcf05aa7b90n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[arun babu]

@Saq, 
Is there any way to use the floating editor you had shown in this link (
https://saqimtiaz.github.io/sq-tw/floating-menu.html#config:config%20%5B%5BDraft%20of%20'RikerIpsum'%5D%5D)
 
within a streams tiddler ?
I could make it work only in the default editor, not in the streams tiddler.

On Sunday, October 25, 2020 at 3:42:09 AM UTC+5:30 saq.i...@gmail.com wrote:

> @Bop
>
> Using tags to reflect relationships is contrary to the design decisions in 
> Streams. I am not familiar with TiddlyMap but I assume tw-list expects a 
> title list, in which a title with spaces would cause issues. I suggest 
> checking if TiddlyMap supports a different edge type that treat the entire 
> field value as a tiddler title. Does tw-title or tw-field exist?
>
> As for Stories, that plugin was made available specifically for Stroll and 
> I am not able to provide support for it beyond that specific configuration.
>
> On Saturday, October 24, 2020 at 12:01:57 AM UTC+2, 波普 wrote:
>>
>> Hi Saq,
>>
>> I added a new edge-type "tw-list: parent" in order to display the 
>> connections of streams in the tiddlymap, but the tiddlymap does not support 
>> spaces in the field, and if there are spaces in the title, the correct 
>> connections cannot be displayed. 
>>
>> Can you make the parent field automatically add a tag so that tiddlymap 
>> can correctly identify the title with spaces?  
>>
>> Regards, 
>> Bop 
>>
>

-- 
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/1aa8cdbf-4873-4a3a-8023-1448c8601738n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Bop

Using tags to reflect relationships is contrary to the design decisions in 
Streams. I am not familiar with TiddlyMap but I assume tw-list expects a 
title list, in which a title with spaces would cause issues. I suggest 
checking if TiddlyMap supports a different edge type that treat the entire 
field value as a tiddler title. Does tw-title or tw-field exist?

As for Stories, that plugin was made available specifically for Stroll and 
I am not able to provide support for it beyond that specific configuration.

On Saturday, October 24, 2020 at 12:01:57 AM UTC+2, 波普 wrote:
>
> Hi Saq,
>
> I added a new edge-type "tw-list: parent" in order to display the 
> connections of streams in the tiddlymap, but the tiddlymap does not support 
> spaces in the field, and if there are spaces in the title, the correct 
> connections cannot be displayed. 
>
> Can you make the parent field automatically add a tag so that tiddlymap 
> can correctly identify the title with spaces?  
>
> Regards, 
> Bop 
>

-- 
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/e953ff4d-e192-4928-b86d-ca3d87b6de9co%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[波普]

Hi Saq,

Are you the author of the Stories plug-in? I have a question to ask you.
I want to automatically hide the sidebar when I click the "show right 
column" icon, and vice versa.
Do you know how I should modify some tiddler's code?

Regards, 
Bop 



-- 
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/5e79d41a-c4a7-4100-aee4-11f55ac419f5n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[波普]

Hi Saq,

I added a new edge-type "tw-list: parent" in order to display the 
connections of streams in the tiddlymap, but the tiddlymap does not support 
spaces in the field, and if there are spaces in the title, the correct 
connections cannot be displayed. 

Can you make the parent field automatically add a tag so that tiddlymap can 
correctly identify the title with spaces?  

Regards, 
Bop 

-- 
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/a100d807-9367-4a20-8a07-0d7c95b90ccdn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Ken Gray]

I'm using TWEXE, so maybe it's because of that. 
Does yours save as expected?

On Wednesday, October 7, 2020 at 9:48:20 AM UTC-4 saq.i...@gmail.com wrote:

> Ken, Streams does't change the default behaviour of autosave in any manner.
>
> Are you using the single file version of TiddlyWiki, or node.js?
>
>
> On Wednesday, October 7, 2020 at 3:16:21 PM UTC+2, Ken Gray wrote:
>>
>> I have 1.1.15 but my 'autosave' still doesn't work.  when I create a new 
>> item in a tiddler, it doesn't save.  however, when I create a new tiddler, 
>> it autosaves as expected. 
>> if not a way at this time, is there a keyboard shortcut to do this while 
>> I work?
>>
>> Thanks!
>>
>> On Friday, July 3, 2020 at 11:29:53 AM UTC-4 saq.i...@gmail.com wrote:
>>
>>> Please post your feedback and any issues for Streams here or on github: 
>>> https://github.com/saqimtiaz/streams
>>>
>>> Demo: https://saqimtiaz.github.io/sq-tw/streams.html
>>> Before posting a bug report please make sure you have the latest version 
>>> of the plugin from the above link.
>>>
>>> Previous thread and background: 
>>> https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/KeVDndcnY0g%5B1-25%5D
>>>
>>> I am focusing only on bug reports for now until I have greater 
>>> availability. However, all feedback will be considered when further 
>>> development takes places. 
>>>
>>> The code needs a full review for consistency after the last major 
>>> refactoring in which fields were renamed among other changes, before new 
>>> features can be added.
>>>
>>

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

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Ken, Streams does't change the default behaviour of autosave in any manner.

Are you using the single file version of TiddlyWiki, or node.js?

On Wednesday, October 7, 2020 at 3:16:21 PM UTC+2, Ken Gray wrote:
>
> I have 1.1.15 but my 'autosave' still doesn't work.  when I create a new 
> item in a tiddler, it doesn't save.  however, when I create a new tiddler, 
> it autosaves as expected. 
> if not a way at this time, is there a keyboard shortcut to do this while I 
> work?
>
> Thanks!
>
> On Friday, July 3, 2020 at 11:29:53 AM UTC-4 saq.i...@gmail.com wrote:
>
>> Please post your feedback and any issues for Streams here or on github: 
>> https://github.com/saqimtiaz/streams
>>
>> Demo: https://saqimtiaz.github.io/sq-tw/streams.html
>> Before posting a bug report please make sure you have the latest version 
>> of the plugin from the above link.
>>
>> Previous thread and background: 
>> https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/KeVDndcnY0g%5B1-25%5D
>>
>> I am focusing only on bug reports for now until I have greater 
>> availability. However, all feedback will be considered when further 
>> development takes places. 
>>
>> The code needs a full review for consistency after the last major 
>> refactoring in which fields were renamed among other changes, before new 
>> features can be added.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e41a99a8-79c3-4eac-9bef-892b47051c60o%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Ken Gray]

I have 1.1.15 but my 'autosave' still doesn't work.  when I create a new 
item in a tiddler, it doesn't save.  however, when I create a new tiddler, 
it autosaves as expected. 
if not a way at this time, is there a keyboard shortcut to do this while I 
work?

Thanks!

On Friday, July 3, 2020 at 11:29:53 AM UTC-4 saq.i...@gmail.com wrote:

> Please post your feedback and any issues for Streams here or on github: 
> https://github.com/saqimtiaz/streams
>
> Demo: https://saqimtiaz.github.io/sq-tw/streams.html
> Before posting a bug report please make sure you have the latest version 
> of the plugin from the above link.
>
> Previous thread and background: 
> https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/KeVDndcnY0g%5B1-25%5D
>
> I am focusing only on bug reports for now until I have greater 
> availability. However, all feedback will be considered when further 
> development takes places. 
>
> The code needs a full review for consistency after the last major 
> refactoring in which fields were renamed among other changes, before new 
> features can be added.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2c07b745-3a03-4217-aedc-8b51a69bcb33n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[sin...@gmail.com]

Hello Saq, 

thank you for your wonderful plugin! It is really helpful!

My suggestion: it would be good if it was possible to maintain the states 
of the nodes (open or closed) between sessions. Or maybe there is already a 
way to do it?

Another idea (that was really simple to do myself) is to add a menu item to 
the context menu "Make todo" which adds a tag "task" to the tiddler. That 
can be used to make a quick todo list using the list-tagged-draggable macro 
that comes with tiddlywiki (the template needs to be modified to show the 
text instead of title). I found it useful and wanted to share :-)

Thanks again!
Valeria

On Wednesday, September 23, 2020 at 2:50:48 PM UTC+2 saq.i...@gmail.com 
wrote:

> Hi Mike,
>
> In exploring the context menu option I mentioned, it seems to be extremely 
>> easy to implement. Using your instructions 
>> 
>>  
>> as a guide
>>
>
> That is good to hear. The individual keyboard shortcut tiddlers were added 
> only in the last plugin update, and this was one of the use cases in mind. 
> You're the first one to actually use them in this way, so this is good 
> feedback.
>
> The default context menu items are currently hardcoded. I would like to 
> move those into separate tiddlers and offer a settings panel for the 
> content menu, before adding more items to the context menu by default.
>
> Cheers,
> Saq
>

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

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Hi Mike,

In exploring the context menu option I mentioned, it seems to be extremely 
> easy to implement. Using your instructions 
> 
>  
> as a guide
>

That is good to hear. The individual keyboard shortcut tiddlers were added 
only in the last plugin update, and this was one of the use cases in mind. 
You're the first one to actually use them in this way, so this is good 
feedback.

The default context menu items are currently hardcoded. I would like to 
move those into separate tiddlers and offer a settings panel for the 
content menu, before adding more items to the context menu by default.

Cheers,
Saq

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

[tw5] Re: [ Streams ] : feedback and issues

[Michael Wiktowy]

Hi Saq,

In exploring the context menu option I mentioned, it seems to be extremely 
easy to implement. Using your instructions 

 
as a guide, I just added the "$:/tags/streams/contextmenu" tag and 
"sq-contextmenu-name" 
field with "Save and Exit" to your 
"$:/plugins/sq/streams/keyboard-shortcuts/save-and-exit" 
plug-in tiddler. That seems to allow mouse-only closing of individual 
stream entries (even with multiple entries open) with minimal fuss. 
Hopefully you can add that into the official plug-in.

/Mike

On Tuesday, September 22, 2020 at 2:11:19 PM UTC-3 saq.i...@gmail.com wrote:

> Hi Mike, 
>
>
> I still feel that there should be some mouse-only way of ending editing ...
>>
>
> I agree, it's just a case of figuring out an intuitive way to do so 
> without cluttering the interface. 
> I thought about a double click in the editor to exit editing feature. 
> However, the way that the editor (which is  a core feature) works wont 
> allow that. 
>
> Open to suggestions if you happen to think of something.
> Cheers,
> Saq
>
>

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

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Hi Mike, 

I still feel that there should be some mouse-only way of ending editing ...
>

I agree, it's just a case of figuring out an intuitive way to do so without 
cluttering the interface. 
I thought about a double click in the editor to exit editing feature. 
However, the way that the editor (which is  a core feature) works wont 
allow that. 

Open to suggestions if you happen to think of something.
Cheers,
Saq

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

[tw5] Re: [ Streams ] : feedback and issues

[Michael Wiktowy]

Hi Saq,

Thanks for pointing out the self-referencing macro trick ... that seems 
like a recipe for disaster and infinite loops but it works great. I will 
try to implement that elsewhere in situations where I don't know the depth 
of the tree.

In working with streams for the past few days, I agree with you. I just 
have to remember to esc out before moving on. Any steps gained with my 
suggestion would be lost by having to do extra steps to do some of the 
other workflows. I still feel that there should be some mouse-only way of 
ending editing ... maybe I will just add a context menu entry since you 
have made that extensible.

Thank you for sharing a very useful tool. It is making daily journal 
entries very streamlined and I am looking at implementing it into a bunch 
of projects.

/Mike

On Thursday, September 17, 2020 at 11:45:38 AM UTC-3 saq.i...@gmail.com 
wrote:

> Mike, 
> Have a look at the following link for a macro that will create a static 
> HTML representation of any stream, regardless of depth:
>
> https://saqimtiaz.github.io/sq-tw/streams.html#Working%20with%20streams%20tiddlers
>
> Regarding exiting edit mode when clicking outside the node, this has come 
> up before.
> However, it would create its own set of usability issues as it's a pretty 
> common workflow for some to refer or copy content from other tiddlers while 
> editing a node, or even have two nodes open for editing in two different 
> tiddlers at the same time 
>
> I welcome any ideas that make it easier to exit editing, while still 
> allowing the above mentioned workflow and not adding visual clutter 
> One option could be a context menu option, though that would still be two 
> clicks of the mouse.
>
> Cheers,
> Saq
> On Thursday, September 17, 2020 at 4:18:44 PM UTC+2 mwik...@gmail.com 
> wrote:
>
>> Hi Saq,
>>
>> I really like this utility and have immediately incorporated it into my 
>> daily log wiki as I wanted to separate things out into tasks anyway and 
>> this does it perfectly including a built in time stamp.
>>
>> Some feedback though. Is there a way to change mouse interaction such 
>> that the edit window closes if you left click anywhere but the edit window? 
>> I find myself caught with the edit window stuck open after clicking 
>> somewhere and it loses focus. Then there is no way to close the edit field 
>> via mouse and the esc key doesn't work to close it so I have to click 
>> inside then switch to the keyboard to close it. It makes for a lot of UI 
>> input-mode-switching.
>>
>> I like the idea of using this in different contexts for to-do list (with 
>> checkboxes) and per-paragraph (with some formatting buttons) editors but it 
>> will take me a while of head-scratching before I figure out how to change 
>> your existing template. In the meanwhile, I've managed to make a template 
>> that will at least list streams as regular uneditable bullets to include in 
>> a weekly summary. I've just arbitrarily made it go 8 levels deep by a 
>> brute-force repetition. I'm not sure there is a way to adjust to the actual 
>> depth of the bullet indentations (and detect possible infinite loops ... 
>> not automatically possible but certainly possible with hand editing).
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *<$link to={{!!title}}> <$transclude field="caption"> <$view 
>> field="title"/><$list 
>> filter="[list[!!stream-list]!is[missing]]"> <$transclude 
>> mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
>> <$transclude mode="block"/> <$list 
>> filter="[list[!!stream-list]!is[missing]]"> <$transclude 
>> mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
>> <$transclude mode="block"/> <$list 
>> filter="[list[!!stream-list]!is[missing]]"> <$transclude 
>> mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
>> <$transclude mode="block"/> <$list 
>> filter="[list[!!stream-list]!is[missing]]"> <$transclude 
>> mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
>> <$transclude mode="block"/>   
>>  
>> *
>>
>> /Mike
>>
>> On Wednesday, September 16, 2020 at 9:50:37 AM UTC-3 saq.i...@gmail.com 
>> wrote:
>>
>>> New Streams update (0.1.15).
>>>
>>> Please backup your wiki before updating and test carefully before using 
>>> with important data.
>>>
>>> *Changes:*
>>>
>>>- Keyboard shortcuts are now configurable from the Control Panel 
>>>
>>> 
>>>
>>>- You can now add custom keyboard shortcuts 
>>>
>>> 
>>>  
>>>without editing any plugin shadow tiddlers.
>>>
>>>- This compliments the already existing ability to add custom 
>>>   context menu items 
>>>   
>>> 
>>>   
>>>   - 

Re: [tw5] Re: [ Streams ] : feedback and issues

[blake]

@Saq,
Confirming I'm having the same experience as Keelan -- seems to work fine
in both the normal text field and with Streams so far.

As always, fantastic work .. thanks ..!

On Sat, Sep 19, 2020 at 1:24 PM Saq Imtiaz  wrote:

> @keelan, thank you, good to know.
>
> On the next occasion I have a solid chunk of time to work on this, I'll
> try to push through an official update of the plugin with these changes.
>
> On Saturday, September 19, 2020 at 11:13:54 AM UTC+2, Keelan Cook wrote:
>>
>> This is a real help, Saq. After adding it to my own setup to test, I'm
>> not seeing any differences in behavior from the regular edit-comptext
>> plugin. It appears to work well in a Streams node now and still works the
>> same in a regular tiddler text field. Though, I've only fiddled with it
>> briefly.
>>
>> On Friday, September 18, 2020 at 11:38:40 AM UTC-5 saq.i...@gmail.com
>> wrote:
>>
>>> *Streams and the Edit-CompText plugin.*
>>>
>>> There have been several requests for compatibility between Streams and
>>> the Edit-CompText plugin which provides autocompletion for tiddler titles.
>>> This requires changes in the autocompletion plugin.
>>>
>>> I have a test version which requires feedback.
>>>
>>> If you are not already accustomed to the Edit-CompText plugin
>>>  and the features it
>>> provides, please familiarize yourself with it first before proceeding.
>>>
>>> Note that any issues or feedback for the features and behaviour of the
>>> Edit-CompText plugin itself should be directed towards its github page. The
>>> remit of the changes in this test version is only to enable the same
>>> features in Streams as are available via this plugin in editing regular
>>> tiddlers, and I will not be making any other changes to the autocomplete
>>> plugin.
>>>
>>> Please back up your wiki and use this version of the plugin for testing
>>> only:
>>>
>>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsnowgoon88%2Fedit-comptext
>>>
>>> I would appreciate feedback on whether the plugin works in Streams as it
>>> does when used in regular tiddlers.
>>>
>>> Cheers,
>>> Saq
>>>
>> --
> 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/1jTwdmq8cgI/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/b6d8f711-7d8a-48be-b00d-50474d8a8b8fo%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/CAOq7E9YKikRPmjd4OtTrNNua%2BU3PWXnwovrVvk6kKzuk04hC%3Dw%40mail.gmail.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@keelan, thank you, good to know.

On the next occasion I have a solid chunk of time to work on this, I'll try 
to push through an official update of the plugin with these changes.

On Saturday, September 19, 2020 at 11:13:54 AM UTC+2, Keelan Cook wrote:
>
> This is a real help, Saq. After adding it to my own setup to test, I'm not 
> seeing any differences in behavior from the regular edit-comptext plugin. 
> It appears to work well in a Streams node now and still works the same in a 
> regular tiddler text field. Though, I've only fiddled with it briefly.
>
> On Friday, September 18, 2020 at 11:38:40 AM UTC-5 saq.i...@gmail.com 
> wrote:
>
>> *Streams and the Edit-CompText plugin.*
>>
>> There have been several requests for compatibility between Streams and 
>> the Edit-CompText plugin which provides autocompletion for tiddler titles. 
>> This requires changes in the autocompletion plugin.
>>
>> I have a test version which requires feedback.
>>
>> If you are not already accustomed to the Edit-CompText plugin 
>>  and the features it 
>> provides, please familiarize yourself with it first before proceeding.
>>
>> Note that any issues or feedback for the features and behaviour of the 
>> Edit-CompText plugin itself should be directed towards its github page. The 
>> remit of the changes in this test version is only to enable the same 
>> features in Streams as are available via this plugin in editing regular 
>> tiddlers, and I will not be making any other changes to the autocomplete 
>> plugin.
>>
>> Please back up your wiki and use this version of the plugin for testing 
>> only:
>>
>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsnowgoon88%2Fedit-comptext
>>
>> I would appreciate feedback on whether the plugin works in Streams as it 
>> does when used in regular tiddlers.
>>
>> Cheers,
>> Saq
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b6d8f711-7d8a-48be-b00d-50474d8a8b8fo%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

This is a real help, Saq. After adding it to my own setup to test, I'm not 
seeing any differences in behavior from the regular edit-comptext plugin. 
It appears to work well in a Streams node now and still works the same in a 
regular tiddler text field. Though, I've only fiddled with it briefly.

On Friday, September 18, 2020 at 11:38:40 AM UTC-5 saq.i...@gmail.com wrote:

> *Streams and the Edit-CompText plugin.*
>
> There have been several requests for compatibility between Streams and the 
> Edit-CompText plugin which provides autocompletion for tiddler titles. This 
> requires changes in the autocompletion plugin.
>
> I have a test version which requires feedback.
>
> If you are not already accustomed to the Edit-CompText plugin 
>  and the features it 
> provides, please familiarize yourself with it first before proceeding.
>
> Note that any issues or feedback for the features and behaviour of the 
> Edit-CompText plugin itself should be directed towards its github page. The 
> remit of the changes in this test version is only to enable the same 
> features in Streams as are available via this plugin in editing regular 
> tiddlers, and I will not be making any other changes to the autocomplete 
> plugin.
>
> Please back up your wiki and use this version of the plugin for testing 
> only:
>
> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsnowgoon88%2Fedit-comptext
>
> I would appreciate feedback on whether the plugin works in Streams as it 
> does when used in regular tiddlers.
>
> Cheers,
> Saq
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/526d49b0-5b59-4663-bf24-ea8b44e18ce4n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

*Streams and the Edit-CompText plugin.*

There have been several requests for compatibility between Streams and the 
Edit-CompText plugin which provides autocompletion for tiddler titles. This 
requires changes in the autocompletion plugin.

I have a test version which requires feedback.

If you are not already accustomed to the Edit-CompText plugin 
 and the features it provides, 
please familiarize yourself with it first before proceeding.

Note that any issues or feedback for the features and behaviour of the 
Edit-CompText plugin itself should be directed towards its github page. The 
remit of the changes in this test version is only to enable the same 
features in Streams as are available via this plugin in editing regular 
tiddlers, and I will not be making any other changes to the autocomplete 
plugin.

Please back up your wiki and use this version of the plugin for testing 
only:
https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsnowgoon88%2Fedit-comptext

I would appreciate feedback on whether the plugin works in Streams as it 
does when used in regular tiddlers.

Cheers,
Saq

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

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

Saq, thanks for the update! All appears to be working as intended for me. 

On Thursday, September 17, 2020 at 9:58:07 AM UTC-5 saq.i...@gmail.com 
wrote:

> Florian,
>
> That is a new feature that will be available in the TiddlyWiki core from 
> version 5.1.23 and is currently available in the pre-release
>
> https://tiddlywiki.com/prerelease/
> Cheers,
>
> Saq
>
> On Thursday, September 17, 2020 at 4:50:21 PM UTC+2 janflor...@gmail.com 
> wrote:
>
>> Saq,
>>
>> besides the obvious greatness of your Streams plugin, what I really like
>> in your demo wiki is the ability to open tiddlers from the search bar by
>> hitting Enter. How did you achieve that/how can one implement that in
>> another wiki?
>>
>> It doesn't seem to be included in your plugins...
>>
>> Regards,
>> Florian
>>
>> Am 04.07.20 um 07:39 schrieb Saq Imtiaz:
>> > Please post your feedback and any issues for Streams here or on github: 
>> > https://github.com/saqimtiaz/streams
>> > 
>> > Demo: https://saqimtiaz.github.io/sq-tw/streams.html
>> > Before posting a bug report please make sure you have the latest 
>> version of 
>> > the plugin from the above link.
>> > 
>> > Previous thread and background: 
>> > 
>> https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/KeVDndcnY0g%5B1-25%5D
>> > 
>> > I am focusing only on bug reports for now until I have greater 
>> > availability. However, all feedback will be considered when further 
>> > development takes places. 
>> > 
>> > The code needs a full review for consistency after the last major 
>> > refactoring in which fields were renamed among other changes, before 
>> new 
>> > features can be added.
>> > 
>>
>

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

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Florian,

That is a new feature that will be available in the TiddlyWiki core from 
version 5.1.23 and is currently available in the pre-release

https://tiddlywiki.com/prerelease/
Cheers,

Saq

On Thursday, September 17, 2020 at 4:50:21 PM UTC+2 janflor...@gmail.com 
wrote:

> Saq,
>
> besides the obvious greatness of your Streams plugin, what I really like
> in your demo wiki is the ability to open tiddlers from the search bar by
> hitting Enter. How did you achieve that/how can one implement that in
> another wiki?
>
> It doesn't seem to be included in your plugins...
>
> Regards,
> Florian
>
> Am 04.07.20 um 07:39 schrieb Saq Imtiaz:
> > Please post your feedback and any issues for Streams here or on github: 
> > https://github.com/saqimtiaz/streams
> > 
> > Demo: https://saqimtiaz.github.io/sq-tw/streams.html
> > Before posting a bug report please make sure you have the latest version 
> of 
> > the plugin from the above link.
> > 
> > Previous thread and background: 
> > 
> https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/KeVDndcnY0g%5B1-25%5D
> > 
> > I am focusing only on bug reports for now until I have greater 
> > availability. However, all feedback will be considered when further 
> > development takes places. 
> > 
> > The code needs a full review for consistency after the last major 
> > refactoring in which fields were renamed among other changes, before new 
> > features can be added.
> > 
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ebbe153f-7eb2-471e-a6ee-7909d4c82465n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Florian Kohrt]

Saq,

besides the obvious greatness of your Streams plugin, what I really like
in your demo wiki is the ability to open tiddlers from the search bar by
hitting Enter. How did you achieve that/how can one implement that in
another wiki?

It doesn't seem to be included in your plugins...

Regards,
Florian

Am 04.07.20 um 07:39 schrieb Saq Imtiaz:
> Please post your feedback and any issues for Streams here or on github: 
> https://github.com/saqimtiaz/streams
> 
> Demo: https://saqimtiaz.github.io/sq-tw/streams.html
> Before posting a bug report please make sure you have the latest version of 
> the plugin from the above link.
> 
> Previous thread and background: 
> https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/KeVDndcnY0g%5B1-25%5D
> 
> I am focusing only on bug reports for now until I have greater 
> availability. However, all feedback will be considered when further 
> development takes places. 
> 
> The code needs a full review for consistency after the last major 
> refactoring in which fields were renamed among other changes, before new 
> features can be added.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5247c889-55a5-e79f-875e-87872cf14cd1%40anche.no.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Mike, 
Have a look at the following link for a macro that will create a static 
HTML representation of any stream, regardless of depth:
https://saqimtiaz.github.io/sq-tw/streams.html#Working%20with%20streams%20tiddlers

Regarding exiting edit mode when clicking outside the node, this has come 
up before.
However, it would create its own set of usability issues as it's a pretty 
common workflow for some to refer or copy content from other tiddlers while 
editing a node, or even have two nodes open for editing in two different 
tiddlers at the same time 

I welcome any ideas that make it easier to exit editing, while still 
allowing the above mentioned workflow and not adding visual clutter 
One option could be a context menu option, though that would still be two 
clicks of the mouse.

Cheers,
Saq
On Thursday, September 17, 2020 at 4:18:44 PM UTC+2 mwik...@gmail.com wrote:

> Hi Saq,
>
> I really like this utility and have immediately incorporated it into my 
> daily log wiki as I wanted to separate things out into tasks anyway and 
> this does it perfectly including a built in time stamp.
>
> Some feedback though. Is there a way to change mouse interaction such that 
> the edit window closes if you left click anywhere but the edit window? I 
> find myself caught with the edit window stuck open after clicking somewhere 
> and it loses focus. Then there is no way to close the edit field via mouse 
> and the esc key doesn't work to close it so I have to click inside then 
> switch to the keyboard to close it. It makes for a lot of UI 
> input-mode-switching.
>
> I like the idea of using this in different contexts for to-do list (with 
> checkboxes) and per-paragraph (with some formatting buttons) editors but it 
> will take me a while of head-scratching before I figure out how to change 
> your existing template. In the meanwhile, I've managed to make a template 
> that will at least list streams as regular uneditable bullets to include in 
> a weekly summary. I've just arbitrarily made it go 8 levels deep by a 
> brute-force repetition. I'm not sure there is a way to adjust to the actual 
> depth of the bullet indentations (and detect possible infinite loops ... 
> not automatically possible but certainly possible with hand editing).
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *<$link to={{!!title}}> <$transclude field="caption"> <$view 
> field="title"/><$list 
> filter="[list[!!stream-list]!is[missing]]"> <$transclude 
> mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
> <$transclude mode="block"/> <$list 
> filter="[list[!!stream-list]!is[missing]]"> <$transclude 
> mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
> <$transclude mode="block"/> <$list 
> filter="[list[!!stream-list]!is[missing]]"> <$transclude 
> mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
> <$transclude mode="block"/> <$list 
> filter="[list[!!stream-list]!is[missing]]"> <$transclude 
> mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
> <$transclude mode="block"/>   
>  
> *
>
> /Mike
>
> On Wednesday, September 16, 2020 at 9:50:37 AM UTC-3 saq.i...@gmail.com 
> wrote:
>
>> New Streams update (0.1.15).
>>
>> Please backup your wiki before updating and test carefully before using 
>> with important data.
>>
>> *Changes:*
>>
>>- Keyboard shortcuts are now configurable from the Control Panel 
>>
>> 
>>
>>- You can now add custom keyboard shortcuts 
>>
>> 
>>  
>>without editing any plugin shadow tiddlers.
>>
>>- This compliments the already existing ability to add custom context 
>>   menu items 
>>   
>> 
>>   
>>   - You can also override macros from 
>>$:/plugins/sq/streams/action-macros to customize behaviour, by adding 
>>tiddlers with macros with the same names, and tagging these tiddlers with 
>>$:/tags/streams/user-actionmacros
>>
>> Regular users can just upgrade the plugin as usual. However, if you have 
>> edited shadow tiddlers from the plugin to make your own customizations, you 
>> will likely need to delete and re-do those changes.
>>  
>> https://saqimtiaz.github.io/sq-tw/streams.html
>>   
>> Cheers,
>> Saq
>>
>

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

[tw5] Re: [ Streams ] : feedback and issues

[Michael Wiktowy]

Hi Saq,

I really like this utility and have immediately incorporated it into my 
daily log wiki as I wanted to separate things out into tasks anyway and 
this does it perfectly including a built in time stamp.

Some feedback though. Is there a way to change mouse interaction such that 
the edit window closes if you left click anywhere but the edit window? I 
find myself caught with the edit window stuck open after clicking somewhere 
and it loses focus. Then there is no way to close the edit field via mouse 
and the esc key doesn't work to close it so I have to click inside then 
switch to the keyboard to close it. It makes for a lot of UI 
input-mode-switching.

I like the idea of using this in different contexts for to-do list (with 
checkboxes) and per-paragraph (with some formatting buttons) editors but it 
will take me a while of head-scratching before I figure out how to change 
your existing template. In the meanwhile, I've managed to make a template 
that will at least list streams as regular uneditable bullets to include in 
a weekly summary. I've just arbitrarily made it go 8 levels deep by a 
brute-force repetition. I'm not sure there is a way to adjust to the actual 
depth of the bullet indentations (and detect possible infinite loops ... 
not automatically possible but certainly possible with hand editing).






























*<$link to={{!!title}}> <$transclude field="caption"> <$view 
field="title"/><$list 
filter="[list[!!stream-list]!is[missing]]"> <$transclude 
mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
<$transclude mode="block"/> <$list 
filter="[list[!!stream-list]!is[missing]]"> <$transclude 
mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
<$transclude mode="block"/> <$list 
filter="[list[!!stream-list]!is[missing]]"> <$transclude 
mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
<$transclude mode="block"/> <$list 
filter="[list[!!stream-list]!is[missing]]"> <$transclude 
mode="block"/> <$list filter="[list[!!stream-list]!is[missing]]"> 
<$transclude mode="block"/>   
 
*

/Mike

On Wednesday, September 16, 2020 at 9:50:37 AM UTC-3 saq.i...@gmail.com 
wrote:

> New Streams update (0.1.15).
>
> Please backup your wiki before updating and test carefully before using 
> with important data.
>
> *Changes:*
>
>- Keyboard shortcuts are now configurable from the Control Panel 
>
> 
>
>- You can now add custom keyboard shortcuts 
>
> 
>  
>without editing any plugin shadow tiddlers.
>
>- This compliments the already existing ability to add custom context 
>   menu items 
>   
> 
>   
>   - You can also override macros from 
>$:/plugins/sq/streams/action-macros to customize behaviour, by adding 
>tiddlers with macros with the same names, and tagging these tiddlers with 
>$:/tags/streams/user-actionmacros
>
> Regular users can just upgrade the plugin as usual. However, if you have 
> edited shadow tiddlers from the plugin to make your own customizations, you 
> will likely need to delete and re-do those changes.
>  
> https://saqimtiaz.github.io/sq-tw/streams.html
>   
> Cheers,
> Saq
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9ed97416-ff13-46ef-a2e0-08230967ad2en%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

New Streams update (0.1.15).

Please backup your wiki before updating and test carefully before using 
with important data.

*Changes:*

   - Keyboard shortcuts are now configurable from the Control Panel 
   

   
   - You can now add custom keyboard shortcuts 
   

 
   without editing any plugin shadow tiddlers.
   
   - This compliments the already existing ability to add custom context 
  menu items 
  

  
  - You can also override macros from 
   $:/plugins/sq/streams/action-macros to customize behaviour, by adding 
   tiddlers with macros with the same names, and tagging these tiddlers with 
   $:/tags/streams/user-actionmacros

Regular users can just upgrade the plugin as usual. However, if you have 
edited shadow tiddlers from the plugin to make your own customizations, you 
will likely need to delete and re-do those changes.
 
https://saqimtiaz.github.io/sq-tw/streams.html
  
Cheers,
Saq

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

Re: [tw5] Re: [ Streams ] : feedback and issues

[TW Tones]

Saw

That is exactly what I am talking about. Just before Relink. Was released I 
investigated the editor rename process.

However there are other ways to rename and I was being thorough.

Regards
Tony

On Friday, 4 September 2020 at 16:51:56 UTC+10 saq.i...@gmail.com wrote:

> @Tony we seem to be talking about very different things. What is relevant 
> and under discussion here is customizing the EditTemplate UI to offer a 
> user interface for additional options related to renaming. The answer 
> probably lies in adding a new edit template segment via a new tiddler which 
> is displayed after $:/core/ui/EditTemplate/title
>
> Streams has code for executing actions on tiddler rename (unpublished) and 
> on tiddler delete (see 
> https://github.com/saqimtiaz/streams/blob/master/plugins/streams/delete-hook/actions.tid)
>  
> that may be of interest to you. If you wish to discuss that, please start a 
> new thread.
> Thank you.
>
> Saq
>
>
> On Friday, September 4, 2020 at 2:25:59 AM UTC+2, TW Tones wrote:
>>
>> Saq,
>>
>> You know more than me I am sure, but here is what I know on this matter.
>>
>> Re-hackability in the rename, 1st it depends on the draft mechanism. Last 
>> time I looked at it Relink uses a hack of its own, when it would be better 
>> if tiddlywiki provisioned the hack for such tools. Eg a tag that will 
>> include and have access to the rename process the current and new tiddler 
>> at a minimum. Thus on rename a conditional process can be activated and 
>> apply the rename according to its own rules. Ideally this would be a 
>> generic solution. eg on rename trigger a mechanism that any solution can 
>> add to. eg $:/tags/on-rename-actions.
>>
>> The next issue is renaming by other means. Ie copy and delete or 
>> WidgetMessage: 
>> tm-rename-tiddler 
>> 
>>
>> Jeremy has a plan to expose the the actions behind WidgetMessages to 
>> increase hackability which should allow the designer to install a custom 
>> response to renames. However I am not sure how often tm-rename-tiddler is 
>> used.
>>
>> I have a project I need to push forward that allows custom actions to be 
>> included behind all existing buttons, this allows any button to be used as 
>> a trigger. In this case the done/save button on a tiddler can trigger an 
>> action to test for and handle the tiddler rename case. However to handle 
>> this comprehensively one needs to deal with other buttons that trigger the 
>> save process including those in other plugins.
>>
>> Regards
>> Tones
>>
>> On Thursday, 3 September 2020 21:21:26 UTC+10, Saq Imtiaz wrote:
>>>
>>> @keelan your description is in accordance with what I tried to express 
>>> in my last message. The UI part might vary, as I haven't looked into how 
>>> much flexibility there is to extend that part of the edit template, seeing 
>>> as how Relink already customizes it. I'll investigate once I get the time 
>>> and see what our options are.
>>>
>>>
>>> On Thursday, September 3, 2020 at 1:05:09 PM UTC+2 keela...@gmail.com 
>>> wrote:
>>>
 @Saq I'm not quite sure I'm following, though I imagine you're correct. 
 Let me rephrase to make sure I'm tracking with you.

 Are you suggesting that, like the relink plugin which triggers an 
 option to rename every mention of this tiddler once someone attempts to 
 rename it, Streams could (and should) suggest renaming the subnodes with 
 that same trigger? In this case, if I choose to rename a stream of nodes, 
 I 
 would get a check box for the relink plugin *and *some form of 
 checkbox asking if I wanted to change the naming scheme of all stream 
 nodes 
 that are "downstream" from this one.

 If that's what you're suggesting, I agree with your point. That does 
 seem to make more sense than adding something in the context menu. It 
 seems 
 to create a more obvious user flow for renaming. That's the way I rename 
 things currently. I click on the bullet that I want to rename, enter edit 
 mode on the displayed tiddler, and then rename, making sure I have the 
 relink checkbox marked. It would make sense to also add a simple checkbox 
 here that would offer to rename all downstream tiddlers as well. This way, 
 a branch can become its own stream but stay a part of the initial stream 
 as 
 well. It would make it searchable separately via the new method you've 
 established. And, if you started at the very beginning of a stream, it 
 would still rename everything downstream, changing the naming scheme on an 
 entire thread.

 If I'm understanding you correctly, this is a better approach.

 On Wednesday, September 2, 2020 at 5:01:42 PM UTC-5 saq.i...@gmail.com 
 wrote:

> @Keelan regarding the rename handling we discussed, it occurs to me 
> that it may make more sense to trigger this via the renaming of a tiddler 
> the 

Re: [tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Tony we seem to be talking about very different things. What is relevant 
and under discussion here is customizing the EditTemplate UI to offer a 
user interface for additional options related to renaming. The answer 
probably lies in adding a new edit template segment via a new tiddler which 
is displayed after $:/core/ui/EditTemplate/title

Streams has code for executing actions on tiddler rename (unpublished) and 
on tiddler delete (see 
https://github.com/saqimtiaz/streams/blob/master/plugins/streams/delete-hook/actions.tid)
 
that may be of interest to you. If you wish to discuss that, please start a 
new thread.
Thank you.

Saq

On Friday, September 4, 2020 at 2:25:59 AM UTC+2, TW Tones wrote:
>
> Saq,
>
> You know more than me I am sure, but here is what I know on this matter.
>
> Re-hackability in the rename, 1st it depends on the draft mechanism. Last 
> time I looked at it Relink uses a hack of its own, when it would be better 
> if tiddlywiki provisioned the hack for such tools. Eg a tag that will 
> include and have access to the rename process the current and new tiddler 
> at a minimum. Thus on rename a conditional process can be activated and 
> apply the rename according to its own rules. Ideally this would be a 
> generic solution. eg on rename trigger a mechanism that any solution can 
> add to. eg $:/tags/on-rename-actions.
>
> The next issue is renaming by other means. Ie copy and delete or 
> WidgetMessage: 
> tm-rename-tiddler 
> 
>
> Jeremy has a plan to expose the the actions behind WidgetMessages to 
> increase hackability which should allow the designer to install a custom 
> response to renames. However I am not sure how often tm-rename-tiddler is 
> used.
>
> I have a project I need to push forward that allows custom actions to be 
> included behind all existing buttons, this allows any button to be used as 
> a trigger. In this case the done/save button on a tiddler can trigger an 
> action to test for and handle the tiddler rename case. However to handle 
> this comprehensively one needs to deal with other buttons that trigger the 
> save process including those in other plugins.
>
> Regards
> Tones
>
> On Thursday, 3 September 2020 21:21:26 UTC+10, Saq Imtiaz wrote:
>>
>> @keelan your description is in accordance with what I tried to express in 
>> my last message. The UI part might vary, as I haven't looked into how much 
>> flexibility there is to extend that part of the edit template, seeing as 
>> how Relink already customizes it. I'll investigate once I get the time and 
>> see what our options are.
>>
>>
>> On Thursday, September 3, 2020 at 1:05:09 PM UTC+2 keela...@gmail.com 
>> wrote:
>>
>>> @Saq I'm not quite sure I'm following, though I imagine you're correct. 
>>> Let me rephrase to make sure I'm tracking with you.
>>>
>>> Are you suggesting that, like the relink plugin which triggers an option 
>>> to rename every mention of this tiddler once someone attempts to rename it, 
>>> Streams could (and should) suggest renaming the subnodes with that same 
>>> trigger? In this case, if I choose to rename a stream of nodes, I would get 
>>> a check box for the relink plugin *and *some form of checkbox asking if 
>>> I wanted to change the naming scheme of all stream nodes that are 
>>> "downstream" from this one.
>>>
>>> If that's what you're suggesting, I agree with your point. That does 
>>> seem to make more sense than adding something in the context menu. It seems 
>>> to create a more obvious user flow for renaming. That's the way I rename 
>>> things currently. I click on the bullet that I want to rename, enter edit 
>>> mode on the displayed tiddler, and then rename, making sure I have the 
>>> relink checkbox marked. It would make sense to also add a simple checkbox 
>>> here that would offer to rename all downstream tiddlers as well. This way, 
>>> a branch can become its own stream but stay a part of the initial stream as 
>>> well. It would make it searchable separately via the new method you've 
>>> established. And, if you started at the very beginning of a stream, it 
>>> would still rename everything downstream, changing the naming scheme on an 
>>> entire thread.
>>>
>>> If I'm understanding you correctly, this is a better approach.
>>>
>>> On Wednesday, September 2, 2020 at 5:01:42 PM UTC-5 saq.i...@gmail.com 
>>> wrote:
>>>
 @Keelan regarding the rename handling we discussed, it occurs to me 
 that it may make more sense to trigger this via the renaming of a tiddler 
 the regular way via the edit template, rather than via renaming of a node 
 via streams. 

 Otherwise, there would be no mechanism to handle renaming the subnodes 
 when the stream-root tiddler is renamed. Whereas a node can always be 
 opened as a tiddler and renamed that way. 

 What do you think?

 On Tuesday, August 25, 2020 at 2:44:07 PM UTC+2 keela...@gmail.com 
 wrote:

Re: [tw5] Re: [ Streams ] : feedback and issues

[TW Tones]

Saq,

You know more than me I am sure, but here is what I know on this matter.

Re-hackability in the rename, 1st it depends on the draft mechanism. Last 
time I looked at it Relink uses a hack of its own, when it would be better 
if tiddlywiki provisioned the hack for such tools. Eg a tag that will 
include and have access to the rename process the current and new tiddler 
at a minimum. Thus on rename a conditional process can be activated and 
apply the rename according to its own rules. Ideally this would be a 
generic solution. eg on rename trigger a mechanism that any solution can 
add to. eg $:/tags/on-rename-actions.

The next issue is renaming by other means. Ie copy and delete or WidgetMessage: 
tm-rename-tiddler 


Jeremy has a plan to expose the the actions behind WidgetMessages to 
increase hackability which should allow the designer to install a custom 
response to renames. However I am not sure how often tm-rename-tiddler is 
used.

I have a project I need to push forward that allows custom actions to be 
included behind all existing buttons, this allows any button to be used as 
a trigger. In this case the done/save button on a tiddler can trigger an 
action to test for and handle the tiddler rename case. However to handle 
this comprehensively one needs to deal with other buttons that trigger the 
save process including those in other plugins.

Regards
Tones

On Thursday, 3 September 2020 21:21:26 UTC+10, Saq Imtiaz wrote:
>
> @keelan your description is in accordance with what I tried to express in 
> my last message. The UI part might vary, as I haven't looked into how much 
> flexibility there is to extend that part of the edit template, seeing as 
> how Relink already customizes it. I'll investigate once I get the time and 
> see what our options are.
>
>
> On Thursday, September 3, 2020 at 1:05:09 PM UTC+2 keela...@gmail.com 
> wrote:
>
>> @Saq I'm not quite sure I'm following, though I imagine you're correct. 
>> Let me rephrase to make sure I'm tracking with you.
>>
>> Are you suggesting that, like the relink plugin which triggers an option 
>> to rename every mention of this tiddler once someone attempts to rename it, 
>> Streams could (and should) suggest renaming the subnodes with that same 
>> trigger? In this case, if I choose to rename a stream of nodes, I would get 
>> a check box for the relink plugin *and *some form of checkbox asking if 
>> I wanted to change the naming scheme of all stream nodes that are 
>> "downstream" from this one.
>>
>> If that's what you're suggesting, I agree with your point. That does seem 
>> to make more sense than adding something in the context menu. It seems to 
>> create a more obvious user flow for renaming. That's the way I rename 
>> things currently. I click on the bullet that I want to rename, enter edit 
>> mode on the displayed tiddler, and then rename, making sure I have the 
>> relink checkbox marked. It would make sense to also add a simple checkbox 
>> here that would offer to rename all downstream tiddlers as well. This way, 
>> a branch can become its own stream but stay a part of the initial stream as 
>> well. It would make it searchable separately via the new method you've 
>> established. And, if you started at the very beginning of a stream, it 
>> would still rename everything downstream, changing the naming scheme on an 
>> entire thread.
>>
>> If I'm understanding you correctly, this is a better approach.
>>
>> On Wednesday, September 2, 2020 at 5:01:42 PM UTC-5 saq.i...@gmail.com 
>> wrote:
>>
>>> @Keelan regarding the rename handling we discussed, it occurs to me that 
>>> it may make more sense to trigger this via the renaming of a tiddler the 
>>> regular way via the edit template, rather than via renaming of a node via 
>>> streams. 
>>>
>>> Otherwise, there would be no mechanism to handle renaming the subnodes 
>>> when the stream-root tiddler is renamed. Whereas a node can always be 
>>> opened as a tiddler and renamed that way. 
>>>
>>> What do you think?
>>>
>>> On Tuesday, August 25, 2020 at 2:44:07 PM UTC+2 keela...@gmail.com 
>>> wrote:
>>>
 That first option to rename if it shares the same prefix.

 I can see creating a steam in a particular topic, realizing it would 
 need a different title, and wanting to maintain the semantic connection 
 with all of the subnodes for the purpose of search. However, I would not 
 want to force a rename on one that I had already broken out with it's own 
 name. 

 On Mon, Aug 24, 2020, 4:41 PM Saq Imtiaz  wrote:

> @Keelan
>
> Is that something I could add to the context menu? I know you've set 
>> it up so users can create their own menu items.
>
>
> Yes, that should be doable. 
> There is some info here: 
> https://saqimtiaz.github.io/sq-tw/streams.html#Extending%20the%20Context%20Menu
>
> I can probably help you get the actions 

Re: [tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

Very good. I do think that makes more sense. 

On Thursday, September 3, 2020 at 6:21:26 AM UTC-5 saq.i...@gmail.com wrote:

> @keelan your description is in accordance with what I tried to express in 
> my last message. The UI part might vary, as I haven't looked into how much 
> flexibility there is to extend that part of the edit template, seeing as 
> how Relink already customizes it. I'll investigate once I get the time and 
> see what our options are.
>
>
> On Thursday, September 3, 2020 at 1:05:09 PM UTC+2 keela...@gmail.com 
> wrote:
>
>> @Saq I'm not quite sure I'm following, though I imagine you're correct. 
>> Let me rephrase to make sure I'm tracking with you.
>>
>> Are you suggesting that, like the relink plugin which triggers an option 
>> to rename every mention of this tiddler once someone attempts to rename it, 
>> Streams could (and should) suggest renaming the subnodes with that same 
>> trigger? In this case, if I choose to rename a stream of nodes, I would get 
>> a check box for the relink plugin *and *some form of checkbox asking if 
>> I wanted to change the naming scheme of all stream nodes that are 
>> "downstream" from this one.
>>
>> If that's what you're suggesting, I agree with your point. That does seem 
>> to make more sense than adding something in the context menu. It seems to 
>> create a more obvious user flow for renaming. That's the way I rename 
>> things currently. I click on the bullet that I want to rename, enter edit 
>> mode on the displayed tiddler, and then rename, making sure I have the 
>> relink checkbox marked. It would make sense to also add a simple checkbox 
>> here that would offer to rename all downstream tiddlers as well. This way, 
>> a branch can become its own stream but stay a part of the initial stream as 
>> well. It would make it searchable separately via the new method you've 
>> established. And, if you started at the very beginning of a stream, it 
>> would still rename everything downstream, changing the naming scheme on an 
>> entire thread.
>>
>> If I'm understanding you correctly, this is a better approach.
>>
>> On Wednesday, September 2, 2020 at 5:01:42 PM UTC-5 saq.i...@gmail.com 
>> wrote:
>>
>>> @Keelan regarding the rename handling we discussed, it occurs to me that 
>>> it may make more sense to trigger this via the renaming of a tiddler the 
>>> regular way via the edit template, rather than via renaming of a node via 
>>> streams. 
>>>
>>> Otherwise, there would be no mechanism to handle renaming the subnodes 
>>> when the stream-root tiddler is renamed. Whereas a node can always be 
>>> opened as a tiddler and renamed that way. 
>>>
>>> What do you think?
>>>
>>> On Tuesday, August 25, 2020 at 2:44:07 PM UTC+2 keela...@gmail.com 
>>> wrote:
>>>
 That first option to rename if it shares the same prefix.

 I can see creating a steam in a particular topic, realizing it would 
 need a different title, and wanting to maintain the semantic connection 
 with all of the subnodes for the purpose of search. However, I would not 
 want to force a rename on one that I had already broken out with it's own 
 name. 

 On Mon, Aug 24, 2020, 4:41 PM Saq Imtiaz  wrote:

> @Keelan
>
> Is that something I could add to the context menu? I know you've set 
>> it up so users can create their own menu items.
>
>
> Yes, that should be doable. 
> There is some info here: 
> https://saqimtiaz.github.io/sq-tw/streams.html#Extending%20the%20Context%20Menu
>
> I can probably help you get the actions right. Are you thinking an 
> option that renames a node, and the subnodes *if* their titles begin with 
> the node title?
>
> Or something to use after you've already renamed a node and the 
> subnodes no longer match in terms of titles.
>
> -- 
>
 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/1jTwdmq8cgI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> tiddlywiki+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/641a43dd-fb43-499f-8468-19c294358dd8n%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/cb2cc03e-139e-42d4-972f-37fba51635ben%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@keelan your description is in accordance with what I tried to express in 
my last message. The UI part might vary, as I haven't looked into how much 
flexibility there is to extend that part of the edit template, seeing as 
how Relink already customizes it. I'll investigate once I get the time and 
see what our options are.


On Thursday, September 3, 2020 at 1:05:09 PM UTC+2 keela...@gmail.com wrote:

> @Saq I'm not quite sure I'm following, though I imagine you're correct. 
> Let me rephrase to make sure I'm tracking with you.
>
> Are you suggesting that, like the relink plugin which triggers an option 
> to rename every mention of this tiddler once someone attempts to rename it, 
> Streams could (and should) suggest renaming the subnodes with that same 
> trigger? In this case, if I choose to rename a stream of nodes, I would get 
> a check box for the relink plugin *and *some form of checkbox asking if I 
> wanted to change the naming scheme of all stream nodes that are 
> "downstream" from this one.
>
> If that's what you're suggesting, I agree with your point. That does seem 
> to make more sense than adding something in the context menu. It seems to 
> create a more obvious user flow for renaming. That's the way I rename 
> things currently. I click on the bullet that I want to rename, enter edit 
> mode on the displayed tiddler, and then rename, making sure I have the 
> relink checkbox marked. It would make sense to also add a simple checkbox 
> here that would offer to rename all downstream tiddlers as well. This way, 
> a branch can become its own stream but stay a part of the initial stream as 
> well. It would make it searchable separately via the new method you've 
> established. And, if you started at the very beginning of a stream, it 
> would still rename everything downstream, changing the naming scheme on an 
> entire thread.
>
> If I'm understanding you correctly, this is a better approach.
>
> On Wednesday, September 2, 2020 at 5:01:42 PM UTC-5 saq.i...@gmail.com 
> wrote:
>
>> @Keelan regarding the rename handling we discussed, it occurs to me that 
>> it may make more sense to trigger this via the renaming of a tiddler the 
>> regular way via the edit template, rather than via renaming of a node via 
>> streams. 
>>
>> Otherwise, there would be no mechanism to handle renaming the subnodes 
>> when the stream-root tiddler is renamed. Whereas a node can always be 
>> opened as a tiddler and renamed that way. 
>>
>> What do you think?
>>
>> On Tuesday, August 25, 2020 at 2:44:07 PM UTC+2 keela...@gmail.com wrote:
>>
>>> That first option to rename if it shares the same prefix.
>>>
>>> I can see creating a steam in a particular topic, realizing it would 
>>> need a different title, and wanting to maintain the semantic connection 
>>> with all of the subnodes for the purpose of search. However, I would not 
>>> want to force a rename on one that I had already broken out with it's own 
>>> name. 
>>>
>>> On Mon, Aug 24, 2020, 4:41 PM Saq Imtiaz  wrote:
>>>
 @Keelan

 Is that something I could add to the context menu? I know you've set it 
> up so users can create their own menu items.


 Yes, that should be doable. 
 There is some info here: 
 https://saqimtiaz.github.io/sq-tw/streams.html#Extending%20the%20Context%20Menu

 I can probably help you get the actions right. Are you thinking an 
 option that renames a node, and the subnodes *if* their titles begin with 
 the node title?

 Or something to use after you've already renamed a node and the 
 subnodes no longer match in terms of titles.

 -- 

>>> 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/1jTwdmq8cgI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 tiddlywiki+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/641a43dd-fb43-499f-8468-19c294358dd8n%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/eccce8cc-f5e9-4513-b69b-c712785c482an%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

@Saq I'm not quite sure I'm following, though I imagine you're correct. Let 
me rephrase to make sure I'm tracking with you.

Are you suggesting that, like the relink plugin which triggers an option to 
rename every mention of this tiddler once someone attempts to rename it, 
Streams could (and should) suggest renaming the subnodes with that same 
trigger? In this case, if I choose to rename a stream of nodes, I would get 
a check box for the relink plugin *and *some form of checkbox asking if I 
wanted to change the naming scheme of all stream nodes that are 
"downstream" from this one.

If that's what you're suggesting, I agree with your point. That does seem 
to make more sense than adding something in the context menu. It seems to 
create a more obvious user flow for renaming. That's the way I rename 
things currently. I click on the bullet that I want to rename, enter edit 
mode on the displayed tiddler, and then rename, making sure I have the 
relink checkbox marked. It would make sense to also add a simple checkbox 
here that would offer to rename all downstream tiddlers as well. This way, 
a branch can become its own stream but stay a part of the initial stream as 
well. It would make it searchable separately via the new method you've 
established. And, if you started at the very beginning of a stream, it 
would still rename everything downstream, changing the naming scheme on an 
entire thread.

If I'm understanding you correctly, this is a better approach.

On Wednesday, September 2, 2020 at 5:01:42 PM UTC-5 saq.i...@gmail.com 
wrote:

> @Keelan regarding the rename handling we discussed, it occurs to me that 
> it may make more sense to trigger this via the renaming of a tiddler the 
> regular way via the edit template, rather than via renaming of a node via 
> streams. 
>
> Otherwise, there would be no mechanism to handle renaming the subnodes 
> when the stream-root tiddler is renamed. Whereas a node can always be 
> opened as a tiddler and renamed that way. 
>
> What do you think?
>
> On Tuesday, August 25, 2020 at 2:44:07 PM UTC+2 keela...@gmail.com wrote:
>
>> That first option to rename if it shares the same prefix.
>>
>> I can see creating a steam in a particular topic, realizing it would need 
>> a different title, and wanting to maintain the semantic connection with all 
>> of the subnodes for the purpose of search. However, I would not want to 
>> force a rename on one that I had already broken out with it's own name. 
>>
>> On Mon, Aug 24, 2020, 4:41 PM Saq Imtiaz  wrote:
>>
>>> @Keelan
>>>
>>> Is that something I could add to the context menu? I know you've set it 
 up so users can create their own menu items.
>>>
>>>
>>> Yes, that should be doable. 
>>> There is some info here: 
>>> https://saqimtiaz.github.io/sq-tw/streams.html#Extending%20the%20Context%20Menu
>>>
>>> I can probably help you get the actions right. Are you thinking an 
>>> option that renames a node, and the subnodes *if* their titles begin with 
>>> the node title?
>>>
>>> Or something to use after you've already renamed a node and the subnodes 
>>> no longer match in terms of titles.
>>>
>>> -- 
>>>
>> 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/1jTwdmq8cgI/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> tiddlywiki+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/641a43dd-fb43-499f-8468-19c294358dd8n%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/1d3f7d7e-77fc-44d6-b8cf-1b0792db74c3n%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Keelan regarding the rename handling we discussed, it occurs to me that it 
may make more sense to trigger this via the renaming of a tiddler the 
regular way via the edit template, rather than via renaming of a node via 
streams. 

Otherwise, there would be no mechanism to handle renaming the subnodes when 
the stream-root tiddler is renamed. Whereas a node can always be opened as 
a tiddler and renamed that way. 

What do you think?

On Tuesday, August 25, 2020 at 2:44:07 PM UTC+2 keela...@gmail.com wrote:

> That first option to rename if it shares the same prefix.
>
> I can see creating a steam in a particular topic, realizing it would need 
> a different title, and wanting to maintain the semantic connection with all 
> of the subnodes for the purpose of search. However, I would not want to 
> force a rename on one that I had already broken out with it's own name. 
>
> On Mon, Aug 24, 2020, 4:41 PM Saq Imtiaz  wrote:
>
>> @Keelan
>>
>> Is that something I could add to the context menu? I know you've set it 
>>> up so users can create their own menu items.
>>
>>
>> Yes, that should be doable. 
>> There is some info here: 
>> https://saqimtiaz.github.io/sq-tw/streams.html#Extending%20the%20Context%20Menu
>>
>> I can probably help you get the actions right. Are you thinking an option 
>> that renames a node, and the subnodes *if* their titles begin with the node 
>> title?
>>
>> Or something to use after you've already renamed a node and the subnodes 
>> no longer match in terms of titles.
>>
>> -- 
>>
> 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/1jTwdmq8cgI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/641a43dd-fb43-499f-8468-19c294358dd8n%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/95ef0ab5-84a7-4ae7-9777-d28dd75d0680n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Thank you Keelan.

Please let me know if you run into any issues.

On Saturday, August 29, 2020 at 4:15:10 PM UTC+2 keela...@gmail.com wrote:

> Just took it for a spin. I'm having no errors so far, and though subtle, 
> it's a great update. The split-at-caret behavior is much more intuitive for 
> me now. I much prefer the new node being created above the existing node if 
> the caret is at the beginning. That effectively moves the current node down 
> one in the order (with all of it's sub-nodes) and presents a new node in 
> the order above it. That's precisely the behavior I expect.
>
> I like having the option to confirm split or merge workflow as a 
> configuration option, though that will be a minority use case for me. 
>
> And, the improvement for mobile on saving with exit was needed. My tablet 
> also pushes TW5 to a mobile layout, and before this update, attempting to 
> exit a node with my stylus was convoluted at best. This has made that a 
> much easier action. 
>
> Great update, Saq!
> On Saturday, August 29, 2020 at 5:24:23 AM UTC-5 saq.i...@gmail.com wrote:
>
>> There is an update to Streams (0.1.14) that brings a fair few small 
>> features and changes, and *needs some testing* and feedback.
>> Please backup your wiki before updating and test carefully before using 
>> with important data.
>>
>> New configuration options that toggle settings depending on whether they 
>> are set to yes or no:
>>
>>
>>- *$:/config/sq/streams/split-at-caret* split the text of a node at 
>>the caret position when saving the node with Enter. This is 
>>existing behaviour that can now be toggled.
>>- *$:/config/sq/streams/prompt-split-to-multiple* prompt for 
>>confirmation when splitting a node to multiple nodes, triggered 
>>by Alt+Enter. New feature.
>>- *$:/config/sq/streams/prompt-merge-with-previous* prompt the user 
>>before attempting to merge a node with the previous node, triggered 
>>by Backspace with the caret position at the beginning of the 
>>text. New feature.
>>- *$:/config/sq/streams/exit-on-saving-empty-node *Exit edit mode on 
>>saving an empty node with Enter. Allows exiting edit mode on 
>>mobile. New feature.
>>
>> With split-at-caret set to "yes", saving a node with Enter with the caret 
>> at the start of the text will create a new node above the current node. 
>>
>> Backspace with the caret at the start of a node will attempt to merge 
>> with the previous node, provided it is at the same indent level and has no 
>> child nodes. This is an intentionally simplified and constrained behaviour 
>> intended as an undo to the above split option. By default the user is 
>> prompted for confirmation before merging, this can be disabled by setting 
>> prompt-merge-with-previous to "no"
>>
>> By default, saving a node with Alt+Enter will ask for confirmation before 
>> splitting the text into multiple nodes. The prompt can be disabled by 
>> setting prompt-split-to-multiple to "no"
>>
>> To allow exiting edit mode on mobile devices, set 
>> exit-on-saving-empty-node to "yes". This will exit edit mode when 
>> attempting to save an empty node with Enter. In other words, hit Enter 
>> twice to exit editing.
>>
>>  https://saqimtiaz.github.io/sq-tw/streams.html
>>
>> Cheers,
>> Saq
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/70670f9f-4099-4624-8364-3acdd6423817n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

Just took it for a spin. I'm having no errors so far, and though subtle, 
it's a great update. The split-at-caret behavior is much more intuitive for 
me now. I much prefer the new node being created above the existing node if 
the caret is at the beginning. That effectively moves the current node down 
one in the order (with all of it's sub-nodes) and presents a new node in 
the order above it. That's precisely the behavior I expect.

I like having the option to confirm split or merge workflow as a 
configuration option, though that will be a minority use case for me. 

And, the improvement for mobile on saving with exit was needed. My tablet 
also pushes TW5 to a mobile layout, and before this update, attempting to 
exit a node with my stylus was convoluted at best. This has made that a 
much easier action. 

Great update, Saq!
On Saturday, August 29, 2020 at 5:24:23 AM UTC-5 saq.i...@gmail.com wrote:

> There is an update to Streams (0.1.14) that brings a fair few small 
> features and changes, and *needs some testing* and feedback.
> Please backup your wiki before updating and test carefully before using 
> with important data.
>
> New configuration options that toggle settings depending on whether they 
> are set to yes or no:
>
>
>- *$:/config/sq/streams/split-at-caret* split the text of a node at 
>the caret position when saving the node with Enter. This is 
>existing behaviour that can now be toggled.
>- *$:/config/sq/streams/prompt-split-to-multiple* prompt for 
>confirmation when splitting a node to multiple nodes, triggered 
>by Alt+Enter. New feature.
>- *$:/config/sq/streams/prompt-merge-with-previous* prompt the user 
>before attempting to merge a node with the previous node, triggered 
>by Backspace with the caret position at the beginning of the 
>text. New feature.
>- *$:/config/sq/streams/exit-on-saving-empty-node *Exit edit mode on 
>saving an empty node with Enter. Allows exiting edit mode on 
>mobile. New feature.
>
> With split-at-caret set to "yes", saving a node with Enter with the caret 
> at the start of the text will create a new node above the current node. 
>
> Backspace with the caret at the start of a node will attempt to merge with 
> the previous node, provided it is at the same indent level and has no child 
> nodes. This is an intentionally simplified and constrained behaviour 
> intended as an undo to the above split option. By default the user is 
> prompted for confirmation before merging, this can be disabled by setting 
> prompt-merge-with-previous to "no"
>
> By default, saving a node with Alt+Enter will ask for confirmation before 
> splitting the text into multiple nodes. The prompt can be disabled by 
> setting prompt-split-to-multiple to "no"
>
> To allow exiting edit mode on mobile devices, set 
> exit-on-saving-empty-node to "yes". This will exit edit mode when 
> attempting to save an empty node with Enter. In other words, hit Enter 
> twice to exit editing.
>
>  https://saqimtiaz.github.io/sq-tw/streams.html
>
> Cheers,
> Saq
>
>

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

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

There is an update to Streams (0.1.14) that brings a fair few small 
features and changes, and *needs some testing* and feedback.
Please backup your wiki before updating and test carefully before using 
with important data.

New configuration options that toggle settings depending on whether they 
are set to yes or no:


   - *$:/config/sq/streams/split-at-caret* split the text of a node at the 
   caret position when saving the node with Enter. This is existing 
   behaviour that can now be toggled.
   - *$:/config/sq/streams/prompt-split-to-multiple* prompt for 
   confirmation when splitting a node to multiple nodes, triggered 
   by Alt+Enter. New feature.
   - *$:/config/sq/streams/prompt-merge-with-previous* prompt the user 
   before attempting to merge a node with the previous node, triggered 
   by Backspace with the caret position at the beginning of the 
   text. New feature.
   - *$:/config/sq/streams/exit-on-saving-empty-node *Exit edit mode on 
   saving an empty node with Enter. Allows exiting edit mode on 
   mobile. New feature.
   
With split-at-caret set to "yes", saving a node with Enter with the caret 
at the start of the text will create a new node above the current node. 

Backspace with the caret at the start of a node will attempt to merge with 
the previous node, provided it is at the same indent level and has no child 
nodes. This is an intentionally simplified and constrained behaviour 
intended as an undo to the above split option. By default the user is 
prompted for confirmation before merging, this can be disabled by setting 
prompt-merge-with-previous to "no"

By default, saving a node with Alt+Enter will ask for confirmation before 
splitting the text into multiple nodes. The prompt can be disabled by 
setting prompt-split-to-multiple to "no"

To allow exiting edit mode on mobile devices, set exit-on-saving-empty-node 
to "yes". This will exit edit mode when attempting to save an empty node 
with Enter. In other words, hit Enter twice to exit editing.

 https://saqimtiaz.github.io/sq-tw/streams.html

Cheers,
Saq

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6057bfe5-a127-4d1c-8c56-25d13339bab8n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Ken Gray]

I really like this.  I'm wondering though, if it is possible to get some 
editor toolbar to show up so that I can do some things like what I do with 
Code Mirror.  Not the general wiki formatting stuff (!  *  -  etc.) but the 
more complicated stuff like @@color:black;background-color:goldenrod;  Test 
Text@@  stuff.

On Friday, July 3, 2020 at 11:29:53 AM UTC-4 saq.i...@gmail.com wrote:

> Please post your feedback and any issues for Streams here or on github: 
> https://github.com/saqimtiaz/streams
>
> Demo: https://saqimtiaz.github.io/sq-tw/streams.html
> Before posting a bug report please make sure you have the latest version 
> of the plugin from the above link.
>
> Previous thread and background: 
> https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/KeVDndcnY0g%5B1-25%5D
>
> I am focusing only on bug reports for now until I have greater 
> availability. However, all feedback will be considered when further 
> development takes places. 
>
> The code needs a full review for consistency after the last major 
> refactoring in which fields were renamed among other changes, before new 
> features can be added.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/27106b2e-2a2a-4279-8772-a5c1c0b53277n%40googlegroups.com.

Re: [tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

That first option to rename if it shares the same prefix.

I can see creating a steam in a particular topic, realizing it would need a
different title, and wanting to maintain the semantic connection with all
of the subnodes for the purpose of search. However, I would not want to
force a rename on one that I had already broken out with it's own name.

On Mon, Aug 24, 2020, 4:41 PM Saq Imtiaz  wrote:

> @Keelan
>
> Is that something I could add to the context menu? I know you've set it up
>> so users can create their own menu items.
>
>
> Yes, that should be doable.
> There is some info here:
> https://saqimtiaz.github.io/sq-tw/streams.html#Extending%20the%20Context%20Menu
>
> I can probably help you get the actions right. Are you thinking an option
> that renames a node, and the subnodes *if* their titles begin with the node
> title?
>
> Or something to use after you've already renamed a node and the subnodes
> no longer match in terms of titles.
>
> --
> 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/1jTwdmq8cgI/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/641a43dd-fb43-499f-8468-19c294358dd8n%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/CACaamTkS%2BuJSve6TGrhduEreW9cKiALnUHqNijMd0AdXPJ8MPQ%40mail.gmail.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Keelan

Is that something I could add to the context menu? I know you've set it up 
> so users can create their own menu items.


Yes, that should be doable. 
There is some info here: 
https://saqimtiaz.github.io/sq-tw/streams.html#Extending%20the%20Context%20Menu

I can probably help you get the actions right. Are you thinking an option 
that renames a node, and the subnodes *if* their titles begin with the node 
title?

Or something to use after you've already renamed a node and the subnodes no 
longer match in terms of titles.

-- 
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/641a43dd-fb43-499f-8468-19c294358dd8n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

That's the plugin that came to mind when I asked. I'll fiddle with it some 
and see if sequential naming is an option.

Though, the concept of adding it to the context menu in Streams is 
intriguing. I agree that you wouldn't want it to be default behavior, but 
having the option from that context menu could be a helpful addition when 
the minority use case presents itself.

Is that something I could add to the context menu? I know you've set it up 
so users can create their own menu items.
On Sunday, August 23, 2020 at 5:11:14 AM UTC-4 saq.i...@gmail.com wrote:

> I haven't used it but I have seen this plugin recommended for batch 
> operations:
> https://github.com/kookma/TW-Commander 
>
> It would also be doable to add a context menu action in Streams, so that 
> "Rename" also renamed the nodes of that tiddler.
> However this feels like a step backwards in terms of flexibility regarding 
> tiddler titles if it were a default. Having this as an optional behaviour 
> that one could trigger when needed would make more sense.
>
> On Sunday, August 23, 2020 at 1:06:02 AM UTC+2 keela...@gmail.com wrote:
>
>> Yes, that makes sense. If I rename a sub-node, then it will also show up 
>> separate. If I rename the root, then they would all show up.
>>
>> Do you happen to know of a plugin that allows for batch renaming in a 
>> sequence, in the event that I did want to change the root node? If not, the 
>> benefits of this search outweigh the cons, I believe.
>>
>> On Saturday, August 22, 2020 at 3:08:18 PM UTC-4 saq.i...@gmail.com 
>> wrote:
>>
>>> Keelan,
>>>
>>> Glad it seems useful. One thing to keep in mind is that for the search 
>>> results, the logic is now dependent on the name of the sub-node tiddler 
>>> starting with the name of the root-node. So if you rename the root, all the 
>>> sub-nodes will turn up as separate results in search.
>>>
>>> On Saturday, August 22, 2020 at 12:13:59 AM UTC+2 keela...@gmail.com 
>>> wrote:
>>>
 I know not what magic you have worked here, but I like it! 

 No errors this time. This is a great improvement on the search. Having 
 that second tab dedicated to streams allows both a regular search and the 
 option to filter out the chaff in a stream and focus on the main tiddler. 
 That's perfect. And, it's unobtrusive too. 

 In fact, it's already allowed me to locate some dangling tiddlers with 
 no content that had somehow been removed from my streams. So, I was able 
 to 
 tidy up a bit. 

 On Friday, August 21, 2020 at 2:44:53 PM UTC-4 saq.i...@gmail.com 
 wrote:

> Hi Keelan,
>
> Apologies, I may not have been diligent enough with error handling.
>
> Try the following steps please:
> 1) try using the search at 
> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>  and 
> see if there is an error
>
> 2) If there isn't an error, try grabbing the updated plugin and try it 
> on your wiki.
>
> If either steps gives the same error, in your browser press 
> Ctrl+Shift+I to open the developer console. In the "Console" tab, if 
> there 
> is an error message in red, click on it to expand and post a screenshot 
> please.
>
>
> On Friday, August 21, 2020 at 8:27:58 PM UTC+2, Keelan Cook wrote:
>>
>> Well, I may have done something wrong in installation, but it's 
>> kicking an error back at me.
>>
>> The error comes as soon as I click into the search bar to type 
>> something. I've attempted a refresh to no avail. When I disable the new 
>> plugin and refresh, the error is gone. 
>>
>> [image: Screenshot 2020-08-21 at 2.25.16 PM.png]
>>
>> On Thursday, August 20, 2020 at 2:15:23 PM UTC-4 saq.i...@gmail.com 
>> wrote:
>>
>>> Keelan, install this and let me know if it gets us in the ballpark 
>>> of helpful search behaviour:
>>>
>>>
>>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>>>
>>>
>>>

-- 
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/8d6a0cc4-7629-437a-bb30-676907d287f1n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

That's the plugin that came to mind when I asked. I'll fiddle with it some 
and see if sequential naming is an option.

Though, the concept of adding it to the context menu in Streams is 
intriguing. I agree that you wouldn't want it to be default behavior, but 
having the option from that context menu could be a helpful addition when 
the minority use case presents itself.

Is that something I could add to the context menu? I know you've set it up 
so users can create their own menu items.
On Sunday, August 23, 2020 at 5:11:14 AM UTC-4 saq.i...@gmail.com wrote:

> I haven't used it but I have seen this plugin recommended for batch 
> operations:
> https://github.com/kookma/TW-Commander 
>
> It would also be doable to add a context menu action in Streams, so that 
> "Rename" also renamed the nodes of that tiddler.
> However this feels like a step backwards in terms of flexibility regarding 
> tiddler titles if it were a default. Having this as an optional behaviour 
> that one could trigger when needed would make more sense.
>
> On Sunday, August 23, 2020 at 1:06:02 AM UTC+2 keela...@gmail.com wrote:
>
>> Yes, that makes sense. If I rename a sub-node, then it will also show up 
>> separate. If I rename the root, then they would all show up.
>>
>> Do you happen to know of a plugin that allows for batch renaming in a 
>> sequence, in the event that I did want to change the root node? If not, the 
>> benefits of this search outweigh the cons, I believe.
>>
>> On Saturday, August 22, 2020 at 3:08:18 PM UTC-4 saq.i...@gmail.com 
>> wrote:
>>
>>> Keelan,
>>>
>>> Glad it seems useful. One thing to keep in mind is that for the search 
>>> results, the logic is now dependent on the name of the sub-node tiddler 
>>> starting with the name of the root-node. So if you rename the root, all the 
>>> sub-nodes will turn up as separate results in search.
>>>
>>> On Saturday, August 22, 2020 at 12:13:59 AM UTC+2 keela...@gmail.com 
>>> wrote:
>>>
 I know not what magic you have worked here, but I like it! 

 No errors this time. This is a great improvement on the search. Having 
 that second tab dedicated to streams allows both a regular search and the 
 option to filter out the chaff in a stream and focus on the main tiddler. 
 That's perfect. And, it's unobtrusive too. 

 In fact, it's already allowed me to locate some dangling tiddlers with 
 no content that had somehow been removed from my streams. So, I was able 
 to 
 tidy up a bit. 

 On Friday, August 21, 2020 at 2:44:53 PM UTC-4 saq.i...@gmail.com 
 wrote:

> Hi Keelan,
>
> Apologies, I may not have been diligent enough with error handling.
>
> Try the following steps please:
> 1) try using the search at 
> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>  and 
> see if there is an error
>
> 2) If there isn't an error, try grabbing the updated plugin and try it 
> on your wiki.
>
> If either steps gives the same error, in your browser press 
> Ctrl+Shift+I to open the developer console. In the "Console" tab, if 
> there 
> is an error message in red, click on it to expand and post a screenshot 
> please.
>
>
> On Friday, August 21, 2020 at 8:27:58 PM UTC+2, Keelan Cook wrote:
>>
>> Well, I may have done something wrong in installation, but it's 
>> kicking an error back at me.
>>
>> The error comes as soon as I click into the search bar to type 
>> something. I've attempted a refresh to no avail. When I disable the new 
>> plugin and refresh, the error is gone. 
>>
>> [image: Screenshot 2020-08-21 at 2.25.16 PM.png]
>>
>> On Thursday, August 20, 2020 at 2:15:23 PM UTC-4 saq.i...@gmail.com 
>> wrote:
>>
>>> Keelan, install this and let me know if it gets us in the ballpark 
>>> of helpful search behaviour:
>>>
>>>
>>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>>>
>>>
>>>

-- 
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/ff8da1dd-08c3-444b-94cb-e80b3a8da670n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

I haven't used it but I have seen this plugin recommended for batch 
operations:
https://github.com/kookma/TW-Commander 

It would also be doable to add a context menu action in Streams, so that 
"Rename" also renamed the nodes of that tiddler.
However this feels like a step backwards in terms of flexibility regarding 
tiddler titles if it were a default. Having this as an optional behaviour 
that one could trigger when needed would make more sense.

On Sunday, August 23, 2020 at 1:06:02 AM UTC+2 keela...@gmail.com wrote:

> Yes, that makes sense. If I rename a sub-node, then it will also show up 
> separate. If I rename the root, then they would all show up.
>
> Do you happen to know of a plugin that allows for batch renaming in a 
> sequence, in the event that I did want to change the root node? If not, the 
> benefits of this search outweigh the cons, I believe.
>
> On Saturday, August 22, 2020 at 3:08:18 PM UTC-4 saq.i...@gmail.com wrote:
>
>> Keelan,
>>
>> Glad it seems useful. One thing to keep in mind is that for the search 
>> results, the logic is now dependent on the name of the sub-node tiddler 
>> starting with the name of the root-node. So if you rename the root, all the 
>> sub-nodes will turn up as separate results in search.
>>
>> On Saturday, August 22, 2020 at 12:13:59 AM UTC+2 keela...@gmail.com 
>> wrote:
>>
>>> I know not what magic you have worked here, but I like it! 
>>>
>>> No errors this time. This is a great improvement on the search. Having 
>>> that second tab dedicated to streams allows both a regular search and the 
>>> option to filter out the chaff in a stream and focus on the main tiddler. 
>>> That's perfect. And, it's unobtrusive too. 
>>>
>>> In fact, it's already allowed me to locate some dangling tiddlers with 
>>> no content that had somehow been removed from my streams. So, I was able to 
>>> tidy up a bit. 
>>>
>>> On Friday, August 21, 2020 at 2:44:53 PM UTC-4 saq.i...@gmail.com wrote:
>>>
 Hi Keelan,

 Apologies, I may not have been diligent enough with error handling.

 Try the following steps please:
 1) try using the search at 
 https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
  and 
 see if there is an error

 2) If there isn't an error, try grabbing the updated plugin and try it 
 on your wiki.

 If either steps gives the same error, in your browser press 
 Ctrl+Shift+I to open the developer console. In the "Console" tab, if there 
 is an error message in red, click on it to expand and post a screenshot 
 please.


 On Friday, August 21, 2020 at 8:27:58 PM UTC+2, Keelan Cook wrote:
>
> Well, I may have done something wrong in installation, but it's 
> kicking an error back at me.
>
> The error comes as soon as I click into the search bar to type 
> something. I've attempted a refresh to no avail. When I disable the new 
> plugin and refresh, the error is gone. 
>
> [image: Screenshot 2020-08-21 at 2.25.16 PM.png]
>
> On Thursday, August 20, 2020 at 2:15:23 PM UTC-4 saq.i...@gmail.com 
> wrote:
>
>> Keelan, install this and let me know if it gets us in the ballpark of 
>> helpful search behaviour:
>>
>>
>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>>
>>
>>

-- 
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/472bf176-1d8b-4145-b918-35b18526f894n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

Yes, that makes sense. If I rename a sub-node, then it will also show up 
separate. If I rename the root, then they would all show up.

Do you happen to know of a plugin that allows for batch renaming in a 
sequence, in the event that I did want to change the root node? If not, the 
benefits of this search outweigh the cons, I believe.

On Saturday, August 22, 2020 at 3:08:18 PM UTC-4 saq.i...@gmail.com wrote:

> Keelan,
>
> Glad it seems useful. One thing to keep in mind is that for the search 
> results, the logic is now dependent on the name of the sub-node tiddler 
> starting with the name of the root-node. So if you rename the root, all the 
> sub-nodes will turn up as separate results in search.
>
> On Saturday, August 22, 2020 at 12:13:59 AM UTC+2 keela...@gmail.com 
> wrote:
>
>> I know not what magic you have worked here, but I like it! 
>>
>> No errors this time. This is a great improvement on the search. Having 
>> that second tab dedicated to streams allows both a regular search and the 
>> option to filter out the chaff in a stream and focus on the main tiddler. 
>> That's perfect. And, it's unobtrusive too. 
>>
>> In fact, it's already allowed me to locate some dangling tiddlers with no 
>> content that had somehow been removed from my streams. So, I was able to 
>> tidy up a bit. 
>>
>> On Friday, August 21, 2020 at 2:44:53 PM UTC-4 saq.i...@gmail.com wrote:
>>
>>> Hi Keelan,
>>>
>>> Apologies, I may not have been diligent enough with error handling.
>>>
>>> Try the following steps please:
>>> 1) try using the search at 
>>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>>>  and 
>>> see if there is an error
>>>
>>> 2) If there isn't an error, try grabbing the updated plugin and try it 
>>> on your wiki.
>>>
>>> If either steps gives the same error, in your browser press Ctrl+Shift+I 
>>> to open the developer console. In the "Console" tab, if there is an error 
>>> message in red, click on it to expand and post a screenshot please.
>>>
>>>
>>> On Friday, August 21, 2020 at 8:27:58 PM UTC+2, Keelan Cook wrote:

 Well, I may have done something wrong in installation, but it's kicking 
 an error back at me.

 The error comes as soon as I click into the search bar to type 
 something. I've attempted a refresh to no avail. When I disable the new 
 plugin and refresh, the error is gone. 

 [image: Screenshot 2020-08-21 at 2.25.16 PM.png]

 On Thursday, August 20, 2020 at 2:15:23 PM UTC-4 saq.i...@gmail.com 
 wrote:

> Keelan, install this and let me know if it gets us in the ballpark of 
> helpful search behaviour:
>
>
> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>
>
>

-- 
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/371aa822-cd62-490b-8fea-d117c1fd305cn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Keelan,

Glad it seems useful. One thing to keep in mind is that for the search 
results, the logic is now dependent on the name of the sub-node tiddler 
starting with the name of the root-node. So if you rename the root, all the 
sub-nodes will turn up as separate results in search.

On Saturday, August 22, 2020 at 12:13:59 AM UTC+2 keela...@gmail.com wrote:

> I know not what magic you have worked here, but I like it! 
>
> No errors this time. This is a great improvement on the search. Having 
> that second tab dedicated to streams allows both a regular search and the 
> option to filter out the chaff in a stream and focus on the main tiddler. 
> That's perfect. And, it's unobtrusive too. 
>
> In fact, it's already allowed me to locate some dangling tiddlers with no 
> content that had somehow been removed from my streams. So, I was able to 
> tidy up a bit. 
>
> On Friday, August 21, 2020 at 2:44:53 PM UTC-4 saq.i...@gmail.com wrote:
>
>> Hi Keelan,
>>
>> Apologies, I may not have been diligent enough with error handling.
>>
>> Try the following steps please:
>> 1) try using the search at 
>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>>  and 
>> see if there is an error
>>
>> 2) If there isn't an error, try grabbing the updated plugin and try it on 
>> your wiki.
>>
>> If either steps gives the same error, in your browser press Ctrl+Shift+I 
>> to open the developer console. In the "Console" tab, if there is an error 
>> message in red, click on it to expand and post a screenshot please.
>>
>>
>> On Friday, August 21, 2020 at 8:27:58 PM UTC+2, Keelan Cook wrote:
>>>
>>> Well, I may have done something wrong in installation, but it's kicking 
>>> an error back at me.
>>>
>>> The error comes as soon as I click into the search bar to type 
>>> something. I've attempted a refresh to no avail. When I disable the new 
>>> plugin and refresh, the error is gone. 
>>>
>>> [image: Screenshot 2020-08-21 at 2.25.16 PM.png]
>>>
>>> On Thursday, August 20, 2020 at 2:15:23 PM UTC-4 saq.i...@gmail.com 
>>> wrote:
>>>
 Keelan, install this and let me know if it gets us in the ballpark of 
 helpful search behaviour:


 https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search




-- 
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/ade06544-92bf-4510-9b03-759009556206n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

I know not what magic you have worked here, but I like it! 

No errors this time. This is a great improvement on the search. Having that 
second tab dedicated to streams allows both a regular search and the option 
to filter out the chaff in a stream and focus on the main tiddler. That's 
perfect. And, it's unobtrusive too. 

In fact, it's already allowed me to locate some dangling tiddlers with no 
content that had somehow been removed from my streams. So, I was able to 
tidy up a bit. 

On Friday, August 21, 2020 at 2:44:53 PM UTC-4 saq.i...@gmail.com wrote:

> Hi Keelan,
>
> Apologies, I may not have been diligent enough with error handling.
>
> Try the following steps please:
> 1) try using the search at 
> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>  and 
> see if there is an error
>
> 2) If there isn't an error, try grabbing the updated plugin and try it on 
> your wiki.
>
> If either steps gives the same error, in your browser press Ctrl+Shift+I 
> to open the developer console. In the "Console" tab, if there is an error 
> message in red, click on it to expand and post a screenshot please.
>
>
> On Friday, August 21, 2020 at 8:27:58 PM UTC+2, Keelan Cook wrote:
>>
>> Well, I may have done something wrong in installation, but it's kicking 
>> an error back at me.
>>
>> The error comes as soon as I click into the search bar to type something. 
>> I've attempted a refresh to no avail. When I disable the new plugin and 
>> refresh, the error is gone. 
>>
>> [image: Screenshot 2020-08-21 at 2.25.16 PM.png]
>>
>> On Thursday, August 20, 2020 at 2:15:23 PM UTC-4 saq.i...@gmail.com 
>> wrote:
>>
>>> Keelan, install this and let me know if it gets us in the ballpark of 
>>> helpful search behaviour:
>>>
>>>
>>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>>>
>>>
>>>

-- 
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/6ea31abf-f2e0-4d3a-b1aa-d088d7bb33ecn%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Hi Keelan,

Apologies, I may not have been diligent enough with error handling.

Try the following steps please:
1) try using the search at 
https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
 and 
see if there is an error

2) If there isn't an error, try grabbing the updated plugin and try it on 
your wiki.

If either steps gives the same error, in your browser press Ctrl+Shift+I to 
open the developer console. In the "Console" tab, if there is an error 
message in red, click on it to expand and post a screenshot please.


On Friday, August 21, 2020 at 8:27:58 PM UTC+2, Keelan Cook wrote:
>
> Well, I may have done something wrong in installation, but it's kicking an 
> error back at me.
>
> The error comes as soon as I click into the search bar to type something. 
> I've attempted a refresh to no avail. When I disable the new plugin and 
> refresh, the error is gone. 
>
> [image: Screenshot 2020-08-21 at 2.25.16 PM.png]
>
> On Thursday, August 20, 2020 at 2:15:23 PM UTC-4 saq.i...@gmail.com wrote:
>
>> Keelan, install this and let me know if it gets us in the ballpark of 
>> helpful search behaviour:
>>
>>
>> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>>
>>
>>

-- 
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/3b35115e-4991-4635-b9aa-46f73efe53a4o%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

Well, I may have done something wrong in installation, but it's kicking an 
error back at me.

The error comes as soon as I click into the search bar to type something. 
I've attempted a refresh to no avail. When I disable the new plugin and 
refresh, the error is gone. 

[image: Screenshot 2020-08-21 at 2.25.16 PM.png]

On Thursday, August 20, 2020 at 2:15:23 PM UTC-4 saq.i...@gmail.com wrote:

> Keelan, install this and let me know if it gets us in the ballpark of 
> helpful search behaviour:
>
>
> https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search
>
>
>

-- 
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/ece401e8-05ea-4c57-9483-fb14465f50f3n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Keelan, install this and let me know if it gets us in the ballpark of 
helpful search behaviour:

https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams-search


-- 
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/4a396488-0e1f-4330-9356-0a97a7f70854o%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

@Keelan your summary for how search could be set up for you is correct.

 I don't know if it makes a great generic solution for Streams users since 
they might customize their node titles to be generated differently, or wish 
to rename without it affecting search results. The best way to figure that 
out of course, is to let people try it.

I wrote the code that follows the parent field to the root, I just need to 
adjust to only follow when the title of the node includes the parent 
tiddler title as a prefix. Will do so as soon as I get the chance.

Regards,
Saq

On Thursday, August 20, 2020 at 4:18:53 PM UTC+2, Keelan Cook wrote:
>
> Saq, if I'm understanding correctly, that does sound intriguing. Let me 
> rehash my understanding of what you are saying, just to make sure I'm 
> getting it.
>
> I do understand (and very much like) that the sub-nodes are not actually 
> in a hierarchy, and that they are attached through the parent field. That's 
> one of the big strengths of the plugin. Each tiddler is actually a stand 
> alone note that can be transcluded a dozen times into different content. 
> Literature notes are durable that way. And when I am creating content, a 
> paragraph can easily be moved to another place in the flow of the article. 
> That makes writing and editing a smooth experience. 
>
> Furthermore, it does allow me to change the title of a note to whatever I 
> desire, because the title is not the determining factor for its presence in 
> the stream. It relies on the title being in the parent field, and the 
> relink plugin ensures it stays there if I change it. 
>
> However, what it sounds like you are suggesting is a search option that 
> uses the parent field and checks it somehow to follow up to the "main" 
> tiddler for that stream. Doing this would search all of the tiddlers in the 
> stream, but show the "main" tiddler as the search result for all of them... 
> with one exception. If I have changed the title to something that does not 
> include the "main" tiddler title, then it would not be included, it would 
> stand alone as it's own search result.
>
> Am I understanding you correctly? If so, that does, indeed sound like a 
> good option, and I think it would streamline the flow for researching with 
> Streams.
>
> Concerning the tiddler you mentioned, here are the contents of that 
> tiddler:
>
> <>/<>
>
> Thanks again, Saq.
> On Wednesday, August 19, 2020 at 6:50:30 AM UTC-4 saq.i...@gmail.com 
> wrote:
>
>> Keelan,
>>
>> Another short reply for now, going to work through the rest of your 
>> feedback piecemeal as time permits.
>>
>> Regarding search:
>>
>> *Search gets confusing.* I've learned to adjust to this, but all of the 
>>> streams tiddlers show up in search. Most of the time, I only want the 
>>> parent to show and then I will find what I want on that "main tiddler." 
>>> However, I periodically have a tiddler created in a stream that rises to 
>>> the level of a stand alone tiddler, so I would want it to index. I realize 
>>> the dilemma in all of this. So, I think if we could omit all the children 
>>> and just index the main parent tiddler for a stream in search, it would be 
>>> preferrable, since it is possible to just rename a specific stream 
>>> tiddler and then it could index.
>>
>>
>>  I thought about putting together a quick search solution for search 
>> where only the root node is returned in search results, but quickly 
>> realized there is a conceptual snag. Streams is intentionally written so 
>> that it doesn't care about the titles of tiddlers for maintaining the 
>> relationships between them. So for example:
>>
>> History/1908 is not a subnode of History because of it's title, but 
>> rather because History/1908 has a field called *parent* with value 
>> History.
>>
>> So it's easily doable to have a custom search only return the root node 
>> of results by following the parent field back through relationships to the 
>> end. However, just renaming a tiddler would not make it show up in the 
>> search results. You would have to delete the "parent" field thereby 
>> removing it from the Stream.
>>
>> So this makes a generic and flexible solution quite difficult. However, 
>> it would be doable to create a custom solution for you where search always 
>> follows the parent field upwards as long as the parent tiddler title is a 
>> substring of the tiddler in question.
>>
>> That is if History/1908 has the field parent pointing to History, we 
>> follow that field.
>> If French Revolution has the field parent pointing to History, we do not 
>> follow it.
>>
>>  Let me know if this would be helpful, and if so what the value of the 
>> tiddler $:/config/sq/streams/new-node-title is when you open it for editing.
>>
>> Cheers,
>> Saq
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

Saq, if I'm understanding correctly, that does sound intriguing. Let me 
rehash my understanding of what you are saying, just to make sure I'm 
getting it.

I do understand (and very much like) that the sub-nodes are not actually in 
a hierarchy, and that they are attached through the parent field. That's 
one of the big strengths of the plugin. Each tiddler is actually a stand 
alone note that can be transcluded a dozen times into different content. 
Literature notes are durable that way. And when I am creating content, a 
paragraph can easily be moved to another place in the flow of the article. 
That makes writing and editing a smooth experience. 

Furthermore, it does allow me to change the title of a note to whatever I 
desire, because the title is not the determining factor for its presence in 
the stream. It relies on the title being in the parent field, and the 
relink plugin ensures it stays there if I change it. 

However, what it sounds like you are suggesting is a search option that 
uses the parent field and checks it somehow to follow up to the "main" 
tiddler for that stream. Doing this would search all of the tiddlers in the 
stream, but show the "main" tiddler as the search result for all of them... 
with one exception. If I have changed the title to something that does not 
include the "main" tiddler title, then it would not be included, it would 
stand alone as it's own search result.

Am I understanding you correctly? If so, that does, indeed sound like a 
good option, and I think it would streamline the flow for researching with 
Streams.

Concerning the tiddler you mentioned, here are the contents of that tiddler:

<>/<>

Thanks again, Saq.
On Wednesday, August 19, 2020 at 6:50:30 AM UTC-4 saq.i...@gmail.com wrote:

> Keelan,
>
> Another short reply for now, going to work through the rest of your 
> feedback piecemeal as time permits.
>
> Regarding search:
>
> *Search gets confusing.* I've learned to adjust to this, but all of the 
>> streams tiddlers show up in search. Most of the time, I only want the 
>> parent to show and then I will find what I want on that "main tiddler." 
>> However, I periodically have a tiddler created in a stream that rises to 
>> the level of a stand alone tiddler, so I would want it to index. I realize 
>> the dilemma in all of this. So, I think if we could omit all the children 
>> and just index the main parent tiddler for a stream in search, it would be 
>> preferrable, since it is possible to just rename a specific stream 
>> tiddler and then it could index.
>
>
>  I thought about putting together a quick search solution for search where 
> only the root node is returned in search results, but quickly realized 
> there is a conceptual snag. Streams is intentionally written so that it 
> doesn't care about the titles of tiddlers for maintaining the relationships 
> between them. So for example:
>
> History/1908 is not a subnode of History because of it's title, but rather 
> because History/1908 has a field called *parent* with value History.
>
> So it's easily doable to have a custom search only return the root node of 
> results by following the parent field back through relationships to the 
> end. However, just renaming a tiddler would not make it show up in the 
> search results. You would have to delete the "parent" field thereby 
> removing it from the Stream.
>
> So this makes a generic and flexible solution quite difficult. However, it 
> would be doable to create a custom solution for you where search always 
> follows the parent field upwards as long as the parent tiddler title is a 
> substring of the tiddler in question.
>
> That is if History/1908 has the field parent pointing to History, we 
> follow that field.
> If French Revolution has the field parent pointing to History, we do not 
> follow it.
>
>  Let me know if this would be helpful, and if so what the value of the 
> tiddler $:/config/sq/streams/new-node-title is when you open it for editing.
>
> Cheers,
> Saq
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9aa49459-4880-477c-8f6e-69fd8f329a07n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Keelan,

Another short reply for now, going to work through the rest of your 
feedback piecemeal as time permits.

Regarding search:

*Search gets confusing.* I've learned to adjust to this, but all of the 
> streams tiddlers show up in search. Most of the time, I only want the 
> parent to show and then I will find what I want on that "main tiddler." 
> However, I periodically have a tiddler created in a stream that rises to 
> the level of a stand alone tiddler, so I would want it to index. I realize 
> the dilemma in all of this. So, I think if we could omit all the children 
> and just index the main parent tiddler for a stream in search, it would be 
> preferrable, since it is possible to just rename a specific stream 
> tiddler and then it could index.


 I thought about putting together a quick search solution for search where 
only the root node is returned in search results, but quickly realized 
there is a conceptual snag. Streams is intentionally written so that it 
doesn't care about the titles of tiddlers for maintaining the relationships 
between them. So for example:

History/1908 is not a subnode of History because of it's title, but rather 
because History/1908 has a field called *parent* with value History.

So it's easily doable to have a custom search only return the root node of 
results by following the parent field back through relationships to the 
end. However, just renaming a tiddler would not make it show up in the 
search results. You would have to delete the "parent" field thereby 
removing it from the Stream.

So this makes a generic and flexible solution quite difficult. However, it 
would be doable to create a custom solution for you where search always 
follows the parent field upwards as long as the parent tiddler title is a 
substring of the tiddler in question.

That is if History/1908 has the field parent pointing to History, we follow 
that field.
If French Revolution has the field parent pointing to History, we do not 
follow it.

 Let me know if this would be helpful, and if so what the value of the 
tiddler $:/config/sq/streams/new-node-title is when you open it for editing.

Cheers,
Saq

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/db348b11-44cf-4ec9-83aa-1a6cf87660deo%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

Saq, tremendously thankful for the detailed response. It was clear and very 
helpful in furthering my understanding of how TW5 works. 

I do see (and had read in other threads on Stroll) the difference between 
plugins and editions and the complexity that offering an out-of-the-box 
edition brings. As best I can tell from my limited experience with it, the 
plugin route should most often be preferred, since it aims to reduce 
dependencies and modifications to core elements. To that regard, I 
personally prefer living in the constraints to search with Streams and 
other issues over trying to develop a specific version that removes some of 
those only to have to deal with issues of extensibility further down the 
road.

Though I see the benefit of a vertical edition such as Stroll, my comment 
about linear guides was less about making a specific edition of TiddlyWiki 
and more about creating a step-by-step walkthrough (like an article or 
how-to guide) for constructing a TW5 instance from available plugins and 
themes that are known to work together well. I'm thinking about a tutorial 
that would get someone up and running for a common use case (notetaking and 
research), without hunting through the threads for different pieces to bolt 
on. For instance, at this point, I've discovered a couple of themes 
(Whitepace and Krystal), your Streams and Stories plugins, the Refnotes 
plugin, and the Crosslinks plugin for backlinks and freelinks all work well 
together to create a solid notetaking instance. Had I been able to locate a 
tutorial that explained TiddlyWiki setup for one notetaking instance and 
turned me on to that set of themes and plugins, I would have been up and 
running much faster. 

I was merely suggesting it might be helpful for the community to come up 
with the 3-5 most common uses and some solid walkthroughs for how to build 
a good instance out of available themes and plugins. That is why I pointed 
out Anne-Laure's work on her site. In fact, I think it better to provide a 
walkthrough than provide a packaged instance of TW5 with the themes and 
plugins already together, since a walkthrough has the added benefit of 
teaching just enough about customizing your TiddlyWiki in order to add the 
plugins. It's the right kind of friction, but it walks with someone instead 
of leaving them in a wide open field. Of course, this information would be 
ever-changing as new plugins are developed, so it might not be a feasible 
approach to onboarding. 

Concerning the export, that's great news. I assumed there was some option, 
and I just wasn't sure how to accomplish it yet. I'll have a go at a 
request here to get that started. 

Thanks again for your response, and for your work on TiddlyWiki. It's been 
refreshing having this at my disposal of late. I look forward to any 
further feedback you may have concerning Streams. And again, I'm happy to 
help and answer any questions you may have concerning my use case.

Thanks,
Keelan




On Tuesday, August 18, 2020 at 11:48:04 AM UTC-5 saq.i...@gmail.com wrote:

> Hi Keelan,
>
> Apologies for the late response, I wanted to wait to reply to your 
> feedback until I had the time to do so properly. I am always happy to 
> discuss at length when the feedback is both detailed and pertinent, as 
> yours has been. I am going to going off on what seems like a bit of a 
> tangent at first, to properly reply to some of the points you raised.
>
> Firstly, I'd like to explain the concept of a TiddlyWiki edition, 
> sometimes also referred to as a vertical edition. Simply put it is a 
> TiddlyWiki meant to serve as a starting point, with a set of plugins and 
> tweaks preconfigured that work together well with no clashes, to provide a 
> specific set of features or workflow. The best example of this currently is 
> Stroll from David Gifford, which encourages a notetaking style dependent on 
> backlinks.
>
> The key part that is relevant here is that with an edition, you have the 
> ability to make sure that all the plugins play together nicely and don't 
> clash, and complement each other with their functionality. When writing a 
> plugin you have to try your utmost not to make changes to the default TW 
> behaviour beyond what you absolutely need to, to minimize the chance of 
> clashes with other plugins.
>
> As an example consider Streams. If it were to be extended to tweak the 
> default search results, it would clash with any other plugin that extended 
> the search results or the search interface. With a pre-configured set of 
> plugins, this isn't an issue. Furthermore, the more changes you make to the 
> defaults in TW, the greater the chance the plugin will need updates when 
> the TiddlyWiki core is updated, increasing the maintenance burden of the 
> plugin.
>
> So at this point, you would be right in thinking that editions is 
> basically what you alluded to when speaking of linear guides or "choose 
> your own adventure" use cases. There are some significant 

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Hi Keelan,

Apologies for the late response, I wanted to wait to reply to your feedback 
until I had the time to do so properly. I am always happy to discuss at 
length when the feedback is both detailed and pertinent, as yours has been. 
I am going to going off on what seems like a bit of a tangent at first, to 
properly reply to some of the points you raised.

Firstly, I'd like to explain the concept of a TiddlyWiki edition, sometimes 
also referred to as a vertical edition. Simply put it is a TiddlyWiki meant 
to serve as a starting point, with a set of plugins and tweaks 
preconfigured that work together well with no clashes, to provide a 
specific set of features or workflow. The best example of this currently is 
Stroll from David Gifford, which encourages a notetaking style dependent on 
backlinks.

The key part that is relevant here is that with an edition, you have the 
ability to make sure that all the plugins play together nicely and don't 
clash, and complement each other with their functionality. When writing a 
plugin you have to try your utmost not to make changes to the default TW 
behaviour beyond what you absolutely need to, to minimize the chance of 
clashes with other plugins.

As an example consider Streams. If it were to be extended to tweak the 
default search results, it would clash with any other plugin that extended 
the search results or the search interface. With a pre-configured set of 
plugins, this isn't an issue. Furthermore, the more changes you make to the 
defaults in TW, the greater the chance the plugin will need updates when 
the TiddlyWiki core is updated, increasing the maintenance burden of the 
plugin.

So at this point, you would be right in thinking that editions is basically 
what you alluded to when speaking of linear guides or "choose your own 
adventure" use cases. There are some significant challenges inherent in 
creating editions, amongst them:

- the need for extensive user studies and testing, to design, test and 
refine a workflow and featureset. This requires a significant amount of 
time and effort from both the developer and the users working together. 
Furthermore it requires developer(s) and users working together towards the 
same end goal in an effective and efficient manner. A common shortcut that 
is employed is for the developer to also act as the user, which works in 
situations where the development is driven by the developer's own needs. 
This, by the way is not the case for Streams which I personally do not use 
and was created as a tech demo for the community. I will come back to this 
later.

- Customizing, simplifying and optimizing the workflow for a specific use 
cases often involves making choices that limit or alter functionality. 
While the components of an edition can be designed to work together well, 
they are likely to clash with other plugins available in the community. 
This often leads to discontent from the users that are unhappy with the 
perceived lack of flexibility and customization in an edition, considering 
that it is still based on TiddlyWiki.

For example let us consider WYSIWYG editors, something that has been a 
frequent topic of discussion in the TW community. Due to the way that 
TiddlyWiki widgets, macros and transclusions work, implementing a full 
featured WYSIWYG editor would be a very significant, challenging and time 
consuming endeavour. There have however been comments in the community that 
even a WYSIWYG editor that *only* handled simple text formatting would be 
useful for everyday writing, but at what cost?

I have a prototype of such an editor that only supports text formatting, 
but that means giving up custom HTML and widgets and macros in the tiddlers 
where you use it. So for instance, in your case to use such an editor you 
would need to give up using the refnotes plugin in those tiddlers. This 
perhaps hasn't been the most ideal example, but hopefully it serves to 
illustrate the point about compromises and limitations imposed when 
designing specific features and workflows. In some ways TiddlyWiki's 
flexibility works against it in these situations, by setting certain user 
expectations.

- Last but not least is the maintenance burden that comes with providing an 
edition, and keeping it up to date with TiddlyWiki core updates as well as 
plugin updates.

I do agree that there is a lot of untapped potential in providing editions 
that serve specific workflows, but I am uncertain if a community as small 
as this has the resources to tackle this.

Similarly Streams would benefit greatly from an edition that incorporated 
it and addressed some of the issues like search results, backlink results 
etc. However, considering both my limited availability and the fact that I 
do not use this myself, I am not the appropriate person to do so. 

Regarding Streams and the motivation behind its development: 

Overall I feel that there is a lack of innovation in the TW5 community in 
recent years, 

Re: [tw5] Re: [ Streams ] : feedback and issues

[E Browns]

Thanks for considering it, Saq! It will make for a more wonderful workflow,
mobile-wise.

I agree it might produce interferences while editting. Maybe while the node
is not in edit mode? Or maybe just along the left margin right outside the
textbox? Whatever the implementation might be I'd love to try it!

Thanks again, i'll also look into the issue you linked!

On Fri, Aug 14, 2020, 01:31 Saq Imtiaz,  wrote:

> Hi JD,
>
> That's an interesting idea. I agree that adding better UX for mobile would
> be a good idea. I'd like to use a smaller library than the one the hammer
> widgets use, but I might use that first to make sure that the interactions
> and flow is satisfactory. In particular, there will likely be issues with
> selecting text clashing with swipe support.
>
> I think the hammer widgets get around this by disabling text selection,
> which wouldn't work for Streams.
>
> I'm tracking another mobile related ticket as well, perhaps you might have
> some thoughts on it?
> https://github.com/saqimtiaz/streams/issues/3
>
> Thank you,
> Saq
>
> On Thursday, August 13, 2020 at 5:59:15 PM UTC+2, JD wrote:
>>
>> Saq! I love your ideas and extensions to the way we can create tiddlers!
>> Honestly, Streams is making it easier for me to write ^^,
>>
>> I have a request for mostly-mobile users like me, because I also want to
>> continue using this on my phone.
>>
>> Will it be possible to implement a swipe mechanism on the nodes? (Sample
>> is BTC's Swipe widget hammerwidgets.tiddlyspot.com)
>>
>> On my phone, I'd like to be able to swipe right on a node to indent it!
>> And be able to swipe left to un-indent. Google Keep has this feature and I
>> found it made listing so much easier! Hopefully Streams can also do it?
>>
>> Thanks for this wonderful creation tool!
>>
>> -jd
>>
>> --
> 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/1jTwdmq8cgI/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/8890c49c-f026-4ff7-846d-d2e67fc03a20o%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/CAOAd_aUWuTbPA4NOOnrP5FjKwwxduHKZyLbph9GvhGdCcJjGiQ%40mail.gmail.com.

[tw5] Re: [ Streams ] : feedback and issues

[Keelan Cook]

Just updated, and the initial space issue is indeed solved. Thanks!

On Thursday, August 13, 2020 at 12:30:48 PM UTC-5 saq.i...@gmail.com wrote:

> Hi JD,
>
> That's an interesting idea. I agree that adding better UX for mobile would 
> be a good idea. I'd like to use a smaller library than the one the hammer 
> widgets use, but I might use that first to make sure that the interactions 
> and flow is satisfactory. In particular, there will likely be issues with 
> selecting text clashing with swipe support.
>
> I think the hammer widgets get around this by disabling text selection, 
> which wouldn't work for Streams.
>
> I'm tracking another mobile related ticket as well, perhaps you might have 
> some thoughts on it?
> https://github.com/saqimtiaz/streams/issues/3
>
> Thank you,
> Saq
>
> On Thursday, August 13, 2020 at 5:59:15 PM UTC+2, JD wrote:
>>
>> Saq! I love your ideas and extensions to the way we can create tiddlers! 
>> Honestly, Streams is making it easier for me to write ^^,
>>
>> I have a request for mostly-mobile users like me, because I also want to 
>> continue using this on my phone. 
>>
>> Will it be possible to implement a swipe mechanism on the nodes? (Sample 
>> is BTC's Swipe widget hammerwidgets.tiddlyspot.com)
>>
>> On my phone, I'd like to be able to swipe right on a node to indent it! 
>> And be able to swipe left to un-indent. Google Keep has this feature and I 
>> found it made listing so much easier! Hopefully Streams can also do it? 
>>
>> Thanks for this wonderful creation tool! 
>>
>> -jd
>>
>>

-- 
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/e9ae915e-debc-4161-8fe2-28b118c24d33n%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Hi JD,

That's an interesting idea. I agree that adding better UX for mobile would 
be a good idea. I'd like to use a smaller library than the one the hammer 
widgets use, but I might use that first to make sure that the interactions 
and flow is satisfactory. In particular, there will likely be issues with 
selecting text clashing with swipe support.

I think the hammer widgets get around this by disabling text selection, 
which wouldn't work for Streams.

I'm tracking another mobile related ticket as well, perhaps you might have 
some thoughts on it?
https://github.com/saqimtiaz/streams/issues/3

Thank you,
Saq

On Thursday, August 13, 2020 at 5:59:15 PM UTC+2, JD wrote:
>
> Saq! I love your ideas and extensions to the way we can create tiddlers! 
> Honestly, Streams is making it easier for me to write ^^,
>
> I have a request for mostly-mobile users like me, because I also want to 
> continue using this on my phone. 
>
> Will it be possible to implement a swipe mechanism on the nodes? (Sample 
> is BTC's Swipe widget hammerwidgets.tiddlyspot.com)
>
> On my phone, I'd like to be able to swipe right on a node to indent it! 
> And be able to swipe left to un-indent. Google Keep has this feature and I 
> found it made listing so much easier! Hopefully Streams can also do it? 
>
> Thanks for this wonderful creation tool! 
>
> -jd
>
>

-- 
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/8890c49c-f026-4ff7-846d-d2e67fc03a20o%40googlegroups.com.

[tw5] Re: [ Streams ] : feedback and issues

[Saq Imtiaz]

Hi Keelan,

The detailed feedback is highly appreciated, no need to apologize. I will 
reply properly when I have a bit more time, but wanted to drop a quick note 
that the latest version of Streams should not have the issue you 
experienced with needing to add a space at the start of a node:

https://saqimtiaz.github.io/sq-tw/streams.html#%24%3A%2Fplugins%2Fsq%2Fstreams

Cheers,
Saq

On Thursday, August 13, 2020 at 3:06:31 PM UTC+2, Keelan Cook wrote:
>
> As promised, my response to your questions... at length (my apologies).
>
> *Have you encountered any issues or pain/choke points in your workflow 
> with Streams?*
>
> Overall, I'm very impressed with the manner in which Streams does what it 
> does. So, pain points are slight, but there are some of course. I've been a 
> long time Workflowy user, and I often find myself wanting it to work like 
> WF in instances. Furthermore, there is a good chance the pain points are 
> simply from the nature of TW and more an issue of me having to relearn 
> behaviors.
>
>- *Hitting enter in a node with text does not always behave the way I 
>want.* - I'm very glad you added the ability to split a tiddler into 
>two nodes by hitting enter. It would really slow down my workflow if that 
>process was inhibited, as I often write full paragraphs into a node, 
>realizing only afterward that they need to be separate paragraphs. If I 
> had 
>to confirm this change every time, it would impede using Streams for 
>writing and notetaking. However, I also expect the reverse behavior 
> because 
>of my time in Workflowy. If I am at the beginning of a node that needs to 
>be connected to the one above it, I expect hitting backspace to join the 
>two nodes. And, of course, Streams doesn't do this, so I find myself 
>regularly attempting this action by reflex.
>- *Nested nodes stay with an empty node when hitting enter instead of 
>moving with content.* - If I have a node with nested tiddlers and hit 
>enter at the beginning of the text in that node, my expectation is that 
> all 
>the text of that node and the nested nodes under it would move down, 
>creating a new blank tiddler above with nothing in it. Again, this is a 
>Workflowy behavior. However, in Streams, this action leaves all nested 
>information under the blank node created and moves the text from the 
> parent 
>node down into a separate tiddler below everything.
>- *Ctrl+down does not always behave as I expect.* - If I've collapsed 
>nested nodes and want to switch between top level nodes. For example, if 
>I'm writing an outline, I will have headings. If I collapse the 
> subheadings 
>under each heading and then attempt to use the Ctrl + down function it 
>switches down to the nested node that is not visible (one of the 
>subheadings) instead of switching down to the next heading that is visible.
>- *Having to add a space at the beginning of a node.* - Finally, there 
>appears to be some quirk where I have to enter a space prior to using a 
>text expander. It will not call the action if I enter the slash as the 
>first character in a new node. So, I have to hit a space and then put it 
> in.
>- *Search gets confusing.* I've learned to adjust to this, but all of 
>the streams tiddlers show up in search. Most of the time, I only want the 
>parent to show and then I will find what I want on that "main tiddler." 
>However, I periodically have a tiddler created in a stream that rises to 
>the level of a stand alone tiddler, so I would want it to index. I realize 
>the dilemma in all of this. So, I think if we could omit all the children 
>and just index the main parent tiddler for a stream in search, it would be 
>preferrable, since it is possible to just rename a specific stream tiddler 
>and then it could index. At current, when I have one of these special 
>stream tiddlers that I want to also stand alone, the relink gives me the 
>ability to name it with something outside the stream and keep it in the 
>stream. That's probably clear as mud. If you can't tell, I'm still 
> thinking 
>through this one myself.
>
> *Are there any features you find yourself wishing that Streams had?*
>
>- *Easily adjust max width.* - It would be nice when you develop a 
>configuration panel to include adjustable max width. I've found that line 
>in the style and can easily adjust that way, but having that option in the 
>control panel would be nice.
>- *Different views would be stellar. *- A Document view, in specific, 
>would be a great addition for me. As mentioned previously, I use this to 
>create a source tiddler for literature notes, then I create an outline 
>tiddler (also with Streams) where I draft the outline of the article I am 
>writing. I can easily drag my notes from source tiddlers to fill in the 
>article outline. With