[tw5] Re: Speech-to-Text v1.0.5 is here!

[BurningTreeC]

@TiddlyTweeter
at https://cloud.google.com/speech-to-text/docs/languages you can check if 
your chosen language supports spoken punctuation
the insertion of boilerplate text may be possible, we'll have to think 
about it a little bit
concatenating transcript fragments could be done by a simple button. Maybe 
we should add $:/tags/TranscriptFragment to a new Transcript Tiddler so 
that filtering for transcript tiddlers gets easier?

Speech Recognition is not perfect, it sometimes doesn't get the text fully 
right. That's a limitation we cannot change

best wishes
Simon
flanc...@gmail.com schrieb am Sonntag, 15. August 2021 um 14:36:26 UTC+2:

> @TiddlyTweeter: 
>
> To answer just your question about punctuation, I have tested the plugin 
> with various punctuation words. The result is, by saying "comma", you have 
> a comma. The same works for question marks, periods, etc. Some of your 
> other points, I felt were really good, as well. Hopefully @BurningTreeC and 
> I can implement them in later versions of the plugin!
>
> On Sunday, August 15, 2021 at 6:10:50 AM UTC-4 TiddlyTweeter wrote:
>
>> Ciao Flanc & BTC ...
>>
>> I agree with @Tones "Wow!". 
>> And the tool has already changed how I use some wiki.
>>
>> ONE point I'd like to quickly make whilst the iron is hot. (Which I will 
>> fill in details for later with more precision.)
>>
>> From MY point of view, I want to get my DICTATION/TRANSCRIPTION so it is 
>> optimally efficient. 
>> (FYI, I'm far less concerned with controlling the wiki outwith dictation. 
>> I'm also not that interested in whether it can "read-back" or record to an 
>> audio file. 
>>
>> *First I need to get basic transcription working really well! *:)
>>
>> To give simple examples of, I think, main *dictation focused needs* ...
>>
>> 1 - A way to verbally insert PUNCTUATION. (Without it, long dictation 
>> produces unwieldy texts.)
>>
>> 2 - A way to verbally INSERT "boilerplate text". 
>> For instance: "*Ok Wiki insert exercise intro"*. Which might(?) be text 
>> in a Tiddler called "Exercise Intro" like "Lie on you back and rest a 
>> moment, scanning for how your back contacts the floor. Notice which parts 
>> touch it and which parts don't."
>>
>> You get the* idea? *
>>
>> *What I don't currently understand is how in dictation you'd execute a 
>> command to INSERT "boilerplate" text into the ongoing transcription?*
>>
>> 3 - A way to CONCATENATE transcript fragments. 
>> WHAT do I mean? In a test I dictated a long text in small segments. The 
>> result being that I ended up with ... 
>>
>>   - New Transcript
>>   - New Transcript 1
>> *... through to ...*
>>- New Transcript 23
>>
>> Manually joining those would be a fag. Maybe we need a way to click a 
>> button to CONCATENATE* (latest last) *all those new transcript fragments?
>>
>> Just a thought, and likely YOU don't need to devise that as a standard TW 
>> macro could likely do it?
>> BUT I did think it a real functional need for folk interested in serious 
>> dictation to be able to manipulate Transcripts, and this is one of the 
>> needs?
>>
>> It is also fun to play with! :-)
>>
>> Thanks & best wishes
>> TT
>>
>>

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

[tw5] Re: [tw] Re: Continue order list numbering after code block?

[Douglas Glenn]

Ouch. You fixed the third bullet issue with it though.

On Sunday, August 15, 2021 at 11:25:17 PM UTC-4 cj.v...@gmail.com wrote:

> Hi,
>
> The first  is fine, but the second  should be a 
>
> On Monday, August 16, 2021 at 12:03:18 AM UTC-3 dgle...@gmail.com wrote:
>
>> @Eric Shulman
>> I appreciate your attempt to to show me a fix, I do. But as demonstrated 
>> below, it doesn't work. It created an oddity of issues (I am using 5.1.23 
>> and CamelCase is off.)
>> My original tiddler is at the bottom showing the formatting that I used 
>> that did work.
>>
>> Duplicating the code you've shown results in the mess below. All the 
>> lines on the second bullet run together and the third bullet point is 
>> treated as a second level bullet to the 2nd bullet.
>> [image: tiddly1.jpg]
>>
>> I fixed the issue with the paragraphs running together but it doesn't 
>> resolve the issue with the 3rd bullet being shown as a secondary level as 
>> previously described.
>> [image: tiddly2.jpg]
>>  
>> My attempt to correct the third bullet problem remains unresolved. 
>> [image: tiddly3.jpg]
>>
>> This is a snapshot of the original tiddler I was working on and what 
>> ended up working for me. On another note, none of the @@ codes worked 
>> either even when directly copied from the example. So I ended up using the 
>> built in 'highlighting' instead. Inline CSS didn't work when used with the 
>> ,  or  tags and I'd spent enough time as it was to get it 
>> looking as I wanted. 
>> [image: originalTiddler.jpg]
>> And another with line numbering and a code block.
>> [image: tiddlerNumberingList.jpg]
>>
>> I'm not adverse at all if someone wishes to correct me and provide a 
>> working example on their end, and if it doesn't work on my end,  I'll turn 
>> to disabling any plugins installed after the TW5 file was installed and 
>> take a look at what plugin I had to disable for it to work as they've shown 
>> me. I don't have many. I try to load only those I need on my collection of 
>> TW5 files for other purposes.
>>
>> Thoughts? Corrections? I'm open to constructive criticism. 
>>
>> On Friday, August 13, 2021 at 8:22:36 PM UTC-4 Eric Shulman wrote:
>>
>>> On Friday, August 13, 2021 at 3:17:28 PM UTC-7 dgle...@gmail.com wrote:
>>>
 Although this is an old thread,
>>>
>>>
>>> As you note, this is an old thread (over 6 years old!).
>>>
>>> *A general solution has long ago been documented* here:
>>> https://tiddlywiki.com/#Lists%20in%20WikiText 
>>> Scroll down to the end of the tiddler and you will see a heading
>>> labeled "Paragraphs in Lists", which describes enclosing the
>>> desired content within a ..., like this:
>>>
>>> # Step 1
>>> # Step 2
>>> # Step 3
>>>
>>> Here is the first of several paragraphs. Note that the double linebreak 
>>> preceding this paragraph is significant.
>>>
>>> And here is the second of several paragraphs.
>>> 
>>> # Step 4
>>> # Step 5
>>> # Step 6
>>>
>>> Note that this technique will work with ANY pair of matching HTML tags.  
>>> *You 
>>> can even use made up tags, like ...*.  The key points are 
>>> these:
>>>
>>>- *the opening tag is placed at the end of the first line that 
>>>starts the the bullet item*
>>>- *there is a double linebreak following that opening tag.*
>>>
>>> enjoy,
>>> -e
>>>
>>

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

[tw5] Re: Highlighting duplicates in lists

[TW Tones]

Hio,

Back in my code

<$list filter="[all[]prefix[New]has[field]]">
   get[field]match{!!field}then[color: 
red;]] }}}>* <> {{!!field}}*




*<> {{!!field}} *is the display
replace this with 
*{{{ [all[current]get[field]format:date[]] }}}*
Not tested by me on this occasion

where field is the chosen fieldname.

Regards
Tones

On Monday, 16 August 2021 at 12:14:51 UTC+10 mohamed...@hotmail.com wrote:

> Thank you tones
>
> The real life example is to evaluate duplicate dates, so the actual real 
> values populating the fields are not  1 ,2 , etc.. they are actual dates , 
> IE . 2021062506295,   20210811055859000,etc.
> and so what i was trying is to  do is have the highlighted duplicate 
> values converted from the tiddly wiki format they are stored in in their 
> respective fields , to a normal readable format when displayed in the filter
>
> the
> On Monday, August 16, 2021 at 2:34:07 AM UTC+2 TW Tones wrote:
>
>> Mohammad,
>>
>> I am confused, until now the fields  field_example,  field_example1,  
>> field_example2 did not contain dates. 
>>
>>- Are you trying to convert these to dates?
>>- the view widget format=date only works on tiddlywiki full serial 
>>number dates!
>>
>> Perhaps step back and describe what you want to do in the real world, not 
>> with tiddlywiki code that may or may not be correct. 
>>
>> Regards
>> Tones
>>
>> On Monday, 16 August 2021 at 01:46:55 UTC+10 mohamed...@hotmail.com 
>> wrote:
>>
>>> HI tones,
>>>
>>> sorry i guess i asked the wrong question, what i wanted to know is where 
>>> to place the widget  in the code , if i do it that way , it no longer 
>>> highlights duplicates
>>>
>>>  <>: |  
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> variable=field-value>
>>> <$view field="field_example "format=date template=""/>
>>> <$view field="field_example1"format=date template=""/>
>>> <$view field="field_example2"format=date template=""/>
>>>
>>>  matchthen[color: 
>>> red;]] }}}><>
>>>
>>> 
>>>
>>> i also tried  adding format:date[DDD]] , which didn't yield any results 
>>>
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> format:date[DDD]] variable=field-value> 
>>> On Sunday, August 15, 2021 at 10:12:57 AM UTC+2 TW Tones wrote:
>>>
 Look for and use the viewWidget and use the format date with a 
 template, or the format relativedate

 Get into the habit also of searching in tiddlywiki.com to learn how to 
 do things.
 [image: Snag_c8a06a9.png]

 eg;

 <$view field=created format=date template=""/>

 <$view field=created format=relativedate/>

  5.1.23 now allows this inside filters. 
 

 Regards
 Tones

 On Sunday, 15 August 2021 at 10:26:32 UTC+10 mohamed...@hotmail.com 
 wrote:

> Sorry one more questions
>
> if the values are dates, how can they be displayed in normal format 
> ,and not the tiddly wiki format
>
> On Monday, August 9, 2021 at 1:10:18 AM UTC+2 paulgilbert2000 wrote:
>
>> Thank you tones
>>
>> Will take me a while to understand all that . but it works like a 
>> charm , and its even more than what i have asked for
>>
>> thanks again:)
>>
>> On Sunday, August 8, 2021 at 7:31:10 AM UTC+2 TW Tones wrote:
>>
>>> Mohamad,
>>>
>>> I am happy to look at solving the problem presented but my suspicion 
>>> remains that there may be a different way to put the question in the 
>>> first 
>>> place. 
>>>
>>> Sometimes a question can be rephrased such that the answer is 
>>> simpler to find.
>>>
>>>- In this we have multiple tiddlers, with multiple fields, with 
>>>*values* that may be duplicated across these tiddlers/fields.
>>>- in effect you want to list all tiddlers using the select 
>>>fields, list these for each tiddler then for each found value
>>>   -  detect when that value occurs in any other tiddler (not 
>>>   self?) or select fields, if it does highlight it.
>>>- I am not sure why you want to do this and can think of many 
>>>ways to list/interpret the data! 
>>>- What about triplicates?
>>>- What about duplicates in the same tiddler?
>>>
>>> I think using your test data this is what you wanted?
>>>
>>> 
>>> <$list filter="[all[]has[field_example]]">
>>><$set name=other-values 
>>> filter="[all[]!get[field_example]] 
>>> [all[]!titleget[field_example2]] 
>>> [all[]!titleget[field_example3]] +[sort[]]">
>>><>: |  
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> variable=field-value>

[tw5] Re: Just a goofy thought: a way to get javascript into a Tiddler

[TW Tones]

Charlie,

Thanks for this. 

   - I presume it is secure because the iframe acts like a sandbox
   - The result will be what is displayed because there is no permitted way 
   to impact the wiki

I wonder if 

   - A template can be used rather than the variable? yes the following 
   worked
   
   - Use a TiddlyWiki template for the content of the iframe may need to 
   wikify first.

Have you played with the* innerwiki plugin* it's similar but different? It 
can pass a lot more data to the iframe (I think), in fact can build a whole 
wiki inside the iframe.

Speculation;

   - Could this be used by students of javascript?
   - what kind of Javascript code can be implemented this way?
   - Could it access functions defined in the parent wiki eg raw tags?
  - I suppose it could if added to the template.
   - Could we use iframes in which to publish complete html pages including 
   javascript as a website development or learning tool.

Regards
Tones

On Monday, 16 August 2021 at 12:39:05 UTC+10 cj.v...@gmail.com wrote:

> Better to keep the HTML readable, drag the attached json with two tiddlers 
> into some TiddlyWiki:
>
> On Sunday, August 15, 2021 at 11:27:41 PM UTC-3 Charlie Veniot wrote:
>
>> I don't know what made me think of this.
>>
>> In case this has not been brought up in a while (I doubt this is new to 
>> seasoned folk) ...
>>
>> I was thinking: could I use an iFrame to include simple javascript in a 
>> tiddler without getting into macros or plugins that enable javascript.
>>
>> And, if I could, then could I set things up so that the iFrame is showing 
>> javascript dynamically created by the tiddler ?
>>
>> So here is a way to show a digital clock in TiddlyWiki, for 
>> non-programmers who just want to copy and paste javascript code from the 
>> web without figuring out how the javascript code works :
>>
>> Put this in a brand new tiddler:
>>
>> *<$vars* *vSrcDoc*={{{ [[
>> let clockEl = document.getElementById("clockDiv");function 
>> getClockTime() {  let date = new Date();  let hr = 
>> date.getHours();  let min = date.getMinutes();  let sec = 
>> date.getSeconds();  hr = ("0" + hr).slice(-2);  min = ("0" + 
>> min).slice(-2);  sec = ("0" + sec).slice(-2);  clockEl.innerHTML = 
>> `${hr}:${min}:${sec}`;}setInterval(getClockTime, 1000);  
>> ]] }}}*>*
>> *>* style="border:none;width:100%;"
>> *>*
>> **
>>
>> Sneaky sneaky, has me wondering what kind of other fun things could be 
>> done...
>>
>

-- 
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/5fd5bd22-1f07-4df2-9f23-40586c8c2d8cn%40googlegroups.com.

[tw5] Re: [tw] Re: Continue order list numbering after code block?

[Eric Shulman]

On Sunday, August 15, 2021 at 8:03:18 PM UTC-7 dgle...@gmail.com wrote:

> @Eric Shulman
> I appreciate your attempt to to show me a fix, I do. But as demonstrated 
> below, it doesn't work. It created an oddity of issues (I am using 5.1.23 
> and CamelCase is off.)
> My original tiddler is at the bottom showing the formatting that I used 
> that did work.
> Duplicating the code you've shown results in the mess below.
>

*You didn't actually duplicate the code I showed*.

In my post, the opening  occurs *after the text of the bullet item*, 
and there are *two newlines immediately following the opening *, so 
that the enclosed content is rendered in block mode.  You also didn't *end 
with a closing *, but rather used *another opening *, so your 
HTML is improperly formed, which is why "*the third bullet point is treated 
as a second level bullet to the 2nd bullet*", rather than starting a 3rd 
bullet as intended.

I'm not adverse at all if someone wishes to correct me
>
Thoughts? Corrections? I'm open to constructive criticism. 
>

Try using *the exact method I posted*, and see if that doesn't work as 
advertised.

Hope this helps,
-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/43072b28-18d2-4e4d-9b8f-84fb479780b6n%40googlegroups.com.

