Re: [tw5] [Discussion] Additional Tag handling feature(s)

[Mohammad Rahmani]

On Wed, May 5, 2021 at 9:01 AM TW Tones  wrote:

> Folks,


Tones

>
> From my systematic learnings from TiddlyWiki I need to ask if anyone has
> considered this Tag handling feature?
>
> I ask this openly because whilst I could "roll my own solution", it
> shoulds like a good case for updating the core tiddlers to respond if a
> variable is set containing "tag filter". So I wonder if someone has done
> this before or could help me do it.
>
> *Background*
> You may be aware the tag macro, the
> templates  {{||$:/core/ui/TagTemplate}} and
> {{||$:/core/ui/EditTemplate/tags}} and {{||$:/core/ui/ViewTemplate/tags}}
> all allow you to list or manipulate tags including with tag pills.
>
> *Extra flexibility *
> There are however times when such a "tool" would be helpful if the tags
> displayed or the tags available in the drop down could be restricted using
> a filter, or when using $:/core/ui/EditTemplate/tags suggests other
> tiddlers (not yet tags) as possible tags.
>

If we look at TW-Scripts, a very clever solution has been given by Eric
Shulman

https://kookma.github.io/TW-Scripts/#Hide%20Tags%20from%20Tagspill%20Drop%20down%20Menu



>
> What do you think?
> Tones
>
> --
> 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/1727aee7-990c-4d66-9879-8c22f5d136c1n%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/CAAV1gMBEK1P_FO8_H6K5v8dt8%2BHduHsMxcguFtLa%2BDLCQo-rsA%40mail.gmail.com.

[tw5] filter question: which tiddler is newer

[Mohammad Rahmani]

Back to winter 2019, when we were working on the Commander plugin we needed
a comparison between two tiddlers to see which is greater. See [1]
The best solution we found (by BTC) at that time was as below [2] (still
works and is part of Commander)


<$set name="tidBMod" value={{{ [[Bb]get[modified]] }}}>
<$set name="tidAMod" value={{{ [[Aa]get[modified]] }}}>
<$list filter="[] []
+[nsort[]last[1]removesuffix]">
Yes, Aa is newer

<$list filter="[] []
+[nsort[]last[1]removesuffix]">
No, Aa is older





With the advent of many new filter operator, I want to know if there is a
shorter and more semantic solution can be found today Apr 2021

I thought about the below solution and it works in TW 5.1.23

<$vars dtb={{{[[Bb]get[modified]]}}}>

<$list filter="[[Aa]get[modified]compare:integer:gtthen[Aa]else[Bb]]">
<> is newer!





But I am wondering if we could use :filter or some other operator to drop
the $vars and dtb and perform the comparison in single $list
Note Aa and Bb are two tiddlers



Best wishes
Mohammad

[1] https://groups.google.com/g/tiddlywiki/c/9QQvkJkLogA/m/3AGSBBJKBgAJ
[2] https://groups.google.com/g/tiddlywiki/c/9QQvkJkLogA/m/UbIgaSFSBgAJ

-- 
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/CAAV1gMBqP4fLS%2B-eSuxYo5m%3D1BPQFpWh44uVm1yfNEKHuB9MPQ%40mail.gmail.com.

[tw5] Re: Change the title of a tiddler from the tiddler itself?

[Mohammad]

On Thursday, April 29, 2021 at 3:47:05 AM UTC+4:30 PMario wrote:

> On Wednesday, April 28, 2021 at 9:26:25 PM UTC+2 si wrote:
>
>> Thank you very much Mario!
>
>
> You are welcome. 
>
> I think a button may make more sense anyway, but am I right to assume that 
>> it is not (easily) possible to have the title automatically update as I 
>> type?
>>
>
> Right. .. In TiddlyWiki the tiddlers are "immutable" [1]. They can't be 
> changed, after they have been created. There actually is _no_ function in 
> TW that says: Edit existing tiddler.
>

Is this true for other fields than title? I mean


   1.  if a new field is added to an existing tiddler? or
   2.  the value of a field is changed? or
   3. a new field is added?


or immutable only means changing the tiddler title?

 

>
>
> The only function to write to a tiddler is: $tw.wiki.addTiddler(...) 
> Adding a tiddler with the same title, will overwrite the existing one. 
> That's the only way to change a tiddler. 
>
> Let's say you have "New Tiddler" and you want to change it to "Faust - 
> Goethe". As soon as you start typing F .. you add tiddler F, then Fa, Fau, 
> Faus ... and so on.
>
>  - go to https://tiddlywiki.com
>  - create a new tiddler
>  - Copy this into a new tiddler: <$edit-text tiddler=<> 
> field=title />
>  - Save
>  - open the right sidebar : Recent tab   <- important
>  - start typing
>
> Nice - right?
>
> have fun!
> mario
> [1] https://en.wikipedia.org/wiki/Immutable_object
>
>
>

-- 
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/1ccaba3c-a2a3-4ae0-8ed5-8455ba243dfbn%40googlegroups.com.

[tw5] [Discussion] Additional Tag handling feature(s)

[TW Tones]

Folks,

>From my systematic learnings from TiddlyWiki I need to ask if anyone has 
considered this Tag handling feature? 

I ask this openly because whilst I could "roll my own solution", it shoulds 
like a good case for updating the core tiddlers to respond if a variable is 
set containing "tag filter". So I wonder if someone has done this before or 
could help me do it.

*Background*
You may be aware the tag macro, the templates  {{||$:/core/ui/TagTemplate}} 
and {{||$:/core/ui/EditTemplate/tags}} and 
{{||$:/core/ui/ViewTemplate/tags}}  all allow you to list or manipulate 
tags including with tag pills.

*Extra flexibility *
There are however times when such a "tool" would be helpful if the tags 
displayed or the tags available in the drop down could be restricted using 
a filter, or when using $:/core/ui/EditTemplate/tags suggests other 
tiddlers (not yet tags) as possible tags.

What do you think?
Tones

-- 
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/1727aee7-990c-4d66-9879-8c22f5d136c1n%40googlegroups.com.

Re: [tw5] A basket on the sidebar

[Mohammad Rahmani]

On Wed, May 5, 2021 at 7:01 AM James  wrote:

> Thanks for the great plugin.
> One quick question, is that possible to create sub-folder under the folder?
>

If you mean to have a outline tree like
-Folder
-- subF01
-- subF02

no, it is not possible! Favorites handle one two levels only: item in root
and item in folder

-- root
-- item
-- Folder
-- -- Item
-- -- Item



> On Tuesday, 4 May 2021 at 17:29:21 UTC+8 Mohammad wrote:
>
>> There was two mistakes in previous post I have corrected and attached
>> again the myBasket.json
>> - remove button tooltip corrected
>> - remove button now works
>>
>> Best wishes
>> Mohammad
>>
>> On Tue, May 4, 2021 at 11:22 AM Mohammad Rahmani 
>> wrote:
>>
>>> Hi Atro,
>>>
>>> Very nice question and a lot of use cases!!
>>>
>>> You get two solutions from Soren and Tones!
>>> The Soren solution implements a real basket !  Soren said it is* a lazy
>>> solution*! I want to see if I can be lazier! *;-)*
>>>
>>> *Third solution*
>>>
>>>1. Clone the Open tab in the sidebar ( $:/core/ui/SideBar/Open  )
>>>2. rename it to "myBasket"
>>>3. change the caption to Basek (I named it Atro Basket for
>>>*Atronoush*)
>>>4. make small change (e.g set the tv-story-list to myBasket to use
>>>it instead of TW tv-story-list)
>>>5. change close all to clear all to clear the list of myBasket
>>>6. add an export button to export tiddlers in basket (e.g listed in
>>>myBasket list field)
>>>7. make your button *draggable* (for example use dragFilter)
>>>
>>> *How it works*
>>>
>>>1. Open the Atro Basket in the sidebar  (see attached file)
>>>2. add items to Basket in different ways like below
>>>   1. drag and drop links, titles to Basket
>>>   2. drag a tag pill to add all tiddler with that tag
>>>   3. if you are not happy click *clear all* to remove all tiddlers
>>>   in basket
>>>   4. if you like remove any item click the *remove button*
>>>3. Export
>>>   1. click export button to export json (all tiddlers in the basket
>>>   as json) OR
>>>   2. drag and drop the export button to other wiki to import all
>>>   tiddlers in basket to your wiki  (your button is draggable)
>>>   3. when finished! if you like to empty the Basket, click clear all
>>>
>>>
>>> I have attached the working tiddler here! Drop into
>>> https://tiddlywiki.com/ and see how it works!
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Tue, May 4, 2021 at 1:38 AM Atronoush Parsi 
>>> wrote:
>>>
 Is there any script or plugin with

 - a sidebar tab (I call it basket)
 - drag and drop features! One can drag a tiddler (e.g title) into the
 basket
 - when finished press a button to export as JSON
 - the button can be dragged and drop into another wiki!

 The last part is what you see in TW-Icons


 -Atro

 --
 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/CAKHVXmoDHTtqMgUcp2ob%3DvHt6_nwBJbM2S4fOCi0gMraE3wEOA%40mail.gmail.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/ac7fec6e-7c0b-45e1-bdc6-322e24b5cfc3n%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/CAAV1gMB4ZTLfroXn82Qv7tbLyCMjiR0%2B02s1GLot3EfMHVU4kw%40mail.gmail.com.

Re: [tw5] A basket on the sidebar

[James]

Thanks for the great plugin.
One quick question, is that possible to create sub-folder under the folder?

On Tuesday, 4 May 2021 at 17:29:21 UTC+8 Mohammad wrote:

> There was two mistakes in previous post I have corrected and attached 
> again the myBasket.json
> - remove button tooltip corrected
> - remove button now works
>
> Best wishes
> Mohammad
>
> On Tue, May 4, 2021 at 11:22 AM Mohammad Rahmani  
> wrote:
>
>> Hi Atro,
>>
>> Very nice question and a lot of use cases!!
>>
>> You get two solutions from Soren and Tones!
>> The Soren solution implements a real basket !  Soren said it is* a lazy 
>> solution*! I want to see if I can be lazier! *;-)*
>>
>> *Third solution*
>>
>>1. Clone the Open tab in the sidebar ( $:/core/ui/SideBar/Open  )
>>2. rename it to "myBasket"
>>3. change the caption to Basek (I named it Atro Basket for *Atronoush*
>>)
>>4. make small change (e.g set the tv-story-list to myBasket to use it 
>>instead of TW tv-story-list)
>>5. change close all to clear all to clear the list of myBasket
>>6. add an export button to export tiddlers in basket (e.g listed in 
>>myBasket list field)
>>7. make your button *draggable* (for example use dragFilter)
>>
>> *How it works*
>>
>>1. Open the Atro Basket in the sidebar  (see attached file)
>>2. add items to Basket in different ways like below
>>   1. drag and drop links, titles to Basket
>>   2. drag a tag pill to add all tiddler with that tag
>>   3. if you are not happy click *clear all* to remove all tiddlers 
>>   in basket
>>   4. if you like remove any item click the *remove button*
>>3. Export
>>   1. click export button to export json (all tiddlers in the basket 
>>   as json) OR
>>   2. drag and drop the export button to other wiki to import all 
>>   tiddlers in basket to your wiki  (your button is draggable)
>>   3. when finished! if you like to empty the Basket, click clear all
>>
>>
>> I have attached the working tiddler here! Drop into 
>> https://tiddlywiki.com/ and see how it works!
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Tue, May 4, 2021 at 1:38 AM Atronoush Parsi  wrote:
>>
>>> Is there any script or plugin with
>>>
>>> - a sidebar tab (I call it basket)
>>> - drag and drop features! One can drag a tiddler (e.g title) into the 
>>> basket
>>> - when finished press a button to export as JSON
>>> - the button can be dragged and drop into another wiki!
>>>
>>> The last part is what you see in TW-Icons
>>>
>>>
>>> -Atro
>>>
>>> -- 
>>> 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/CAKHVXmoDHTtqMgUcp2ob%3DvHt6_nwBJbM2S4fOCi0gMraE3wEOA%40mail.gmail.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/ac7fec6e-7c0b-45e1-bdc6-322e24b5cfc3n%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

[Rika Sukenik]

Hey, everyone! I'm passionate about Zettelkasten too. If you haven't seen 
Ross Ashby's digital Zettelkasten archive, it's worth checking 
out. http://rossashby.info/

On Sunday, May 2, 2021 at 4:09:38 PM UTC-4 bimlas wrote:

> Soren,
>
> Thank you for bringing the TiddlyWiki and Zettelkasten communities one 
> step closer. I think these two groups are very close to each other, just 
> the two parties just don’t know each other enough.
>
> I have read your notes and I would like to comment on a few:
>
> https://zettelkasten.sorenbjornstad.com/#DataAsKnowledgeGraph
>
> This may not be exactly what the description is about, but for some reason 
> the description is reminiscent of a solution where you basically navigate 
> between tables, but you are very free to do so. Read the description firtst 
> on https://groups.google.com/g/tiddlywiki/c/Re11x96t-qI/m/WoqDEuJzGQAJ, 
> then try out on https://bimlas.gitlab.io/demo/tw5/property-comparison.html
>
> https://zettelkasten.sorenbjornstad.com/#FullTextSearch
>
> Here is a very good description of the topic: 
> https://tefkos.comminfo.rutgers.edu/Courses/e530/Readings/Beal%202008%20full%20text%20searching.pdf
>
> https://zettelkasten.sorenbjornstad.com/#WritingFreesHeadspace
>
> I have found in myself that writing makes me more efficient, but my memory 
> has deteriorated a lot. It’s easier to describe something than to remember 
> it in the long run and I think it’s okay, but in the eyes of those around 
> me, I seem like a forgetful person. Have you noticed anything like this in 
> yourself?
>
> My further thoughts on note-taking methods: 
> https://groups.google.com/g/tiddlywiki/c/2yRiVsbAv9g/m/vKBIC5CjBQAJ
>

-- 
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/57942a6b-c015-4dc2-b5cf-9af9c3f3ec4fn%40googlegroups.com.

Re: [tw5] What plugins do you use to write?

[Rika Sukenik]

Hey Anders, thank you for the recommendation! On first glance, it looks 
really sleek and helpful for longer form text. I'll dig in!

On Sunday, May 2, 2021 at 10:55:53 AM UTC-4 Anjar wrote:

> Hi Rika,
>
> It may not be what you want, but a tiddlywiki more customized for longer 
> texts can be found here: https://andjar.github.io/TW5-longtext/
>
> You can choose to have two story rivers; writing to the left and 
> previewing to the right, or you can have other stuff to the right (figures, 
> references...). Or if you simply want to focus on the writing, you can 
> close the toddlers to the right (and just click "Preview" to open the 
> preview again). In addition, you have the plainrev plugin to take care of 
> revisions (each time you click "SAVE")
>
> Best,
> Anders
> fredag 23. april 2021 kl. 07:47:51 UTC+2 skrev bmad...@gmail.com:
>
>> I made this plugin to be able to write long form in TW easily: 
>> https://adithya-badidey.github.io/TW5-codemirror-plus/
>> Along with this, I keep a small cheatsheet of shortcuts and formatting 
>> symbols.
>>
>>
>> On Thursday, April 22, 2021 at 10:38:08 AM UTC-6 Javier Rojas wrote:
>>
>>> On Thu, Apr 22, 2021 at 09:28:28AM -0700, Rika Sukenik wrote: 
>>> > I'm starting to write more long form in Tiddlywiki and I'd like an 
>>> easy way 
>>> > to bold, highlight, and add quotes. I'd love to hear what tool writers 
>>> like 
>>> > to use for writing. Thanks! 
>>>
>>> I wanted to use a proper editor to edit the text in textareas, and was 
>>> really happy to find about 
>>> https://addons.mozilla.org/en-Us/firefox/addon/firenvim/ , which embeds 
>>> an nvim instance in any textarea in your browser, including of course 
>>> the edit field for tiddlers in tiddlywiki. Since nvim is quite 
>>> extensible, that fills my needs, although I admit vim/nvim is not 
>>> everybody's text editor of choice. 
>>>
>>> Another approach is 
>>> https://addons.mozilla.org/en-Us/firefox/addon/ghosttext/ , which will 
>>> let you edit the contents of textareas in an external text editor of 
>>> your choice; I've also used that one, and I like it, but I prefer the 
>>> "embedded" approach of firenvim better. 
>>>
>>>

