[tw5] Re: LeftBar plugin and node.js server crashes

[Jean-Pierre Rivière]

The origin of the crash has ben found by @joshuafontany in an other thread 
on tiddlytalk, that I paste here for any reader to know it:


You have run into a bug in 5.1.23 and earlier that would crash the server 
trying to write a tiddler with no text field. This happens rarely, but most 
often when an $action-setfield widget sets a NON-text field on a 
non-existent tiddler (this creating it without a text field).

The button in the plugin sets a temp tiddler’s NON-text fields, and that is 
when the crash is happening. I would recommend using the pre-release on 
node.


Le lundi 27 septembre 2021 à 19:37:45 UTC+2, Jean-Pierre Rivière a écrit :

> Hi Matt. Thank you for being there today!
>
> At last, I know there is no hidden javascript to look for. This will help 
> me search after the culprit.
>
> Le lundi 27 septembre 2021 à 18:37:37 UTC+2, Mat a écrit :
>
>> Hi jn.pierr I am the author of LeftBar . 
>> You really timed your question because I have barely passed by here for a 
>> few months now. Unfortunately I can't really answer your question. I only 
>> create wikitext plugins and in vanilla TW and the link I gave is the actual 
>> source for the plugin. You obviously use nodejs so I'm afraid I don't have 
>> any idea what might cause the error or how to resolve it.
>>
>> With that said, it is not a very complicated construction. And it is 
>> likely to be considered a hack because I'm not a real coder. You see the 
>> plugin "files", really its shadow tiddlers, just like for any plugin - i.e 
>> in the TW Ctrlpanel, click the plugin and see its contents tab. To a great 
>> extent, the plugin functions by setting CSS values for the TW native page 
>> layout values. The actual menu is a tiddler forced to sit up in the left 
>> corner.
>>
>> <:-)
>>
>> On Monday, September 27, 2021 at 3:21:28 PM UTC+2 jn.pierr...@gmail.com 
>> wrote:
>>
>>> I’ve encountered a problem with the LeftBar plugin (v2.1.4). It happens 
>>> on a brand new empty server edition on node.js (linux arm64, run through 
>>> docker) where:
>>>
>>>- I create a $:/config/FileSystemPaths tiddler whose sole content 
>>>is [!is[system]slugify[]] (not interesting but deliberately very reduced)
>>>- I then quit the server and import my plugin with
>>>
>>> tiddlywiki mywiki --load plugin.json 
>>>
>>> Now’ I start again the server. This sandwich icon of LeftBar is or the 
>>> upper left corner. 
>>>
>>> Then I click on that sandwich icon for LeftBar and the server crashes. 
>>> See below:
>>>
>>> =
>>> syncer-server-filesystem: Dispatching 'save' task: 
>>> $:/plugins/TWaddle/LeftBar/temp node:internal/fs/utils:879 throw new 
>>> ERR_INVALID_ARG_TYPE( ^ TypeError [ERR_INVALID_ARG_TYPE]: The "data" 
>>> argument must be of type string or an instance of Buffer, TypedArray, 
>>> or DataView. Received undefined at Object.writeFile (node:fs:2106:5) at 
>>> Object.exports.saveTiddlerToFile 
>>> ($:/core/modules/utils/filesystem.js:414:6) at 
>>> $:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:85:13 at 
>>> FileSystemAdaptor.getTiddlerFileInfo 
>>> ($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:72:2) at 
>>> FileSystemAdaptor.saveTiddler 
>>> ($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:81:7) at 
>>> SaveTiddlerTask.run ($:/core/modules/syncer.js:597:27) at 
>>> Syncer.processTaskQueue ($:/core/modules/syncer.js:503:9) at 
>>> Function. ($:/core/modules/syncer.js:90:9) at 
>>> $tw.Wiki.exports.dispatchEvent ($:/core/modules/wiki.js:133:13) at 
>>> $:/core/modules/wiki.js:166:10 { code: 'ERR_INVALID_ARG_TYPE' }
>>> =
>>>   
>>>
>>> I suppose my plugin is not correctly installed. So I was about to do it 
>>> the proper way with tiddlywiki --build index and after having set 
>>> the TIDDLYWIKI_PLUGIN_PATH environment variable. But there is a problem: I 
>>> don’t know how to get all the individual tiddlers of the plugin. The plugin 
>>> shows its shadow tiddlers, which I can export. But what for the core of the 
>>> plugin, actual code? I have not been able to get any source code repository 
>>> for LeftBar.
>>>
>>> My questions:
>>>
>>>- is my diagnostic of the crash correct (bad installation of the 
>>>plugin)?
>>>- how could I get all of the files of a plugin given its json file?
>>>
>>> Thank you for your help!
>>>
>>

-- 
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/b50fe94a-2de3-403b-ba06-433728e25047n%40googlegroups.com.

[tw5] Re: Just a Filtering Code Pattern

[Álvaro]

@Télumire . It's true. They works like an OR. `{{{ [tag[Tag 1],[Tag 2],[Tag 
3],[Tag 4]]  }}}` also return different result. This behaviour would be 
documented.

El lunes, 27 de septiembre de 2021 a las 14:08:07 UTC+2, 
jn.pierr...@gmail.com escribió:

> Just a thought: it would be fine if the tagging operator could have a 
> "all" parameter which would select tiddlers tagging all of the tags in 
> input (currently, that's "any tag is enough").
>
> Thus we would have a simple and readable solution as:
>
> {{{ [tag1 tag2 tag3 tag4 +[tagging:all[]]] }}}
>
> Le lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>
>> Hello all ! 
>> The filter syntax provided by @Álvaro  is very neat but doesnt match the 
>> requirements of cj.v : counting the tiddlers with 4 specifics tags and 
>> only those tiddlers.
>>
>> See this screenshot  :
>>
>> https://i.imgur.com/lVlsYZt.png
>>
>> I think it's because the commas imply an OR condition, but here we want 
>> an AND :)
>>
>> So with a a tiny bit of tweaking the correct filter is : 
>>
>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Here's a live demo : 
>>
>>
>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>
>>> - In the fields cases we have a workaround with `fields` operator. It 
>>> has suffixs (exclude, include)
>>> - I think that there in't any tiddler with those tags. The search is the 
>>> tiddler with all these tags (¿and any other?)
>>>
>>> In the case of titles, you find a issue, but I don't know its reason. I 
>>> was trying to find a workaround but i wasn't lucky. I also found that the 
>>> match operator doesn't support multiple parameters.
>>>
>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones 
>>> escribió:
>>>
 Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] 
 }}}

 On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:

> Very interesting. 
>
> I think he documentation should be expanded to detail this. Multiple 
> parameters to operators are only documented in a few operators, but if I 
> read this correctly they can work on operators in *general*?
>
> If general you may expect this to work ```{{{ 
> [title[tid1],[tid2],[tid3]] }}}``` it does not.
> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>
>> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
>> containing
>> ```
>> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>> ```
>>
>> and another tiddler with the four tags (note capitalization and 
>> spaces in the tag values).
>>
>> It *does* seem to work on both versions of TW
>> -e
>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>
>>> Alvaro;
>>>
>>> You suggested something like this
>>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>
>>> As far as I can see this does not work on the pre-release and the 
>>> t6ag format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not 
>>> documented
>>>
>>> Does not work. So I asked if you tested this?
>>>
>>>
>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>
 I don't know if I understand you.


 El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones 
 escribió:

> Alvaro;
>
> Have you tested this?
>
> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
> :filter[tags[]count[]compare:eq[4]]  }}}
>
> I cant see it working. Here 
>  is says 
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters 
> which are separated by a  ,  character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are 
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> It works fine. I tried to find a alternative, but I wasn't lucky.
>>
>> When I resee your filter, I remember about the multiple 
>> parameters in filter operator with commas (from last version, 
>> 5.1.23). And 
>> we can add a second filter run that it applies your filter to result 
>> of 
>> first run. Then you can rewrite 

[tw5] Re: Sharing a hosted wiki with other Contributors

[Radiant Fork]

That doesn't fit the kind of flow I'm trying to generate, but I appreciate 
the suggestion. Do you know any other way to have an online hosted wiki 
with two contributors? Any leads on where to look for something like this?

On Tuesday, September 28, 2021 at 5:43:38 AM UTC+5:30 cj.v...@gmail.com 
wrote:

> It might be safer for your remain solo editor of the TiddlyWiki, and have 
> content that is multi-editor kept on Google Drive (Docs, Sheets, Slides, 
> Drawings), because those support simultaneous/collaborative editing really 
> well.
>
> Say you have a TiddlyWiki tiddler about Blender.  Create a related Google 
> Doc (where everybody can put in information about blender, and add comments 
> related to whatever) and embed it in your tiddler.
>
> Now your TiddlyWiki has content that makes sense there, but also acts as a 
> portal to content that maybe makes more sense somewhere else (for 
> simultaneous/collaborative editing and/or whatever else?
>
>
>
> On Monday, September 27, 2021 at 12:18:05 PM UTC-3 radiant...@gmail.com 
> wrote:
>
>> So I understand that I can open access to wikis by turning them public. 
>> But I wanted to figure out how to give some other logged in users the 
>> permission to add and or edit tiddlers in a wiki. For context, I have a 
>> friend whose learning 3d modelling with blender and I wanna get started 
>> with 2d digital art and I wanna set up a shared wiki so we can share what 
>> we learn and what we made in an organized way. (Don't worry about file 
>> size, we'll be using a shared drive and share links to that instead of 
>> putting it on the wiki)
>
>

-- 
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/6623eb97-a6ad-4f9f-81c7-28fc374eb410n%40googlegroups.com.

[tw5] Re: Sharing a hosted wiki with other Contributors

['Mark S.' via TiddlyWiki]

There is no recognized, safe way to use a TW on the open internet for 
multi-user operation.

If you use a host like tiddlyhost, then you could share by taking turns, 
with a gentleman’s (person’s) agreement when your operating times are and 
what your tiddler naming scheme will be. You will need to remember to 
reload whenever you start a new session in case there have been updates.

Another approach is to both have your own version of an initial TW file. 
Once again agree on a tiddler naming scheme. Then periodically you can pull 
new entries from the friends’ TW and your friend can periodically pull your 
new entries from yours. TW’s list filters makes it pretty easy to find, 
say, all entries that start with “MAS” and were made in the last 3 days. 
You can list them, and then drag them over one by one or download in a JSON 
file and import.


On Monday, September 27, 2021 at 5:13:38 PM UTC-7 cj.v...@gmail.com wrote:

> It might be safer for your remain solo editor of the TiddlyWiki, and have 
> content that is multi-editor kept on Google Drive (Docs, Sheets, Slides, 
> Drawings), because those support simultaneous/collaborative editing really 
> well.
>
> Say you have a TiddlyWiki tiddler about Blender.  Create a related Google 
> Doc (where everybody can put in information about blender, and add comments 
> related to whatever) and embed it in your tiddler.
>
> Now your TiddlyWiki has content that makes sense there, but also acts as a 
> portal to content that maybe makes more sense somewhere else (for 
> simultaneous/collaborative editing and/or whatever else?
>
>
>
> On Monday, September 27, 2021 at 12:18:05 PM UTC-3 radiant...@gmail.com 
> wrote:
>
>> So I understand that I can open access to wikis by turning them public. 
>> But I wanted to figure out how to give some other logged in users the 
>> permission to add and or edit tiddlers in a wiki. For context, I have a 
>> friend whose learning 3d modelling with blender and I wanna get started 
>> with 2d digital art and I wanna set up a shared wiki so we can share what 
>> we learn and what we made in an organized way. (Don't worry about file 
>> size, we'll be using a shared drive and share links to that instead of 
>> putting it on the wiki)
>
>

-- 
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/9770a3ef-95d3-40ed-b53b-26895844c32bn%40googlegroups.com.

[tw5] Some filtering fun

[Charlie Veniot]

Over at TiddlyTalk, in the A list containing tiddlers with the same tags as 
current tiddler? 

 thread, 
I had posted the following as my approach:

<$vars theseTags={{{ [tags[]sort[]join[,]] }}} >

<$list filter="[all[tiddlers]] :filter[tags[]sort[]join[,]match] 
+[!match]">
<$link/>




That got me thinking: what if we wanted a list containing tiddlers with the 
same tags as current tiddler + 0-to-more tags ?

Say we also had Tiddler E with tags "topic a", "topic aa" and "topic b", 
and we wanted that to also be included when we look at Tiddler A?

Modified version of the code above:

<$vars theseTags={{{ [tags[]sort[]join[*]] }}} >

<$list filter="[all[tiddlers]] :filter[tags[]sort[]join[]regexp] 
+[!match]">
<$link/>




Attached file has Tiddlers A-E, A being the one with the goodies.  Download 
and drag into any TiddlyWiki (TiddlyWiki.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/c423c756-7895-41da-82f9-27d398c3280fn%40googlegroups.com.


TiddlersAtoE.json
Description: application/json

[tw5] Re: Just a Filtering Code Pattern

[TW Tones]

JP,

One way of handling all tags on the current tiddler is not to use the 
various tag operators but address the tags field directly.

[all[current]get[tags]] returns the content of the tags field which 
includes all tags.

Does this meet with your requirement?

On Monday, 27 September 2021 at 22:08:07 UTC+10 jn.pierr...@gmail.com wrote:

> Just a thought: it would be fine if the tagging operator could have a 
> "all" parameter which would select tiddlers tagging all of the tags in 
> input (currently, that's "any tag is enough").
>
> Thus we would have a simple and readable solution as:
>
> {{{ [tag1 tag2 tag3 tag4 +[tagging:all[]]] }}}
>
> Le lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>
>> Hello all ! 
>> The filter syntax provided by @Álvaro  is very neat but doesnt match the 
>> requirements of cj.v : counting the tiddlers with 4 specifics tags and 
>> only those tiddlers.
>>
>> See this screenshot  :
>>
>> https://i.imgur.com/lVlsYZt.png
>>
>> I think it's because the commas imply an OR condition, but here we want 
>> an AND :)
>>
>> So with a a tiny bit of tweaking the correct filter is : 
>>
>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Here's a live demo : 
>>
>>
>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>
>>> - In the fields cases we have a workaround with `fields` operator. It 
>>> has suffixs (exclude, include)
>>> - I think that there in't any tiddler with those tags. The search is the 
>>> tiddler with all these tags (¿and any other?)
>>>
>>> In the case of titles, you find a issue, but I don't know its reason. I 
>>> was trying to find a workaround but i wasn't lucky. I also found that the 
>>> match operator doesn't support multiple parameters.
>>>
>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones 
>>> escribió:
>>>
 Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] 
 }}}

 On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:

> Very interesting. 
>
> I think he documentation should be expanded to detail this. Multiple 
> parameters to operators are only documented in a few operators, but if I 
> read this correctly they can work on operators in *general*?
>
> If general you may expect this to work ```{{{ 
> [title[tid1],[tid2],[tid3]] }}}``` it does not.
> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>
>> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
>> containing
>> ```
>> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>> ```
>>
>> and another tiddler with the four tags (note capitalization and 
>> spaces in the tag values).
>>
>> It *does* seem to work on both versions of TW
>> -e
>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>
>>> Alvaro;
>>>
>>> You suggested something like this
>>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>
>>> As far as I can see this does not work on the pre-release and the 
>>> t6ag format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not 
>>> documented
>>>
>>> Does not work. So I asked if you tested this?
>>>
>>>
>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>
 I don't know if I understand you.


 El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones 
 escribió:

> Alvaro;
>
> Have you tested this?
>
> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
> :filter[tags[]count[]compare:eq[4]]  }}}
>
> I cant see it working. Here 
>  is says 
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters 
> which are separated by a  ,  character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are 
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> It works fine. I tried to find a alternative, but I wasn't lucky.
>>
>> When I resee your filter, I remember about the multiple 
>> parameters in filter operator with commas (from last version, 
>> 5.1.23). And 
>> we can add a second filter run that it 

[tw5] Re: Sharing a hosted wiki with other Contributors

[Charlie Veniot]

It might be safer for your remain solo editor of the TiddlyWiki, and have 
content that is multi-editor kept on Google Drive (Docs, Sheets, Slides, 
Drawings), because those support simultaneous/collaborative editing really 
well.

Say you have a TiddlyWiki tiddler about Blender.  Create a related Google 
Doc (where everybody can put in information about blender, and add comments 
related to whatever) and embed it in your tiddler.

Now your TiddlyWiki has content that makes sense there, but also acts as a 
portal to content that maybe makes more sense somewhere else (for 
simultaneous/collaborative editing and/or whatever else?



On Monday, September 27, 2021 at 12:18:05 PM UTC-3 radiant...@gmail.com 
wrote:

> So I understand that I can open access to wikis by turning them public. 
> But I wanted to figure out how to give some other logged in users the 
> permission to add and or edit tiddlers in a wiki. For context, I have a 
> friend whose learning 3d modelling with blender and I wanna get started 
> with 2d digital art and I wanna set up a shared wiki so we can share what 
> we learn and what we made in an organized way. (Don't worry about file 
> size, we'll be using a shared drive and share links to that instead of 
> putting it on the wiki)

-- 
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/e6983e8a-8f97-47e7-b86a-6fd4efab96c8n%40googlegroups.com.

[tw5] Re: Just a Filtering Code Pattern

[Charlie Veniot]

You would need something to wrap tags that have spaces in them.

The "what" to wrap that in, no idea.

On Monday, September 27, 2021 at 9:08:07 AM UTC-3 jn.pierr...@gmail.com 
wrote:

> Just a thought: it would be fine if the tagging operator could have a 
> "all" parameter which would select tiddlers tagging all of the tags in 
> input (currently, that's "any tag is enough").
>
> Thus we would have a simple and readable solution as:
>
> {{{ [tag1 tag2 tag3 tag4 +[tagging:all[]]] }}}
>
> Le lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>
>> Hello all ! 
>> The filter syntax provided by @Álvaro  is very neat but doesnt match the 
>> requirements of cj.v : counting the tiddlers with 4 specifics tags and 
>> only those tiddlers.
>>
>> See this screenshot  :
>>
>> https://i.imgur.com/lVlsYZt.png
>>
>> I think it's because the commas imply an OR condition, but here we want 
>> an AND :)
>>
>> So with a a tiny bit of tweaking the correct filter is : 
>>
>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Here's a live demo : 
>>
>>
>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>
>>> - In the fields cases we have a workaround with `fields` operator. It 
>>> has suffixs (exclude, include)
>>> - I think that there in't any tiddler with those tags. The search is the 
>>> tiddler with all these tags (¿and any other?)
>>>
>>> In the case of titles, you find a issue, but I don't know its reason. I 
>>> was trying to find a workaround but i wasn't lucky. I also found that the 
>>> match operator doesn't support multiple parameters.
>>>
>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones 
>>> escribió:
>>>
 Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] 
 }}}

 On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:

> Very interesting. 
>
> I think he documentation should be expanded to detail this. Multiple 
> parameters to operators are only documented in a few operators, but if I 
> read this correctly they can work on operators in *general*?
>
> If general you may expect this to work ```{{{ 
> [title[tid1],[tid2],[tid3]] }}}``` it does not.
> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>
>> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
>> containing
>> ```
>> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>> ```
>>
>> and another tiddler with the four tags (note capitalization and 
>> spaces in the tag values).
>>
>> It *does* seem to work on both versions of TW
>> -e
>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>
>>> Alvaro;
>>>
>>> You suggested something like this
>>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>
>>> As far as I can see this does not work on the pre-release and the 
>>> t6ag format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not 
>>> documented
>>>
>>> Does not work. So I asked if you tested this?
>>>
>>>
>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>
 I don't know if I understand you.


 El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones 
 escribió:

> Alvaro;
>
> Have you tested this?
>
> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
> :filter[tags[]count[]compare:eq[4]]  }}}
>
> I cant see it working. Here 
>  is says 
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters 
> which are separated by a  ,  character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are 
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> It works fine. I tried to find a alternative, but I wasn't lucky.
>>
>> When I resee your filter, I remember about the multiple 
>> parameters in filter operator with commas (from last version, 
>> 5.1.23). And 
>> we can add a second filter run that it applies your filter to result 
>> of 
>> first run. Then you can rewrite your filter something like this (in 
>> filtering transclusion)

[tw5] Re: LeftBar plugin and node.js server crashes

[Jean-Pierre Rivière]

Hi Matt. Thank you for being there today!

At last, I know there is no hidden javascript to look for. This will help 
me search after the culprit.

Le lundi 27 septembre 2021 à 18:37:37 UTC+2, Mat a écrit :

> Hi jn.pierr I am the author of LeftBar . 
> You really timed your question because I have barely passed by here for a 
> few months now. Unfortunately I can't really answer your question. I only 
> create wikitext plugins and in vanilla TW and the link I gave is the actual 
> source for the plugin. You obviously use nodejs so I'm afraid I don't have 
> any idea what might cause the error or how to resolve it.
>
> With that said, it is not a very complicated construction. And it is 
> likely to be considered a hack because I'm not a real coder. You see the 
> plugin "files", really its shadow tiddlers, just like for any plugin - i.e 
> in the TW Ctrlpanel, click the plugin and see its contents tab. To a great 
> extent, the plugin functions by setting CSS values for the TW native page 
> layout values. The actual menu is a tiddler forced to sit up in the left 
> corner.
>
> <:-)
>
> On Monday, September 27, 2021 at 3:21:28 PM UTC+2 jn.pierr...@gmail.com 
> wrote:
>
>> I’ve encountered a problem with the LeftBar plugin (v2.1.4). It happens 
>> on a brand new empty server edition on node.js (linux arm64, run through 
>> docker) where:
>>
>>- I create a $:/config/FileSystemPaths tiddler whose sole content 
>>is [!is[system]slugify[]] (not interesting but deliberately very reduced)
>>- I then quit the server and import my plugin with
>>
>> tiddlywiki mywiki --load plugin.json 
>>
>> Now’ I start again the server. This sandwich icon of LeftBar is or the 
>> upper left corner. 
>>
>> Then I click on that sandwich icon for LeftBar and the server crashes. 
>> See below:
>>
>> =
>> syncer-server-filesystem: Dispatching 'save' task: 
>> $:/plugins/TWaddle/LeftBar/temp node:internal/fs/utils:879 throw new 
>> ERR_INVALID_ARG_TYPE( ^ TypeError [ERR_INVALID_ARG_TYPE]: The "data" 
>> argument must be of type string or an instance of Buffer, TypedArray, or 
>> DataView. Received undefined at Object.writeFile (node:fs:2106:5) at 
>> Object.exports.saveTiddlerToFile 
>> ($:/core/modules/utils/filesystem.js:414:6) at 
>> $:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:85:13 at 
>> FileSystemAdaptor.getTiddlerFileInfo 
>> ($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:72:2) at 
>> FileSystemAdaptor.saveTiddler 
>> ($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:81:7) at 
>> SaveTiddlerTask.run ($:/core/modules/syncer.js:597:27) at 
>> Syncer.processTaskQueue ($:/core/modules/syncer.js:503:9) at 
>> Function. ($:/core/modules/syncer.js:90:9) at 
>> $tw.Wiki.exports.dispatchEvent ($:/core/modules/wiki.js:133:13) at 
>> $:/core/modules/wiki.js:166:10 { code: 'ERR_INVALID_ARG_TYPE' }
>> =
>>   
>>
>> I suppose my plugin is not correctly installed. So I was about to do it 
>> the proper way with tiddlywiki --build index and after having set 
>> the TIDDLYWIKI_PLUGIN_PATH environment variable. But there is a problem: I 
>> don’t know how to get all the individual tiddlers of the plugin. The plugin 
>> shows its shadow tiddlers, which I can export. But what for the core of the 
>> plugin, actual code? I have not been able to get any source code repository 
>> for LeftBar.
>>
>> My questions:
>>
>>- is my diagnostic of the crash correct (bad installation of the 
>>plugin)?
>>- how could I get all of the files of a plugin given its json file?
>>
>> Thank you for your help!
>>
>

-- 
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/c1a41559-ca67-4242-8641-e1cdbea50be9n%40googlegroups.com.

[tw5] Re: LeftBar plugin and node.js server crashes

[Mat]

Hi jn.pierr I am the author of LeftBar . 
You really timed your question because I have barely passed by here for a 
few months now. Unfortunately I can't really answer your question. I only 
create wikitext plugins and in vanilla TW and the link I gave is the actual 
source for the plugin. You obviously use nodejs so I'm afraid I don't have 
any idea what might cause the error or how to resolve it.

With that said, it is not a very complicated construction. And it is likely 
to be considered a hack because I'm not a real coder. You see the plugin 
"files", really its shadow tiddlers, just like for any plugin - i.e in the 
TW Ctrlpanel, click the plugin and see its contents tab. To a great extent, 
the plugin functions by setting CSS values for the TW native page layout 
values. The actual menu is a tiddler forced to sit up in the left corner.

<:-)

On Monday, September 27, 2021 at 3:21:28 PM UTC+2 jn.pierr...@gmail.com 
wrote:

> I’ve encountered a problem with the LeftBar plugin (v2.1.4). It happens on 
> a brand new empty server edition on node.js (linux arm64, run through 
> docker) where:
>
>- I create a $:/config/FileSystemPaths tiddler whose sole content 
>is [!is[system]slugify[]] (not interesting but deliberately very reduced)
>- I then quit the server and import my plugin with
>
> tiddlywiki mywiki --load plugin.json 
>
> Now’ I start again the server. This sandwich icon of LeftBar is or the 
> upper left corner. 
>
> Then I click on that sandwich icon for LeftBar and the server crashes. See 
> below:
>
> =
> syncer-server-filesystem: Dispatching 'save' task: 
> $:/plugins/TWaddle/LeftBar/temp node:internal/fs/utils:879 throw new 
> ERR_INVALID_ARG_TYPE( ^ TypeError [ERR_INVALID_ARG_TYPE]: The "data" 
> argument must be of type string or an instance of Buffer, TypedArray, or 
> DataView. Received undefined at Object.writeFile (node:fs:2106:5) at 
> Object.exports.saveTiddlerToFile 
> ($:/core/modules/utils/filesystem.js:414:6) at 
> $:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:85:13 at 
> FileSystemAdaptor.getTiddlerFileInfo 
> ($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:72:2) at 
> FileSystemAdaptor.saveTiddler 
> ($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:81:7) at 
> SaveTiddlerTask.run ($:/core/modules/syncer.js:597:27) at 
> Syncer.processTaskQueue ($:/core/modules/syncer.js:503:9) at 
> Function. ($:/core/modules/syncer.js:90:9) at 
> $tw.Wiki.exports.dispatchEvent ($:/core/modules/wiki.js:133:13) at 
> $:/core/modules/wiki.js:166:10 { code: 'ERR_INVALID_ARG_TYPE' }
> =
>   
>
> I suppose my plugin is not correctly installed. So I was about to do it 
> the proper way with tiddlywiki --build index and after having set 
> the TIDDLYWIKI_PLUGIN_PATH environment variable. But there is a problem: I 
> don’t know how to get all the individual tiddlers of the plugin. The plugin 
> shows its shadow tiddlers, which I can export. But what for the core of the 
> plugin, actual code? I have not been able to get any source code repository 
> for LeftBar.
>
> My questions:
>
>- is my diagnostic of the crash correct (bad installation of the 
>plugin)?
>- how could I get all of the files of a plugin given its json file?
>
> Thank you for your help!
>

-- 
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/52f63da4-519a-4778-b392-3b3a86def95en%40googlegroups.com.

[tw5] Sharing a hosted wiki with other Contributors

[Radiant Fork]

So I understand that I can open access to wikis by turning them public. But 
I wanted to figure out how to give some other logged in users the 
permission to add and or edit tiddlers in a wiki. For context, I have a 
friend whose learning 3d modelling with blender and I wanna get started 
with 2d digital art and I wanna set up a shared wiki so we can share what 
we learn and what we made in an organized way. (Don't worry about file 
size, we'll be using a shared drive and share links to that instead of 
putting it on the wiki)

-- 
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/430024b3-996c-40ee-a92a-aaf4f94707dbn%40googlegroups.com.

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

[Petri M.]

Ah I did not know that. But it does not seem to work, probably because I 
have 5.1.22. Maybe I'll have to look into upgrading if I can't figure this 
out.

Thanks!

On Monday, September 27, 2021 at 3:43:24 PM UTC+3 Soren Bjornstad wrote:

> Petri,
>
> Are you aware you can use the down arrow key to select items in that list? 
> (You need 5.1.23 or higher I think.)
>
> On Monday, September 27, 2021 at 5:16:56 AM UTC-5 Petri M. wrote:
>
>> I am trying to remove some extra tabbing when I do ctrl+L and search for 
>> a tiddler and try to link to it. Now it tabs through the search "tabs" 
>> first and then goes to the list. I think I can just remove that with the 
>> CSS attribute tabindex="-1" but I have no idea how to actually do it. I 
>> tried to set buttonTemplate so transclude my own template which would then 
>> have this command in it but I can't seem to get it to work. I don't think 
>> the template adds the attribute to the button itself, just to the content 
>> inside of the button.
>>
>> How can I achieve this?
>>
>> Thanks,
>> Petri
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/221df5dc-7e0e-47cd-9762-061f776ca40cn%40googlegroups.com.

[tw5] LeftBar plugin and node.js server crashes

[Jean-Pierre Rivière]

I’ve encountered a problem with the LeftBar plugin (v2.1.4). It happens on 
a brand new empty server edition on node.js (linux arm64, run through 
docker) where:

   - I create a $:/config/FileSystemPaths tiddler whose sole content 
   is [!is[system]slugify[]] (not interesting but deliberately very reduced)
   - I then quit the server and import my plugin with

tiddlywiki mywiki --load plugin.json 

Now’ I start again the server. This sandwich icon of LeftBar is or the 
upper left corner. 

Then I click on that sandwich icon for LeftBar and the server crashes. See 
below:

=
syncer-server-filesystem: Dispatching 'save' task: 
$:/plugins/TWaddle/LeftBar/temp node:internal/fs/utils:879 throw new 
ERR_INVALID_ARG_TYPE( ^ TypeError [ERR_INVALID_ARG_TYPE]: The "data" 
argument must be of type string or an instance of Buffer, TypedArray, or 
DataView. Received undefined at Object.writeFile (node:fs:2106:5) at 
Object.exports.saveTiddlerToFile 
($:/core/modules/utils/filesystem.js:414:6) at 
$:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:85:13 at 
FileSystemAdaptor.getTiddlerFileInfo 
($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:72:2) at 
FileSystemAdaptor.saveTiddler 
($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:81:7) at 
SaveTiddlerTask.run ($:/core/modules/syncer.js:597:27) at 
Syncer.processTaskQueue ($:/core/modules/syncer.js:503:9) at 
Function. ($:/core/modules/syncer.js:90:9) at 
$tw.Wiki.exports.dispatchEvent ($:/core/modules/wiki.js:133:13) at 
$:/core/modules/wiki.js:166:10 { code: 'ERR_INVALID_ARG_TYPE' }
=
  

I suppose my plugin is not correctly installed. So I was about to do it the 
proper way with tiddlywiki --build index and after having set 
the TIDDLYWIKI_PLUGIN_PATH environment variable. But there is a problem: I 
don’t know how to get all the individual tiddlers of the plugin. The plugin 
shows its shadow tiddlers, which I can export. But what for the core of the 
plugin, actual code? I have not been able to get any source code repository 
for LeftBar.

My questions:

   - is my diagnostic of the crash correct (bad installation of the plugin)?
   - how could I get all of the files of a plugin given its json file?

Thank you for your help!

-- 
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/03256b3e-89c8-48e9-8205-bc21d335d263n%40googlegroups.com.

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

[Soren Bjornstad]

Petri,

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

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/96c5f928-d691-479f-9c02-83964fbee202n%40googlegroups.com.

[tw5] Re: Just a Filtering Code Pattern

[Jean-Pierre Rivière]

Just a thought: it would be fine if the tagging operator could have a "all" 
parameter which would select tiddlers tagging all of the tags in input 
(currently, that's "any tag is enough").

Thus we would have a simple and readable solution as:

{{{ [tag1 tag2 tag3 tag4 +[tagging:all[]]] }}}

Le lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :

> Hello all ! 
> The filter syntax provided by @Álvaro  is very neat but doesnt match the 
> requirements of cj.v : counting the tiddlers with 4 specifics tags and 
> only those tiddlers.
>
> See this screenshot  :
>
> https://i.imgur.com/lVlsYZt.png
>
> I think it's because the commas imply an OR condition, but here we want an 
> AND :)
>
> So with a a tiny bit of tweaking the correct filter is : 
>
> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]] 
> :filter[tags[]count[]compare:eq[4]] }}}
>
> Here's a live demo : 
>
>
> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>
>> - In the fields cases we have a workaround with `fields` operator. It has 
>> suffixs (exclude, include)
>> - I think that there in't any tiddler with those tags. The search is the 
>> tiddler with all these tags (¿and any other?)
>>
>> In the case of titles, you find a issue, but I don't know its reason. I 
>> was trying to find a workaround but i wasn't lucky. I also found that the 
>> match operator doesn't support multiple parameters.
>>
>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones 
>> escribió:
>>
>>> Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] 
>>> }}}
>>>
>>> On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:
>>>
 Very interesting. 

 I think he documentation should be expanded to detail this. Multiple 
 parameters to operators are only documented in a few operators, but if I 
 read this correctly they can work on operators in *general*?

 If general you may expect this to work ```{{{ 
 [title[tid1],[tid2],[tid3]] }}}``` it does not.
 or {{{ [all[current]get[caption],[description]] }}}``` it does not.
 On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:

> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
> containing
> ```
> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
> :filter[tags[]count[]compare:eq[4]] }}}
> ```
>
> and another tiddler with the four tags (note capitalization and spaces 
> in the tag values).
>
> It *does* seem to work on both versions of TW
> -e
> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>
>> Alvaro;
>>
>> You suggested something like this
>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> As far as I can see this does not work on the pre-release and the 
>> t6ag format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not 
>> documented
>>
>> Does not work. So I asked if you tested this?
>>
>>
>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>
>>> I don't know if I understand you.
>>>
>>>
>>> El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones 
>>> escribió:
>>>
 Alvaro;

 Have you tested this?

 {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
 :filter[tags[]count[]compare:eq[4]]  }}}

 I cant see it working. Here 
  is says 

 * NEW IN: 5.1.23 Filter operators support multiple parameters which 
 are separated by a  ,  character.*

 *For example: [param1],[param2] or ,{param2}*
 However as far as I can see only if such multiple parameters are 
 documented in the operator in question.

 Tones
 On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:

> It works fine. I tried to find a alternative, but I wasn't lucky.
>
> When I resee your filter, I remember about the multiple parameters 
> in filter operator with commas (from last version, 5.1.23). And we 
> can add 
> a second filter run that it applies your filter to result of first 
> run. 
> Then you can rewrite your filter something like this (in filtering 
> transclusion)
> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
> :filter[tags[]count[]compare:eq[4]]  }}}
>
> Although maybe it be less understandble for you.
>
>
> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
> jn.pierr...@gmail.com escribió:

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

[Petri M.]

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

How can I achieve this?

Thanks,
Petri

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7226ac70-e8a6-49b0-9f00-90b800406894n%40googlegroups.com.

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

[maki aea]

the link on the AFNNCF's own site has changed: (you can access it from the 
AIM menu on https://manuals.annafreud.org/ambit/ )

https://manuals.annafreud.org/ambit/#AIM%20questionnaire%20-%20interactive%20version
On Tuesday, August 3, 2021 at 11:48:52 PM UTC+1 TW Tones wrote:

> Liz,
>
> Thanks for sharing. Its great to get such insights.
>
> Toneas
>
> On Wednesday, 4 August 2021 at 03:00:55 UTC+10 elizabeth...@googlemail.com 
> wrote:
>
>> Hi all, I'm reposting this because my first reply got deleted (spam 
>> filter, I assume!)
>>
>> I wanted to add some reflections from the Anna Freud centre. We are very 
>> excited about this development, for two main reasons: 
>>
>> 1. It helps us to directly connect outcomes measurement to the evidence 
>> base for what works for different types of problem. 
>>
>> The interactive AIM sits within our tiddlywiki treatment manual, which 
>> means that the suggested interventions list generated by the questionnaire 
>> links directly into content on how to deliver the most appropriate 
>> evidence-based intervention. We will easily be able to update this as the 
>> evidence-base evolves. 
>>
>> 2. It helps us to overcome a major barrier to using outcomes measures in 
>> practice: feasibility/ practically 
>>
>> Generally outcome measures like this are valued by health and social care 
>> workers in principle, but the impracticality of scoring and recording the 
>> data often results in low use of the measures in practice. 
>>
>> We want to encourage services working with young people to use the AIM to 
>> plan care and assess outcome for individual young people, but also to to 
>> collate the data to evaluate their service as a whole. Here is a paper 
>> evaluating outcomes of a young person's substance use service that looks at 
>> a series of pre- and post-treatment AIM scores for 100 young people: 
>> https://journals.sagepub.com/doi/abs/10.1177/1359104521994875?journalCode=ccpa
>>  
>>
>> Jeremy's interactive AIM, with its different options for saving the 
>> results, makes it easy for workers to save the results for multiple 
>> purposes - perhaps saving the .doc file to the young person's health 
>> record, then copying the data into a spreadsheet capturing the whole team's 
>> outcomes. 
>>
>> Thanks, Jeremy!
>>
>> Liz
>>
>> On Friday, 16 July 2021 at 08:14:00 UTC+1 TiddlyTweeter wrote:
>>
>>> Ciao Jeremy
>>>
>>> Thanks for that! It helps clarify what I am trying to do!
>>>
>>> I will post an update note in the original thread about how I look at 
>>> the issue now.
>>>
>>> Best wishes
>>> TT
>>>
>>> On Thursday, 15 July 2021 at 10:39:57 UTC+2 jeremy...@gmail.com wrote:
>>>
 Hi TT

 Thank you – I was hoping you might find the translation mechanism 
 interesting too, does it fit your needs discussed in that other thread?

 You can try out the translation mechanism in the demo by switching the 
 language to "Spanish" in the sidebar tab; you'll get gobbledegook that 
 isn't Spanish, but it illustrates the difference. (Note that in the demo 
 only the UI is translated, the questions themselves there are only in 
 English).

 Best wishes

 Jeremy.

 Very interesting to see! Thanks.
 I ran through the whole thing and completed all questions. It is a 
 seriously real application! :-)

 As a side note: The Anna Freud people designed the questions really 
 well. It is extremely difficult to design such questionnaires in a way 
 that 
 makes sense in normal English AND can produce operational,  quantitative, 
 meaningful, results.  Hats off to them!

 Best wishes
 TT

 On Wednesday, 14 July 2021 at 12:46:02 UTC+2 jeremy...@gmail.com wrote:

> I’ve recently completed a small project for the Anna Freud National 
> Centre for Children and Families in London (see https://annafreud.org/) 
> to make an interactive questionnaire that has some interesting features:
>
>
>- Fairly sophisticated scoring of the answers to multiple choice 
>questions
>- Generating spreadsheet files that can be downloaded and opened 
>in Excel, and .DOC files that open in Microsoft Word
>- Copying spreadsheet data to the clipboard for pasting directly 
>into Excel
>
>
> In its current form, the questionnaire is not directly reusable for 
> other purposes, but I hope some of the techniques will prove useful to 
> others.
>
> The context for this work is that the AFNCCF trains teams of care 
> workers in Britain and around the world to work with the most troubled, 
> hard to reach young people and their families.  For more than a decade, 
> they have been working on the Adolescent Integrative Measure (AIM) to 
> help 
> care workers make a systematic, objective record of the problems 
> affecting 
> a particular young person, and to make suggestions of the 

[tw5] Re: Just a Filtering Code Pattern

[Télumire]

Hello all ! 
The filter syntax provided by @Álvaro  is very neat but doesnt match the 
requirements of cj.v : counting the tiddlers with 4 specifics tags and only 
those tiddlers.

See this screenshot  :

https://i.imgur.com/lVlsYZt.png

I think it's because the commas imply an OR condition, but here we want an 
AND :)