[tw5] Re: [tw] Re: Continue order list numbering after code block?

[Charlie Veniot]

Hi,

The first  is fine, but the second  should be a 

On Monday, August 16, 2021 at 12:03:18 AM UTC-3 dgle...@gmail.com wrote:

> @Eric Shulman
> I appreciate your attempt to to show me a fix, I do. But as demonstrated 
> below, it doesn't work. It created an oddity of issues (I am using 5.1.23 
> and CamelCase is off.)
> My original tiddler is at the bottom showing the formatting that I used 
> that did work.
>
> Duplicating the code you've shown results in the mess below. All the lines 
> on the second bullet run together and the third bullet point is treated as 
> a second level bullet to the 2nd bullet.
> [image: tiddly1.jpg]
>
> I fixed the issue with the paragraphs running together but it doesn't 
> resolve the issue with the 3rd bullet being shown as a secondary level as 
> previously described.
> [image: tiddly2.jpg]
>  
> My attempt to correct the third bullet problem remains unresolved. 
> [image: tiddly3.jpg]
>
> This is a snapshot of the original tiddler I was working on and what ended 
> up working for me. On another note, none of the @@ codes worked either even 
> when directly copied from the example. So I ended up using the built in 
> 'highlighting' instead. Inline CSS didn't work when used with the , 
>  or  tags and I'd spent enough time as it was to get it looking as 
> I wanted. 
> [image: originalTiddler.jpg]
> And another with line numbering and a code block.
> [image: tiddlerNumberingList.jpg]
>
> I'm not adverse at all if someone wishes to correct me and provide a 
> working example on their end, and if it doesn't work on my end,  I'll turn 
> to disabling any plugins installed after the TW5 file was installed and 
> take a look at what plugin I had to disable for it to work as they've shown 
> me. I don't have many. I try to load only those I need on my collection of 
> TW5 files for other purposes.
>
> Thoughts? Corrections? I'm open to constructive criticism. 
>
> On Friday, August 13, 2021 at 8:22:36 PM UTC-4 Eric Shulman wrote:
>
>> On Friday, August 13, 2021 at 3:17:28 PM UTC-7 dgle...@gmail.com wrote:
>>
>>> Although this is an old thread,
>>
>>
>> As you note, this is an old thread (over 6 years old!).
>>
>> *A general solution has long ago been documented* here:
>> https://tiddlywiki.com/#Lists%20in%20WikiText 
>> Scroll down to the end of the tiddler and you will see a heading
>> labeled "Paragraphs in Lists", which describes enclosing the
>> desired content within a ..., like this:
>>
>> # Step 1
>> # Step 2
>> # Step 3
>>
>> Here is the first of several paragraphs. Note that the double linebreak 
>> preceding this paragraph is significant.
>>
>> And here is the second of several paragraphs.
>> 
>> # Step 4
>> # Step 5
>> # Step 6
>>
>> Note that this technique will work with ANY pair of matching HTML tags.  
>> *You 
>> can even use made up tags, like ...*.  The key points are 
>> these:
>>
>>- *the opening tag is placed at the end of the first line that starts 
>>the the bullet item*
>>- *there is a double linebreak following that opening tag.*
>>
>> enjoy,
>> -e
>>
>

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

[tw5] Re: Just a goofy thought: a way to get javascript into a Tiddler

[Charlie Veniot]

Better to keep the HTML readable, drag the attached json with two tiddlers 
into some TiddlyWiki:

On Sunday, August 15, 2021 at 11:27:41 PM UTC-3 Charlie Veniot wrote:

> I don't know what made me think of this.
>
> In case this has not been brought up in a while (I doubt this is new to 
> seasoned folk) ...
>
> I was thinking: could I use an iFrame to include simple javascript in a 
> tiddler without getting into macros or plugins that enable javascript.
>
> And, if I could, then could I set things up so that the iFrame is showing 
> javascript dynamically created by the tiddler ?
>
> So here is a way to show a digital clock in TiddlyWiki, for 
> non-programmers who just want to copy and paste javascript code from the 
> web without figuring out how the javascript code works :
>
> Put this in a brand new tiddler:
>
> *<$vars* *vSrcDoc*={{{ [[
> let clockEl = document.getElementById("clockDiv");function 
> getClockTime() {  let date = new Date();  let hr = 
> date.getHours();  let min = date.getMinutes();  let sec = 
> date.getSeconds();  hr = ("0" + hr).slice(-2);  min = ("0" + 
> min).slice(-2);  sec = ("0" + sec).slice(-2);  clockEl.innerHTML = 
> `${hr}:${min}:${sec}`;}setInterval(getClockTime, 1000);  
> ]] }}}*>*
> *>* style="border:none;width:100%;"*>*
> **
>
> Sneaky sneaky, has me wondering what kind of other fun things could be 
> done...
>

-- 
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/3774ebc2-cb7f-4463-8e08-271af889fdf4n%40googlegroups.com.


TwClock.json
Description: application/json

[tw5] Re: Just a goofy thought: a way to get javascript into a Tiddler

[Charlie Veniot]

Better to keep the HTML readable, drag this package of two tiddlers into 
some TiddlyWiki:


On Sunday, August 15, 2021 at 11:27:41 PM UTC-3 Charlie Veniot wrote:

> I don't know what made me think of this.
>
> In case this has not been brought up in a while (I doubt this is new to 
> seasoned folk) ...
>
> I was thinking: could I use an iFrame to include simple javascript in a 
> tiddler without getting into macros or plugins that enable javascript.
>
> And, if I could, then could I set things up so that the iFrame is showing 
> javascript dynamically created by the tiddler ?
>
> So here is a way to show a digital clock in TiddlyWiki, for 
> non-programmers who just want to copy and paste javascript code from the 
> web without figuring out how the javascript code works :
>
> Put this in a brand new tiddler:
>
> *<$vars* *vSrcDoc*={{{ [[
> let clockEl = document.getElementById("clockDiv");function 
> getClockTime() {  let date = new Date();  let hr = 
> date.getHours();  let min = date.getMinutes();  let sec = 
> date.getSeconds();  hr = ("0" + hr).slice(-2);  min = ("0" + 
> min).slice(-2);  sec = ("0" + sec).slice(-2);  clockEl.innerHTML = 
> `${hr}:${min}:${sec}`;}setInterval(getClockTime, 1000);  
> ]] }}}*>*
> *>* style="border:none;width:100%;"*>*
> **
>
> Sneaky sneaky, has me wondering what kind of other fun things could be 
> done...
>

-- 
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/065f1c41-7c35-4b56-ad5f-17071a8ef873n%40googlegroups.com.

[tw5] Just a goofy thought: a way to get javascript into a Tiddler

[Charlie Veniot]

I don't know what made me think of this.

In case this has not been brought up in a while (I doubt this is new to 
seasoned folk) ...

I was thinking: could I use an iFrame to include simple javascript in a 
tiddler without getting into macros or plugins that enable javascript.

And, if I could, then could I set things up so that the iFrame is showing 
javascript dynamically created by the tiddler ?

So here is a way to show a digital clock in TiddlyWiki, for non-programmers 
who just want to copy and paste javascript code from the web without 
figuring out how the javascript code works :

Put this in a brand new tiddler:

*<$vars* *vSrcDoc*={{{ [[let 
clockEl = document.getElementById("clockDiv");function getClockTime() 
{  let date = new Date();  let hr = date.getHours();  let min = 
date.getMinutes();  let sec = date.getSeconds();  hr = ("0" + 
hr).slice(-2);  min = ("0" + min).slice(-2);  sec = ("0" + 
sec).slice(-2);  clockEl.innerHTML = `${hr}:${min}:${sec}`;}
setInterval(getClockTime, 1000);  ]] }}}*>*
*>* style="border:none;width:100%;"*>*
**

Sneaky sneaky, has me wondering what kind of other fun things could be 
done...

-- 
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/cb08b664-8cc9-4531-bd25-783463ebbef4n%40googlegroups.com.

[tw5] Re: Highlighting duplicates in lists

[paulgilbert2000]

Thank you tones

The real life example is to evaluate duplicate dates, so the actual real 
values populating the fields are not  1 ,2 , etc.. they are actual dates , 
IE . 2021062506295,   20210811055859000,etc.
and so what i was trying is to  do is have the highlighted duplicate values 
converted from the tiddly wiki format they are stored in in their 
respective fields , to a normal readable format when displayed in the filter

the
On Monday, August 16, 2021 at 2:34:07 AM UTC+2 TW Tones wrote:

> Mohammad,
>
> I am confused, until now the fields  field_example,  field_example1,  
> field_example2 did not contain dates. 
>
>- Are you trying to convert these to dates?
>- the view widget format=date only works on tiddlywiki full serial 
>number dates!
>
> Perhaps step back and describe what you want to do in the real world, not 
> with tiddlywiki code that may or may not be correct. 
>
> Regards
> Tones
>
> On Monday, 16 August 2021 at 01:46:55 UTC+10 mohamed...@hotmail.com wrote:
>
>> HI tones,
>>
>> sorry i guess i asked the wrong question, what i wanted to know is where 
>> to place the widget  in the code , if i do it that way , it no longer 
>> highlights duplicates
>>
>>  <>: |  
>><$list filter="[all[current]get[field_example]] 
>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>> variable=field-value>
>> <$view field="field_example "format=date template=""/>
>> <$view field="field_example1"format=date template=""/>
>> <$view field="field_example2"format=date template=""/>
>>
>>  matchthen[color: 
>> red;]] }}}><>
>>
>> 
>>
>> i also tried  adding format:date[DDD]] , which didn't yield any results 
>>
>><$list filter="[all[current]get[field_example]] 
>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>> format:date[DDD]] variable=field-value> 
>> On Sunday, August 15, 2021 at 10:12:57 AM UTC+2 TW Tones wrote:
>>
>>> Look for and use the viewWidget and use the format date with a template, 
>>> or the format relativedate
>>>
>>> Get into the habit also of searching in tiddlywiki.com to learn how to 
>>> do things.
>>> [image: Snag_c8a06a9.png]
>>>
>>> eg;
>>>
>>> <$view field=created format=date template=""/>
>>>
>>> <$view field=created format=relativedate/>
>>>
>>>  5.1.23 now allows this inside filters. 
>>> 
>>>
>>> Regards
>>> Tones
>>>
>>> On Sunday, 15 August 2021 at 10:26:32 UTC+10 mohamed...@hotmail.com 
>>> wrote:
>>>
 Sorry one more questions

 if the values are dates, how can they be displayed in normal format 
 ,and not the tiddly wiki format

 On Monday, August 9, 2021 at 1:10:18 AM UTC+2 paulgilbert2000 wrote:

> Thank you tones
>
> Will take me a while to understand all that . but it works like a 
> charm , and its even more than what i have asked for
>
> thanks again:)
>
> On Sunday, August 8, 2021 at 7:31:10 AM UTC+2 TW Tones wrote:
>
>> Mohamad,
>>
>> I am happy to look at solving the problem presented but my suspicion 
>> remains that there may be a different way to put the question in the 
>> first 
>> place. 
>>
>> Sometimes a question can be rephrased such that the answer is simpler 
>> to find.
>>
>>- In this we have multiple tiddlers, with multiple fields, with 
>>*values* that may be duplicated across these tiddlers/fields.
>>- in effect you want to list all tiddlers using the select 
>>fields, list these for each tiddler then for each found value
>>   -  detect when that value occurs in any other tiddler (not 
>>   self?) or select fields, if it does highlight it.
>>- I am not sure why you want to do this and can think of many 
>>ways to list/interpret the data! 
>>- What about triplicates?
>>- What about duplicates in the same tiddler?
>>
>> I think using your test data this is what you wanted?
>>
>> 
>> <$list filter="[all[]has[field_example]]">
>><$set name=other-values 
>> filter="[all[]!get[field_example]] 
>> [all[]!titleget[field_example2]] 
>> [all[]!titleget[field_example3]] +[sort[]]">
>><>: |  
>><$list filter="[all[current]get[field_example]] 
>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>> variable=field-value>
>> > [enlistmatchthen[color: red;]] 
>> }}}><>
>> 
>>
>> 
>> 
>>
>> It will also highlight triplicates...
>>
>> A slightly more efficient method is available that could actually 
>> could the number of repeats and color red if > 1
>>
>> <$set name=all-values filter="=[all[]get[field_example]] 
>> =[all[]get[field_example2]] =[all[]get[field_example3]]">
>> "<>" {{{ [split[ ]count[]] }}}
>> 
>> <$list filter="[all[]has[field_example]]">
>><>: |  

Re: [tw5] Re: Presenting Text-to-Speech v1.0.0: the flip-side of Speech-to-Text!

[Finn Lancaster]

Good to know, @TW Tones, I'll change the hotkey to Alt+Shift+L when I can
(Alt+Shift+R is taken by speech-to-text already, so I had to choose
something different.)

On Sun, Aug 15, 2021 at 8:44 PM TW Tones  wrote:

> Flanc,
>
> Exciting and thanks for this. I am getting my firefox menus with
> Alt+Shift+E
>
> In chrome I heard it momentarily only. I will experiment further.
>
> Regards
> Tones
>
> On Monday, 16 August 2021 at 00:00:45 UTC+10 flanc...@gmail.com wrote:
>
>> After seeing some recommendations for a text-to-speech plugin in TW5
>> while releasing the Speech-to-Text plugin v1.0.5 with BTC, I took it upon
>> myself to make my first solo plugin: text-to-speech!
>>
>> *How does it work?*
>> Text-to-Speech uses the web text-to-speech API, which functions like a
>> screen reader. To apply this to TiddlyWiki, I made a custom function
>> calling this API, which then takes as arguments a selected area of text
>> using cutom code I wrote!
>>
>> *Get Started!*
>> To get started with the plugin, you can install by drag-and-drop from
>> text-to-speech.finnsoftware.net! Then, anywhere in your TiddlyWiki, you
>> can highlight text, and press the hotkey Alt+Shift+E, and listen to the
>> plugin read the text to you!
>>
>> *What to Expect in the Future?*
>>
>>- test for foreign language support
>>- test support across browsers
>>- button in toolbar/editing
>>
>> --
> 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/ad0f829f-fe4b-4b39-814d-6756ba6e1b99n%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/CALXL%2BrNXM%2BpDeRCcN-t%2BBXYy-QYQZhxxwNgsHEJautD3ZNmJ7g%40mail.gmail.com.

[tw5] Re: convert date in a text field to date format

[Eric Shulman]

On Sunday, August 15, 2021 at 4:47:47 PM UTC-7 Mark S. wrote:

> Just tried 
> <>
> and got a hard RSOE ("from" not defined). I think the arguments need to be 
> tweaked in the macro.
>

OOPS!  I had originally used "date" and "format" as the parameter names, 
but then I decided to change to using "from" and "to".  Unfortunately, the 
arguments in the macro function declaration were still using "date" and 
"format", but internally, the macro code referenced "from" and "to" as 
intended.  I've corrected the arguments in the macro function declaration 
and posted an update here:

https://tiddlytools.com/timer.html#TiddlyTools%2FTime%2FConvertDate

Thanks,
-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/56b0ae37-8392-445a-b679-092e172dccc8n%40googlegroups.com.

