Re: [tw5] One journal tiddler / day (like a diary): how?

[David Bakin]

Ray, thanks - I'll look into your technique!

Yeah, learning curve is steep.  But I gotta tell you ... it's not as steep
now as it was 5 yrs ago ... so there's that ...

On Fri, Apr 16, 2021 at 4:01 PM Ray Vermey  wrote:

> Hi, i am new too, and still cry sometimes... so hard i think it is to
> really learn TW :-)
> Then i see others having TW's and I scream: HOW!??? How did you do
> that?
> So i feel you bro.
>
> I use TW exactly like you plan to do.
> For each event, thing that occurs i create a journal tiddler with date and
> time.
> Then i use tags to tag the people involved.
>
> I use this filter below to have overview of a day, i put the date in
> manually, must be possible to do that better but ok it works for me:
>
> <$list
> filter="[!is[system]!tag[script]sameday:created[20210415]!tag[desc]sort[created]]">
>
> 
> 
> {{!!text}}
>
> 
>
> Hope it helps you too.
> The  e dont know why anymore tbh :-)
>
> Maybe this tiddler can be rebuild in some kind of matrix overview?
>
> Other people have ideas?
>
> Keep on TW'ing, you WILL learn!!
>
> Ray
>
> Op vr 16 apr. 2021 om 23:06 schreef da...@bakins-bits.com <
> da...@bakins-bits.com>:
>
>> (I think) I'd like to have one journal entry each day - formatted like a
>> list.  Unless there's a better way of handling things.
>>
>> So, questions that I'm hoping you can point to (or provide with) answers:
>>
>> How can I change the "new journal" button to bring up that day's journal
>> entry (creating it if necessary)? (Assuming I have the "title of new
>> journal tiddlers" set properly, e.g., [UTC]-0MM-0DDZ)
>> (Optional:) How can I arrange that on creating a new tiddler it gets
>> appended to that day's journal's list? Either "manually" (e.g., a button on
>> any new tiddler I create) or automatically (possibly with an opt-out
>> button)?
>> Or maybe this isn't the way I should be using the journal tiddlers at
>> all.  Maybe instead I should create the journal tiddlers as I want them -
>> with full timestamp - and have a separate way (some kind of tiddler with
>> macro) for quickly seeing the list of all journal entries for a given day?
>>
>> (Obviously I'm very new to TW5.  I did use TW Classic for several years,
>> several years ago.  But gave it up when I could no longer save
>> (automatically) locally via browser.  Now
>> I'm happy with gitlab integration and I'm getting back into TiddlyWiki
>> use.)
>>
>> Thanks! -- David Bakin
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/8d6db65b-dccd-4e4a-921b-056f7456b72dn%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/CAAF_p9CDRV7tX1uHbzDt14VOMxM0Sb6dUFsEELHDQKnm3%3D4wPw%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/CAF-gu8jhoRUQDVVqq_GCvikyOA0%3DK699iqCObrdOyVeGYvgBWg%40mail.gmail.com.

Re: [tw5] Re: [Introducing] TiddlyJam - new Plugin, CMS and static website generator

[Mohammad Rahmani]

Hi Adithya,
 Many thanks for the new update! I will go through and will send you my
comments if any!



Best wishes
Mohammad


On Sun, Apr 18, 2021 at 6:45 AM Adithya B  wrote:

> @Mohammed,
>
> I have added support for custom css and some additional stuff in the
> latest release :)
>
> On Saturday, April 17, 2021 at 3:55:24 PM UTC-6 Adithya B wrote:
>
>> Hi Flohit,
>>
>> I have added some notes on how to get started/customize your website
>> here: https://tiddlyjam.com/
>> Could you check it out and let me know if that helps you?
>>
>> On categories: I am still getting around to writing support for them into
>> the system. Will update that in a few weeks.
>>
>> Adithya
>> On Thursday, March 25, 2021 at 1:27:16 PM UTC-6 flohit...@googlemail.com
>> wrote:
>>
>>> So, I have been trying it out.
>>>
>>> I really like the website you created for yourself, but its not really
>>> clear how you managed that :D
>>> For example where can i change the css? could i just use an existing TW
>>> theme that I don't use for the non-static TW and set it up as a template?
>>> that would be quite cool bc we would instantly have some cool templates :)
>>> Or use the CSS packages for TW that exist (also the icon packs - feather is
>>> quite cool)
>>> Then, what are categories for - how do i use them? How do i, in general
>>> include tiddlers that are not  pages or blogs like you did?
>>> by the way, here is another, older try at what you're doing - i thought
>>> the idea of creating a framework was worthwile, but on the other hand, it
>>> uses so many tags...  https://github.com/welford/twstaticblog
>>>  i don't know if it helps but i discovered an easy toggleable sidebar in
>>> a jekyll theme when i was trying to work with that which works with a
>>> minimum of javascript for the button, i could show you that one - I used to
>>> copy that over to over themes, which was pretty easy. I don't even know if
>>> that's possible to include though ^^
>>>
>>>
>>> bmad...@gmail.com schrieb am Dienstag, 16. März 2021 um 22:24:57 UTC+1:
>>>
 Looks like fun!
 On Tuesday, March 16, 2021 at 11:15:51 AM UTC-6
 flohit...@googlemail.com wrote:

> cool! would love graphing, i was first starting with this jekyll
> template (the map is on the bottom of the side):
> https://digital-garden-jekyll-template.netlify.app/cats  --- i think
> there could be possibilities using the graphviz and vis.js libraries that
> are available as plugins. I should maybe make an own post for that.
>
> bmad...@gmail.com schrieb am Dienstag, 16. März 2021 um 17:50:44
> UTC+1:
>
>> Thanks for your comment!
>>
>> To answer your question about the plans for this project:
>> Toggleable sidebar and search - yes
>> Graph-visualization - probably not (its possible though)
>> On Tuesday, March 16, 2021 at 10:49:02 AM UTC-6
>> flohit...@googlemail.com wrote:
>>
>>> This all looks very lovely :) especially your own website.
>>> I am also looking for a "digital gardening" tool, though i'm not
>>> capable of coding myself.
>>> This and jeremys announcement are making me hopeful for finally
>>> being able to settling for tiddlywiki - i was just going to start to 
>>> look
>>> into org-roam, although i have found so many cool features in TW.
>>> You are not planning on adding things like a toggleable-sidebar, a
>>> graph - visualization, and a search, though, are you (:
>>>
>>> bmad...@gmail.com schrieb am Sonntag, 14. März 2021 um 18:17:56
>>> UTC+1:
>>>
 Hi everyone!

 I have been working on a static website generator/CMS plugin for
 TiddlyWiki for my personal use for the past six months or so. Finally, 
 I
 feel I am ready to share it!

- Have a look at the rendered website at https://tiddlyjam.com
- The github repo is at
https://github.com/adithya-badidey/tiddlyjam
- Actual wiki is at https://tiddlyjam.com/tiddly
- Its still in alpha - please share bugs, comments, feedback -
either here or at
https://github.com/adithya-badidey/tiddlyjam/discussions

 Cheers!
 Adithya

>>> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/70fe536c-d0c3-48f6-95d1-d067df5f7657n%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 

Re: [tw5] A tour through my Zettelkasten

[Mohammad Rahmani]

>
>
> Curious – what tiddlers do you think don't need a link summary?
>
>
> I have attached some images to answer this question! I think
shadows/systems may not need such a summary!

[image: img_76_chrome.png]



[image: img_75_chrome.png]


I also noted favicon does not work! (It uses a uri to local file)

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

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

[Mohammad Rahmani]

Thank you Mark!

I will give a try!



Best wishes
Mohammad


On Sun, Apr 18, 2021 at 8:44 AM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> In that case, thanks to Brian's input, I seem to have gotten it to work,
> though maybe only once. Here's a screen shot without the code:
>
> [image: 1618718712_2105_17.04.2021_1366x768.png]
>
> and here's a screenshot with the code
>
> [image: 1618718788_2106_17.04.2021_1366x768.png]
>
> I only tested once. For about 3 seconds. I have no idea if it breaks with
> repeated use, as  Brian suggested.
>
> Good luck!
>
>
> On Saturday, April 17, 2021 at 8:55:35 PM UTC-7 Mohammad wrote:
>
>> On Sun, Apr 18, 2021 at 1:18 AM 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>> Hi Mohammad,
>>>
>>> How do you test your code? On a small device? Portrait mode? Or ... ?
>>>
>>
>> Hi Mark,
>> I used the code on a large screen (laptop)! I attached the three tiddlers
>> show to the JS, CSS and the test!
>> To examine the code you need to add/remove some text to push the tooltip
>> to the edge of the screen!
>>
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/280af977-1b60-4b87-a154-27d91a0393b1n%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/CAAV1gMDc9TQPxNzH2bOJQTQYp1Hj_3r8KwNPav8t7-aegBfk9A%40mail.gmail.com.

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

['Mark S.' via TiddlyWiki]

In that case, thanks to Brian's input, I seem to have gotten it to work, 
though maybe only once. Here's a screen shot without the code:

[image: 1618718712_2105_17.04.2021_1366x768.png]

and here's a screenshot with the code

[image: 1618718788_2106_17.04.2021_1366x768.png]

I only tested once. For about 3 seconds. I have no idea if it breaks with 
repeated use, as  Brian suggested.

Good luck!


On Saturday, April 17, 2021 at 8:55:35 PM UTC-7 Mohammad wrote:

> On Sun, Apr 18, 2021 at 1:18 AM 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com> wrote:
>
>> Hi Mohammad,
>>
>> How do you test your code? On a small device? Portrait mode? Or ... ?
>>
>
> Hi Mark, 
> I used the code on a large screen (laptop)! I attached the three tiddlers 
> show to the JS, CSS and the test!
> To examine the code you need to add/remove some text to push the tooltip 
> to the edge of the screen!
>
>>
>>

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


X$__core_modules_tooltips.js.json
Description: application/json

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

[Mohammad Rahmani]

On Sun, Apr 18, 2021 at 1:18 AM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> Hi Mohammad,
>
> How do you test your code? On a small device? Portrait mode? Or ... ?
>

Hi Mark,
I used the code on a large screen (laptop)! I attached the three tiddlers
show to the JS, CSS and the test!
To examine the code you need to add/remove some text to push the tooltip to
the edge of the screen!

>
>

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


ktooltip.json
Description: application/json

[tw5] Re: [Introducing] TiddlyJam - new Plugin, CMS and static website generator

[Adithya B]

@Mohammed,

I have added support for custom css and some additional stuff in the latest 
release :)

On Saturday, April 17, 2021 at 3:55:24 PM UTC-6 Adithya B wrote:

> Hi Flohit,
>
> I have added some notes on how to get started/customize your website here: 
> https://tiddlyjam.com/
> Could you check it out and let me know if that helps you?
>
> On categories: I am still getting around to writing support for them into 
> the system. Will update that in a few weeks.
>
> Adithya
> On Thursday, March 25, 2021 at 1:27:16 PM UTC-6 flohit...@googlemail.com 
> wrote:
>
>> So, I have been trying it out. 
>>
>> I really like the website you created for yourself, but its not really 
>> clear how you managed that :D 
>> For example where can i change the css? could i just use an existing TW 
>> theme that I don't use for the non-static TW and set it up as a template? 
>> that would be quite cool bc we would instantly have some cool templates :) 
>> Or use the CSS packages for TW that exist (also the icon packs - feather is 
>> quite cool)
>> Then, what are categories for - how do i use them? How do i, in general 
>> include tiddlers that are not  pages or blogs like you did? 
>> by the way, here is another, older try at what you're doing - i thought 
>> the idea of creating a framework was worthwile, but on the other hand, it 
>> uses so many tags...  https://github.com/welford/twstaticblog
>>  i don't know if it helps but i discovered an easy toggleable sidebar in 
>> a jekyll theme when i was trying to work with that which works with a 
>> minimum of javascript for the button, i could show you that one - I used to 
>> copy that over to over themes, which was pretty easy. I don't even know if 
>> that's possible to include though ^^
>>
>>
>> bmad...@gmail.com schrieb am Dienstag, 16. März 2021 um 22:24:57 UTC+1:
>>
>>> Looks like fun!
>>> On Tuesday, March 16, 2021 at 11:15:51 AM UTC-6 flohit...@googlemail.com 
>>> wrote:
>>>
 cool! would love graphing, i was first starting with this jekyll 
 template (the map is on the bottom of the side): 
 https://digital-garden-jekyll-template.netlify.app/cats  --- i think 
 there could be possibilities using the graphviz and vis.js libraries that 
 are available as plugins. I should maybe make an own post for that. 

 bmad...@gmail.com schrieb am Dienstag, 16. März 2021 um 17:50:44 UTC+1:

> Thanks for your comment!
>
> To answer your question about the plans for this project:
> Toggleable sidebar and search - yes
> Graph-visualization - probably not (its possible though)
> On Tuesday, March 16, 2021 at 10:49:02 AM UTC-6 
> flohit...@googlemail.com wrote:
>
>> This all looks very lovely :) especially your own website.
>> I am also looking for a "digital gardening" tool, though i'm not 
>> capable of coding myself.
>> This and jeremys announcement are making me hopeful for finally being 
>> able to settling for tiddlywiki - i was just going to start to look into 
>> org-roam, although i have found so many cool features in TW.
>> You are not planning on adding things like a toggleable-sidebar, a 
>> graph - visualization, and a search, though, are you (:
>>
>> bmad...@gmail.com schrieb am Sonntag, 14. März 2021 um 18:17:56 
>> UTC+1:
>>
>>> Hi everyone!
>>>
>>> I have been working on a static website generator/CMS plugin for 
>>> TiddlyWiki for my personal use for the past six months or so. Finally, 
>>> I 
>>> feel I am ready to share it!
>>>
>>>- Have a look at the rendered website at https://tiddlyjam.com
>>>- The github repo is at 
>>>https://github.com/adithya-badidey/tiddlyjam
>>>- Actual wiki is at https://tiddlyjam.com/tiddly
>>>- Its still in alpha - please share bugs, comments, feedback - 
>>>either here or at 
>>>https://github.com/adithya-badidey/tiddlyjam/discussions
>>>
>>> Cheers!
>>> Adithya
>>>
>>

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

[tw5] Re: More Free Icons/images for Windows 10 Users that work well with TiddlyWiki

[TW Tones]

We all agree then, sorry I sent us on a wild goose chase.

Something that can be drawn from this is that a local app from which you 
can search, list, drag icons is helpful, perhaps a tiddlywiki that can be 
installed locally in TiddlyDesktop etc.. could be nice.

In the mean time I have created a Chrome App Icon to access the icons from 
https://morosanuae.github.io/tw-icons/  


Tones
On Saturday, 17 April 2021 at 19:00:02 UTC+10 TiddlyTweeter wrote:

> TW Tones wrote:
>
>> The pricing in US Dollars can be found here https://icons8.com/pricing 
>> along with this and the icon limitations even with a paid plan has turned 
>> me off this option. 
>>
>
> Right. That was my point, that that link is a DEAD end. In multiple ways.
>
> Users can *already* easily use 38,000+ TW icons in TW icon format via 
> https://morosanuae.github.io/tw-icons/  
> . 
> It is brilliant & comprehensive.
>
> There is NO need to re-invent the wheel when it already exists and works 
> well!  :-).
>
> TT
>
>
>

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

[tw5] Re: A How To Prototype: An edit toolbar button to add widgets to a tiddler

[Charlie Veniot]

BTW, just a reminder about the predefined snippets of text button on the 
edit toolbar.  I forgot about it.

That's a bit less work than what I'm doing  If I give up on the more 
elaborate thing I've got in mind, this will be my plan B.

[image: Screenshot 2021-04-17 8.42.01 PM - Display 2.png]

On Saturday, April 17, 2021 at 4:22:06 PM UTC-3 Charlie Veniot wrote:

> G'day,
>
> Following up on an idea from the EditTextWidget: ouch when 
> tiddler=currentTiddler and using index 
>  conversation:
>
> A Widgets Dropdown Button on EditToolbar 
> 
>
> [image: Screenshot 2021-04-17 3.50.41 PM - Display 2.png]
>
>
>
>

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

[tw5] Re: A tour through my Zettelkasten

[Soren Bjornstad]

Haha, sorry, I forgot to turn off the vim keybindings. PMario has explained 
how to do that.

On Saturday, April 17, 2021 at 1:30:57 PM UTC-5 ludwa6 wrote:

> OK, after struggling w/ this a bit, i have to stop and ask: is there 
> something that would cause the editor widget to behave very differently 
> from standard TW5?  Triple-click on a tiddler to edit (new one on me, but 
> that's cool), and then -instead of opening into a typical text box- it's a 
> single line edit widget, with a blinking green box instead of simple cursor 
> (flashback to ye ole VT100 term-em days :-) that does not respond to key 
> commands as usual: hitting space bar or backspace key moves the cursor as 
> though i were hitting forward and back arrows.  So i wonder: is this maybe 
> configured for external editor control, somehow?  I really love the system 
> overall, but just can't get the hang of this text editor variant, so if 
> there's any way to make it revert to standard, i'd sure like to know how.
> On Saturday, April 17, 2021 at 6:06:29 PM UTC+1 Soren Bjornstad wrote:
>
>> The public version lacks some functionality that is important for editing 
>> and has a bunch of settings changed that are a bit of a pain to change 
>> back, so it'll be much better if I do a second build off of the "real" 
>> private version. I've attached a first 15-minute attempt at this.
>>
>> Things that could use improvement here:
>>
>>- There are no instructions at all, so you'll have to figure out how 
>>to get started on your own. Some of the conventions tiddlers are missing 
>>and would be nice to have.
>>- I included all the red, yellow, and black tag tiddlers, but since 
>>there is no content in this version, most of them are not tagging 
>> anything, 
>>so they don't show up in the tags list. Also, some of the tag tiddlers 
>> have 
>>content that probably won't be very useful for you in them.
>>- There's a button for the ReadingInbox on the toolbar, but said 
>>inbox is not included in the edition at present. You can hide or delete 
>>that button tiddler.
>>
>> Please let me know what else does not work right – I'd love to add a 
>> build of this edition to my standard publish process in the future.
>> On Saturday, April 17, 2021 at 6:52:30 AM UTC-5 stan...@gmail.com wrote:
>>
>>> +1 to Walt's post.  Thanks, Soren, for the great contribution to the 
>>> community. This really helped me understand how to implement a Zettelkasten 
>>> in TW.  I, too, have been wondering how to filter out your content and keep 
>>> the skeleton, if that is at all possible. Thanks again.
>>>
>>> Stan
>>>
>>> On Saturday, April 17, 2021 at 7:17:38 AM UTC-4 ludwa6 wrote:
>>>
 Wow.  For all the buzz around the Digital Gardening/ Mind-Mapping 
 space, this is so far and away beyond anything i have seen... An amazing 
 gift to the commons, Soren; i just gotta give your system a try.

 To that end, i have just one question: what would be the easiest way to 
 filter out & delete all your content from the downloaded .html file, 
 without losing any of the many useful functions that you have outlined & 
 demoed so well?



 /walt

 On Thursday, April 15, 2021 at 4:15:49 AM UTC+1 Soren Bjornstad wrote:

> For those who have been interested in my public Zettelkasten wiki 
>  in the past (or might be 
> interested in it now), I've just put up an extensive discussion of 
> Zettelkasten and how I've implemented it in my TiddlyWiki on my YouTube 
> channel:
>
> https://www.youtube.com/watch?v=GjpjE5pMZMI
>
> Here are the segments if you're curious:
>
> *About Zettelkasten:*
> 0:00 Welcome and introduction
> 1:00 Public and private versions of my Zettelkasten
> 2:08 What is a Zettelkasten?
> 4:16 What idea tiddlers look like and how we navigate through them
> 6:28 Implementation evolves with the content
>
> *Organizing my Zettelkasten and relating ideas:*
> 7:06 Why I use CamelCase names
> 8:12 Expressing relationships by linking
> 9:40 Expressing memberships by tagging
> 10:07 Tags serve in many roles – topics/indexes, publicity level, 
> lists, types, pseudo-types, and maintenance
> 15:42 Index tiddlers provide overviews of a topic area
> 17:33 Transclusion can combine with the ‘description’ field to create 
> overviews
> 18:42 Why I don’t use tags for all overviews
> 19:28 Stretchtext creates interactive, expandable overviews
> 20:42 Subtiddlers aggregate tightly coupled content
> 23:58 Bibliographies aggregate related sources
> 25:38 The Write tab highlights fruitful areas for further work (stubs, 
> missing, needing attention, needing excision, to-dos, open questions)
> 29:58 The Reference Explorer shows related tiddlers (backlinks and 
> forward links) in a concise table
> 34:48 Graph 

[tw5] Re: [Introducing] TiddlyJam - new Plugin, CMS and static website generator

[Adithya B]

Hi Flohit,

I have added some notes on how to get started/customize your website 
here: https://tiddlyjam.com/
Could you check it out and let me know if that helps you?

On categories: I am still getting around to writing support for them into 
the system. Will update that in a few weeks.

Adithya
On Thursday, March 25, 2021 at 1:27:16 PM UTC-6 flohit...@googlemail.com 
wrote:

> So, I have been trying it out. 
>
> I really like the website you created for yourself, but its not really 
> clear how you managed that :D 
> For example where can i change the css? could i just use an existing TW 
> theme that I don't use for the non-static TW and set it up as a template? 
> that would be quite cool bc we would instantly have some cool templates :) 
> Or use the CSS packages for TW that exist (also the icon packs - feather is 
> quite cool)
> Then, what are categories for - how do i use them? How do i, in general 
> include tiddlers that are not  pages or blogs like you did? 
> by the way, here is another, older try at what you're doing - i thought 
> the idea of creating a framework was worthwile, but on the other hand, it 
> uses so many tags...  https://github.com/welford/twstaticblog
>  i don't know if it helps but i discovered an easy toggleable sidebar in a 
> jekyll theme when i was trying to work with that which works with a minimum 
> of javascript for the button, i could show you that one - I used to copy 
> that over to over themes, which was pretty easy. I don't even know if 
> that's possible to include though ^^
>
>
> bmad...@gmail.com schrieb am Dienstag, 16. März 2021 um 22:24:57 UTC+1:
>
>> Looks like fun!
>> On Tuesday, March 16, 2021 at 11:15:51 AM UTC-6 flohit...@googlemail.com 
>> wrote:
>>
>>> cool! would love graphing, i was first starting with this jekyll 
>>> template (the map is on the bottom of the side): 
>>> https://digital-garden-jekyll-template.netlify.app/cats  --- i think 
>>> there could be possibilities using the graphviz and vis.js libraries that 
>>> are available as plugins. I should maybe make an own post for that. 
>>>
>>> bmad...@gmail.com schrieb am Dienstag, 16. März 2021 um 17:50:44 UTC+1:
>>>
 Thanks for your comment!

 To answer your question about the plans for this project:
 Toggleable sidebar and search - yes
 Graph-visualization - probably not (its possible though)
 On Tuesday, March 16, 2021 at 10:49:02 AM UTC-6 
 flohit...@googlemail.com wrote:

> This all looks very lovely :) especially your own website.
> I am also looking for a "digital gardening" tool, though i'm not 
> capable of coding myself.
> This and jeremys announcement are making me hopeful for finally being 
> able to settling for tiddlywiki - i was just going to start to look into 
> org-roam, although i have found so many cool features in TW.
> You are not planning on adding things like a toggleable-sidebar, a 
> graph - visualization, and a search, though, are you (:
>
> bmad...@gmail.com schrieb am Sonntag, 14. März 2021 um 18:17:56 UTC+1:
>
>> Hi everyone!
>>
>> I have been working on a static website generator/CMS plugin for 
>> TiddlyWiki for my personal use for the past six months or so. Finally, I 
>> feel I am ready to share it!
>>
>>- Have a look at the rendered website at https://tiddlyjam.com
>>- The github repo is at 
>>https://github.com/adithya-badidey/tiddlyjam
>>- Actual wiki is at https://tiddlyjam.com/tiddly
>>- Its still in alpha - please share bugs, comments, feedback - 
>>either here or at 
>>https://github.com/adithya-badidey/tiddlyjam/discussions
>>
>> Cheers!
>> Adithya
>>
>

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

[tw5] Re: A tour through my Zettelkasten

[PMario]

On Saturday, April 17, 2021 at 8:30:57 PM UTC+2 ludwa6 wrote:
...

> I really love the system overall, but just can't get the hang of this text 
> editor variant, so if there's any way to make it revert to standard, i'd 
> sure like to know how.
>

First delete $:/config/codemirror/keyMap 
You can go to the control-panel and delete the codemirror-keymap-vim 
tiddler. 
Install codemirror-keymap-sublime or emacs  from the official plugin library
Then set the keymap config to sublime or emacs. 

-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/c1e7bdbc-5c56-48f4-9f72-23cc95b88b0dn%40googlegroups.com.

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

['Mark S.' via TiddlyWiki]

Question 2. How do you apply .kooltip ?

On Saturday, April 17, 2021 at 1:47:57 PM UTC-7 Mark S. wrote:

> Hi Mohammad,
>
> How do you test your code? On a small device? Portrait mode? Or ... ?
>
> On Saturday, April 17, 2021 at 10:48:00 AM UTC-7 Mohammad wrote:
>
>> Hi Brian,
>>  You are right! the code does not work for me and the solution is not 
>> based on TW recommendation! So I gave up and
>> will stay to see what Jeremy decides on 
>> https://github.com/Jermolene/TiddlyWiki5/issues/4531#issue-591121784
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Sat, Apr 17, 2021 at 10:01 PM Brian Theado  
>> wrote:
>>
>>> Will all your .tooltip dom elements be static and available when the 
>>> rawMarkup script runs? The way you have the code, this will run just once:
>>>
>>> var ktooltips = document.querySelectorAll(".tooltip");
>>>
>>>
>>> Any new DOM elements which come after will not be picked up 
>>> automatically.
>>>
>>> If you want to make it dynamic, then it might work to register 
>>> a th-page-refreshed hook by calling $tw.hooks.addHook 
>>>
>>> Change your main code into a function and register that with the addHook 
>>> call.  IOW, put this code into a function:
>>>
>>> var ktooltips = document.querySelectorAll(".ktooltip");
>>> ktooltips.forEach(function(ktooltip, index){// For each 
>>> ktooltip
>>>   ktooltip.addEventListener("mouseover", position_tooltip); // On 
>>> hover, launch the function below
>>> })
>>>
>>>
>>> Instead of tagging the tiddler as RawMarkup, you can set the module-type 
>>> field to 'startup'.
>>>
>>> One worry I have is that your code will be called on every refresh and 
>>> the call to addEventListener will happen on every matching dom element 
>>> every time. You should research that method to see if your event listeners 
>>> will continually accumulate (i.e. getting added over and over until the dom 
>>> element goes away). If that is the case, then you would probably want some 
>>> way to avoid adding the listener multiple times.
>>>
>>> I've never used the tw addHook...just sharing in case it helps you.  
>>> Also, this solution altogether seems a little "hacky" and not really in 
>>> line with the tiddlywiki-way.
>>>
>>> Here is a link to documentation for addHook and startup modules:
>>>
>>>
>>> https://tiddlywiki.com/dev/#StartupMechanism:StartupMechanism%20HookMechanism%20%5B%5BHook%3A%20th-page-refreshed%5D%5D%20HelloThere%20Introduction
>>>
>>>
>>> On Sat, Apr 17, 2021 at 12:20 PM 'Mark S.' via TiddlyWiki <
>>> tiddl...@googlegroups.com> wrote:
>>>
 You could try putting in it's own tiddler:

 tags: $:/tags/RawMarkup
 type: application/javascript

 
  code ...
 

 Note that you have to save and reload before anything happens. I would 
 not be surprised if something clashes with TW's rendering system, though.

 On Saturday, April 17, 2021 at 7:38:41 AM UTC-7 Mohammad wrote:

> What is the simplest way to have the below JS code into a Tiddlywiki 
> plugin! It is not a macro, nor a widget!
>
> var ktooltips = document.querySelectorAll(".ktooltip");
> ktooltips.forEach(function(ktooltip, index){// For 
> each ktooltip
>   ktooltip.addEventListener("mouseover", position_tooltip); // On 
> hover, launch the function below
> })
>
> function position_tooltip(){
>   // Get .ktooltiptext sibling
>   var tooltip = this.parentNode.querySelector(".ktooltiptext");
>   
>   // Get calculated ktooltip coordinates and size
>   var ktooltip_rect = this.getBoundingClientRect();
>
>   var tipX = ktooltip_rect.width + 5; // 5px on the right of the 
> ktooltip
>   var tipY = -40; // 40px on the top of the 
> ktooltip
>   // Position tooltip
>   tooltip.style.top = tipY + 'px';
>   tooltip.style.left = tipX + 'px';
>
>   // Get calculated tooltip coordinates and size
>   var tooltip_rect = tooltip.getBoundingClientRect();
>   // Corrections if out of window
>   if ((tooltip_rect.x + tooltip_rect.width) > window.innerWidth) // 
> Out on the right
> tipX = -tooltip_rect.width - 5;  // Simulate a "right: tipX" 
> position
>   if (tooltip_rect.y < 0)// Out on the top
> tipY = tipY - tooltip_rect.y;// Align on the top
>
>   // Apply corrected position
>   tooltip.style.top = tipY + 'px';
>   tooltip.style.left = tipX + 'px';
> }
>
> This is a partial solution for repositioning the tooltips to prevent 
> screen overflow (off screen issue)!
>
>
> 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 
 

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

['Mark S.' via TiddlyWiki]

Hi Mohammad,

How do you test your code? On a small device? Portrait mode? Or ... ?

On Saturday, April 17, 2021 at 10:48:00 AM UTC-7 Mohammad wrote:

> Hi Brian,
>  You are right! the code does not work for me and the solution is not 
> based on TW recommendation! So I gave up and
> will stay to see what Jeremy decides on 
> https://github.com/Jermolene/TiddlyWiki5/issues/4531#issue-591121784
>
>
> Best wishes
> Mohammad
>
>
> On Sat, Apr 17, 2021 at 10:01 PM Brian Theado  wrote:
>
>> Will all your .tooltip dom elements be static and available when the 
>> rawMarkup script runs? The way you have the code, this will run just once:
>>
>> var ktooltips = document.querySelectorAll(".tooltip");
>>
>>
>> Any new DOM elements which come after will not be picked up automatically.
>>
>> If you want to make it dynamic, then it might work to register 
>> a th-page-refreshed hook by calling $tw.hooks.addHook 
>>
>> Change your main code into a function and register that with the addHook 
>> call.  IOW, put this code into a function:
>>
>> var ktooltips = document.querySelectorAll(".ktooltip");
>> ktooltips.forEach(function(ktooltip, index){// For each 
>> ktooltip
>>   ktooltip.addEventListener("mouseover", position_tooltip); // On hover, 
>> launch the function below
>> })
>>
>>
>> Instead of tagging the tiddler as RawMarkup, you can set the module-type 
>> field to 'startup'.
>>
>> One worry I have is that your code will be called on every refresh and 
>> the call to addEventListener will happen on every matching dom element 
>> every time. You should research that method to see if your event listeners 
>> will continually accumulate (i.e. getting added over and over until the dom 
>> element goes away). If that is the case, then you would probably want some 
>> way to avoid adding the listener multiple times.
>>
>> I've never used the tw addHook...just sharing in case it helps you.  
>> Also, this solution altogether seems a little "hacky" and not really in 
>> line with the tiddlywiki-way.
>>
>> Here is a link to documentation for addHook and startup modules:
>>
>>
>> https://tiddlywiki.com/dev/#StartupMechanism:StartupMechanism%20HookMechanism%20%5B%5BHook%3A%20th-page-refreshed%5D%5D%20HelloThere%20Introduction
>>
>>
>> On Sat, Apr 17, 2021 at 12:20 PM 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>> You could try putting in it's own tiddler:
>>>
>>> tags: $:/tags/RawMarkup
>>> type: application/javascript
>>>
>>> 
>>>  code ...
>>> 
>>>
>>> Note that you have to save and reload before anything happens. I would 
>>> not be surprised if something clashes with TW's rendering system, though.
>>>
>>> On Saturday, April 17, 2021 at 7:38:41 AM UTC-7 Mohammad wrote:
>>>
 What is the simplest way to have the below JS code into a Tiddlywiki 
 plugin! It is not a macro, nor a widget!

 var ktooltips = document.querySelectorAll(".ktooltip");
 ktooltips.forEach(function(ktooltip, index){// For each 
 ktooltip
   ktooltip.addEventListener("mouseover", position_tooltip); // On 
 hover, launch the function below
 })

 function position_tooltip(){
   // Get .ktooltiptext sibling
   var tooltip = this.parentNode.querySelector(".ktooltiptext");
   
   // Get calculated ktooltip coordinates and size
   var ktooltip_rect = this.getBoundingClientRect();

   var tipX = ktooltip_rect.width + 5; // 5px on the right of the 
 ktooltip
   var tipY = -40; // 40px on the top of the ktooltip
   // Position tooltip
   tooltip.style.top = tipY + 'px';
   tooltip.style.left = tipX + 'px';

   // Get calculated tooltip coordinates and size
   var tooltip_rect = tooltip.getBoundingClientRect();
   // Corrections if out of window
   if ((tooltip_rect.x + tooltip_rect.width) > window.innerWidth) // Out 
 on the right
 tipX = -tooltip_rect.width - 5;  // Simulate a "right: tipX" 
 position
   if (tooltip_rect.y < 0)// Out on the top
 tipY = tipY - tooltip_rect.y;// Align on the top

   // Apply corrected position
   tooltip.style.top = tipY + 'px';
   tooltip.style.left = tipX + 'px';
 }

 This is a partial solution for repositioning the tooltips to prevent 
 screen overflow (off screen issue)!


 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/15fb086c-650b-4f3e-affd-84067b7b0632n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You 

[tw5] Re: EditTextWidget: ouch when tiddler=currentTiddler and using index

[Charlie Veniot]

And there it is:   A How To Prototype: An edit toolbar button to add 
widgets to a tiddler 

On Saturday, April 17, 2021 at 1:32:13 PM UTC-3 Charlie Veniot wrote:

> I've got this idea festering:
>
> Add a select widget to the Editor Toolbar, a "insert a widget" widget.
>
> Populate this select widget with a list of "canned" wikitext for 
> pre-configured widgets.
>
> Every single item in the select widget will insert, at the cursor 
> location, the wikitext for the relevant pre-configured widget.
>
> Each pre-configured widget will have "tiddler" parameter set to the macro 
> <>
>
> The code for the GetDataTid macro:
>
> \define  GetDataTid()
>
> {{{ [is[tiddler]] [addsuffix[ Data]] +[first[]] 
> }}}
>
> \end
>
> For any widget in a tiddler without the variable  defined, 
> GetDataTid will say the Data Tiddler for whatever widget is the title of a 
> tiddler = the current tiddler with suffix " Data" added.
>
> If  is defined and is a valid tiddler, then GetDataTid will say 
> the Data Tiddler for whatever widget is the title specified by .
>
> So as long as I always use the "select widget" widget in the editor 
> toolbar, I should stop running into problems.
>
> Maybe?
>
>
>
> On Friday, April 16, 2021 at 10:50:54 PM UTC-3 Charlie Veniot wrote:
>
>> G'day all,
>>
>> I have been bitten by this one too many times.  This wouldn't happen if I 
>> did not so stubbornly preferred data tiddlers for storing data values, 
>> instead of using tiddler fields.
>>
>> But, dang it: I really like data tiddlers for some strange reason.
>>
>> As I setup EditText widgets in some tiddler  (let's call this a "Form" 
>> tiddler) to maintain values stored in a data tiddler, I often make a 
>> mistake setting up one or more widgets in a way that winds up blowing away 
>> the content of the "Form" tiddler.
>>
>> As a trivial/ridiculous simulation that duplicates my regular 
>> self-inflicted drop-kick through the goalposts of life, create a new 
>> tiddler with the following content:
>>
>> [image: Screenshot 2021-04-16 10.41.02 PM.png]
>>
>> Save that tiddler and type some letter key on your keyboard in this text 
>> field.  Wham.   Now the tiddler looks something like the following (with 
>> the field "bub" set to whatever key ):
>>
>> [image: Screenshot 2021-04-16 10.25.18 PM.png]
>>
>> Is there some way for me to tell TiddlyWiki: never allow "index" to be 
>> used with tiddler = currentTiddler (either explicitly set or implicitly 
>> assumed) for any widget?
>>
>>
>>
>>  
>>
>>
>>

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

[tw5] A How To Prototype: An edit toolbar button to add widgets to a tiddler

[Charlie Veniot]

G'day,

Following up on an idea from the EditTextWidget: ouch when 
tiddler=currentTiddler and using index 
 conversation:

A Widgets Dropdown Button on EditToolbar 


[image: Screenshot 2021-04-17 3.50.41 PM - Display 2.png]



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

[tw5] Re: A tour through my Zettelkasten

[ludwa6]

OK, after struggling w/ this a bit, i have to stop and ask: is there 
something that would cause the editor widget to behave very differently 
from standard TW5?  Triple-click on a tiddler to edit (new one on me, but 
that's cool), and then -instead of opening into a typical text box- it's a 
single line edit widget, with a blinking green box instead of simple cursor 
(flashback to ye ole VT100 term-em days :-) that does not respond to key 
commands as usual: hitting space bar or backspace key moves the cursor as 
though i were hitting forward and back arrows.  So i wonder: is this maybe 
configured for external editor control, somehow?  I really love the system 
overall, but just can't get the hang of this text editor variant, so if 
there's any way to make it revert to standard, i'd sure like to know how.
On Saturday, April 17, 2021 at 6:06:29 PM UTC+1 Soren Bjornstad wrote:

> The public version lacks some functionality that is important for editing 
> and has a bunch of settings changed that are a bit of a pain to change 
> back, so it'll be much better if I do a second build off of the "real" 
> private version. I've attached a first 15-minute attempt at this.
>
> Things that could use improvement here:
>
>- There are no instructions at all, so you'll have to figure out how 
>to get started on your own. Some of the conventions tiddlers are missing 
>and would be nice to have.
>- I included all the red, yellow, and black tag tiddlers, but since 
>there is no content in this version, most of them are not tagging 
> anything, 
>so they don't show up in the tags list. Also, some of the tag tiddlers 
> have 
>content that probably won't be very useful for you in them.
>- There's a button for the ReadingInbox on the toolbar, but said inbox 
>is not included in the edition at present. You can hide or delete that 
>button tiddler.
>
> Please let me know what else does not work right – I'd love to add a build 
> of this edition to my standard publish process in the future.
> On Saturday, April 17, 2021 at 6:52:30 AM UTC-5 stan...@gmail.com wrote:
>
>> +1 to Walt's post.  Thanks, Soren, for the great contribution to the 
>> community. This really helped me understand how to implement a Zettelkasten 
>> in TW.  I, too, have been wondering how to filter out your content and keep 
>> the skeleton, if that is at all possible. Thanks again.
>>
>> Stan
>>
>> On Saturday, April 17, 2021 at 7:17:38 AM UTC-4 ludwa6 wrote:
>>
>>> Wow.  For all the buzz around the Digital Gardening/ Mind-Mapping space, 
>>> this is so far and away beyond anything i have seen... An amazing gift to 
>>> the commons, Soren; i just gotta give your system a try.
>>>
>>> To that end, i have just one question: what would be the easiest way to 
>>> filter out & delete all your content from the downloaded .html file, 
>>> without losing any of the many useful functions that you have outlined & 
>>> demoed so well?
>>>
>>>
>>>
>>> /walt
>>>
>>> On Thursday, April 15, 2021 at 4:15:49 AM UTC+1 Soren Bjornstad wrote:
>>>
 For those who have been interested in my public Zettelkasten wiki 
  in the past (or might be 
 interested in it now), I've just put up an extensive discussion of 
 Zettelkasten and how I've implemented it in my TiddlyWiki on my YouTube 
 channel:

 https://www.youtube.com/watch?v=GjpjE5pMZMI

 Here are the segments if you're curious:

 *About Zettelkasten:*
 0:00 Welcome and introduction
 1:00 Public and private versions of my Zettelkasten
 2:08 What is a Zettelkasten?
 4:16 What idea tiddlers look like and how we navigate through them
 6:28 Implementation evolves with the content

 *Organizing my Zettelkasten and relating ideas:*
 7:06 Why I use CamelCase names
 8:12 Expressing relationships by linking
 9:40 Expressing memberships by tagging
 10:07 Tags serve in many roles – topics/indexes, publicity level, 
 lists, types, pseudo-types, and maintenance
 15:42 Index tiddlers provide overviews of a topic area
 17:33 Transclusion can combine with the ‘description’ field to create 
 overviews
 18:42 Why I don’t use tags for all overviews
 19:28 Stretchtext creates interactive, expandable overviews
 20:42 Subtiddlers aggregate tightly coupled content
 23:58 Bibliographies aggregate related sources
 25:38 The Write tab highlights fruitful areas for further work (stubs, 
 missing, needing attention, needing excision, to-dos, open questions)
 29:58 The Reference Explorer shows related tiddlers (backlinks and 
 forward links) in a concise table
 34:48 Graph theory and Zettelkästen; link graph
 37:11 Types of tiddlers; why I include non-idea tiddlers, unlike 
 classic Zettelkasten

 *Plugins and custom TiddlyWiki logic:*
 41:04 Interesting TiddlyWiki plugins I use
 47:17 Publishing only part of a 

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

[Mohammad Rahmani]

Hi Brian,
 You are right! the code does not work for me and the solution is not based
on TW recommendation! So I gave up and
will stay to see what Jeremy decides on
https://github.com/Jermolene/TiddlyWiki5/issues/4531#issue-591121784


Best wishes
Mohammad


On Sat, Apr 17, 2021 at 10:01 PM Brian Theado 
wrote:

> Will all your .tooltip dom elements be static and available when the
> rawMarkup script runs? The way you have the code, this will run just once:
>
> var ktooltips = document.querySelectorAll(".tooltip");
>
>
> Any new DOM elements which come after will not be picked up automatically.
>
> If you want to make it dynamic, then it might work to register
> a th-page-refreshed hook by calling $tw.hooks.addHook
>
> Change your main code into a function and register that with the addHook
> call.  IOW, put this code into a function:
>
> var ktooltips = document.querySelectorAll(".ktooltip");
> ktooltips.forEach(function(ktooltip, index){// For each
> ktooltip
>   ktooltip.addEventListener("mouseover", position_tooltip); // On hover,
> launch the function below
> })
>
>
> Instead of tagging the tiddler as RawMarkup, you can set the module-type
> field to 'startup'.
>
> One worry I have is that your code will be called on every refresh and the
> call to addEventListener will happen on every matching dom element every
> time. You should research that method to see if your event listeners will
> continually accumulate (i.e. getting added over and over until the dom
> element goes away). If that is the case, then you would probably want some
> way to avoid adding the listener multiple times.
>
> I've never used the tw addHook...just sharing in case it helps you.  Also,
> this solution altogether seems a little "hacky" and not really in line with
> the tiddlywiki-way.
>
> Here is a link to documentation for addHook and startup modules:
>
>
> https://tiddlywiki.com/dev/#StartupMechanism:StartupMechanism%20HookMechanism%20%5B%5BHook%3A%20th-page-refreshed%5D%5D%20HelloThere%20Introduction
>
>
> On Sat, Apr 17, 2021 at 12:20 PM 'Mark S.' via TiddlyWiki <
> tiddlywiki@googlegroups.com> wrote:
>
>> You could try putting in it's own tiddler:
>>
>> tags: $:/tags/RawMarkup
>> type: application/javascript
>>
>> 
>>  code ...
>> 
>>
>> Note that you have to save and reload before anything happens. I would
>> not be surprised if something clashes with TW's rendering system, though.
>>
>> On Saturday, April 17, 2021 at 7:38:41 AM UTC-7 Mohammad wrote:
>>
>>> What is the simplest way to have the below JS code into a Tiddlywiki
>>> plugin! It is not a macro, nor a widget!
>>>
>>> var ktooltips = document.querySelectorAll(".ktooltip");
>>> ktooltips.forEach(function(ktooltip, index){// For each
>>> ktooltip
>>>   ktooltip.addEventListener("mouseover", position_tooltip); // On hover,
>>> launch the function below
>>> })
>>>
>>> function position_tooltip(){
>>>   // Get .ktooltiptext sibling
>>>   var tooltip = this.parentNode.querySelector(".ktooltiptext");
>>>
>>>   // Get calculated ktooltip coordinates and size
>>>   var ktooltip_rect = this.getBoundingClientRect();
>>>
>>>   var tipX = ktooltip_rect.width + 5; // 5px on the right of the ktooltip
>>>   var tipY = -40; // 40px on the top of the ktooltip
>>>   // Position tooltip
>>>   tooltip.style.top = tipY + 'px';
>>>   tooltip.style.left = tipX + 'px';
>>>
>>>   // Get calculated tooltip coordinates and size
>>>   var tooltip_rect = tooltip.getBoundingClientRect();
>>>   // Corrections if out of window
>>>   if ((tooltip_rect.x + tooltip_rect.width) > window.innerWidth) // Out
>>> on the right
>>> tipX = -tooltip_rect.width - 5;  // Simulate a "right: tipX" position
>>>   if (tooltip_rect.y < 0)// Out on the top
>>> tipY = tipY - tooltip_rect.y;// Align on the top
>>>
>>>   // Apply corrected position
>>>   tooltip.style.top = tipY + 'px';
>>>   tooltip.style.left = tipX + 'px';
>>> }
>>>
>>> This is a partial solution for repositioning the tooltips to prevent
>>> screen overflow (off screen issue)!
>>>
>>>
>>> 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/15fb086c-650b-4f3e-affd-84067b7b0632n%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
> 

[tw5] Re: A tour through my Zettelkasten

[ludwa6]

Thanks, Soren!  I'm on it now -just trying to figure out how i can make 
this my home repo at github.io.  I think i've got to convert it from single 
file to node wiki (right?), but i've never done this. Should be fun! :-)

/walt

On Saturday, April 17, 2021 at 6:06:29 PM UTC+1 Soren Bjornstad wrote:

> The public version lacks some functionality that is important for editing 
> and has a bunch of settings changed that are a bit of a pain to change 
> back, so it'll be much better if I do a second build off of the "real" 
> private version. I've attached a first 15-minute attempt at this.
>
> Things that could use improvement here:
>
>- There are no instructions at all, so you'll have to figure out how 
>to get started on your own. Some of the conventions tiddlers are missing 
>and would be nice to have.
>- I included all the red, yellow, and black tag tiddlers, but since 
>there is no content in this version, most of them are not tagging 
> anything, 
>so they don't show up in the tags list. Also, some of the tag tiddlers 
> have 
>content that probably won't be very useful for you in them.
>- There's a button for the ReadingInbox on the toolbar, but said inbox 
>is not included in the edition at present. You can hide or delete that 
>button tiddler.
>
> Please let me know what else does not work right – I'd love to add a build 
> of this edition to my standard publish process in the future.
> On Saturday, April 17, 2021 at 6:52:30 AM UTC-5 stan...@gmail.com wrote:
>
>> +1 to Walt's post.  Thanks, Soren, for the great contribution to the 
>> community. This really helped me understand how to implement a Zettelkasten 
>> in TW.  I, too, have been wondering how to filter out your content and keep 
>> the skeleton, if that is at all possible. Thanks again.
>>
>> Stan
>>
>> On Saturday, April 17, 2021 at 7:17:38 AM UTC-4 ludwa6 wrote:
>>
>>> Wow.  For all the buzz around the Digital Gardening/ Mind-Mapping space, 
>>> this is so far and away beyond anything i have seen... An amazing gift to 
>>> the commons, Soren; i just gotta give your system a try.
>>>
>>> To that end, i have just one question: what would be the easiest way to 
>>> filter out & delete all your content from the downloaded .html file, 
>>> without losing any of the many useful functions that you have outlined & 
>>> demoed so well?
>>>
>>>
>>>
>>> /walt
>>>
>>> On Thursday, April 15, 2021 at 4:15:49 AM UTC+1 Soren Bjornstad wrote:
>>>
 For those who have been interested in my public Zettelkasten wiki 
  in the past (or might be 
 interested in it now), I've just put up an extensive discussion of 
 Zettelkasten and how I've implemented it in my TiddlyWiki on my YouTube 
 channel:

 https://www.youtube.com/watch?v=GjpjE5pMZMI

 Here are the segments if you're curious:

 *About Zettelkasten:*
 0:00 Welcome and introduction
 1:00 Public and private versions of my Zettelkasten
 2:08 What is a Zettelkasten?
 4:16 What idea tiddlers look like and how we navigate through them
 6:28 Implementation evolves with the content

 *Organizing my Zettelkasten and relating ideas:*
 7:06 Why I use CamelCase names
 8:12 Expressing relationships by linking
 9:40 Expressing memberships by tagging
 10:07 Tags serve in many roles – topics/indexes, publicity level, 
 lists, types, pseudo-types, and maintenance
 15:42 Index tiddlers provide overviews of a topic area
 17:33 Transclusion can combine with the ‘description’ field to create 
 overviews
 18:42 Why I don’t use tags for all overviews
 19:28 Stretchtext creates interactive, expandable overviews
 20:42 Subtiddlers aggregate tightly coupled content
 23:58 Bibliographies aggregate related sources
 25:38 The Write tab highlights fruitful areas for further work (stubs, 
 missing, needing attention, needing excision, to-dos, open questions)
 29:58 The Reference Explorer shows related tiddlers (backlinks and 
 forward links) in a concise table
 34:48 Graph theory and Zettelkästen; link graph
 37:11 Types of tiddlers; why I include non-idea tiddlers, unlike 
 classic Zettelkasten

 *Plugins and custom TiddlyWiki logic:*
 41:04 Interesting TiddlyWiki plugins I use
 47:17 Publishing only part of a TiddlyWiki (public/private switch): 
 Marking tiddlers
 49:05 Public/private: The PrivateChunk
 51:28 Public/private: The build process (shell script)
 54:18 Custom copy-title and permalink buttons
 55:38 GIS (mapping) support for places
 57:55 The missing-tiddler helper
 58:36 Quick reading-list import by pasting a URL
 59:30 Reading inbox
 1:00:15 Simple Analytics and raw markup snippets
 1:01:05 Sorting tags by color and putting them in columns

 *Philosophy:*
 1:03:01 Just get started and then continuously improve
 1:05:20 

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

[Brian Theado]

Will all your .tooltip dom elements be static and available when the
rawMarkup script runs? The way you have the code, this will run just once:

var ktooltips = document.querySelectorAll(".tooltip");


Any new DOM elements which come after will not be picked up automatically.

If you want to make it dynamic, then it might work to register
a th-page-refreshed hook by calling $tw.hooks.addHook

Change your main code into a function and register that with the addHook
call.  IOW, put this code into a function:

var ktooltips = document.querySelectorAll(".ktooltip");
ktooltips.forEach(function(ktooltip, index){// For each
ktooltip
  ktooltip.addEventListener("mouseover", position_tooltip); // On hover,
launch the function below
})


Instead of tagging the tiddler as RawMarkup, you can set the module-type
field to 'startup'.

One worry I have is that your code will be called on every refresh and the
call to addEventListener will happen on every matching dom element every
time. You should research that method to see if your event listeners will
continually accumulate (i.e. getting added over and over until the dom
element goes away). If that is the case, then you would probably want some
way to avoid adding the listener multiple times.

I've never used the tw addHook...just sharing in case it helps you.  Also,
this solution altogether seems a little "hacky" and not really in line with
the tiddlywiki-way.

Here is a link to documentation for addHook and startup modules:

https://tiddlywiki.com/dev/#StartupMechanism:StartupMechanism%20HookMechanism%20%5B%5BHook%3A%20th-page-refreshed%5D%5D%20HelloThere%20Introduction


On Sat, Apr 17, 2021 at 12:20 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> You could try putting in it's own tiddler:
>
> tags: $:/tags/RawMarkup
> type: application/javascript
>
> 
>  code ...
> 
>
> Note that you have to save and reload before anything happens. I would not
> be surprised if something clashes with TW's rendering system, though.
>
> On Saturday, April 17, 2021 at 7:38:41 AM UTC-7 Mohammad wrote:
>
>> What is the simplest way to have the below JS code into a Tiddlywiki
>> plugin! It is not a macro, nor a widget!
>>
>> var ktooltips = document.querySelectorAll(".ktooltip");
>> ktooltips.forEach(function(ktooltip, index){// For each
>> ktooltip
>>   ktooltip.addEventListener("mouseover", position_tooltip); // On hover,
>> launch the function below
>> })
>>
>> function position_tooltip(){
>>   // Get .ktooltiptext sibling
>>   var tooltip = this.parentNode.querySelector(".ktooltiptext");
>>
>>   // Get calculated ktooltip coordinates and size
>>   var ktooltip_rect = this.getBoundingClientRect();
>>
>>   var tipX = ktooltip_rect.width + 5; // 5px on the right of the ktooltip
>>   var tipY = -40; // 40px on the top of the ktooltip
>>   // Position tooltip
>>   tooltip.style.top = tipY + 'px';
>>   tooltip.style.left = tipX + 'px';
>>
>>   // Get calculated tooltip coordinates and size
>>   var tooltip_rect = tooltip.getBoundingClientRect();
>>   // Corrections if out of window
>>   if ((tooltip_rect.x + tooltip_rect.width) > window.innerWidth) // Out
>> on the right
>> tipX = -tooltip_rect.width - 5;  // Simulate a "right: tipX" position
>>   if (tooltip_rect.y < 0)// Out on the top
>> tipY = tipY - tooltip_rect.y;// Align on the top
>>
>>   // Apply corrected position
>>   tooltip.style.top = tipY + 'px';
>>   tooltip.style.left = tipX + 'px';
>> }
>>
>> This is a partial solution for repositioning the tooltips to prevent
>> screen overflow (off screen issue)!
>>
>>
>> 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/15fb086c-650b-4f3e-affd-84067b7b0632n%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/CAO5X8Cxf4_5%2BVAf1HHW3J02Rsui1jtFg1X-s3Lj9HSTayBGFRQ%40mail.gmail.com.

Re: [tw5] Re: A tour through my Zettelkasten

[Mohammad Rahmani]

Thank you for sharing the empty version!


Best wishes
Mohammad


On Sat, Apr 17, 2021 at 9:36 PM Soren Bjornstad 
wrote:

> The public version lacks some functionality that is important for editing
> and has a bunch of settings changed that are a bit of a pain to change
> back, so it'll be much better if I do a second build off of the "real"
> private version. I've attached a first 15-minute attempt at this.
>
> Things that could use improvement here:
>
>- There are no instructions at all, so you'll have to figure out how
>to get started on your own. Some of the conventions tiddlers are missing
>and would be nice to have.
>- I included all the red, yellow, and black tag tiddlers, but since
>there is no content in this version, most of them are not tagging anything,
>so they don't show up in the tags list. Also, some of the tag tiddlers have
>content that probably won't be very useful for you in them.
>- There's a button for the ReadingInbox on the toolbar, but said inbox
>is not included in the edition at present. You can hide or delete that
>button tiddler.
>
> Please let me know what else does not work right – I'd love to add a build
> of this edition to my standard publish process in the future.
> On Saturday, April 17, 2021 at 6:52:30 AM UTC-5 stan...@gmail.com wrote:
>
>> +1 to Walt's post.  Thanks, Soren, for the great contribution to the
>> community. This really helped me understand how to implement a Zettelkasten
>> in TW.  I, too, have been wondering how to filter out your content and keep
>> the skeleton, if that is at all possible. Thanks again.
>>
>> Stan
>>
>> On Saturday, April 17, 2021 at 7:17:38 AM UTC-4 ludwa6 wrote:
>>
>>> Wow.  For all the buzz around the Digital Gardening/ Mind-Mapping space,
>>> this is so far and away beyond anything i have seen... An amazing gift to
>>> the commons, Soren; i just gotta give your system a try.
>>>
>>> To that end, i have just one question: what would be the easiest way to
>>> filter out & delete all your content from the downloaded .html file,
>>> without losing any of the many useful functions that you have outlined &
>>> demoed so well?
>>>
>>>
>>>
>>> /walt
>>>
>>> On Thursday, April 15, 2021 at 4:15:49 AM UTC+1 Soren Bjornstad wrote:
>>>
 For those who have been interested in my public Zettelkasten wiki
  in the past (or might be
 interested in it now), I've just put up an extensive discussion of
 Zettelkasten and how I've implemented it in my TiddlyWiki on my YouTube
 channel:

 https://www.youtube.com/watch?v=GjpjE5pMZMI

 Here are the segments if you're curious:

 *About Zettelkasten:*
 0:00 Welcome and introduction
 1:00 Public and private versions of my Zettelkasten
 2:08 What is a Zettelkasten?
 4:16 What idea tiddlers look like and how we navigate through them
 6:28 Implementation evolves with the content

 *Organizing my Zettelkasten and relating ideas:*
 7:06 Why I use CamelCase names
 8:12 Expressing relationships by linking
 9:40 Expressing memberships by tagging
 10:07 Tags serve in many roles – topics/indexes, publicity level,
 lists, types, pseudo-types, and maintenance
 15:42 Index tiddlers provide overviews of a topic area
 17:33 Transclusion can combine with the ‘description’ field to create
 overviews
 18:42 Why I don’t use tags for all overviews
 19:28 Stretchtext creates interactive, expandable overviews
 20:42 Subtiddlers aggregate tightly coupled content
 23:58 Bibliographies aggregate related sources
 25:38 The Write tab highlights fruitful areas for further work (stubs,
 missing, needing attention, needing excision, to-dos, open questions)
 29:58 The Reference Explorer shows related tiddlers (backlinks and
 forward links) in a concise table
 34:48 Graph theory and Zettelkästen; link graph
 37:11 Types of tiddlers; why I include non-idea tiddlers, unlike
 classic Zettelkasten

 *Plugins and custom TiddlyWiki logic:*
 41:04 Interesting TiddlyWiki plugins I use
 47:17 Publishing only part of a TiddlyWiki (public/private switch):
 Marking tiddlers
 49:05 Public/private: The PrivateChunk
 51:28 Public/private: The build process (shell script)
 54:18 Custom copy-title and permalink buttons
 55:38 GIS (mapping) support for places
 57:55 The missing-tiddler helper
 58:36 Quick reading-list import by pasting a URL
 59:30 Reading inbox
 1:00:15 Simple Analytics and raw markup snippets
 1:01:05 Sorting tags by color and putting them in columns

 *Philosophy:*
 1:03:01 Just get started and then continuously improve
 1:05:20 The Three-Links Heuristic for determining whether ideas are
 effectively linked together
 1:07:02 A Zettelkasten never walks backwards: consistency doesn’t
 matter that much
 1:08:56 Why I default to 

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

[Mohammad Rahmani]

Thank you Mark!


Best wishes
Mohammad


On Sat, Apr 17, 2021 at 8:50 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> You could try putting in it's own tiddler:
>
> tags: $:/tags/RawMarkup
> type: application/javascript
>
> 
>  code ...
> 
>
> Note that you have to save and reload before anything happens. I would not
> be surprised if something clashes with TW's rendering system, though.
>
> On Saturday, April 17, 2021 at 7:38:41 AM UTC-7 Mohammad wrote:
>
>> What is the simplest way to have the below JS code into a Tiddlywiki
>> plugin! It is not a macro, nor a widget!
>>
>> var ktooltips = document.querySelectorAll(".ktooltip");
>> ktooltips.forEach(function(ktooltip, index){// For each
>> ktooltip
>>   ktooltip.addEventListener("mouseover", position_tooltip); // On hover,
>> launch the function below
>> })
>>
>> function position_tooltip(){
>>   // Get .ktooltiptext sibling
>>   var tooltip = this.parentNode.querySelector(".ktooltiptext");
>>
>>   // Get calculated ktooltip coordinates and size
>>   var ktooltip_rect = this.getBoundingClientRect();
>>
>>   var tipX = ktooltip_rect.width + 5; // 5px on the right of the ktooltip
>>   var tipY = -40; // 40px on the top of the ktooltip
>>   // Position tooltip
>>   tooltip.style.top = tipY + 'px';
>>   tooltip.style.left = tipX + 'px';
>>
>>   // Get calculated tooltip coordinates and size
>>   var tooltip_rect = tooltip.getBoundingClientRect();
>>   // Corrections if out of window
>>   if ((tooltip_rect.x + tooltip_rect.width) > window.innerWidth) // Out
>> on the right
>> tipX = -tooltip_rect.width - 5;  // Simulate a "right: tipX" position
>>   if (tooltip_rect.y < 0)// Out on the top
>> tipY = tipY - tooltip_rect.y;// Align on the top
>>
>>   // Apply corrected position
>>   tooltip.style.top = tipY + 'px';
>>   tooltip.style.left = tipX + 'px';
>> }
>>
>> This is a partial solution for repositioning the tooltips to prevent
>> screen overflow (off screen issue)!
>>
>>
>> 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/15fb086c-650b-4f3e-affd-84067b7b0632n%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/CAAV1gMCJ46xOFf-u6HX3c40q5G-oihdQJiJgH15492vdbTfeNA%40mail.gmail.com.

[tw5] Re: EditTextWidget: ouch when tiddler=currentTiddler and using index

[Charlie Veniot]

I've got this idea festering:

Add a select widget to the Editor Toolbar, a "insert a widget" widget.

Populate this select widget with a list of "canned" wikitext for 
pre-configured widgets.

Every single item in the select widget will insert, at the cursor location, 
the wikitext for the relevant pre-configured widget.

Each pre-configured widget will have "tiddler" parameter set to the macro 
<>

The code for the GetDataTid macro:

\define  GetDataTid()

{{{ [is[tiddler]] [addsuffix[ Data]] +[first[]] }}}

\end

For any widget in a tiddler without the variable  defined, 
GetDataTid will say the Data Tiddler for whatever widget is the title of a 
tiddler = the current tiddler with suffix " Data" added.

If  is defined and is a valid tiddler, then GetDataTid will say 
the Data Tiddler for whatever widget is the title specified by .

So as long as I always use the "select widget" widget in the editor 
toolbar, I should stop running into problems.

Maybe?



On Friday, April 16, 2021 at 10:50:54 PM UTC-3 Charlie Veniot wrote:

> G'day all,
>
> I have been bitten by this one too many times.  This wouldn't happen if I 
> did not so stubbornly preferred data tiddlers for storing data values, 
> instead of using tiddler fields.
>
> But, dang it: I really like data tiddlers for some strange reason.
>
> As I setup EditText widgets in some tiddler  (let's call this a "Form" 
> tiddler) to maintain values stored in a data tiddler, I often make a 
> mistake setting up one or more widgets in a way that winds up blowing away 
> the content of the "Form" tiddler.
>
> As a trivial/ridiculous simulation that duplicates my regular 
> self-inflicted drop-kick through the goalposts of life, create a new 
> tiddler with the following content:
>
> [image: Screenshot 2021-04-16 10.41.02 PM.png]
>
> Save that tiddler and type some letter key on your keyboard in this text 
> field.  Wham.   Now the tiddler looks something like the following (with 
> the field "bub" set to whatever key ):
>
> [image: Screenshot 2021-04-16 10.25.18 PM.png]
>
> Is there some way for me to tell TiddlyWiki: never allow "index" to be 
> used with tiddler = currentTiddler (either explicitly set or implicitly 
> assumed) for any widget?
>
>
>
>  
>
>
>

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

[tw5] Re: How to use 2 fields to create a filter in a visjstimeline widget

[jln]

Thank you very much Mark. I couldn't get your solution to work, but I did 
it differently, with a macro:

\define concatenate_filter(fd fi) 
<$visjstimeline filter="[$fd$$fi$]" startDateField="date-debut" 
endDateField="date-fin" format="-MM-DD" groupField="institution" 
boxing="auto" navpad />
\end

<$macrocall $name="concatenate_filter" fd={{!!filtre_domaine}} 
fi={{!!filtre_institution}} />
Le vendredi 16 avril 2021 à 20:18:59 UTC+2, Mark S. a écrit :

> Try:
>
> <$visjstimeline 
> filter="[get[filtre_domaine]compare:string:eq{!!filtre_institution}]"
>  
> startDateField="date-debut" endDateField="date-fin" format="-MM-DD" 
> groupField="institution" boxing="auto" navpad />
>
> This requires a recent edition of TW since it uses the compare operator.
>
> Double braces (e.g. {{ and }} ) don't work inside of filters. They get 
> reduced to single braces (as above). Text substitution only works inside of 
> macros, so here instead I use the "get" operator to fetch the contents of 
> the filtre-_domaine field and then compare it with the contents of 
> filtre_institution. It's good practice to put your filter inside double 
> quotes.
>
> This is a case where seeing a website would help -- setting up my own 
> visjstimeline test site might take hours.
>
> Good luck!
>
> On Friday, April 16, 2021 at 7:28:49 AM UTC-7 jln wrote:
>
>> Hi,
>>
>> I've a field named "filtre_domaine" with value tag[AÀP] and a second one 
>> named "filtre_institution" with value field:institution[CLARA]
>>
>> I would like to "inject" these values into a visjstimeline widget
>>
>> The following doesn't work :
>>
>> <$visjstimeline filter=[{{!!filtre_domaine}}{{!!filtre_institution}}] 
>> startDateField="date-debut" endDateField="date-fin" format="-MM-DD" 
>> groupField="institution" boxing="auto" navpad />
>>
>> so I guess I've to create a macro to concatenate the fields values:
>>
>> \define concatenate_filter() 
>> [{{!!filtre_domaine}}{{!!filtre_institution}}]
>>
>> The "result" of the macro is fine: when I call <> I 
>> get 
>>
>> tag[AÀP]field:institution[CLARA]]
>> and if I copy/paste this litteral result into the widget, the Gantt chart 
>> is ok.
>>
>> But it doesn't work when I try to call the macro inside the widget:
>>
>> <$visjstimeline filter=<> startDateField="date-debut" 
>> endDateField="date-fin" format="-MM-DD" groupField="institution" 
>> boxing="auto" navpad />. I get "Filter error: Missing [ in filter 
>> expression" but I dont' undertand why…
>>
>> Thanks!
>>
>>

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

[tw5] Re: The simplest way to include the JS code into Tiddlywiki

['Mark S.' via TiddlyWiki]

You could try putting in it's own tiddler:

tags: $:/tags/RawMarkup
type: application/javascript


 code ...


Note that you have to save and reload before anything happens. I would not 
be surprised if something clashes with TW's rendering system, though.

On Saturday, April 17, 2021 at 7:38:41 AM UTC-7 Mohammad wrote:

> What is the simplest way to have the below JS code into a Tiddlywiki 
> plugin! It is not a macro, nor a widget!
>
> var ktooltips = document.querySelectorAll(".ktooltip");
> ktooltips.forEach(function(ktooltip, index){// For each 
> ktooltip
>   ktooltip.addEventListener("mouseover", position_tooltip); // On hover, 
> launch the function below
> })
>
> function position_tooltip(){
>   // Get .ktooltiptext sibling
>   var tooltip = this.parentNode.querySelector(".ktooltiptext");
>   
>   // Get calculated ktooltip coordinates and size
>   var ktooltip_rect = this.getBoundingClientRect();
>
>   var tipX = ktooltip_rect.width + 5; // 5px on the right of the ktooltip
>   var tipY = -40; // 40px on the top of the ktooltip
>   // Position tooltip
>   tooltip.style.top = tipY + 'px';
>   tooltip.style.left = tipX + 'px';
>
>   // Get calculated tooltip coordinates and size
>   var tooltip_rect = tooltip.getBoundingClientRect();
>   // Corrections if out of window
>   if ((tooltip_rect.x + tooltip_rect.width) > window.innerWidth) // Out on 
> the right
> tipX = -tooltip_rect.width - 5;  // Simulate a "right: tipX" position
>   if (tooltip_rect.y < 0)// Out on the top
> tipY = tipY - tooltip_rect.y;// Align on the top
>
>   // Apply corrected position
>   tooltip.style.top = tipY + 'px';
>   tooltip.style.left = tipX + 'px';
> }
>
> This is a partial solution for repositioning the tooltips to prevent 
> screen overflow (off screen issue)!
>
>
> 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/15fb086c-650b-4f3e-affd-84067b7b0632n%40googlegroups.com.

[tw5] The simplest way to include the JS code into Tiddlywiki

[Mohammad Rahmani]

What is the simplest way to have the below JS code into a Tiddlywiki
plugin! It is not a macro, nor a widget!

var ktooltips = document.querySelectorAll(".ktooltip");
ktooltips.forEach(function(ktooltip, index){// For each
ktooltip
  ktooltip.addEventListener("mouseover", position_tooltip); // On hover,
launch the function below
})

function position_tooltip(){
  // Get .ktooltiptext sibling
  var tooltip = this.parentNode.querySelector(".ktooltiptext");

  // Get calculated ktooltip coordinates and size
  var ktooltip_rect = this.getBoundingClientRect();

  var tipX = ktooltip_rect.width + 5; // 5px on the right of the ktooltip
  var tipY = -40; // 40px on the top of the ktooltip
  // Position tooltip
  tooltip.style.top = tipY + 'px';
  tooltip.style.left = tipX + 'px';

  // Get calculated tooltip coordinates and size
  var tooltip_rect = tooltip.getBoundingClientRect();
  // Corrections if out of window
  if ((tooltip_rect.x + tooltip_rect.width) > window.innerWidth) // Out on
the right
tipX = -tooltip_rect.width - 5;  // Simulate a "right: tipX" position
  if (tooltip_rect.y < 0)// Out on the top
tipY = tipY - tooltip_rect.y;// Align on the top

  // Apply corrected position
  tooltip.style.top = tipY + 'px';
  tooltip.style.left = tipX + 'px';
}

This is a partial solution for repositioning the tooltips to prevent screen
overflow (off screen issue)!


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/CAAV1gMCq94yaA0cb1oBkC-0Oi6xehw78L261%3D%2BmjqBRh7uhbvg%40mail.gmail.com.

Re: [tw5] Fetching tiddlers from one wiki to another

[Jan Johannpeter]

Hi Saq,
thank you very much for this widget! This is a great help, I have 
looked for something like this for a long time.
This is a very important puzzlepiece to use TW as an interactive 
Learning Management System.
For this usecase it is great that it has a silent mode, which makes it 
mor unobstrusive than the fetch-function of Twederation.

For the interactity of an LMS I would love three other features:

-Can it handle filters to import only certain tiddlers? So far I could 
not see how to implement them in the action-widget.
-It would be great if it could tag them imported tiddlers like "temp" 
or "imported"
-It would be very important to have an "Overwrite Filter" determining 
which tiddlers can be overwritten by the imported tiddlers. (For 
example al those whose modifier is not the current user).


Best wishes  and nany thanks for this great improvement!
Jan





Am So, 4. Apr, 2021 um 10:49 VORMITTAGS schrieb Saq Imtiaz 
:

Hi Jeremy,

A little background: I have a couple of ideas in mind for projects to 
do with education with some of the organizations I work with, for 
which I am considering TiddlyWiki. One of them would be very similar 
to the syncing educator and student notebooks project that was based 
on TiddlyWiki classic over 10 years ago. The other involves providing 
a sandbox for exploration and developing skills to do with using and 
potentially creating/customizing digital tools to aid one's own 
learning. While TiddlyWiki sounds like a good fit, it will also be 
essential that it is hard for the students to break the tool itself.


Both projects, if they proceed, will entail quite a bit of custom 
coding to get the user experience just right, so as a first step I 
wanted to understand what was possible today in terms of browser 
restrictions and loading content dynamically in TW5. As mentioned in 
my original post, I realize the use case for this particular 
prototype is very narrow. However I find that sharing ideas and 
prototypes is rarely a bad idea as it can often inspire other ideas 
in the community, so I try my best to do so whenever possible.


Those restrictions still exist. For example, the XMLHttpRequest 
approach described here generally won’t work from a file: URI, 
which was a major design goal for the plugin library and Twederation.


That's interesting as I've found it to work without problems to fetch 
content into a local file wiki as long as the remote content is 
served with the correct CORS headers (and the request is made without 
the X-Requested-With header). Or do you mean when the remote content 
is also accessed via a file: URI ? I have not tested that scenario.


Hosting all the wikis with CORS support is an easy requirement to 
satisfy for the projects I have in mind.


It’s definitely time we explored dynamic content loading via 
XMLHttpRequest in more detail. The constraints get less onerous as 
we gain better HTTP/HTTPS solutions.


Agreed. I quite miss the possibilities offered by the quite rich 
ecosystem of adaptors that we had in TiddlyWiki Classic and even the 
sync mechanism, despite all the clunkiness inherent in the design and 
the later difficulties imposed by greater browser restrictions.


Regards,
Saq
 --
 You received this message because you are subscribed to the Google 
Groups "TiddlyWiki" group.
 To unsubscribe from this group and stop receiving emails from it, 
send an email to tiddlywiki+unsubscr...@googlegroups.com 
.
 To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7ea4cca2-c07a-486d-a60c-b59c9838c0bdn%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/UMOPRQ.4ES1X6YF4FAM%40gmail.com.

[tw5] Re: A tour through my Zettelkasten

[stan...@gmail.com]

+1 to Walt's post.  Thanks, Soren, for the great contribution to the 
community. This really helped me understand how to implement a Zettelkasten 
in TW.  I, too, have been wondering how to filter out your content and keep 
the skeleton, if that is at all possible. Thanks again.

Stan

On Saturday, April 17, 2021 at 7:17:38 AM UTC-4 ludwa6 wrote:

> Wow.  For all the buzz around the Digital Gardening/ Mind-Mapping space, 
> this is so far and away beyond anything i have seen... An amazing gift to 
> the commons, Soren; i just gotta give your system a try.
>
> To that end, i have just one question: what would be the easiest way to 
> filter out & delete all your content from the downloaded .html file, 
> without losing any of the many useful functions that you have outlined & 
> demoed so well?
>
>
>
> /walt
>
> On Thursday, April 15, 2021 at 4:15:49 AM UTC+1 Soren Bjornstad wrote:
>
>> For those who have been interested in my public Zettelkasten wiki 
>>  in the past (or might be 
>> interested in it now), I've just put up an extensive discussion of 
>> Zettelkasten and how I've implemented it in my TiddlyWiki on my YouTube 
>> channel:
>>
>> https://www.youtube.com/watch?v=GjpjE5pMZMI
>>
>> Here are the segments if you're curious:
>>
>> *About Zettelkasten:*
>> 0:00 Welcome and introduction
>> 1:00 Public and private versions of my Zettelkasten
>> 2:08 What is a Zettelkasten?
>> 4:16 What idea tiddlers look like and how we navigate through them
>> 6:28 Implementation evolves with the content
>>
>> *Organizing my Zettelkasten and relating ideas:*
>> 7:06 Why I use CamelCase names
>> 8:12 Expressing relationships by linking
>> 9:40 Expressing memberships by tagging
>> 10:07 Tags serve in many roles – topics/indexes, publicity level, lists, 
>> types, pseudo-types, and maintenance
>> 15:42 Index tiddlers provide overviews of a topic area
>> 17:33 Transclusion can combine with the ‘description’ field to create 
>> overviews
>> 18:42 Why I don’t use tags for all overviews
>> 19:28 Stretchtext creates interactive, expandable overviews
>> 20:42 Subtiddlers aggregate tightly coupled content
>> 23:58 Bibliographies aggregate related sources
>> 25:38 The Write tab highlights fruitful areas for further work (stubs, 
>> missing, needing attention, needing excision, to-dos, open questions)
>> 29:58 The Reference Explorer shows related tiddlers (backlinks and 
>> forward links) in a concise table
>> 34:48 Graph theory and Zettelkästen; link graph
>> 37:11 Types of tiddlers; why I include non-idea tiddlers, unlike classic 
>> Zettelkasten
>>
>> *Plugins and custom TiddlyWiki logic:*
>> 41:04 Interesting TiddlyWiki plugins I use
>> 47:17 Publishing only part of a TiddlyWiki (public/private switch): 
>> Marking tiddlers
>> 49:05 Public/private: The PrivateChunk
>> 51:28 Public/private: The build process (shell script)
>> 54:18 Custom copy-title and permalink buttons
>> 55:38 GIS (mapping) support for places
>> 57:55 The missing-tiddler helper
>> 58:36 Quick reading-list import by pasting a URL
>> 59:30 Reading inbox
>> 1:00:15 Simple Analytics and raw markup snippets
>> 1:01:05 Sorting tags by color and putting them in columns
>>
>> *Philosophy:*
>> 1:03:01 Just get started and then continuously improve
>> 1:05:20 The Three-Links Heuristic for determining whether ideas are 
>> effectively linked together
>> 1:07:02 A Zettelkasten never walks backwards: consistency doesn’t matter 
>> that much
>> 1:08:56 Why I default to open and publish my Zettelkasten
>> 1:11:25 Polyspecialize your Zettelkasten, include variety
>> 1:13:34 Prioritize; you won’t have time to write about everything
>> 1:14:55 Using the flexibility and user-programmability of TiddlyWiki to 
>> your advantage
>>
>>

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

[tw5] Re: A tour through my Zettelkasten

[ludwa6]

Wow.  For all the buzz around the Digital Gardening/ Mind-Mapping space, 
this is so far and away beyond anything i have seen... An amazing gift to 
the commons, Soren; i just gotta give your system a try.

To that end, i have just one question: what would be the easiest way to 
filter out & delete all your content from the downloaded .html file, 
without losing any of the many useful functions that you have outlined & 
demoed so well?



/walt

On Thursday, April 15, 2021 at 4:15:49 AM UTC+1 Soren Bjornstad wrote:

> For those who have been interested in my public Zettelkasten wiki 
>  in the past (or might be 
> interested in it now), I've just put up an extensive discussion of 
> Zettelkasten and how I've implemented it in my TiddlyWiki on my YouTube 
> channel:
>
> https://www.youtube.com/watch?v=GjpjE5pMZMI
>
> Here are the segments if you're curious:
>
> *About Zettelkasten:*
> 0:00 Welcome and introduction
> 1:00 Public and private versions of my Zettelkasten
> 2:08 What is a Zettelkasten?
> 4:16 What idea tiddlers look like and how we navigate through them
> 6:28 Implementation evolves with the content
>
> *Organizing my Zettelkasten and relating ideas:*
> 7:06 Why I use CamelCase names
> 8:12 Expressing relationships by linking
> 9:40 Expressing memberships by tagging
> 10:07 Tags serve in many roles – topics/indexes, publicity level, lists, 
> types, pseudo-types, and maintenance
> 15:42 Index tiddlers provide overviews of a topic area
> 17:33 Transclusion can combine with the ‘description’ field to create 
> overviews
> 18:42 Why I don’t use tags for all overviews
> 19:28 Stretchtext creates interactive, expandable overviews
> 20:42 Subtiddlers aggregate tightly coupled content
> 23:58 Bibliographies aggregate related sources
> 25:38 The Write tab highlights fruitful areas for further work (stubs, 
> missing, needing attention, needing excision, to-dos, open questions)
> 29:58 The Reference Explorer shows related tiddlers (backlinks and forward 
> links) in a concise table
> 34:48 Graph theory and Zettelkästen; link graph
> 37:11 Types of tiddlers; why I include non-idea tiddlers, unlike classic 
> Zettelkasten
>
> *Plugins and custom TiddlyWiki logic:*
> 41:04 Interesting TiddlyWiki plugins I use
> 47:17 Publishing only part of a TiddlyWiki (public/private switch): 
> Marking tiddlers
> 49:05 Public/private: The PrivateChunk
> 51:28 Public/private: The build process (shell script)
> 54:18 Custom copy-title and permalink buttons
> 55:38 GIS (mapping) support for places
> 57:55 The missing-tiddler helper
> 58:36 Quick reading-list import by pasting a URL
> 59:30 Reading inbox
> 1:00:15 Simple Analytics and raw markup snippets
> 1:01:05 Sorting tags by color and putting them in columns
>
> *Philosophy:*
> 1:03:01 Just get started and then continuously improve
> 1:05:20 The Three-Links Heuristic for determining whether ideas are 
> effectively linked together
> 1:07:02 A Zettelkasten never walks backwards: consistency doesn’t matter 
> that much
> 1:08:56 Why I default to open and publish my Zettelkasten
> 1:11:25 Polyspecialize your Zettelkasten, include variety
> 1:13:34 Prioritize; you won’t have time to write about everything
> 1:14:55 Using the flexibility and user-programmability of TiddlyWiki to 
> your advantage
>
>

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

[tw5] Mentat

[Ray Vermey]

Hi,

i installed the great looking all the Mentat plugins and it looks really 
nice.
I drag and resize, works nice!
But when i create a new Tiddler it is shown behind the tiddlers on screen.
Is that on purpose?
I must close all the other tiddlers to reach the new one.
Am i using the wrong workflow here??

Also the red Engine button is hidden under the Google Drive button...
That is a bit annoying... is a placement option for 1 of the 2 possible?

Also when i edit a tiddler the top of it is underneath the Topbar of Mentat.
That makes it a bit difficult to close..

I feel i use it the wrong way, can someone tell me how i can make the best 
use
of it?

Thanks

Ray

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

Re: [tw5] Re: [Announcement] "TW Icons" - A large collection of icons for TiddlyWiki

[TiddlyTweeter]

Ciao morosanuae,

 moros...@gmail.com wrote:

> @TT Hello!
>
> 1. I will add a loading screen (in the next version), but this will not 
> improve the loading speed ;). 
>