-- 
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/eed84175-9058-41a7-919f-9d40968314fdn%40googlegroups.com.

Re: [tw5] Streams 0.21 is now available

[TW Tones]

Si,

Yes, a tag would be helpful, No I have not gone further with this yet 
except in using a stream name that hides the items behind $:/, and rename 
to make them permanent independent tiddlers. Once permanent independent 
tiddlers I can use tags and other methods to manage them, if not yet in 
streams.

I did however discover how easy it is to drag and drop stream items 
elsewhere, which is an easy way to manipulate them, It even integrates with 
projectify.

Tones


On Wednesday, 5 May 2021 at 07:48:09 UTC+10 si wrote:

> @Tones - I like your idea. You could have a tag like 
> $:/tags/streams/ViewTemplate that would transclude its text field onto 
> every node. One obvious use-case could be adding a checkbox to mark tasks 
> as done.
>
> Did you manage to get anything working?
>
> @Saq - Totally unrelated question. Is there a way to save and exit a node 
> while on mobile? I.e. the equivalent of Ctrl+Enter on a normal keyboard.
> On Monday, 3 May 2021 at 08:09:59 UTC+1 TW Tones wrote:
>
>> Saq,
>>
>> Thanks I realised the  Context Menu  has some customisation. However it 
>> assumes a button/action where I may just want to display something 
>> conditionally. 
>> I could use a popup to contain something a bit like the rename, but more 
>> info, but I am interested in placing a tag pill or button after the dot 
>> point. I continue to try and see how to hack it.
>>
>> Regards
>> Tony
>>
>>
>> On Monday, 3 May 2021 at 15:02:15 UTC+10 Saq Imtiaz wrote:
>>
>>> @Tones https://saqimtiaz.github.io/streams/#FAQs
>>>
>>> On Monday, May 3, 2021 at 5:20:06 AM UTC+2 TW Tones wrote:
>>>
 Saq,

 With each item in a stream, the bullet has its own menu and drag. 
 Perhaps a simple way for the user to extend this would be being able to 
 add 
 an item to the stream item, or menu, just like how we add content to 
 tiddlers with the view template, would permit many additional requirements 
 to be added by the user. For example a button to tag the stream entry as a 
 todo, or set a field aa a priority. Another space where users can display 
 something per stream item would be similar.

 Tones

 On Friday, 30 April 2021 at 22:42:41 UTC+10 Saq Imtiaz wrote:

> Hi Mohammad,
>   
>
>> Lovely! This is one of my favorite use case! At the end I normally 
>> merge the notes!
>>
>
> I need to develop my workflow further but so far I've been dragging 
> and dropping to an actions items tiddler or other tiddlers that are 
> relevant to the topic. At the end there are no nodes left in the original 
> conference call notes.
>  
>
>> I use this solution! Assume I want to put note or discuss a slide or 
>> report in an online meeting!
>> Say tiddler is $:/kookma/courses/CHE403/rk45
>>
>> Yes your way of doing things is one option.
>
> What I am considering is this: imagine that you want to take notes 
> using Streams on $:/kookma/courses/CHE403/rk45
> If you add nodes, directly streams will edit this tiddler's 
> stream-list field. This is a problem if you want to maybe synchronize 
> this tiddler with another wiki later, you will get a merge conflict.
>
> So there should be a way to use Streams to take notes on a tiddler 
> without having to modify it.
> So the idea is, instead of saving the list of nodes in the stream-list 
> field of the tiddler $:/kookma/courses/CHE403/rk45, we can save them 
> in a config tiddler called something like 
> $:/streams/sidecar/$:/kookma/courses/CHE403/rk45
>
> Streams can then read the list of nodes from this tiddler, instead of 
> from the stream-list field in the $:/kookma/courses/CHE403/rk45 
> tiddler.
>
> We would not need to do this for every node, just the stream root 
> tiddler.
>


-- 
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/606139ab-03b5-41f7-9eaa-a91e48e93c85n%40googlegroups.com.

Re: [tw5] Streams 0.21 is now available

[Joshua Fontany]

I like the idea that Streams would store its relational data NOT on the 
parent tiddler, but in some other (system prefixed?). That is worth 
exploring. :)

Best,
Joshua Fontany

On Tuesday, May 4, 2021 at 2:48:09 PM UTC-7 si wrote:

> @Tones - I like your idea. You could have a tag like 
> $:/tags/streams/ViewTemplate that would transclude its text field onto 
> every node. One obvious use-case could be adding a checkbox to mark tasks 
> as done.
>
> Did you manage to get anything working?
>
> @Saq - Totally unrelated question. Is there a way to save and exit a node 
> while on mobile? I.e. the equivalent of Ctrl+Enter on a normal keyboard.
> On Monday, 3 May 2021 at 08:09:59 UTC+1 TW Tones wrote:
>
>> Saq,
>>
>> Thanks I realised the  Context Menu  has some customisation. However it 
>> assumes a button/action where I may just want to display something 
>> conditionally. 
>> I could use a popup to contain something a bit like the rename, but more 
>> info, but I am interested in placing a tag pill or button after the dot 
>> point. I continue to try and see how to hack it.
>>
>> Regards
>> Tony
>>
>>
>> On Monday, 3 May 2021 at 15:02:15 UTC+10 Saq Imtiaz wrote:
>>
>>> @Tones https://saqimtiaz.github.io/streams/#FAQs
>>>
>>> On Monday, May 3, 2021 at 5:20:06 AM UTC+2 TW Tones wrote:
>>>
 Saq,

 With each item in a stream, the bullet has its own menu and drag. 
 Perhaps a simple way for the user to extend this would be being able to 
 add 
 an item to the stream item, or menu, just like how we add content to 
 tiddlers with the view template, would permit many additional requirements 
 to be added by the user. For example a button to tag the stream entry as a 
 todo, or set a field aa a priority. Another space where users can display 
 something per stream item would be similar.

 Tones

 On Friday, 30 April 2021 at 22:42:41 UTC+10 Saq Imtiaz wrote:

> Hi Mohammad,
>   
>
>> Lovely! This is one of my favorite use case! At the end I normally 
>> merge the notes!
>>
>
> I need to develop my workflow further but so far I've been dragging 
> and dropping to an actions items tiddler or other tiddlers that are 
> relevant to the topic. At the end there are no nodes left in the original 
> conference call notes.
>  
>
>> I use this solution! Assume I want to put note or discuss a slide or 
>> report in an online meeting!
>> Say tiddler is $:/kookma/courses/CHE403/rk45
>>
>> Yes your way of doing things is one option.
>
> What I am considering is this: imagine that you want to take notes 
> using Streams on $:/kookma/courses/CHE403/rk45
> If you add nodes, directly streams will edit this tiddler's 
> stream-list field. This is a problem if you want to maybe synchronize 
> this tiddler with another wiki later, you will get a merge conflict.
>
> So there should be a way to use Streams to take notes on a tiddler 
> without having to modify it.
> So the idea is, instead of saving the list of nodes in the stream-list 
> field of the tiddler $:/kookma/courses/CHE403/rk45, we can save them 
> in a config tiddler called something like 
> $:/streams/sidecar/$:/kookma/courses/CHE403/rk45
>
> Streams can then read the list of nodes from this tiddler, instead of 
> from the stream-list field in the $:/kookma/courses/CHE403/rk45 
> tiddler.
>
> We would not need to do this for every node, just the stream root 
> tiddler.
>


-- 
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/14c4aeb8-4e24-476b-8e4f-440da6641089n%40googlegroups.com.

[tw5] Re: "Filter Expression" doc

[Joshua Fontany]

Ooops, that should have been  `./path/to/TiddlyWiki5/bin/serve.sh`.

Best,
Joshua Fontany

On Tuesday, May 4, 2021 at 4:13:42 PM UTC-7 Joshua Fontany wrote:

> Fork the TW5 repository to your own GitHub user account, and then clone it 
> locally. 
>
> Then checkout the "tiddlywiki-com" branch via git command line. (This 
> branch can live push updates to the website, and not wait until the next 
> Version release).
>
> Then, run the node command given in the `bin` scripts folder:
> `./path/to/TiddlyWiki5/bin.serve.sh`
>
> This launches the "tiddlywiki-com-server" Edition (from the 
> 'TiddlyWiki5/editions' folder) as a node process.
>
> Navigate a browser to 127.0.0.1:8080. Make changes to documentation 
> tiddlers. Push your changes back to your fork.
>
> From GitHub, create a Pull Request from your fork of the "tiddlywiki-com" 
> branch to the official repository's "tiddlywiki-com" branch. Describe your 
> changes in your PR.
>
> The community can then review those changes, and Jeremy can merge if it 
> all looks good.
>
> Best,
> Joshua Fontany
>
>
>
> On Tuesday, May 4, 2021 at 1:50:32 PM UTC-7 jn.pierr...@gmail.com wrote:
>
>> Fine. How may I help then? It's also that bit that I find lacking in the 
>> doc (just poke at it but got no interesting stuff for this).
>>
>> Le mardi 4 mai 2021 à 21:59:46 UTC+2, saq.i...@gmail.com a écrit :
>>
>>> I don't disagree. Contributions to the documentation are very welcome.
>>>
>>> On Tuesday, May 4, 2021 at 9:46:02 PM UTC+2 jn.pierr...@gmail.com wrote:
>>>
 right. not very user friendly. could be noted earlier at ~

 the same for the others. when there is so much to read, being kind on 
 the reader is not undue.

 Le mardi 4 mai 2021 à 21:30:54 UTC+2, saq.i...@gmail.com a écrit :

> As the table indicates, :else is equivalent to the ~ filter run prefix 
> which is explained earlier in the same tiddler.
>
> On Tuesday, May 4, 2021 at 9:09:23 PM UTC+2 jn.pierr...@gmail.com 
> wrote:
>
>> In the "Filter Expression" tiddler the :enter prefix is not listed in 
>> the first part, only given in a subsequent table.
>>
>> As such, :else lacks a proper explanation of what it does.
>>
>

-- 
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/59da2002-de75-482a-a878-a074c9846a8dn%40googlegroups.com.

[tw5] Re: "Filter Expression" doc

[Joshua Fontany]

Fork the TW5 repository to your own GitHub user account, and then clone it 
locally. 

Then checkout the "tiddlywiki-com" branch via git command line. (This 
branch can live push updates to the website, and not wait until the next 
Version release).

Then, run the node command given in the `bin` scripts folder:
`./path/to/TiddlyWiki5/bin.serve.sh`

This launches the "tiddlywiki-com-server" Edition (from the 
'TiddlyWiki5/editions' folder) as a node process.

Navigate a browser to 127.0.0.1:8080. Make changes to documentation 
tiddlers. Push your changes back to your fork.

>From GitHub, create a Pull Request from your fork of the "tiddlywiki-com" 
branch to the official repository's "tiddlywiki-com" branch. Describe your 
changes in your PR.

The community can then review those changes, and Jeremy can merge if it all 
looks good.

Best,
Joshua Fontany



On Tuesday, May 4, 2021 at 1:50:32 PM UTC-7 jn.pierr...@gmail.com wrote:

> Fine. How may I help then? It's also that bit that I find lacking in the 
> doc (just poke at it but got no interesting stuff for this).
>
> Le mardi 4 mai 2021 à 21:59:46 UTC+2, saq.i...@gmail.com a écrit :
>
>> I don't disagree. Contributions to the documentation are very welcome.
>>
>> On Tuesday, May 4, 2021 at 9:46:02 PM UTC+2 jn.pierr...@gmail.com wrote:
>>
>>> right. not very user friendly. could be noted earlier at ~
>>>
>>> the same for the others. when there is so much to read, being kind on 
>>> the reader is not undue.
>>>
>>> Le mardi 4 mai 2021 à 21:30:54 UTC+2, saq.i...@gmail.com a écrit :
>>>
 As the table indicates, :else is equivalent to the ~ filter run prefix 
 which is explained earlier in the same tiddler.

 On Tuesday, May 4, 2021 at 9:09:23 PM UTC+2 jn.pierr...@gmail.com 
 wrote:

> In the "Filter Expression" tiddler the :enter prefix is not listed in 
> the first part, only given in a subsequent table.
>
> As such, :else lacks a proper explanation of what it does.
>


-- 
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/3aaf0911-87b3-4ee5-9b44-0f530f398639n%40googlegroups.com.

[tw5] Re: [IDEA] Archiving tiddlers, for Projectify users and potentially others

[TW Tones]

Diego,

Good idea providing "full" archive to Projectify. If packaged perhaps you 
can "give" it to the author to include.

I want to do something similar with streams, but I need additional logic. I 
use a naming standard for stream (tiddlers) to hide them behind system 
tiddlers "$:/", however if one wants to keep them indefinitely and make 
them accessible, I rename them to non system tiddlers.

Obviously If I am on a tiddler with a lot of stream notes, I may want to 
archive the whole set but not remove regular tiddlers.

As mentioned by HH Mohamad's trashbin (KOOKMAs) plugin does this already,  
I would like to see your solution, mohamads or the recent Basket tool 
generalised to provide better tiddler to json and back handling.

Just some thoughts
Tones
On Tuesday, 4 May 2021 at 12:17:48 UTC+10 dieg...@gmail.com wrote:

> I work a lot with Nicos excellent Projectify plugin. 
>
> As a result, I have a lot of ephemeral tiddlers for my to-dos that once 
> done, are no longer really needed as full tiddlers. I don't need to search 
> them, tag them, etc. 
>
> Also, since I use node, I don't really want them cluttering the tiddlers 
> folder, as I frequently go in there and do some searching outside TW.
>
> As a result, I thought about "Archiving" them, or "flattening" them, into 
> a single JSON tiddler for reference. 
>
> I came up with the following "Archive" button, which appends all tiddlers 
> tagged with done to an Archive tiddler. 
>
> Code:
> <$vars archiveTiddlerTitle="Archive" 
>todoText=<> 
>emptyJSON="[]" linebreak="
>
> "> 
> <$set name="newArchiveText" 
>   filter="[!match]" 
>   value={{{ 
> [titleget[text]addsuffixaddsuffix] 
> }}} 
>   emptyValue={{{ [titleget[text]] }}} >
>
> <$button>
> <$action-setfield $tiddler=<> 
>   $field="text" 
>   $value=<> />
> <$action-deletetiddler $filter="[tag[done]]" />   
> Archive! 
> 
>
> 
> 
>
>
> Some notes:
>
>- I had to solve an annoying issue with the <> macro 
>that when its empty, returns an "[]", which is actually not empty (is this 
>intended?!) 
>- Different archiving batches will just be appended as separate JSON 
>objects, instead of merging everything back into one large JSON object.
>- There is no "unarchive" feature, and building one is probably beyond 
>my abilities (thought might be a good use case for Joshua's JSON Mangler! 
>if I understand it correctly!)
>
>
> This could be of use for others to "flatten" large tag structures that 
> you're done with and don't need flying around as separate tiddlers. 
>
> Your thoughts/suggestions/comments/etc are welcome!
>
> Diego
>

-- 
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/d1f671bc-50f5-494f-9bae-79ea166f4a93n%40googlegroups.com.

Re: [tw5] Re: Ten Ways to Drag and Drop Tiddlers to Tiddlywiki

[Joshua Fontany]

Drag and Drop a whole wiki into another wiki (a more recent TW version) to 
automatically import all user-created tiddlers into the new wiki.

On Tuesday, May 4, 2021 at 2:00:09 AM UTC-7 Mohammad wrote:

> Thank you Tones! Lovely!
>
>
>
> Best wishes
> Mohammad
>
>
> On Tue, May 4, 2021 at 12:40 PM TW Tones  wrote:
>
>>
>>1. Drag a tiddler from one wiki to another
>>2. Export a tiddler as a tid file and drag and drop the tid file on 
>>any wiki
>>3. Any title can be dropped on the text field in edit mode to add it 
>>to the text
>>4. Export a set of tiddlers as a JSON file and drag and drop the JSON 
>>file on any wiki
>>5. Drag and drop multiple tiddlers on a wiki, the $:/import tiddler 
>>is opened, rename the $:./import tiddler and remove its fields. You now 
>>have a JSON tiddler containing all the tiddlers that were in the import.
>>6. Drag and drop plugins (of course) to install.
>>7. add Mohammads items
>>8. Drop tiddlers or text on suitably configured buttons
>>9. ...
>>
>>
>> On Tuesday, 4 May 2021 at 17:50:01 UTC+10 Mohammad wrote:
>>
>>> Drag and drop contents into Tiddlywiki for importing and exporting 
>>> contents is one of the amazing features of Tiddlywiki, it is not known as 
>>> it deserved.
>>>
>>> To bring the power into attention I asked the above question and I am 
>>> looking forward to see how others use this feature!
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>> -- 
>>
> 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/6bfb5cf6-ed5c-4c66-9d2d-6b60016d3936n%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/cd209600-f9df-4c44-91b2-39c7738146e8n%40googlegroups.com.

Re: [tw5] Streams 0.21 is now available

[si]

@Tones - I like your idea. You could have a tag like 
$:/tags/streams/ViewTemplate that would transclude its text field onto 
every node. One obvious use-case could be adding a checkbox to mark tasks 
as done.

Did you manage to get anything working?

@Saq - Totally unrelated question. Is there a way to save and exit a node 
while on mobile? I.e. the equivalent of Ctrl+Enter on a normal keyboard.
On Monday, 3 May 2021 at 08:09:59 UTC+1 TW Tones wrote:

> Saq,
>
> Thanks I realised the  Context Menu  has some customisation. However it 
> assumes a button/action where I may just want to display something 
> conditionally. 
> I could use a popup to contain something a bit like the rename, but more 
> info, but I am interested in placing a tag pill or button after the dot 
> point. I continue to try and see how to hack it.
>
> Regards
> Tony
>
>
> On Monday, 3 May 2021 at 15:02:15 UTC+10 Saq Imtiaz wrote:
>
>> @Tones https://saqimtiaz.github.io/streams/#FAQs
>>
>> On Monday, May 3, 2021 at 5:20:06 AM UTC+2 TW Tones wrote:
>>
>>> Saq,
>>>
>>> With each item in a stream, the bullet has its own menu and drag. 
>>> Perhaps a simple way for the user to extend this would be being able to add 
>>> an item to the stream item, or menu, just like how we add content to 
>>> tiddlers with the view template, would permit many additional requirements 
>>> to be added by the user. For example a button to tag the stream entry as a 
>>> todo, or set a field aa a priority. Another space where users can display 
>>> something per stream item would be similar.
>>>
>>> Tones
>>>
>>> On Friday, 30 April 2021 at 22:42:41 UTC+10 Saq Imtiaz wrote:
>>>
 Hi Mohammad,
   

> Lovely! This is one of my favorite use case! At the end I normally 
> merge the notes!
>

 I need to develop my workflow further but so far I've been dragging and 
 dropping to an actions items tiddler or other tiddlers that are relevant 
 to 
 the topic. At the end there are no nodes left in the original conference 
 call notes.
  

> I use this solution! Assume I want to put note or discuss a slide or 
> report in an online meeting!
> Say tiddler is $:/kookma/courses/CHE403/rk45
>
> Yes your way of doing things is one option.

 What I am considering is this: imagine that you want to take notes 
 using Streams on $:/kookma/courses/CHE403/rk45
 If you add nodes, directly streams will edit this tiddler's stream-list 
 field. This is a problem if you want to maybe synchronize this tiddler 
 with 
 another wiki later, you will get a merge conflict.

 So there should be a way to use Streams to take notes on a tiddler 
 without having to modify it.
 So the idea is, instead of saving the list of nodes in the stream-list 
 field of the tiddler $:/kookma/courses/CHE403/rk45, we can save them 
 in a config tiddler called something like 
 $:/streams/sidecar/$:/kookma/courses/CHE403/rk45

 Streams can then read the list of nodes from this tiddler, instead of 
 from the stream-list field in the $:/kookma/courses/CHE403/rk45 
 tiddler.

 We would not need to do this for every node, just the stream root 
 tiddler.

>>>

-- 
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/3a8a1d7e-099b-4674-a04e-a3e4cf8067d6n%40googlegroups.com.

[tw5] Re: "Filter Expression" doc

[Jean-Pierre Rivière]

Fine. How may I help then? It's also that bit that I find lacking in the 
doc (just poke at it but got no interesting stuff for this).

Le mardi 4 mai 2021 à 21:59:46 UTC+2, saq.i...@gmail.com a écrit :

> I don't disagree. Contributions to the documentation are very welcome.
>
> On Tuesday, May 4, 2021 at 9:46:02 PM UTC+2 jn.pierr...@gmail.com wrote:
>
>> right. not very user friendly. could be noted earlier at ~
>>
>> the same for the others. when there is so much to read, being kind on the 
>> reader is not undue.
>>
>> Le mardi 4 mai 2021 à 21:30:54 UTC+2, saq.i...@gmail.com a écrit :
>>
>>> As the table indicates, :else is equivalent to the ~ filter run prefix 
>>> which is explained earlier in the same tiddler.
>>>
>>> On Tuesday, May 4, 2021 at 9:09:23 PM UTC+2 jn.pierr...@gmail.com wrote:
>>>
 In the "Filter Expression" tiddler the :enter prefix is not listed in 
 the first part, only given in a subsequent table.

 As such, :else lacks a proper explanation of what it does.

>>>

-- 
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/3f9535f6-738d-452b-b780-44a6abe8ae60n%40googlegroups.com.

[tw5] Re: "Filter Expression" doc

[Saq Imtiaz]

I don't disagree. Contributions to the documentation are very welcome.

On Tuesday, May 4, 2021 at 9:46:02 PM UTC+2 jn.pierr...@gmail.com wrote:

> right. not very user friendly. could be noted earlier at ~
>
> the same for the others. when there is so much to read, being kind on the 
> reader is not undue.
>
> Le mardi 4 mai 2021 à 21:30:54 UTC+2, saq.i...@gmail.com a écrit :
>
>> As the table indicates, :else is equivalent to the ~ filter run prefix 
>> which is explained earlier in the same tiddler.
>>
>> On Tuesday, May 4, 2021 at 9:09:23 PM UTC+2 jn.pierr...@gmail.com wrote:
>>
>>> In the "Filter Expression" tiddler the :enter prefix is not listed in 
>>> the first part, only given in a subsequent table.
>>>
>>> As such, :else lacks a proper explanation of what it does.
>>>
>>

-- 
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/ff87bcd0-49e3-4a30-8294-a05d21d1cf66n%40googlegroups.com.

[tw5] Re: "Filter Expression" doc

[Jean-Pierre Rivière]

right. not very user friendly. could be noted earlier at ~

the same for the others. when there is so much to read, being kind on the 
reader is not undue.

Le mardi 4 mai 2021 à 21:30:54 UTC+2, saq.i...@gmail.com a écrit :

> As the table indicates, :else is equivalent to the ~ filter run prefix 
> which is explained earlier in the same tiddler.
>
> On Tuesday, May 4, 2021 at 9:09:23 PM UTC+2 jn.pierr...@gmail.com wrote:
>
>> In the "Filter Expression" tiddler the :enter prefix is not listed in the 
>> first part, only given in a subsequent table.
>>
>> As such, :else lacks a proper explanation of what it does.
>>
>

-- 
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/587b747d-1109-400a-9fcd-ac7a8f5a5069n%40googlegroups.com.

[tw5] Re: "Filter Expression" doc

[Saq Imtiaz]

As the table indicates, :else is equivalent to the ~ filter run prefix 
which is explained earlier in the same tiddler.

On Tuesday, May 4, 2021 at 9:09:23 PM UTC+2 jn.pierr...@gmail.com wrote:

> In the "Filter Expression" tiddler the :enter prefix is not listed in the 
> first part, only given in a subsequent table.
>
> As such, :else lacks a proper explanation of what it does.
>

-- 
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/c43503dc-cc49-48d9-8150-b26690b701ddn%40googlegroups.com.

[tw5] Re: improving smart resarch for in-situ macros for filter

[Saq Imtiaz]

Filter run prefixes have seen a lot of improvements recently, and as such 
there is definitely room for more documentation.

The documentation is a community effort and maintained in the same git repo 
as the TW source code. Contributions to the documentation as PR are highly 
welcome.

On Tuesday, May 4, 2021 at 8:58:08 PM UTC+2 jn.pierr...@gmail.com wrote:

>
> Saq, your example should be added to the "Filter Run Prefix (Examples)" 
> tiddler of the doc.
>
> Jeremy's is the best answer, but clearly both are convincing enough that 
> the UI is about right today. And yes I was aware I could have a pablic 
> macro help me, but that would not be very neat or a bit of hassle to setup 
> and get rid of after use.
> Le mardi 4 mai 2021 à 09:56:30 UTC+2, saq.i...@gmail.com a écrit :
>
>> [all[tiddlers]] :filter[get[type]match[application/javascript]]
>>
>>
>> On Tuesday, May 4, 2021 at 9:42:30 AM UTC+2 jn.pierr...@gmail.com wrote:
>>
>>> Today I wanted to see which tiddlers I have that are javascript.
>>>
>>> In advanced research i can execute something like
>>>
>>> [get[type]match[application/javascript]]
>>>
>>> but it would only bring "application/javascript"
>>>
>>> I can't have [filter[get[type]match[application/javascript]]]
>>>
>>> because this is gross syntax error.
>>>
>>> But if I had access to another input ext for a macro to be called extra 
>>> I could do
>>>
>>> extra : [get[type]match[application/javascript]]
>>> research : filtersortan[]
>>>
>>> and the job would be done.
>>>
>>> BTW, I think a standard "nop" macro doing nothing would be useful. I'm 
>>> using it many times when I have to decide for an eventual treatment, for 
>>> (actual real) instance:
>>>
>>> \define deleteProjectNewAltjson(target id)
>>> <$action-log $$message="delete project «$target$##$id$»"/>
>>> <$action-deletefield $tiddler="$target$" $field="$id$"/>
>>> <$set name=next-step 
>>> filter="[getindex]then[_kludge4deleteProjectNewAltjson]else[nop]]">
>>> <>
>>> 
>>> <$action-log $$message="deleted project «$target$##$id$»"/>
>>> \end
>>>
>>> (this concerns a potential bug for impossibility to delete a property of 
>>> first level within a json object tiddler -- there is a separate thread I 
>>> fielded yesterday for that)
>>>
>>> I have not seen any other way to have a conditional call to a macro.
>>>
>>> regards,
>>>
>>> -- 
>>> Jean-Pierre
>>>
>>

-- 
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/2ae0ca24-b22d-4218-b6c6-604917280001n%40googlegroups.com.

[tw5] "Filter Expression" doc

[Jean-Pierre Rivière]

In the "Filter Expression" tiddler the :enter prefix is not listed in the 
first part, only given in a subsequent table.

As such, :else lacks a proper explanation of what it does.

-- 
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/b3894440-0af0-45ab-92ad-49bdf41cbb51n%40googlegroups.com.

[tw5] Re: improving smart resarch for in-situ macros for filter

[Jean-Pierre Rivière]

Saq, your example should be added to the "Filter Run Prefix (Examples)" 
tiddler of the doc.

Jeremy's is the best answer, but clearly both are convincing enough that 
the UI is about right today. And yes I was aware I could have a pablic 
macro help me, but that would not be very neat or a bit of hassle to setup 
and get rid of after use.
Le mardi 4 mai 2021 à 09:56:30 UTC+2, saq.i...@gmail.com a écrit :

> [all[tiddlers]] :filter[get[type]match[application/javascript]]
>
>
> On Tuesday, May 4, 2021 at 9:42:30 AM UTC+2 jn.pierr...@gmail.com wrote:
>
>> Today I wanted to see which tiddlers I have that are javascript.
>>
>> In advanced research i can execute something like
>>
>> [get[type]match[application/javascript]]
>>
>> but it would only bring "application/javascript"
>>
>> I can't have [filter[get[type]match[application/javascript]]]
>>
>> because this is gross syntax error.
>>
>> But if I had access to another input ext for a macro to be called extra I 
>> could do
>>
>> extra : [get[type]match[application/javascript]]
>> research : filtersortan[]
>>
>> and the job would be done.
>>
>> BTW, I think a standard "nop" macro doing nothing would be useful. I'm 
>> using it many times when I have to decide for an eventual treatment, for 
>> (actual real) instance:
>>
>> \define deleteProjectNewAltjson(target id)
>> <$action-log $$message="delete project «$target$##$id$»"/>
>> <$action-deletefield $tiddler="$target$" $field="$id$"/>
>> <$set name=next-step 
>> filter="[getindex]then[_kludge4deleteProjectNewAltjson]else[nop]]">
>> <>
>> 
>> <$action-log $$message="deleted project «$target$##$id$»"/>
>> \end
>>
>> (this concerns a potential bug for impossibility to delete a property of 
>> first level within a json object tiddler -- there is a separate thread I 
>> fielded yesterday for that)
>>
>> I have not seen any other way to have a conditional call to a macro.
>>
>> regards,
>>
>> -- 
>> Jean-Pierre
>>
>

-- 
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/2e7fc87c-f13b-4a6a-ae50-32104d810078n%40googlegroups.com.

[tw5] Re: Very random Javascript errors

[Ste]

Red Screen of Death. Sometimes also called RSOE Red Screen of 
Embarrassment. 

On Tuesday, 4 May 2021 at 16:25:33 UTC+1 History Buff wrote:

> By RSOD, I'm assuming you mean the error window that pops up. Next time 
> that happens, I'll take a screenshot.
>
> On Monday, May 3, 2021 at 11:17:30 PM UTC-7 PMario wrote:
>
>> Hi,
>> It would be good, if you could post the exact text, that is shown on the 
>> RSOD. It should tell us, what's causing the problem.
>>
>> ... Yes most likely a plugin, if you can't replicate it at tiddlywiki.com
>>
>> -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/311213b4-8d85-49f0-a9be-076c0f2bbb13n%40googlegroups.com.

[tw5] Re: action-delefield et json

[Jean-Pierre Rivière]

well, the current way of deljeting an index is not very satisfying from the 
readability point of view. so yes, an $action-deleteindex is as justified 
as $action-deletefield. and if not, then $action-deletefield should get an 
$index parameter.

BTW, I think it would be good to allow for a "getfield" homonym for "get" 
filter operator, for a naming consistency.

Le mardi 4 mai 2021 à 14:52:40 UTC+2, PMario a écrit :

> On Tuesday, May 4, 2021 at 2:02:06 PM UTC+2 jn.pierr...@gmail.com wrote:
> ...
>
>> and why is there not any $acion-deleteindex?
>>
>
> IMO because, if users know how to do it, they use the existing 
> functionality.
>
> -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/7edc52ef-e1fc-4ce3-a613-3631c1b73c69n%40googlegroups.com.

Re: [tw5] Re: Three remaining conundrums

[Mohammad Rahmani]

On Tue, May 4, 2021 at 1:42 AM Charlie Veniot  wrote:

> Oh no, not using node.js.  TiddlyWiki in GoogleDrive, with TiddlyDrive
> Add-on.
>
> Yeah, so far at most three tiddlers, each exported individually, drag them
> individually into TiddlyWiki.com as a quick sanity test, then zip them up.
>
> Mindless clicking away.  Probably not good for the finger knuckle (i.e.
> mouse-clicky-induced tendinitis of the finger knuckle.)  Mindlessness over
> tendinitis-fears any day.
>


Good luck! You can now consider the Basket solution in another thread which
is very easy to select tiddlers and share!




>
> On Monday, May 3, 2021 at 4:46:09 PM UTC-3 Mohammad wrote:
>
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Tue, May 4, 2021 at 12:06 AM Charlie Veniot  wrote:
>>
>>> Truth be told, I was seriously buying in until "just open the
>>> $:/AdvancedSearch and Filter what you want to export and then click export
>>> to JSON!"
>>>
>>> Yuck.
>>>
>>> I very much enjoy writing filters, but mindless clicking to ZIP only
>>> several tiddlers fits my personality better.
>>>
>>
>> How do you do this? Are you using Node.JS? or you export tids one by one
>> and then zip them?
>>
>>
>>> However, when I get into dozens of tiddlers, I will love advanced search
>>> to JSON export, and I will be then hugging you, virtually, quite
>>> furiously.  That's very good info to have in one's back-pocket.
>>>
>>
>> ;-)
>>
>>>
>>>
>>> On Monday, May 3, 2021 at 4:05:57 PM UTC-3 Mohammad wrote:
>>>
 I believe JSON is much better and I assume GG lets you attach them!
 I am sure you know export to json
 just open the $:/AdvancedSearch and Filter what you want to export and
 then click export to JSON!
 Add data and revision numbers as you like!
 On Sharing we can simply drag and drop to our wikis! no unzip required!




 Best wishes
 Mohammad