[tw5] Re: convert date in a text field to date format

['Mark S.' via TiddlyWiki]

On Sunday, August 15, 2021 at 5:08:35 PM UTC-7 TW Tones wrote:

> Format  T.  ?
>
> Surely you mean "0DD. MMM "
>
>
That's a good point. I imagine S2's source application is using some local 
formatting code (e.g. German, Dutch). So the format would have to be 
altered to the ISO 8601 standard for use in javascript (and probably all of 
TW) when specifying input. But, presumably the output would automatically 
conform to the browser's locale string ??



 

-- 
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/7e298246-990b-4bc9-a9e2-4c891fb71431n%40googlegroups.com.

[tw5] Re: Presenting Text-to-Speech v1.0.0: the flip-side of Speech-to-Text!

[TW Tones]

Flanc,

Exciting and thanks for this. I am getting my firefox menus with  
Alt+Shift+E

In chrome I heard it momentarily only. I will experiment further.

Regards
Tones

On Monday, 16 August 2021 at 00:00:45 UTC+10 flanc...@gmail.com wrote:

> After seeing some recommendations for a text-to-speech plugin in TW5 while 
> releasing the Speech-to-Text plugin v1.0.5 with BTC, I took it upon myself 
> to make my first solo plugin: text-to-speech!
>
> *How does it work?*
> Text-to-Speech uses the web text-to-speech API, which functions like a 
> screen reader. To apply this to TiddlyWiki, I made a custom function 
> calling this API, which then takes as arguments a selected area of text 
> using cutom code I wrote!
>
> *Get Started!*
> To get started with the plugin, you can install by drag-and-drop from 
> text-to-speech.finnsoftware.net! Then, anywhere in your TiddlyWiki, you 
> can highlight text, and press the hotkey Alt+Shift+E, and listen to the 
> plugin read the text to you!
>
> *What to Expect in the Future?*
>
>- test for foreign language support
>- test support across browsers
>- button in toolbar/editing
>
>

-- 
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/ad0f829f-fe4b-4b39-814d-6756ba6e1b99n%40googlegroups.com.

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[Joshua Fontany]

We've found a bug!

The wikitext parser object always tries to read Pragmas from the beginning 
to parse a text, and this _always_ trims whitespace from the text (moves 
the parser position past any leading whitespace).

The $:/core/modules/parsers/wikiparser/wikiparser.js module needs to 
updated.

The Parser's `this.skipWhiteSpace =` method needs to check the 
`this.configTrimWhiteSpace` value before moving the parser position, or 
reset the parser position if no pragmas are read, etc.

This type of change should definitely have Jeremy's eye on it.

I am terribly busy at work, so I will come back and file a Bug/Issue on 
GitHub if no-one else can.

Best,
Joshua Fontany

On Sunday, August 15, 2021 at 10:34:41 AM UTC-7 Misterel85 wrote:

> Yay, it works!!! Thank you very much for your quick reply and your simple 
> and straightforward solution, Eric!
> After a bit of trial and error, I could adapt it to my TiddlyWiki.
> No need for an  anymore indeed.
> Thanks again to all of you for your help, solutions, explanations and 
> suggestions.
>
> Best,
> -Stéphane
>
> Le dimanche 15 août 2021 à 18:01:55 UTC+2, Eric Shulman a écrit :
>
>> On Sunday, August 15, 2021 at 7:10:39 AM UTC-7 Misterel85 wrote:
>>
>>> I first thought there would have been a more straightforward solution to 
>>> that issue, but actually I come to think that it should be possible to 
>>> inspect the first character in the contents of field 2:
>>> If value of field2 starts with space, then insert `` between the 
>>> transclusions, else just proceed with both transclusions.
>>>
>>
>> Try this:
>> <$transclude field="field1"/><$text text={{{ 
>> [{!!field2}split[]first[]match[ ]] }}}/><$transclude field="field2"/>
>>
>> Notes:
>> * The {{{ [...] }}} is a "filtered transclusion"
>> * The filter starts by getting the value of the desired field, using 
>> {!!field2}
>> * It then splits that value into separate characters, using split[]
>> * Next, it gets just the first character, using first[]
>> * and compares it with a space, using match[ ]
>> * The result of the filter is either nothing, or an actual space 
>> character (not an )
>> * The <$text> widget then converts the output to plain text (instead of 
>> displaying a link to a space!)
>>
>> enjoy,
>> -e
>>
>

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

[tw5] Re: Highlighting duplicates in lists

[TW Tones]

Mohammad,

I am confused, until now the fields  field_example,  field_example1,  
field_example2 did not contain dates. 

   - Are you trying to convert these to dates?
   - the view widget format=date only works on tiddlywiki full serial 
   number dates!

Perhaps step back and describe what you want to do in the real world, not 
with tiddlywiki code that may or may not be correct. 

Regards
Tones

On Monday, 16 August 2021 at 01:46:55 UTC+10 mohamed...@hotmail.com wrote:

> HI tones,
>
> sorry i guess i asked the wrong question, what i wanted to know is where 
> to place the widget  in the code , if i do it that way , it no longer 
> highlights duplicates
>
>  <>: |  
><$list filter="[all[current]get[field_example]] 
> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
> variable=field-value>
> <$view field="field_example "format=date template=""/>
> <$view field="field_example1"format=date template=""/>
> <$view field="field_example2"format=date template=""/>
>
>  matchthen[color: red;]] 
> }}}><>
>
> 
>
> i also tried  adding format:date[DDD]] , which didn't yield any results 
>
><$list filter="[all[current]get[field_example]] 
> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
> format:date[DDD]] variable=field-value> 
> On Sunday, August 15, 2021 at 10:12:57 AM UTC+2 TW Tones wrote:
>
>> Look for and use the viewWidget and use the format date with a template, 
>> or the format relativedate
>>
>> Get into the habit also of searching in tiddlywiki.com to learn how to 
>> do things.
>> [image: Snag_c8a06a9.png]
>>
>> eg;
>>
>> <$view field=created format=date template=""/>
>>
>> <$view field=created format=relativedate/>
>>
>>  5.1.23 now allows this inside filters. 
>> 
>>
>> Regards
>> Tones
>>
>> On Sunday, 15 August 2021 at 10:26:32 UTC+10 mohamed...@hotmail.com 
>> wrote:
>>
>>> Sorry one more questions
>>>
>>> if the values are dates, how can they be displayed in normal format ,and 
>>> not the tiddly wiki format
>>>
>>> On Monday, August 9, 2021 at 1:10:18 AM UTC+2 paulgilbert2000 wrote:
>>>
 Thank you tones

 Will take me a while to understand all that . but it works like a charm 
 , and its even more than what i have asked for

 thanks again:)

 On Sunday, August 8, 2021 at 7:31:10 AM UTC+2 TW Tones wrote:

> Mohamad,
>
> I am happy to look at solving the problem presented but my suspicion 
> remains that there may be a different way to put the question in the 
> first 
> place. 
>
> Sometimes a question can be rephrased such that the answer is simpler 
> to find.
>
>- In this we have multiple tiddlers, with multiple fields, with 
>*values* that may be duplicated across these tiddlers/fields.
>- in effect you want to list all tiddlers using the select fields, 
>list these for each tiddler then for each found value
>   -  detect when that value occurs in any other tiddler (not 
>   self?) or select fields, if it does highlight it.
>- I am not sure why you want to do this and can think of many ways 
>to list/interpret the data! 
>- What about triplicates?
>- What about duplicates in the same tiddler?
>
> I think using your test data this is what you wanted?
>
> 
> <$list filter="[all[]has[field_example]]">
><$set name=other-values 
> filter="[all[]!get[field_example]] 
> [all[]!titleget[field_example2]] 
> [all[]!titleget[field_example3]] +[sort[]]">
><>: |  
><$list filter="[all[current]get[field_example]] 
> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
> variable=field-value>
>  [enlistmatchthen[color: red;]] 
> }}}><>
> 
>
> 
> 
>
> It will also highlight triplicates...
>
> A slightly more efficient method is available that could actually 
> could the number of repeats and color red if > 1
>
> <$set name=all-values filter="=[all[]get[field_example]] 
> =[all[]get[field_example2]] =[all[]get[field_example3]]">
> "<>" {{{ [split[ ]count[]] }}}
> 
> <$list filter="[all[]has[field_example]]">
><>: |  
><$list filter="[all[current]get[field_example]] 
> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
> variable=field-value>
> <$set name=value-count filter="[split[ 
> ]matchcount[]]">
> compare:number:gt[1]then[color: 
> Red;]] }}} ><> (<>)
>  
> 
> 
> 
> 
>
> Of course in the above you can choose not to show the count of the 
> same value delete  "(<>)"
>
> Regards
> Tones
>
> On Sunday, 8 August 2021 at 02:05:57 UTC+10 mohamed...@hotmail.com 
> wrote:
>
>> Hi Tones,
>>
>> sorry for the 

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[TW Tones]

Misterel,

I believe I understand what you are trying todo. Yet I would persist in 
suggesting you separate the data from its presentation. 

Of course its is fine to use the pragmatic approach as you wish.

What I would do is build the concatenation process to always include a 
space between elements, no leading or trailing spaces needed, except when 
it starts with period or any other exceptions you identify.

Basically I would get the logic to handle the language concatenation and 
leave such fiddling, outside of the data. Ideally I would even leave 
leading commas out of the data as this is again all about presentation eg 
if I have a list of three items the first is separated from the second by a 
comma the third by "and". and the full stop comes at the very end. ie just 
store the items because you need not know how you will use them in the 
future and when using them format according to the presentation. The recent 
and next version 5.2.0 contains some support for this first, seconds and 
last treatment such as with the counter variable, even css can handle this.

Experience has shown me such an approach is actually much simpler in the 
short term and few exceptions are required, where the approach you are 
taking will ultimately be the opposite, more complex and have more 
exceptions, while also loosing flexibility.

But yes you are an autonomous being :) do what you want.

Tones
On Monday, 16 August 2021 at 03:34:41 UTC+10 Misterel85 wrote:

> Yay, it works!!! Thank you very much for your quick reply and your simple 
> and straightforward solution, Eric!
> After a bit of trial and error, I could adapt it to my TiddlyWiki.
> No need for an  anymore indeed.
> Thanks again to all of you for your help, solutions, explanations and 
> suggestions.
>
> Best,
> -Stéphane
>
> Le dimanche 15 août 2021 à 18:01:55 UTC+2, Eric Shulman a écrit :
>
>> On Sunday, August 15, 2021 at 7:10:39 AM UTC-7 Misterel85 wrote:
>>
>>> I first thought there would have been a more straightforward solution to 
>>> that issue, but actually I come to think that it should be possible to 
>>> inspect the first character in the contents of field 2:
>>> If value of field2 starts with space, then insert `` between the 
>>> transclusions, else just proceed with both transclusions.
>>>
>>
>> Try this:
>> <$transclude field="field1"/><$text text={{{ 
>> [{!!field2}split[]first[]match[ ]] }}}/><$transclude field="field2"/>
>>
>> Notes:
>> * The {{{ [...] }}} is a "filtered transclusion"
>> * The filter starts by getting the value of the desired field, using 
>> {!!field2}
>> * It then splits that value into separate characters, using split[]
>> * Next, it gets just the first character, using first[]
>> * and compares it with a space, using match[ ]
>> * The result of the filter is either nothing, or an actual space 
>> character (not an )
>> * The <$text> widget then converts the output to plain text (instead of 
>> displaying a link to a space!)
>>
>> enjoy,
>> -e
>>
>

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

[tw5] Re: convert date in a text field to date format

[TW Tones]

Format  T.  ?

Surely you mean "0DD. MMM "

In this case you would parse this date to extract the DD, MMM and  as 
separate values, convert from MMM to a month number with a 12 month table, 
then re-assemble them into a tiddlywiki date/time string. I suggest 1200 or 
12 noon as the time, otherwise zero fill seconds and milliseconds.

eg D all before ".", 
Month split[ ]nth[2]
Year split[ ]nth[3] or last[]

Regrds
Tones
On Monday, 16 August 2021 at 09:47:47 UTC+10 Mark S. wrote:

> @ Eric
>
> Just tried 
>
> <>
>
> and got a hard RSOE ("from" not defined). I think the arguments need to be 
> tweaked in the macro.
>
> HTH
> On Friday, August 13, 2021 at 2:53:09 PM UTC-7 Eric Shulman wrote:
>
>> On Friday, August 13, 2021 at 12:36:11 AM UTC-7 S² wrote:
>>
>>> I use a created text field 'published', which will be filled with a date.
>>> (This date can also be in the future)
>>> format is *T.  * - (eg. *7. April 2021* or *13. August 2021*).
>>>
>>> 1. How can this be converted into a date format?
>>>
>>
>> I have just added a new javascript macro to the TiddlyTools timer package.
>>
>> https://tiddlytools.com/timer.html#TiddlyTools%2FTime%2FConvertDate
>>
>>- To convert a date to a different format, use <>from:inputdate to:outputformat>>.
>>- The input date can use any date format recognized by the Javascript 
>>Date.parse() function. Generally this conforms to *ISO 8601 standard 
>>date format*. 
>>- The output format uses TiddlyWiki Date Format codes 
>>, and defaults to 
>>*[UTC]0MM0DD0hh0mm0ss0XXX*.
>>
>> enjoy,
>> -e
>>
>

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

[tw5] Re: Help please for indicators in SideBar

[TW Tones]

Folks,

I said I would share the result back, and it is attached so far. 

It is largely working very nicely, later I will package a range of 
indicators with it as I develop them.

However it still has a problem.

   - The attached JSON has a few tiddlers, which displays indicators 
   (icons/buttons tagged $:/tags/indicator) just above the sideBar tabs
   - It currently only comes with one indicator, an info icon with a 
   tooltip about itself.

Unfortunately there is an artifact, no doubt a clash with the CSS I am 
using.
eg class="tc-btn-invisible" on the button.

Regards
Tones
On Saturday, 14 August 2021 at 18:39:08 UTC+10 TW Tones wrote:

> Télumire,
>
> Hey thanks soo much, that is exactly what I needed.
>
> I have adopted the final css as follows to get smaller icons that the 
> PageControls.
>
> .indicator-container { display:block; margin-top: -15px; margin-bottom: 
> -22px; line-height:unset; } .indicator-item{ height:15px; width:15px; 
> display:inline-block; position:relative; } .indicator-item button, 
> .indicator-item button * { width:100%!important; height:100%!important; 
> padding:unset; margin:unset; display:inline-block; left:0; top:0; }
>
> I will shareback my indicators "bar" macro shortly
>
> Regards
> Tones
>
> On Friday, 13 August 2021 at 04:16:44 UTC+10 Télumire wrote:
>
>> Erratum bis (sorry..) :
>>
>> .indicator-container {
>> display: flex;
>> flex-wrap:wrap;
>> margin-top: -14px;
>> margin-bottom: -26px;
>> --indicator-size:10px;
>> }
>>
>> .indicator-item{
>> height:var(--indicator-size);
>> width:var(--indicator-size);
>> display:inline-block;
>> position:relative;
>> }
>>
>> .indicator-item button, .indicator-item button * {
>> position:absolute;
>> width:100%!important;
>> height:100%!important;
>> padding:unset;
>> margin:unset;
>> left:0;
>> top:0;
>> }
>>
>> Should I send further replies by private message to avoid spam ?
>>
>>
>> Le jeudi 12 août 2021 à 20:02:22 UTC+2, Télumire a écrit :
>>
>>> Erratum : no need for the line-height:unset nor the inline-block for the 
>>> button and its content :
>>
>>
>>>
>>> .indicator-container {
>>> display:block;
>>> margin-top: -14px;
>>> margin-bottom: -26px;
>>> }
>>>
>>> .indicator-item{
>>> height:40px;
>>> width:40px;
>>> display:inline-block;
>>> position:relative;
>>> }
>>>
>>> .indicator-item button, .indicator-item button * {
>>> width:100%!important;
>>> height:100%!important;
>>> padding:unset;
>>> margin:unset;
>>>
>> left:0;
>>> top:0;
>>> }
>>>
>>> Le jeudi 12 août 2021 à 20:00:09 UTC+2, Télumire a écrit :
>>>
 Ok now I understand what you mean … This is because tiddly wiki wrap 
 the content in a  tag, which has a margin of 14px. So to fix that, 
 since 
 we can't style an element based on it's content (at least not until the 
 pseudo-class :has is supported) nor give it a class (as far as I know), we 
 need to wrap the indicators in a container and use it to compensate with 
 negative margin.

 The code becomes :

 \whitespace trim
 
 
 {{$:/core/ui/Buttons/edit}}
  
 ..etc..
 
 {{$:/core/ui/Buttons/cancel}}
 
  

 And the css becomes 

 .indicator-container {
 display:block;
 margin-top: -14px;
 margin-bottom: -26px;
 line-height:unset;
 }

 .indicator-item{
 height:40px;
 width:40px;
 display:inline-block;
 position:relative;
 }

 .indicator-item button, .indicator-item button * {
 width:100%!important;
 height:100%!important;
 padding:unset;
 margin:unset;
 display:inline-block;
 left:0;
 top:0;
 }
 Le jeudi 12 août 2021 à 08:22:19 UTC+2, TW Tones a écrit :

> Télumire
>
> I just tried this on tiddlywiki.com;
>
> Thanks, we are almost there.
>
> I set the width and height to 15px, look like I wanted then added 
> list-before = $:/core/ui/SideBarSegments/tabs
>
> Once it moves above the tabs there is too much white space above and 
> below
>
> [image: Snag_1f281978.png]
>
> Is there some way to remove or reduce this space top and bottom?
>
> Regards
> Tones
>
>
> On Thursday, 12 August 2021 at 12:07:40 UTC+10 Télumire wrote:
>
>> So if I understand correctly, you want to be able to give a custom 
>> size to your icons/buttons and be able to have them next to each other ?
>>
>> Try this and tell me if that works :
>>
>> In the tiddler tagged with $:/tags/SideBarSegment : 
>>
>> \whitespace trim
>> 
>> {{button 1}}
>> 
>> ..etc..
>> 
>> {{button n}} 
>>  
>>
>> In a stylesheet tiddler :
>>
>> .indicator{
>> height:20px;
>> width:20px;
>> display:inline-block;
>> position:relative;
>> }
>>
>> .indicator button, .indicator button * {
>> width:100%!important;
>> height:100%!important;
>> padding:unset;
>> margin:unset;

[tw5] Re: convert date in a text field to date format

['Mark S.' via TiddlyWiki]

@ Eric

Just tried 

<>

and got a hard RSOE ("from" not defined). I think the arguments need to be 
tweaked in the macro.

HTH
On Friday, August 13, 2021 at 2:53:09 PM UTC-7 Eric Shulman wrote:

> On Friday, August 13, 2021 at 12:36:11 AM UTC-7 S² wrote:
>
>> I use a created text field 'published', which will be filled with a date.
>> (This date can also be in the future)
>> format is *T.  * - (eg. *7. April 2021* or *13. August 2021*).
>>
>> 1. How can this be converted into a date format?
>>
>
> I have just added a new javascript macro to the TiddlyTools timer package.
>
> https://tiddlytools.com/timer.html#TiddlyTools%2FTime%2FConvertDate
>
>- To convert a date to a different format, use >.
>- The input date can use any date format recognized by the Javascript 
>Date.parse() function. Generally this conforms to *ISO 8601 standard 
>date format*. 
>- The output format uses TiddlyWiki Date Format codes 
>, and defaults to 
>*[UTC]0MM0DD0hh0mm0ss0XXX*.
>
> enjoy,
> -e
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/37a7b1cb-bb21-4878-90e2-392a2f34521bn%40googlegroups.com.

[tw5] Re: convert date in a text field to date format

['Mark S.' via TiddlyWiki]

Is your source text field in T.  format?

Are you converting it back to TW format?

Where are you storing the converted value?



On Friday, August 13, 2021 at 12:36:11 AM UTC-7 S² wrote:

> Hello forum,
>
> I use a created text field 'published', which will be filled with a date.
> (This date can also be in the future)
> format is *T.  * - (eg. *7. April 2021* or *13. August 2021*).
>
> 1. How can this be converted into a date format?
>
> 2. The 'published' field is also shown in TOC - $:/_macros/alternative/toc 
> -  (see 
> https://groups.google.com/g/tiddlywiki/c/AAPGy6pFpnc/m/hlKHyhzsAwAJ).
> I would like to have TOC sorted on this field (recent on top) 
>
> Thanks for feedback
> Stefan
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/734b3a58-8a29-4a9f-8182-3e96dba95d03n%40googlegroups.com.

Re: [tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[PMario]

On Sunday, August 15, 2021 at 10:13:33 PM UTC+2 cmari wrote:

> Hello all,  
> Thanks!! Thanks to Mario for a way to wrap the macro that works perfectly. 
>

It was Jeremy's comment, that made me play with the possibilities. ... 

One further question that would help my understanding of things: is the 
> wrapping enough to restore this macro to acceptability?


IMO it should do the trick. .. It basically adds the refresh mechanism that 
should "inside" the macro code, onto the outside. ... The $vars widget (as 
every other widget) implements a "watchdog" that "listens" to changes that 
happen to parameters that are passed to the widget. 

In case of the workaround <$vars x={{!!toggled}} y={{!!barray}}> it's the 
{{!!field-names}} that are important. The variable names don't matter, 
since we don't really need them. Whenever the fields change, the vars 
widget will redraw itself and it's childs. Since the <> and 
<> macro are part of the widget body they get refreshed, in the 
exact same way as the <$transclude macro did it in the past. 
 

> Or is there really some deeper fundamental problem being described by 
> "broken", "off-spec", and "improper" that means I should think of the 
> wrapping as only a temporary bandage? 
> cmari
>

I think this workaround is perfectly valid. ... It still should be fixed on 
the js-code level. ... BUT upgrading to v5.2.0 isn't "killing" the old 
functionality anymore. So we have more time to really fix the problem, 
where it should be fixed. 

-mario

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

Re: [tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[cmari]

Hello all,  
Thanks!! Thanks to Mario for a way to wrap the macro that works perfectly. 
Thanks to Jeremy and Saq for all of the explanations - for me those always 
make it easier to adapt to change. Thanks to Saq for persisting with a 
search for alternatives in the face of my insistence on wanting what I 
want. And thanks to Josiah for highlighting the amazing longevity of TW 
tools.  

One further question that would help my understanding of things: is the 
wrapping enough to restore this macro to acceptability? Or is there really 
some deeper fundamental problem being described by "broken", "off-spec", 
and "improper" that means I should think of the wrapping as only a 
temporary bandage? 
cmari


On Sunday, August 15, 2021 at 9:55:55 AM UTC-7 PMario wrote:

> Did more tests ... It seems to be 
>
> <$vars x={{!!toggled}} y={{!!barray}}>
> <>
> 
>
> -m
>
> On Sunday, August 15, 2021 at 6:41:56 PM UTC+2 PMario wrote:
>
>> On Sunday, August 15, 2021 at 1:20:54 PM UTC+2 Jeremy Ruston wrote:
>>
>> * It should usually be easy to fix: wrap the macro invocation in a 
>>> <$tiddler> widget referencing the tiddler in question
>>
>>
>> I did test that, but it seems the tiddler-widget only views the 
>> tiddler-attribute for a change and a simple state, that only calculates the 
>> classes. ... 
>> So if any tiddler-field changes, it doesn't do a refreshSelf() and may be 
>> it shouldn't. It needs to refreshSelf() if the parameter itself is changed, 
>> and not if the tiddler, where the parameter points to is changed. ... 
>>
>> But this seems to work: 
>>
>> <$set name=x value={{!!toggled}}>
>> <>
>> 
>>
>> and
>>
>> <$set name=x value={{!!toggled}}>
>> <>
>> 
>>
>>
>> -mario
>>
>>

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

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[Misterel85]

Yay, it works!!! Thank you very much for your quick reply and your simple 
and straightforward solution, Eric!
After a bit of trial and error, I could adapt it to my TiddlyWiki.
No need for an  anymore indeed.
Thanks again to all of you for your help, solutions, explanations and 
suggestions.

Best,
-Stéphane

Le dimanche 15 août 2021 à 18:01:55 UTC+2, Eric Shulman a écrit :

> On Sunday, August 15, 2021 at 7:10:39 AM UTC-7 Misterel85 wrote:
>
>> I first thought there would have been a more straightforward solution to 
>> that issue, but actually I come to think that it should be possible to 
>> inspect the first character in the contents of field 2:
>> If value of field2 starts with space, then insert `` between the 
>> transclusions, else just proceed with both transclusions.
>>
>
> Try this:
> <$transclude field="field1"/><$text text={{{ 
> [{!!field2}split[]first[]match[ ]] }}}/><$transclude field="field2"/>
>
> Notes:
> * The {{{ [...] }}} is a "filtered transclusion"
> * The filter starts by getting the value of the desired field, using 
> {!!field2}
> * It then splits that value into separate characters, using split[]
> * Next, it gets just the first character, using first[]
> * and compares it with a space, using match[ ]
> * The result of the filter is either nothing, or an actual space character 
> (not an )
> * The <$text> widget then converts the output to plain text (instead of 
> displaying a link to a space!)
>
> enjoy,
> -e
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3afe1cc5-8ccd-4b0d-90e3-397ac079f9ffn%40googlegroups.com.

Re: [tw5] Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[Jeremy Ruston]

Hi Josiah

> A compounding factor is that devs of older stuff are often NOT around to fix 
> for compliance with new.
> The issue is the users who relied on what they thought were kosher tools that 
> STOP working that the author won't fix.

Indeed.

>  Jeremy: |  do plan to update the release note with a more prominent warning 
> of the impact of this change.
> 
> Good! IMHO, it might also be worth mentioning that their tool of concern 
> would continue to run fine under previous versions of TW. 
> For working apps mostly it is NOT needed you upgrade! 
> (("Upgradeitis" is a serious modern disease. :-))

>From the core perspective we really want people to upgrade actively used wikis 
>to each new version because it’s expensive and complex to offer support for 
>old versions. For example, if we had a user on v5.1.23 who was holding back 
>updating to v5.2.0 then that user wouldn’t be able to benefit from bug fixes 
>in subsequent releases. If they reported a bug that was then fixed by the core 
>team they wouldn’t be able to get the fix without updating.

Best wishes

Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5FED7921-F486-4CB1-9EF1-60A674723458%40gmail.com.

Re: [tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[PMario]

Did more tests ... It seems to be 

<$vars x={{!!toggled}} y={{!!barray}}>
<>


-m

On Sunday, August 15, 2021 at 6:41:56 PM UTC+2 PMario wrote:

> On Sunday, August 15, 2021 at 1:20:54 PM UTC+2 Jeremy Ruston wrote:
>
> * It should usually be easy to fix: wrap the macro invocation in a 
>> <$tiddler> widget referencing the tiddler in question
>
>
> I did test that, but it seems the tiddler-widget only views the 
> tiddler-attribute for a change and a simple state, that only calculates the 
> classes. ... 
> So if any tiddler-field changes, it doesn't do a refreshSelf() and may be 
> it shouldn't. It needs to refreshSelf() if the parameter itself is changed, 
> and not if the tiddler, where the parameter points to is changed. ... 
>
> But this seems to work: 
>
> <$set name=x value={{!!toggled}}>
> <>
> 
>
> and
>
> <$set name=x value={{!!toggled}}>
> <>
> 
>
>
> -mario
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5be4acbf-961e-4dca-8ac4-2a4d32668784n%40googlegroups.com.

Re: [tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[PMario]

On Sunday, August 15, 2021 at 1:20:54 PM UTC+2 Jeremy Ruston wrote:

* It should usually be easy to fix: wrap the macro invocation in a 
> <$tiddler> widget referencing the tiddler in question


I did test that, but it seems the tiddler-widget only views the 
tiddler-attribute for a change and a simple state, that only calculates the 
classes. ... 
So if any tiddler-field changes, it doesn't do a refreshSelf() and may be 
it shouldn't. It needs to refreshSelf() if the parameter itself is changed, 
and not if the tiddler, where the parameter points to is changed. ... 

But this seems to work: 

<$set name=x value={{!!toggled}}>
<>


and

<$set name=x value={{!!toggled}}>
<>



-mario

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

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[Eric Shulman]

On Sunday, August 15, 2021 at 7:10:39 AM UTC-7 Misterel85 wrote:

> I first thought there would have been a more straightforward solution to 
> that issue, but actually I come to think that it should be possible to 
> inspect the first character in the contents of field 2:
> If value of field2 starts with space, then insert `` between the 
> transclusions, else just proceed with both transclusions.
>

Try this:
<$transclude field="field1"/><$text text={{{ 
[{!!field2}split[]first[]match[ ]] }}}/><$transclude field="field2"/>

Notes:
* The {{{ [...] }}} is a "filtered transclusion"
* The filter starts by getting the value of the desired field, using 
{!!field2}
* It then splits that value into separate characters, using split[]
* Next, it gets just the first character, using first[]
* and compares it with a space, using match[ ]
* The result of the filter is either nothing, or an actual space character 
(not an )
* The <$text> widget then converts the output to plain text (instead of 
displaying a link to a space!)

enjoy,
-e

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

[tw5] Re: Highlighting duplicates in lists

[paulgilbert2000]

HI tones,

sorry i guess i asked the wrong question, what i wanted to know is where to 
place the widget  in the code , if i do it that way , it no longer 
highlights duplicates

 <>: |  
   <$list filter="[all[current]get[field_example]] 
[all[current]get[field_example2]] [all[current]get[field_example3]]" 
variable=field-value>
<$view field="field_example "format=date template=""/>
<$view field="field_example1"format=date template=""/>
<$view field="field_example2"format=date template=""/>

 matchthen[color: red;]] 
}}}><>



i also tried  adding format:date[DDD]] , which didn't yield any results 

   <$list filter="[all[current]get[field_example]] 
[all[current]get[field_example2]] [all[current]get[field_example3]]" 
format:date[DDD]] variable=field-value> 
On Sunday, August 15, 2021 at 10:12:57 AM UTC+2 TW Tones wrote:

> Look for and use the viewWidget and use the format date with a template, 
> or the format relativedate
>
> Get into the habit also of searching in tiddlywiki.com to learn how to do 
> things.
> [image: Snag_c8a06a9.png]
>
> eg;
>
> <$view field=created format=date template=""/>
>
> <$view field=created format=relativedate/>
>
>  5.1.23 now allows this inside filters. 
> 
>
> Regards
> Tones
>
> On Sunday, 15 August 2021 at 10:26:32 UTC+10 mohamed...@hotmail.com wrote:
>
>> Sorry one more questions
>>
>> if the values are dates, how can they be displayed in normal format ,and 
>> not the tiddly wiki format
>>
>> On Monday, August 9, 2021 at 1:10:18 AM UTC+2 paulgilbert2000 wrote:
>>
>>> Thank you tones
>>>
>>> Will take me a while to understand all that . but it works like a charm 
>>> , and its even more than what i have asked for
>>>
>>> thanks again:)
>>>
>>> On Sunday, August 8, 2021 at 7:31:10 AM UTC+2 TW Tones wrote:
>>>
 Mohamad,

 I am happy to look at solving the problem presented but my suspicion 
 remains that there may be a different way to put the question in the first 
 place. 

 Sometimes a question can be rephrased such that the answer is simpler 
 to find.

- In this we have multiple tiddlers, with multiple fields, with 
*values* that may be duplicated across these tiddlers/fields.
- in effect you want to list all tiddlers using the select fields, 
list these for each tiddler then for each found value
   -  detect when that value occurs in any other tiddler (not 
   self?) or select fields, if it does highlight it.
- I am not sure why you want to do this and can think of many ways 
to list/interpret the data! 
- What about triplicates?
- What about duplicates in the same tiddler?

 I think using your test data this is what you wanted?

 
 <$list filter="[all[]has[field_example]]">
<$set name=other-values 
 filter="[all[]!get[field_example]] 
 [all[]!titleget[field_example2]] 
 [all[]!titleget[field_example3]] +[sort[]]">
<>: |  
<$list filter="[all[current]get[field_example]] 
 [all[current]get[field_example2]] [all[current]get[field_example3]]" 
 variable=field-value>
 >>> [enlistmatchthen[color: red;]] 
 }}}><>
 

 
 

 It will also highlight triplicates...

 A slightly more efficient method is available that could actually could 
 the number of repeats and color red if > 1

 <$set name=all-values filter="=[all[]get[field_example]] 
 =[all[]get[field_example2]] =[all[]get[field_example3]]">
 "<>" {{{ [split[ ]count[]] }}}
 
 <$list filter="[all[]has[field_example]]">
<>: |  
<$list filter="[all[current]get[field_example]] 
 [all[current]get[field_example2]] [all[current]get[field_example3]]" 
 variable=field-value>
 <$set name=value-count filter="[split[ 
 ]matchcount[]]">
 compare:number:gt[1]then[color: 
 Red;]] }}} ><> (<>)
  
 
 
 
 

 Of course in the above you can choose not to show the count of the same 
 value delete  "(<>)"

 Regards
 Tones

 On Sunday, 8 August 2021 at 02:05:57 UTC+10 mohamed...@hotmail.com 
 wrote:

> Hi Tones,
>
> sorry for the late reply , i wasn't clear at all in my last question 
> actually
>
> So for example ,if  every tiddler has three fields  , field_example , 
> field_example2 and  field_example3 
>
> [image: Capture.PNG]
>
> and they are populated with values as such
>
> *   tiddler 1*has in field_example "3" And in field_example2 
> "2"And in field_example3 "6"
> and
>*tiddler 2 *   has in field_example "4" And in field_example2 
> "9"And in field_example3 "8"
> and
>*tiddler 3*has in field_example "2" And in field_example2 
> "7"And in 

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[Misterel85]

Thanks for your complementary explanation about order, Tones, and you're 
quite right.
But as I wrote in a previous message, in that particular TW instance I am 
adamant that I won't change the field order.

Concatenating / Joining snippets of text from two fields in immutable 
order, while retaining Wikitext or HTML formatting or links is exactly what 
I want to do.

The basic example I gave earlier is thus:

if field1 contains: 'The cat is eating'
field2 might contain: ' a mouse.' or ' cat food.' (note the space),  or ', 
while the dog is playing.' or '.' (no space required before a full stop / 
period or a comma).

Actually I need that to reference sources for tiddler contents. It is a bit 
more complex because field1 is in the source tiddler, providing general 
info, whereas field2 is in the content tiddler, with references specific to 
that content.

As an example:
field1 in 'source' tiddler might contain: 'Doe, John. //My Great Book.// 
(2020)'
while field2 in 'excerpt' or 'content' tiddler might contain details such 
as: ', p. 22.' or ' — see chapter 8.' or '. John Doe develops that idea in 
the first 3 chapters.'
So the leading character in field2 might either be a period, a comma, a 
space, depending on how I wish to gracefully join the two parts 
punctuation-wise.
It is pretty similar to connecting words and parts of speech in a sentence.

What I have achieved so far works fine, except for the space trimming in 
the transclusion of field 2.

I first thought there would have been a more straightforward solution to 
that issue, but actually I come to think that it should be possible to 
inspect the first character in the contents of field 2:

If value of field2 starts with space, then insert `` between the 
transclusions, else just proceed with both transclusions.
But I don't think I have enough TW knowledge to do that, unfortunately.

Best,

Stéphane

Le dimanche 15 août 2021 à 15:22:31 UTC+2, TW Tones a écrit :

> I think you can have your cake and eat it, as long as you use the 
> tiddlywiki recipe/ingredients.
>
> First lets see if I can explain about order.
>
> If this was my first design (with space between them)
> <$transclude field="field1" /> <$transclude field="field2" />
>
> And I decided I wanted;
> <$transclude field="field2" /> <$transclude field="field1" />
>
>
>- I modify the presentation in the above code, I do not need to modify 
>my data, just its presentation. This may be happening inside a list widget 
>for example.
>- In your case you may need to change both the presentation and the 
>data.
>
>
> Now, If I understand correctly you want to correctly treat the joining of 
> "snipits" found in fields correctly, you would be better served building 
> some standards for your data and tools to do the joining. Since there are 
> already implied standards for handling those values lets adopt them, then 
> if you can identify occasions where appending one snippet to the other by 
> separation with a space, is not working, let us detect and alter that case.
>
> In the original post I think you go down the path of altering the way they 
> are presented by modifying the data.
>
> *Could you give us some examples where you are finding it hard to join 
> such snippets?*
>
> I would suggest {{!!foo}}{{!!bar}} for your first example (As did 
> Mario)
>
> Tones
>
> On Sunday, 15 August 2021 at 22:54:39 UTC+10 Misterel85 wrote:
>
>> Thank you for your replies, PMario, Joshua and Tones.
>>
>> @ Joshua: Thanks a lot for taking the time to write this comprehensive 
>> and clear explanation.
>>
>> I have followed your solution to insert `\whitespace notrim` at the 
>> beginning of a tiddler text, but unfortunately, it doesn't work.
>>
>> I also tried to place it into a macro like this:
>>
>> ```
>> \define mymacro()
>> \whitespace notrim
>> <$transclude field="field1" /><$transclude field="field2" />
>> \end
>> ```
>>
>> but in vain. In the documentation , the 
>> default is set to 'notrim', so adding such an instruction in a macro is 
>> useless.
>>
>>
>> @ PMario:
>>
>> I am aware of the solution you provide, but inserting a normal or 
>> non-breakable space between the two transclusions is not an option.
>>
>> A very simplified example of what I would like to do is connecting two 
>> parts of something similar to a sentence together, but that sentence may 
>> not need a complement in the second part.
>> For instance:
>> if field1 contains: 'The cat is eating'
>> field2 might contain: ' a mouse.' or ' cat food.' (note the space), or 
>> '.' (no space required before a full stop / period).
>>
>> Your solution would always insert a space, even before a punctuation sign 
>> such as a period or a comma...
>>
>>
>>
>> @ Tones
>>
>> Your advice is worth following 'for standard use cases'. But what I wish 
>> to implement is probably not an ordinary one.
>>
>> You wrote:
>>
>>- The spacing you wish is something best done in the display of the 
>>  

[tw5] Presenting Text-to-Speech v1.0.0: the flip-side of Speech-to-Text!

[Finn Lancaster]

After seeing some recommendations for a text-to-speech plugin in TW5 while 
releasing the Speech-to-Text plugin v1.0.5 with BTC, I took it upon myself 
to make my first solo plugin: text-to-speech!

*How does it work?*
Text-to-Speech uses the web text-to-speech API, which functions like a 
screen reader. To apply this to TiddlyWiki, I made a custom function 
calling this API, which then takes as arguments a selected area of text 
using cutom code I wrote!

*Get Started!*
To get started with the plugin, you can install by drag-and-drop from 
text-to-speech.finnsoftware.net! Then, anywhere in your TiddlyWiki, you can 
highlight text, and press the hotkey Alt+Shift+E, and listen to the plugin 
read the text to you!

*What to Expect in the Future?*

   - test for foreign language support
   - test support across browsers
   - button in toolbar/editing

-- 
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/c5bcc9c8-76e3-44ef-b21f-9bb276b994b5n%40googlegroups.com.

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[TW Tones]

I think you can have your cake and eat it, as long as you use the 
tiddlywiki recipe/ingredients.

First lets see if I can explain about order.

If this was my first design (with space between them)
<$transclude field="field1" /> <$transclude field="field2" />

And I decided I wanted;
<$transclude field="field2" /> <$transclude field="field1" />


   - I modify the presentation in the above code, I do not need to modify 
   my data, just its presentation. This may be happening inside a list widget 
   for example.
   - In your case you may need to change both the presentation and the data.


Now, If I understand correctly you want to correctly treat the joining of 
"snipits" found in fields correctly, you would be better served building 
some standards for your data and tools to do the joining. Since there are 
already implied standards for handling those values lets adopt them, then 
if you can identify occasions where appending one snippet to the other by 
separation with a space, is not working, let us detect and alter that case.

In the original post I think you go down the path of altering the way they 
are presented by modifying the data.

*Could you give us some examples where you are finding it hard to join such 
snippets?*

I would suggest {{!!foo}}{{!!bar}} for your first example (As did 
Mario)

Tones

On Sunday, 15 August 2021 at 22:54:39 UTC+10 Misterel85 wrote:

> Thank you for your replies, PMario, Joshua and Tones.
>
> @ Joshua: Thanks a lot for taking the time to write this comprehensive and 
> clear explanation.
>
> I have followed your solution to insert `\whitespace notrim` at the 
> beginning of a tiddler text, but unfortunately, it doesn't work.
>
> I also tried to place it into a macro like this:
>
> ```
> \define mymacro()
> \whitespace notrim
> <$transclude field="field1" /><$transclude field="field2" />
> \end
> ```
>
> but in vain. In the documentation , the 
> default is set to 'notrim', so adding such an instruction in a macro is 
> useless.
>
>
> @ PMario:
>
> I am aware of the solution you provide, but inserting a normal or 
> non-breakable space between the two transclusions is not an option.
>
> A very simplified example of what I would like to do is connecting two 
> parts of something similar to a sentence together, but that sentence may 
> not need a complement in the second part.
> For instance:
> if field1 contains: 'The cat is eating'
> field2 might contain: ' a mouse.' or ' cat food.' (note the space), or '.' 
> (no space required before a full stop / period).
>
> Your solution would always insert a space, even before a punctuation sign 
> such as a period or a comma...
>
>
>
> @ Tones
>
> Your advice is worth following 'for standard use cases'. But what I wish 
> to implement is probably not an ordinary one.
>
> You wrote:
>
>- The spacing you wish is something best done in the display of the 
>data and not in the data, what if they changed order? 
>
>
> I don't understand what you mean by 'what if they changed order?'.
> What would change order? The data? The fields? No, I wouldn't need to 
> change their order. See my example above. Why would I need the 
> 'complementary' part of the data to show before the 'main' part?
>
> As for the spacing, it is an integral part of the data here (as a word 
> separator within a sencence, for instance). Therefore putting it anywhere 
> else in this case wouldn't be a wise choice.
>
>
>- A field containing a list of titles or tiddlers is typically space 
>delimited. So we often need the leading and trailing spaces not to be 
>included.
>
>
> Sure, but that's not my use case. And 'often' is not 'always'! ;-)
>
>
>- You can access fields in a different way if you really need to have 
>leading or training spaces as part of the data
>
>
> Well, that's exactly what I'm after!
>
>
> > '{{{ [all[current]get[afield]] }}}'
>
> > The transcluded filter output demonstrates the field contains a leading 
> space of it has one.
>
> That filter output is interesting. But it doesn't render HTML tags or 
> Wikitext, contrary to $transclude.
> If 'afield' contains: ` This is my //field//. `, 
> then 
> '{{{ [all[current]get[afield]] }}}'
> '<$text text={{{ [all[current]get[afield]] }}} />'
> '<$view field=afield />'
> all render raw text as: 
> ' This is my //field//. '
> whereas
> '<$transclude field=afield/>'
> renders as:
> 'This is *my* *field*.'
>
> Seems that I have to trade in the leading space for formatting and 
> vice-versa. Can't have my cake and eat it.
>
> Regards,
>
> Stéphane
>
>
>

-- 
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/16ca2a52-3650-4c35-ade2-571397e83523n%40googlegroups.com.

[tw5] Re: Timely help needed

[Ste]

Thanks. I'll delve into those a bit more next week when I'm at a pc. 
Now that I've looked I remember seeing the +1hour thread and thinking that 
would be useful! 
Just trying to automate things so the deadline tiddler auto updates from 
the end date of the assignment for example. 
Or setup to self populate week numbers from a given start date. 
Ste



On Sunday, August 15, 2021 at 12:59:50 AM UTC+1 mohamed...@hotmail.com 
wrote:

> Hey,
>
> i have a similar setup , not sure if this helps , but check this thread  
> https://groups.google.com/g/tiddlywiki/c/OUJlcbbK5v0/m/Wpc2SWMWAgAJ?hl=en  
>
> for adding a day , i don't know how to do it , however i got help to add 
> an hour in this thread
> https://groups.google.com/g/tiddlywiki/c/uB1RxGj2qz0/m/QYjk6VO_AwAJ?hl=en 
>   .. i think it will probably be easy to modify the 1 hour value to 24 to 
> achieve what you want
>
>
> On Friday, August 13, 2021 at 9:38:01 AM UTC+2 Ste wrote:
>
>>
>> For context this is what I'm working on:
>> https://tmc.stephenteacher.com/Assesment%20Schedule.html
>> On Thursday, 12 August 2021 at 18:42:18 UTC+1 Ste wrote:
>>
>>>
>>> Hello wonderful people's. 
>>> I need help with time. 
>>> I am sure there have been discussions about this but alas I can't seem 
>>> to find what I'm looking for. Google groups. You know how it is! 
>>>
>>> I have a date in a field. I would like to use this same date in another 
>>> tiddler, but it needs to be plain text so it can be used by the vis.js time 
>>> line plugin.. 
>>>
>>> I'd also like to be able to add/ subtract days and have it back into a 
>>> form the plugin can use. 
>>>
>>> I'd like a date picker to return the same date in different formats to 
>>> different fields, or be able to convert an existing date into a different 
>>> format, and for it to be useable by the time line or the timely calender. 
>>>
>>> So not much really... 
>>>
>>> Thanks for your time :)
>>>
>>> Ste 
>>>
>>> Date picker and timeline 
>>> http://kixam.github.io/TW5-visjsTimeline/
>>>
>>> Timely 
>>> https://tiddlytools.com/timer.html 
>>>
>>>
>>>