So with a a tiny bit of tweaking the correct filter is : 

{{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]] 
:filter[tags[]count[]compare:eq[4]] }}}

Here's a live demo : 

https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :

> - In the fields cases we have a workaround with `fields` operator. It has 
> suffixs (exclude, include)
> - I think that there in't any tiddler with those tags. The search is the 
> tiddler with all these tags (¿and any other?)
>
> In the case of titles, you find a issue, but I don't know its reason. I 
> was trying to find a workaround but i wasn't lucky. I also found that the 
> match operator doesn't support multiple parameters.
>
> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones 
> escribió:
>
>> Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] 
>> }}}
>>
>> On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:
>>
>>> Very interesting. 
>>>
>>> I think he documentation should be expanded to detail this. Multiple 
>>> parameters to operators are only documented in a few operators, but if I 
>>> read this correctly they can work on operators in *general*?
>>>
>>> If general you may expect this to work ```{{{ 
>>> [title[tid1],[tid2],[tid3]] }}}``` it does not.
>>> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
>>> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>>>
 I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
 containing
 ```
 {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
 :filter[tags[]count[]compare:eq[4]] }}}
 ```

 and another tiddler with the four tags (note capitalization and spaces 
 in the tag values).

 It *does* seem to work on both versions of TW
 -e
 On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:

> Alvaro;
>
> You suggested something like this
> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
> :filter[tags[]count[]compare:eq[4]] }}}
>
> As far as I can see this does not work on the pre-release and the t6ag 
> format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not 
> documented
>
> Does not work. So I asked if you tested this?
>
>
> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>
>> I don't know if I understand you.
>>
>>
>> El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones 
>> escribió:
>>
>>> Alvaro;
>>>
>>> Have you tested this?
>>>
>>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>>> :filter[tags[]count[]compare:eq[4]]  }}}
>>>
>>> I cant see it working. Here 
>>>  is says 
>>>
>>> * NEW IN: 5.1.23 Filter operators support multiple parameters which 
>>> are separated by a  ,  character.*
>>>
>>> *For example: [param1],[param2] or ,{param2}*
>>> However as far as I can see only if such multiple parameters are 
>>> documented in the operator in question.
>>>
>>> Tones
>>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>>
 It works fine. I tried to find a alternative, but I wasn't lucky.

 When I resee your filter, I remember about the multiple parameters 
 in filter operator with commas (from last version, 5.1.23). And we can 
 add 
 a second filter run that it applies your filter to result of first 
 run. 
 Then you can rewrite your filter something like this (in filtering 
 transclusion)
 {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
 :filter[tags[]count[]compare:eq[4]]  }}}

 Although maybe it be less understandble for you.


 El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
 jn.pierr...@gmail.com escribió:

> That's fine by me.
>
> And yes filters are fun even if sometimes a bit tricky.
>
> So for the fun of it, you could arrange your filter so that the 
> input would be the 4 tags you want.
>
> something like that:
>
> \define fun(tags)
> <$set variable=occ filter="[[$tags]put your filter code 
> here...count[]]">Seen <> tiddlers with tags $tags$
> \end
>
> Sometimes,