Re: [tw5] Re: Note Taking in 2021 (article & reflection)

[CJ Veniot]

Ugh et oops..  e-Learner.  I went a little off-track there thinking
in-person classroom/auditorium/hall.

On Sat, Jun 19, 2021 at 1:53 PM Charlie Veniot  wrote:

> Now we're talking.  That is an awesome use case.
>
> Are you thinking of doing that on a smartphone?  If so: yuck.  A small
> screen would require flipping back and forth between outliner + your
> thoughts + "presentation" notes.  Could be done (sliding panels), but I'm
> no fan of not having everything in front of me.
>
> I'd want a device with a screen big enough to have all three panels
> visible.  A decent-sized tablet?
>
> So a tiddler for a specific class/seminar/presentation would look something
> like this
> 
> ?
>
>
>
> On Saturday, June 19, 2021 at 12:54:59 PM UTC-3 ludwa6 wrote:
>
>> OK @Charlie: For a scenario of agile NoteTaking in an outliner that might
>> hold a “deep issue” or few for TW to solve, let us consider the case of an
>> isolated eLearner taking notes in one window while video lecture is playing
>> in another.
>>
>>  Teacher is talking, and I’m here banging out notes as fast as i can type
>> a key phrase and hit return… And before you know it, I’ve got a screen full
>> of lines that reflect the lecturer’s train of thought, insofar as i have
>> followed it. Thing is, I’ve been having my own thoughts about all this
>> as we go along -some of which i may want to nest beneath a pithy quote from
>> Teacher, while others may be my own original train of thought that I want
>> to organize in a separate group- and this i can easily do, without needing
>> to pause the video, because each line is a discrete object that i can move
>> up or down, indent or outdent, fold or unfold, whether by a single
>> keystroke or mouse click or gesture on glass.
>>
>> Now: can you show me a one window interface in TiddlyWiki where i can
>> work like that?
>>
>> /walt
>>
>> On Saturday, June 19, 2021 at 4:07:37 PM UTC+1 cj.v...@gmail.com wrote:
>>
>>> I am really enjoying this thread of discussion.
>>>
>>> Fully recognizing (almost giddy about it) that any one solution can be
>>> the best for one group of doers'n thinkers, it can come up short for other
>>> groups of doers'n thinkers (cognitive differences/preferences are one of
>>> the beautiful thing that make our species so danged interesting)...
>>>
>>> I can't help myself, always wondering: how would I do this/that with
>>> TiddlyWiki.
>>>
>>> There are a lot of angles to cover re taking vs making notes.
>>>
>>> Maybe we can go over, one-by-one, your list of deep issues that keep TW
>>> from being Agile.  (Yeah, I"m kind of an over-eager beaver over here, ready
>>> to jump at each "feature" and instinctively react with a "why couldn't
>>> TiddlyWiki can do that?  All rainbows and blue skies and butterflies me...")
>>>
>>>
>>>
>>> On Saturday, June 19, 2021 at 4:30:12 AM UTC-3 ludwa6 wrote:
>>>
 I see what you can do about mode-switching , Charlie, and agree: that’s
 a good hi-level UI affordance..

 Still, I think that there be pretty deep issues that keep TW from being
 a very agile NoteTaking tool.

 The best solution to the portability problem that I have found involves
 using Quine2 app on my iPhone, with sync to my desktop TW instance via
 Apple iCloud, but that is kind of a hack, overly dependent on Apple, I
 would say.

 Still more challenging to my mind is the diff between an outlining
 editor and the text editing window in a tiddler;  that is fundamentally
 constrained by web standards -is it not?

 /walt


 On Saturday, June 19, 2021 at 5:21:42 AM UTC+1 cj.v...@gmail.com wrote:

> Instinctively, I'm thinking it should be possible to simultaneously
> have both "modes" (taking vs making) at the same time available, just
> because TiddlyWiki is so flexible.
>
> If not simultaneous modes, then it should be possible to switch
> between the two modes without batting an eyelash, kind of like how my more
> recent TiddlyWiki instances can switch between "reader" and "author" modes
> (triggered by hide/show of sidebar).  Or how my Favourite Stuff and
> Projects
> 
> TiddlyWiki can switch between contexts.
>
> That said, I must chew on it a bit, and read all previously mentioned
> articles a few times over.
>
>
> On Friday, June 18, 2021 at 6:29:42 PM UTC-3 ludwa6 wrote:
>
>> Thanks for engaging, Saq: responses inline below.
>>
>> On Friday, June 18, 2021 at 6:53:51 PM UTC+1 saq.i...@gmail.com
>> wrote:
>>
>>> Crude, but effective enough, albeit with some editing overhead in TW
 that it would be nice to eliminate.  Am starting to explore the
 possibilities of Logseq as a potential Dynalist replacement; it does
 outlining in 

[tw5] Re: Note Taking in 2021 (article & reflection)

[Charlie Veniot]

Now we're talking.  That is an awesome use case.

Are you thinking of doing that on a smartphone?  If so: yuck.  A small 
screen would require flipping back and forth between outliner + your 
thoughts + "presentation" notes.  Could be done (sliding panels), but I'm 
no fan of not having everything in front of me.

I'd want a device with a screen big enough to have all three panels 
visible.  A decent-sized tablet?

So a tiddler for a specific class/seminar/presentation would look something 
like this 

?



On Saturday, June 19, 2021 at 12:54:59 PM UTC-3 ludwa6 wrote:

> OK @Charlie: For a scenario of agile NoteTaking in an outliner that might 
> hold a “deep issue” or few for TW to solve, let us consider the case of an 
> isolated eLearner taking notes in one window while video lecture is playing 
> in another. 
>
>  Teacher is talking, and I’m here banging out notes as fast as i can type 
> a key phrase and hit return… And before you know it, I’ve got a screen full 
> of lines that reflect the lecturer’s train of thought, insofar as i have 
> followed it. Thing is, I’ve been having my own thoughts about all this as 
> we go along -some of which i may want to nest beneath a pithy quote from 
> Teacher, while others may be my own original train of thought that I want 
> to organize in a separate group- and this i can easily do, without needing 
> to pause the video, because each line is a discrete object that i can move 
> up or down, indent or outdent, fold or unfold, whether by a single 
> keystroke or mouse click or gesture on glass.
>
> Now: can you show me a one window interface in TiddlyWiki where i can work 
> like that?
>
> /walt 
>
> On Saturday, June 19, 2021 at 4:07:37 PM UTC+1 cj.v...@gmail.com wrote:
>
>> I am really enjoying this thread of discussion.
>>
>> Fully recognizing (almost giddy about it) that any one solution can be 
>> the best for one group of doers'n thinkers, it can come up short for other 
>> groups of doers'n thinkers (cognitive differences/preferences are one of 
>> the beautiful thing that make our species so danged interesting)...
>>
>> I can't help myself, always wondering: how would I do this/that with 
>> TiddlyWiki.
>>
>> There are a lot of angles to cover re taking vs making notes.
>>
>> Maybe we can go over, one-by-one, your list of deep issues that keep TW 
>> from being Agile.  (Yeah, I"m kind of an over-eager beaver over here, ready 
>> to jump at each "feature" and instinctively react with a "why couldn't 
>> TiddlyWiki can do that?  All rainbows and blue skies and butterflies me...")
>>
>>
>>
>> On Saturday, June 19, 2021 at 4:30:12 AM UTC-3 ludwa6 wrote:
>>
>>> I see what you can do about mode-switching , Charlie, and agree: that’s 
>>> a good hi-level UI affordance..
>>>
>>> Still, I think that there be pretty deep issues that keep TW from being 
>>> a very agile NoteTaking tool. 
>>>
>>> The best solution to the portability problem that I have found involves 
>>> using Quine2 app on my iPhone, with sync to my desktop TW instance via 
>>> Apple iCloud, but that is kind of a hack, overly dependent on Apple, I 
>>> would say. 
>>>
>>> Still more challenging to my mind is the diff between an outlining 
>>> editor and the text editing window in a tiddler;  that is fundamentally 
>>> constrained by web standards -is it not?
>>>
>>> /walt 
>>>
>>>
>>> On Saturday, June 19, 2021 at 5:21:42 AM UTC+1 cj.v...@gmail.com wrote:
>>>
 Instinctively, I'm thinking it should be possible to simultaneously 
 have both "modes" (taking vs making) at the same time available, just 
 because TiddlyWiki is so flexible.

 If not simultaneous modes, then it should be possible to switch between 
 the two modes without batting an eyelash, kind of like how my more recent 
 TiddlyWiki instances can switch between "reader" and "author" modes 
 (triggered by hide/show of sidebar).  Or how my Favourite Stuff and 
 Projects 
  
 TiddlyWiki can switch between contexts.

 That said, I must chew on it a bit, and read all previously mentioned 
 articles a few times over.


 On Friday, June 18, 2021 at 6:29:42 PM UTC-3 ludwa6 wrote:

> Thanks for engaging, Saq: responses inline below.
>
> On Friday, June 18, 2021 at 6:53:51 PM UTC+1 saq.i...@gmail.com wrote:
>
>> Crude, but effective enough, albeit with some editing overhead in TW 
>>> that it would be nice to eliminate.  Am starting to explore the 
>>> possibilities of Logseq as a potential Dynalist replacement; it does 
>>> outlining in much the same way, but has some interesting export 
>>> functions, 
>>> including JSON and Roam JSON.  If there were a way in TW to import such 
>>> exports and convert them into proper tiddlers... That would be amazing!
>>>

[tw5] Re: Awesome Tiddlywiki Example

[Ste]

Looks very slick. I like the references fold down and tabs at the bottom of 
the tiddlers. 

On Saturday, 19 June 2021 at 11:03:42 UTC+1 TiddlyTweeter wrote:

> Right! Awesome.
>
> You might want to note that it extensively uses both Theme and Plugins by 
> Thomas Elmiger to enable what the user needed!
>
> Best wishes
> TT
>
> On Saturday, 19 June 2021 at 07:02:23 UTC+2 Mohammad wrote:
>
>> Tweeted by @OffrayLC on 
>> https://twitter.com/offrayLC/status/1405947061787312130?s=20
>> a #Starforged character sheet done in @TiddlyWiki.
>>
>> See it here: https://mutabit.com/repos.fossil/502Lab/uv/wiki/502Lab.html#
>>
>>
>> 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/0dadf858-7805-4c45-aa44-63f6cf8afc9bn%40googlegroups.com.

[tw5] Re: Note Taking in 2021 (article & reflection)

[ludwa6]

OK @Charlie: For a scenario of agile NoteTaking in an outliner that might 
hold a “deep issue” or few for TW to solve, let us consider the case of an 
isolated eLearner taking notes in one window while video lecture is playing 
in another. 

 Teacher is talking, and I’m here banging out notes as fast as i can type a 
key phrase and hit return… And before you know it, I’ve got a screen full 
of lines that reflect the lecturer’s train of thought, insofar as i have 
followed it. Thing is, I’ve been having my own thoughts about all this as 
we go along -some of which i may want to nest beneath a pithy quote from 
Teacher, while others may be my own original train of thought that I want 
to organize in a separate group- and this i can easily do, without needing 
to pause the video, because each line is a discrete object that i can move 
up or down, indent or outdent, fold or unfold, whether by a single 
keystroke or mouse click or gesture on glass.

Now: can you show me a one window interface in TiddlyWiki where i can work 
like that?

/walt 

On Saturday, June 19, 2021 at 4:07:37 PM UTC+1 cj.v...@gmail.com wrote:

> I am really enjoying this thread of discussion.
>
> Fully recognizing (almost giddy about it) that any one solution can be the 
> best for one group of doers'n thinkers, it can come up short for other 
> groups of doers'n thinkers (cognitive differences/preferences are one of 
> the beautiful thing that make our species so danged interesting)...
>
> I can't help myself, always wondering: how would I do this/that with 
> TiddlyWiki.
>
> There are a lot of angles to cover re taking vs making notes.
>
> Maybe we can go over, one-by-one, your list of deep issues that keep TW 
> from being Agile.  (Yeah, I"m kind of an over-eager beaver over here, ready 
> to jump at each "feature" and instinctively react with a "why couldn't 
> TiddlyWiki can do that?  All rainbows and blue skies and butterflies me...")
>
>
>
> On Saturday, June 19, 2021 at 4:30:12 AM UTC-3 ludwa6 wrote:
>
>> I see what you can do about mode-switching , Charlie, and agree: that’s a 
>> good hi-level UI affordance..
>>
>> Still, I think that there be pretty deep issues that keep TW from being a 
>> very agile NoteTaking tool. 
>>
>> The best solution to the portability problem that I have found involves 
>> using Quine2 app on my iPhone, with sync to my desktop TW instance via 
>> Apple iCloud, but that is kind of a hack, overly dependent on Apple, I 
>> would say. 
>>
>> Still more challenging to my mind is the diff between an outlining editor 
>> and the text editing window in a tiddler;  that is fundamentally 
>> constrained by web standards -is it not?
>>
>> /walt 
>>
>>
>> On Saturday, June 19, 2021 at 5:21:42 AM UTC+1 cj.v...@gmail.com wrote:
>>
>>> Instinctively, I'm thinking it should be possible to simultaneously have 
>>> both "modes" (taking vs making) at the same time available, just because 
>>> TiddlyWiki is so flexible.
>>>
>>> If not simultaneous modes, then it should be possible to switch between 
>>> the two modes without batting an eyelash, kind of like how my more recent 
>>> TiddlyWiki instances can switch between "reader" and "author" modes 
>>> (triggered by hide/show of sidebar).  Or how my Favourite Stuff and 
>>> Projects 
>>>  
>>> TiddlyWiki can switch between contexts.
>>>
>>> That said, I must chew on it a bit, and read all previously mentioned 
>>> articles a few times over.
>>>
>>>
>>> On Friday, June 18, 2021 at 6:29:42 PM UTC-3 ludwa6 wrote:
>>>
 Thanks for engaging, Saq: responses inline below.

 On Friday, June 18, 2021 at 6:53:51 PM UTC+1 saq.i...@gmail.com wrote:

> Crude, but effective enough, albeit with some editing overhead in TW 
>> that it would be nice to eliminate.  Am starting to explore the 
>> possibilities of Logseq as a potential Dynalist replacement; it does 
>> outlining in much the same way, but has some interesting export 
>> functions, 
>> including JSON and Roam JSON.  If there were a way in TW to import such 
>> exports and convert them into proper tiddlers... That would be amazing!
>>
>
> It is definitely doable. How useful such an import is will depend on 
> what kind of features/markup you are using in those systems and how well 
> they would translate to wikitext. Converting pure text though is very 
> straight forward.
>

 It is mostly plain text, but for Markdown formatting ( which I could 
 live without) and links- formatted like [Google](https:// Google.com) 
 -which would need conversion to [[wikilinks form|https://google.com]].
  

>  
>
>> If anyone else has got some other solution for agile NoteTaking that 
>> integrates nicely with TiddlyWiki for NoteMaking, i'd be very interested 
>> to 
>> hear about it.
>>
>
> To this end, it would be interesting to understand 

[tw5] Re: Is it possible to add "Home" icon beside hamburger icon on menubar plugin

[Euthymious]

Just tag the tiddler $:/core/ui/Buttons/home with $:/tags/MenuBar

суббота, 19 июня 2021 г. в 16:56:44 UTC+3, lishu...@gmail.com: 

> I find that it will be much convenient if there is a home button beside 
> (on the right of) the hamburger button when I use mobile phone to browse 
> tiddlywiki.
>
> Sorry that I am really not good at programming. Thanks guys.
>

-- 
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/1a3a37c8-ad68-42bd-bdca-152bec8104e9n%40googlegroups.com.

[tw5] Re: Note Taking in 2021 (article & reflection)

[Charlie Veniot]

I am really enjoying this thread of discussion.

Fully recognizing (almost giddy about it) that any one solution can be the 
best for one group of doers'n thinkers, it can come up short for other 
groups of doers'n thinkers (cognitive differences/preferences are one of 
the beautiful thing that make our species so danged interesting)...

I can't help myself, always wondering: how would I do this/that with 
TiddlyWiki.

There are a lot of angles to cover re taking vs making notes.

Maybe we can go over, one-by-one, your list of deep issues that keep TW 
from being Agile.  (Yeah, I"m kind of an over-eager beaver over here, ready 
to jump at each "feature" and instinctively react with a "why couldn't 
TiddlyWiki can do that?  All rainbows and blue skies and butterflies me...")



On Saturday, June 19, 2021 at 4:30:12 AM UTC-3 ludwa6 wrote:

> I see what you can do about mode-switching , Charlie, and agree: that’s a 
> good hi-level UI affordance..
>
> Still, I think that there be pretty deep issues that keep TW from being a 
> very agile NoteTaking tool. 
>
> The best solution to the portability problem that I have found involves 
> using Quine2 app on my iPhone, with sync to my desktop TW instance via 
> Apple iCloud, but that is kind of a hack, overly dependent on Apple, I 
> would say. 
>
> Still more challenging to my mind is the diff between an outlining editor 
> and the text editing window in a tiddler;  that is fundamentally 
> constrained by web standards -is it not?
>
> /walt 
>
>
> On Saturday, June 19, 2021 at 5:21:42 AM UTC+1 cj.v...@gmail.com wrote:
>
>> Instinctively, I'm thinking it should be possible to simultaneously have 
>> both "modes" (taking vs making) at the same time available, just because 
>> TiddlyWiki is so flexible.
>>
>> If not simultaneous modes, then it should be possible to switch between 
>> the two modes without batting an eyelash, kind of like how my more recent 
>> TiddlyWiki instances can switch between "reader" and "author" modes 
>> (triggered by hide/show of sidebar).  Or how my Favourite Stuff and 
>> Projects 
>>  
>> TiddlyWiki can switch between contexts.
>>
>> That said, I must chew on it a bit, and read all previously mentioned 
>> articles a few times over.
>>
>>
>> On Friday, June 18, 2021 at 6:29:42 PM UTC-3 ludwa6 wrote:
>>
>>> Thanks for engaging, Saq: responses inline below.
>>>
>>> On Friday, June 18, 2021 at 6:53:51 PM UTC+1 saq.i...@gmail.com wrote:
>>>
 Crude, but effective enough, albeit with some editing overhead in TW 
> that it would be nice to eliminate.  Am starting to explore the 
> possibilities of Logseq as a potential Dynalist replacement; it does 
> outlining in much the same way, but has some interesting export 
> functions, 
> including JSON and Roam JSON.  If there were a way in TW to import such 
> exports and convert them into proper tiddlers... That would be amazing!
>

 It is definitely doable. How useful such an import is will depend on 
 what kind of features/markup you are using in those systems and how well 
 they would translate to wikitext. Converting pure text though is very 
 straight forward.

>>>
>>> It is mostly plain text, but for Markdown formatting ( which I could 
>>> live without) and links- formatted like [Google](https:// Google.com) 
>>> -which would need conversion to [[wikilinks form|https://google.com]].
>>>  
>>>
  

> If anyone else has got some other solution for agile NoteTaking that 
> integrates nicely with TiddlyWiki for NoteMaking, i'd be very interested 
> to 
> hear about it.
>

 To this end, it would be interesting to understand what features or 
 workflow in Dynalist (or Logseq) make it better for note taking (vs 
 TiddlyWiki) in your experience. 

>>>
>>> Essentially it’s about speed and portability, traversing/ elaborating/ 
>>> reorganizing outlines as fast as fingers can type, and context switching 
>>> from local desktop to mobile phone in the field ( i.e. cloud) many times 
>>> per day without a hitch.  If this is possible in TW, I’d love to know how… 
>>> But i think it’s a case of architectures that are optimized for different 
>>> things, don’t you think?
>>>
>>> /walt 
>>>
>>

-- 
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/736e1a82-f580-4a6a-9cf4-51a95027971fn%40googlegroups.com.

[tw5] Re: Note Taking in 2021 (article & reflection)

[ludwa6]

Agree, @Saq: context switching and mobile (+desktop) usage is the toughest 
nut to crack. It’s the classic problem of concurrent databases: in case of 
edit conflict, which version wins?

Best solution to this problem i know about is GitHub; indeed it’s the ease 
with which Logseq can sync from browser LocalStorage to GitHub that has me 
considering switch from Dynalist to Logseq. 

If we only had a good way to bridge the gap between .md file format ( 
default format of Logseq files at GitHub) and .tid format ( the way content 
of my TW instance at GitHub is stored), then we could have the first solid 
bridge between worlds of outlining and wiki-weaving that the world has ever 
seen, AFAICT. 

What do you think?

/walt 

On Saturday, June 19, 2021 at 9:06:31 AM UTC+1 saq.i...@gmail.com wrote:

> Hi Walt,
>
> It is mostly plain text, but for Markdown formatting ( which I could live 
>> without) and links- formatted like [Google](https:// Google.com) -which 
>> would need conversion to [[wikilinks form|https://google.com]].
>>
>
> Right so importing something like this is definitely doable. You could 
> then either use the markdown plugin and just use these tiddlers as 
> markdown, or try to convert to TW markup. Where things get problematic is 
> if your content is using features or syntax specific to them. A markdown to 
> TW converter currently does not exist but should not be that much work. 
> I've dabbled in both areas previously, so time permitting might be able to 
> help out if you go down this road.
>  
>
>> To this end, it would be interesting to understand what features or 
>>> workflow in Dynalist (or Logseq) make it better for note taking (vs 
>>> TiddlyWiki) in your experience. 
>>>
>>
>> Essentially it’s about speed and portability, traversing/ elaborating/ 
>> reorganizing outlines as fast as fingers can type, and context switching 
>> from local desktop to mobile phone in the field ( i.e. cloud) many times 
>> per day without a hitch.  If this is possible in TW, I’d love to know how… 
>> But i think it’s a case of architectures that are optimized for different 
>> things, don’t you think?
>>
>
> It actually isn't my intention to push TiddlyWiki here. I find it 
> interesting from a UX perspective when someone has a strong preference for 
> one tool over another. I always feel its best to choose the tool best 
> suited for a particular task. Also, tools should always complement one's 
> natural way of thinking and working rather than the other way. I often find 
> that conversations around note taking don't take into account individual 
> cognitive differences.
>
> Context switching and mobile usage is indeed in my opinion something TW 
> doesn't have a good workflow for. The single file model doesn't help either 
> when it comes to concerns about overwriting one version with one with older 
> content. For the use case you describe I would consider this to be the 
> biggest barrier. Setting up something like TiddlyWiki on node.js on Azure 
> would help, especially with the upcoming server sent events feature in 
> 5.2.0. However, that only takes care of the syncing and the UI issues will 
> remain.
>
> > Still more challenging to my mind is the diff between an outlining 
> editor and the text editing window in a tiddler;  that is fundamentally 
> constrained by web standards -is it not?
>
> Not really. After all dynalist also is implemented as a web app. Streams 
> goes some ways towards creating a similar workflow in TiddlyWiki even 
> though it was never intended as an outliner. I think a key difference is 
> that in dynalist you feel like you are editing a document, versus in TW or 
> Streams you have an edit window for one portion of the document. Part of 
> the reason for that is how rich TW markup (think widgets and transclusions) 
> can be and how different rendered text can be from the markup. This drives 
> the need for separation between viewing and editing for all but the most 
> limited use cases. However, for a keyboard driven workflow the difference 
> in practice in Streams is not that significant in my experience.
>
> 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/6ca4a48f-2c0e-4dc0-a417-0c5b62491ed0n%40googlegroups.com.

[tw5] Re: Note Taking in 2021 (article & reflection)

[ludwa6]

Amen, @TT: machine models are all too simplistic, AFAICT, forcing us to 
choose between either hierarchical (I.e. outlining) or network (I.e. 
wiki-weaving) mode, while reality calls for sometimes one modality and 
sometimes the other, depending on the context. 

A corresponding dichotomy that has gained currency among cognitive 
theorists wants us to decide: are you an Architect or a Gardener? I for one 
am both, in fact - and i think I’m not the only one!

/walt

On Saturday, June 19, 2021 at 11:10:55 AM UTC+1 TiddlyTweeter wrote:

> Ciao ludwa6
>
> Slightly in a different direction, but strongly related, is fact that 
> computer science is UNDER appreciative of cognitive variations.
>
> Meaning and pattern finding is an infinite human activity that existed 
> long before computers or modern ideas of what is "kosher".
>
> It is certainly true that some kind of typology of different strategies 
> in  HOW ONE LEARNS & RECORDS is useful.
>
> But, to be honest, our current usual models on the net are somewhat crude 
> to what human beings actually do, which is vast, in many directions.
>
> Just thoughts :-)
> TT 
>
> On Friday, 18 June 2021 at 18:36:29 UTC+2 ludwa6 wrote:
>
>> Came across this article today 
>>  via HackerNews 
>> (where it has sparked quite a lively comment thread 
>> ), which brought me to 
>> realise something about an inner tension i have been struggling for too 
>> long to reconcile: it's about the difference between NoteTAKING vs 
>> NoteMAKING (or DigitalGardening or MindMapping or ZettelKasten or PKMS or 
>> whatever you want to call it) -two modalities of work that are so 
>> fundamentally different, the idea of trying to do both with the same tool 
>> might just never work, period. 
>>
>> Interestingly, author Victor Dorneau keeps his own Zettelkasten in 
>> TiddlyWiki, citing @Soren B's as his inspiration (GMTA ;-)...And tho his 
>> NoteTaking/GTD system is rather more complicated than i would like (it 
>> involves Emacs ORG mode and some proprietary mobile app,  from which he 
>> extracts & converts data to XML via a "simple" Golang script), i completely 
>> resonate with the principle:  while one's NoteMAKING tool should be 
>> optimised for "Intertwingularity" -as TiddlyWiki of course is- one's 
>> NoteTAKING tool should optimised for maximum speed & portability. 
>>
>> So, i'm now back to using Dynalist for agile NoteTaking, exporting my 
>> workfile at day's end as plain text, and copy/pasting it into a new Journal 
>> tiddler in TW for integration.  Crude, but effective enough, albeit with 
>> some editing overhead in TW that it would be nice to eliminate.  Am 
>> starting to explore the possibilities of Logseq as a potential Dynalist 
>> replacement; it does outlining in much the same way, but has some 
>> interesting export functions, including JSON and Roam JSON.  If there were 
>> a way in TW to import such exports and convert them into proper tiddlers... 
>> That would be amazing!
>>
>> If anyone else has got some other solution for agile NoteTaking that 
>> integrates nicely with TiddlyWiki for NoteMaking, i'd be very interested to 
>> hear about it.
>>
>

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

[tw5] Is it possible to add "Home" icon beside hamburger icon on menubar plugin

[Lishuo Lin]

I find that it will be much convenient if there is a home button beside (on 
the right of) the hamburger button when I use mobile phone to browse 
tiddlywiki.

Sorry that I am really not good at programming. Thanks guys.

-- 
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/a2cdf28e-f122-4419-8267-902485e277e9n%40googlegroups.com.

[tw5] Re: [TW5] - HammerWidgets to be revised

[TiddlyTweeter]

Ciao BurningTreeC

ALL the work you done on this has been good and solid in TW.
I use PC Desktop, PC Touch Tablet and Android Smart Phone.

Smart phones are problematic for multiple reasons. They are touch screen 
ONLY.

I AM interested in to what extent Hammer on smart-phone can do stuff I CAN 
do on touchscreen PC.
JUST FYI I found D-n-D, ironically, awful, on Android with TW :-(

Just a comment!
TT

On Saturday, 19 June 2021 at 10:10:05 UTC+2 BurningTreeC wrote:

> Hello dear TiddlyWikians,
>
> I'm currently revising my HammerWidgets based on the hammer.js library and 
> I'm planning to pack useful features into the plugin
>
> Here  there's a 
> preview (prerelease currently) with only the <$pan> widget included. In 
> this preview the pan widget is used to change the sidebar/story width using 
> a slider between the sidebar and the story
>
> There will also be <$swipe>, <$press>, <$tap> and <$pinch> widgets and I'm 
> looking fore useful things we can build with them so that I can include 
> them in the plugin
>
> Maybe some of you are interested to check the preview out and to give me 
> some feedback, all ideas are welcome :)
>
> best wishes, BTC
>

-- 
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/5292a816-b2b8-436b-9f52-52edc5e083fan%40googlegroups.com.

Re: [tw5] Re: Artwork for v5.2.0

[James Anderson]

that's the wrong chroma-w, correct one shoud be:
 [image: chroma-w.png]

On Saturday, 19 June 2021 at 11:26:01 UTC+1 James Anderson wrote:

> [image: preview.png]
>
> Move things in from the sides a little and provided some alternatives ont 
> he same theme,
>
> [image: chroma-orig.png]
> [image: chroma-w.png]
> [image: chroma-w-alt.png]
> [image: chroma-b-alt.png]
>
>
> On Friday, 18 June 2021 at 02:00:00 UTC+1 iamdar...@gmail.com wrote:
>
>> Hello all and thank you very much for your considerations and up votes! I 
>> wish to caution though that the when the image is smaller, as it would be 
>> viewed on the tiddlywiki homepage, the fish is much harder to identify. 
>> That was one of the reasons I switched things up in the 3rd/4th attempt.
>>
>> *f.brunsb*, as *Springer* stated it was the last one at the time, the 
>> floating 5.2.0 with the hand holding it that I really liked.
>>
>> I don't feel comfortable pointing out one of my own but if I should/need 
>> to I would say I like my *iamdar-1.png *(Assorted Swedish Tiddlers) the 
>> best (despite my concern about its visibility when smaller) and then 
>> *Logo4.png* (Drag'n'Drop JSON LG) next.
>>
>> I also really like *entw5.png* (Tilted Version) and *entw2.png* (Frank B 
>> #2).
>>
>> Thanks!
>>
>> On Thursday, June 17, 2021 at 8:14:15 PM UTC-4 Brian Radspinner wrote:
>>
>>> springer, if you could replace my first two attempts with the below 
>>> smaller-sized version, I'd appreciate it.[image: 
>>> v5.2.0_banner_brian.png]
>>>
>>> On Thursday, June 17, 2021 at 4:26:25 PM UTC-7 springer wrote:
>>>
 Frank, and all,

 My own sense is that your last entry is the most compelling of your set 
 (and is probably the post to which IAmDarthMole is replying), followed by 
 your #2. 

 Out of IAmDarthMole's submissions, I think (as Frank did, apparently) 
 that the first one (Assorted Swedish Tiddlers) has the most coherence.

 I also love James' RGB image, though it's a bit crowded out to the 
 edges. James, if you would pull everything in just a bit to give the 
 content breathing room, I think it would be a good contender!

 Out of Brian's submissions, I think the second captures something of 
 the drag-and-drop cues better than the first. For some reason, though, the 
 filesize is very large (on both submissions). So I think it would be a 
 better contender if the same idea could fit into a leaner file.

 In my more recent attempts I've been stepping away from including the 
 full "TiddlyWiki" label since (1) including that text is a bit redundant 
 in 
 its use-context, and was not part of the version-number images prior to 
 5.1.23, and (2) even if TiddlyWiki isn't ready to rebrand *now*, it's 
 possible that the conversation will be at a different place by the time we 
 approach the *next* revision... I'm agnostic about what should happen, but 
 I suppose it might be a strong point for a version's graphic banner just 
 to 
 focus on the version number along with whatever feature-hints can show up 
 without getting too busy.

 -Springer
 On Thursday, June 17, 2021 at 4:32:41 PM UTC-4 f.brunsb...@gmail.com 
 wrote:

> Hi to all artwork fans,
>
> I can support what springer writes. But perhaps we should already 
> agree on a few pictures where changes make sense.
>
> My three favourites so far are (excluding my pictures - these are the 
> best anyway), here without a ranking:
>
>- iamdar-1.png (IAmDarthMole)
>- dark-fields.png (springer)
>- 名称未設定.png (James W)
>
> have a nice night, Frank
>
> PS: @IAmDarthMole: Thanks for the pat on the back but which picture? 
> springer schrieb am Donnerstag, 17. Juni 2021 um 05:09:40 UTC+2:
>
>> Entries -- including through this most recent one submitted by James 
>> -- are all posted for easy comparison at 
>>
>> https://tw-logo-contest.tiddlyhost.com/
>>
>> Currently I haven't removed any entries except where authors have 
>> withdrawn them or indicated that one image is to replace another. So, 
>> Frank 
>> B currently has 5 entries, and others have 1-3 each. 
>>
>> If anyone has requests in the next couple days (such as "I'd love to 
>> see a variation on this with xyz font or xyz colors), I would be happy 
>> to 
>> give it a go (and am guessing the same holds for many of us who enjoy 
>> this 
>> kind of tinkering).
>>
>> -Springer
>> On Wednesday, June 16, 2021 at 6:26:59 PM UTC-4 james.w@gmail.com 
>> wrote:
>>
>>> something really basic:
>>>
>>> [image: キャプチャ.PNG]
>>>
>>> [image: 名称未設定.png]
>>>
>>> something about breaking things apart and putting them back together 
>>> :)
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wednesday, 16 June 2021 at 22:22:18 UTC+1 

[tw5] Re: empty.html should start with a "Centered story, fixed sidebar" setting.

[TiddlyTweeter]

Ciao Frank.brunsb... & all,

f.brunsb...@gmail.com wrote

> Apart from that, variable widths depending on your own screen would still 
> be worth considering for a default setting?
> You could use a min-width as well as a max-width for the Storyriver. 
> Designers and graphic artists like to work with the "golden ratio".
>

Right. The "golden ratio" is kinda helpful. TBH I use it in photography 
(visual medium) a lot, but the web is also "other" (largely textually 
organised medium) .

If I ever got time I'd love to do an internet version of MEDIEVAL 
MANUSCRIPTS that fill the page fully, all INLINE (in net jargon). 
Paragraphs are indicated by RUBICATION (starting paras in Red), not with 
blank links.

*Truth is, all this stuff is just conventions! *

Line length MAYBE needs to be CENTRALISED in TW at 80 chars / line for 
easier read. 
But if we went MEDIEVAL the font would be 3 times larger. 80 characters or 
less per screen width.

MY POINT is what we need is better FLEX on CSS not "perfect solutions" :-) 

Just my 2 cents!
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/edeec9a2-fc70-49e4-8d1e-04f3468c7d0en%40googlegroups.com.

Re: [tw5] [Plugin] Presenting TW5-Uglify! Plugin compression the TiddlyWIki way!

[Jan Johannpeter]

Hi Flibbles,
I think a publish filter is a good idea, I wanted to do that for years with
Mat's publish-plugin but lost it out of sight. What is the best tool to do
this right now?
It would be interesting to combine this with your plugin to have the
maximum reduction.

Best wishes Jan

Am Sa., 19. Juni 2021 um 01:21 Uhr schrieb Flibbles <
challenged.real...@gmail.com>:

> Hey Jan,
>
> I'm glad Uglify works well for you. To answer your questions
>
>
>1. Removing overridden core Tiddlers could reduce the code size
>somewhat, but I'm not sure how often that use case would come up. Even in
>my beastly TiddlyWiki projects, my overridden tiddlers don't make up very
>much space, particularly since I (and most people I'd think) only override
>smallish tiddlers. If it's something larger, a monkey-patch injection is
>used more often. Meanwhile, removing those overridden shadows could lead to
>a whole slew of nasty bugs if someone A) Removed the override down the
>line, or B) Tried to export their project into any form other than exactly
>what it is.
>2. Temporarily removing deactivated plugins seems out of scope for a
>content compression plugin (But just by a little. It compresses plugins.
>Removing them is a different job), and it's probably best done by the user.
>If they are serving versions of a tiddler where they want certain plugins
>excluded, they'd could use the publishFilter. A slightly elaborate
>tiddly-filter could exclude all deactivated plugins.
>
>
> Hope this helps!
> -Flibbles
>
> On Friday, June 18, 2021 at 6:45:03 PM UTC-4 Jan wrote:
>
>> Hi Flibbles,
>> great idea! My wikis tended to grow recently this seems to be a great
>> remedy.
>> Some Questions: Could it also remove
>> - overridden core Tiddlers
>> - temporarily deactivated plugins and inactive themes
>> from the version which is served?
>>
>> Best wishes Jan
>>
>> Am Di., 19. Jan. 2021 um 21:26 Uhr schrieb Flibbles <
>> challenge...@gmail.com>:
>>
>>> Some people want a minified version of the TW5 core, but it'd be too
>>> much work to maintain.
>>> Some people think it should remain uncompressed for the sake of editors,
>>> but TW5 continues to grow by the day.
>>> Some developers compress their plugins, making efficient code, but it's
>>> a pain for anyone debugging it.
>>> Some developers leave their plugins uncompressed, but that means it's
>>> larger than necessary for 90% of all end-users.
>>>
>>> Now there's a solution for everybody: TW5-uglify.
>>>
>>> This is a plugin primarily designed to be used by a Node.JS server. Your
>>> server has access to all your uncompressed and unpacked plugins, which is
>>> fine, since servers have the speed and memory for it. But what it sends to
>>> browsers are fully compressed plugins. Your little smart phones and tablets
>>> get the efficient TW5 they deserve.
>>>
>>> Or maybe you're a plugin developer who wants to minify their code. Now
>>> you no longer have to resort to using npm-gulp like some kind of chump.
>>> Your build process can remain an entirely TiddlyWiki process.
>>>
>>> Or maybe you want to miniify your standalone TiddlyWiki file. You can,
>>> but... think hard about this before you do it. Because unlike with
>>> TW5-Uglified server, compressing your standalone files is a one-way
>>> process. You'll forever have compressed code unless you download a new
>>> Tiddlywiki, redownload all your plugins, and transfer all your tiddlers
>>> from your old file. But hey! Maybe you're running TiddlyWiki on your 2000
>>> era Nokia phone in an wifi wasteland. Then go ahead.
>>>
>>> Check it out.
>>> Here's the demo site. 
>>> And here's the github page .
>>>
>>> Let me know what you all think.
>>>
>>> --
>>> 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/2ce6fad2-8600-4c73-940c-515548e49c1en%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/f7283bcf-1f16-426e-bfd7-402dfe712a45n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this 

[tw5] Re: Note Taking in 2021 (article & reflection)

[TiddlyTweeter]

Ciao ludwa6

Slightly in a different direction, but strongly related, is fact that 
computer science is UNDER appreciative of cognitive variations.

Meaning and pattern finding is an infinite human activity that existed long 
before computers or modern ideas of what is "kosher".

It is certainly true that some kind of typology of different strategies in  
HOW ONE LEARNS & RECORDS is useful.

But, to be honest, our current usual models on the net are somewhat crude 
to what human beings actually do, which is vast, in many directions.

Just thoughts :-)
TT 

On Friday, 18 June 2021 at 18:36:29 UTC+2 ludwa6 wrote:

> Came across this article today 
>  via HackerNews 
> (where it has sparked quite a lively comment thread 
> ), which brought me to 
> realise something about an inner tension i have been struggling for too 
> long to reconcile: it's about the difference between NoteTAKING vs 
> NoteMAKING (or DigitalGardening or MindMapping or ZettelKasten or PKMS or 
> whatever you want to call it) -two modalities of work that are so 
> fundamentally different, the idea of trying to do both with the same tool 
> might just never work, period. 
>
> Interestingly, author Victor Dorneau keeps his own Zettelkasten in 
> TiddlyWiki, citing @Soren B's as his inspiration (GMTA ;-)...And tho his 
> NoteTaking/GTD system is rather more complicated than i would like (it 
> involves Emacs ORG mode and some proprietary mobile app,  from which he 
> extracts & converts data to XML via a "simple" Golang script), i completely 
> resonate with the principle:  while one's NoteMAKING tool should be 
> optimised for "Intertwingularity" -as TiddlyWiki of course is- one's 
> NoteTAKING tool should optimised for maximum speed & portability. 
>
> So, i'm now back to using Dynalist for agile NoteTaking, exporting my 
> workfile at day's end as plain text, and copy/pasting it into a new Journal 
> tiddler in TW for integration.  Crude, but effective enough, albeit with 
> some editing overhead in TW that it would be nice to eliminate.  Am 
> starting to explore the possibilities of Logseq as a potential Dynalist 
> replacement; it does outlining in much the same way, but has some 
> interesting export functions, including JSON and Roam JSON.  If there were 
> a way in TW to import such exports and convert them into proper tiddlers... 
> That would be amazing!
>
> If anyone else has got some other solution for agile NoteTaking that 
> integrates nicely with TiddlyWiki for NoteMaking, i'd be very interested to 
> hear about it.
>

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

[tw5] Re: Awesome Tiddlywiki Example

[TiddlyTweeter]

Right! Awesome.

You might want to note that it extensively uses both Theme and Plugins by 
Thomas Elmiger to enable what the user needed!

Best wishes
TT

On Saturday, 19 June 2021 at 07:02:23 UTC+2 Mohammad wrote:

> Tweeted by @OffrayLC on 
> https://twitter.com/offrayLC/status/1405947061787312130?s=20
> a #Starforged character sheet done in @TiddlyWiki.
>
> See it here: https://mutabit.com/repos.fossil/502Lab/uv/wiki/502Lab.html#
>
>
> 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/5602ff34-a61c-46c1-8c54-ef52a64ee2e0n%40googlegroups.com.

[tw5] Re: [TW5] - HammerWidgets to be revised

[Saq Imtiaz]

Have a look at the variables made available to actions in the eventcatcher 
and see if that gives you what you need. I'm not familiar with hammerjs 
itself but event co-ordinates are made available as variables in 
eventcatcher. 

It could be that hammerjs events are structured differently though (which 
we might be able to find a generic way to support in eventcatcher). Or at 
least for now, you could subclass eventcatcher to create your own version 
of it that gives you the variables that you need.

On Saturday, June 19, 2021 at 11:10:32 AM UTC+2 BurningTreeC wrote:

> Ok, I see. The problem that I'd be facing is with the pan event and its 
> coordinates. How should those be propagated to an eventual <$eventcatcher> 
> widget?
>
> saq.i...@gmail.com schrieb am Samstag, 19. Juni 2021 um 11:04:17 UTC+2:
>
>> You are welcome. I used this approach for implementing the swipe events 
>> in Streams and it worked really well. The big plus is that it means users 
>> can create their own UX on top of these events with just wikitext.
>>
>> On Saturday, June 19, 2021 at 10:54:44 AM UTC+2 BurningTreeC wrote:
>>
>>> Hi Saq, no I hadn't considered that but I will, it's a great idea!
>>>
>>> Thanks!
>>>
>>> saq.i...@gmail.com schrieb am Samstag, 19. Juni 2021 um 10:39:33 UTC+2:
>>>
 Hi BTC,

 I was wondering if you have considered a more generic <$hammer> widget? 

 The idea would be to create a DOM node and enable the swipe, press, tap 
 etc events on that DOM node. This could then be wrapped in an 
 <$eventcatcher> to react to the events.
 Cheers,

 Saq
 On Saturday, June 19, 2021 at 10:10:05 AM UTC+2 BurningTreeC wrote:

> Hello dear TiddlyWikians,
>
> I'm currently revising my HammerWidgets based on the hammer.js library 
> and I'm planning to pack useful features into the plugin
>
> Here  there's 
> a preview (prerelease currently) with only the <$pan> widget included. In 
> this preview the pan widget is used to change the sidebar/story width 
> using 
> a slider between the sidebar and the story
>
> There will also be <$swipe>, <$press>, <$tap> and <$pinch> widgets and 
> I'm looking fore useful things we can build with them so that I can 
> include 
> them in the plugin
>
> Maybe some of you are interested to check the preview out and to give 
> me some feedback, all ideas are welcome :)
>
> best wishes, BTC
>


-- 
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/e9f38f3e-5970-4b30-bfc2-a7b524cc0b96n%40googlegroups.com.

[tw5] Re: [TW5] - HammerWidgets to be revised

[BurningTreeC]

Ok, I see. The problem that I'd be facing is with the pan event and its 
coordinates. How should those be propagated to an eventual <$eventcatcher> 
widget?

saq.i...@gmail.com schrieb am Samstag, 19. Juni 2021 um 11:04:17 UTC+2:

> You are welcome. I used this approach for implementing the swipe events in 
> Streams and it worked really well. The big plus is that it means users can 
> create their own UX on top of these events with just wikitext.
>
> On Saturday, June 19, 2021 at 10:54:44 AM UTC+2 BurningTreeC wrote:
>
>> Hi Saq, no I hadn't considered that but I will, it's a great idea!
>>
>> Thanks!
>>
>> saq.i...@gmail.com schrieb am Samstag, 19. Juni 2021 um 10:39:33 UTC+2:
>>
>>> Hi BTC,
>>>
>>> I was wondering if you have considered a more generic <$hammer> widget? 
>>>
>>> The idea would be to create a DOM node and enable the swipe, press, tap 
>>> etc events on that DOM node. This could then be wrapped in an 
>>> <$eventcatcher> to react to the events.
>>> Cheers,
>>>
>>> Saq
>>> On Saturday, June 19, 2021 at 10:10:05 AM UTC+2 BurningTreeC wrote:
>>>
 Hello dear TiddlyWikians,

 I'm currently revising my HammerWidgets based on the hammer.js library 
 and I'm planning to pack useful features into the plugin

 Here  there's 
 a preview (prerelease currently) with only the <$pan> widget included. In 
 this preview the pan widget is used to change the sidebar/story width 
 using 
 a slider between the sidebar and the story

 There will also be <$swipe>, <$press>, <$tap> and <$pinch> widgets and 
 I'm looking fore useful things we can build with them so that I can 
 include 
 them in the plugin

 Maybe some of you are interested to check the preview out and to give 
 me some feedback, all ideas are welcome :)

 best wishes, BTC

>>>

-- 
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/a5f046c1-7a3a-4665-8f90-8d6a56712c50n%40googlegroups.com.

[tw5] Re: [TW5] - HammerWidgets to be revised

[Saq Imtiaz]

You are welcome. I used this approach for implementing the swipe events in 
Streams and it worked really well. The big plus is that it means users can 
create their own UX on top of these events with just wikitext.

On Saturday, June 19, 2021 at 10:54:44 AM UTC+2 BurningTreeC wrote:

> Hi Saq, no I hadn't considered that but I will, it's a great idea!
>
> Thanks!
>
> saq.i...@gmail.com schrieb am Samstag, 19. Juni 2021 um 10:39:33 UTC+2:
>
>> Hi BTC,
>>
>> I was wondering if you have considered a more generic <$hammer> widget? 
>>
>> The idea would be to create a DOM node and enable the swipe, press, tap 
>> etc events on that DOM node. This could then be wrapped in an 
>> <$eventcatcher> to react to the events.
>> Cheers,
>>
>> Saq
>> On Saturday, June 19, 2021 at 10:10:05 AM UTC+2 BurningTreeC wrote:
>>
>>> Hello dear TiddlyWikians,
>>>
>>> I'm currently revising my HammerWidgets based on the hammer.js library 
>>> and I'm planning to pack useful features into the plugin
>>>
>>> Here  there's 
>>> a preview (prerelease currently) with only the <$pan> widget included. In 
>>> this preview the pan widget is used to change the sidebar/story width using 
>>> a slider between the sidebar and the story
>>>
>>> There will also be <$swipe>, <$press>, <$tap> and <$pinch> widgets and 
>>> I'm looking fore useful things we can build with them so that I can include 
>>> them in the plugin
>>>
>>> Maybe some of you are interested to check the preview out and to give me 
>>> some feedback, all ideas are welcome :)
>>>
>>> best wishes, BTC
>>>
>>

-- 
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/673206df-a189-4628-a8b5-99c97d67410fn%40googlegroups.com.

[tw5] Re: [TW5] - HammerWidgets to be revised

[BurningTreeC]

Hi Saq, no I hadn't considered that but I will, it's a great idea!

Thanks!

saq.i...@gmail.com schrieb am Samstag, 19. Juni 2021 um 10:39:33 UTC+2:

> Hi BTC,
>
> I was wondering if you have considered a more generic <$hammer> widget? 
>
> The idea would be to create a DOM node and enable the swipe, press, tap 
> etc events on that DOM node. This could then be wrapped in an 
> <$eventcatcher> to react to the events.
> Cheers,
>
> Saq
> On Saturday, June 19, 2021 at 10:10:05 AM UTC+2 BurningTreeC wrote:
>
>> Hello dear TiddlyWikians,
>>
>> I'm currently revising my HammerWidgets based on the hammer.js library 
>> and I'm planning to pack useful features into the plugin
>>
>> Here  there's 
>> a preview (prerelease currently) with only the <$pan> widget included. In 
>> this preview the pan widget is used to change the sidebar/story width using 
>> a slider between the sidebar and the story
>>
>> There will also be <$swipe>, <$press>, <$tap> and <$pinch> widgets and 
>> I'm looking fore useful things we can build with them so that I can include 
>> them in the plugin
>>
>> Maybe some of you are interested to check the preview out and to give me 
>> some feedback, all ideas are welcome :)
>>
>> best wishes, BTC
>>
>

-- 
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/2c861ada-de57-4697-9e4f-6b29e9671cdfn%40googlegroups.com.

[tw5] Re: How to remove duplicate values from $list ?

[Saq Imtiaz]

пожалуйста

On Saturday, June 19, 2021 at 10:46:06 AM UTC+2 Siniy-Kit wrote:

> Thank you. It works very good.
>
> суббота, 19 июня 2021 г. в 11:36:58 UTC+3, saq.i...@gmail.com: 
>
>> Have you tried using the unique[] operator?
>> https://tiddlywiki.com/#unique%20Operator
>> On Saturday, June 19, 2021 at 10:25:23 AM UTC+2 Siniy-Kit wrote:
>>
>>> Hi! I have a very simple list here 
>>> https://heeg.ru/shop2_2.html?id=1E2t7KGpcX5Gar0erhnUsH4th7kCk5BoVll-QYbNbTwY#Obshchij
>>>
>>> <$list 
>>> filter="[is[current]tagging[]tag[$:/Note]fields[]prefix[parametr]!suffix[-hide-hide]minlength[1]]"
>>>  
>>> variable=name >
>>>  <$text 
>>> text={{{[removeprefix[parametr]removesuffix[-hide]][!suffix[-hide]removeprefix[parametr]]
>>>  
>>> +[decodeuri[]]}}}/> 
>>> 
>>> *<$list  
>>> filter="[is[current]tagging[]tag[$:/Note]eachgetsplit[,]trim[]] 
>>> ">*
>>>
>>> **<>*
>>> **
>>>  
>>>
>>> it works,  but I get duplicates [image: Снимок экрана 2021-06-19 
>>> 111700.png] 
>>>  when I try to make enlist to this filter  to remove duplicates, I get 
>>> many lines and [[
>>> How to remove duplicate values from $list ? 
>>>
>>>

-- 
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/5c53ef3a-f75f-433a-874d-da76176202fan%40googlegroups.com.

[tw5] Re: How to remove duplicate values from $list ?

[Siniy-Kit]

Thank you. It works very good.

суббота, 19 июня 2021 г. в 11:36:58 UTC+3, saq.i...@gmail.com: 

> Have you tried using the unique[] operator?
> https://tiddlywiki.com/#unique%20Operator
> On Saturday, June 19, 2021 at 10:25:23 AM UTC+2 Siniy-Kit wrote:
>
>> Hi! I have a very simple list here 
>> https://heeg.ru/shop2_2.html?id=1E2t7KGpcX5Gar0erhnUsH4th7kCk5BoVll-QYbNbTwY#Obshchij
>>
>> <$list 
>> filter="[is[current]tagging[]tag[$:/Note]fields[]prefix[parametr]!suffix[-hide-hide]minlength[1]]"
>>  
>> variable=name >
>>  <$text 
>> text={{{[removeprefix[parametr]removesuffix[-hide]][!suffix[-hide]removeprefix[parametr]]
>>  
>> +[decodeuri[]]}}}/> 
>> 
>> *<$list  
>> filter="[is[current]tagging[]tag[$:/Note]eachgetsplit[,]trim[]] 
>> ">*
>>
>> **<>*
>> **
>>  
>>
>> it works,  but I get duplicates [image: Снимок экрана 2021-06-19 
>> 111700.png] 
>>  when I try to make enlist to this filter  to remove duplicates, I get 
>> many lines and [[
>> How to remove duplicate values from $list ? 
>>
>>

-- 
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/21e3b124-686d-4dcd-8c35-dc240eb084bfn%40googlegroups.com.

[tw5] Re: [TW5] - HammerWidgets to be revised

[Saq Imtiaz]

Hi BTC,

I was wondering if you have considered a more generic <$hammer> widget? 

The idea would be to create a DOM node and enable the swipe, press, tap etc 
events on that DOM node. This could then be wrapped in an <$eventcatcher> 
to react to the events.
Cheers,

Saq
On Saturday, June 19, 2021 at 10:10:05 AM UTC+2 BurningTreeC wrote:

> Hello dear TiddlyWikians,
>
> I'm currently revising my HammerWidgets based on the hammer.js library and 
> I'm planning to pack useful features into the plugin
>
> Here  there's a 
> preview (prerelease currently) with only the <$pan> widget included. In 
> this preview the pan widget is used to change the sidebar/story width using 
> a slider between the sidebar and the story
>
> There will also be <$swipe>, <$press>, <$tap> and <$pinch> widgets and I'm 
> looking fore useful things we can build with them so that I can include 
> them in the plugin
>
> Maybe some of you are interested to check the preview out and to give me 
> some feedback, all ideas are welcome :)
>
> best wishes, BTC
>

-- 
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/c9271d74-11f9-4050-b12c-dc8c88b09988n%40googlegroups.com.

[tw5] Re: How to remove duplicate values from $list ?

[Saq Imtiaz]

Have you tried using the unique[] operator?
https://tiddlywiki.com/#unique%20Operator
On Saturday, June 19, 2021 at 10:25:23 AM UTC+2 Siniy-Kit wrote:

> Hi! I have a very simple list here 
> https://heeg.ru/shop2_2.html?id=1E2t7KGpcX5Gar0erhnUsH4th7kCk5BoVll-QYbNbTwY#Obshchij
>
> <$list 
> filter="[is[current]tagging[]tag[$:/Note]fields[]prefix[parametr]!suffix[-hide-hide]minlength[1]]"
>  
> variable=name >
>  <$text 
> text={{{[removeprefix[parametr]removesuffix[-hide]][!suffix[-hide]removeprefix[parametr]]
>  
> +[decodeuri[]]}}}/> 
> 
> *<$list  
> filter="[is[current]tagging[]tag[$:/Note]eachgetsplit[,]trim[]] 
> ">*
>
> **<>*
> **
>  
>
> it works,  but I get duplicates [image: Снимок экрана 2021-06-19 
> 111700.png] 
>  when I try to make enlist to this filter  to remove duplicates, I get 
> many lines and [[
> How to remove duplicate values from $list ? 
>
>

-- 
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/91cff886-ab45-4b98-97fd-ac90dbc4e0ccn%40googlegroups.com.

[tw5] How to remove duplicate values from $list ?

[Siniy-Kit]

Hi! I have a very simple list 
here 
https://heeg.ru/shop2_2.html?id=1E2t7KGpcX5Gar0erhnUsH4th7kCk5BoVll-QYbNbTwY#Obshchij

<$list 
filter="[is[current]tagging[]tag[$:/Note]fields[]prefix[parametr]!suffix[-hide-hide]minlength[1]]"
 
variable=name >
 <$text 
text={{{[removeprefix[parametr]removesuffix[-hide]][!suffix[-hide]removeprefix[parametr]]
 
+[decodeuri[]]}}}/> 

*<$list  
filter="[is[current]tagging[]tag[$:/Note]eachgetsplit[,]trim[]] 
">*

**<>*
**
 

it works,  but I get duplicates [image: Снимок экрана 2021-06-19 111700.png]
 
 when I try to make enlist to this filter  to remove duplicates, I get many 
lines and [[
How to remove duplicate values from $list ? 

-- 
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/1e97cd61-3ab3-477e-9c24-3cf969d83e24n%40googlegroups.com.

[tw5] [TW5] - HammerWidgets to be revised

[BurningTreeC]

Hello dear TiddlyWikians,

I'm currently revising my HammerWidgets based on the hammer.js library and 
I'm planning to pack useful features into the plugin

Here  there's a 
preview (prerelease currently) with only the <$pan> widget included. In 
this preview the pan widget is used to change the sidebar/story width using 
a slider between the sidebar and the story

There will also be <$swipe>, <$press>, <$tap> and <$pinch> widgets and I'm 
looking fore useful things we can build with them so that I can include 
them in the plugin

Maybe some of you are interested to check the preview out and to give me 
some feedback, all ideas are welcome :)

best wishes, BTC

-- 
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/cbc9e83e-b8ed-456a-8e84-93adb00e6a53n%40googlegroups.com.

[tw5] Re: Note Taking in 2021 (article & reflection)

[Saq Imtiaz]

Hi Walt,

It is mostly plain text, but for Markdown formatting ( which I could live 
> without) and links- formatted like [Google](https:// Google.com) -which 
> would need conversion to [[wikilinks form|https://google.com]].
>

Right so importing something like this is definitely doable. You could then 
either use the markdown plugin and just use these tiddlers as markdown, or 
try to convert to TW markup. Where things get problematic is if your 
content is using features or syntax specific to them. A markdown to TW 
converter currently does not exist but should not be that much work. I've 
dabbled in both areas previously, so time permitting might be able to help 
out if you go down this road.
 

> To this end, it would be interesting to understand what features or 
>> workflow in Dynalist (or Logseq) make it better for note taking (vs 
>> TiddlyWiki) in your experience. 
>>
>
> Essentially it’s about speed and portability, traversing/ elaborating/ 
> reorganizing outlines as fast as fingers can type, and context switching 
> from local desktop to mobile phone in the field ( i.e. cloud) many times 
> per day without a hitch.  If this is possible in TW, I’d love to know how… 
> But i think it’s a case of architectures that are optimized for different 
> things, don’t you think?
>

It actually isn't my intention to push TiddlyWiki here. I find it 
interesting from a UX perspective when someone has a strong preference for 
one tool over another. I always feel its best to choose the tool best 
suited for a particular task. Also, tools should always complement one's 
natural way of thinking and working rather than the other way. I often find 
that conversations around note taking don't take into account individual 
cognitive differences.

Context switching and mobile usage is indeed in my opinion something TW 
doesn't have a good workflow for. The single file model doesn't help either 
when it comes to concerns about overwriting one version with one with older 
content. For the use case you describe I would consider this to be the 
biggest barrier. Setting up something like TiddlyWiki on node.js on Azure 
would help, especially with the upcoming server sent events feature in 
5.2.0. However, that only takes care of the syncing and the UI issues will 
remain.

> Still more challenging to my mind is the diff between an outlining editor 
and the text editing window in a tiddler;  that is fundamentally 
constrained by web standards -is it not?

Not really. After all dynalist also is implemented as a web app. Streams 
goes some ways towards creating a similar workflow in TiddlyWiki even 
though it was never intended as an outliner. I think a key difference is 
that in dynalist you feel like you are editing a document, versus in TW or 
Streams you have an edit window for one portion of the document. Part of 
the reason for that is how rich TW markup (think widgets and transclusions) 
can be and how different rendered text can be from the markup. This drives 
the need for separation between viewing and editing for all but the most 
limited use cases. However, for a keyboard driven workflow the difference 
in practice in Streams is not that significant in my experience.

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/14462118-dc8e-4214-8368-5ad19bbd5cb5n%40googlegroups.com.

[tw5] Re: Note Taking in 2021 (article & reflection)

[ludwa6]

I see what you can do about mode-switching , Charlie, and agree: that’s a 
good hi-level UI affordance..

Still, I think that there be pretty deep issues that keep TW from being a 
very agile NoteTaking tool. 

The best solution to the portability problem that I have found involves 
using Quine2 app on my iPhone, with sync to my desktop TW instance via 
Apple iCloud, but that is kind of a hack, overly dependent on Apple, I 
would say. 

Still more challenging to my mind is the diff between an outlining editor 
and the text editing window in a tiddler;  that is fundamentally 
constrained by web standards -is it not?

/walt 


On Saturday, June 19, 2021 at 5:21:42 AM UTC+1 cj.v...@gmail.com wrote:

> Instinctively, I'm thinking it should be possible to simultaneously have 
> both "modes" (taking vs making) at the same time available, just because 
> TiddlyWiki is so flexible.
>
> If not simultaneous modes, then it should be possible to switch between 
> the two modes without batting an eyelash, kind of like how my more recent 
> TiddlyWiki instances can switch between "reader" and "author" modes 
> (triggered by hide/show of sidebar).  Or how my Favourite Stuff and 
> Projects 
>  
> TiddlyWiki can switch between contexts.
>
> That said, I must chew on it a bit, and read all previously mentioned 
> articles a few times over.
>
>
> On Friday, June 18, 2021 at 6:29:42 PM UTC-3 ludwa6 wrote:
>
>> Thanks for engaging, Saq: responses inline below.
>>
>> On Friday, June 18, 2021 at 6:53:51 PM UTC+1 saq.i...@gmail.com wrote:
>>
>>> Crude, but effective enough, albeit with some editing overhead in TW 
 that it would be nice to eliminate.  Am starting to explore the 
 possibilities of Logseq as a potential Dynalist replacement; it does 
 outlining in much the same way, but has some interesting export functions, 
 including JSON and Roam JSON.  If there were a way in TW to import such 
 exports and convert them into proper tiddlers... That would be amazing!

>>>
>>> It is definitely doable. How useful such an import is will depend on 
>>> what kind of features/markup you are using in those systems and how well 
>>> they would translate to wikitext. Converting pure text though is very 
>>> straight forward.
>>>
>>
>> It is mostly plain text, but for Markdown formatting ( which I could live 
>> without) and links- formatted like [Google](https:// Google.com) -which 
>> would need conversion to [[wikilinks form|https://google.com]].
>>  
>>
>>>  
>>>
 If anyone else has got some other solution for agile NoteTaking that 
 integrates nicely with TiddlyWiki for NoteMaking, i'd be very interested 
 to 
 hear about it.

>>>
>>> To this end, it would be interesting to understand what features or 
>>> workflow in Dynalist (or Logseq) make it better for note taking (vs 
>>> TiddlyWiki) in your experience. 
>>>
>>
>> Essentially it’s about speed and portability, traversing/ elaborating/ 
>> reorganizing outlines as fast as fingers can type, and context switching 
>> from local desktop to mobile phone in the field ( i.e. cloud) many times 
>> per day without a hitch.  If this is possible in TW, I’d love to know how… 
>> But i think it’s a case of architectures that are optimized for different 
>> things, don’t you think?
>>
>> /walt 
>>
>

-- 
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/f8418686-058e-4114-aada-87b90564b499n%40googlegroups.com.

[tw5] Re: custom checkbox colors not working with PrintRiver Plugin

[S²]

*Thanks Brian, that's what I want. :-)*

One remark:
I prefer your first CSS post - it's more colored:

[image: 1.png]

2nd post:
[image: 2.png]
Brian Radspinner schrieb am Freitag, 18. Juni 2021 um 23:10:32 UTC+2:

> Actually, go with the below code, it has the default checkboxes fixed so 
> you don't need to specify the PrintRiver div at all
>
> input[type="checkbox"],
>
> .tc-tiddler-body input[type="checkbox"], 
> .tc-tiddler-preview-preview input[type="checkbox"], 
> .tc-sidebar-scrollable input[type="checkbox"] {
>-webkit-appearance:none;
>background-color: rgba(var(--primary),0.15);
>border: none;
>box-shadow: 0 0 0 1px rgba(var(--primary),1) inset;
>
>display: inline-block;
>height: 0.8em;
>outline-color: transparent;
>width: 0.8em;
> }
>
> input[type="checkbox"]:checked,
>
> .tc-tiddler-body input[type="checkbox"]:checked, 
> .tc-tiddler-preview-preview input[type="checkbox"]:checked, 
> .tc-sidebar-scrollable input[type="checkbox"]:checked { 
>background-color: rgba(var(--primary),1);
>
> }
>
> input[type="checkbox"]:checked::after,
> .tc-tiddler-body input[type="checkbox"]:checked::after, 
> .tc-tiddler-preview-preview input[type="checkbox"]:checked::after, 
> .tc-sidebar-scrollable input[type="checkbox"]:checked::after { 
>color: rgba(var(--secondary),1);
>content: "\2713";
>font-size: 1em;
>
>font-weight: bold;
>left: 0;
>position: relative;
>text-shadow: 1px 1px 1px #000;
>top: -0.3em;
> }
>
> input[type="checkbox"]:active,
>
> .tc-tiddler-body input[type="checkbox"]:active, 
> .tc-tiddler-preview-preview input[type="checkbox"]:active, 
> .tc-sidebar-scrollable input[type="checkbox"]:active { 
>border: none;
>box-shadow: none;
>outline-color: transparent;
> }
>
> On Friday, June 18, 2021 at 2:04:14 PM UTC-7 Brian Radspinner wrote:
>
>> I added the PrintRiver div class to the code. Give the below update a 
>> shot:
>>
>>
>> .tc-tiddler-body input[type="checkbox"],
>> .tc-tiddler-preview-preview input[type="checkbox"],
>> .tc-sidebar-scrollable input[type="checkbox"],
>> .tc-print-river-view-template input[type="checkbox"] {
>>
>>-webkit-appearance:none;
>>background-color: rgb(38,38,38);
>>border: none;
>>box-shadow: 0 0 0 1px rgba(210,210,210,0.5) inset;
>>display: inline-block;
>>height: 0.8em;
>>outline-color: transparent;
>>width: 0.8em;
>> }
>>
>> .tc-tiddler-body input[type="checkbox"]:checked,
>> .tc-tiddler-preview-preview input[type="checkbox"]:checked,
>> .tc-sidebar-scrollable input[type="checkbox"]:checked,
>> .tc-print-river-view-template input[type="checkbox"]:checked {
>>
>>background-color: rgba(38, 38, 38,0.5);
>> }
>>
>> .tc-tiddler-body input[type="checkbox"]:checked::after,
>> .tc-tiddler-preview-preview input[type="checkbox"]:checked::after,
>> .tc-sidebar-scrollable input[type="checkbox"]:checked::after,
>> .tc-print-river-view-template input[type="checkbox"]:checked::after {
>>
>>color: rgb(144,238,144);
>>content: "\2713";
>>font-size: 1.1em;
>>font-weight: bold;
>>left: 0;
>>position: relative;
>>text-shadow: 1px 1px 1px #000;
>>top: -0.3em;
>> }
>>
>> .tc-tiddler-body input[type="checkbox"]:active,
>> .tc-tiddler-preview-preview input[type="checkbox"]:active,
>> .tc-sidebar-scrollable input[type="checkbox"]:active,
>> .tc-print-river-view-template  input[type="checkbox"]:active {
>>
>>border: none;
>>box-shadow: none;
>>outline-color: transparent;
>> }
>>
>>
>>
>> On Friday, June 18, 2021 at 10:53:11 AM UTC-7 S² wrote:
>>
>>> Hello,
>>>
>>> I got this CSS ( 
>>>
>>> https://groups.google.com/g/tiddlywiki/c/483sdAJq6AY/m/r8Q3H8YmBQAJ
>>> ) from Brain - thanks to Brain - to have custom checkbox colors.
>>>
>>> This is working fine for the Wiki but not for the PrintRiver Plugin.
>>> Print Preview:
>>> [image: PrintRiver_print_window.png]
>>>
>>> This is my adapted CSS:
>>>
>>> .tc-tiddler-body input[type="checkbox"],
>>> .tc-tiddler-preview-preview input[type="checkbox"],
>>> .tc-sidebar-scrollable input[type="checkbox"] {
>>>-webkit-appearance:none;
>>>background-color: rgb(38,38,38);
>>>border: none;
>>>box-shadow: 0 0 0 1px rgba(210,210,210,0.5) inset;
>>>display: inline-block;
>>>height: 0.8em;
>>>outline-color: transparent;
>>>width: 0.8em;
>>> }
>>>
>>> .tc-tiddler-body input[type="checkbox"]:checked,
>>> .tc-tiddler-preview-preview input[type="checkbox"]:checked,
>>> .tc-sidebar-scrollable input[type="checkbox"]:checked {
>>>background-color: rgba(38, 38, 38,0.5);
>>> }
>>>
>>> .tc-tiddler-body input[type="checkbox"]:checked::after,
>>> .tc-tiddler-preview-preview input[type="checkbox"]:checked::after,
>>> .tc-sidebar-scrollable input[type="checkbox"]:checked::after {
>>>color: rgb(144,238,144);
>>>content: "\2713";
>>>font-size: 1.1em;
>>>font-weight: bold;
>>>left: 0;
>>>position: relative;
>>>text-shadow: 1px 1px 1px #000;
>>>top: