[tw5] Re: A voting/rating button on tiddler

[Mohammad]

The votings/ratings are stored in a hidden tiddler $:/vote/dataTiddler
So, original tiddlers are rated will remain intact.

Using this separate tiddler for ratings there are some opportunities:
Ratings can be exported
Ratings can be listed e.g list all tiddlers with 5 stars or no star, ...


On Monday, February 15, 2021 at 9:09:48 AM UTC+3:30 Mohammad wrote:

> This is a slightly better version of voting/rating tiddler
>
> Change log
> 1. elements in separate tiddlers (e.g styles, macro, template, ...)  (to 
> be a small plugin in future release)
> 2. only works on non-system tiddlers
> 3. uses colors for rating (red, yellow, grey, blue, green)
>
>
> To give a try
> 1. Download the attached json file
> 2. open https://tiddlywiki.com/
> 3. drag and drop the json file into https://tiddlywiki.com/
> 4. look at the new small buttons appear at the left of title bar of NON 
> system tiddlers
> 5. click on upvote / downvote buttons
>
>
> How to contribute
> - customize and re-share
> - improve performance
> - improve code simplicity
> - use better css
>
> Best wishes
> Mohammad
>
> On Monday, February 15, 2021 at 12:27:09 AM UTC+3:30 Mohammad wrote:
>
>> This is a rough idea for having a rating / voting button for tiddlers. It 
>> can be customized to be used even for tracking reading and so on!
>>
>> Drag and drop the attached tiddler into https://tiddlywiki.com/
>> Note to the new buttons appeared before tiddler title
>>
>> People with good CSS knowledge can help to have a better look and feel.
>> The code stores rating/voting in the same tiddler you rate, but it can be 
>> customized to store ratings in another tiddler(s)!
>>
>> - Please contribute
>> - Customize and reshare!
>> - do you think this is useful at all?
>>
>>
>> Credits go to GitHub!
>>
>>
>>
>> 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/ea55e22b-bf4c-4184-b622-e5903c1cb069n%40googlegroups.com.

[tw5] Re: A voting/rating button on tiddler

[Mohammad]

This is a slightly better version of voting/rating tiddler

Change log
1. elements in separate tiddlers (e.g styles, macro, template, ...)  (to be 
a small plugin in future release)
2. only works on non-system tiddlers
3. uses colors for rating (red, yellow, grey, blue, green)


To give a try
1. Download the attached json file
2. open https://tiddlywiki.com/
3. drag and drop the json file into https://tiddlywiki.com/
4. look at the new small buttons appear at the left of title bar of NON 
system tiddlers
5. click on upvote / downvote buttons


How to contribute
- customize and re-share
- improve performance
- improve code simplicity
- use better css

Best wishes
Mohammad

On Monday, February 15, 2021 at 12:27:09 AM UTC+3:30 Mohammad wrote:

> This is a rough idea for having a rating / voting button for tiddlers. It 
> can be customized to be used even for tracking reading and so on!
>
> Drag and drop the attached tiddler into https://tiddlywiki.com/
> Note to the new buttons appeared before tiddler title
>
> People with good CSS knowledge can help to have a better look and feel.
> The code stores rating/voting in the same tiddler you rate, but it can be 
> customized to store ratings in another tiddler(s)!
>
> - Please contribute
> - Customize and reshare!
> - do you think this is useful at all?
>
>
> Credits go to GitHub!
>
>
>
> 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/d0ce6f42-e546-4721-b8f0-05f8985b39ban%40googlegroups.com.


voting-rating-tiddler-r2.json
Description: application/json

[tw5] Question: a comparison filter more like a switch-case

[Mohammad Rahmani]

I want to return a color based on the user input: *x*

x <= -5   color:red
x < 0 color:yellow
x = 0 color:grey
x > 0 color:blue
x >= 5color:green

As a test, I have implemented the below solution.

*<$vars x=-3>*
<$list filter="[compare:number:lt[0]then[yellow]]
[compare:number:lteq[-5]then[red]] [compare:number:gt[0]then[blue]]
[compare:number:gteq[5]then[green]] +[last[]]" emptyMessage=grey>
<>



Copy paste in an empty tiddler in https://tiddlywiki.com/ and change x and
see the result, it works fine, but seems a lengthy solution.
What simpler, more semantic alternative do you propose?


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/CAAV1gMDBFhkhurS6FbFciAhqse7c%2B4b4dUJyoyfE_wfPKCscpQ%40mail.gmail.com.

[tw5] TW5: Paywall plugin

[Dr. Bob Jansen]

Anyone know of a paywall plugin for TW5? I have an interested potential 
client but he wants a paywall feature around parts of the wiki.


bobj

--

Dr Bob Jansen
122 Cameron St, Rockdale NSW 2216, Australia
Ph (Korea): +82 10-4494-0328
Ph (Australia) +61 414 297 448
Resume: http://au.linkedin.com/in/bobjan
Skype: bobjtls
KakaoTalk: bobjtls
http://cultconv.com

In line with the Australian anti-spam legislation, if you wish to receive no further 
email from me, please send me an email with the subject "No Spam"

--
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/6fa743cb-9e19-eb12-4a64-a9b0fe99343b%40gmail.com.

[tw5] Re: Tricky Filter Question

[Charlie Veniot]

Silly question:  If A was : Alpha Beta Alternative Delta, and B was still 
"Alpha Gamma", what should the final result be?

On Sunday, February 14, 2021 at 8:25:57 AM UTC-4 scourfie...@gmail.com 
wrote:

> Hey all
>
> I've got a situation where I have two lists. List A and List B. I've 
> specified some dummy info below:
>
> *A: *Alpha Beta Gamma Delta
> *B **(this will change by user input, but for this example:) *Alpha Gamma
>
> I want to write a filter to apply to List A where if any item does not 
> also appear on List B (i.e. in this case Beta and Delta are missing), it is 
> overwritten by the immediately subsequent value in List A, except the very 
> last item in List A which is remains in place to act as a default value if 
> no subsequent value can be found.
>
> So in this example the filtered version of List A would output as: *Alpha 
> Gamma Gamma Delta*, because Beta was not present in List B so it is 
> replaced by the next value of Gamma, and Delta remains because it is at the 
> very end.
>
> My question is, is there a way to do this with a static filter expression? 
> I'm sure I could make something with action-listops widgets that would do 
> the job when they were activated, but ideally I want something that updates 
> automatically whenever the user changes List B.
>
> Any help anyone could provide would be much appreciated.
>
> Thanks
> Joseph
>

-- 
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/468dd8da-2cb5-400c-9b92-9da9e633c708n%40googlegroups.com.

[tw5] Re: Nested List from a customized list

['Stephen Kimmel' via TiddlyWiki]

That is extremely close to what I need but there is one wrinkle that isn't 
obvious. If you look at my example, you'll see that the second and third 
have accent marks on the leading letter, α (alpha).  It would be nice, if 
it is possible, for the routine to ignore the accent and breath mark and 
group them as simply alpha. In the system I'm working in there are 
something six combinations of accents that can go on the first character 
but the accents should be ignored for this purpose. Is that possible? If 
not I can always go to my alternate plan of adding a field that would 
contain the character I want to use.

On Sunday, February 14, 2021 at 5:58:13 PM UTC-6 Eric Shulman wrote:

> On Sunday, February 14, 2021 at 3:01:56 PM UTC-8 Stephen Kimmel wrote:
>
>> several tiddlers that have names in Greek letters. I want to create a 
>> list rather like the sidebar type list with the heading being the first 
>> letter of the tiddler name followed by a list of tiddler titles that start 
>> with that Greek letter.
>>
>
> Using this list of greek letters: (48 symbols, upper and lower case for 
> each)
> *Α α Β β Γ γ Δ δ Ε ε Ζ ζ Η η Θ θ Ι ι Κ κ Λ λ Μ μ Ν ν Ξ ξ Ο ο Π π Ρ ρ Σ σ Τ 
> τ Υ υ Φ φ Χ χ Ψ ψ Ω ω*
>
> NOTE: A, B, E, H, K, M, N, O, P, T, Y, and X are *NOT* standard ASCII 
> characters, but are actual greek characters, copied and pasted directly 
> from the first paragraph of this page:
> https://en.wikipedia.org/wiki/Greek_alphabet
>
> <$list filter="[enlist[Α α Β β Γ γ Δ δ Ε ε Ζ ζ Η η Θ θ Ι ι Κ κ Λ λ Μ μ Ν ν 
> Ξ ξ Ο ο Π π Ρ ρ Σ σ Τ τ Υ υ Φ φ Χ χ Ψ ψ Ω ω]]" variable="letter">
><$list filter="[all[]prefixcount[]!match[0]]">
>   <>
>   <$list filter="[all[]prefix]">
>   <$link />
>   
>
> 
>
> Notes:
> * the first $list sets the "letter" variable to each of the 48 symbols, 
> one at a time
> * the second $list checks to see if there are any tiddlers that start with 
> the current letter
> * the letter is displayed on a line by itself
> * the third $list finds each tiddler that starts with the current letter
> * a link to each matching tiddler is displayed, indented by a space, on a 
> line by itself
>
> enjoy,
> -e
>

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

[tw5] Re: Nested List from a customized list

[Eric Shulman]

On Sunday, February 14, 2021 at 3:01:56 PM UTC-8 Stephen Kimmel wrote:

> several tiddlers that have names in Greek letters. I want to create a list 
> rather like the sidebar type list with the heading being the first letter 
> of the tiddler name followed by a list of tiddler titles that start with 
> that Greek letter.
>

Using this list of greek letters: (48 symbols, upper and lower case for 
each)
*Α α Β β Γ γ Δ δ Ε ε Ζ ζ Η η Θ θ Ι ι Κ κ Λ λ Μ μ Ν ν Ξ ξ Ο ο Π π Ρ ρ Σ σ Τ 
τ Υ υ Φ φ Χ χ Ψ ψ Ω ω*

NOTE: A, B, E, H, K, M, N, O, P, T, Y, and X are *NOT* standard ASCII 
characters, but are actual greek characters, copied and pasted directly 
from the first paragraph of this page:
https://en.wikipedia.org/wiki/Greek_alphabet

<$list filter="[enlist[Α α Β β Γ γ Δ δ Ε ε Ζ ζ Η η Θ θ Ι ι Κ κ Λ λ Μ μ Ν ν 
Ξ ξ Ο ο Π π Ρ ρ Σ σ Τ τ Υ υ Φ φ Χ χ Ψ ψ Ω ω]]" variable="letter">
   <$list filter="[all[]prefixcount[]!match[0]]">
  <>
  <$list filter="[all[]prefix]">
  <$link />
  
   


Notes:
* the first $list sets the "letter" variable to each of the 48 symbols, one 
at a time
* the second $list checks to see if there are any tiddlers that start with 
the current letter
* the letter is displayed on a line by itself
* the third $list finds each tiddler that starts with the current letter
* a link to each matching tiddler is displayed, indented by a space, on a 
line by itself

enjoy,
-e

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

[tw5] Nested List from a customized list

['Stephen Kimmel' via TiddlyWiki]

This will probably strike some of you as ridiculously simple ... I'm 
working with a wiki that contains several tiddlers that have names in Greek 
letters. I want to create a list rather like the sidebar type list with the 
heading being the first letter of the tiddler name followed by a list of 
tiddler titles that start with that Greek letter. So my list would look 
something like:

α
  αγαπε
  ἄγω
  ἀναβαίνω
β
  βάλλω
  βλέπω 

I want to exclude any tiddler that doesn't begin with a Greek letter so I'm 
assuming that I would have to supply a list of starting characters.

I would appreciate it if someone could point me in the right direction on 
this.

-- 
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/013d4fce-138d-4ead-b816-bed3d6357b81n%40googlegroups.com.

[tw5] A voting/rating button on tiddler

[Mohammad Rahmani]

This is a rough idea for having a rating / voting button for tiddlers. It
can be customized to be used even for tracking reading and so on!

Drag and drop the attached tiddler into https://tiddlywiki.com/
Note to the new buttons appeared before tiddler title

People with good CSS knowledge can help to have a better look and feel.
The code stores rating/voting in the same tiddler you rate, but it can be
customized to store ratings in another tiddler(s)!

- Please contribute
- Customize and reshare!
- do you think this is useful at all?


Credits go to GitHub!



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/CAAV1gMDJ1-kg8HH5jgod_J9w41mKnW6pWoCczR6bbd6pj2hLdQ%40mail.gmail.com.


voting-rating-tiddler.tid
Description: Binary data

Re: [tw5] How can I import the TiddlyWiki docs into my own wiki?

[si]

Thanks Jeremy that makes way more sense than what I was going to do!

On Sunday, 14 February 2021 at 14:27:04 UTC jeremy...@gmail.com wrote:

> @Jeremy - I did notice that the docs were available as a plugin, which is 
> definitely useful, but I'm not sure that it will solve my problem. Since I 
> will tag tiddlers from the docs "Read" when I have read them, I'll end up 
> just overriding every shadow tiddler anyway. In my case I want to be able 
> to tag tiddlers as "Read", but if that tiddler gets updated in the docs 
> have a way to overwrite that tiddler so that I know that I need to re-read 
> it and see what the updates were, without overwriting tiddlers that have 
> not been updated.
>
>
> I wouldn't recommend using tags to mark docs tiddlers as read, for the 
> reason you've spotted. A reasonable alternative might be to use a separate 
> tiddler to keep track of the status of each docs tiddler. You might use a 
> prefix like `$:/read/`, so that the status for "HelloThere" would be in 
> `$:/read/HelloThere`. You could use the "modified" field of the $:/read/ 
> tiddler to track when you marked a tiddler as read. You'd also be able to 
> detect tiddlers that had changed since you read them.
>
> Best wishes
>
> Jeremy
>
>
> @Soren - Yep there is certainly overlap between our respective problems. 
> Please let me know if you find a solution!
>
> On Saturday, 13 February 2021 at 19:13:33 UTC jeremy...@gmail.com wrote:
>
>> Hi Soren, si,
>>
>> Some time ago we made the docs from tiddlywiki.com available as a plugin 
>> in the official plugin library under the name $:/plugins/tiddlywiki/
>> tw5.com-docs. The idea was very much as you suggest, to be able to keep 
>> a copy of the docs in ones own wiki.
>>
>> Sadly, most of the documentation had already been written on the 
>> assumption that the docs tiddlers were ordinary tiddlers, not shadow 
>> tiddlers, and so constructions like this don’t work properly:
>>
>> <>
>>
>> It would be terrific to go through and fix these issues to make things a 
>> bit more useful.
>>
>> Best wishes
>>
>> Jeremy.
>>
>>
>>
>> On 13 Feb 2021, at 17:04, Soren Bjornstad  wrote:
>>
>> I'm very interested in this question, as *Grok TiddlyWiki*  faces a 
>> similar problem moving forward -- users might want to update to the latest 
>> edition of the book, but presumably will not want to lose their progress in 
>> all of the takeaways. What I've done so far is load the takeaways (and the 
>> snippets) in shadow tiddlers, so if the user has personalized any of them, 
>> they won't change if a different version is imported (I imagine the easiest 
>> way to upgrade will actually be to export the takeaways from the old 
>> version and then import them into the new version, where the user's 
>> existing takeaways will hide any takeaways with the same ID in the new 
>> version, e.g., showing only the user's versions unless new takeaways have 
>> been added).
>>
>> I could imagine extending this with a tool that identifies places where a 
>> shadow tiddler differs from an overridden tiddler, perhaps displaying the 
>> modification dates and a diff and providing the option of overwriting your 
>> version (or even just specific fields on your version -- e.g., in the 
>> takeaways scenario, the user might want to update the text of the prompt 
>> but keep the scheduling history).
>>
>> On Saturday, February 13, 2021 at 9:05:24 AM UTC-6 si wrote:
>>
>>> Hi all.
>>>
>>> I plan to import the entirety of tiddlywiki.com into my personal wiki, 
>>> so that I can learn TiddlyWiki more thoroughly by making flashcards and 
>>> notes as I read through the docs.
>>>
>>> Here are a couple of more specific points:
>>>
>>>- In order to keep track of what I have ready, I will create a 
>>>checkbox to add a "Done" tag to a tiddler if I have read it.
>>>- There may be overlap between the titles of tiddlers in the docs 
>>>and titles that already exist in my wiki. To get around this I will 
>>> prefix 
>>>every tiddler from the docs with "TiddlyWiki docs/".
>>>
>>> So far so good - I know how to do all that. The problem that I have is 
>>> that I want to be able to keep up with updates to the docs. This means that 
>>> I want to be able to re-import the docs, but only replace tiddlers that 
>>> have been modified more recently than already imported tiddlers.
>>>
>>> I don't know a way to approach this last point, so any help would be 
>>> much appreciated. Thanks in advance.
>>>
>>
>> -- 
>> 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/571f95f9-9c9b-4a2d-9b66-ef9e9eadda70n%40googlegroups.com
>>  
>> 