> --
>>> 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/cde7c5c6-c222-4207-a85c-a20583457f17n%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/e41a69de-b46b-472d-8402-994e94df2a70n%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/CAAV1gMDaD6-n%3DWHpcsTz4WMdGcLbFKu6b-a%2BR82qhW1dEOteHA%40mail.gmail.com.

Re: [tw5] Re: Default Tiddler Configuration

[Jax Kovak]

Yes, Iv tried clicking that small image indicated in the image, and the 
button and the default button. No joy I'm afraid.

On Tuesday, 4 May 2021 at 13:56:38 UTC+1 PMario wrote:

> Hi,
> Have a look at the image from my first post. There is a marker, that says 
> "click". ... 
>
> It should be possible to create a "New Edit with Template" button. ... But 
> I didn't do that. I did recycle the code from this thread: 
> https://groups.google.com/g/tiddlywiki/c/sQr3OJwnj8I/m/Qnv_Z9KsAgAJ
>
> -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/06c1036e-c332-44c5-9875-85de50f2afe3n%40googlegroups.com.

[tw5] Re: Very random Javascript errors

[History Buff]

By RSOD, I'm assuming you mean the error window that pops up. Next time 
that happens, I'll take a screenshot.

On Monday, May 3, 2021 at 11:17:30 PM UTC-7 PMario wrote:

> Hi,
> It would be good, if you could post the exact text, that is shown on the 
> RSOD. It should tell us, what's causing the problem.
>
> ... Yes most likely a plugin, if you can't replicate it at tiddlywiki.com
>
> -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/46d44d55-0552-4d61-ae3d-94817cd76e96n%40googlegroups.com.

Re: [tw5] twexe (the plugin) update

[James Anderson]

https://en.wikipedia.org/wiki/HTML_Application

It's asscoiated with Windows rather than IE (it probably uses some IE or 
edge stuff under the hood, but you don't need IE installed to use it iirc)

if you rename an html file to .hta on windows you get elevated permissions 
that a web page wouldn't normally have. This is powerful but potentially 
dangerous (i'd only ever use it for my own tiddlywikis) 

by default a tw running from hta can save to itself with no plugins 
required. With my plugin it can run other executables (my plugin is also 
safe for browser versions, it just won't attempt to do anything in that 
case)

Also I * think * my plugin predates twexe the app :D


On Tuesday, 4 May 2021 at 15:45:02 UTC+1 Mark S. wrote:

> What is meant by a "hta" type file? Do all browsers support it? I had the 
> notion that it was associated with Internet Explorer. Support for IE is 
> supposed to end this summer.
>
> I was confused by the name at first, because  there is an existing product 
> called "twexe" which bundles up TW files into executables.
>
> Thanks!
>
> On Tuesday, May 4, 2021 at 6:36:43 AM UTC-7 Mohammad wrote:
>
>> James,
>>  This is one of great tools which will always be useful! 
>>  
>>   Thank you very much for the update!
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Tue, May 4, 2021 at 5:01 PM James Anderson  
>> wrote:
>>
>>> Incase any windows/hta users still use this:
>>>
>>> I've updated this plugin. the source is here: 
>>> https://github.com/welford/twexe and you can grab a copy of the updated 
>>> plugin from http://welford.github.io/
>>>
>>> The big change is that you can run the contents of a tiddler as a batch 
>>> file, which should help keep things portable (between machines / 
>>> environments, not cross platform). 
>>>
>>> It will create a temporary twexe.bat file in %TEMP% fill it with the 
>>> contents of the tiddler and then run it. You can change the default 
>>> temporary location via  $:/plugins/welford/twexe/tmpdir
>>>
>>> in the attached image i have two examples, one will run my local node.js 
>>> tw, the other just an example batch file that prints hello and the first 
>>> arg passed to it.
>>>
>>> -- 
>>> 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/49e93d80-9a3e-449e-bbd4-9a007b0782dcn%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/69fab1b3-3742-45a8-be37-7fadf9e658c0n%40googlegroups.com.

Re: [tw5] twexe (the plugin) update

['Mark S.' via TiddlyWiki]

What is meant by a "hta" type file? Do all browsers support it? I had the 
notion that it was associated with Internet Explorer. Support for IE is 
supposed to end this summer.

I was confused by the name at first, because  there is an existing product 
called "twexe" which bundles up TW files into executables.

Thanks!

On Tuesday, May 4, 2021 at 6:36:43 AM UTC-7 Mohammad wrote:

> James,
>  This is one of great tools which will always be useful! 
>  
>   Thank you very much for the update!
>
> Best wishes
> Mohammad
>
>
> On Tue, May 4, 2021 at 5:01 PM James Anderson  
> wrote:
>
>> Incase any windows/hta users still use this:
>>
>> I've updated this plugin. the source is here: 
>> https://github.com/welford/twexe and you can grab a copy of the updated 
>> plugin from http://welford.github.io/
>>
>> The big change is that you can run the contents of a tiddler as a batch 
>> file, which should help keep things portable (between machines / 
>> environments, not cross platform). 
>>
>> It will create a temporary twexe.bat file in %TEMP% fill it with the 
>> contents of the tiddler and then run it. You can change the default 
>> temporary location via  $:/plugins/welford/twexe/tmpdir
>>
>> in the attached image i have two examples, one will run my local node.js 
>> tw, the other just an example batch file that prints hello and the first 
>> arg passed to it.
>>
>> -- 
>> 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/49e93d80-9a3e-449e-bbd4-9a007b0782dcn%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/52014518-c6d3-4961-83c8-0305aa7e85f1n%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[TW Tones]

Mario,

Ah yes, these related fields could be for a range  long-ago..from, 
long-ago..to meaning there is no need for long-ago or long-ago..

We need to be careful we do not confuse the type with the fieldname. I 
would not expect a fieldname.type in any tiddler but perhaps in a dedicated 
fieldname tiddler.

Thus there may be a tiddler named long-ago..from and another long-ago..to 
which include a field called field-type=ancient which demands a negative 
number or 0 ? and has a "year" as its units.

I once thought that I must decide on a set of modes that either the tiddler 
or a specific field can be "displayed in" such as view update(click to 
change) edit already in edit mode etc...
During this thread I have come to realise each time we add a field we can 
also add it to more than one mode tiddler eg edit-mode which can contain 
the wikitext for that field in edit mode, in fact all fields wiki text in 
edit mode. And another for view and update, I can just add another mode 
tiddler eg designer and decide what wiki text markup to use for the field 
in this mode.
The trick is to simplify this so you start with a default related to the 
tidler type, for example a view provided for long-ago..from woul;d be 
{{!!long-ago..from}} if I put the tiddler into edit mode, it looks to see 
if this field has an entry in the edit mode tiddler, if not it "steps back 
one" and inherits the view mode.

It would be easy to scan the wiki and identify all fields and store them in 
a view mode tiddler just with the {{!!fieldname}} as an initial value. Do 
the same for editmode and place in each field in the tiddler the code to 
edit each field defaulting to text edit. However as pointed out before 
having a field-type determine how to view or edit is more precise. Thus on 
creating a field add the field name to a $:/fields tiddler and provide a 
default field-type, then in separate mode tiddlers provide the wikitext to 
handle that field type in that mode.

I am working on an example now, and using some buttons to populate default 
fields.

Tones
On Tuesday, 4 May 2021 at 19:32:04 UTC+10 PMario wrote:

> On Tuesday, May 4, 2021 at 11:27:49 AM UTC+2 PMario wrote:
>
> I still want to have  sec-expanded-years 
>>  as in 
>> https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/jpQJrSi8BwAJ
>> and: SI prefix multipliers 
>> 
>>  
>> as in: 
>> https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/l5S9-TnaBwAJ from 
>> the same thread. 
>>
>
> And I want, that TW-fields can handle this. eg: long-ago..from, 
> long-ago..to   
>
> just an idea ;)
> -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/282a6301-668b-4d7e-baf0-5216abb612abn%40googlegroups.com.

Re: [tw5] twexe (the plugin) update

[Mohammad Rahmani]

James,
 This is one of great tools which will always be useful!

  Thank you very much for the update!

Best wishes
Mohammad


On Tue, May 4, 2021 at 5:01 PM James Anderson 
wrote:

> Incase any windows/hta users still use this:
>
> I've updated this plugin. the source is here:
> https://github.com/welford/twexe and you can grab a copy of the updated
> plugin from http://welford.github.io/
>
> The big change is that you can run the contents of a tiddler as a batch
> file, which should help keep things portable (between machines /
> environments, not cross platform).
>
> It will create a temporary twexe.bat file in %TEMP% fill it with the
> contents of the tiddler and then run it. You can change the default
> temporary location via  $:/plugins/welford/twexe/tmpdir
>
> in the attached image i have two examples, one will run my local node.js
> tw, the other just an example batch file that prints hello and the first
> arg passed to it.
>
> --
> 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/49e93d80-9a3e-449e-bbd4-9a007b0782dcn%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/CAAV1gMDJt5hS11_P%3D7Z76Y3u-56AEP-_fvtQAJZHG8RU3%2BM_cQ%40mail.gmail.com.

Re: [tw5] Re: Three remaining conundrums

[Charlie Veniot]

You are talking my language:  knowing just enough to be dangerous.

World domination.  I'll cede that job to you, because my attempt might have 
an odeur of Dr. Evil or Megamind.

Armed with a couple of extra tricks up your sleeves, I am cheering you on:  
Tame them intertwingularity Goliath's.

Huh, movie title:  David and the Intertwingularity Goliath's.  Or a very 
strange rock band.

On Tuesday, May 4, 2021 at 9:19:22 AM UTC-3 David Gifford wrote:

> Hey Charles I finally tried your second solution this morning. THIS is 
> exactly, precisely, particularly what I needed.
>
> And studying this will help me learn to do many wonderful and dangerous 
> things! World domination is a step closer!
>
> On Monday, May 3, 2021 at 8:27:57 PM UTC-5 cj.v...@gmail.com wrote:
>
>> Poop.  I missed the starting pistol.
>>
>> As before, you supply "Tiddler A."  And you will want to alter the 
>> "ThisPrefix" and "ThisSuffix" macros in "Add Tiddler A Content" tiddler.
>>
>> Cheers !
>>
>>


-- 
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/ab1ed4bb-b673-4770-9c0f-0fdbeaee4489n%40googlegroups.com.

Re: [tw5] Re: Default Tiddler Configuration

[PMario]

Hi,
Have a look at the image from my first post. There is a marker, that says 
"click". ... 

It should be possible to create a "New Edit with Template" button. ... But 
I didn't do that. I did recycle the code from this thread: 
https://groups.google.com/g/tiddlywiki/c/sQr3OJwnj8I/m/Qnv_Z9KsAgAJ

-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/0660117e-eee4-4b15-a856-235307c414b4n%40googlegroups.com.

[tw5] Re: action-delefield et json

[PMario]

On Tuesday, May 4, 2021 at 2:02:06 PM UTC+2 jn.pierr...@gmail.com wrote:
...

> and why is there not any $acion-deleteindex?
>

IMO because, if users know how to do it, they use the existing 
functionality.

-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/ed6f1fe4-64e5-48fa-856a-0fc49def9dbcn%40googlegroups.com.

[tw5] Re: action-delefield et json

[PMario]

On Tuesday, May 4, 2021 at 2:02:06 PM UTC+2 jn.pierr...@gmail.com wrote:

> thus to get rid of "foo" in my previous example all I have to do is:
> <$action-setfield $tiddler="data" $index="foo"/>
>

Right, that's a bit strange. 
 

> this possibility should be recalled in the doc of $action-deletefield.
>

Or $action-deletefield should get a $index parameter, because I think 
that's the function where users would expect it. 
Right?

-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/bff0fd84-e5ea-4293-a24a-b6bf4dc14e78n%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[PMario]

On Tuesday, May 4, 2021 at 12:26:30 PM UTC+2 jn.pierr...@gmail.com wrote:

> ".." is commonly used in describing a continuation, for instance 3..7 is 
> for 3, 4, 5, 6, 7. 


> IMO the proposed use of .. is then counter-intuitive.
>

I don't think so. We probably don't use field names 3..7. We use 
field-name..meta-data ... I don't see a problem there. 

Everything else dosn't look good, is forbidden or is hard to write. 

If we use dots in regexp, we need to escape them anyway. So there shouldn't 
be a problem with regexps. 

just my thoughts. 
-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/09684b6b-a4c0-45c2-b01c-25441a3f051cn%40googlegroups.com.

[tw5] twexe (the plugin) update

[James Anderson]

Incase any windows/hta users still use this:

I've updated this plugin. the source is here: 
https://github.com/welford/twexe and you can grab a copy of the updated 
plugin from http://welford.github.io/

The big change is that you can run the contents of a tiddler as a batch 
file, which should help keep things portable (between machines / 
environments, not cross platform). 

It will create a temporary twexe.bat file in %TEMP% fill it with the 
contents of the tiddler and then run it. You can change the default 
temporary location via  $:/plugins/welford/twexe/tmpdir

in the attached image i have two examples, one will run my local node.js 
tw, the other just an example batch file that prints hello and the first 
arg passed to it.

-- 
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/49e93d80-9a3e-449e-bbd4-9a007b0782dcn%40googlegroups.com.

Re: [tw5] Re: Three remaining conundrums

[David Gifford]

Hey Charles I finally tried your second solution this morning. THIS is 
exactly, precisely, particularly what I needed.

And studying this will help me learn to do many wonderful and dangerous 
things! World domination is a step closer!

On Monday, May 3, 2021 at 8:27:57 PM UTC-5 cj.v...@gmail.com wrote:

> Poop.  I missed the starting pistol.
>
> As before, you supply "Tiddler A."  And you will want to alter the 
> "ThisPrefix" and "ThisSuffix" macros in "Add Tiddler A Content" tiddler.
>
> Cheers !
>
>
>>>

-- 
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/bcd32a76-de62-40af-8feb-dea2ae4700c8n%40googlegroups.com.

[tw5] Re: filter to get tiddlers newer than a given date

[James Anderson]

thanks Tones, that is also useful!

On Tuesday, 4 May 2021 at 09:46:56 UTC+1 TW Tones wrote:

> James,
>
> You can also use the days operator, but it is a little tricky to use.
>
> Tones
>
> On Tuesday, 4 May 2021 at 18:22:21 UTC+10 james.w@gmail.com wrote:
>
>>
>> Thanks! This seems to be what i am after :)
>> On Tuesday, 4 May 2021 at 09:01:28 UTC+1 saq.i...@gmail.com wrote:
>>
>>> Try this:
>>>
>>> [all[tiddlers]] :filter[get[modified]compare:date:gt[2021]]
>>>
>>> On Tuesday, May 4, 2021 at 9:09:42 AM UTC+2 james.w@gmail.com wrote:
>>>
 Hey Mark,

 that doesn't seem to work in the advances search filters tab (see 
 attachment) I assume it won't work with $tw.wiki.filterTiddlers in a 
 plugin 
 either.

 >TW Tones
 if you put this into the seach box in the image i attached hopefully 
 it's clearer [all[tiddlers]get[modified]compare:date:gt[2021]] 

 I would just like a way to return a list of tiddlers older or newer 
 than a given date (though the date might be a custom field in the future)

 Thanks

 James




 On Tuesday, 4 May 2021 at 03:30:17 UTC+1 Mark S. wrote:

> You need the "filter" operator which is actually a subfilter operator. 
> It requires you to pre-specify the inner filter with a variable:
>
> <$vars myfilt="[get[modified]compare:date:gt[2021]]">
> <]">>
> 
>
>
>
> On Monday, May 3, 2021 at 3:56:30 PM UTC-7 james.w@gmail.com 
> wrote:
>
>> Hello,
>>
>> I've tried [all[tiddlers]get[modified]compare:date:gt[2021]] in 
>> advanced search but this seems to give me links to tiddlers named after 
>> modified field
>>
>> eventually would like to do this in a plugin via 
>> $tw.wiki.filterTiddlers, is there a way to do this in the advanced 
>> search 
>> on the filters tab? If nto what is the best way to do this in a widget?
>>
>>
>> thanks,
>> James
>>
>

-- 
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/d10a5990-cd40-46de-83b6-53279fdd9253n%40googlegroups.com.

[tw5] Re: action-delefield et json

[Jean-Pierre Rivière]

Resolved my problem.

to delete a fied or an index, you can (and in json that's an index, so it's 
"you must") use $action/setfield without specifying any $value.

thus to get rid of "foo" in my previous example all I have to do is:

<$action-setfield $tiddler="data" $index="foo"/>

this possibility should be recalled in the doc of $action-deletefield.

and why is there not any $acion-deleteindex?

Le lundi 3 mai 2021 à 22:45:29 UTC+2, Jean-Pierre Rivière a écrit :

> I have  tiddler "data" of json data like 
>
> {
>   "foo": { ... },
>   "bar": { ... }
> }
>
> I want to get rid of "foo".
>
> so I have setup a $button where the action is
>
> <$action-deletefield $tiddler="data" $field="foo"/>
>
> the action does nothing (if I set an action-deletefield instead, it works 
> so the problem is just the deletefield widget).
>
> any idea?
>
>

-- 
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/9b08558c-6dff-4e7c-a6fc-25d0fa018a2an%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[Jean-Pierre Rivière]

oups. forgot that restriction. I mostly work with indexes (greater liberty 
for names)

what about main. and main._.sub ? ._. is seen nowhere else and is rather 
cute and evoke a SUBtil smile.

Le mardi 4 mai 2021 à 13:45:46 UTC+2, TW Tones a écrit :

> jean-Pierre
>
> Field Names are quite limited
>
> *TiddlerFields are name:value pairs that make up a [[tiddler|Tiddlers]]. 
> Field names must be lowercase letters, digits or the characters `-` (dash), 
> `_` (underscore) and `.` (period).*
> https://tiddlywiki.com/#TiddlerFields
>
> The .. considered as continuation actually works from my perspective eg 
> url.. is continued elsewhere in url..name.
>
> In answer to your question, yes they should be regular fields you can use 
> in every other way if possible. The question is what is the defacto 
> standard and how do we best implement support for such fields. Can we 
> provide a generic solution?
>
> Tones
>
>
> On Tuesday, 4 May 2021 at 20:26:30 UTC+10 jn.pierr...@gmail.com wrote:
>
>> ".." is commonly used in describing a continuation, for instance 3..7 is 
>> for 3, 4, 5, 6, 7.
>>
>> IMO the proposed use of .. is then counter-intuitive.
>>
>> I prefer a simple dot.
>>
>> We could use an arrow but -> is awkward in an html oriented language so 
>> it's a no-starter.
>>
>> We could use ^ but it may interfer in regexp. it would probably be no big 
>> deal though.
>>
>> We could have a mix. for instance:
>>
>> main field is "date."
>> sub-fields are "date.^value" or "date.^format" or "date.^units".
>>
>> the other way around:
>>
>> main field is "date^"
>> sub-fields are "date^.value" or "date^.format" or "date^.units".
>>
>> question: are sub-fields regular fields in the end, just being taken in 
>> charge by a set of ad-hoc macros and filters and templates? there would be 
>> a lot to tinker depending of the choces being made. or are sub-field a 
>> brand new mechanism of 1st-class core components?
>>
>> just suggestions...
>>
>> -- 
>> Jean-Pierre
>> Le mardi 4 mai 2021 à 11:32:04 UTC+2, PMario a écrit :
>>
>>> On Tuesday, May 4, 2021 at 11:27:49 AM UTC+2 PMario wrote:
>>>
>>> I still want to have  sec-expanded-years 
  as in 
 https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/jpQJrSi8BwAJ
 and: SI prefix multipliers 
 
  
 as in: 
 https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/l5S9-TnaBwAJ 
 from the same thread. 

>>>
>>> And I want, that TW-fields can handle this. eg: long-ago..from, 
>>> long-ago..to   
>>>
>>> just an idea ;)
>>> -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/87975951-64d7-4fa5-873d-e9d52b565ba6n%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[TW Tones]

jean-Pierre

Field Names are quite limited

*TiddlerFields are name:value pairs that make up a [[tiddler|Tiddlers]]. 
Field names must be lowercase letters, digits or the characters `-` (dash), 
`_` (underscore) and `.` (period).*
https://tiddlywiki.com/#TiddlerFields

The .. considered as continuation actually works from my perspective eg 
url.. is continued elsewhere in url..name.

In answer to your question, yes they should be regular fields you can use 
in every other way if possible. The question is what is the defacto 
standard and how do we best implement support for such fields. Can we 
provide a generic solution?

Tones


On Tuesday, 4 May 2021 at 20:26:30 UTC+10 jn.pierr...@gmail.com wrote:

> ".." is commonly used in describing a continuation, for instance 3..7 is 
> for 3, 4, 5, 6, 7.
>
> IMO the proposed use of .. is then counter-intuitive.
>
> I prefer a simple dot.
>
> We could use an arrow but -> is awkward in an html oriented language so 
> it's a no-starter.
>
> We could use ^ but it may interfer in regexp. it would probably be no big 
> deal though.
>
> We could have a mix. for instance:
>
> main field is "date."
> sub-fields are "date.^value" or "date.^format" or "date.^units".
>
> the other way around:
>
> main field is "date^"
> sub-fields are "date^.value" or "date^.format" or "date^.units".
>
> question: are sub-fields regular fields in the end, just being taken in 
> charge by a set of ad-hoc macros and filters and templates? there would be 
> a lot to tinker depending of the choces being made. or are sub-field a 
> brand new mechanism of 1st-class core components?
>
> just suggestions...
>
> -- 
> Jean-Pierre
> Le mardi 4 mai 2021 à 11:32:04 UTC+2, PMario a écrit :
>
>> On Tuesday, May 4, 2021 at 11:27:49 AM UTC+2 PMario wrote:
>>
>> I still want to have  sec-expanded-years 
>>>  as in 
>>> https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/jpQJrSi8BwAJ
>>> and: SI prefix multipliers 
>>> 
>>>  
>>> as in: 
>>> https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/l5S9-TnaBwAJ 
>>> from the same thread. 
>>>
>>
>> And I want, that TW-fields can handle this. eg: long-ago..from, 
>> long-ago..to   
>>
>> just an idea ;)
>> -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/cd0cbc47-52cf-4875-a126-a90c02233b66n%40googlegroups.com.

Re: [tw5] Re: Default Tiddler Configuration

[Jax Kovak]

Ah! I forgot to mention that I have already edited the 
*language/MissingTiddler/Hint* as well.

When I click a missing tiddler link I get as far as seeing the new tiddler, 
with the correct name and it contains the contents of the 
MissingTiddler/Hint, but when opened with the normal edit button or the 
NewHere button added by the imported script, the tiddler remains empty when 
opened, which suggests that when it gets opened something is removing the 
contents..

I cant see that it would matter much but I am using TiddlyDesktop. 

It is most frustrating.

Regards

JK

On Tuesday, 4 May 2021 at 03:34:01 UTC+1 PMario wrote:

> Hi,
> See the instructions at: 
> https://groups.google.com/g/tiddlywiki/c/tf-7T3zxEo0/m/qOR8yPFNAwAJ  You 
> need to change the 
> https://tiddlywiki.com/#%24%3A%2Flanguage%2FMissingTiddler%2FHint  
> tiddler too.
> -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/23e63cc0-608a-4a50-b98e-6f5488357bf1n%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[Jean-Pierre Rivière]

".." is commonly used in describing a continuation, for instance 3..7 is 
for 3, 4, 5, 6, 7.

IMO the proposed use of .. is then counter-intuitive.

I prefer a simple dot.

We could use an arrow but -> is awkward in an html oriented language so 
it's a no-starter.

We could use ^ but it may interfer in regexp. it would probably be no big 
deal though.

We could have a mix. for instance:

main field is "date."
sub-fields are "date.^value" or "date.^format" or "date.^units".

the other way around:

main field is "date^"
sub-fields are "date^.value" or "date^.format" or "date^.units".

question: are sub-fields regular fields in the end, just being taken in 
charge by a set of ad-hoc macros and filters and templates? there would be 
a lot to tinker depending of the choces being made. or are sub-field a 
brand new mechanism of 1st-class core components?

just suggestions...

-- 
Jean-Pierre
Le mardi 4 mai 2021 à 11:32:04 UTC+2, PMario a écrit :

> On Tuesday, May 4, 2021 at 11:27:49 AM UTC+2 PMario wrote:
>
> I still want to have  sec-expanded-years 
>>  as in 
>> https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/jpQJrSi8BwAJ
>> and: SI prefix multipliers 
>> 
>>  
>> as in: 
>> https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/l5S9-TnaBwAJ from 
>> the same thread. 
>>
>
> And I want, that TW-fields can handle this. eg: long-ago..from, 
> long-ago..to   
>
> just an idea ;)
> -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/39d164b7-cbaa-418e-8987-959bee5c7c77n%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[PMario]

On Tuesday, May 4, 2021 at 11:27:49 AM UTC+2 PMario wrote:

I still want to have  sec-expanded-years 
>  as in 
> https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/jpQJrSi8BwAJ
> and: SI prefix multipliers 
> 
>  
> as in: https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/l5S9-TnaBwAJ 
> from the same thread. 
>

And I want, that TW-fields can handle this. eg: long-ago..from, 
long-ago..to   

just an idea ;)
-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/c6d6916a-6f71-4969-b6b1-4e7cf964a4f3n%40googlegroups.com.

Re: [tw5] improving smart resarch for in-situ macros for filter

[TW Tones]

Jean-Pierre / Jeremy,

The approach would possibly be a one off, new tab in advanced search, 
cloned from the filters tab ($:/core/ui/AdvancedSearch/Filter), edited to 
allow extra variables to be set, then used in the search.

Or a global macro to set the variables.

Easy  customisation for special use cases are everywhere in tiddlywiki. :)

Tones

On Tuesday, 4 May 2021 at 17:58:15 UTC+10 Jeremy Ruston wrote:

> Hi Jean-Pierre
>
> The idea of being able to specify variables for use in the advanced 
> “filter” search has come up before, and is worth considering. My concern 
> would be that using variables is relatively rare, and thus I wouldn’t like 
> to make the default UI more complex.
>
> It’s also worth noting that your example can be done directly without 
> variables:
>
> [field:type[application/javascript]]
>
> Best wishes
>
> Jeremy.
>
>
> On 4 May 2021, at 08:50, TW Tones  wrote:
>
> Jean-Pierre,
>
> On the first filter consider;
>
> {{{  [all[]get[type]match[application/javascript]then] }}}
>
> Untested, This should list the tiddlernames of the selected tiddlers 
> (those with  [type]match[application/javascript])
> Is that pArt of the problem.
>
> I believe you can conditionally call macros, wrap them in a list or reveal 
> widget.?
>
> Tones
>
>
>
> On Tuesday, 4 May 2021 at 17:42:30 UTC+10 jn.pierr...@gmail.com wrote:
>
>> Today I wanted to see which tiddlers I have that are javascript.
>>
>> In advanced research i can execute something like
>>
>> [get[type]match[application/javascript]]
>>
>> but it would only bring "application/javascript"
>>
>> I can't have [filter[get[type]match[application/javascript]]]
>>
>> because this is gross syntax error.
>>
>> But if I had access to another input ext for a macro to be called extra I 
>> could do
>>
>> extra : [get[type]match[application/javascript]]
>> research : filtersortan[]
>>
>> and the job would be done.
>>
>> BTW, I think a standard "nop" macro doing nothing would be useful. I'm 
>> using it many times when I have to decide for an eventual treatment, for 
>> (actual real) instance:
>>
>> \define deleteProjectNewAltjson(target id)
>> <$action-log $$message="delete project «$target$##$id$»"/>
>> <$action-deletefield $tiddler="$target$" $field="$id$"/>
>> <$set name=next-step 
>> filter="[getindex]then[_kludge4deleteProjectNewAltjson]else[nop]]">
>> <>
>> 
>> <$action-log $$message="deleted project «$target$##$id$»"/>
>> \end
>>
>> (this concerns a potential bug for impossibility to delete a property of 
>> first level within a json object tiddler -- there is a separate thread I 
>> fielded yesterday for that)
>>
>> I have not seen any other way to have a conditional call to a macro.
>>
>> regards,
>>
>> -- 
>> Jean-Pierre
>>
>
> -- 
> 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/e0b372f9-39f2-4268-a31b-2d71cfa130een%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/b767e424-694a-4430-9ef8-37e9e3e3e1c5n%40googlegroups.com.

Re: [tw5] A basket on the sidebar

[Mohammad Rahmani]

There was two mistakes in previous post I have corrected and attached again
the myBasket.json
- remove button tooltip corrected
- remove button now works

Best wishes
Mohammad

On Tue, May 4, 2021 at 11:22 AM Mohammad Rahmani 
wrote:

> Hi Atro,
>
> Very nice question and a lot of use cases!!
>
> You get two solutions from Soren and Tones!
> The Soren solution implements a real basket !  Soren said it is* a lazy
> solution*! I want to see if I can be lazier! *;-)*
>
> *Third solution*
>
>1. Clone the Open tab in the sidebar ( $:/core/ui/SideBar/Open  )
>2. rename it to "myBasket"
>3. change the caption to Basek (I named it Atro Basket for *Atronoush*)
>4. make small change (e.g set the tv-story-list to myBasket to use it
>instead of TW tv-story-list)
>5. change close all to clear all to clear the list of myBasket
>6. add an export button to export tiddlers in basket (e.g listed in
>myBasket list field)
>7. make your button *draggable* (for example use dragFilter)
>
> *How it works*
>
>1. Open the Atro Basket in the sidebar  (see attached file)
>2. add items to Basket in different ways like below
>   1. drag and drop links, titles to Basket
>   2. drag a tag pill to add all tiddler with that tag
>   3. if you are not happy click *clear all* to remove all tiddlers in
>   basket
>   4. if you like remove any item click the *remove button*
>3. Export
>   1. click export button to export json (all tiddlers in the basket
>   as json) OR
>   2. drag and drop the export button to other wiki to import all
>   tiddlers in basket to your wiki  (your button is draggable)
>   3. when finished! if you like to empty the Basket, click clear all
>
>
> I have attached the working tiddler here! Drop into
> https://tiddlywiki.com/ and see how it works!
>
> Best wishes
> Mohammad
>
>
> On Tue, May 4, 2021 at 1:38 AM Atronoush Parsi 
> wrote:
>
>> Is there any script or plugin with
>>
>> - a sidebar tab (I call it basket)
>> - drag and drop features! One can drag a tiddler (e.g title) into the
>> basket
>> - when finished press a button to export as JSON
>> - the button can be dragged and drop into another wiki!
>>
>> The last part is what you see in TW-Icons
>>
>>
>> -Atro
>>
>> --
>> 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/CAKHVXmoDHTtqMgUcp2ob%3DvHt6_nwBJbM2S4fOCi0gMraE3wEOA%40mail.gmail.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/CAAV1gMCvxC%3DGeWNWumH%3Dm37UzvFmtaXQ-K0Xd_sgY-ZsAOLRcA%40mail.gmail.com.


myBasket-rev2.json
Description: application/json

[tw5] Re: [Discussion] Field Related or subFields

[PMario]

Hi,

I still want to have  sec-expanded-years 
 as in 
https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/jpQJrSi8BwAJ
and: SI prefix multipliers 

 
as in: https://groups.google.com/g/tiddlywiki/c/YaFzHXfjnFc/m/l5S9-TnaBwAJ 
from the same thread. 

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/a9cc245d-c8a5-42ca-8a3d-24a83d2bd44dn%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[PMario]

On Tuesday, May 4, 2021 at 9:44:50 AM UTC+2 TW Tones wrote:
... 