Right. Good! 
The performance, once loaded, is stellar so no issue. 
On phone too. It is only load-time that is a VISUAL issue ... just being 
aware it IS loading.

Best wishes
TT

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

[tw5] Re: EditTextWidget: ouch when tiddler=currentTiddler and using index

[PMario]

Hi,
Yea, There are some widgets, where the default values used can cause data 
loss. Especially if you are developing new stuff and have variables, that 
are not initialized in the right way. 

The problem is, that we can't change this behavior anymore, because of 
backwards compatibility reasons.  

The only way would be to create new widgets, that do the same thing, but 
are safe, if you don't specify parameters.

-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/d1f82d21-318a-4465-ba2b-3d5014898234n%40googlegroups.com.

[tw5] Re: More Free Icons/images for Windows 10 Users that work well with TiddlyWiki

[TiddlyTweeter]

TW Tones wrote:

> The pricing in US Dollars can be found here https://icons8.com/pricing 
> along with this and the icon limitations even with a paid plan has turned 
> me off this option. 
>

Right. That was my point, that that link is a DEAD end. In multiple ways.

Users can *already* easily use 38,000+ TW icons in TW icon format via 
https://morosanuae.github.io/tw-icons/  
. 
It is brilliant & comprehensive.

There is NO need to re-invent the wheel when it already exists and works 
well!  :-).

TT


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

[tw5] Re: List tiddlers that have a field value with certain suffix

[Mat]

Saq... thank you!

https://www.youtube.com/watch?v=218iXiKhKlg

<:-)
On Saturday, April 17, 2021 at 10:35:04 AM UTC+2 Saq Imtiaz wrote:

> Try this:
>
> {{{ [has[path]] :filter[get[path]suffix<__chunk__>] }}}
>
> On Saturday, April 17, 2021 at 10:26:04 AM UTC+2 Mat wrote:
>
>> I have a variable <<__chunk__>>  with e.g the value bar/ and need to 
>> find which tiddlers have a path field with where this value is a *suffix*. 
>> For example, I need to find the two tiddlers that have these respective 
>> path fields:
>>
>> path: foo/bar/
>> path: frotz/bar/
>>
>> It seems I must[1] use a regexp but I can't get this to work:
>>
>> <$vars chunk="bar/">
>> <$vars reg="[$]" >
>> <$list filter="""[all[tiddlers]regexp:path]""">
>> <$link/> {{!!path}}
>> 
>> 
>> 
>>
>> (In actual use, the chunk variable is remote so it reads 
>> reg="[<__chunk__>$]" )
>>
>> Is the regexp wrong? What to do? Better ideas?
>>
>> Thank you!
>>
>> <:-)
>>
>> *Note*
>> [1] Using the filter operator  
>> for 
>> a subfilter does not work because the filter op has a bug 
>> , i.e this does 
>> not work:
>>
>> <$vars subfilter="[get[path]suffix<__chunk__>]">
>> {{{ [all[tiddlers]has[path]filter] }}}
>> 
>>
>

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