-- 
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/5f5b83a1-a2bc-4d48-9ed8-3d623d794204n%40googlegroups.com.

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[Misterel85]

Thank you for your replies, PMario, Joshua and Tones.

@ Joshua: Thanks a lot for taking the time to write this comprehensive and 
clear explanation.

I have followed your solution to insert `\whitespace notrim` at the 
beginning of a tiddler text, but unfortunately, it doesn't work.

I also tried to place it into a macro like this:

```
\define mymacro()
\whitespace notrim
<$transclude field="field1" /><$transclude field="field2" />
\end
```

but in vain. In the documentation , the 
default is set to 'notrim', so adding such an instruction in a macro is 
useless.


@ PMario:

I am aware of the solution you provide, but inserting a normal or 
non-breakable space between the two transclusions is not an option.

A very simplified example of what I would like to do is connecting two 
parts of something similar to a sentence together, but that sentence may 
not need a complement in the second part.
For instance:
if field1 contains: 'The cat is eating'
field2 might contain: ' a mouse.' or ' cat food.' (note the space), or '.' 
(no space required before a full stop / period).

Your solution would always insert a space, even before a punctuation sign 
such as a period or a comma...



@ Tones

Your advice is worth following 'for standard use cases'. But what I wish to 
implement is probably not an ordinary one.

You wrote:
- The spacing you wish is something best done in the display of the data 
and not in the data, what if they changed order? 

I don't understand what you mean by 'what if they changed order?'.
What would change order? The data? The fields? No, I wouldn't need to 
change their order. See my example above. Why would I need the 
'complementary' part of the data to show before the 'main' part?

As for the spacing, it is an integral part of the data here (as a word 
separator within a sencence, for instance). Therefore putting it anywhere 
else in this case wouldn't be a wise choice.

- A field containing a list of titles or tiddlers is typically space 
delimited. So we often need the leading and trailing spaces not to be 
included.

Sure, but that's not my use case. And 'often' is not 'always'! ;-)

- You can access fields in a different way if you really need to have 
leading or training spaces as part of the data

Well, that's exactly what I'm after!


> '{{{ [all[current]get[afield]] }}}'

> The transcluded filter output demonstrates the field contains a leading 
space of it has one.

That filter output is interesting. But it doesn't render HTML tags or 
Wikitext, contrary to $transclude.
If 'afield' contains: ` This is my //field//. `, 
then 
'{{{ [all[current]get[afield]] }}}'
'<$text text={{{ [all[current]get[afield]] }}} />'
'<$view field=afield />'
all render raw text as: 
' This is my //field//. '
whereas
'<$transclude field=afield/>'
renders as:
'This is *my* *field*.'

Seems that I have to trade in the leading space for formatting and 
vice-versa. Can't have my cake and eat it.

Regards,

Stéphane


-- 
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/19c1fa23-fb11-48c6-8ee6-513a5657597cn%40googlegroups.com.

Re: [tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[TiddlyTweeter]

Ciao Jeremy

A c*ompounding factor *is that devs of older stuff are often NOT around to 
fix for compliance with new.
The issue is the users who relied on what they thought were kosher tools 
that STOP working that the author won't fix.

 Jeremy: |  do plan to update the release note with a more prominent 
warning of the impact of this change.

Good! IMHO, it might also be worth mentioning that their tool of concern 
would continue to *run fine under previous versions of TW*. 
For working apps mostly it is NOT needed you upgrade! 
(("Upgradeitis" is a serious modern disease. :-))

Best wishes
TT


On Sunday, 15 August 2021 at 13:20:54 UTC+2 jeremy...@gmail.com wrote:

> But it is *slightly worrying* that Simon Kilner's(?) TOGGLER macro 
> (actually a re-write of something originally on Classic?) is kinda 
> *deprecated 
> *now. And NEVER was BEFORE.
>
> The tool WORKED forever already.
>
> And your formal explanation kinda misses the point that IF it *was *working, 
> *why *is it NOT working now?
>
>
> It's the price for fixing the ability to edit a field within the same 
> tiddler, which has been a perennial problem/bug that affects many users.
>
> There's definitely a tension with breaking these macros, but there's a 
> couple of points:
>
> * More users encounter the edit-field-of-same-tiddler problem than would 
> be running some old broken macro
> * These macros were broken to begin with, and in many/most cases the 
> authors chose to ignore warnings
> * It should usually be easy to fix: wrap the macro invocation in a 
> <$tiddler> widget referencing the tiddler in question
>
> With reference to the second point, we've always tried to educate 
> developers on the proper way to write macros. Literally every time a 
> developer posts about a JS macro that they're writing, my first angle is to 
> look to see if it follows the rules, and to provide feedback if not.
>
> In many cases, of course, developers aren't very interested, and work on 
> the basis of "it works for me so why should I change it", which of course 
> in the end can be very damaging to the community unless the limitations are 
> very carefully documented.
>
> I do plan to update the release note with a more prominent warning of the 
> impact of this change.
>
> Best wishes
>
> Jeremy
>
>
>
>

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

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

[Finn Lancaster]

Sounds great! I'll try my best to be there, although I have school at that 
time. Looking forward to seeing what @Saq, Jeremy, and everyone else have 
to say. Particularly related to the migration from GoogleGroups!

On Saturday, August 14, 2021 at 9:10:56 AM UTC-4 jeremy...@gmail.com wrote:

> Just to add that an additional topic we intend to discuss is the start of 
> a plan to migrate from Google Groups. We’ll give more details then,
>
> Best wishes
>
> Jeremy
>
> On Sat, 24 Jul 2021 at 17:36, Boris Mann  wrote:
>
>> Yes, it's hard to fit Europe, west coast North American, and Australian 
>> timezones in one slot -- sorry about that!
>>
>> Yes, the session will be recorded.
>>
>>
>> On Friday, July 23, 2021 at 6:28:12 PM UTC-7 TW Tones wrote:
>>
>>> Given
>>> Converted Time Sydney, NSW, Australia 
>>> 
>>> 2:00 am AEST 
>>> Wednesday, 18 August 2021
>>>
>>> I am not sure I will make it, perhaps in a follow-up one. If possible if 
>>> you can publish a recording after it would be appreciated.
>>>
>>> This subject means a lot to me. If I may share these points in advance 
>>> for consideration.
>>>
>>>
>>>- The provision of serial editing (one use after the other) through 
>>>check in and check out mechanisms, for all saver mechanism's.  This 
>>> would 
>>>be the quickest route to supporting multi-users/teams on tiddlywiki
>>>- It is quite easy to change the filename of a saved tiddlywiki, say 
>>>on php and tw-reciever. it seems to be the save technology can already 
>>> save 
>>>files to hosts. It seems to be we need to open this up to trusted users 
>>>with the appropriate credentials so for example
>>>   - A single file tiddlywiki could save the changes made by one 
>>>   user only, in an independent file (delta backup). Then either the 
>>>  - owner can import all user contributions and apply them to 
>>>  the master copy, 
>>>  - or users can recover their current state by loading their 
>>>  own file of changes (delta backup) from the host ). 
>>>  - or both 
>>>  - Contention and overwrites can be handled by the wiki 
>>>  designer or interactively.
>>>   - Designers could write information or logs to the host file 
>>>   system from the tiddlywiki, acknowledging all permitted users have 
>>> file 
>>>   update rights. This would allow survey answers, to be saved, comments 
>>> etc...
>>>
>>> Regards
>>> Tones
>>> On Saturday, 24 July 2021 at 04:02:41 UTC+10 bo...@fission.codes wrote:
>>>
 Thanks for the kind words, Saq. It's been great working with you and 
 Jeremy and I'm happy to support you and the community.

 I'd really like some open discussion around how the TiddlyWiki 
 community can use and rally around Open Collective. I'm personally _very_ 
 inspired by the organization and the promise it has over time -- and where 
 it is at today. Their recent blog post is a very good read 
 https://blog.opencollective.com/solidarity-as-our-guiding-principle/. 
 I'll quote part of the post:

 *Technology Owned by the People*
 *Open Collective is part of a movement for start-ups and tech platforms 
 become to become owned by their users and stakeholders, called “exit to 
 community” or E2C. Learn more about this community interested in community 
 control and governance here. We don’t know exactly what the future holds, 
 but OCF, grounded in perspectives of solidarity, will be a key influence 
 on 
 the future of the Open Collective platform as a commons.*

 In short, I've been working with open source software and communities 
 for 2 decades now. I'm more convinced than ever that we can "Build 
 Software 
 Together" and that Open Collective is a tool that can be used by 
 communities to pool funds towards common goals.

 This experiment with the file uploads plugin has lead directly to 
 having Saq spend time working on a more solid foundation for core TW 
 architecture. Can we continue this? Can we get more small and large 
 projects and people funded through OC?

 On Thursday, July 22, 2021 at 12:33:18 PM UTC-7 saq.i...@gmail.com 
 wrote:

> We will be having a *TiddlyWiki Community call* with Jeremy, Boris 
> and myself on August 17th at 6pm CET: TiddlyWiki Community: Core 
> Savers & Syncers, Upload Plugin, & Community Forum - Zoom 
> 
>
> I hope some of you will be able to join us for what I think will be a 
> very interesting discussion. Please register for the event at the link 
> above.
>
> The call will include:
>
>- a progress update on my work on the *Uploads plugin* funded by 
>Open Collective
>- a summary of some rather exciting and promising avenues for core 

[tw5] Re: Speech-to-Text v1.0.5 is here!

[Finn Lancaster]

@TiddlyTweeter: 

To answer just your question about punctuation, I have tested the plugin 
with various punctuation words. The result is, by saying "comma", you have 
a comma. The same works for question marks, periods, etc. Some of your 
other points, I felt were really good, as well. Hopefully @BurningTreeC and 
I can implement them in later versions of the plugin!

On Sunday, August 15, 2021 at 6:10:50 AM UTC-4 TiddlyTweeter wrote:

> Ciao Flanc & BTC ...
>
> I agree with @Tones "Wow!". 
> And the tool has already changed how I use some wiki.
>
> ONE point I'd like to quickly make whilst the iron is hot. (Which I will 
> fill in details for later with more precision.)
>
> From MY point of view, I want to get my DICTATION/TRANSCRIPTION so it is 
> optimally efficient. 
> (FYI, I'm far less concerned with controlling the wiki outwith dictation. 
> I'm also not that interested in whether it can "read-back" or record to an 
> audio file. 
>
> *First I need to get basic transcription working really well! *:)
>
> To give simple examples of, I think, main *dictation focused needs* ...
>
> 1 - A way to verbally insert PUNCTUATION. (Without it, long dictation 
> produces unwieldy texts.)
>
> 2 - A way to verbally INSERT "boilerplate text". 
> For instance: "*Ok Wiki insert exercise intro"*. Which might(?) be text 
> in a Tiddler called "Exercise Intro" like "Lie on you back and rest a 
> moment, scanning for how your back contacts the floor. Notice which parts 
> touch it and which parts don't."
>
> You get the* idea? *
>
> *What I don't currently understand is how in dictation you'd execute a 
> command to INSERT "boilerplate" text into the ongoing transcription?*
>
> 3 - A way to CONCATENATE transcript fragments. 
> WHAT do I mean? In a test I dictated a long text in small segments. The 
> result being that I ended up with ... 
>
>   - New Transcript
>   - New Transcript 1
> *... through to ...*
>- New Transcript 23
>
> Manually joining those would be a fag. Maybe we need a way to click a 
> button to CONCATENATE* (latest last) *all those new transcript fragments?
>
> Just a thought, and likely YOU don't need to devise that as a standard TW 
> macro could likely do it?
> BUT I did think it a real functional need for folk interested in serious 
> dictation to be able to manipulate Transcripts, and this is one of the 
> needs?
>
> It is also fun to play with! :-)
>
> Thanks & best wishes
> TT
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3aea9b7e-d564-498f-a76c-37d680352f2an%40googlegroups.com.

[tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[Saq Imtiaz]

@cmari perhaps this is closer to what you need?
https://groups.google.com/g/tiddlywiki/c/9hZTwQBuwe8/m/YlRPXrn0BQAJ

Note that you can use the "arrow" buttons to move forwards and backwards in 
time.

I've bookmarked these two habit tracking solutions so they show up at 
TiddlyWikiLinks:
https://links.tiddlywiki.com/topics/daily-tasks/

On Saturday, August 14, 2021 at 8:03:30 PM UTC+2 cmari wrote:

> Yes, I have seen that, thanks. Unfortunately, I lack the necessary 
> skills/time to identify the pieces that would need to be adapted to allow 
> for viewing (and updating) a running overview of the task status for the 
> last 10 days.
>
> On Saturday, August 14, 2021 at 10:04:33 AM UTC-7 saq.i...@gmail.com 
> wrote:
>
>> This is one of the first things that came up with a search, perhaps it 
>> may be of interest:
>> https://rawgit.com/Guitlle/habito/build/build/habito-docs.html
>>
>> On Saturday, August 14, 2021 at 6:54:23 PM UTC+2 Saq Imtiaz wrote:
>>
>>> Just to add a bit more clarification to the issue since I have a bit 
>>> more time now than I did yesterday, this functionality should have been 
>>> implemented as a widget and not a macro. I quickly dropped the link in 
>>> reply yesterday so you would know that there was some follow up on your 
>>> post.
>>>
>>> JavaScript macros in TiddlyWiki5 are supposed to be for simple text 
>>> substitution and do not have any facilities for refreshing in response to 
>>> other changes in the wiki, the input of the macro determines the output. A 
>>> macro should never modify tiddlers. The macro in question both needs to 
>>> refresh itself in response to tiddler changes, and also modifies tiddlers. 
>>>
>>> Such a macro was never intended to be supported but has worked so far 
>>> because we were aggressively refreshing entire tiddlers when anything in 
>>> that tiddler changed. So for example a change to a tiddler "list" field 
>>> would refresh the entire tiddler in the story. However this is suboptimal 
>>> both from a performance point of view and in terms of user experience. Some 
>>> of the annoyances commonly encountered like an edit-text widget in a 
>>> tiddlers text field not being usable to modify a field in the same tiddler 
>>> come from this aggressive and unnecessary refresh behaviour.
>>>
>>> So the question that presents itself now is whether we maintain 
>>> backwards compatibility for a behaviour from third party macros that was 
>>> never intended to be supported and holds back improvements, or break such 
>>> macros as their implementation will trip us up again in unexpected places 
>>> and limit future possibilities.
>>>
>>> Your actual need for the functionality offered by this macro could 
>>> probably be solved with a wikitext implementation as well. It might be 
>>> worth a search to see if someone has shared such a solution.
>>>
>>> Regards,
>>> Saq
>>>
>>> On Saturday, August 14, 2021 at 6:42:38 PM UTC+2 cmari wrote:
>>>
 Thanks Saq, that was certainly not the answer I was hoping for, but 
 it's good to know which way the wind is blowing after so many years (I 
 think the original dailytasks plugin that got me started 13 years ago came 
 from you?).
 cmari (considering changing my name to "offspec user"!)

 On Friday, August 13, 2021 at 1:03:59 PM UTC-7 saq.i...@gmail.com 
 wrote:

> See 
> https://github.com/Jermolene/TiddlyWiki5/issues/5903#issuecomment-898691487
>
> On Friday, August 13, 2021 at 9:26:33 PM UTC+2 cmari wrote:
>
>> I have been a happy daily user of *Daily Task Macro *(
>> http://togglers.tiddlyspot.com/) for years, so I am wondering 
>> whether someone can point me to any tips for how I might update the 
>> macro 
>> so that it will continue to work in the new prerelease. 
>>  
>> Specifically, the fields in toggler tiddlers do continue to update 
>> correctly when the images are clicked, but the (svg) images themselves 
>> do 
>> not update in response to the click until the tiddler is opened and 
>> closed 
>> again.
>>
>> Thanks for any help!
>> cmari
>>
>

-- 
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/14565e42-4306-482a-aef8-dc62a82784a9n%40googlegroups.com.

Re: [tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[Jeremy Ruston]

> But it is slightly worrying that Simon Kilner's(?) TOGGLER macro (actually a 
> re-write of something originally on Classic?) is kinda deprecated now. And 
> NEVER was BEFORE.
> 
> The tool WORKED forever already.
> 
> And your formal explanation kinda misses the point that IF it was working, 
> why is it NOT working now?

It's the price for fixing the ability to edit a field within the same tiddler, 
which has been a perennial problem/bug that affects many users.

There's definitely a tension with breaking these macros, but there's a couple 
of points:

* More users encounter the edit-field-of-same-tiddler problem than would be 
running some old broken macro
* These macros were broken to begin with, and in many/most cases the authors 
chose to ignore warnings
* It should usually be easy to fix: wrap the macro invocation in a <$tiddler> 
widget referencing the tiddler in question

With reference to the second point, we've always tried to educate developers on 
the proper way to write macros. Literally every time a developer posts about a 
JS macro that they're writing, my first angle is to look to see if it follows 
the rules, and to provide feedback if not.

In many cases, of course, developers aren't very interested, and work on the 
basis of "it works for me so why should I change it", which of course in the 
end can be very damaging to the community unless the limitations are very 
carefully documented.

I do plan to update the release note with a more prominent warning of the 
impact of this change.

Best wishes

Jeremy



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3A4AD25B-76DD-4DD4-ADC4-F8A6BD557180%40gmail.com.

[tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[TiddlyTweeter]

Ciao Saq ...

Side comment ... 

saq.i...@gmail.com wrote:

> ... Just to add a bit more clarification ... this functionality should 
> have been implemented as a widget and not a macro. 

 

> JavaScript macros in TiddlyWiki5 are supposed to be for simple text 
> substitution and do not have any facilities for refreshing in response to 
> other changes in the wiki, the input of the macro determines the output. 
>
 

> ... Such a macro was never intended to be supported but has worked so far 
> because we were aggressively refreshing entire tiddlers when anything in 
> that tiddler changed. 
>

Right! YET.

But it is *slightly worrying* that Simon Kilner's(?) TOGGLER macro 
(actually a re-write of something originally on Classic?) is kinda *deprecated 
*now. And NEVER was BEFORE.

The tool WORKED forever already.

And your formal explanation kinda misses the point that IF it *was *working, 
*why *is it NOT working now?

Saq, I never want to argue with you, you are so sweet! :-) 
I just think that the *recent leap *in TiddlyWiki is kinda a BREAK with 
it's previous tolerance of non-kosher JS?

IMO, one of the great achievements of TW has been the combo of VAST 
functional expansion combined with pretty amazing backwards compatibility. 

THIS is an interesting case where it broke down.

Just thoughts
TT


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

[tw5] Re: Speech-to-Text v1.0.5 is here!

[TiddlyTweeter]

Ciao Flanc & BTC ...

I agree with @Tones "Wow!". 
And the tool has already changed how I use some wiki.

ONE point I'd like to quickly make whilst the iron is hot. (Which I will 
fill in details for later with more precision.)

>From MY point of view, I want to get my DICTATION/TRANSCRIPTION so it is 
optimally efficient. 
(FYI, I'm far less concerned with controlling the wiki outwith dictation. 
I'm also not that interested in whether it can "read-back" or record to an 
audio file. 

*First I need to get basic transcription working really well! *:)

To give simple examples of, I think, main *dictation focused needs* ...

1 - A way to verbally insert PUNCTUATION. (Without it, long dictation 
produces unwieldy texts.)

2 - A way to verbally INSERT "boilerplate text". 
For instance: "*Ok Wiki insert exercise intro"*. Which might(?) be text in 
a Tiddler called "Exercise Intro" like "Lie on you back and rest a moment, 
scanning for how your back contacts the floor. Notice which parts touch it 
and which parts don't."

You get the* idea? *

*What I don't currently understand is how in dictation you'd execute a 
command to INSERT "boilerplate" text into the ongoing transcription?*

3 - A way to CONCATENATE transcript fragments. 
WHAT do I mean? In a test I dictated a long text in small segments. The 
result being that I ended up with ... 

  - New Transcript
  - New Transcript 1
*... through to ...*
   - New Transcript 23

Manually joining those would be a fag. Maybe we need a way to click a 
button to CONCATENATE* (latest last) *all those new transcript fragments?

Just a thought, and likely YOU don't need to devise that as a standard TW 
macro could likely do it?
BUT I did think it a real functional need for folk interested in serious 
dictation to be able to manipulate Transcripts, and this is one of the 
needs?

It is also fun to play with! :-)

Thanks & best wishes
TT

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

[tw5] Re: Speech-to-Text v1.0.5 is here!

[TiddlyTweeter]

BurningTreeC wrote:

> The Link to the GitHub project page 
> https://github.com/flancast90/Speech-To-Text-in-TW5
>
> The Link to the Demo page https://speech-to-text.finnsoftware.net/
>

Thanks BTC & Flanc for the update beta.

I will check over next few days & comment back

Best wishes, TT 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/677ba613-26dc-48f3-9158-25597567ed57n%40googlegroups.com.

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[PMario]

On Sunday, August 15, 2021 at 9:19:57 AM UTC+2 TW Tones wrote:
 

>
>- The spacing you wish is something best done in the display of the 
>data and not in the data, what if they changed order? 
>
> I can only second that. If the data needs to be treated special, you will 
get a maintenance problem and it's errorprone. Everytime you forget about 
the special handling. It ends up to be more work. ...

-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2a6668b8-1081-407c-979c-42bd03783a78n%40googlegroups.com.

[tw5] Re: System and shadow need some love

[TW Tones]

Post script,

In line with the OT, I also though we could have a system-caption field 
that is searched Along with standard tiddlers, so system tiddlers would 
have the option of "publishing themselves" in the standard search. eg the 
tag manager, if you search for it in empty you will not find it, as it 
exist in a system tiddler  $:/TagManager if we gave this a system-caption = 
"Tag Manager" then this system tiddler would be found although it is a 
system tiddler.

This is a somewhat simple core change, or hack.

Regards
Tones
On Sunday, 15 August 2021 at 18:25:39 UTC+10 TW Tones wrote:

> I am late to this thread but I have designed a method called advanced 
> search indicators. Below
>
> There is already a feature to support tabs see $:/tags/SearchResults 
> 
> additional tabs appear in the standard search drop down if you tag some 
> search tabs, *although I am not keen on this method*.
>
> eg make a tiddler tagged $:/tags/SearchResults and the field caption = 
> System and include the below, now search in the sidebar
> \define searchResultList()
>
> //Search System Tiddlers//
> //{{$:/language/Search/Matches/Title}}//
> <$list 
> filter="[is[system]search:title{$(searchTiddler)$}sort[title]limit[250]]" 
> template="$:/PSaT/ExtendedSearch/ListItemCaptionTemplate"/>
>
> //{{$:/language/Search/Matches/All}}//
>
> <$list filter="[is[system]search{$(searchTiddler)$}sort[title]limit[250]]" 
> template="$:/PSaT/ExtendedSearch/ListItemCaptionTemplate"/>
>
> \end
> <>
>
> *Advanced search indicators - design concept*
>
>- What it does is monitor the content if the standard search entry and 
>does much of what you want, ie starts with $ searches for system tiddlers, 
>or allows you to open a tiddler if it exists and a lot, lot more. 
> Basically 
>additional icons appear that if clicked will do something based on the 
>content of the search temp field. eg list all items with the current 
> search 
>string as a prefix...
>
> I will publish this one day, and sooner if someone can sponsor me.
>
> Tones
>
>
>
> On Sunday, 15 August 2021 at 10:23:56 UTC+10 springer wrote:
>
>> David, I'm confused why you see 5 steps to get to advanced search. 
>>
>> Control-Shift-A opens the Advanced Search tiddler and puts your cursor in 
>> the search field... The tab is whatever you last chose, so often there's 
>> only the one quick step. 
>>
>> Your other points are important (and I too use advanced search about as 
>> often as the standard search), but this "5-steps" description misses the 
>> keyboard shortcut...
>>
>> -Springer
>>
>> On Saturday, August 14, 2021 at 10:10:44 AM UTC-4 David Gifford wrote:
>>
>>> I hate the loss of the edit post button on this forum. 
>>>
>>> I forgot a point: the actual steps are four, before you can enter your 
>>> search term in $:/Advanced search:
>>>
>>> 1. Move from what you are doing in the story river, to the sidebar.
>>> 2. Resist the urge to do a regular search, and instead click 
>>> $:/AdvancedSearch button.
>>> 3. Switch your attention back to the story river to view 
>>> $:/AdvancedSearch.
>>> 4. Pick a tab
>>> 5. Then and only then can you enter your search string.
>>>
>>> Instead, what I am proposing is
>>>
>>> 1. Move from what you are doing in the story river, to the sidebar. 
>>> 2. Enter search string in regular search bar **as step two, rather than 
>>> step five**
>>> 3. Pick a tab and see results
>>> 4. Refine search string if needed
>>>
>>> On Saturday, August 14, 2021 at 10:01:54 AM UTC-4 David Gifford wrote:
>>>
 Hi everyone

 I am playing with the field-search plugin by PMario, and seeing how 
 search results for a simple search come up in tabs one can pick from.

 This made me wonder, why couldn't there be something similar: do a 
 search from the default searchbar, and have standard, system and shadow 
 come up as tabs? 

 This seems like it would be much more intuitive for users: search, then 
 filter results. As it stands, $:/AdvancedSearch does the opposite: it 
 makes 
 you pick a type of search (standard, system, shadow, filter) first, and 
 only then can you do the search. The search string you want to enter may 
 or 
 may not stay in your short term memory while you are figuring out which 
 type of search you want to do. It seems like it would be a better user 
 experience to 'dump' the search term first, then figure out which tab you 
 want.

 On the same subject, Why is there no comparable "recent" tab for system 
 tiddlers? It seems like developers would benefit greatly having something 
 like that open as they work on macros, styling, buttons, etc. 

 I would love to hear your input: 
 Do you agree with me? Why or why not? If so, should this be core pull 
 request or a plugin? 
 What are the reasons $:/AdvancedSearch is set up backwards? Technical 

[tw5] Re: System and shadow need some love

[TW Tones]

I am late to this thread but I have designed a method called advanced 
search indicators. Below

There is already a feature to support tabs see $:/tags/SearchResults 

additional tabs appear in the standard search drop down if you tag some 
search tabs, *although I am not keen on this method*.

eg make a tiddler tagged $:/tags/SearchResults and the field caption = 
System and include the below, now search in the sidebar
\define searchResultList()

//Search System Tiddlers//
//{{$:/language/Search/Matches/Title}}//
<$list 
filter="[is[system]search:title{$(searchTiddler)$}sort[title]limit[250]]" 
template="$:/PSaT/ExtendedSearch/ListItemCaptionTemplate"/>

//{{$:/language/Search/Matches/All}}//

<$list filter="[is[system]search{$(searchTiddler)$}sort[title]limit[250]]" 
template="$:/PSaT/ExtendedSearch/ListItemCaptionTemplate"/>

\end
<>

*Advanced search indicators - design concept*

   - What it does is monitor the content if the standard search entry and 
   does much of what you want, ie starts with $ searches for system tiddlers, 
   or allows you to open a tiddler if it exists and a lot, lot more. Basically 
   additional icons appear that if clicked will do something based on the 
   content of the search temp field. eg list all items with the current search 
   string as a prefix...

I will publish this one day, and sooner if someone can sponsor me.

Tones



On Sunday, 15 August 2021 at 10:23:56 UTC+10 springer wrote:

> David, I'm confused why you see 5 steps to get to advanced search. 
>
> Control-Shift-A opens the Advanced Search tiddler and puts your cursor in 
> the search field... The tab is whatever you last chose, so often there's 
> only the one quick step. 
>
> Your other points are important (and I too use advanced search about as 
> often as the standard search), but this "5-steps" description misses the 
> keyboard shortcut...
>
> -Springer
>
> On Saturday, August 14, 2021 at 10:10:44 AM UTC-4 David Gifford wrote:
>
>> I hate the loss of the edit post button on this forum. 
>>
>> I forgot a point: the actual steps are four, before you can enter your 
>> search term in $:/Advanced search:
>>
>> 1. Move from what you are doing in the story river, to the sidebar.
>> 2. Resist the urge to do a regular search, and instead click 
>> $:/AdvancedSearch button.
>> 3. Switch your attention back to the story river to view 
>> $:/AdvancedSearch.
>> 4. Pick a tab
>> 5. Then and only then can you enter your search string.
>>
>> Instead, what I am proposing is
>>
>> 1. Move from what you are doing in the story river, to the sidebar. 
>> 2. Enter search string in regular search bar **as step two, rather than 
>> step five**
>> 3. Pick a tab and see results
>> 4. Refine search string if needed
>>
>> On Saturday, August 14, 2021 at 10:01:54 AM UTC-4 David Gifford wrote:
>>
>>> Hi everyone
>>>
>>> I am playing with the field-search plugin by PMario, and seeing how 
>>> search results for a simple search come up in tabs one can pick from.
>>>
>>> This made me wonder, why couldn't there be something similar: do a 
>>> search from the default searchbar, and have standard, system and shadow 
>>> come up as tabs? 
>>>
>>> This seems like it would be much more intuitive for users: search, then 
>>> filter results. As it stands, $:/AdvancedSearch does the opposite: it makes 
>>> you pick a type of search (standard, system, shadow, filter) first, and 
>>> only then can you do the search. The search string you want to enter may or 
>>> may not stay in your short term memory while you are figuring out which 
>>> type of search you want to do. It seems like it would be a better user 
>>> experience to 'dump' the search term first, then figure out which tab you 
>>> want.
>>>
>>> On the same subject, Why is there no comparable "recent" tab for system 
>>> tiddlers? It seems like developers would benefit greatly having something 
>>> like that open as they work on macros, styling, buttons, etc. 
>>>
>>> I would love to hear your input: 
>>> Do you agree with me? Why or why not? If so, should this be core pull 
>>> request or a plugin? 
>>> What are the reasons $:/AdvancedSearch is set up backwards? Technical 
>>> limitations? Workflow-related?
>>> What are the ways you work around these limitations?
>>>
>>>

