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

[BurningTreeC]

... And *custom VoiceCommands* are possible!

Create a tiddler tagged *$:/tags/VoiceCommand*
Fill its text field with your desired actions
Use the field *voice-commands *to add a list of commands that should 
trigger the actions



flanc...@gmail.com schrieb am Sonntag, 15. August 2021 um 00:55:13 UTC+2:

> *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/16189e10-88f5-41d3-b1ff-0e94f85c9740n%40googlegroups.com.

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

[Joshua Fontany]

Hi Misterel85,

This behaviour is found 
in https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Fwidgets%2Ftransclude.js


```
/*\
title: $:/core/modules/widgets/transclude.js
type: application/javascript
module-type: widget

Transclude widget \*/
...
var parser = this.wiki.parseTextReference( this.transcludeTitle, 
this.transcludeField, this.transcludeIndex, { parseAsInline: parseAsInline, 
subTiddler: this.transcludeSubTiddler })
...
```

And we can lookup the `wiki.parseTextReference` method 
here: https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Fwiki.js

and see that it uses the `parseText' method. This means we actually need to 
look at the *$:/core/modules/parsers/wikiparser/wikiparser.js* module, 
where we find:

```
/*
Push a text widget onto an array, respecting the configTrimWhiteSpace 
setting
*/
WikiParser.prototype.pushTextWidget = function(array,text) {
if(this.configTrimWhiteSpace) {
text = $tw.utils.trim(text);
}
if(text) {
array.push({type: "text", text: text}); 
}
};
```
Now we are getting somewhere. Searching the system tiddler for 
*configTrimWhiteSpace* gives us 
*$:/core/modules/parsers/wikiparser/rules/whitespace.js*

Where we see the 2 pragma defined as:
```
\whitespace trim
\whitespace notrim
```

AHA!

Now we know that if we put the "pragma" of `\whitespace notrim` at the very 
beginning of any Tiddler's text field, then all parsers in that tiddler 
will not trim whitespace when parsing text.

Try *\whitespace notrim* before your other wikitext.

Best,
Joshua Fontany

On Saturday, August 14, 2021 at 1:28:56 PM UTC-7 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/a77cfb02-7841-438f-89fa-463643fe2a8bn%40googlegroups.com.

[tw5] Re: Highlighting duplicates in lists

[paulgilbert2000]

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 performance. There are other "algorithms you 
 can deploy" if you describe the full problem, especially if you can share 
 test data.

 The thing is, what you want to achieve could be addressed more 
 efficiently with better knowledge of the input data(set), and ensuring 
 that 
 data is arranged appropriately. Over in the aforementioned  github item 
 https://github.com/Jermolene/TiddlyWiki5/discussions/5925 I think a 
 solution may be a *report widget* designed for most reporting 
 requirements ie beyond the list widget features. However even in this case 
 you will need to give further thought on y

[tw5] Re: System and shadow need some love

[springer]

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/1b1bd8d9-c618-4770-87b5-92febe146e6cn%40googlegroups.com.

Re: [tw5] Re: Better indexes through semantic modeling

[Joshua Fontany]

Good discussion. I have been experimenting with dynamically generating 
Indexes from individual Tiddlers in my Martial-Arts wiki.

https://silat.chronicles.wiki/#Glossary

I had to set that aside for my real-time multiplayer experiments, but hope 
to get back to UI work soon.

Best,
Joshua Fontany

On Friday, August 13, 2021 at 9:21:46 AM UTC-7 springer wrote:

> Ah, I believe that techniques like "extracting introductions" might even 
> have developed in tandem with a need I had, way back -- to have a list of 
> "quick definitions" that displayed only the title and first line of each 
> definition-tagged tiddler while dropping any further content of text field 
> (examples, discussion). That technique started back in TW Classic days, 
> though, before we *had* such powerful use of fields!
>
> Mostly I'm leaning toward using fields now for any kind of structured info 
> (such as summary), and transcluding those fields (or using distinctive 
> ViewTemplate sections) as needed. 
>
> Still, there's something to be said for the writing practice of crafting 
> the first line of an entry to serve as a helpful summary (often revised 
> after writing out the actual content). For certain use-cases, that kind of 
> discipline helps both readers and writers, and of course it's especially 
> compatible with off-the-shelf search behavior.
>
> -Springer
> On Friday, August 13, 2021 at 12:08:24 PM UTC-4 Mohammad wrote:
>
>> Hi Springer!
>> The conditional summary needs a summary field! This is what Soren 
>> explained and is a good approach!
>>
>> I mean Extracting Introduction From Tiddlers: 
>> https://tobibeer.github.io/tb5/#Extracting%20Introductions%20From%20Tiddlers
>> It lets you use the same standard searchbox!
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Fri, Aug 13, 2021 at 8:31 PM springer  wrote:
>>
>>> Mohammad, By "Tobias Beer's method" do you mean the one here:
>>> https://tobibeer.github.io/tb5/#Conditional%20Summary
>>> ?
>>>
>>> That's quite similar to what I use. In fact, I like to create visually 
>>> distinctive ViewTemplate sections for various fields, iff the fields are 
>>> populated. Since I often use tiddlers to hold excerpts, and want to put 
>>> nothing in the text there field apart from the excerpt itself, a 
>>> conditional view template for the "notes" field --  displaying in a 
>>> contrasting box below the text content if and only if I've added notes -- 
>>> was the first such field-based auto-include that I found indispensable. 
>>>
>>> -Springer
>>>
>>> On Friday, August 13, 2021 at 7:43:09 AM UTC-4 Mohammad wrote:
>>>
 Springer


 On Thu, Aug 12, 2021 at 4:01 AM springer  wrote:

> Soren,
>
> In your "better indexes" essay you write:
> If we do have the full text included in each locus, we may want to 
> write a summary anyway and store it along with the full text: this way, 
> we’ll be able to create an outline later and more easily see what parts 
> of 
> the document we’re hopping between.
>
> And it reminds me how certain enlightenment texts were printed with a 
> running outer-margin summary distilling key points (and of course the 
> cognitive work of spelling out those side-notes is considerable!). For 
> example, see the side-notes starting at p 49 (pdf-pagination) on this 
> Adam 
> Smith manuscript: 
> https://oll-resources.s3.us-east-2.amazonaws.com/oll3/store/titles/237/0206-01_Bk.pdf
>
> For some tiddlywiki projects, I've started to employ a super-condensed 
> summary field (call it, say, the tldr field) that can be displayed for 
> certain purposes. Unlike the main body of the tiddler, the tldr is 
> text-only, maximum of a single sentence. (And if I can't summarize the 
> tiddler in one sentence, then it needs to be more than one tiddler. ;) ) 
> Of 
> course, the fact that tw's standard search interface doesn't peek beyond 
> title and text field means this solution requires some building-around to 
> be useful. 
>

 I would recommend Tobias Beer method for creating a description, 
 Summary!
 Also in kookma utility there is a find macro (it has been published 
 separately, see find macro in kookma GitHub page) which can simply extract 
 the summary/description part and you can still use the standard 
 searchbox by Tiddlywiki


  

>
> Overall, I'm enjoying your essay and its questions!
>
> -Springer
> On Monday, August 9, 2021 at 9:17:00 PM UTC-4 Soren Bjornstad wrote:
>
>> Some of you all might be interested in this new post on my blog:
>>
>>
>> https://controlaltbackspace.org/notes/better-indexes-through-semantic-modeling/
>>
>> It's a proposal for a system for indexing large documents based on a 
>> hypertext graph, including a discussion of a possible TiddlyWiki 
>> prototype. 
>> Warning: 6,000+ words.
>>
> -- 
>
 You rec

[tw5] Re: Timely help needed

[paulgilbert2000]

 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/ef88c1eb-2ceb-4dfa-ad53-b83e1d5f3951n%40googlegroups.com.

[tw5] Re: Timely help needed

[paulgilbert2000]

Hey,

i have a similar setup , not sure if this helps , but check this thread 
https://groups.google.com/g/tiddlywiki/c/uB1RxGj2qz0/m/QYjk6VO_AwAJ?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/OUJlcbbK5v0/m/Wpc2SWMWAgAJ?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/767b0fba-0ab9-4f36-9b7d-c60bc6d81fe6n%40googlegroups.com.

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

[Finn Lancaster]

*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/99e35ff8-0ee8-4cbe-99f0-b3cc2722edddn%40googlegroups.com.

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

[PMario]

Hi,

Try this: <$transclude field="foo" /> <$transclude field="bar" /> 

See the red space! It should do the trick
-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/c8150fa7-a1d4-46c8-a257-d04b75dbeda9n%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[Charlie Veniot]

Woohoo !

All is working A-1.  Thank-you very much for your help !

I got rid of the wonky tiddler likely created while in the midst of coding 
a new-tiddler action widget.

I also replaced my on startup "context-setting" javascript macro with some 
native TW code to do the job, which makes me a much happier camper.

Cheers !

On Saturday, August 14, 2021 at 5:03:07 PM UTC-3 PMario wrote:

> On Saturday, August 14, 2021 at 9:30:58 PM UTC+2 PMario wrote:
>
>> You have a very strange tiddler title, that start with: <$vars 
>> vWorkingTid .   It seems to cause a problem with the node.js syncer. 
>> ... No tiddlers are saved. ... I did disable it at import so all tiddlers 
>> seemed to be created ... But .. see next issue ;)
>>
>
> It seems the prerelease can handle this strange tiddler name. .. That's a 
> good thing :)
>
> have fun!
> over and out ;)
> 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/61384f67-a098-4e92-aefe-67da9e97a7dan%40googlegroups.com.

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

[Misterel85]

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/22f3a526-db90-40e8-8378-da60676512b7n%40googlegroups.com.

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

[S²]

Hello Eric,

thanks for the new macro, but I have no idea, how to assign it  :-(
Regards
Stefan
Eric Shulman schrieb am Freitag, 13. August 2021 um 23:53:09 UTC+2:

> 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/ef8c8168-53d5-41ef-b017-1a5c37f22292n%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[PMario]

On Saturday, August 14, 2021 at 9:30:58 PM UTC+2 PMario wrote:

> You have a very strange tiddler title, that start with: <$vars vWorkingTid 
> .   It seems to cause a problem with the node.js syncer. ... No 
> tiddlers are saved. ... I did disable it at import so all tiddlers seemed 
> to be created ... But .. see next issue ;)
>

It seems the prerelease can handle this strange tiddler name. .. That's a 
good thing :)

have fun!
over and out ;)
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/8c305fe8-6a23-4a68-889b-26999a617314n%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[PMario]

I'm not really sure, what the macro does, but if the .run function would 
look like this: 

exports.run = function() {
if ($tw.browser) {
const queryString = window.location.search;
try {
const urlParams = new URLSearchParams(queryString);
const wikicontext = urlParams.get('context');
var output = wikicontext;

if ( (output !== "OffGridding") && (output !== "HydroCutting"
)  && (output !== "Chromebook") ){
output = "ProductReviews";
};
document.title = output;
}
catch(err) {
output = "ProductReviews";
}
return output;
}
};

It will let the server start in a normal way. .. 

-mario

On Saturday, August 14, 2021 at 9:48:25 PM UTC+2 PMario wrote:

> Hi,
> Yea, if those 2 tiddlers are removed it works. ... Will have a closer look 
> at the macro. ... 
> -m
>
> On Saturday, August 14, 2021 at 9:45:19 PM UTC+2 PMario wrote:
>
>> On Saturday, August 14, 2021 at 9:35:11 PM UTC+2 cj.v...@gmail.com wrote:
>>
>>> getstartupcontext.js, that I can get rid of going forward.
>>>
>>> If you want, delete that tiddler from the process.
>>>
>>
>> It's astonishing that this mechanism works. ... Where did you get this 
>> implementation from?
>> The mechanism in "Set Startup Context" is completely new to me. ... And 
>> it seems to cause a problem in the server because it references the 
>> "window" object, which is only available in the browser. ... 
>>
>> So IMO there would only be a if($tw.browser) needed. ... Maybe
>>
>> -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/f7e852a3-f28c-4dfc-83f0-20d912f1c1c9n%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[Charlie Veniot]

Please don't spend too much of your time on that macro.

That was very early going when I couldn't figure out a way to accomplish 
the same thing with just native TW code.

I am no fan of javascript, so quite happy to send that js code to the 
dustbin.

Maybe not tonight.  Bad thunderstorm going on over here, and the lights are 
flickering something silly...

On Saturday, August 14, 2021 at 4:48:25 PM UTC-3 PMario wrote:

> Hi,
> Yea, if those 2 tiddlers are removed it works. ... Will have a closer look 
> at the macro. ... 
> -m
>
> On Saturday, August 14, 2021 at 9:45:19 PM UTC+2 PMario wrote:
>
>> On Saturday, August 14, 2021 at 9:35:11 PM UTC+2 cj.v...@gmail.com wrote:
>>
>>> getstartupcontext.js, that I can get rid of going forward.
>>>
>>> If you want, delete that tiddler from the process.
>>>
>>
>> It's astonishing that this mechanism works. ... Where did you get this 
>> implementation from?
>> The mechanism in "Set Startup Context" is completely new to me. ... And 
>> it seems to cause a problem in the server because it references the 
>> "window" object, which is only available in the browser. ... 
>>
>> So IMO there would only be a if($tw.browser) needed. ... Maybe
>>
>> -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/0205b2b2-d853-408b-8a29-440315f24818n%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[PMario]

Hi,
Yea, if those 2 tiddlers are removed it works. ... Will have a closer look 
at the macro. ... 
-m

On Saturday, August 14, 2021 at 9:45:19 PM UTC+2 PMario wrote:

> On Saturday, August 14, 2021 at 9:35:11 PM UTC+2 cj.v...@gmail.com wrote:
>
>> getstartupcontext.js, that I can get rid of going forward.
>>
>> If you want, delete that tiddler from the process.
>>
>
> It's astonishing that this mechanism works. ... Where did you get this 
> implementation from?
> The mechanism in "Set Startup Context" is completely new to me. ... And it 
> seems to cause a problem in the server because it references the "window" 
> object, which is only available in the browser. ... 
>
> So IMO there would only be a if($tw.browser) needed. ... Maybe
>
> -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/80452021-13b9-4598-9be0-6a4037489f3an%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[PMario]

On Saturday, August 14, 2021 at 9:35:11 PM UTC+2 cj.v...@gmail.com wrote:

> getstartupcontext.js, that I can get rid of going forward.
>
> If you want, delete that tiddler from the process.
>

It's astonishing that this mechanism works. ... Where did you get this 
implementation from?
The mechanism in "Set Startup Context" is completely new to me. ... And it 
seems to cause a problem in the server because it references the "window" 
object, which is only available in the browser. ... 

So IMO there would only be a if($tw.browser) needed. ... Maybe

-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/ce7070b2-c6f6-4560-9f17-35c8efe33512n%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[Charlie Veniot]

And that "<$vars vWorking Tid..." tiddler, that's definitely something I 
created by mistake while in the process of creating an action widget.

I think.  I can't explain that tiddler.

On Saturday, August 14, 2021 at 4:30:58 PM UTC-3 PMario wrote:

> You have a very strange tiddler title, that start with: <$vars vWorkingTid 
> .   It seems to cause a problem with the node.js syncer. ... No 
> tiddlers are saved. ... I did disable it at import so all tiddlers seemed 
> to be created ... But .. see next issue ;)
>
> And there seems to be a getstartupcontext.js macro that I don't know. ... 
> It causes a problem at server startup.
>
> I'll investigate further and let you know. 
>
> -m
>
> On Saturday, August 14, 2021 at 8:54:15 PM UTC+2 cj.v...@gmail.com wrote:
>
>> Hi,
>>
>> version 5.1.23
>>
>> Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?
>>
>> On Saturday, August 14, 2021 at 3:39:14 PM UTC-3 PMario wrote:
>>
>>> Hi, 
>>> Which TW server version do you use?
>>>
>>> tiddlywiki --version   will show it. 
>>>
>>> -m
>>>
>>> On Saturday, August 14, 2021 at 7:36:45 PM UTC+2 cj.v...@gmail.com 
>>> wrote:
>>>
 Hello all,

 I was under the impression that the html file for a single-file 
 TiddlyWiki could simply be dragged to the node.js TiddlyWiki for importing.

 Having tried this with two different single-file TiddlyWikis, the 
 node.js TiddlyWiki (i.e. a clean/unmodified new TiddlyWiki instance) 
 cannot 
 be restarted after the import, getting all kinds of errors that seem 
 javascript related.

 Using this single-file TiddlyWiki 
  
 as the case study, what's the process to successfully import that 
 TiddlyWiki's tiddlers into a new and unmodified TiddlyWiki running on 
 node.js ?

 And are there other process steps to consider that may not need to be 
 considered in this particular example TiddlyWiki ?

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/422f7315-95c5-46dd-9755-341b0573be3dn%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[Charlie Veniot]

getstartupcontext.js, that I can get rid of going forward.

If you want, delete that tiddler from the process.

On Saturday, August 14, 2021 at 4:30:58 PM UTC-3 PMario wrote:

> You have a very strange tiddler title, that start with: <$vars vWorkingTid 
> .   It seems to cause a problem with the node.js syncer. ... No 
> tiddlers are saved. ... I did disable it at import so all tiddlers seemed 
> to be created ... But .. see next issue ;)
>
> And there seems to be a getstartupcontext.js macro that I don't know. ... 
> It causes a problem at server startup.
>
> I'll investigate further and let you know. 
>
> -m
>
> On Saturday, August 14, 2021 at 8:54:15 PM UTC+2 cj.v...@gmail.com wrote:
>
>> Hi,
>>
>> version 5.1.23
>>
>> Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?
>>
>> On Saturday, August 14, 2021 at 3:39:14 PM UTC-3 PMario wrote:
>>
>>> Hi, 
>>> Which TW server version do you use?
>>>
>>> tiddlywiki --version   will show it. 
>>>
>>> -m
>>>
>>> On Saturday, August 14, 2021 at 7:36:45 PM UTC+2 cj.v...@gmail.com 
>>> wrote:
>>>
 Hello all,

 I was under the impression that the html file for a single-file 
 TiddlyWiki could simply be dragged to the node.js TiddlyWiki for importing.

 Having tried this with two different single-file TiddlyWikis, the 
 node.js TiddlyWiki (i.e. a clean/unmodified new TiddlyWiki instance) 
 cannot 
 be restarted after the import, getting all kinds of errors that seem 
 javascript related.

 Using this single-file TiddlyWiki 
  
 as the case study, what's the process to successfully import that 
 TiddlyWiki's tiddlers into a new and unmodified TiddlyWiki running on 
 node.js ?

 And are there other process steps to consider that may not need to be 
 considered in this particular example TiddlyWiki ?

>>>

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

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[PMario]

You have a very strange tiddler title, that start with: <$vars vWorkingTid 
.   It seems to cause a problem with the node.js syncer. ... No 
tiddlers are saved. ... I did disable it at import so all tiddlers seemed 
to be created ... But .. see next issue ;)

And there seems to be a getstartupcontext.js macro that I don't know. ... 
It causes a problem at server startup.

I'll investigate further and let you know. 

-m

On Saturday, August 14, 2021 at 8:54:15 PM UTC+2 cj.v...@gmail.com wrote:

> Hi,
>
> version 5.1.23
>
> Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?
>
> On Saturday, August 14, 2021 at 3:39:14 PM UTC-3 PMario wrote:
>
>> Hi, 
>> Which TW server version do you use?
>>
>> tiddlywiki --version   will show it. 
>>
>> -m
>>
>> On Saturday, August 14, 2021 at 7:36:45 PM UTC+2 cj.v...@gmail.com wrote:
>>
>>> Hello all,
>>>
>>> I was under the impression that the html file for a single-file 
>>> TiddlyWiki could simply be dragged to the node.js TiddlyWiki for importing.
>>>
>>> Having tried this with two different single-file TiddlyWikis, the 
>>> node.js TiddlyWiki (i.e. a clean/unmodified new TiddlyWiki instance) cannot 
>>> be restarted after the import, getting all kinds of errors that seem 
>>> javascript related.
>>>
>>> Using this single-file TiddlyWiki 
>>>  
>>> as the case study, what's the process to successfully import that 
>>> TiddlyWiki's tiddlers into a new and unmodified TiddlyWiki running on 
>>> node.js ?
>>>
>>> And are there other process steps to consider that may not need to be 
>>> considered in this particular example TiddlyWiki ?
>>>
>>

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

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[Charlie Veniot]

If it matters any: version of node is 10.24.0

On Saturday, August 14, 2021 at 4:22:25 PM UTC-3 PMario wrote:

> On Saturday, August 14, 2021 at 8:54:15 PM UTC+2 cj.v...@gmail.com wrote:
>
>> version 5.1.23
>>
>> Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?
>>
>
> No. ... I did test it with the prerelease and it worked without a problem. 
> I'll test it with 5.1.23 again.
> -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/77d57c95-897c-4d2d-930c-1db1fb6159c6n%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[PMario]

On Saturday, August 14, 2021 at 8:54:15 PM UTC+2 cj.v...@gmail.com wrote:

> version 5.1.23
>
> Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?
>

No. ... I did test it with the prerelease and it worked without a problem. 
I'll test it with 5.1.23 again.
-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/8e339f6f-27a0-400b-97cd-ef2c15dac7f7n%40googlegroups.com.

Re: [tw5] Re: System and shadow need some love

[PMario]

On Saturday, August 14, 2021 at 7:19:53 PM UTC+2 Stobot wrote:

> I agree that the other forms of search could be made a bit more 
> convenient, though I've gone back and forth on the best way to solve it. 
> For a few years I did what has been suggested, break the other options down 
> into tabs. As a minimalist though, nowadays I instead built a "smarter" 
> search bar that looks at the first character and changes search type 
> accordingly. I just opened the code for AdvancedSearch and copy pasted it 
> all into one search area. Now if my search bar starts with the:
>
>- "[" character it acts like I'm in the filter area
>- "$" character it acts like I'm in the system area
>- "!" character it acts like I'm in the shadow area
>- else, treats as a regular search
>
> That's a nice idea. I like it!
 

>
>- S - Search: Where I house the "smart" search bar.
>- O - Open: I just transclude the normal open sidebar tab
>- R - Recent: I just transclude the normal recent tab (though like the 
>idea below of separating / including system tiddlers!)
>- T - Tags: Kind of a mashup of the tags area, and some kind of global 
>table of contents - still a work-in-process. 
>
> Lots of CSS still to figure out (really not my strong suit), but I like 
> the way it's coming together. I aim to pair this with some introductory 
> videos etc. linking it to how to use it along-side other Office 
> applications like Outlook, Excel, etc. 
> [image: image.png]
> Anyways, sorry if that branches off too hard from your post David, but 
> just adding thoughts. 
>

That's pretty. I'm looking forward to that theme. If you need help, just 
let me know. 

-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/8caf029a-d7a5-4177-8136-e92ad0eb6bd1n%40googlegroups.com.

[tw5] Re: System and shadow need some love

[PMario]

On Saturday, August 14, 2021 at 4:01:54 PM UTC+2 David Gifford wrote:

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

I think this should be possible. ... The whole search behaviour has grown 
organically. I think nobody requested it in a reasonable interesting way. 
... I personally did create the advanced-search-plus (ASP) plugin, which 
perfectly fits my needs. .. So I don't have the desire to create new stuff 
as long as the existing behaviour is "just good enough" ;)
 

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

That was 1 reason, why I did create ASP plugin. 

 

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

IMO Nobody requested it. But it seems to make sense. 
 

> I would love to hear your input: 
> Do you agree with me?
>

yes
 

> Why or why not? If so, should this be core pull request or a plugin? 
>

hmmm, That's a difficult question. ... You are a very advanced user 
already. So your desire IMO is very different to novice users. 
 

> What are the reasons $:/AdvancedSearch is set up backwards?
>

It has been implemented that way and it did make sense. I think nobody 
questioned it since now.
 

> Technical limitations? Workflow-related?
>

No ... It was developed that way and it worked. ... just good enough ;)
 

> What are the ways you work around these limitations?
>

As I wrote: advanced search plus plugin 
. ... There is a 
video on the plugin page. In combination with the "link-to-tabs" plugin it 
solves all my dev needs. 

have fun!
mario
 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0573053e-f885-46fa-8c93-89a4ee5410cdn%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[Charlie Veniot]

Hi,

version 5.1.23

Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?

On Saturday, August 14, 2021 at 3:39:14 PM UTC-3 PMario wrote:

> Hi, 
> Which TW server version do you use?
>
> tiddlywiki --version   will show it. 
>
> -m
>
> On Saturday, August 14, 2021 at 7:36:45 PM UTC+2 cj.v...@gmail.com wrote:
>
>> Hello all,
>>
>> I was under the impression that the html file for a single-file 
>> TiddlyWiki could simply be dragged to the node.js TiddlyWiki for importing.
>>
>> Having tried this with two different single-file TiddlyWikis, the node.js 
>> TiddlyWiki (i.e. a clean/unmodified new TiddlyWiki instance) cannot be 
>> restarted after the import, getting all kinds of errors that seem 
>> javascript related.
>>
>> Using this single-file TiddlyWiki 
>>  
>> as the case study, what's the process to successfully import that 
>> TiddlyWiki's tiddlers into a new and unmodified TiddlyWiki running on 
>> node.js ?
>>
>> And are there other process steps to consider that may not need to be 
>> considered in this particular example TiddlyWiki ?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2f2c7afb-80e2-46ab-8ba7-fc0c999ac80fn%40googlegroups.com.

[tw5] Re: What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[PMario]

Hi, 
Which TW server version do you use?

tiddlywiki --version   will show it. 

-m

On Saturday, August 14, 2021 at 7:36:45 PM UTC+2 cj.v...@gmail.com wrote:

> Hello all,
>
> I was under the impression that the html file for a single-file TiddlyWiki 
> could simply be dragged to the node.js TiddlyWiki for importing.
>
> Having tried this with two different single-file TiddlyWikis, the node.js 
> TiddlyWiki (i.e. a clean/unmodified new TiddlyWiki instance) cannot be 
> restarted after the import, getting all kinds of errors that seem 
> javascript related.
>
> Using this single-file TiddlyWiki 
>  
> as the case study, what's the process to successfully import that 
> TiddlyWiki's tiddlers into a new and unmodified TiddlyWiki running on 
> node.js ?
>
> And are there other process steps to consider that may not need to be 
> considered in this particular example TiddlyWiki ?
>

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

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

[cmari]

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/d907a01f-a345-475a-b627-619c204575b8n%40googlegroups.com.

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

[noa@noanoa.space]

Thank you for the help! i’ve actually just discovered that TiddlyMaps does an 
even better version of what I’m after, so I think I’ll try using that. (:

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

[tw5] What's the process for moving a single-file TiddlyWiki to a TiddlyWiki on node.js?

[Charlie Veniot]

Hello all,

I was under the impression that the html file for a single-file TiddlyWiki 
could simply be dragged to the node.js TiddlyWiki for importing.

Having tried this with two different single-file TiddlyWikis, the node.js 
TiddlyWiki (i.e. a clean/unmodified new TiddlyWiki instance) cannot be 
restarted after the import, getting all kinds of errors that seem 
javascript related.

Using this single-file TiddlyWiki 
 
as the case study, what's the process to successfully import that 
TiddlyWiki's tiddlers into a new and unmodified TiddlyWiki running on 
node.js ?

And are there other process steps to consider that may not need to be 
considered in this particular example TiddlyWiki ?

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

Re: [tw5] Re: Parameters into macros

[Saq Imtiaz]

Feel free to post here with your filter code (and of the macro) if you get 
stuck.

On Saturday, August 14, 2021 at 7:24:06 PM UTC+2 Stobot wrote:

> Thanks Saq, actually that sounds like an interesting challenge. From a 
> Javascript standpoint all I've done is tweak the macros of others so it may 
> be a bit over my head, but I'll give it a try. 
>
> On Sat, Aug 14, 2021 at 1:04 PM Saq Imtiaz  wrote:
>
>> The first thing that comes to mind is rewriting the macro as a filter 
>> operator.
>>
>>
>>
>> On Saturday, August 14, 2021 at 6:54:22 PM UTC+2 Stobot wrote:
>>
>>> Is there a way to pass dynamic parameters into macros (javascript) other 
>>> than using <$macrocall/>? 
>>>
>>> For instance I use a modified version of (Jed's I think) add-time.js 
>>> that allows you to use a parameter 'days' to feed days to add to current 
>>> date. So, doing something like <> would return the date 
>>> 10 days from now. If it's a static number like 10, things are easy, but if 
>>> it's dynamic (stored in a field) then things get more complicated - I have 
>>> to use the <$macrocall/> instead, which is less convenient but sometimes 
>>> not a problem. 
>>>
>>> It becomes a problem when I need to use this new date in a filter. I 
>>> *am* excited that in pre-release now we can feed *static* values as 
>>> parameters into macros within filters, but the missing piece is still 
>>> dynamic values as parameters - can't do a <$macrocall/> within a filter. 
>>>
>>> If it's a normal macro, right now I'd surround the <$list/> with some 
>>> <$wikify> runs that run the <$macrocall/>'s and wikify it to be fed in as a 
>>> static value. I'm just wondering if there's a better way that I'm not 
>>> thinking about (I end up with LOTS of wikify's which people tell me is not 
>>> great). 
>>>
>>> For instance, doing something like:
>>>  <$vars days={{!!daystoadd}}><$list 
>>> filter="[duedate]"> would work if it was a regular 
>>> macro instead of a javascript macro. But, even though the parameter that 
>>>  can be fed is called days, it's not picked up by the macro call. 
>>>
>>> Hopefully that makes sense - thanks
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/82fd0bc8-0322-4ef8-ba51-0b33342e8626n%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/2c8e661b-2c62-4f1e-b613-a536cb7ce005n%40googlegroups.com.

Re: [tw5] Re: Parameters into macros

[Adam Stobbe]

Thanks Saq, actually that sounds like an interesting challenge. From a
Javascript standpoint all I've done is tweak the macros of others so it may
be a bit over my head, but I'll give it a try.

On Sat, Aug 14, 2021 at 1:04 PM Saq Imtiaz  wrote:

> The first thing that comes to mind is rewriting the macro as a filter
> operator.
>
>
>
> On Saturday, August 14, 2021 at 6:54:22 PM UTC+2 Stobot wrote:
>
>> Is there a way to pass dynamic parameters into macros (javascript) other
>> than using <$macrocall/>?
>>
>> For instance I use a modified version of (Jed's I think) add-time.js that
>> allows you to use a parameter 'days' to feed days to add to current date.
>> So, doing something like <> would return the date 10 days
>> from now. If it's a static number like 10, things are easy, but if it's
>> dynamic (stored in a field) then things get more complicated - I have to
>> use the <$macrocall/> instead, which is less convenient but sometimes not a
>> problem.
>>
>> It becomes a problem when I need to use this new date in a filter. I *am*
>> excited that in pre-release now we can feed *static* values as parameters
>> into macros within filters, but the missing piece is still dynamic values
>> as parameters - can't do a <$macrocall/> within a filter.
>>
>> If it's a normal macro, right now I'd surround the <$list/> with some
>> <$wikify> runs that run the <$macrocall/>'s and wikify it to be fed in as a
>> static value. I'm just wondering if there's a better way that I'm not
>> thinking about (I end up with LOTS of wikify's which people tell me is not
>> great).
>>
>> For instance, doing something like:
>>  <$vars days={{!!daystoadd}}><$list
>> filter="[duedate]"> would work if it was a regular
>> macro instead of a javascript macro. But, even though the parameter that
>>  can be fed is called days, it's not picked up by the macro call.
>>
>> Hopefully that makes sense - thanks
>>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/82fd0bc8-0322-4ef8-ba51-0b33342e8626n%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/CA%2B%2B2uhHZddcXZBNebeRg4D1wid%2BNnQuO7X6NLg9Mka6f%3Dq%2BQHw%40mail.gmail.com.

Re: [tw5] Re: System and shadow need some love

[Adam Stobbe]

I agree that the other forms of search could be made a bit more convenient,
though I've gone back and forth on the best way to solve it. For a few
years I did what has been suggested, break the other options down into
tabs. As a minimalist though, nowadays I instead built a "smarter" search
bar that looks at the first character and changes search type accordingly.
I just opened the code for AdvancedSearch and copy pasted it all into one
search area. Now if my search bar starts with the:

   - "[" character it acts like I'm in the filter area
   - "$" character it acts like I'm in the system area
   - "!" character it acts like I'm in the shadow area
   - else, treats as a regular search

This kind of gets me to the same place, but is a little more keyboard
friendly. It also kind of hides the advanced functionality for those that
might be overwhelmed by it - until such time that they realize how valuable
it can be. I know I'm not the first to think of it - just mentioning it for
others who haven't thought that way.

On another topic related to the search functionality (and I bring up since
I mentioned greatly changing normal functionality), I like a persistent
results area (rather than the standard semi-transient default one). I'm
currently working on a theme/edition aimed at corporate Office workers like
myself (currently calling Officey) and am taking opportunities to make it
look/feel more like an Office365 web application to hopefully drive
adoption at my company. A quick example screenshot is below. I envision
there being 4 key ways of navigating content that happily have the acronym
SORT - so I can call it the SORT area. The components are dedicated tabs
for each:

   - S - Search: Where I house the "smart" search bar.
   - O - Open: I just transclude the normal open sidebar tab
   - R - Recent: I just transclude the normal recent tab (though like the
   idea below of separating / including system tiddlers!)
   - T - Tags: Kind of a mashup of the tags area, and some kind of global
   table of contents - still a work-in-process.

Lots of CSS still to figure out (really not my strong suit), but I like the
way it's coming together. I aim to pair this with some introductory videos
etc. linking it to how to use it along-side other Office applications like
Outlook, Excel, etc.
[image: image.png]
Anyways, sorry if that branches off too hard from your post David, but just
adding thoughts.

On Sat, Aug 14, 2021 at 10:17 AM ludwa6  wrote:

> Like you, @David : i rely heavily on $:/AdvancedSearch -but that is often
> a 2nd step, after i first 'dump the search term' into the default
> searchbar, i will then click the magnifier icon beside to look into the
> other tabs provided by #:/AdvancedSearch.  I guess this the search workflow
> on which the UI design is predicated; works well enough for an "advanced
> beginner" like myself (i.e. one who is usually looking for content, but
> does fairly often need to retrieve the code behind it), but for a bonafide
> developer like yourself, i can see how this 3-step workflow might be
> suboptimal.
>
> /walt
>
> On Saturday, August 14, 2021 at 3:01:54 PM UTC+1 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/8a1a656e-a676-449b-965b-f17876705c1cn%40googlegroups.com
> 

[tw5] Re: Parameters into macros

[Saq Imtiaz]

The first thing that comes to mind is rewriting the macro as a filter 
operator.



On Saturday, August 14, 2021 at 6:54:22 PM UTC+2 Stobot wrote:

> Is there a way to pass dynamic parameters into macros (javascript) other 
> than using <$macrocall/>? 
>
> For instance I use a modified version of (Jed's I think) add-time.js that 
> allows you to use a parameter 'days' to feed days to add to current date. 
> So, doing something like <> would return the date 10 days 
> from now. If it's a static number like 10, things are easy, but if it's 
> dynamic (stored in a field) then things get more complicated - I have to 
> use the <$macrocall/> instead, which is less convenient but sometimes not a 
> problem. 
>
> It becomes a problem when I need to use this new date in a filter. I *am* 
> excited that in pre-release now we can feed *static* values as parameters 
> into macros within filters, but the missing piece is still dynamic values 
> as parameters - can't do a <$macrocall/> within a filter. 
>
> If it's a normal macro, right now I'd surround the <$list/> with some 
> <$wikify> runs that run the <$macrocall/>'s and wikify it to be fed in as a 
> static value. I'm just wondering if there's a better way that I'm not 
> thinking about (I end up with LOTS of wikify's which people tell me is not 
> great). 
>
> For instance, doing something like:
>  <$vars days={{!!daystoadd}}><$list 
> filter="[duedate]"> would work if it was a regular 
> macro instead of a javascript macro. But, even though the parameter that 
>  can be fed is called days, it's not picked up by the macro call. 
>
> Hopefully that makes sense - thanks
>

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

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

[Saq Imtiaz]

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/58810d81-b325-426f-b065-35dd37eb2a83n%40googlegroups.com.

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

[Saq Imtiaz]

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/403ef6e8-2580-4497-811c-c498fd78n%40googlegroups.com.

[tw5] Parameters into macros

[Stobot]

Is there a way to pass dynamic parameters into macros (javascript) other 
than using <$macrocall/>? 

For instance I use a modified version of (Jed's I think) add-time.js that 
allows you to use a parameter 'days' to feed days to add to current date. 
So, doing something like <> would return the date 10 days 
from now. If it's a static number like 10, things are easy, but if it's 
dynamic (stored in a field) then things get more complicated - I have to 
use the <$macrocall/> instead, which is less convenient but sometimes not a 
problem. 

It becomes a problem when I need to use this new date in a filter. I *am* 
excited that in pre-release now we can feed *static* values as parameters 
into macros within filters, but the missing piece is still dynamic values 
as parameters - can't do a <$macrocall/> within a filter. 

If it's a normal macro, right now I'd surround the <$list/> with some 
<$wikify> runs that run the <$macrocall/>'s and wikify it to be fed in as a 
static value. I'm just wondering if there's a better way that I'm not 
thinking about (I end up with LOTS of wikify's which people tell me is not 
great). 

For instance, doing something like:
 <$vars days={{!!daystoadd}}><$list 
filter="[duedate]"> would work if it was a regular 
macro instead of a javascript macro. But, even though the parameter that 
 can be fed is called days, it's not picked up by the macro call. 

Hopefully that makes sense - thanks

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

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

[cmari]

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/6df911ec-6fed-45bd-b80b-aa889e09875dn%40googlegroups.com.

[tw5] Re: System and shadow need some love

[ludwa6]

Like you, @David : i rely heavily on $:/AdvancedSearch -but that is often a 
2nd step, after i first 'dump the search term' into the default searchbar, 
i will then click the magnifier icon beside to look into the other tabs 
provided by #:/AdvancedSearch.  I guess this the search workflow on which 
the UI design is predicated; works well enough for an "advanced beginner" 
like myself (i.e. one who is usually looking for content, but does fairly 
often need to retrieve the code behind it), but for a bonafide developer 
like yourself, i can see how this 3-step workflow might be suboptimal. 

/walt

On Saturday, August 14, 2021 at 3:01:54 PM UTC+1 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/8a1a656e-a676-449b-965b-f17876705c1cn%40googlegroups.com.

[tw5] Re: System and shadow need some love

[David Gifford]

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/ba5c752c-a302-4307-8c0a-b861d1af6442n%40googlegroups.com.

[tw5] System and shadow need some love

[David Gifford]

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/6b62bfc7-7439-4f86-8dba-f7ccfc340afdn%40googlegroups.com.

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

[Jeremy Ruston]

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
development in the areas of *Savers and Syncers* that has come out
of discussions around the Uploads plugin
- an update on the *Open Collective* model for funding TiddlyWiki
work and what we have learned from it thus far
- some news from Jeremy and Boris regarding improvements to
TiddlyWiki *community infrastructure*.

 I have been slowly working away on the TiddlyWiki file uploads plugin as
 was previously

[tw5] Re: !!! ''foo'' does not appear as bold

[PMario]

Hi,
I did test it at tiddlywiki.com and it does, what it should do. So there 
may be a problem with your stylesheets somewhere. 
-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/b1ba581a-586c-4b4f-8635-786c67c15431n%40googlegroups.com.

[tw5] !!! ''foo'' does not appear as bold

[Sapphireslinger]

The heading wikitext cancels out the bold wikitext.

I went to the control panel and looked through the palette editor but 
couldn't find anything to edit to keep the H1 and H2  and H3 (etc) buttons 
from interfering with the bold formatting. 

I am using Vanilla theme.

Thank you for any tips.

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

[tw5] How to turn off video auto-play?

[Sapphireslinger]

So I open a tiddler and all the videos contained in it all start playing at 
once. AAaagh! Even the ones embedded in Detail widgets. Is there some 
"do-not-autoplay" code I am missing?

For instance: one of my tiddlers contains both of these codes:



and 

<$list filter="[tag[video]]">  

The {{!!url}} just calls for a video file on my computer, the video is not 
actually in the tiddlywiki file.

Thanks in advance for any tips.

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

[tw5] Re: Help please for indicators in SideBar

[TW Tones]

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;
> display:inline-block;
> position:absolute;
> left:0;
> top:0;
> }
> Le jeudi 12 août 2021 à 02:42:42 UTC+2, TW Tones a écrit :
>
>> Folks,
>>
>> I have a number of projects that could use icons placed in the 
>> sidebar, top menu and other places. They would indicate some status such 
>> as 
>> a green storage icon when the local storage is on and much more. I call 
>> these indicators, They may have tooltips or actions on click, with or 
>> without modifier keys. 
>>
>> I have attempted to build a new element tagged $:/tags/SideBarSegment 
>> and list-before $:/core/ui/SideBarSegments/tabs
>>
>> The problem I have for for which I seek help is I am finding it 
>> difficult to reduce icons and buttons to a half height and not have 
>> unnecessary white space 

[tw5] Re: Presenting my plugin library

[TiddlyTweeter]

Ciao Andrew

Side comment. *It is lovely to see you have a plugin library!*
I have used several of your contributions with vigor and to continuous good 
effect over what is now years.

It is very nice to see you replenished stuff that continues to be useful! 

My very best wishes
TT

>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a06ec51d-2bba-4b7c-85d4-485e1fec3a6dn%40googlegroups.com.