> I can share some examples of my prior work on this is anyone is interested.
>

That would be nice!

But I want to get a bit further. If we define due-date..type: date   
Something like this should be possible.

<$action-setfield $tiddler=xx $field="due-date.." $value="Sept 20th" />  
the result should be

due-date.. = 20120920because: somewhere we have due-date..: 2021 
due-date..edit-template:" mmm DDth" 

This would allows us to define sensible defaults.  
due-date..edit-template:{{date-format}} should be possible too in a second 
step 

I also want to be able to use: long-ago..type: x   that understands. 
500 mil years ago

just dreaming
-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/3b4e79ae-4829-48ea-9399-0a38dbcecde1n%40googlegroups.com.

Re: [tw5] Re: Ten Ways to Drag and Drop Tiddlers to Tiddlywiki

[Mohammad Rahmani]

Thank you Tones! Lovely!



Best wishes
Mohammad


On Tue, May 4, 2021 at 12:40 PM TW Tones  wrote:

>
>1. Drag a tiddler from one wiki to another
>2. Export a tiddler as a tid file and drag and drop the tid file on
>any wiki
>3. Any title can be dropped on the text field in edit mode to add it
>to the text
>4. Export a set of tiddlers as a JSON file and drag and drop the JSON
>file on any wiki
>5. Drag and drop multiple tiddlers on a wiki, the $:/import tiddler is
>opened, rename the $:./import tiddler and remove its fields. You now have a
>JSON tiddler containing all the tiddlers that were in the import.
>6. Drag and drop plugins (of course) to install.
>7. add Mohammads items
>8. Drop tiddlers or text on suitably configured buttons
>9. ...
>
>
> On Tuesday, 4 May 2021 at 17:50:01 UTC+10 Mohammad wrote:
>
>> Drag and drop contents into Tiddlywiki for importing and exporting
>> contents is one of the amazing features of Tiddlywiki, it is not known as
>> it deserved.
>>
>> To bring the power into attention I asked the above question and I am
>> looking forward to see how others use this feature!
>>
>>
>>
>> Best wishes
>> Mohammad
>>
> --
> 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/6bfb5cf6-ed5c-4c66-9d2d-6b60016d3936n%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/CAAV1gMDFR64ooiZoDSh6ty_cJxRaKPtLwoXyOav%2BuCX%2B%3DPUfDA%40mail.gmail.com.

[tw5] Re: filter to get tiddlers newer than a given date

[TW Tones]

James,

You can also use the days operator, but it is a little tricky to use.

Tones

On Tuesday, 4 May 2021 at 18:22:21 UTC+10 james.w@gmail.com wrote:

>
> Thanks! This seems to be what i am after :)
> On Tuesday, 4 May 2021 at 09:01:28 UTC+1 saq.i...@gmail.com wrote:
>
>> Try this:
>>
>> [all[tiddlers]] :filter[get[modified]compare:date:gt[2021]]
>>
>> On Tuesday, May 4, 2021 at 9:09:42 AM UTC+2 james.w@gmail.com wrote:
>>
>>> Hey Mark,
>>>
>>> that doesn't seem to work in the advances search filters tab (see 
>>> attachment) I assume it won't work with $tw.wiki.filterTiddlers in a plugin 
>>> either.
>>>
>>> >TW Tones
>>> if you put this into the seach box in the image i attached hopefully 
>>> it's clearer [all[tiddlers]get[modified]compare:date:gt[2021]] 
>>>
>>> I would just like a way to return a list of tiddlers older or newer than 
>>> a given date (though the date might be a custom field in the future)
>>>
>>> Thanks
>>>
>>> James
>>>
>>>
>>>
>>>
>>> On Tuesday, 4 May 2021 at 03:30:17 UTC+1 Mark S. wrote:
>>>
 You need the "filter" operator which is actually a subfilter operator. 
 It requires you to pre-specify the inner filter with a variable:

 <$vars myfilt="[get[modified]compare:date:gt[2021]]">
 <]">>
 



 On Monday, May 3, 2021 at 3:56:30 PM UTC-7 james.w@gmail.com wrote:

> Hello,
>
> I've tried [all[tiddlers]get[modified]compare:date:gt[2021]] in 
> advanced search but this seems to give me links to tiddlers named after 
> modified field
>
> eventually would like to do this in a plugin via 
> $tw.wiki.filterTiddlers, is there a way to do this in the advanced search 
> on the filters tab? If nto what is the best way to do this in a widget?
>
>
> thanks,
> James
>


-- 
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/1c0ab91d-ed6a-452d-9e04-2727d193e499n%40googlegroups.com.

Re: [tw5] Re: A basket on the sidebar

[Atronoush Parsi]

@Soren
Lovely solution! Works great for me and I like the possiblity to add tags
before export. In the target wiki I can recognize what I imported

@Tones
I love your solution! I can have several basket in this way

@Mohmmad
WOW, I learnt I can use TW elemnts theirslves and I can shape  them for my
use case.
I love the draggable button! I can export to a file, or drag the button to
target wiki! Amazing!!


Thank you all! While I am very happy with all these solutions., I really
appreciate the help of this wonderful community!

--Atro

On Tue, May 4, 2021 at 3:44 AM Soren Bjornstad 
wrote:

> Here's a simple version. Put it in a tiddler called Basket and tag it
> $:/tags/SideBar:
>
> \define apply-tag() <$list filter={{Basket!!list}}><$action-listops
> $tags="Basket"/>
> \define clear-tag() <$list filter="[tag[Basket]]"><$action-listops
> $tags="-Basket"/><$action-setfield $tiddler="Basket" list=""/>
> \define export-basket() <$action-sendmessage $message="tm-download-file"
> $param="$:/core/templates/exporters/JsonFile" exportFilter={{Basket!!list}}
> filename=<>/>
>
> Basket (drag tiddlers here):
>
> <>
>
> <$button actions=<> tooltip="Add the 'Basket' tag to all items
> in the basket.">Apply tag
> <>
> <$button actions=<> tooltip="Export all the items in the
> basket to a JSON file.">Export JSON
> <$button actions=<> tooltip="Remove the 'Basket' tag from all
> items and clear the basket list.">Empty basket
>
> The list-links-draggable widget allows you to drag and drop tiddlers
> (putting this as a sidebar tab might make it a little hard to source
> tiddlers to drag though -- maybe better to put it somewhere else!). Those
> will be stored in the list field of the Basket tiddler. Then the "Apply
> Tag" button lets you tag each of those tiddlers, if you so desire. You can
> then drag and drop the tag into a different wiki to copy the tiddlers, or
> use the Export JSON button to export a JSON file. The empty button will
> remove the Basket tag from all tiddlers where it's used and clear out the
> list.
>
> Opportunities for improvement:
>
>- It would be possible to roll something using the $dropzone widget
>that would automatically add the tag and eliminate the need for the "Apply
>Tag" step. I was feeling lazy and wanted to use list-links-draggable.
>- You might consider temporarily turning off timestamps while tagging
>and untagging things so that they don't show up as modified just because
>you were selecting them (not sure if there's a way to do that with an
>action tiddler).
>- The interface here leaves something to be desired, but should be
>functional.
>
> On Monday, May 3, 2021 at 4:08:06 PM UTC-5 Atronoush wrote:
>
>> Is there any script or plugin with
>>
>> - a sidebar tab (I call it basket)
>> - drag and drop features! One can drag a tiddler (e.g title) into the
>> basket
>> - when finished press a button to export as JSON
>> - the button can be dragged and drop into another wiki!
>>
>> The last part is what you see in TW-Icons
>>
>>
>> -Atro
>>
>> --
> 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/779bfc4d-b938-41a3-839e-213b5cd2d7dcn%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/CAKHVXmqxe9j_J1mW5Qhsbg-mNNZm6NHqnN1MHB_F1W-JjYvEmQ%40mail.gmail.com.

[tw5] Re: filter to get tiddlers newer than a given date

[James Anderson]

Thanks! This seems to be what i am after :)
On Tuesday, 4 May 2021 at 09:01:28 UTC+1 saq.i...@gmail.com wrote:

> Try this:
>
> [all[tiddlers]] :filter[get[modified]compare:date:gt[2021]]
>
> On Tuesday, May 4, 2021 at 9:09:42 AM UTC+2 james.w@gmail.com wrote:
>
>> Hey Mark,
>>
>> that doesn't seem to work in the advances search filters tab (see 
>> attachment) I assume it won't work with $tw.wiki.filterTiddlers in a plugin 
>> either.
>>
>> >TW Tones
>> if you put this into the seach box in the image i attached hopefully it's 
>> clearer [all[tiddlers]get[modified]compare:date:gt[2021]] 
>>
>> I would just like a way to return a list of tiddlers older or newer than 
>> a given date (though the date might be a custom field in the future)
>>
>> Thanks
>>
>> James
>>
>>
>>
>>
>> On Tuesday, 4 May 2021 at 03:30:17 UTC+1 Mark S. wrote:
>>
>>> You need the "filter" operator which is actually a subfilter operator. 
>>> It requires you to pre-specify the inner filter with a variable:
>>>
>>> <$vars myfilt="[get[modified]compare:date:gt[2021]]">
>>> <]">>
>>> 
>>>
>>>
>>>
>>> On Monday, May 3, 2021 at 3:56:30 PM UTC-7 james.w@gmail.com wrote:
>>>
 Hello,

 I've tried [all[tiddlers]get[modified]compare:date:gt[2021]] in 
 advanced search but this seems to give me links to tiddlers named after 
 modified field

 eventually would like to do this in a plugin via 
 $tw.wiki.filterTiddlers, is there a way to do this in the advanced search 
 on the filters tab? If nto what is the best way to do this in a widget?


 thanks,
 James

>>>

-- 
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/0bfd3cc1-fc74-4654-9cce-2f41d7c3618bn%40googlegroups.com.

[tw5] Re: Ten Ways to Drag and Drop Tiddlers to Tiddlywiki

[TW Tones]

   
   1. Drag a tiddler from one wiki to another
   2. Export a tiddler as a tid file and drag and drop the tid file on any 
   wiki
   3. Any title can be dropped on the text field in edit mode to add it to 
   the text
   4. Export a set of tiddlers as a JSON file and drag and drop the JSON 
   file on any wiki
   5. Drag and drop multiple tiddlers on a wiki, the $:/import tiddler is 
   opened, rename the $:./import tiddler and remove its fields. You now have a 
   JSON tiddler containing all the tiddlers that were in the import.
   6. Drag and drop plugins (of course) to install.
   7. add Mohammads items
   8. Drop tiddlers or text on suitably configured buttons
   9. ...


On Tuesday, 4 May 2021 at 17:50:01 UTC+10 Mohammad wrote:

> Drag and drop contents into Tiddlywiki for importing and exporting 
> contents is one of the amazing features of Tiddlywiki, it is not known as 
> it deserved.
>
> To bring the power into attention I asked the above question and I am 
> looking forward to see how others use this feature!
>
>
>
> Best wishes
> Mohammad
>

-- 
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/6bfb5cf6-ed5c-4c66-9d2d-6b60016d3936n%40googlegroups.com.

Re: [tw5] Re: Ten Ways to Drag and Drop Tiddlers to Tiddlywiki

[Mohammad Rahmani]

Hi Saq,


On Tue, May 4, 2021 at 12:28 PM Saq Imtiaz  wrote:

> Speaking of drag and drop, I was expecting to see some dropzone magic with
> bibtex paste/drop ? :)


Ah! I forgot about it and yes it is an amazing new feature added by you!
The new dropzone capability to deserize content brought us many new
opportunities and it deserves to be discussed in detail!
I will open a new thread and will discuss it!





>
>
> On Tuesday, May 4, 2021 at 9:53:55 AM UTC+2 Mohammad wrote:
>
>> 1. drag and drop a tiddler link
>> 2. drag and drop a tag pill
>> 3. drag and drop a $button with dragFilter
>> 4. drag and drop a $button with dragTiddler
>> 5. a $draggable widget
>> 6. drag a tiddler to browser bookmark and later drag into another wiki
>> 7.
>> 8.
>> 9.
>> 10.
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Tue, May 4, 2021 at 12:19 PM Mohammad Rahmani 
>> wrote:
>>
>>> Drag and drop contents into Tiddlywiki for importing and exporting
>>> contents is one of the amazing features of Tiddlywiki, it is not known as
>>> it deserved.
>>>
>>> To bring the power into attention I asked the above question and I am
>>> looking forward to see how others use this feature!
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>> --
> 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/3ab9fb44-7fbc-4888-aac7-65bcb08e55c3n%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/CAAV1gMCX8rnKkP%2BzRPR-sderhCX7%2B%2BSZQdfq82TdMwp1tjCkng%40mail.gmail.com.

[tw5] Re: filter to get tiddlers newer than a given date

[Saq Imtiaz]

Try this:

[all[tiddlers]] :filter[get[modified]compare:date:gt[2021]]

On Tuesday, May 4, 2021 at 9:09:42 AM UTC+2 james.w@gmail.com wrote:

> Hey Mark,
>
> that doesn't seem to work in the advances search filters tab (see 
> attachment) I assume it won't work with $tw.wiki.filterTiddlers in a plugin 
> either.
>
> >TW Tones
> if you put this into the seach box in the image i attached hopefully it's 
> clearer [all[tiddlers]get[modified]compare:date:gt[2021]] 
>
> I would just like a way to return a list of tiddlers older or newer than a 
> given date (though the date might be a custom field in the future)
>
> Thanks
>
> James
>
>
>
>
> On Tuesday, 4 May 2021 at 03:30:17 UTC+1 Mark S. wrote:
>
>> You need the "filter" operator which is actually a subfilter operator. It 
>> requires you to pre-specify the inner filter with a variable:
>>
>> <$vars myfilt="[get[modified]compare:date:gt[2021]]">
>> <]">>
>> 
>>
>>
>>
>> On Monday, May 3, 2021 at 3:56:30 PM UTC-7 james.w@gmail.com wrote:
>>
>>> Hello,
>>>
>>> I've tried [all[tiddlers]get[modified]compare:date:gt[2021]] in advanced 
>>> search but this seems to give me links to tiddlers named after modified 
>>> field
>>>
>>> eventually would like to do this in a plugin via 
>>> $tw.wiki.filterTiddlers, is there a way to do this in the advanced search 
>>> on the filters tab? If nto what is the best way to do this in a widget?
>>>
>>>
>>> thanks,
>>> James
>>>
>>

-- 
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/297c25c2-a0f5-42c6-b94c-f8503b028e92n%40googlegroups.com.

[tw5] Re: Ten Ways to Drag and Drop Tiddlers to Tiddlywiki

[Saq Imtiaz]

Speaking of drag and drop, I was expecting to see some dropzone magic with 
bibtex paste/drop ? :)


On Tuesday, May 4, 2021 at 9:53:55 AM UTC+2 Mohammad wrote:

> 1. drag and drop a tiddler link
> 2. drag and drop a tag pill
> 3. drag and drop a $button with dragFilter
> 4. drag and drop a $button with dragTiddler
> 5. a $draggable widget
> 6. drag a tiddler to browser bookmark and later drag into another wiki
> 7.
> 8.
> 9.
> 10.
>
> Best wishes
> Mohammad
>
>
> On Tue, May 4, 2021 at 12:19 PM Mohammad Rahmani  
> wrote:
>
>> Drag and drop contents into Tiddlywiki for importing and exporting 
>> contents is one of the amazing features of Tiddlywiki, it is not known as 
>> it deserved.
>>
>> To bring the power into attention I asked the above question and I am 
>> looking forward to see how others use this feature!
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>

-- 
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/3ab9fb44-7fbc-4888-aac7-65bcb08e55c3n%40googlegroups.com.

Re: [tw5] improving smart resarch for in-situ macros for filter

[Jeremy Ruston]

Hi Jean-Pierre

The idea of being able to specify variables for use in the advanced “filter” 
search has come up before, and is worth considering. My concern would be that 
using variables is relatively rare, and thus I wouldn’t like to make the 
default UI more complex.

It’s also worth noting that your example can be done directly without variables:

[field:type[application/javascript]]

Best wishes

Jeremy.


> On 4 May 2021, at 08:50, TW Tones  wrote:
> 
> Jean-Pierre,
> 
> On the first filter consider;
> 
> {{{  [all[]get[type]match[application/javascript]then] }}}
> 
> Untested, This should list the tiddlernames of the selected tiddlers (those 
> with  [type]match[application/javascript])
> Is that pArt of the problem.
> 
> I believe you can conditionally call macros, wrap them in a list or reveal 
> widget.?
> 
> Tones
> 
> 
> 
> On Tuesday, 4 May 2021 at 17:42:30 UTC+10 jn.pierr...@gmail.com 
>  wrote:
> Today I wanted to see which tiddlers I have that are javascript.
> 
> In advanced research i can execute something like
> 
> [get[type]match[application/javascript]]
> 
> but it would only bring "application/javascript"
> 
> I can't have [filter[get[type]match[application/javascript]]]
> 
> because this is gross syntax error.
> 
> But if I had access to another input ext for a macro to be called extra I 
> could do
> 
> extra : [get[type]match[application/javascript]]
> research : filtersortan[]
> 
> and the job would be done.
> 
> BTW, I think a standard "nop" macro doing nothing would be useful. I'm using 
> it many times when I have to decide for an eventual treatment, for (actual 
> real) instance:
> 
> \define deleteProjectNewAltjson(target id)
> <$action-log $$message="delete project «$target$##$id$»"/>
> <$action-deletefield $tiddler="$target$" $field="$id$"/>
> <$set name=next-step 
> filter="[getindex]then[_kludge4deleteProjectNewAltjson]else[nop]]">
> <>
> 
> <$action-log $$message="deleted project «$target$##$id$»"/>
> \end
> 
> (this concerns a potential bug for impossibility to delete a property of 
> first level within a json object tiddler -- there is a separate thread I 
> fielded yesterday for that)
> 
> I have not seen any other way to have a conditional call to a macro.
> 
> regards,
> 
> -- 
> Jean-Pierre
> 
> -- 
> 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/e0b372f9-39f2-4268-a31b-2d71cfa130een%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/EB2FC757-6E26-4AAA-84BB-25F62B3FB4FA%40gmail.com.

[tw5] Re: improving smart resarch for in-situ macros for filter

[Saq Imtiaz]

[all[tiddlers]] :filter[get[type]match[application/javascript]]


On Tuesday, May 4, 2021 at 9:42:30 AM UTC+2 jn.pierr...@gmail.com wrote:

> Today I wanted to see which tiddlers I have that are javascript.
>
> In advanced research i can execute something like
>
> [get[type]match[application/javascript]]
>
> but it would only bring "application/javascript"
>
> I can't have [filter[get[type]match[application/javascript]]]
>
> because this is gross syntax error.
>
> But if I had access to another input ext for a macro to be called extra I 
> could do
>
> extra : [get[type]match[application/javascript]]
> research : filtersortan[]
>
> and the job would be done.
>
> BTW, I think a standard "nop" macro doing nothing would be useful. I'm 
> using it many times when I have to decide for an eventual treatment, for 
> (actual real) instance:
>
> \define deleteProjectNewAltjson(target id)
> <$action-log $$message="delete project «$target$##$id$»"/>
> <$action-deletefield $tiddler="$target$" $field="$id$"/>
> <$set name=next-step 
> filter="[getindex]then[_kludge4deleteProjectNewAltjson]else[nop]]">
> <>
> 
> <$action-log $$message="deleted project «$target$##$id$»"/>
> \end
>
> (this concerns a potential bug for impossibility to delete a property of 
> first level within a json object tiddler -- there is a separate thread I 
> fielded yesterday for that)
>
> I have not seen any other way to have a conditional call to a macro.
>
> regards,
>
> -- 
> Jean-Pierre
>

-- 
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/8720d453-1be6-4bdb-be4b-28e627f7cf45n%40googlegroups.com.

[tw5] Re: Ten Ways to Drag and Drop Tiddlers to Tiddlywiki

[Mohammad Rahmani]

1. drag and drop a tiddler link
2. drag and drop a tag pill
3. drag and drop a $button with dragFilter
4. drag and drop a $button with dragTiddler
5. a $draggable widget
6. drag a tiddler to browser bookmark and later drag into another wiki
7.
8.
9.
10.

Best wishes
Mohammad


On Tue, May 4, 2021 at 12:19 PM Mohammad Rahmani 
wrote:

> Drag and drop contents into Tiddlywiki for importing and exporting
> contents is one of the amazing features of Tiddlywiki, it is not known as
> it deserved.
>
> To bring the power into attention I asked the above question and I am
> looking forward to see how others use this feature!
>
>
>
> Best wishes
> Mohammad
>

-- 
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/CAAV1gMB8dODdhDOFZge7y9kqd0mh0OKCn-HDPoDwnMhwYf%2Bwyg%40mail.gmail.com.

[tw5] Re: improving smart resarch for in-situ macros for filter

[TW Tones]

Jean-Pierre,

On the first filter consider;

{{{  [all[]get[type]match[application/javascript]then] }}}

Untested, This should list the tiddlernames of the selected tiddlers (those 
with  [type]match[application/javascript])
Is that pArt of the problem.

I believe you can conditionally call macros, wrap them in a list or reveal 
widget.?

Tones



On Tuesday, 4 May 2021 at 17:42:30 UTC+10 jn.pierr...@gmail.com wrote:

> Today I wanted to see which tiddlers I have that are javascript.
>
> In advanced research i can execute something like
>
> [get[type]match[application/javascript]]
>
> but it would only bring "application/javascript"
>
> I can't have [filter[get[type]match[application/javascript]]]
>
> because this is gross syntax error.
>
> But if I had access to another input ext for a macro to be called extra I 
> could do
>
> extra : [get[type]match[application/javascript]]
> research : filtersortan[]
>
> and the job would be done.
>
> BTW, I think a standard "nop" macro doing nothing would be useful. I'm 
> using it many times when I have to decide for an eventual treatment, for 
> (actual real) instance:
>
> \define deleteProjectNewAltjson(target id)
> <$action-log $$message="delete project «$target$##$id$»"/>
> <$action-deletefield $tiddler="$target$" $field="$id$"/>
> <$set name=next-step 
> filter="[getindex]then[_kludge4deleteProjectNewAltjson]else[nop]]">
> <>
> 
> <$action-log $$message="deleted project «$target$##$id$»"/>
> \end
>
> (this concerns a potential bug for impossibility to delete a property of 
> first level within a json object tiddler -- there is a separate thread I 
> fielded yesterday for that)
>
> I have not seen any other way to have a conditional call to a macro.
>
> regards,
>
> -- 
> Jean-Pierre
>

-- 
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/e0b372f9-39f2-4268-a31b-2d71cfa130een%40googlegroups.com.

[tw5] Ten Ways to Drag and Drop Tiddlers to Tiddlywiki

[Mohammad Rahmani]

Drag and drop contents into Tiddlywiki for importing and exporting contents
is one of the amazing features of Tiddlywiki, it is not known as it
deserved.

To bring the power into attention I asked the above question and I am
looking forward to see how others use this feature!



Best wishes
Mohammad

-- 
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/CAAV1gMB4ztKgzFrDvV7TOqr5gjz8UQmCmirdLS-AYP9jwxk%2BGA%40mail.gmail.com.

[tw5] Re: [Discussion] Field Related or subFields

[TW Tones]

Mario,

You speculation sounds interesting, but I do not fully grasp it.

In relation to inheritance I have build a few applications on tiddlywiki 
that define a fieldname by creating a "fieldname" tiddler (like you can 
with tags tiddlers), within that there are fields that define the "default 
values" and other details, however the most critical is the field-type 
field, each field-type eg date, also have a tiddler of their own and they 
contain fields for modes (read-only view update edit and design). In each 
of these field-type's mode fields, I place the wikitext and macros to 
operate on the field in each mode. Fieldname tiddlers may also have a 
values-filter used in the field-type to provide a select in edit and update 
modes.

Then I access any field in the body of a tiddler or view template with 
<> and this macro is sensitive to the field definition, 
its field-type and its mode. Once can also force the mode <> (but not if in read-only mode)

There will always be more fieldnames than field-types because many fields 
can use the same field-type eg; date, short-text, prose. With a structured 
design one can collect fieldname definitions and the related field-types 
and share these among wikis for rapid development.

With the above already in the wings, you can see how needing these 
complementary fields is another dimension in creating comprehensive 
mechanisms for solutions. It would be interesting to consider if a 
fieldname defined using the above mechanism (fieldname/field-type/mode) 
could be designed to support the "complementary fields".  For example if 
the fieldname is created/populated on a tiddler its fieldname..displayname 
would be created and a default set. In the tiddler (template) the designer 
could place <> to display the complementary 
fields in the tiddler mode. eg read only may only show a hyperlink with the 
name and target, edit mode the way to edit name and target.

I can share some examples of my prior work on this is anyone is interested.


Tones

On Tuesday, 4 May 2021 at 17:13:50 UTC+10 PMario wrote:

> On Tuesday, May 4, 2021 at 8:48:36 AM UTC+2 jn.pierr...@gmail.com wrote:
>
> It seems to me that these smart fields would lesser the need to have json 
>> data. Or maybe we could just have fields store json data and get methods 
>> for accessing json au part of the core? Thus, we would be able to handle 
>> them but also json in the text field, which is only a field like other.
>
>
> If we want user-facing wikitext functions that can handle JSON, imo we 
> would need a "schema", that defines the behavior. 
>
> This is 1 level "higher" than my previous thoughts.
>
> just brainstorming. 
> -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/bdb882c2-d4da-4dca-b468-00a66c5d3309n%40googlegroups.com.

[tw5] improving smart resarch for in-situ macros for filter

[Jean-Pierre Rivière]

Today I wanted to see which tiddlers I have that are javascript.

In advanced research i can execute something like

[get[type]match[application/javascript]]

but it would only bring "application/javascript"

I can't have [filter[get[type]match[application/javascript]]]

because this is gross syntax error.

But if I had access to another input ext for a macro to be called extra I 
could do

extra : [get[type]match[application/javascript]]
research : filtersortan[]

and the job would be done.

BTW, I think a standard "nop" macro doing nothing would be useful. I'm 
using it many times when I have to decide for an eventual treatment, for 
(actual real) instance:

\define deleteProjectNewAltjson(target id)
<$action-log $$message="delete project «$target$##$id$»"/>
<$action-deletefield $tiddler="$target$" $field="$id$"/>
<$set name=next-step 
filter="[getindex]then[_kludge4deleteProjectNewAltjson]else[nop]]">
<>

<$action-log $$message="deleted project «$target$##$id$»"/>
\end

(this concerns a potential bug for impossibility to delete a property of 
first level within a json object tiddler -- there is a separate thread I 
fielded yesterday for that)

I have not seen any other way to have a conditional call to a macro.

regards,

-- 
Jean-Pierre

-- 
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/a5a970de-75ce-427d-b655-62c8e27301e4n%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[TW Tones]

Jean Pierre,

We sound like we are on the same page, my idea was to store the fields by 
that compound name, just as "complementary fields"" fieldname..description 
could describe the content of the specific "fieldname" on this specific 
tiddler.

Concretely what I wish to get is *additional information* stored per 
fieldname on a given tiddler, complementary fields. The first case was an 
anyname.link (containiong a URL) field can have the complementary fields  
anyname.link..name  anyname.link..target

However to assist many anyname.link fields I want the use of the 
complementary fields somewhat automated, perhaps only a de facto standard, 
with supporting macros as needed.

I see this need for a method by which to have  complimentary field names 
quite compelling so supporting tools can be built once and used by many.

Tones
On Tuesday, 4 May 2021 at 16:48:36 UTC+10 jn.pierr...@gmail.com wrote:

> A while back', I had a field having structured data like 
> "Potter^14^sorcery" but it was up to my macros to handle them. Say that 
> field was called "identity". If I understand your proposal correctly, under 
> your scheme, it would be called "identity." and its 3 sub-fields known as "
> identity.name"', "identity.age" and identity.business". But how would 
> they be stored? And retrived? Anything that could streamline the handling 
> of such things would be cool.
>
> I fail to see what you concretely wish to get.
>
> It seems to me that these smart fields would lesser the need to have json 
> data. Or maybe we could just have fields store json data and get methods 
> for accessing json au part of the core? Thus, we would be able to handle 
> them but also json in the text field, which is only a field like other.
>
> regards,
>
> -- 
> Jean-Pierre
> Le mardi 4 mai 2021 à 02:48:55 UTC+2, TW Tones a écrit :
>
>> Charlie,
>>
>> Good idea. If I wanted to reduce the clashes I could use ".." unlike 
>> double __ or -- .. is clearer. and the chance others are using ".." is 
>> lower. then we can safely search for all "Related fields" ie; and field 
>> name containing ".." eg discussion..name supports the field discussion with 
>> a name. Disambiguation from other fields using _ - or . which are 
>> permissible.
>>
>> Now I need to automate in some way the identification of related fields 
>> and there use in code/wikitext.
>>
>> Tones
>>
>> On Tuesday, 4 May 2021 at 10:21:51 UTC+10 cj.v...@gmail.com wrote:
>>
>>> Underscores and dashes are pretty similar looking.  If that matters any 
>>> (i.e. if you already use either one in field names), then how about a 
>>> period?
>>>
>>> So "url.", looks nice to me.  Then you could have url.name, url.target, 
>>> etc.
>>>
>>> That becomes just a matter of personal preference.  I think they are all 
>>> fine for what you're thinking.
>>>
>>> On Monday, May 3, 2021 at 3:35:10 AM UTC-3 TW Tones wrote:
>>>
 Folks,

 I have come across a "problem" for which I am investigating a solution, 
 and keen to hear any ideas. ultimately I hope this to provide a generic 
 solution for advanced field handling I would share back into the community.

 *Problem:*

 Consider we may like to have a field in one or more tiddlers to store a 
 url to an external resource for that tiddler.

 Field: url, Value: https://tiddlywiki.com/#cycle%20Operator

 The thing is what if we wanted to store a simplified name such as 
 "Cycle Operator" or a target for links such as _blank or "operators" there 
 is no where to specify the url/name and url/target. when we construct a 
 link to this URL it would be nice to find the name/target for this url 
 field/tiddler combination.

 In future I also want to have a discussion-link tiddler with matching 
 name and target, with even more similar fields.

 *Possible approach*
 We could use the "_" underscore to delimit such "subFields" and create 
 additional fieldnames such as url_name and url_target. Then when I have 
 code dealing with "url" it can look for fields beginning url_ to find its 
 "subfields". I wonder if this compromises the available fieldnames or 
 others plugins and solutions that make use of the "_" underscore more 
 often 
 than I do?

 Perhaps such fields that may have subfields could end with "_" eg; 
 "url_" meaning subfields exist for this fieldname.

 *More complex systematic approach*
 I could store in a data tiddler (For each tiddler) these additional 
 subfields, or even in a new special text field inside each tiddler.

 *A not so desirable approach*
 Build all the handling to allow the url field (in this case) actually 
 be the full http link or html  tag. The problem being one may need to 
 code and decode the content of the url field for every add or change, also 
 if one had dozens of different link fields it could get messy.

 Your Thoughts?
 Tones

[tw5] Re: [Discussion] Field Related or subFields

[PMario]

On Tuesday, May 4, 2021 at 8:48:36 AM UTC+2 jn.pierr...@gmail.com wrote:

It seems to me that these smart fields would lesser the need to have json 
> data. Or maybe we could just have fields store json data and get methods 
> for accessing json au part of the core? Thus, we would be able to handle 
> them but also json in the text field, which is only a field like other.


If we want user-facing wikitext functions that can handle JSON, imo we 
would need a "schema", that defines the behavior. 

This is 1 level "higher" than my previous thoughts.

just brainstorming. 
-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/b59a1205-bf70-4a7d-8dbd-b4d64ca9eb95n%40googlegroups.com.

[tw5] Re: filter to get tiddlers newer than a given date

[James Anderson]

Hey Mark,

that doesn't seem to work in the advances search filters tab (see 
attachment) I assume it won't work with $tw.wiki.filterTiddlers in a plugin 
either.

>TW Tones
if you put this into the seach box in the image i attached hopefully it's 
clearer [all[tiddlers]get[modified]compare:date:gt[2021]] 

I would just like a way to return a list of tiddlers older or newer than a 
given date (though the date might be a custom field in the future)

Thanks

James




On Tuesday, 4 May 2021 at 03:30:17 UTC+1 Mark S. wrote:

> You need the "filter" operator which is actually a subfilter operator. It 
> requires you to pre-specify the inner filter with a variable:
>
> <$vars myfilt="[get[modified]compare:date:gt[2021]]">
> <]">>
> 
>
>
>
> On Monday, May 3, 2021 at 3:56:30 PM UTC-7 james.w@gmail.com wrote:
>
>> Hello,
>>
>> I've tried [all[tiddlers]get[modified]compare:date:gt[2021]] in advanced 
>> search but this seems to give me links to tiddlers named after modified 
>> field
>>
>> eventually would like to do this in a plugin via $tw.wiki.filterTiddlers, 
>> is there a way to do this in the advanced search on the filters tab? If nto 
>> what is the best way to do this in a widget?
>>
>>
>> thanks,
>> James
>>
>

-- 
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/960fa264-96aa-4de5-816d-0dac2f7f8a8en%40googlegroups.com.

[tw5] Re: [Discussion] Field Related or subFields

[PMario]

On Tuesday, May 4, 2021 at 1:48:33 AM UTC+2 TW Tones wrote:

In the original post I was placing under consideration the idea that a 
> convention would be that a field such as "discussion" may also have a 
> discussion_name and  discussion_target field. What ever handling I do for 
> "discussion" I can test for the existence or or attempt to get the values 
> in one or more "discussion_" fields. 


For me this looks like a mechanism, for inheritance. ... Similar to a 
possibility to define a field, that behaves like the "tags" field. 

eg: my-tags..type: tags  Which would look up the "setters" and 
"getters" from the tags field to read and write there.
similar: due-date..type: date ... Has the same functionality as created and 
modified.

So the existence of due-date..type implies the existence of due-date.. and 
hides them both from the edit-template. 

So due-date..macros: $:/tiddlerName  contains the macros, that are 
"inherited"   If ..macros doesn't exist it assumes tha name to be 
$:/fields/macros// In norm al cases ..macros is used for development 
and $:/.. is used for production. 

... Just brainstorming

-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/7d7b6af4-eb3b-4516-9d69-f4b58020d0d7n%40googlegroups.com.

Re: [tw5] A basket on the sidebar

[Mohammad Rahmani]

*Fourth solution*

If you like a quick solution without extra coding see Favorites from kookma!

*I. install Favorites plugin (skip this step if you have it)*

1. open https://kookma.github.io/TW-Favorites/
2. drag and drop the Favorites (
https://kookma.github.io/TW-Favorites/#%24%3A%2Fplugins%2Fkookma%2Ffavorites)
to your wiki


*II. use Favorites Basket*
1. on the sidebar open Favorites
2. Click the setting button (gear button)
3. Create a Basket folder
4. keep open the Favorites tab in the sidebar
5. add items by drag and drop
   5.1. use drag and drop links/titles
   5.2 use drag and drop tag pills
   5.3. remove items if you are not happy with list
6. when finished
  6.1. Click the setting button (gear button)
  6.2. Open Export tab
  6.3 Export the folder





Best wishes
Mohammad


On Tue, May 4, 2021 at 1:38 AM Atronoush Parsi  wrote:

> Is there any script or plugin with
>
> - a sidebar tab (I call it basket)
> - drag and drop features! One can drag a tiddler (e.g title) into the
> basket
> - when finished press a button to export as JSON
> - the button can be dragged and drop into another wiki!
>
> The last part is what you see in TW-Icons
>
>
> -Atro
>
> --
> 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/CAKHVXmoDHTtqMgUcp2ob%3DvHt6_nwBJbM2S4fOCi0gMraE3wEOA%40mail.gmail.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/CAAV1gMAdGbUTw7MKtJUQbeqLfJEFxX8%3DeJ0OvCjZeQvgZMVUHQ%40mail.gmail.com.

Re: [tw5] [IDEA] Archiving tiddlers, for Projectify users and potentially others

[Hans Huber]

Diego

Sounds to me as if KOOKMAs trashbin plugin does exactly what you intend

HH

On Tue, May 4, 2021, 04:17 dieg...@gmail.com  wrote:

> I work a lot with Nicos excellent Projectify plugin.
>
> As a result, I have a lot of ephemeral tiddlers for my to-dos that once
> done, are no longer really needed as full tiddlers. I don't need to search
> them, tag them, etc.
>
> Also, since I use node, I don't really want them cluttering the tiddlers
> folder, as I frequently go in there and do some searching outside TW.
>
> As a result, I thought about "Archiving" them, or "flattening" them, into
> a single JSON tiddler for reference.
>
> I came up with the following "Archive" button, which appends all tiddlers
> tagged with done to an Archive tiddler.
>
> Code:
> <$vars archiveTiddlerTitle="Archive"
>todoText=<>
>emptyJSON="[]" linebreak="
>
> ">
> <$set name="newArchiveText"
>   filter="[!match]"
>   value={{{
> [titleget[text]addsuffixaddsuffix]
> }}}
>   emptyValue={{{ [titleget[text]] }}} >
>
> <$button>
> <$action-setfield $tiddler=<>
>   $field="text"
>   $value=<> />
> <$action-deletetiddler $filter="[tag[done]]" />
> Archive!
> 
>
> 
> 
>
>
> Some notes:
>
>- I had to solve an annoying issue with the <> macro
>that when its empty, returns an "[]", which is actually not empty (is this
>intended?!)
>- Different archiving batches will just be appended as separate JSON
>objects, instead of merging everything back into one large JSON object.
>- There is no "unarchive" feature, and building one is probably beyond
>my abilities (thought might be a good use case for Joshua's JSON Mangler!
>if I understand it correctly!)
>
>
> This could be of use for others to "flatten" large tag structures that
> you're done with and don't need flying around as separate tiddlers.
>
> Your thoughts/suggestions/comments/etc are welcome!
>
> Diego
>
> --
> 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/d14c93ef-456d-40cf-a51c-698c77c579adn%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/CAD273SSjMVExcmTOe4LFEL%3DKyNgenoD6RY-DdRz4ye_HXqGBag%40mail.gmail.com.

Re: [tw5] A basket on the sidebar

[Mohammad Rahmani]

Hi Atro,

Very nice question and a lot of use cases!!

You get two solutions from Soren and Tones!
The Soren solution implements a real basket !  Soren said it is* a lazy
solution*! I want to see if I can be lazier! *;-)*

*Third solution*

   1. Clone the Open tab in the sidebar ( $:/core/ui/SideBar/Open  )
   2. rename it to "myBasket"
   3. change the caption to Basek (I named it Atro Basket for *Atronoush*)
   4. make small change (e.g set the tv-story-list to myBasket to use it
   instead of TW tv-story-list)
   5. change close all to clear all to clear the list of myBasket
   6. add an export button to export tiddlers in basket (e.g listed in
   myBasket list field)
   7. make your button *draggable* (for example use dragFilter)

*How it works*

   1. Open the Atro Basket in the sidebar  (see attached file)
   2. add items to Basket in different ways like below
  1. drag and drop links, titles to Basket
  2. drag a tag pill to add all tiddler with that tag
  3. if you are not happy click *clear all* to remove all tiddlers in
  basket
  4. if you like remove any item click the *remove button*
   3. Export
  1. click export button to export json (all tiddlers in the basket as
  json) OR
  2. drag and drop the export button to other wiki to import all
  tiddlers in basket to your wiki  (your button is draggable)
  3. when finished! if you like to empty the Basket, click clear all


I have attached the working tiddler here! Drop into https://tiddlywiki.com/
and see how it works!

Best wishes
Mohammad


On Tue, May 4, 2021 at 1:38 AM Atronoush Parsi  wrote:

> Is there any script or plugin with
>
> - a sidebar tab (I call it basket)
> - drag and drop features! One can drag a tiddler (e.g title) into the
> basket
> - when finished press a button to export as JSON
> - the button can be dragged and drop into another wiki!
>
> The last part is what you see in TW-Icons
>
>
> -Atro
>
> --
> 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/CAKHVXmoDHTtqMgUcp2ob%3DvHt6_nwBJbM2S4fOCi0gMraE3wEOA%40mail.gmail.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/CAAV1gMDWpY8MpmK%3DK%2B7JKESdzTt9Tk%2BfZkk%2BQjR62LhMxqBXFQ%40mail.gmail.com.


myBasket.json
Description: application/json

[tw5] Re: [Discussion] Field Related or subFields

[Jean-Pierre Rivière]

A while back', I had a field having structured data like 
"Potter^14^sorcery" but it was up to my macros to handle them. Say that 
field was called "identity". If I understand your proposal correctly, under 
your scheme, it would be called "identity." and its 3 sub-fields known as 
"identity.name"', "identity.age" and identity.business". But how would they 
be stored? And retrived? Anything that could streamline the handling of 
such things would be cool.

I fail to see what you concretely wish to get.

It seems to me that these smart fields would lesser the need to have json 
data. Or maybe we could just have fields store json data and get methods 
for accessing json au part of the core? Thus, we would be able to handle 
them but also json in the text field, which is only a field like other.

regards,

-- 
Jean-Pierre
Le mardi 4 mai 2021 à 02:48:55 UTC+2, TW Tones a écrit :

> Charlie,
>
> Good idea. If I wanted to reduce the clashes I could use ".." unlike 
> double __ or -- .. is clearer. and the chance others are using ".." is 
> lower. then we can safely search for all "Related fields" ie; and field 
> name containing ".." eg discussion..name supports the field discussion with 
> a name. Disambiguation from other fields using _ - or . which are 
> permissible.
>
> Now I need to automate in some way the identification of related fields 
> and there use in code/wikitext.
>
> Tones
>
> On Tuesday, 4 May 2021 at 10:21:51 UTC+10 cj.v...@gmail.com wrote:
>
>> Underscores and dashes are pretty similar looking.  If that matters any 
>> (i.e. if you already use either one in field names), then how about a 
>> period?
>>
>> So "url.", looks nice to me.  Then you could have url.name, url.target, 
>> etc.
>>
>> That becomes just a matter of personal preference.  I think they are all 
>> fine for what you're thinking.
>>
>> On Monday, May 3, 2021 at 3:35:10 AM UTC-3 TW Tones wrote:
>>
>>> Folks,
>>>
>>> I have come across a "problem" for which I am investigating a solution, 
>>> and keen to hear any ideas. ultimately I hope this to provide a generic 
>>> solution for advanced field handling I would share back into the community.
>>>
>>> *Problem:*
>>>
>>> Consider we may like to have a field in one or more tiddlers to store a 
>>> url to an external resource for that tiddler.
>>>
>>> Field: url, Value: https://tiddlywiki.com/#cycle%20Operator
>>>
>>> The thing is what if we wanted to store a simplified name such as "Cycle 
>>> Operator" or a target for links such as _blank or "operators" there is no 
>>> where to specify the url/name and url/target. when we construct a link to 
>>> this URL it would be nice to find the name/target for this url 
>>> field/tiddler combination.
>>>
>>> In future I also want to have a discussion-link tiddler with matching 
>>> name and target, with even more similar fields.
>>>
>>> *Possible approach*
>>> We could use the "_" underscore to delimit such "subFields" and create 
>>> additional fieldnames such as url_name and url_target. Then when I have 
>>> code dealing with "url" it can look for fields beginning url_ to find its 
>>> "subfields". I wonder if this compromises the available fieldnames or 
>>> others plugins and solutions that make use of the "_" underscore more often 
>>> than I do?
>>>
>>> Perhaps such fields that may have subfields could end with "_" eg; 
>>> "url_" meaning subfields exist for this fieldname.
>>>
>>> *More complex systematic approach*
>>> I could store in a data tiddler (For each tiddler) these additional 
>>> subfields, or even in a new special text field inside each tiddler.
>>>
>>> *A not so desirable approach*
>>> Build all the handling to allow the url field (in this case) actually be 
>>> the full http link or html  tag. The problem being one may need to code 
>>> and decode the content of the url field for every add or change, also if 
>>> one had dozens of different link fields it could get messy.
>>>
>>> Your Thoughts?
>>> Tones
>>>
>>

-- 
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/d6e6c090-0e56-4367-beaa-e2d31c690df0n%40googlegroups.com.

[tw5] Re: Custom sort order

[Max Rozeman]

No problem Mario. I've learned from each of the replies to my question so 
I'm glad you posted.

On Monday, May 3, 2021 at 11:05:12 PM UTC+10 PMario wrote:

> On Monday, May 3, 2021 at 11:48:41 AM UTC+2 Max Rozeman wrote:
>
>> Well it looks like this isn't as simple as I had hoped. Maybe what I need 
>> is a macro, but that's a skill I've yet to learn. For the time being then 
>> I'll just have to sort my titles the easy and messy way by adding prefixes 
>> to my prefixes.
>>
>
> You are right. My code doesn't work as expected. ... I did very poor 
> testing, so it looked like it would have worked. ... :/ Sorry for that. 
>
> But the sortby operator needs "matching titles" it doesn't use regexp 
> matches internally, which would have been needed for your usecase. 
>
> So imo there won't be a "out of the box" solution. ... At least I don't 
> know it. 
>
> -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/8860e2aa-0b9d-4294-b32c-7311263ad7fdn%40googlegroups.com.

[tw5] Re: Custom sort order

[Max Rozeman]

Thank you very much Soren -- it works beautifully! Thanks also for your 
clear explanation.

On Tuesday, May 4, 2021 at 4:34:21 AM UTC+10 Soren Bjornstad wrote:

> Sorry, there's a typo in that macro, should be:
>
> \define myfilt() [all[current]split[ ]first[]match[SP]then[010]] 
> [all[current]split[ ]first[]match[SC]then[020]] [all[current]split[ 
> ]first[]match[ER]then[030]]
>
> On Monday, May 3, 2021 at 1:30:56 PM UTC-5 Soren Bjornstad wrote:
>
>> Here's a solution using sortsub, which sorts based on a key obtained by 
>> running a filter against each input item.  This assumes your prefixes are 
>> separated from the rest of the tiddler title by a space. If not, you may 
>> have to change the split character or get a bit more creative:
>>
>> \define myfilt() [all[current]split[ ]first[]match[SP]then[010] 
>> [all[current]split[ ]first[]match[SC]then[020]] [all[current]split[ 
>> ]first[]match[ER]then[030]]
>>
>> <]">>
>>
>> The subfilter in myfilt uses a series of runs to convert each prefix 
>> into a numerical value which sorts in the order you want. You can add as 
>> many steps to the filter as you need to handle all your prefixes. Any items 
>> that don't have a prefix listed in the filter will get no sort key and so 
>> show up at the top of the list.
>>
>> I am sure you could get creative and figure out how to store the mapping 
>> in a data tiddler and dynamically build the filter, but I'll let someone 
>> else figure that out if they're so inclined.
>>
>> On Monday, May 3, 2021 at 8:05:12 AM UTC-5 PMario wrote:
>>
>>> On Monday, May 3, 2021 at 11:48:41 AM UTC+2 Max Rozeman wrote:
>>>
 Well it looks like this isn't as simple as I had hoped. Maybe what I 
 need is a macro, but that's a skill I've yet to learn. For the time being 
 then I'll just have to sort my titles the easy and messy way by adding 
 prefixes to my prefixes.

>>>
>>> You are right. My code doesn't work as expected. ... I did very poor 
>>> testing, so it looked like it would have worked. ... :/ Sorry for that. 
>>>
>>> But the sortby operator needs "matching titles" it doesn't use regexp 
>>> matches internally, which would have been needed for your usecase. 
>>>
>>> So imo there won't be a "out of the box" solution. ... At least I don't 
>>> know it. 
>>>
>>> -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/667c128b-5cff-47f4-9207-cf9b73189f92n%40googlegroups.com.

[tw5] Re: Very random Javascript errors

[PMario]

Hi,
It would be good, if you could post the exact text, that is shown on the 
RSOD. It should tell us, what's causing the problem.

... Yes most likely a plugin, if you can't replicate it at tiddlywiki.com

-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/0675fa47-318d-4675-b783-1e72e81383fen%40googlegroups.com.