-- 
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/0596e1a3-27f2-4478-bcec-41ed4b8dc736n%40googlegroups.com.

[tw5] Re: Speech-to-Text v1.0.5 is here!

[BurningTreeC]

Hi @Tones,

To answer 4)
There's the tiddler $:/config/speech-to-text/keywords that can be used to 
add multiple new keywords
Use its fields "ok-keywords" and "wiki-keywords" for that
There's the rule that we're using two keywords which are "Ok" and "Wiki"
But the $:/config/speech-to-text/keywords can be used to extend them

An example:

ok-keywords: bonjour Bonjour
wiki-keywords: madame Madame

TW Tones schrieb am Sonntag, 15. August 2021 um 10:04:42 UTC+2:

> Thanks BTC, and especially Flanc...
>
> This is seriously cool, I will try and contribute more moving forward.
>
> I can't believe how I could switch to the French language and even my poor 
> French was recognised as I spoke it. Wow.  As I said before to practice a 
> new language and succeed at having the correct words transcribed is a 
> revolutionary tool. No need to always talk to native speakers to practice :)
>
>
>
> Some thoughts
>
>1. I feel perhaps I need to identify easy ways to have tiddlers read 
>back to us as a complement, I am sure there are similar tools for 
> browsers, 
>whether or not they can be built in like this transcription process. There 
>was a plugin that reads text with a progress indication over the text as 
> it 
>reads, I will share when I locate it. 
>   1. Windows already has text to voice readers, 
>2. I do look forward, if possible to inserting transcriptions into 
>existing text, which I understand is on the list of features.
>3. The commands seem to be working well. 
>4. I do not follow how to add multiple new keywords, I am just a 
>little confused.
>5. Is it possible to capture the actual audio and save that in a 
>tiddler as well? 
>   1. ie using voice not only to transcribe but also to trigger a 
>   recording. 
>
>
> Speculation
>
>- The reason I ask question 5 above, is along with 1. above we could 
>build a wiki for managing reading and playing spoken word as a script or 
>like karaoke. Podcasters, radio producers etc... may find this useful. 
> Then 
>editing content could be as simple as rearranging tiddlers, be it textural 
>and/or audio read what you hear, and see what is up next.
>- If this was running on top of a node server we could imagine the 
>operating system responding when detecting a new tiddler containing 
>instructions.
>- I listen to a lot of spoken work podcasts. Perhaps one day I can 
>just play a favorite quote into my microphone, to capture it in 
> tiddlywiki, 
>a bit like how I can copy and past a types transcript.
>
> Regards
> Your excited tiddlywikian
> Tones
>
> On Sunday, 15 August 2021 at 17:11:49 UTC+10 BurningTreeC wrote:
>
>> The Link to the GitHub project page 
>> https://github.com/flancast90/Speech-To-Text-in-TW5
>>
>> The Link to the Demo page https://speech-to-text.finnsoftware.net/
>>
>> TW Tones schrieb am Sonntag, 15. August 2021 um 09:06:51 UTC+2:
>>
>>>
>>> Links etc... here in this thread please
>>> On Sunday, 15 August 2021 at 08:55:13 UTC+10 flanc...@gmail.com wrote:
>>>
 *What's New?*

 New language features:

- auto switch when TW language switched (opt-in on plugin settings)
- more settings, such as continuous listening option!
- Loads of more languages!
- minor BUG fixes
- and lots more!



-- 
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/92eba636-bb96-42c1-bac8-f222a5ead3d5n%40googlegroups.com.

[tw5] Re: Highlighting duplicates in lists

[TW Tones]

Look for and use the viewWidget and use the format date with a template, or 
the format relativedate

Get into the habit also of searching in tiddlywiki.com to learn how to do 
things.
[image: Snag_c8a06a9.png]

eg;

<$view field=created format=date template=""/>

<$view field=created format=relativedate/>

 5.1.23 now allows this inside filters. 


Regards
Tones

On Sunday, 15 August 2021 at 10:26:32 UTC+10 mohamed...@hotmail.com wrote:

> Sorry one more questions
>
> if the values are dates, how can they be displayed in normal format ,and 
> not the tiddly wiki format
>
> On Monday, August 9, 2021 at 1:10:18 AM UTC+2 paulgilbert2000 wrote:
>
>> Thank you tones
>>
>> Will take me a while to understand all that . but it works like a charm , 
>> and its even more than what i have asked for
>>
>> thanks again:)
>>
>> On Sunday, August 8, 2021 at 7:31:10 AM UTC+2 TW Tones wrote:
>>
>>> Mohamad,
>>>
>>> I am happy to look at solving the problem presented but my suspicion 
>>> remains that there may be a different way to put the question in the first 
>>> place. 
>>>
>>> Sometimes a question can be rephrased such that the answer is simpler to 
>>> find.
>>>
>>>- In this we have multiple tiddlers, with multiple fields, with 
>>>*values* that may be duplicated across these tiddlers/fields.
>>>- in effect you want to list all tiddlers using the select fields, 
>>>list these for each tiddler then for each found value
>>>   -  detect when that value occurs in any other tiddler (not self?) 
>>>   or select fields, if it does highlight it.
>>>- I am not sure why you want to do this and can think of many ways 
>>>to list/interpret the data! 
>>>- What about triplicates?
>>>- What about duplicates in the same tiddler?
>>>
>>> I think using your test data this is what you wanted?
>>>
>>> 
>>> <$list filter="[all[]has[field_example]]">
>>><$set name=other-values 
>>> filter="[all[]!get[field_example]] 
>>> [all[]!titleget[field_example2]] 
>>> [all[]!titleget[field_example3]] +[sort[]]">
>>><>: |  
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> variable=field-value>
>>> >> [enlistmatchthen[color: red;]] 
>>> }}}><>
>>> 
>>>
>>> 
>>> 
>>>
>>> It will also highlight triplicates...
>>>
>>> A slightly more efficient method is available that could actually could 
>>> the number of repeats and color red if > 1
>>>
>>> <$set name=all-values filter="=[all[]get[field_example]] 
>>> =[all[]get[field_example2]] =[all[]get[field_example3]]">
>>> "<>" {{{ [split[ ]count[]] }}}
>>> 
>>> <$list filter="[all[]has[field_example]]">
>>><>: |  
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> variable=field-value>
>>> <$set name=value-count filter="[split[ 
>>> ]matchcount[]]">
>>> compare:number:gt[1]then[color: 
>>> Red;]] }}} ><> (<>)
>>>  
>>> 
>>> 
>>> 
>>> 
>>>
>>> Of course in the above you can choose not to show the count of the same 
>>> value delete  "(<>)"
>>>
>>> Regards
>>> Tones
>>>
>>> On Sunday, 8 August 2021 at 02:05:57 UTC+10 mohamed...@hotmail.com 
>>> wrote:
>>>
 Hi Tones,

 sorry for the late reply , i wasn't clear at all in my last question 
 actually

 So for example ,if  every tiddler has three fields  , field_example , 
 field_example2 and  field_example3 

 [image: Capture.PNG]

 and they are populated with values as such

 *   tiddler 1*has in field_example "3" And in field_example2 
 "2"And in field_example3 "6"
 and
*tiddler 2 *   has in field_example "4" And in field_example2 
 "9"And in field_example3 "8"
 and
*tiddler 3*has in field_example "2" And in field_example2 
 "7"And in field_example3 "5"
 and
*tiddler 4*has in field_example "1" And in field_example2 
 "2"And in field_example3 "4"   


  as you can see, the number 2  is reoccurring in different fields in 
 different tiddlers , so when doing a list, can all these tiddlers  which 
 has a 2 be highlighted

 [image: Capture2.PNG]

 even better can the transcluded values only be highlighted and not the 
 whole line
 [image: Capture3.PNG] 

 i have attached a sample file with with the test data i am working with
  

 Thanks again for your help


 On Monday, August 2, 2021 at 2:33:26 AM UTC+2 TW Tones wrote:

> Mohamad,
>
> My solution above can be used to do this for multiple fields/criteria 
> because it re-examines the whole list every time. This makes it logically 
> very flexible but revisiting the whole list for every special field for 
> each tiddler is not very high 

[tw5] Re: Speech-to-Text v1.0.5 is here!

[TW Tones]

Thanks BTC, and especially Flanc...

This is seriously cool, I will try and contribute more moving forward.

I can't believe how I could switch to the French language and even my poor 
French was recognised as I spoke it. Wow.  As I said before to practice a 
new language and succeed at having the correct words transcribed is a 
revolutionary tool. No need to always talk to native speakers to practice :)



Some thoughts

   1. I feel perhaps I need to identify easy ways to have tiddlers read 
   back to us as a complement, I am sure there are similar tools for browsers, 
   whether or not they can be built in like this transcription process. There 
   was a plugin that reads text with a progress indication over the text as it 
   reads, I will share when I locate it. 
  1. Windows already has text to voice readers, 
   2. I do look forward, if possible to inserting transcriptions into 
   existing text, which I understand is on the list of features.
   3. The commands seem to be working well. 
   4. I do not follow how to add multiple new keywords, I am just a little 
   confused.
   5. Is it possible to capture the actual audio and save that in a tiddler 
   as well? 
  1. ie using voice not only to transcribe but also to trigger a 
  recording. 
   

Speculation

   - The reason I ask question 5 above, is along with 1. above we could 
   build a wiki for managing reading and playing spoken word as a script or 
   like karaoke. Podcasters, radio producers etc... may find this useful. Then 
   editing content could be as simple as rearranging tiddlers, be it textural 
   and/or audio read what you hear, and see what is up next.
   - If this was running on top of a node server we could imagine the 
   operating system responding when detecting a new tiddler containing 
   instructions.
   - I listen to a lot of spoken work podcasts. Perhaps one day I can just 
   play a favorite quote into my microphone, to capture it in tiddlywiki, a 
   bit like how I can copy and past a types transcript.

Regards
Your excited tiddlywikian
Tones

On Sunday, 15 August 2021 at 17:11:49 UTC+10 BurningTreeC wrote:

> The Link to the GitHub project page 
> https://github.com/flancast90/Speech-To-Text-in-TW5
>
> The Link to the Demo page https://speech-to-text.finnsoftware.net/
>
> TW Tones schrieb am Sonntag, 15. August 2021 um 09:06:51 UTC+2:
>
>>
>> Links etc... here in this thread please
>> On Sunday, 15 August 2021 at 08:55:13 UTC+10 flanc...@gmail.com wrote:
>>
>>> *What's New?*
>>>
>>> New language features:
>>>
>>>- auto switch when TW language switched (opt-in on plugin settings)
>>>- more settings, such as continuous listening option!
>>>- Loads of more languages!
>>>- minor BUG fixes
>>>- and lots more!
>>>
>>>

-- 
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/e9489b92-da85-4199-9efd-13e71e5c0271n%40googlegroups.com.

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

[TW Tones]

Misterel

Joshua does a great technical explanation here, and Mario gives the 
standard solution.

   - The spacing you wish is something best done in the display of the data 
   and not in the data, what if they changed order? 
   - A field containing a list of titles or tiddlers is typically space 
   delimited. So we often need the leading and trailing spaces not to be 
   included.
   - Create a new tiddler and give it leading and ending spaces and you 
   will see how these end up trimmed and do not become part of the title.
   - You can access fields in a different way if you really need to have 
   leading or training spaces as part of the data
   - Transcluding not only brings the fields value, in but what follows is 
   it is rendered, I believe this is when the spaces are trimmed.

Try
'<$transclude field=afield/>' or '{{!!afield}}'
'{{{ [all[current]get[afield]] }}}'

The transcluded filter output demonstrates the field contains a leading 
space of it has one.

Regards
Tones
On Sunday, 15 August 2021 at 06:28:56 UTC+10 Misterel85 wrote:

> How can I prevent TW from trimming leading space in field transclusion?
>
> When transcludings two fields one after the other, for instance:
>
> `<$transclude field="foo" /><$transclude field="bar" />`
>
> if the value of field "bar" starts with a space, that space is 
> automatically removed in the transclusion.
>
> In this example the successive transclusions of:
>
> "foo"=> "This is foo"
> "bar"=> " and this is bar."
>
> render as:
>
> "This is fooand this is bar."
>
> Inserting a trailing space in "foo" or a `` between the two 
> transclusions is not an option for me.
> Placing a `` at the beginning of the value in the second transcluded 
> field works, but that's a bit of a hassle with multiple transclusions.
>
> Why does TW behave so and what is needed to achieve the result I am 
> looking for (a kind of 'untrim' operator)? 
>
> Sorry if that question seems trivial or was already asked before.
>
> -Stéphane L.
>

-- 
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/0fb97f65-5446-478a-9665-075f82789aa0n%40googlegroups.com.

[tw5] Re: Speech-to-Text v1.0.5 is here!

[BurningTreeC]

The Link to the GitHub project page 
https://github.com/flancast90/Speech-To-Text-in-TW5

The Link to the Demo page https://speech-to-text.finnsoftware.net/

TW Tones schrieb am Sonntag, 15. August 2021 um 09:06:51 UTC+2:

>
> Links etc... here in this thread please
> On Sunday, 15 August 2021 at 08:55:13 UTC+10 flanc...@gmail.com wrote:
>
>> *What's New?*
>>
>> New language features:
>>
>>- auto switch when TW language switched (opt-in on plugin settings)
>>- more settings, such as continuous listening option!
>>- Loads of more languages!
>>- minor BUG fixes
>>- and lots more!
>>
>>

-- 
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/14f4da98-64f9-464c-b721-71ed0912e271n%40googlegroups.com.

[tw5] Re: Speech-to-Text v1.0.5 is here!

[BurningTreeC]

The Link to the GitHub project page 
https://github.com/flancast90/Speech-To-Text-in-TW5/graphs/traffic

The Link to the Demo page https://speech-to-text.finnsoftware.net/

TW Tones schrieb am Sonntag, 15. August 2021 um 09:06:51 UTC+2:

>
> Links etc... here in this thread please
> On Sunday, 15 August 2021 at 08:55:13 UTC+10 flanc...@gmail.com wrote:
>
>> *What's New?*
>>
>> New language features:
>>
>>- auto switch when TW language switched (opt-in on plugin settings)
>>- more settings, such as continuous listening option!
>>- Loads of more languages!
>>- minor BUG fixes
>>- and lots more!
>>
>>

-- 
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/e66fedb2-0391-47d6-9583-ad4cbd55b979n%40googlegroups.com.

[tw5] Re: Speech-to-Text v1.0.5 is here!

[TW Tones]

Links etc... here in this thread please
On Sunday, 15 August 2021 at 08:55:13 UTC+10 flanc...@gmail.com wrote:

> *What's New?*
>
> New language features:
>
>- auto switch when TW language switched (opt-in on plugin settings)
>- more settings, such as continuous listening option!
>- Loads of more languages!
>- minor BUG fixes
>- and lots more!
>
>

-- 
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/d61f883f-9875-4fc1-84f3-702c177033b1n%40googlegroups.com.