[tw5] Re: My setup for long static HTMLs with TOC and sections

[David Gifford]

On Sunday, February 14, 2021 at 9:54:03 AM UTC-6 springer wrote:

> David,
>
> Ah, I had not noticed that you had set up the Instructions as a details 
> drop-down, nice! (The little triangle at left is a bit easy to miss when 
> the summary doesn't have any additional css like contrasting background 
> color.)
>

It sounds like the conversion process will be quite a project (given that 
> I'm already fully invested in lots of things that won't convert easily into 
> static html, and there's no automatic conversion for getting telmiger-style 
> detail syntax boiled down to html details). 
>

Yes, if you have been using Telmiger's details plugin for a lot of 
tiddlers, it would take a while. But for starting from scratch, my actual 
process is actually fairly simple.

>
> Thanks for the documentation!
>
> -Springer
> On Friday, February 12, 2021 at 11:28:46 PM UTC-5 David Gifford wrote:
>
>> Hi Springer
>>
>> I use the details HTML in mine with statics. For an example, see the 
>> Instructions section of https://giffmex.org/wiki/apocrifos.at.html
>>
>> You can't use Telmiger's plugin, or any plugin, with statics. But you CAN 
>> create buttons with simple details snippets.
>>
>> I just updated this section for you. 
>> https://giffmex.org/gifts/documenting.tw.html#Sliders%20for%20static%20HTMLs%20with%20details%20and%20summary
>>
>> Note that transcluded tiddlers work best if their text is wrapped with 
>>  and  IN the transcluded tiddler.
>>
>> Enjoy!
>>
>>
>>
>> On Friday, February 12, 2021 at 8:14:24 PM UTC-6 springer wrote:
>>
>>> David,
>>>
>>> Thanks for sharing this. 
>>>
>>> I'm anticipating a need to convert a TW resource into a static html 
>>> archive so that it can be "handed off" to people who want something 
>>> standard, linear, and familiar (and that can be served up in non-dynamic 
>>> environments like sharepoint). 
>>>
>>> So, I might take advantage of something like this. 
>>>
>>> But one feature I wonder about is whether we can make ample use of 
>>> html's  feature to make sections collapsible, preserving a bit of 
>>> the dynamic experience without actually deviating from the linear flow of  
>>> static html.
>>>
>>> Of course, there are a couple different variations on details / slider / 
>>> reveal widgets in TiddlyWiki. I use TElmiger's plugin regularly, and would 
>>> love if exporting to static html could translate over to html's simpler 
>>>  (with ) syntax. Does that sound possible to you?q
>>>
>>> -Springer
>>>
>>> On Monday, February 8, 2021 at 11:34:45 AM UTC-5 David Gifford wrote:
>>>

 Hi everyone

 I updated my documentation to include a walk through on my set up for 
 writing:

- Long static HTMLs that transclude sections
- with id's for section headers for quick navigation to and from a 
manual table of contents
- where the link back up goes all the way to the top of the file, 
not just to another section.

 An example, in Spanish, of the output is 
 https://giffmex.org/wiki/apocrifos.at.html

 The walk through of how to do it, complete with button tiddlers and 
 image tiddlers, is at:


 https://giffmex.org/gifts/documenting.tw.html#My%20long%20static%20HTML%20setup




-- 
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/d0f18eeb-e6dc-47c9-9bd6-ea86a0853453n%40googlegroups.com.

Re: [tw5] Selective freelinks, freelinking basesd on filter condition

[springer]

Jeremy and all, 

The last frontier, then, is aliases... while we're at it. ;)

In addition to finding case-insensitive matches, freelinks ought to be able 
to look for specified variants on a tiddler's title (alternate spellings, 
plurals, adjectival forms, synonyms, whatever is important enough to flag). 
In the TWC implementation, I think the field for such strings was aliases 
... although both alias and aliases have apparently been put to other uses 
more recently... But whatever it's called, there ought to be some field 
that houses any name-variations that should serve as alternate "magnets" 
for freelinks.

This is a can of worms, perhaps. But if the worry was about slow-down, and 
filters can allow us to mitigate that effect as needed, then maybe it's 
time to put freelinks via aliases back on the table? 

(insert Cheshire grin emoji here)

-Springer
On Sunday, February 14, 2021 at 10:42:07 AM UTC-5 jeremy...@gmail.com wrote:

> Hi Elise,
>
> Great, glad it’s working for you.
>
>
> On 14 Feb 2021, at 15:40, springer  wrote:
>
> Meanwhile, I don't know whether anyone else actually might have preferred 
> some variant of the behavior as you initially set it up. Would some wish to 
> disable freelinks *except* on some limited set of tiddlers? For example, an 
> author might have plot-brainstorming and character-sketching tiddlers where 
> freelinks (or freelinks to all characters and events) are helpful, but want 
> to ensure that tiddlers with a "clean-prose" tag provide a reading 
> experience that suppresses all internal freelinks. That's not my use-case, 
> but I'd hate to imagine that my own nudge (to filter-limit the targets for 
> freelinks) breaks something that would be welcome to others!
>
>
> No problem at all. I documented the approach in the readme for the plugin, 
> and we can polish it up a bit if anyone is interested.
>
> Best wishes
>
> Jeremy.
>

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

[tw5] Re: My setup for long static HTMLs with TOC and sections

[springer]

David,

Ah, I had not noticed that you had set up the Instructions as a details 
drop-down, nice! (The little triangle at left is a bit easy to miss when 
the summary doesn't have any additional css like contrasting background 
color.)

It sounds like the conversion process will be quite a project (given that 
I'm already fully invested in lots of things that won't convert easily into 
static html, and there's no automatic conversion for getting telmiger-style 
detail syntax boiled down to html details). 

Thanks for the documentation!

-Springer
On Friday, February 12, 2021 at 11:28:46 PM UTC-5 David Gifford wrote:

> Hi Springer
>
> I use the details HTML in mine with statics. For an example, see the 
> Instructions section of https://giffmex.org/wiki/apocrifos.at.html
>
> You can't use Telmiger's plugin, or any plugin, with statics. But you CAN 
> create buttons with simple details snippets.
>
> I just updated this section for you. 
> https://giffmex.org/gifts/documenting.tw.html#Sliders%20for%20static%20HTMLs%20with%20details%20and%20summary
>
> Note that transcluded tiddlers work best if their text is wrapped with 
>  and  IN the transcluded tiddler.
>
> Enjoy!
>
>
>
> On Friday, February 12, 2021 at 8:14:24 PM UTC-6 springer wrote:
>
>> David,
>>
>> Thanks for sharing this. 
>>
>> I'm anticipating a need to convert a TW resource into a static html 
>> archive so that it can be "handed off" to people who want something 
>> standard, linear, and familiar (and that can be served up in non-dynamic 
>> environments like sharepoint). 
>>
>> So, I might take advantage of something like this. 
>>
>> But one feature I wonder about is whether we can make ample use of html's 
>>  feature to make sections collapsible, preserving a bit of the 
>> dynamic experience without actually deviating from the linear flow of  
>> static html.
>>
>> Of course, there are a couple different variations on details / slider / 
>> reveal widgets in TiddlyWiki. I use TElmiger's plugin regularly, and would 
>> love if exporting to static html could translate over to html's simpler 
>>  (with ) syntax. Does that sound possible to you?q
>>
>> -Springer
>>
>> On Monday, February 8, 2021 at 11:34:45 AM UTC-5 David Gifford wrote:
>>
>>>
>>> Hi everyone
>>>
>>> I updated my documentation to include a walk through on my set up for 
>>> writing:
>>>
>>>- Long static HTMLs that transclude sections
>>>- with id's for section headers for quick navigation to and from a 
>>>manual table of contents
>>>- where the link back up goes all the way to the top of the file, 
>>>not just to another section.
>>>
>>> An example, in Spanish, of the output is 
>>> https://giffmex.org/wiki/apocrifos.at.html
>>>
>>> The walk through of how to do it, complete with button tiddlers and 
>>> image tiddlers, is at:
>>>
>>>
>>> https://giffmex.org/gifts/documenting.tw.html#My%20long%20static%20HTML%20setup
>>>
>>>
>>>

-- 
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/6a7b853b-9066-49fd-a6e4-fb2ce9cba5efn%40googlegroups.com.

Re: [tw5] Selective freelinks, freelinking basesd on filter condition

[Jeremy Ruston]

Hi Elise,

Great, glad it’s working for you.

> On 14 Feb 2021, at 15:40, springer  wrote:
> 
> Meanwhile, I don't know whether anyone else actually might have preferred 
> some variant of the behavior as you initially set it up. Would some wish to 
> disable freelinks *except* on some limited set of tiddlers? For example, an 
> author might have plot-brainstorming and character-sketching tiddlers where 
> freelinks (or freelinks to all characters and events) are helpful, but want 
> to ensure that tiddlers with a "clean-prose" tag provide a reading experience 
> that suppresses all internal freelinks. That's not my use-case, but I'd hate 
> to imagine that my own nudge (to filter-limit the targets for freelinks) 
> breaks something that would be welcome to others!

No problem at all. I documented the approach in the readme for the plugin, and 
we can polish it up a bit if anyone is interested.

Best wishes

Jeremy.

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

Re: [tw5] Selective freelinks, freelinking basesd on filter condition

[springer]

Jeremy, brilliant, and thanks! 

I downloaded the prerelease, set the freelinking filter to [tag[Concepts]] 
with case insensitive, and confirmed that a new tiddler with 
 "Tiddlywiki community develops plugins, macros, and filters" 
shows Tiddlywiki (even with case difference), plus those last three terms, 
lit up as links (but not community). Just as envisioned!

Of course, I'm not in a position to understand yet what the performance 
drag will be on larger projects, but at least I should be able to narrow 
the scope of freelinks, without losing them altogether, if things get too 
slow.

Meanwhile, I don't know whether anyone else actually might have preferred 
some variant of the behavior as you initially set it up. Would some wish to 
disable freelinks *except* on some limited set of tiddlers? For example, an 
author might have plot-brainstorming and character-sketching tiddlers where 
freelinks (or freelinks to all characters and events) are helpful, but want 
to ensure that tiddlers with a "clean-prose" tag provide a reading 
experience that suppresses all internal freelinks. That's not my use-case, 
but I'd hate to imagine that my own nudge (to filter-limit the targets for 
freelinks) breaks something that would be welcome to others!

Thanks again for the super-responsive coding!

-Springer

On Saturday, February 13, 2021 at 7:05:30 AM UTC-5 jeremy...@gmail.com 
wrote:

> Hi Elise
>
>
> When I tried this recently, I thought it wasn't working... until I 
> realized we were talking past each other a bit. 
>
>- ALICE: I do say what I mean; I always mean what I say. It's the same 
>thing.
>- MAD HATTER: Not in the slightest. Is it the same thing to say you 
>see what you eat and you eat what you see?
>
> I envisioned EVERY tiddler being poised to display with outbound 
> freelinks, but pointing ONLY to the tiddlers with MyTag (wherever those 
> titles are mentioned in a text field).
> Instead, the recipe above limits freelinks the other way: we don't see 
> them EXCEPT when MyTag tiddlers are being viewed (but then we see outbound 
> links to EVERY tiddler whose title is mentioned).
>
> So..., is it possible to develop a filter that constrains which "targets" 
> are eligible? (Use case: I've got defined technical terms; whenever 
> pasted-in text happens to mention the term, the term "lights up")
>
>
> Ah, that makes sense. Apologies for the confusion.
>
> I’ve made a small tweak here that adds a filter to the “Settings” page of 
> the plugin where you can specify which tiddlers will be the targets of 
> freelinks:
>
>
> https://github.com/Jermolene/TiddlyWiki5/commit/0ed32fded996826a59832d7a7555bb16c4a57864
>
> The change should be available on the prerelease in 5 or 10 minutes,
>
> Best wishes
>
> Jeremy
>
>
>
> -Springer
>
>
> -- 
> 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/957004ff-97a7-497d-800e-c990156be8f7n%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/dd88d988-0a0d-47a4-ae63-fca0d3836b4en%40googlegroups.com.

Re: [tw5] On Github why?

[springer]

Jemer

On Saturday, February 13, 2021 at 6:24:51 AM UTC-5 jeremy...@gmail.com 
wrote:

> It turns out there’s only one instance of “options.event.event” in the 
> core source code, in the file $:/core/modules/utils/dom/modal.js.
>
> There is a bug there that would result in exactly the error message you 
> saw. I’ve committed a fix here:
>
>
> https://github.com/Jermolene/TiddlyWiki5/commit/50d0b6ee50689fd7ed8d7e8cc7ac4ea285da36d9
>
> You can try the change out at https://tiddlywiki.com/prerelease. Note 
> that this may not fix your underlying issue, it would be helpful to know 
> more about any plugins you’ve got installed, and exactly what action 
> prompted the crash.
>
> Best wishes
>
> Jeremy.
>
> On 13 Feb 2021, at 10:16, Ste  wrote:
>
> Welcome :)
> What are you gitting trying to do when this happens? TW version? Browser? 
> Os? Plugin related? 
>
> On Friday, 12 February 2021 at 18:24:36 UTC ooc...@gmail.com wrote:
>
>>
> -- 
> 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/8a9cbfe7-b4d0-4f2e-bc19-99767b9e28d4n%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/b1b01230-a470-43a9-9699-8b06e5afe30fn%40googlegroups.com.

Re: [tw5] Re: empty.html should start with "fluid-fixed" layout

[Mohammad Rahmani]

Best wishes
Mohammad


On Sun, Feb 14, 2021 at 5:58 PM si  wrote:

> @Mohammad - No I mean literally just using the zoom in the browser (i.e.
> "ctrl + -"). I use it when I just need to fit more content on the screen.
> But if you zoom-out to say 70-80%, with fluid-fixed the sidebar becomes too
> small for my use, and with fixed-fluid it takes up most of the screen (at
> least on my monitor).
>

Okay, I got it! Yes Soren proposal is the one you like!

Best wishes

> On Sunday, 14 February 2021 at 14:22:12 UTC Mohammad wrote:
>
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Sun, Feb 14, 2021 at 5:39 PM si  wrote:
>>
>>> @Soren @Jeremy I often zoom out when using TW in the browser so I also
>>> experience the problem Soren describes. I just wanted to add my vote to his
>>> alternative proposal.
>>>
>>
>> Hi Si,
>>  Is this related to text or other objects? Do you like to have a pair of
>> buttons to increase/decrease/reset the font size?
>>
>>>
>>> On Saturday, 13 February 2021 at 17:37:35 UTC Soren Bjornstad wrote:
>>>
 Maybe this is a good thread to piggyback on, as I've been having
 trouble with the fixed-fluid and fluid-fixed dichotomy lately. I have a
 different proposal. I don't have enough experience with either CSS or
 TiddlyWiki internals to know how difficult it would be to implement, but it
 doesn't seem crazy complicated to me.

 Here's the fundamental problem I see with the existing layout: there is
 a range of widths that are desirable for the story river. Up until a point,
 it should be as wide as possible while leaving enough room for the sidebar
 because you can fit more content on the screen that way. But eventually,
 making the story river wider makes it harder to read because the lines get
 unpleasantly long (see for example here
  on readable line
 widths). I think the desirable point for TW, at least for me, is often
 substantially wider than for, e.g., a novel, since there's also the
 side-by-side preview to consider, as well as tables, images, etc.
 Nevertheless, there's definitely a point where additional width makes the
 wiki less usable.

 The fluid-fixed mode is thus problematic because the story river will
 continue growing without bound as your monitor size increases, to the point
 where lines are unreadably long. It would be better to leave extra space to
 the right of the sidebar on large monitors. Fixed-fluid mode solves this
 problem, but if you set the story river width to a value that leaves enough
 space for the sidebar on a small monitor, the story river will be exactly
 the same size on a large monitor, wasting a ton of space, while if you set
 it to a value that looks good on a large monitor, the sidebar will be
 permanently exiled to the top of the screen on a small monitor.
 Essentially, whichever mode you choose, your wiki will look bad on a
 monitor of a significantly different size.

 I think a new mode should be offered, perhaps entirely replacing the
 existing modes and certainly becoming the default, which has two width
 breakpoints rather than the existing one:

- Zone 1, used when viewport width is below minimum side-by-side
width:
   - Sidebar above content; both sidebar and content take up full
   viewport width (as presently).
- Zone 2, used when viewport width is above minimum side-by-side
width but below *maximum story river width + fixed sidebar width*:
   - Sidebar to right of content; sidebar consumes a configurable
   fixed width, and story river consumes all remaining available space 
 (as in
   fluid-fixed presently).
- Zone 3, used when viewport width exceeds *maximum story river
width + fixed sidebar width*:
   - Sidebar to right of content; story river consumes a
   configurable maximum width, and sidebar consumes all remaining 
 available
   space (as in fixed-fluid presently).

 This would allow each wiki to select sidebar and story river widths
 that make sense for their content, while retaining a sane display on all
 screens.

 On Saturday, February 13, 2021 at 3:44:11 AM UTC-6 TiddlyTweeter wrote:

> coda coder wrote:
>
>> ... And If one disagrees, how does one express dissent?
>>
>
> The GitHub has "downvote" for that  :-).
>
> So far it has 8 "upvotes", which is significant enough to get
> attention there.
>
> My sense is that PMario's PR is, basically, a good idea.
>
> TT, x
>
>
>
 --
>>>
>> 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 discussio

Re: [tw5] Re: empty.html should start with "fluid-fixed" layout

[si]

@Mohammad - No I mean literally just using the zoom in the browser (i.e. 
"ctrl + -"). I use it when I just need to fit more content on the screen. 
But if you zoom-out to say 70-80%, with fluid-fixed the sidebar becomes too 
small for my use, and with fixed-fluid it takes up most of the screen (at 
least on my monitor).
On Sunday, 14 February 2021 at 14:22:12 UTC Mohammad wrote:

>
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Feb 14, 2021 at 5:39 PM si  wrote:
>
>> @Soren @Jeremy I often zoom out when using TW in the browser so I also 
>> experience the problem Soren describes. I just wanted to add my vote to his 
>> alternative proposal.
>>
>
> Hi Si,
>  Is this related to text or other objects? Do you like to have a pair of 
> buttons to increase/decrease/reset the font size?
>
>>
>> On Saturday, 13 February 2021 at 17:37:35 UTC Soren Bjornstad wrote:
>>
>>> Maybe this is a good thread to piggyback on, as I've been having trouble 
>>> with the fixed-fluid and fluid-fixed dichotomy lately. I have a different 
>>> proposal. I don't have enough experience with either CSS or TiddlyWiki 
>>> internals to know how difficult it would be to implement, but it doesn't 
>>> seem crazy complicated to me.
>>>
>>> Here's the fundamental problem I see with the existing layout: there is 
>>> a range of widths that are desirable for the story river. Up until a point, 
>>> it should be as wide as possible while leaving enough room for the sidebar 
>>> because you can fit more content on the screen that way. But eventually, 
>>> making the story river wider makes it harder to read because the lines get 
>>> unpleasantly long (see for example here 
>>>  on readable line 
>>> widths). I think the desirable point for TW, at least for me, is often 
>>> substantially wider than for, e.g., a novel, since there's also the 
>>> side-by-side preview to consider, as well as tables, images, etc. 
>>> Nevertheless, there's definitely a point where additional width makes the 
>>> wiki less usable.
>>>
>>> The fluid-fixed mode is thus problematic because the story river will 
>>> continue growing without bound as your monitor size increases, to the point 
>>> where lines are unreadably long. It would be better to leave extra space to 
>>> the right of the sidebar on large monitors. Fixed-fluid mode solves this 
>>> problem, but if you set the story river width to a value that leaves enough 
>>> space for the sidebar on a small monitor, the story river will be exactly 
>>> the same size on a large monitor, wasting a ton of space, while if you set 
>>> it to a value that looks good on a large monitor, the sidebar will be 
>>> permanently exiled to the top of the screen on a small monitor. 
>>> Essentially, whichever mode you choose, your wiki will look bad on a 
>>> monitor of a significantly different size.
>>>
>>> I think a new mode should be offered, perhaps entirely replacing the 
>>> existing modes and certainly becoming the default, which has two width 
>>> breakpoints rather than the existing one:
>>>
>>>- Zone 1, used when viewport width is below minimum side-by-side 
>>>width:
>>>   - Sidebar above content; both sidebar and content take up full 
>>>   viewport width (as presently).
>>>- Zone 2, used when viewport width is above minimum side-by-side 
>>>width but below *maximum story river width + fixed sidebar width*:
>>>   - Sidebar to right of content; sidebar consumes a configurable 
>>>   fixed width, and story river consumes all remaining available space 
>>> (as in 
>>>   fluid-fixed presently).
>>>- Zone 3, used when viewport width exceeds *maximum story river 
>>>width + fixed sidebar width*:
>>>   - Sidebar to right of content; story river consumes a 
>>>   configurable maximum width, and sidebar consumes all remaining 
>>> available 
>>>   space (as in fixed-fluid presently).
>>>
>>> This would allow each wiki to select sidebar and story river widths that 
>>> make sense for their content, while retaining a sane display on all screens.
>>>
>>> On Saturday, February 13, 2021 at 3:44:11 AM UTC-6 TiddlyTweeter wrote:
>>>
 coda coder wrote:

> ... And If one disagrees, how does one express dissent?
>

 The GitHub has "downvote" for that  :-).

 So far it has 8 "upvotes", which is significant enough to get attention 
 there.

 My sense is that PMario's PR is, basically, a good idea.

 TT, x

  

>>> -- 
>>
> 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/d288ea50-da29-4b39-b54f-a30ddd0d7d5dn%40googlegroups.com
>>  
>> 

Re: [tw5] How can I import the TiddlyWiki docs into my own wiki?

[Jeremy Ruston]

> @Jeremy - I did notice that the docs were available as a plugin, which is 
> definitely useful, but I'm not sure that it will solve my problem. Since I 
> will tag tiddlers from the docs "Read" when I have read them, I'll end up 
> just overriding every shadow tiddler anyway. In my case I want to be able to 
> tag tiddlers as "Read", but if that tiddler gets updated in the docs have a 
> way to overwrite that tiddler so that I know that I need to re-read it and 
> see what the updates were, without overwriting tiddlers that have not been 
> updated.

I wouldn't recommend using tags to mark docs tiddlers as read, for the reason 
you've spotted. A reasonable alternative might be to use a separate tiddler to 
keep track of the status of each docs tiddler. You might use a prefix like 
`$:/read/`, so that the status for "HelloThere" would be in 
`$:/read/HelloThere`. You could use the "modified" field of the $:/read/ 
tiddler to track when you marked a tiddler as read. You'd also be able to 
detect tiddlers that had changed since you read them.

Best wishes

Jeremy

> 
> @Soren - Yep there is certainly overlap between our respective problems. 
> Please let me know if you find a solution!
> 
>> On Saturday, 13 February 2021 at 19:13:33 UTC jeremy...@gmail.com wrote:
>> Hi Soren, si,
>> 
>> Some time ago we made the docs from tiddlywiki.com available as a plugin in 
>> the official plugin library under the name 
>> $:/plugins/tiddlywiki/tw5.com-docs. The idea was very much as you suggest, 
>> to be able to keep a copy of the docs in ones own wiki.
>> 
>> Sadly, most of the documentation had already been written on the assumption 
>> that the docs tiddlers were ordinary tiddlers, not shadow tiddlers, and so 
>> constructions like this don’t work properly:
>> 
>> <>
>> 
>> It would be terrific to go through and fix these issues to make things a bit 
>> more useful.
>> 
>> Best wishes
>> 
>> Jeremy.
>> 
>> 
>> 
 On 13 Feb 2021, at 17:04, Soren Bjornstad  wrote:
 
>>> I'm very interested in this question, as Grok TiddlyWiki  faces a similar 
>>> problem moving forward -- users might want to update to the latest edition 
>>> of the book, but presumably will not want to lose their progress in all of 
>>> the takeaways. What I've done so far is load the takeaways (and the 
>>> snippets) in shadow tiddlers, so if the user has personalized any of them, 
>>> they won't change if a different version is imported (I imagine the easiest 
>>> way to upgrade will actually be to export the takeaways from the old 
>>> version and then import them into the new version, where the user's 
>>> existing takeaways will hide any takeaways with the same ID in the new 
>>> version, e.g., showing only the user's versions unless new takeaways have 
>>> been added).
>>> 
>>> I could imagine extending this with a tool that identifies places where a 
>>> shadow tiddler differs from an overridden tiddler, perhaps displaying the 
>>> modification dates and a diff and providing the option of overwriting your 
>>> version (or even just specific fields on your version -- e.g., in the 
>>> takeaways scenario, the user might want to update the text of the prompt 
>>> but keep the scheduling history).
>>> 
> On Saturday, February 13, 2021 at 9:05:24 AM UTC-6 si wrote:
> Hi all.
> 
> I plan to import the entirety of tiddlywiki.com into my personal wiki, so 
> that I can learn TiddlyWiki more thoroughly by making flashcards and 
> notes as I read through the docs.
> 
> Here are a couple of more specific points:
> In order to keep track of what I have ready, I will create a checkbox to 
> add a "Done" tag to a tiddler if I have read it.
> There may be overlap between the titles of tiddlers in the docs and 
> titles that already exist in my wiki. To get around this I will prefix 
> every tiddler from the docs with "TiddlyWiki docs/".
> So far so good - I know how to do all that. The problem that I have is 
> that I want to be able to keep up with updates to the docs. This means 
> that I want to be able to re-import the docs, but only replace tiddlers 
> that have been modified more recently than already imported tiddlers.
> 
> I don't know a way to approach this last point, so any help would be much 
> appreciated. Thanks in advance.
 
 
>>> -- 
>>> 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/571f95f9-9c9b-4a2d-9b66-ef9e9eadda70n%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.
> T

Re: [tw5] Re: empty.html should start with "fluid-fixed" layout

[Mohammad Rahmani]

Best wishes
Mohammad


On Sun, Feb 14, 2021 at 5:39 PM si  wrote:

> @Soren @Jeremy I often zoom out when using TW in the browser so I also
> experience the problem Soren describes. I just wanted to add my vote to his
> alternative proposal.
>

Hi Si,
 Is this related to text or other objects? Do you like to have a pair of
buttons to increase/decrease/reset the font size?

>
> On Saturday, 13 February 2021 at 17:37:35 UTC Soren Bjornstad wrote:
>
>> Maybe this is a good thread to piggyback on, as I've been having trouble
>> with the fixed-fluid and fluid-fixed dichotomy lately. I have a different
>> proposal. I don't have enough experience with either CSS or TiddlyWiki
>> internals to know how difficult it would be to implement, but it doesn't
>> seem crazy complicated to me.
>>
>> Here's the fundamental problem I see with the existing layout: there is a
>> range of widths that are desirable for the story river. Up until a point,
>> it should be as wide as possible while leaving enough room for the sidebar
>> because you can fit more content on the screen that way. But eventually,
>> making the story river wider makes it harder to read because the lines get
>> unpleasantly long (see for example here
>>  on readable line
>> widths). I think the desirable point for TW, at least for me, is often
>> substantially wider than for, e.g., a novel, since there's also the
>> side-by-side preview to consider, as well as tables, images, etc.
>> Nevertheless, there's definitely a point where additional width makes the
>> wiki less usable.
>>
>> The fluid-fixed mode is thus problematic because the story river will
>> continue growing without bound as your monitor size increases, to the point
>> where lines are unreadably long. It would be better to leave extra space to
>> the right of the sidebar on large monitors. Fixed-fluid mode solves this
>> problem, but if you set the story river width to a value that leaves enough
>> space for the sidebar on a small monitor, the story river will be exactly
>> the same size on a large monitor, wasting a ton of space, while if you set
>> it to a value that looks good on a large monitor, the sidebar will be
>> permanently exiled to the top of the screen on a small monitor.
>> Essentially, whichever mode you choose, your wiki will look bad on a
>> monitor of a significantly different size.
>>
>> I think a new mode should be offered, perhaps entirely replacing the
>> existing modes and certainly becoming the default, which has two width
>> breakpoints rather than the existing one:
>>
>>- Zone 1, used when viewport width is below minimum side-by-side
>>width:
>>   - Sidebar above content; both sidebar and content take up full
>>   viewport width (as presently).
>>- Zone 2, used when viewport width is above minimum side-by-side
>>width but below *maximum story river width + fixed sidebar width*:
>>   - Sidebar to right of content; sidebar consumes a configurable
>>   fixed width, and story river consumes all remaining available space 
>> (as in
>>   fluid-fixed presently).
>>- Zone 3, used when viewport width exceeds *maximum story river width
>>+ fixed sidebar width*:
>>   - Sidebar to right of content; story river consumes a configurable
>>   maximum width, and sidebar consumes all remaining available space (as 
>> in
>>   fixed-fluid presently).
>>
>> This would allow each wiki to select sidebar and story river widths that
>> make sense for their content, while retaining a sane display on all screens.
>>
>> On Saturday, February 13, 2021 at 3:44:11 AM UTC-6 TiddlyTweeter wrote:
>>
>>> coda coder wrote:
>>>
 ... And If one disagrees, how does one express dissent?

>>>
>>> The GitHub has "downvote" for that  :-).
>>>
>>> So far it has 8 "upvotes", which is significant enough to get attention
>>> there.
>>>
>>> My sense is that PMario's PR is, basically, a good idea.
>>>
>>> TT, x
>>>
>>>
>>>
>> --
> 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/d288ea50-da29-4b39-b54f-a30ddd0d7d5dn%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/CAAV1gMC0Qb70GKUQA88_yEpvkWoixRxGTt%3DsgVrOGpkhh60YOg%40mail.gmail.com.

Re: [tw5] How can I import the TiddlyWiki docs into my own wiki?

[si]

@Jeremy - I did notice that the docs were available as a plugin, which is 
definitely useful, but I'm not sure that it will solve my problem. Since I 
will tag tiddlers from the docs "Read" when I have read them, I'll end up 
just overriding every shadow tiddler anyway. In my case I want to be able 
to tag tiddlers as "Read", but if that tiddler gets updated in the docs 
have a way to overwrite that tiddler so that I know that I need to re-read 
it and see what the updates were, without overwriting tiddlers that have 
not been updated.

@Soren - Yep there is certainly overlap between our respective problems. 
Please let me know if you find a solution!

On Saturday, 13 February 2021 at 19:13:33 UTC jeremy...@gmail.com wrote:

> Hi Soren, si,
>
> Some time ago we made the docs from tiddlywiki.com available as a plugin 
> in the official plugin library under the name $:/plugins/tiddlywiki/
> tw5.com-docs. The idea was very much as you suggest, to be able to keep a 
> copy of the docs in ones own wiki.
>
> Sadly, most of the documentation had already been written on the 
> assumption that the docs tiddlers were ordinary tiddlers, not shadow 
> tiddlers, and so constructions like this don’t work properly:
>
> <>
>
> It would be terrific to go through and fix these issues to make things a 
> bit more useful.
>
> Best wishes
>
> Jeremy.
>
>
>
> On 13 Feb 2021, at 17:04, Soren Bjornstad  wrote:
>
> I'm very interested in this question, as *Grok TiddlyWiki*  faces a 
> similar problem moving forward -- users might want to update to the latest 
> edition of the book, but presumably will not want to lose their progress in 
> all of the takeaways. What I've done so far is load the takeaways (and the 
> snippets) in shadow tiddlers, so if the user has personalized any of them, 
> they won't change if a different version is imported (I imagine the easiest 
> way to upgrade will actually be to export the takeaways from the old 
> version and then import them into the new version, where the user's 
> existing takeaways will hide any takeaways with the same ID in the new 
> version, e.g., showing only the user's versions unless new takeaways have 
> been added).
>
> I could imagine extending this with a tool that identifies places where a 
> shadow tiddler differs from an overridden tiddler, perhaps displaying the 
> modification dates and a diff and providing the option of overwriting your 
> version (or even just specific fields on your version -- e.g., in the 
> takeaways scenario, the user might want to update the text of the prompt 
> but keep the scheduling history).
>
> On Saturday, February 13, 2021 at 9:05:24 AM UTC-6 si wrote:
>
>> Hi all.
>>
>> I plan to import the entirety of tiddlywiki.com into my personal wiki, 
>> so that I can learn TiddlyWiki more thoroughly by making flashcards and 
>> notes as I read through the docs.
>>
>> Here are a couple of more specific points:
>>
>>- In order to keep track of what I have ready, I will create a 
>>checkbox to add a "Done" tag to a tiddler if I have read it.
>>- There may be overlap between the titles of tiddlers in the docs and 
>>titles that already exist in my wiki. To get around this I will prefix 
>>every tiddler from the docs with "TiddlyWiki docs/".
>>
>> So far so good - I know how to do all that. The problem that I have is 
>> that I want to be able to keep up with updates to the docs. This means that 
>> I want to be able to re-import the docs, but only replace tiddlers that 
>> have been modified more recently than already imported tiddlers.
>>
>> I don't know a way to approach this last point, so any help would be much 
>> appreciated. Thanks in advance.
>>
>
> -- 
> 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/571f95f9-9c9b-4a2d-9b66-ef9e9eadda70n%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/ad675444-f2e3-4fc6-bf5b-2754bfded046n%40googlegroups.com.

[tw5] Re: empty.html should start with "fluid-fixed" layout

[si]

@Soren @Jeremy I often zoom out when using TW in the browser so I also 
experience the problem Soren describes. I just wanted to add my vote to his 
alternative proposal.

On Saturday, 13 February 2021 at 17:37:35 UTC Soren Bjornstad wrote:

> Maybe this is a good thread to piggyback on, as I've been having trouble 
> with the fixed-fluid and fluid-fixed dichotomy lately. I have a different 
> proposal. I don't have enough experience with either CSS or TiddlyWiki 
> internals to know how difficult it would be to implement, but it doesn't 
> seem crazy complicated to me.
>
> Here's the fundamental problem I see with the existing layout: there is a 
> range of widths that are desirable for the story river. Up until a point, 
> it should be as wide as possible while leaving enough room for the sidebar 
> because you can fit more content on the screen that way. But eventually, 
> making the story river wider makes it harder to read because the lines get 
> unpleasantly long (see for example here 
>  on readable line 
> widths). I think the desirable point for TW, at least for me, is often 
> substantially wider than for, e.g., a novel, since there's also the 
> side-by-side preview to consider, as well as tables, images, etc. 
> Nevertheless, there's definitely a point where additional width makes the 
> wiki less usable.
>
> The fluid-fixed mode is thus problematic because the story river will 
> continue growing without bound as your monitor size increases, to the point 
> where lines are unreadably long. It would be better to leave extra space to 
> the right of the sidebar on large monitors. Fixed-fluid mode solves this 
> problem, but if you set the story river width to a value that leaves enough 
> space for the sidebar on a small monitor, the story river will be exactly 
> the same size on a large monitor, wasting a ton of space, while if you set 
> it to a value that looks good on a large monitor, the sidebar will be 
> permanently exiled to the top of the screen on a small monitor. 
> Essentially, whichever mode you choose, your wiki will look bad on a 
> monitor of a significantly different size.
>
> I think a new mode should be offered, perhaps entirely replacing the 
> existing modes and certainly becoming the default, which has two width 
> breakpoints rather than the existing one:
>
>- Zone 1, used when viewport width is below minimum side-by-side width:
>   - Sidebar above content; both sidebar and content take up full 
>   viewport width (as presently).
>- Zone 2, used when viewport width is above minimum side-by-side width 
>but below *maximum story river width + fixed sidebar width*:
>   - Sidebar to right of content; sidebar consumes a configurable 
>   fixed width, and story river consumes all remaining available space (as 
> in 
>   fluid-fixed presently).
>- Zone 3, used when viewport width exceeds *maximum story river width 
>+ fixed sidebar width*:
>   - Sidebar to right of content; story river consumes a configurable 
>   maximum width, and sidebar consumes all remaining available space (as 
> in 
>   fixed-fluid presently).
>
> This would allow each wiki to select sidebar and story river widths that 
> make sense for their content, while retaining a sane display on all screens.
>
> On Saturday, February 13, 2021 at 3:44:11 AM UTC-6 TiddlyTweeter wrote:
>
>> coda coder wrote:
>>
>>> ... And If one disagrees, how does one express dissent?
>>>
>>
>> The GitHub has "downvote" for that  :-).
>>
>> So far it has 8 "upvotes", which is significant enough to get attention 
>> there.
>>
>> My sense is that PMario's PR is, basically, a good idea.
>>
>> TT, x
>>
>>  
>>
>

-- 
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/d288ea50-da29-4b39-b54f-a30ddd0d7d5dn%40googlegroups.com.

[tw5] Re: Seeking reviewers for an upcoming TiddlyWiki textbook (both experts and beginners)

[stan...@gmail.com]

@Soren, @Walt, you are both right about the need for an editable version of 
GTW.  I was hoping to be able to have one on my iPad, but I ditched the 
idea yesterday afternoon after reading both of your messages.  The nice 
part about using the Chromebook is that I can have two copies, side by 
side: The first I am reading (and doing the exercises) and the second I am 
using for my editing suggestions.  The latter I will send back to @Soren.   

Stan
On Saturday, February 13, 2021 at 1:39:34 PM UTC-5 ludwa6 wrote:

> Now that i've got some experience w/ the spaced-repetition dynamic of the 
> Takeaway feature (since only night before last, i can see how it's helping 
> my recall), i have to agree with Soren: a read-only version of this book is 
> just not the same thing -not even close.  That being said: until i got the 
> editable version working in Quine (as previously described), i still got a 
> lot out of it in that mode.  But if i had a MacBook Air, @stan, i'd be 
> sorely tempted to take it to bed, because i *so* hate typing on glass, and 
> yet this book really inspires you to get weave some wiki.
>
> Speaking of which, @Soren, i have to ask: When the inevitable revision(s) 
> to this book come out, how do we upgrade without losing our edits?  You 
> mentioned something about this in another thread 
> , 
> but i'm still not clear from a user perspective how this is supposed to 
> work.  Would appreciate if you could explain.
>
> /walt
>
>
> On Saturday, February 13, 2021 at 4:59:11 PM UTC Soren Bjornstad wrote:
>
>> Stan, I've seen the same problem and unfortunately have not found a 
>> solution (my phone is new enough, I just haven't downloaded Quine). It's 
>> kind of bizarre that Apple doesn't have a way to open an HTML file on your 
>> phone (except in preview, which doesn't work since it doesn't have JS), 
>> even though you have both a browser and a file storage area.
>>
>> In any case, you're probably going to want to be able to save changes to 
>> the book to track your progress on the takeaways, so I'm not sure direct 
>> access through Firefox would work out well for this use case anyway.
>>
>>
>> On Saturday, February 13, 2021 at 7:48:14 AM UTC-6 stan...@gmail.com 
>> wrote:
>>
>>> Is there some way to read the book on an old iPad? I have an *iPad mini 
>>> 4, iOS 12.5*, so Quine 2 is not an option.  I tried the simplistic 
>>> approach of downloading the book using Firefox, but for the life of me, 
>>> could not figure out how to load it to read the book.  I also tried Safari, 
>>> Firefox Focus, Dolphin (in desperation!) and finally went to sleep.  A 
>>> tablet version sans Quine 2 would be attractive - I don't want to take my 
>>> Chromebook or one of my MacBook Airs to bed. 
>>>
>>> On Thursday, February 11, 2021 at 4:39:24 AM UTC-5 ludwa6 wrote:
>>>
 @Soren : Amazing piece of work, mate!  I just downloaded it last night 
 on my iPad, fully expecting to nod-off in <15min (a nice fat eBook on some 
 tech topic is my favourite form of sleeping pill :-)... But then the darn 
 thing kept me going *way* into the wee-hours, until i must either get up 
 and get working in TiddlyDesktop (had some trouble saving a local copy on 
 iPad via Quine2 [note1]), or else power-down somehow (which i finally 
 did... But it wasn't easy!). 

 So i think it's fair to say -at least for those like me that already 
 quite into TiddlyWiki, but also with serious gaps in know-how, begging to 
 be filled- this book is a great resource, even in current form.  To be 
 clear: this is no "5hi++y first draft" (as authors are advised these days 
 to call their first Request For Comments);  it's a very broad and deep 
 treatment of the subject, organised by a guy who really knows the tool and 
 how to use it to max advantage.  Moreover: Soren brings some progressive 
 learning theory to the table, in the form of this "Takeways" feature (i.e. 
 granular Q&A exercises in context) that really works.  

 Check it out!

 /walt


 On Tuesday, February 9, 2021 at 12:59:27 PM UTC PMario wrote:

> Hi,
> -as in my first post
> My github profile contains an e-mail link
> -m
> On Tuesday, February 9, 2021 at 3:55:29 AM UTC+1 Soren Bjornstad wrote:
>
>> I have a draft just about ready for review, but it looks like the 
>> group as configured doesn't allow me to see the contact information of 
>> anyone who posted. Could everyone who was interested in participating 
>> please take 30 seconds to fill out this Google form with your email 
>> address?
>>
>>
>> https://docs.google.com/forms/d/e/1FAIpQLSetcYknEP3bbJN38u1jpp2QJIHQUyhYArdc-ZQk7aSrQuqskA/viewform?usp=sf_link
>>
>> I am looking at having this out to you all by the end of the week and 
>> would love to have your fee

[tw5] Tricky Filter Question

[scourfie...@gmail.com]

Hey all

I've got a situation where I have two lists. List A and List B. I've 
specified some dummy info below:

*A: *Alpha Beta Gamma Delta
*B **(this will change by user input, but for this example:) *Alpha Gamma

I want to write a filter to apply to List A where if any item does not also 
appear on List B (i.e. in this case Beta and Delta are missing), it is 
overwritten by the immediately subsequent value in List A, except the very 
last item in List A which is remains in place to act as a default value if 
no subsequent value can be found.

So in this example the filtered version of List A would output as: *Alpha 
Gamma Gamma Delta*, because Beta was not present in List B so it is 
replaced by the next value of Gamma, and Delta remains because it is at the 
very end.

My question is, is there a way to do this with a static filter expression? 
I'm sure I could make something with action-listops widgets that would do 
the job when they were activated, but ideally I want something that updates 
automatically whenever the user changes List B.

Any help anyone could provide would be much appreciated.

Thanks
Joseph

-- 
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/d1e99395-7d9b-4059-983f-8f9abbbee1acn%40googlegroups.com.