[tw5] Re: List tiddlers that have a field value with certain suffix

[Saq Imtiaz]

Try this:

{{{ [has[path]] :filter[get[path]suffix<__chunk__>] }}}

On Saturday, April 17, 2021 at 10:26:04 AM UTC+2 Mat wrote:

> I have a variable <<__chunk__>>  with e.g the value bar/ and need to find 
> which tiddlers have a path field with where this value is a *suffix*. For 
> example, I need to find the two tiddlers that have these respective path 
> fields:
>
> path: foo/bar/
> path: frotz/bar/
>
> It seems I must[1] use a regexp but I can't get this to work:
>
> <$vars chunk="bar/">
> <$vars reg="[$]" >
> <$list filter="""[all[tiddlers]regexp:path]""">
> <$link/> {{!!path}}
> 
> 
> 
>
> (In actual use, the chunk variable is remote so it reads 
> reg="[<__chunk__>$]" )
>
> Is the regexp wrong? What to do? Better ideas?
>
> Thank you!
>
> <:-)
>
> *Note*
> [1] Using the filter operator  for 
> a subfilter does not work because the filter op has a bug 
> , i.e this does not 
> work:
>
> <$vars subfilter="[get[path]suffix<__chunk__>]">
> {{{ [all[tiddlers]has[path]filter] }}}
> 
>

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

[tw5] List tiddlers that have a field value with certain suffix

[Mat]

I have a variable <<__chunk__>>  with e.g the value bar/ and need to find 
which tiddlers have a path field with where this value is a *suffix*. For 
example, I need to find the two tiddlers that have these respective path 
fields:

path: foo/bar/
path: frotz/bar/

It seems I must[1] use a regexp but I can't get this to work:

<$vars chunk="bar/">
<$vars reg="[$]" >
<$list filter="""[all[tiddlers]regexp:path]""">
<$link/> {{!!path}}




(In actual use, the chunk variable is remote so it reads 
reg="[<__chunk__>$]" )

Is the regexp wrong? What to do? Better ideas?

Thank you!

<:-)

*Note*
[1] Using the filter operator  for 
a subfilter does not work because the filter op has a bug 
, i.e this does not 
work:

<$vars subfilter="[get[path]suffix<__chunk__>]">
{{{ [all[tiddlers]has[path]filter] }}}


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

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

[Saq Imtiaz]

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

Saq

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

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

[Saq Imtiaz]

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

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

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

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