Re: [tw5] accessibility support for links

[PMario]

Hi, 

On Friday, November 20, 2020 at 5:44:27 PM UTC+1 jn.pierr...@gmail.com 
wrote:
...

> You're right for external link. Though something like [[label|external 
> URL|hint text|language of target]] would be solving nearly all cases.

 
If I understand this https://www.boia.org/wcag2/cp/3.1.2 right it's not 
language of target, that needs to be defined. If the link has a label, that 
is a different language it has to be defined for the label. In most cases 
the target document will be that lang too. But it may be different.

-m

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

[tw5] Re: ViewTemplate question

[History Buff]

Finally got it figured out with the following code:

<$button> remove extraneous text
<$list filter="[tag[Railroads]]" variable="tid" >
<$list filter="[get[text]split[\define]splitregexp[.*>]]" 
variable="pap">
<$action-setfield $tiddler=<> text=<> />




On Friday, November 20, 2020 at 11:11:08 AM UTC-7 History Buff wrote:

> Alright, I've made a lot of progress. I would now like to be able to 
> delete all of the previous defines and transcludes that I had at the 
> beginning of the text field. I want to create a button that would do this 
> automatically for me. I know it's going to use splitregexp, but I am 
> totally new to regular expressions and have no idea where to start. Below 
> is the code at the beginning of the text field for the tiddler that I 
> included the screenshot for:
>
> \define successor() [[Wichita Northwestern Railway]]
>
> \define proposedroute() From Anthony, through the counties of Harper, 
> Barber, Pratt, Stafford, Pawnee, Rush, Ellis, Rooks and Phillips, to 
> Hastings, Nebraska. Length: 275 miles.
>
> \define business() Hutchinson, Kansas; Pratt, Kansas
>
> \define term() 50 years
>
> \define directors() O. P. Byers, Hutchinson, Kansas; E. A. Smith, Kansas 
> City, Missouri; H. J. Duvall, Hutchinson, Kansas; A. C. Mallory, 
> Hutchinson, Kansas; R. A. Cox, Pratt, Kansas.
>
> \define capital() $150,000 - 1,500 shares at $100 each
>
> \define stockholders() Same as directors.
>
> \define signers() All the directors; December 3, 1912
>
> \define notes() See: The [[Wichita Northwestern Railway]] 
> CompanyAmended Charters --- 1916-11-21; Vol. A-22, p. 199; 
> Increased Capital Stock --- 1917-01-04; Vol. A-22; pp. 274-280; Added more 
> counties to route --- 1918-04-03; Vol. A-23; pp. 445-447; Increased number 
> of directors --- 1919-11-24; Vol. A-25; p. 247; Included authority to 
> operate in Sedgwick County
>
> \define maplink()  target="_blank"> 
>
> \define paper() No
>
> <$list filter="[all[current]!has[notinbarnes]]">
>   <$transclude tiddler="Barnesbox">
>   
> 
>
> <$list filter="[all[current]has[notinbarnes]]">
>   <$transclude tiddler="Infobox">
>   
> 
>
> I would like to remove all of this text automatically because there are so 
> many tiddlers that I'd like to not do it manually. Any ideas for the 
> regular expression illiterate?
>
> Damon
>
> On Wednesday, November 18, 2020 at 9:16:35 PM UTC-7 History Buff wrote:
>
>> I'm always terrible at giving enough information and I apologize. After 
>> some thinking about it, I finally figured out a way to do it. I put the map 
>> link in a field named maplink and then put {{!!maplink}} in the appropriate 
>> area of the infobox table. Works like a charm. Whether you directly solve 
>> my issue or not, you always get me thinking in the right direction for 
>> which I thank you. Highest regards, sir.
>>
>> Damon
>>
>> On Wednesday, November 18, 2020 at 9:09:24 PM UTC-7 TW Tones wrote:
>>
>>> Damon,
>>>
>>> So as I understand it when you transclude  Infobox it is rendered with 
>>> the current tiddler set to the tiddler in which your code snipit is written 
>>> unless you take other steps to alter the currentTiddler, this is supported 
>>> by the idea that  you subsequently transclude the text field presumable of 
>>> the same tiddler.
>>>
>>> How does Infobox determine the correct map tiddler to link to?
>>>
>>> A global macro that references a field in the currentTiddler, will adapt 
>>> to local content.
>>>
>>> I do not have enough to help address your specific issues, but best of 
>>> luck. Feel free to ask more.
>>>
>>> Tones
>>>
>>> On Thursday, 19 November 2020 at 14:27:22 UTC+11 History Buff wrote:
>>>
 You're right, I forgot to show my code which I now have below:

 
 <$transclude tiddler="Infobox">
 
 

 <$transclude field=text mode=block/>

 I can't have a globally defined map link because each railroad has a 
 unique map.

 I misspoke earlier. My infobox stylesheet is being used.

 Damon
 On Wednesday, November 18, 2020 at 7:21:12 PM UTC-7 TW Tones wrote:

> Buff,
>
> If you place \defines in a tiddler tagged $:/tags/Macro it can be used 
> by name globally, similarly css placed in a tiddler 
> tagged $:/tags/Stylesheet will also be usable globally, this is the 
> approach to use when you want to reuse.
>
> Remember when using theit 
> assumes tiddler=<>, what is the current tiddler at the 
> time? 
> You do not show how you have coded the click here for map legend, but 
> it sounds like to need to set or reference the correct tiddler.
>
> I hope this is helping.
>
> Tones 
>
> On Thursday, 19 November 2020 at 10:15:33 UTC+11 History Buff wrote:
>
>> Tones,
>>
>> The aside element worked as long as it was above the transcluded 
>> body. The table didn't really work the way I wanted becuase, if the body 
>> text was very long, it wouldn't wrap ar

[tw5] Re: WikiWords vs Double Brackets

[Ed Heil]

Now that you mention the issues that come up with French, I guess it brings 
up the fact that many languages (many scripts) don't have a case 
distinction!  So there are definite limits to the internationality of 
CamelCase.

On Friday, November 20, 2020 at 12:01:53 PM UTC-5 jn.pierr...@gmail.com 
wrote:

> CamelCase is fine, but when you have an acronym in your title, the 
> question of how to do starts.
>
> for instance: HistoryOfHTMLBrowser or HistoryOfHtmlBrowser ? The first one 
> is more consistant but so many uppercase in a row does not seem very 
> Camel-like to me. And the second is nice but has no justification but ease 
> of reading (but that's a very good reason indeed).
>
> You have also some problem with apostrophes, although English has few of 
> them, French has many. For instance "l'heure et l'habitude" would be 
> LHeureEtLHabitude and that's ugly. You could resolve it by a title like 
> HeureEtHabitude but this example really show that, as has been told, 
> CamelCase is not fit for every purpose, and you have to have an extensive 
> naming convention to avoid misspelling.
>
> Also, orthographic corrector are showing a lot of ill-advised red because 
> of every camelcase word and you will have a harsh time spotting the true 
> errors or would have to clutter your dictionary with all your camels...
>
>
> Le vendredi 20 novembre 2020 à 16:47:20 UTC+1, Ed Heil a écrit :
>
>> Hey, thanks, all, this is exactly the kind of discussion I was hoping to 
>> hear!  It's been very informative, and I've really enjoyed looking at, 
>> e.g., Soren's Zettelkasten!
>>
>>
>> On Friday, November 20, 2020 at 5:47:11 AM UTC-5 TiddlyTweeter wrote:
>>
>>> Ciao Soren
>>>
>>> On Thursday, 19 November 2020 at 20:53:05 UTC+1 soren.b...@gmail.com 
>>> wrote:
>>>
 I use WikiWords in my Zettelkasten 
 . Besides saving a couple of 
 keystrokes, I actually like them aesthetically ... 
>>>
>>> And I think the restrictions in form 
  help 
 me come up with concise names for things.
>>>
>>>
>>> Right. I agree. Constraints can be highly productive of good use--when 
>>> they match well the users cognitive process.
>>> CamelCase is particularly interesting in that *its Semantics & Form 
>>> co-incide*. There is no need to add additional [[bracket]] construction 
>>> forms that envelope.
>>> In that sense CamelCase is: efficient,  meaningful, pretty obvious, 
>>> readable & MarkupMinimal.
>>>
>>> Of course, usage hangs out on more than that. Often CamelCase is not 
>>> appropriate, requires too much forethought, won't work for titles etc.
>>>
>>> But it still has real uses & excellent efficiency in some many use cases.
>>>
>>> Best wishes
>>> TT
>>>
>>

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

[tw5] Re: A How To Example: Relationship Matrix

[Charlie Veniot]

>
> Project:  ORM-ish à la TiddlyWiki 
>  project.
>

Just update a bit (in case you are interested in the programming behind the 
scenes):

[image: Screenshot 2020-11-20 at 10.24.18 PM.png] 

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

[tw5] Re: Using TiddlyWiki for fact-based information modelling and database engineering ???

[Charlie Veniot]

Project: ORM-ish à la TiddlyWiki 


Update, focused latest changes on "Reports":

   - Facts 
   
   - Arities 
   
   - Primary Keys 
   

   - Entities 
   
  - (NEW) Entity Relationship Matrix 
  

   

-- 
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/ad6e2791-f213-4939-910a-28a2974a10e5n%40googlegroups.com.

[tw5] Re: WikiWords vs Double Brackets

[tony]

i am a fan of the c2WikiConvention (<-- note the HungarianNotation mistake! 
or dialect?)  of CamelCase and it has stuck over the years. i think of 
WikiEntries as kind of a SubjectToken, a unique semantic entity  and it is 
easy to create and search with other tools like autocomplete in vim and 
ripgrep. Prefixing the WikiEntry with AnotherWikiEntry serves as a 
NameSpace; a compounding that reminds me of German or Urls. My TiddlyWiki 
has TiddlywikiStuff and i have no problem with not CamelCasing the NextWord 
when compounded as my searches are often CaseInsensitive.  i agree with the 
issues of NamingConventions and PunctuationAsProblem when CamelCasing but 
since my wiki is personal, the WikiLanguage stays subjective and unique. 
This is important to my setup as the TiddlywikiNodeJs TidFiles are housed 
in a VimWiki where the VimDictionary built from WikiEntries serves as an 
index to afford global autocompletion much like TiddlyWiki CtrlL 
CreateWikitextLink; PureLazyConvenience! WikiLanguage, a fun, jumbled mess.

Best,
tony
On Friday, November 20, 2020 at 9:01:53 AM UTC-8 jn.pierr...@gmail.com 
wrote:

> CamelCase is fine, but when you have an acronym in your title, the 
> question of how to do starts.
>
> for instance: HistoryOfHTMLBrowser or HistoryOfHtmlBrowser ? The first one 
> is more consistant but so many uppercase in a row does not seem very 
> Camel-like to me. And the second is nice but has no justification but ease 
> of reading (but that's a very good reason indeed).
>
> You have also some problem with apostrophes, although English has few of 
> them, French has many. For instance "l'heure et l'habitude" would be 
> LHeureEtLHabitude and that's ugly. You could resolve it by a title like 
> HeureEtHabitude but this example really show that, as has been told, 
> CamelCase is not fit for every purpose, and you have to have an extensive 
> naming convention to avoid misspelling.
>
> Also, orthographic corrector are showing a lot of ill-advised red because 
> of every camelcase word and you will have a harsh time spotting the true 
> errors or would have to clutter your dictionary with all your camels...
>
>
> Le vendredi 20 novembre 2020 à 16:47:20 UTC+1, Ed Heil a écrit :
>
>> Hey, thanks, all, this is exactly the kind of discussion I was hoping to 
>> hear!  It's been very informative, and I've really enjoyed looking at, 
>> e.g., Soren's Zettelkasten!
>>
>>
>> On Friday, November 20, 2020 at 5:47:11 AM UTC-5 TiddlyTweeter wrote:
>>
>>> Ciao Soren
>>>
>>> On Thursday, 19 November 2020 at 20:53:05 UTC+1 soren.b...@gmail.com 
>>> wrote:
>>>
 I use WikiWords in my Zettelkasten 
 . Besides saving a couple of 
 keystrokes, I actually like them aesthetically ... 
>>>
>>> And I think the restrictions in form 
  help 
 me come up with concise names for things.
>>>
>>>
>>> Right. I agree. Constraints can be highly productive of good use--when 
>>> they match well the users cognitive process.
>>> CamelCase is particularly interesting in that *its Semantics & Form 
>>> co-incide*. There is no need to add additional [[bracket]] construction 
>>> forms that envelope.
>>> In that sense CamelCase is: efficient,  meaningful, pretty obvious, 
>>> readable & MarkupMinimal.
>>>
>>> Of course, usage hangs out on more than that. Often CamelCase is not 
>>> appropriate, requires too much forethought, won't work for titles etc.
>>>
>>> But it still has real uses & excellent efficiency in some many use cases.
>>>
>>> Best wishes
>>> TT
>>>
>>

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

Re: [tw5] Re: Modal question (last question today, I promise)

[David Gifford]

Okay I deleted it from the toolmap.

On Fri, Nov 20, 2020 at 6:15 PM Alfonso Arciniega 
wrote:

> Jero and David,
>
> "TheBook" in my DropPages is just an early version of a manual that I put
> there just as an example that you can share any type of file at DropPages,
> not just TiddlyWiki documents. As it is an early draft, it should not be in
> TiddlyWiki Toolmap. I am interested to see if TheBook has been updated or
> completed.
>
> Cheers,
>
> Alfonso
>
> On Tuesday, November 17, 2020 at 6:11:03 PM UTC-7 jero...@gmail.com wrote:
>
>> Hi, David.
>> I saw this PDF TiddlyWiki manual:
>> https://my-tw-notes.droppages.com/TheBook.pdf
>> and could not find it in your "TiddlyWiki Toolmap".
>> I think it would be useful to include it there.
>> Have a nice day.
>>
>> On Tuesday, November 17, 2020 at 11:52:29 PM UTC+9 David Gifford wrote:
>>
>>> ¡Muchas de nadas!
>>>
>>> On Monday, November 16, 2020 at 10:20:04 PM UTC-6 j.te...@gmail.com
>>> wrote:
>>>
 Hey Dave...worked like a charm!
 It's a little more work, but it works...cool.
 Muchas gracias amigo. 👍

 On Monday, November 16, 2020 at 7:49:53 PM UTC-5 David Gifford wrote:

> Hi Julio
>
> Probably not what you are looking for, since it involves a mediating
> tiddler, but if you create a tiddler Avatarimg and add [img width="50%"
> [img_avatar.png]], adjusting the width to your liking, < "Avatarimg">> it works fine. Also lets you set the width, since an image
> could be too big and make the modal have scrollbars, which is no fun. - 
> Dave
>
> On Monday, November 16, 2020 at 6:27:13 PM UTC-6 j.te...@gmail.com
> wrote:
>
>> Hello there all,
>>
>> @David':
>> Enjoying your modal herehowever...
>> It looks like your modal doesn't play too nicely when it comes to
>> images.
>> Would it be possible to tweak this modal to work with images? or
>> Was it only meant for text content?
>>
>> Or...maybe it's the way I'm using the syntax?
>>
>> <>
>>
>> img_avatar.png being the name of the image tiddler.
>>
>> At your leisure no worries. Thanks in advance.
>>
>>
>> Best wishes,
>> Julio
>>
>> On Saturday, November 7, 2020 at 2:28:27 PM UTC-5 Ste wrote:
>>
>>> I may be way off here, I didn't really understand the queston, but
>>> here
>>> Is Jeds code for the help button which is what your link reminded me
>>> of.
>>>
>>> \define HelpButton(label, ButtonText:?)
>>> ^^(<$button popup="""$:/temp/popup/$(currentTiddler)$/$label$"""
>>> class='tc-btn-invisible tc-tiddlylink'>$ButtonText$)<$reveal
>>> type='popup' state="""$:/temp/popup/$(currentTiddler)$/$label$""">>> class='tc-drop-down'
>>> style='width:150px;max-width:75vw;white-space:pre-wrap;padding:10px;text-align:left;font-size:1.3em;border-radus:0.5em;'><$transclude
>>> field="""$label$"""/>^^
>>> \end
>>>
>>> On Saturday, 7 November 2020 at 18:48:07 UTC Ste wrote:
>>>
 Ah! Have looked! Very nice. Like a posher version of Jed's help
 Button macro! (it's somewhere from inmysocks).

 On Saturday, 7 November 2020 at 15:25:29 UTC David Gifford wrote:

> Here is what it looks like in practice. Click "Golden Rule, the"
> from the articles tab.
> https://giffmex.org/experiments/asterisk.modal.nt1.html
>
> On Saturday, November 7, 2020 at 9:02:36 AM UTC-6 David Gifford
> wrote:
>
>> I have been playing around with Eric's "hack" today. And I
>> created an editortoolbar button to insert the macro.
>>
>> Used in conjunction with the Freelinks plugin, this appears to be
>> a really great way to create and read content:
>>
>> 1. Create an article with minimal content, and add subordinate
>> content that can be viewed in modals without leaving the originating
>> tiddler. This is helpful since closing a target tiddler in some
>> situations/view modes in TiddlyWiki does not take you back to the
>> originating tiddler.
>> 2. By inserting the macro with a button, and inputting the title,
>> you create a 'link' that shows the tiddler in the modal if it 
>> exists, and
>> you have a button in the modal to create the tiddler in edit mode if 
>> it
>> does not.
>> 3. If you want links also without doing two separate steps, you
>> can use the Freelinks plugin.
>>
>> Now if only the comptext plugin gave you autocomplete suggestions
>> for this macro as it does for links...but even so, it is a great 
>> process
>> for writing articles uncluttered by all the details, but giving 
>> instant
>> access to those details without leaving the context of the article.
>>
>> Thanks again, Eric!
>>

[tw5] Re: The-Book Chapter 10

[Alfonso Arciniega]

https://github.com/kewapo/The-Tiddlywiki-Manual

This is the repository of TheBook, last updated in February 2020.

On Friday, November 20, 2020 at 5:27:09 PM UTC-7 Alfonso Arciniega wrote:

> As I mention in a another post, "TheBook" in my droppages site was just an 
> example of different formats that are able to be opened in droppages. It is 
> an old draft.
>
> Cheers,
>
> Alfonso
>
> On Friday, November 20, 2020 at 5:49:02 AM UTC-7 Ste wrote:
>
>> It was mentioned somewhere on here recently!
>> https://my-tw-notes.droppages.com/TheBook.pdf
>>
>> On Thursday, 19 November 2020 at 18:28:25 UTC dieg...@gmail.com wrote:
>>
>>> Hello! 
>>>
>>> Just a re-ping on this project! Does anyone know?
>>>
>>> On Saturday, July 25, 2020 at 5:22:51 PM UTC-5 dieg...@gmail.com wrote:
>>>
 Hello!

 I just want to checkup on this wonderful project! Has it been completed?

 On Wednesday, January 15, 2020 at 2:37:37 AM UTC-6, Luis Gonzalez wrote:
>
> After the Christmas stop I continue writing The-Book. I think is 
> important to include a little chapter with some architectural aspects of 
> Tiddlywiki.
> The attached pages contains the beginning.I saw the Tiddlywiki Hangout 
> 10 to fill the pages.
>
>
> * PLEASE:*
>
> * All experts in Tiddlywiki, check the table. If there is missing or 
> bad information, please tell me.
> * What more information do you think should be included in this 
> chapter?
>
>
>
>
> Thanks for your help.
> The-Book keep moving forward.
>


-- 
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/276703f8-d117-4ee7-b137-a0706489e4ffn%40googlegroups.com.

[tw5] Re: The-Book Chapter 10

[Alfonso Arciniega]

As I mention in a another post, "TheBook" in my droppages site was just an 
example of different formats that are able to be opened in droppages. It is 
an old draft.

Cheers,

Alfonso

On Friday, November 20, 2020 at 5:49:02 AM UTC-7 Ste wrote:

> It was mentioned somewhere on here recently!
> https://my-tw-notes.droppages.com/TheBook.pdf
>
> On Thursday, 19 November 2020 at 18:28:25 UTC dieg...@gmail.com wrote:
>
>> Hello! 
>>
>> Just a re-ping on this project! Does anyone know?
>>
>> On Saturday, July 25, 2020 at 5:22:51 PM UTC-5 dieg...@gmail.com wrote:
>>
>>> Hello!
>>>
>>> I just want to checkup on this wonderful project! Has it been completed?
>>>
>>> On Wednesday, January 15, 2020 at 2:37:37 AM UTC-6, Luis Gonzalez wrote:

 After the Christmas stop I continue writing The-Book. I think is 
 important to include a little chapter with some architectural aspects of 
 Tiddlywiki.
 The attached pages contains the beginning.I saw the Tiddlywiki Hangout 
 10 to fill the pages.


 * PLEASE:*

 * All experts in Tiddlywiki, check the table. If there is missing or 
 bad information, please tell me.
 * What more information do you think should be included in this 
 chapter?




 Thanks for your help.
 The-Book keep moving forward.

>>>

-- 
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/3e670f0f-deb6-4b53-a55f-73d4dc799af4n%40googlegroups.com.

[tw5] Re: Modal question (last question today, I promise)

[Alfonso Arciniega]

Jero and David,

"TheBook" in my DropPages is just an early version of a manual that I put 
there just as an example that you can share any type of file at DropPages, 
not just TiddlyWiki documents. As it is an early draft, it should not be in 
TiddlyWiki Toolmap. I am interested to see if TheBook has been updated or 
completed.

Cheers,

Alfonso

On Tuesday, November 17, 2020 at 6:11:03 PM UTC-7 jero...@gmail.com wrote:

> Hi, David.
> I saw this PDF TiddlyWiki manual:
> https://my-tw-notes.droppages.com/TheBook.pdf
> and could not find it in your "TiddlyWiki Toolmap".
> I think it would be useful to include it there.
> Have a nice day.
>
> On Tuesday, November 17, 2020 at 11:52:29 PM UTC+9 David Gifford wrote:
>
>> ¡Muchas de nadas!
>>
>> On Monday, November 16, 2020 at 10:20:04 PM UTC-6 j.te...@gmail.com 
>> wrote:
>>
>>> Hey Dave...worked like a charm!  
>>> It's a little more work, but it works...cool.
>>> Muchas gracias amigo. 👍
>>>
>>> On Monday, November 16, 2020 at 7:49:53 PM UTC-5 David Gifford wrote:
>>>
 Hi Julio

 Probably not what you are looking for, since it involves a mediating 
 tiddler, but if you create a tiddler Avatarimg and add [img width="50%" 
 [img_avatar.png]], adjusting the width to your liking, <>>> "Avatarimg">> it works fine. Also lets you set the width, since an image 
 could be too big and make the modal have scrollbars, which is no fun. - 
 Dave

 On Monday, November 16, 2020 at 6:27:13 PM UTC-6 j.te...@gmail.com 
 wrote:

> Hello there all,
>
> @David': 
> Enjoying your modal herehowever...
> It looks like your modal doesn't play too nicely when it comes to 
> images.
> Would it be possible to tweak this modal to work with images? or
> Was it only meant for text content?
>
> Or...maybe it's the way I'm using the syntax?
>
> <>
>
> img_avatar.png being the name of the image tiddler.
>
> At your leisure no worries. Thanks in advance. 
>
>
> Best wishes,
> Julio
>
> On Saturday, November 7, 2020 at 2:28:27 PM UTC-5 Ste wrote:
>
>> I may be way off here, I didn't really understand the queston, but 
>> here 
>> Is Jeds code for the help button which is what your link reminded me 
>> of. 
>>
>> \define HelpButton(label, ButtonText:?)
>> ^^(<$button popup="""$:/temp/popup/$(currentTiddler)$/$label$""" 
>> class='tc-btn-invisible tc-tiddlylink'>$ButtonText$)<$reveal 
>> type='popup' state="""$:/temp/popup/$(currentTiddler)$/$label$""">> class='tc-drop-down' 
>> style='width:150px;max-width:75vw;white-space:pre-wrap;padding:10px;text-align:left;font-size:1.3em;border-radus:0.5em;'><$transclude
>>  
>> field="""$label$"""/>^^
>> \end
>>
>> On Saturday, 7 November 2020 at 18:48:07 UTC Ste wrote:
>>
>>> Ah! Have looked! Very nice. Like a posher version of Jed's help 
>>> Button macro! (it's somewhere from inmysocks). 
>>>
>>> On Saturday, 7 November 2020 at 15:25:29 UTC David Gifford wrote:
>>>
 Here is what it looks like in practice. Click "Golden Rule, the" 
 from the articles tab. 
 https://giffmex.org/experiments/asterisk.modal.nt1.html

 On Saturday, November 7, 2020 at 9:02:36 AM UTC-6 David Gifford 
 wrote:

> I have been playing around with Eric's "hack" today. And I created 
> an editortoolbar button to insert the macro.
>
> Used in conjunction with the Freelinks plugin, this appears to be 
> a really great way to create and read content:
>
> 1. Create an article with minimal content, and add subordinate 
> content that can be viewed in modals without leaving the originating 
> tiddler. This is helpful since closing a target tiddler in some 
> situations/view modes in TiddlyWiki does not take you back to the 
> originating tiddler. 
> 2. By inserting the macro with a button, and inputting the title, 
> you create a 'link' that shows the tiddler in the modal if it exists, 
> and 
> you have a button in the modal to create the tiddler in edit mode if 
> it 
> does not.
> 3. If you want links also without doing two separate steps, you 
> can use the Freelinks plugin.
>
> Now if only the comptext plugin gave you autocomplete suggestions 
> for this macro as it does for links...but even so, it is a great 
> process 
> for writing articles uncluttered by all the details, but giving 
> instant 
> access to those details without leaving the context of the article.
>
> Thanks again, Eric!
>
> On Thursday, October 29, 2020 at 6:06:18 PM UTC-6 David Gifford 
> wrote:
>
>> Hi all
>>
>> Any way to add a link to the tiddler after the t

[tw5] Re: A truely great Slide-Show: reveal.js by Devin Weaver

[David Gifford]

It is now! Thanks for this discovery!

On Friday, November 20, 2020 at 3:27:50 PM UTC-6 Jan wrote:

> Hi folks!
> Am I the only one to have missed this jewel?
> Devin has Integrated the reveal.js library to TW.
> This is a true gamechanger!
> This has to be celebrated.
>
> Dave is this in your Dynalist already.
>
> https://sukima.github.io/tiddlywiki-reveal-js/
>
> enjoy!
> Jan
>

-- 
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/f97f5890-c0b6-4c9b-b025-c56759c37377n%40googlegroups.com.

[tw5] Re: [TW Official Plugin] Help regarding markdown

[Prestige]

Got it. Thanks :)

One more querry if you could help out, whatever changes I make in the wiki 
get refreshed as soon as I kill the server and start again. How can I make 
the changes stay?
I cannot save and retain the changes:

   - The WikiTitle and Subtitle
   - The theme tweaks - like the sidebar width and tiddler width.
   - even the changes mentioned in the fix.

How to save it and retain everytime I run the wiki?

Prestige.

On Saturday, 21 November 2020 at 03:47:54 UTC+5:30 saq.i...@gmail.com wrote:

> WikiLinks are not Markdown syntax. But using the official plugin you can 
> enable support for wikilinks by following the instructions at that link.
>
> On Friday, November 20, 2020 at 11:11:03 PM UTC+1 Prestige wrote:
>
>> So, TW5 supports wikilinks, but with markdown plugin, it won't? :(
>>
>> On Saturday, 21 November 2020 at 03:37:29 UTC+5:30 saq.i...@gmail.com 
>> wrote:
>>
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/issues/4610#issuecomment-621709996
>>>
>>> On Friday, November 20, 2020 at 10:15:03 PM UTC+1 Prestige wrote:
>>>

 Hi

 I am using wiki links in my markdown notes ` [[ ]] `. When I load them 
 in raw TW5 without any plugins, the links are displayed correctly but the 
 rest of the formatting is haywire. But as soon as I add a plugin - TW 
 Official Markdown Plugin, the wikilinks aren't captured while the rest of 
 the formatting seems okay.
 The above is related to raw TW5.

 I tried antosa/tw5-markdown  
 too, it works flawlessly but isn't working with a plugin 
  I like to use.

 Can someone help for a fix?

 Thanks
 Prestige

>>>

-- 
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/91d6ae20-a65a-400f-ac9f-190cf478d5fdn%40googlegroups.com.

[tw5] Re: The-Book Chapter 10

[amreus]

I believe this is the source  of the 
book.  

On Friday, November 20, 2020 at 7:49:02 AM UTC-5 Ste wrote:

> It was mentioned somewhere on here recently!
> https://my-tw-notes.droppages.com/TheBook.pdf
>
> On Thursday, 19 November 2020 at 18:28:25 UTC dieg...@gmail.com wrote:
>
>> Hello! 
>>
>> Just a re-ping on this project! Does anyone know?
>>
>> On Saturday, July 25, 2020 at 5:22:51 PM UTC-5 dieg...@gmail.com wrote:
>>
>>> Hello!
>>>
>>> I just want to checkup on this wonderful project! Has it been completed?
>>>
>>> On Wednesday, January 15, 2020 at 2:37:37 AM UTC-6, Luis Gonzalez wrote:

 After the Christmas stop I continue writing The-Book. I think is 
 important to include a little chapter with some architectural aspects of 
 Tiddlywiki.
 The attached pages contains the beginning.I saw the Tiddlywiki Hangout 
 10 to fill the pages.


 * PLEASE:*

 * All experts in Tiddlywiki, check the table. If there is missing or 
 bad information, please tell me.
 * What more information do you think should be included in this 
 chapter?




 Thanks for your help.
 The-Book keep moving forward.

>>>

-- 
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/2454da1b-d37f-40f6-a82e-df24309df915n%40googlegroups.com.

[tw5] Re: [TW Official Plugin] Help regarding markdown

[Saq Imtiaz]

WikiLinks are not Markdown syntax. But using the official plugin you can 
enable support for wikilinks by following the instructions at that link.

On Friday, November 20, 2020 at 11:11:03 PM UTC+1 Prestige wrote:

> So, TW5 supports wikilinks, but with markdown plugin, it won't? :(
>
> On Saturday, 21 November 2020 at 03:37:29 UTC+5:30 saq.i...@gmail.com 
> wrote:
>
>>
>> https://github.com/Jermolene/TiddlyWiki5/issues/4610#issuecomment-621709996
>>
>> On Friday, November 20, 2020 at 10:15:03 PM UTC+1 Prestige wrote:
>>
>>>
>>> Hi
>>>
>>> I am using wiki links in my markdown notes ` [[ ]] `. When I load them 
>>> in raw TW5 without any plugins, the links are displayed correctly but the 
>>> rest of the formatting is haywire. But as soon as I add a plugin - TW 
>>> Official Markdown Plugin, the wikilinks aren't captured while the rest of 
>>> the formatting seems okay.
>>> The above is related to raw TW5.
>>>
>>> I tried antosa/tw5-markdown  
>>> too, it works flawlessly but isn't working with a plugin 
>>>  I like to use.
>>>
>>> Can someone help for a fix?
>>>
>>> Thanks
>>> Prestige
>>>
>>

-- 
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/2276f1be-3b12-4918-841b-63f6b6021b72n%40googlegroups.com.

[tw5] Re: [TW Official Plugin] Help regarding markdown

[Prestige]

So, TW5 supports wikilinks, but with markdown plugin, it won't? :(

On Saturday, 21 November 2020 at 03:37:29 UTC+5:30 saq.i...@gmail.com wrote:

> https://github.com/Jermolene/TiddlyWiki5/issues/4610#issuecomment-621709996
>
> On Friday, November 20, 2020 at 10:15:03 PM UTC+1 Prestige wrote:
>
>>
>> Hi
>>
>> I am using wiki links in my markdown notes ` [[ ]] `. When I load them in 
>> raw TW5 without any plugins, the links are displayed correctly but the rest 
>> of the formatting is haywire. But as soon as I add a plugin - TW Official 
>> Markdown Plugin, the wikilinks aren't captured while the rest of the 
>> formatting seems okay.
>> The above is related to raw TW5.
>>
>> I tried antosa/tw5-markdown  
>> too, it works flawlessly but isn't working with a plugin 
>>  I like to use.
>>
>> Can someone help for a fix?
>>
>> Thanks
>> Prestige
>>
>

-- 
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/1df203f8-7ff7-4b4b-ba02-55252a0fe167n%40googlegroups.com.

Re: [tw5] Re: Seeking suggestions for my use case

[Dummy ME]

Oh yes, my bad. It was clearly mentioned in the guides. :)


On Fri, 20 Nov 2020 at 22:34, soren.b...@gmail.com <
soren.bjorns...@gmail.com> wrote:

> Author of TiddlyRemember here. Si is correct, you don't have to *host
> your wiki *on Node. You just have to have TiddlyWiki's Node version
> installed on your computer, so that TiddlyRemember can process your
> single-file wiki and extract the Anki questions.
>
> On Sunday, November 15, 2020 at 7:25:37 AM UTC-6 Prestige wrote:
>
>> Hello all!
>>  First of all, wish you all a happy festive season (as it is here in
>> India). I use TiddlyWiki is for my notes and use ANKI for Spaced
>> repetition. I wanted to put forward my use case, and seek suggestions from
>> anyone and everyone :)
>>
>> Current Requirement:
>>
>>1. Multi-Device Access
>>   1. Since I use Android and Ipad along with PC, it would be
>>   beneficial if I can read and/or edit my wiki on any of these devices.
>>   2. Currently, I use a bulky way to do so. Sync on Github (single
>>   file) -- It doesn't feel feasible as my wiki already going big.
>>2. ANKI Sync
>>   1. I found that there is a plugin called 'TiddlyRemember' which
>>   seems to fit my use.
>>   2. But it needs to TW to be installed on the node and if I do that
>>   I will lose the cross-platform editing capability.
>>   3. I am willing to make sync on the PC, but I would love to keep
>>   the multi-device access. I don't know how to work it out.
>>3. Export my notes
>>   1. I would be great if I could export my tiddlers/notes in some
>>   format like Markdown.
>>   2. Also, if it's possible can I, somehow, make my notes to be
>>   available in my 'tiddlers' folder as markdown files instead of .tids?
>>4. Backlinks of course.
>>   1. I see that TiddlyResearch uses TiddlyRemember and Backlinking
>>   quite well.
>>   2. Also, there is a plugin someone mentioned here
>>    
>> which
>>   can help create cards while annotating!! I couldn't find it yet. But I
>>   wonder if it works with TiddlyResearch?
>>5. Free?!
>>
>>
>> From what I can see from my own points above, I basically have problems
>> in setting up Tiddlywiki on Node while making it accessible to all my
>> devices (Maybe through Github).
>>
>> I will try installing TW on the node with TiddlyResearch and
>> TiddlyRemember and get back here :)
>> Please help me if possible to make it cross-platform.
>>
>> THANKS for reading a rather long post.
>>
>> Regards,
>> Prestige
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/zrBki-NYgHA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/53cb42b3-1664-45d4-8bc4-7889816b0cb4n%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/CAN_OoTj8sKdiOgHB_NfW63sJ3-pF25RxsMKPD3cSSw_vTc-Rzw%40mail.gmail.com.

[tw5] Re: [TW Official Plugin] Help regarding markdown

[Saq Imtiaz]

https://github.com/Jermolene/TiddlyWiki5/issues/4610#issuecomment-621709996

On Friday, November 20, 2020 at 10:15:03 PM UTC+1 Prestige wrote:

>
> Hi
>
> I am using wiki links in my markdown notes ` [[ ]] `. When I load them in 
> raw TW5 without any plugins, the links are displayed correctly but the rest 
> of the formatting is haywire. But as soon as I add a plugin - TW Official 
> Markdown Plugin, the wikilinks aren't captured while the rest of the 
> formatting seems okay.
> The above is related to raw TW5.
>
> I tried antosa/tw5-markdown  
> too, it works flawlessly but isn't working with a plugin 
>  I like to use.
>
> Can someone help for a fix?
>
> Thanks
> Prestige
>

-- 
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/3e3fc7b5-a82f-4ea5-9781-18dbdbf408b9n%40googlegroups.com.

[tw5] A truely great Slide-Show: reveal.js by Devin Weaver

[Jan]

Hi folks!
Am I the only one to have missed this jewel?
Devin has Integrated the reveal.js library to TW.
This is a true gamechanger!
This has to be celebrated.

Dave is this in your Dynalist already.

https://sukima.github.io/tiddlywiki-reveal-js/

enjoy!
Jan

--
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/5FB833B2.1060603%40googlemail.com.

[tw5] [TW Official Plugin] Help regarding markdown

[Prestige]

Hi

I am using wiki links in my markdown notes ` [[ ]] `. When I load them in 
raw TW5 without any plugins, the links are displayed correctly but the rest 
of the formatting is haywire. But as soon as I add a plugin - TW Official 
Markdown Plugin, the wikilinks aren't captured while the rest of the 
formatting seems okay.
The above is related to raw TW5.

I tried antosa/tw5-markdown  too, 
it works flawlessly but isn't working with a plugin 
 I like to use.

Can someone help for a fix?

Thanks
Prestige

-- 
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/11421df2-b188-4999-91d5-21e0ec68ee9an%40googlegroups.com.

Re: [tw5] Re: Help on translating a virtual stack of cards to wikitext needed...

[Jan]

Hi,
thanks for the syntax of the radio-widget... the problem is to match the 
css to the html-elements produced by this syntax.
Because I want the cards to be animated, I have to do the transformation 
without the reveal-widget.


Sorry for not answering sooner... I felt several times close to the 
result...


Best Wishes Jan

P.S. Reveal uses "text" instead of "value".



Am 18.11.2020 um 23:32 schrieb 'c pa' via TiddlyWiki:
The tiddlywiki way is to have the radio buttons set a value into a 
field and then display the corresponding card based on the field being 
populated


Pseudo code:

<$radio tiddler=<> field="card-state" 
value="Card-1">Card 1 
<$radio tiddler=<> field="card-state" 
value="Card-2">Card 2 
<$radio tiddler=<> field="card-state" 
value="Card-3">Card 3 


<$reveal type="match" state="!!card-state" value="Card-1">
Card 1 content


<$reveal type="match" state="!!card-state" value="Card-2">
Card 2 content


<$reveal type="match" state="!!card-state" value="Card-3">
Card 3 content


On Tuesday, November 17, 2020 at 10:27:52 AM UTC-8 Jan wrote:

Hi Fans of skeumorph (https://en.wikipedia.org/wiki/Skeuomorph)
design.

When trying to enhance my quizcard macro I stumbled upon this codepen
https://codepen.io/miroot/pen/YXpOGG

The html and css already work in TW
http://szen.io/quiz/#Quiz%20Cardstack .
So far I failed trying to translate the syntax to wikitext because
the
radio input makes use of IDs.

How can I solve this with the radiowidget?

Best wishes Jan







--
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/9cedf255-a283-466b-8822-5e3f185f0155n%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/5FB82DC1.4090008%40googlemail.com.

[tw5] Re: Lightweight diagrams (e.g. concept maps)?

[Sean Boyle]

CORAS: http://coras.sourceforge.net/ It is unfortunate that there are name 
collisions.  This is a methodology and a set of symbols to be used with 
drawing software, not related to the ginormous commercial package by the 
same name.  BPMN is certainly well documented and there are large tools 
which can automatically create workflows, &c. For creating drawings, it is 
really just a set of swimlanes and symbols which extend the IBM flowchart 
symbol set, which is a smaller problem.  Neither of these in and of 
themselves should radically grow an existing tool.

I can appreciate that no one wants to work on a plugin, send it out for 
feedback and get none, and perhaps I am guilty of that very thing as I have 
tried several of them.

Size is a problem.  There is the problem that each graphics plugin seems to 
have their own library, so they are all additive.  One must certainly be 
choosy.  At this point, I have several graphics related plugins loaded 
(railroad, tidgraph, rocklib/ mermaid-tw5, visjs, viz).  Tracking 
dependencies is not exactly easy (any advice on this?) and I seriously need 
to do some preening, but I have tried to torture one or more of these to 
get to my end goal.  It might be smarter to strip all of these out, store 
the source bits for any drawings, cook them externally and import the SVG 
(hoping that the external tools do not bloat the SVG too much).
I am probably already asking a lot of it already by having several years 
worth of journals with drawings, all encrypted.  My initial plan was to 
replace a daily planner and moleskine / engineering pad with a software 
version which is as platform independent as possible today, lightweight, 
and fulfills much of the requirement which I traditionally would fulfill 
with a pencil.  In the abstract, it is simple enough.  The implementation 
is really the dickens, no doubt filled with what TRIZ folks call 
contradictions.  For now, I should probably stick with it for the strengths 
and go elsewhere for the missing bits.  Before trying to integrate all with 
Tiddlywiki, I was using yEd (https://yworks.com/products/yed) for BPMN and 
CORAS (imported the symbols), and something like draw.io (jgraph).

This was a good discussion.  Thanks to TiddyTweeter and PMario!

On Saturday, November 7, 2020 at 5:33:32 AM UTC-8 TiddlyTweeter wrote:

> PMario wrote:
>>
>>
>> ... So for me it looks like a 20/80 approach. 20% of time invested to get 
>> 80% of functions out of it.
>>
>> This gives you the possibility to implement 5 different libs (as seen at: 
>> https://gt6796c.github.io/) at the same time as doing 100% for 1 
>> library. ... (sometimes) That's a good idea 
>>
>
>  Right. Ambitious but useful.
>
> It seems none of the libraries took of (eg: lack of feedback), 
>>
>
> Right. There was virtually no feedback at all. Though the tool really 
> needed a lot to help the author.
>
> I am pretty sure that is why its development froze. They got no feedback.
>
> --- 
>
> The "Mermaid" approach is interesting.
>
> Mainly because  it is a unifying front-end that, if done well, would save 
> a lot of hassle.
>
> Best wishes
> TT
>

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

[tw5] Re: ViewTemplate question

[History Buff]

Alright, I've made a lot of progress. I would now like to be able to delete 
all of the previous defines and transcludes that I had at the beginning of 
the text field. I want to create a button that would do this automatically 
for me. I know it's going to use splitregexp, but I am totally new to 
regular expressions and have no idea where to start. Below is the code at 
the beginning of the text field for the tiddler that I included the 
screenshot for:

\define successor() [[Wichita Northwestern Railway]]

\define proposedroute() From Anthony, through the counties of Harper, 
Barber, Pratt, Stafford, Pawnee, Rush, Ellis, Rooks and Phillips, to 
Hastings, Nebraska. Length: 275 miles.

\define business() Hutchinson, Kansas; Pratt, Kansas

\define term() 50 years

\define directors() O. P. Byers, Hutchinson, Kansas; E. A. Smith, Kansas 
City, Missouri; H. J. Duvall, Hutchinson, Kansas; A. C. Mallory, 
Hutchinson, Kansas; R. A. Cox, Pratt, Kansas.

\define capital() $150,000 - 1,500 shares at $100 each

\define stockholders() Same as directors.

\define signers() All the directors; December 3, 1912

\define notes() See: The [[Wichita Northwestern Railway]] 
CompanyAmended Charters --- 1916-11-21; Vol. A-22, p. 199; 
Increased Capital Stock --- 1917-01-04; Vol. A-22; pp. 274-280; Added more 
counties to route --- 1918-04-03; Vol. A-23; pp. 445-447; Increased number 
of directors --- 1919-11-24; Vol. A-25; p. 247; Included authority to 
operate in Sedgwick County

\define maplink()  

\define paper() No

<$list filter="[all[current]!has[notinbarnes]]">
  <$transclude tiddler="Barnesbox">
  


<$list filter="[all[current]has[notinbarnes]]">
  <$transclude tiddler="Infobox">
  


I would like to remove all of this text automatically because there are so 
many tiddlers that I'd like to not do it manually. Any ideas for the 
regular expression illiterate?

Damon

On Wednesday, November 18, 2020 at 9:16:35 PM UTC-7 History Buff wrote:

> I'm always terrible at giving enough information and I apologize. After 
> some thinking about it, I finally figured out a way to do it. I put the map 
> link in a field named maplink and then put {{!!maplink}} in the appropriate 
> area of the infobox table. Works like a charm. Whether you directly solve 
> my issue or not, you always get me thinking in the right direction for 
> which I thank you. Highest regards, sir.
>
> Damon
>
> On Wednesday, November 18, 2020 at 9:09:24 PM UTC-7 TW Tones wrote:
>
>> Damon,
>>
>> So as I understand it when you transclude  Infobox it is rendered with 
>> the current tiddler set to the tiddler in which your code snipit is written 
>> unless you take other steps to alter the currentTiddler, this is supported 
>> by the idea that  you subsequently transclude the text field presumable of 
>> the same tiddler.
>>
>> How does Infobox determine the correct map tiddler to link to?
>>
>> A global macro that references a field in the currentTiddler, will adapt 
>> to local content.
>>
>> I do not have enough to help address your specific issues, but best of 
>> luck. Feel free to ask more.
>>
>> Tones
>>
>> On Thursday, 19 November 2020 at 14:27:22 UTC+11 History Buff wrote:
>>
>>> You're right, I forgot to show my code which I now have below:
>>>
>>> 
>>> <$transclude tiddler="Infobox">
>>> 
>>> 
>>>
>>> <$transclude field=text mode=block/>
>>>
>>> I can't have a globally defined map link because each railroad has a 
>>> unique map.
>>>
>>> I misspoke earlier. My infobox stylesheet is being used.
>>>
>>> Damon
>>> On Wednesday, November 18, 2020 at 7:21:12 PM UTC-7 TW Tones wrote:
>>>
 Buff,

 If you place \defines in a tiddler tagged $:/tags/Macro it can be used 
 by name globally, similarly css placed in a tiddler 
 tagged $:/tags/Stylesheet will also be usable globally, this is the 
 approach to use when you want to reuse.

 Remember when using theit 
 assumes tiddler=<>, what is the current tiddler at the 
 time? 
 You do not show how you have coded the click here for map legend, but 
 it sounds like to need to set or reference the correct tiddler.

 I hope this is helping.

 Tones 

 On Thursday, 19 November 2020 at 10:15:33 UTC+11 History Buff wrote:

> Tones,
>
> The aside element worked as long as it was above the transcluded body. 
> The table didn't really work the way I wanted becuase, if the body text 
> was 
> very long, it wouldn't wrap around the infobox.
>
> Now the only issue I have remaining is the map within the infobox. The 
> link to the map is defined with a define statement within the body text, 
> but using the method you outlined above prevents the link from being seen 
> by the infobox. Is there another way I can define the link to the map 
> that 
> would work with your using the ?
>
> On Tuesday, November 17, 2020 at 10:49:44 PM UTC-7 TW Tones wrote:
>
>> Ahhh,
>>
>> Yes

[tw5] Style refresh issue in radio inputs when using a template

[Eskha]

Hello,

I have an issue with style refresh while using RadioWidget in a view 
template element.


I am using Edge - Version 86.

I have defined a style to use for the label of a a radio button input when 
it is selected (by using the "tc-radio-selected"). This is working when I 
directly use the RadioWidget  in a tiddler.
However, if I use the RadioWidget in a tiddler tagged with 
"$:/tags/ViewTemplate", the style is not refreshed unless I edit the 
tiddler or close it then open it again.


Here is a minimal test case with three tiddlers:

title: Test Template
tags: $:/tags/ViewTemplate

<$radio field="test-field" value="Y">Yes
<$radio field="test-field" value="N">No


title: Test CSS
tags: $:/tags/Stylesheet

label.tc-radio-selected {
background-color: #ffc;
}


title: Test

<$radio field="test-field" value="Y">Yes
<$radio field="test-field" value="N">No

My question: How can I fix it?
(Am i doing something wrong? Is-it a widget issue? An internet browser 
issue? à

Best regards,

Eskha

-- 
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/a4ff5a77-97a5-44e1-a063-37ed962ff7d0n%40googlegroups.com.

[tw5] Re: Seeking suggestions for my use case

[soren.b...@gmail.com]

Author of TiddlyRemember here. Si is correct, you don't have to *host your 
wiki *on Node. You just have to have TiddlyWiki's Node version installed on 
your computer, so that TiddlyRemember can process your single-file wiki and 
extract the Anki questions.

On Sunday, November 15, 2020 at 7:25:37 AM UTC-6 Prestige wrote:

> Hello all!
>  First of all, wish you all a happy festive season (as it is here in 
> India). I use TiddlyWiki is for my notes and use ANKI for Spaced 
> repetition. I wanted to put forward my use case, and seek suggestions from 
> anyone and everyone :)
>
> Current Requirement:
>
>1. Multi-Device Access
>   1. Since I use Android and Ipad along with PC, it would be 
>   beneficial if I can read and/or edit my wiki on any of these devices.
>   2. Currently, I use a bulky way to do so. Sync on Github (single 
>   file) -- It doesn't feel feasible as my wiki already going big.
>2. ANKI Sync
>   1. I found that there is a plugin called 'TiddlyRemember' which 
>   seems to fit my use.
>   2. But it needs to TW to be installed on the node and if I do that 
>   I will lose the cross-platform editing capability.
>   3. I am willing to make sync on the PC, but I would love to keep 
>   the multi-device access. I don't know how to work it out.
>3. Export my notes
>   1. I would be great if I could export my tiddlers/notes in some 
>   format like Markdown. 
>   2. Also, if it's possible can I, somehow, make my notes to be 
>   available in my 'tiddlers' folder as markdown files instead of .tids?
>4. Backlinks of course.
>   1. I see that TiddlyResearch uses TiddlyRemember and Backlinking 
>   quite well.  
>   2. Also, there is a plugin someone mentioned here 
>    
> which 
>   can help create cards while annotating!! I couldn't find it yet. But I 
>   wonder if it works with TiddlyResearch?
>5. Free?!
>
>
> From what I can see from my own points above, I basically have problems in 
> setting up Tiddlywiki on Node while making it accessible to all my devices 
> (Maybe through Github).
>
> I will try installing TW on the node with TiddlyResearch and 
> TiddlyRemember and get back here :)
> Please help me if possible to make it cross-platform.
>
> THANKS for reading a rather long post.
>
> Regards,
> Prestige
>
>

-- 
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/53cb42b3-1664-45d4-8bc4-7889816b0cb4n%40googlegroups.com.

[tw5] Re: WikiWords vs Double Brackets

[Jean-Pierre Rivière]

CamelCase is fine, but when you have an acronym in your title, the question 
of how to do starts.

for instance: HistoryOfHTMLBrowser or HistoryOfHtmlBrowser ? The first one 
is more consistant but so many uppercase in a row does not seem very 
Camel-like to me. And the second is nice but has no justification but ease 
of reading (but that's a very good reason indeed).

You have also some problem with apostrophes, although English has few of 
them, French has many. For instance "l'heure et l'habitude" would be 
LHeureEtLHabitude and that's ugly. You could resolve it by a title like 
HeureEtHabitude but this example really show that, as has been told, 
CamelCase is not fit for every purpose, and you have to have an extensive 
naming convention to avoid misspelling.

Also, orthographic corrector are showing a lot of ill-advised red because 
of every camelcase word and you will have a harsh time spotting the true 
errors or would have to clutter your dictionary with all your camels...


Le vendredi 20 novembre 2020 à 16:47:20 UTC+1, Ed Heil a écrit :

> Hey, thanks, all, this is exactly the kind of discussion I was hoping to 
> hear!  It's been very informative, and I've really enjoyed looking at, 
> e.g., Soren's Zettelkasten!
>
>
> On Friday, November 20, 2020 at 5:47:11 AM UTC-5 TiddlyTweeter wrote:
>
>> Ciao Soren
>>
>> On Thursday, 19 November 2020 at 20:53:05 UTC+1 soren.b...@gmail.com 
>> wrote:
>>
>>> I use WikiWords in my Zettelkasten 
>>> . Besides saving a couple of 
>>> keystrokes, I actually like them aesthetically ... 
>>
>> And I think the restrictions in form 
>>>  help 
>>> me come up with concise names for things.
>>
>>
>> Right. I agree. Constraints can be highly productive of good use--when 
>> they match well the users cognitive process.
>> CamelCase is particularly interesting in that *its Semantics & Form 
>> co-incide*. There is no need to add additional [[bracket]] construction 
>> forms that envelope.
>> In that sense CamelCase is: efficient,  meaningful, pretty obvious, 
>> readable & MarkupMinimal.
>>
>> Of course, usage hangs out on more than that. Often CamelCase is not 
>> appropriate, requires too much forethought, won't work for titles etc.
>>
>> But it still has real uses & excellent efficiency in some many use cases.
>>
>> Best wishes
>> TT
>>
>

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

Re: [tw5] accessibility support for links

[Jean-Pierre Rivière]

You're right for external link. Though something like [[label|external 
URL|hint text|language of target]] would be solving nearly all cases.

And, there can be cases where a wiki has pages in several languages, 
meaning that $link would be nice to offer that possibility too. and the 
[[...]] notation would be the very same than above.

As for the hint text, this is also something that may have to be set for 
accessibility reasons.

Le vendredi 20 novembre 2020 à 14:31:43 UTC+1, jeremy...@gmail.com a écrit :

> Hi Jean-Pierre
>
> I am professionally concerned by a11y problems, checking website or 
> webapps for compliance to WCAG rules. Being French, this means following 
> RGAA for me, but this is only a facilitating tool for WCAG.
>
> Whatever. I came upon two points that meant my support tw for RGAA stuff, 
> being in French, should mention that outer links to WCAG stuff be in 
> French. The standards linking doesn't allow for this. I wrote my own macro 
> to elaborated a custom  link. But definitely, if I had to recover all 
> the specifics of the standard linking mechanism, my macro would have been 
> much more complex! So I think the standard markup (or at least the $link 
> widget) should allow for specifying the language of the linked page.
>
> BTW, my (crude!) macro:
>
> \define enLink(label, url) $label$
>
> an example of use (not too much of a hassle to write compared with 
> [[label|url]] indeed):
>
> < https://www.w3.org/TR/wai-aria-practices-1.1/";>>
>
> (where it was shown I didn't need anything else for accessibility 
> requirements for the kind of links I used within my project)
>
>
> The <$link> widget is only used for internal links, which I assume are not 
> covered by the directive?. The usual [ext[link syntax]] or [[
> https://example.com/]] for external links generates an  tag, so the 
> macro you’re using would be the recommended solution for a case like this.
>
> 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+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/0f5fb8b2-a909-4aad-86fe-82666e392adbn%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/c248f724-416d-4622-bf0d-cd7f2d3e7fc4n%40googlegroups.com.

[tw5] Re: WikiWords vs Double Brackets

[Ed Heil]

Hey, thanks, all, this is exactly the kind of discussion I was hoping to 
hear!  It's been very informative, and I've really enjoyed looking at, 
e.g., Soren's Zettelkasten!


On Friday, November 20, 2020 at 5:47:11 AM UTC-5 TiddlyTweeter wrote:

> Ciao Soren
>
> On Thursday, 19 November 2020 at 20:53:05 UTC+1 soren.b...@gmail.com 
> wrote:
>
>> I use WikiWords in my Zettelkasten 
>> . Besides saving a couple of 
>> keystrokes, I actually like them aesthetically ... 
>
> And I think the restrictions in form 
>>  help 
>> me come up with concise names for things.
>
>
> Right. I agree. Constraints can be highly productive of good use--when 
> they match well the users cognitive process.
> CamelCase is particularly interesting in that *its Semantics & Form 
> co-incide*. There is no need to add additional [[bracket]] construction 
> forms that envelope.
> In that sense CamelCase is: efficient,  meaningful, pretty obvious, 
> readable & MarkupMinimal.
>
> Of course, usage hangs out on more than that. Often CamelCase is not 
> appropriate, requires too much forethought, won't work for titles etc.
>
> But it still has real uses & excellent efficiency in some many use cases.
>
> Best wishes
> TT
>

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

[tw5] Re: Minimal tweak: Automatic night mode

[Mohammad]

Beautiful! 

On Friday, November 20, 2020 at 5:45:50 PM UTC+3:30 bimlas wrote:

> To get less contrasting colors, decrease the invert value, e.g. 0.85
>

-- 
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/faa23cf8-7c4f-4ed8-a25b-b8ee09deaf29n%40googlegroups.com.

[tw5] Re: hint messages (help text) in input box

[Eric Shulman]

On Friday, November 20, 2020 at 4:27:52 AM UTC-8 jn.pierr...@gmail.com 
wrote:

> But what were the numbers (42,142,225,24) meaning in my example? (even 
> though I don't have to know it to use it, it's just that I'm curious.)
>

Those numbers define the rectangle where the popup is displayed: 
(left,top,width,height) and are automatically generated by the TWCore 
popup.js code.
(see *$:/core/modules/utils/dom/popup.js*, and search for *popupRect* in 
the *Popup.prototype.show function*)

-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/97b24202-b3b7-479e-8e36-e745674d5d60n%40googlegroups.com.

[tw5] Re: Minimal tweak: Automatic night mode

[bimlas]

To get less contrasting colors, decrease the invert value, e.g. 0.85

-- 
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/84edb902-7229-4bf2-bd90-71996749be6bn%40googlegroups.com.

[tw5] Private and public tiddlers in single-file wiki with tw-receiver

[Anjar]

Hi all, 

I know there has been some discussions on how to manage to have both public 
and private tiddlers, so here is my take on the problem:

If we use tw-receiver as the saving mechanism, we can post-process the html 
file after saving with PHP. The most brutal form would be to simply add

// make a public version
  $doc = new DOMDocument();
  $doc->loadHTML(file_get_contents($destinationfile));
  $selector = new DOMXPath($doc);
  
  // search for private tiddlers
  $result = $selector->query('//div[contains(@tags, "Private")]');
  
  // loop through all private tiddlers
  $titletext = array();
  foreach($result as $item) {
  $titletext[] = $item->getAttribute("title"); //save the title for 
later
  $item->parentNode->removeChild($item); // remove the tiddler
  }
  $str_doc = $doc->saveHTML(); // convert to string
  $str_doc = str_replace($titletext, '%%%', $str_doc); // remove all 
mentions of the private tiddler
  $doc->loadHTML($str_doc); //convert back
  $doc->saveHTMLFile("./public.html"); // save public version

to tw-receiver-server.php (see https://github.com/andjar/tw-receiver). This 
would create a third output file called public.html and remove all the 
tiddlers tagged with Private and also replace all mentions of it with %%% 
(tags, text, links, field etc.). I will try to refine it so that a private 
tiddler called "link" would not mess up all the html link attributes and so 
on. Maybe it would be enough to replace in-text links only (and the 
occurence in the tiddler list in the beginning of the html)?

So one can have an admin wiki protected by basic http auth with drafts and 
so on, and each time one saves, the public version is updated as well. Then 
it may be useful to have the tw-receiver password hard coded so that one 
authentication is enough

Best,
Anders

-- 
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/f31d2d90-29f6-49bc-80e6-f2d4163d10fen%40googlegroups.com.

Re: [tw5] accessibility support for links

[Jeremy Ruston]

Hi Jean-Pierre
> I am professionally concerned by a11y problems, checking website or webapps 
> for compliance to WCAG rules. Being French, this means following RGAA for me, 
> but this is only a facilitating tool for WCAG.
> 
> Whatever. I came upon two points that meant my support tw for RGAA stuff, 
> being in French, should mention that outer links to WCAG stuff be in French. 
> The standards linking doesn't allow for this. I wrote my own macro to 
> elaborated a custom  link. But definitely, if I had to recover all the 
> specifics of the standard linking mechanism, my macro would have been much 
> more complex! So I think the standard markup (or at least the $link widget) 
> should allow for specifying the language of the linked page.
> 
> BTW, my (crude!) macro:
> 
> \define enLink(label, url) $label$
> 
> an example of use (not too much of a hassle to write compared with 
> [[label|url]] indeed):
> 
> < "https://www.w3.org/TR/wai-aria-practices-1.1/";>>
> 
> (where it was shown I didn't need anything else for accessibility 
> requirements for the kind of links I used within my project)

The <$link> widget is only used for internal links, which I assume are not 
covered by the directive?. The usual [ext[link syntax]] or 
[[https://example.com/]] for external links generates an  tag, so the macro 
you’re using would be the recommended solution for a case like this.

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/0f5fb8b2-a909-4aad-86fe-82666e392adbn%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/6800BB20-DA29-4EC7-AD8D-CB0649FC14D0%40gmail.com.

[tw5] Re: The-Book Chapter 10

[Ste]

It was mentioned somewhere on here recently!
https://my-tw-notes.droppages.com/TheBook.pdf

On Thursday, 19 November 2020 at 18:28:25 UTC dieg...@gmail.com wrote:

> Hello! 
>
> Just a re-ping on this project! Does anyone know?
>
> On Saturday, July 25, 2020 at 5:22:51 PM UTC-5 dieg...@gmail.com wrote:
>
>> Hello!
>>
>> I just want to checkup on this wonderful project! Has it been completed?
>>
>> On Wednesday, January 15, 2020 at 2:37:37 AM UTC-6, Luis Gonzalez wrote:
>>>
>>> After the Christmas stop I continue writing The-Book. I think is 
>>> important to include a little chapter with some architectural aspects of 
>>> Tiddlywiki.
>>> The attached pages contains the beginning.I saw the Tiddlywiki Hangout 
>>> 10 to fill the pages.
>>>
>>>
>>> * PLEASE:*
>>>
>>> * All experts in Tiddlywiki, check the table. If there is missing or bad 
>>> information, please tell me.
>>> * What more information do you think should be included in this chapter?
>>>
>>>
>>>
>>>
>>> Thanks for your help.
>>> The-Book keep moving forward.
>>>
>>

-- 
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/68d565b3-bb64-486d-8862-caf217bf69b9n%40googlegroups.com.

[tw5] Re: Google Group New Interface

[Ste]

Yep...you have to go to the menu in the browser and click 'show desktop 
site'

On Thursday, 19 November 2020 at 18:22:43 UTC bimlas wrote:

> I know a thread has already been opened for the new forum somewhere, but I 
> can't find it, so here's one of the big negatives (I think): I can't write 
> a reply on Android because I don't have a button to press!
> Mohammad a következőt írta (2020. október 22., csütörtök, 7:38:45 UTC+2):
>
>> In the new interface we have missed some great features we have got used 
>> to. But it seems the new GG interface has brought some of them back.
>>
>> 1. Mark a post/message as favorite using star button at the right of post 
>> title and then see them under Starred conversation from left side bar
>>
>> 2. Label conversation like tag in previous version. Group admin has 
>> blocked this feature now, but if open you can label a message from top bar
>>
>> 3. To list all message labeled (tagged) say with Bob from left sidebar 
>> click on Labels and then click on Bob 
>>
>> 4. You can organize favorite groups into folder
>>
>

-- 
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/78ca3fe3-b2cc-4e52-ab7f-f0a02586dfaan%40googlegroups.com.

[tw5] Re: [Help] Trying to include my markdown files as tiddlers in my wiki

[Prestige]

Kindly help :)

On Friday, 20 November 2020 at 02:05:30 UTC+5:30 Prestige wrote:

> Anyone?
>
> On Friday, 20 November 2020 at 01:16:48 UTC+5:30 Prestige wrote:
>
>> I was trying to include a folder of .md files as tiddlers into my Wiki, 
>> but I am facing an issue in the name of the tiddler. The tiddler is 
>> imported fine but, the name includes the whole path of the file.
>> This is my tiddlywiki.files file. Can someone tell me what mistake I 
>> might be doing?
>>
>> {
>> "directories": [
>> {
>> "path": "./TheVault",
>> "filesRegExp": "^.*\\.md$",
>> "isTiddlerFile": true,
>> "fields": {
>> "title": {"source": "basename"},
>> "created": {"source": "created"},
>> "modified": {"source": "modified"},
>> "type": "text/x-markdown"
>> }
>> }
>> ]
>> }
>>
>> Thanks
>> Prestige
>>
>

-- 
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/b3ad28fb-18f8-4bf9-ac47-028b76140391n%40googlegroups.com.

[tw5] Re: hint messages (help text) in input box

[Jean-Pierre Rivière]

Very helpful of both you and it!

The $edit-text widget doc is a bit tiny, lacking in example. This one would 
clarify it in a definitive manner for a useful feature.

Thanks again.

But what were the numbers (42,142,225,24) meaning in my example? (even 
though I don't have to know it to use it, it's just that I'm curious.)

Le vendredi 20 novembre 2020 à 12:28:54 UTC+1, Eric Shulman a écrit :

> On Friday, November 20, 2020 at 3:08:36 AM UTC-8 jn.pierr...@gmail.com 
> wrote:
>
>> I was about to write I forgot to mention that the $edit-text widget have 
>> a focusPopup property, which I have not found out how to use. I saw it 
>> apparently required the widget having css class tc-popup-handle. I put my 
>> help in focusPopup, but not directly: I use a tiddler name "grid" where I 
>> specify the help text (as focusPopup needs to be a tiddler title or perhaps 
>> more broadly a tw reference (?)). In my case, the reference was "grid##a3" 
>> for instance and in grid (a simple dictionary) I had "a3: A3" (just to show 
>> what cell you are editing). But when I clicked on the cell, it has the 
>> hidden effect to switch "a3: A3" to something like "a3: (42,142,225,24)".
>>
>
> The focusPopup parameter doesn't specify the *contents* of the desired 
> popup.  Rather, it specifies a "state tiddler" used to control the 
> appearance of a separately-specified popup shown via a $reveal widget.  
> Thus:
>
> <$edit-text tiddler="foo" class="tc-popup-handle" 
> focusPopup="$:/state/popup/something" />
> <$reveal type="popup" state="$:/state/popup/something" 
> class="tc-drop-down">
>this content appears when the edit field has focus
> 
>
> -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/e1cf0c01-fd8e-4b72-b2bc-b8e2c147816bn%40googlegroups.com.

[tw5] Re: hint messages (help text) in input box

[Eric Shulman]

On Friday, November 20, 2020 at 3:08:36 AM UTC-8 jn.pierr...@gmail.com 
wrote:

> I was about to write I forgot to mention that the $edit-text widget have 
> a focusPopup property, which I have not found out how to use. I saw it 
> apparently required the widget having css class tc-popup-handle. I put my 
> help in focusPopup, but not directly: I use a tiddler name "grid" where I 
> specify the help text (as focusPopup needs to be a tiddler title or perhaps 
> more broadly a tw reference (?)). In my case, the reference was "grid##a3" 
> for instance and in grid (a simple dictionary) I had "a3: A3" (just to show 
> what cell you are editing). But when I clicked on the cell, it has the 
> hidden effect to switch "a3: A3" to something like "a3: (42,142,225,24)".
>

The focusPopup parameter doesn't specify the *contents* of the desired 
popup.  Rather, it specifies a "state tiddler" used to control the 
appearance of a separately-specified popup shown via a $reveal widget.  
Thus:

<$edit-text tiddler="foo" class="tc-popup-handle" 
focusPopup="$:/state/popup/something" />
<$reveal type="popup" state="$:/state/popup/something" class="tc-drop-down">
   this content appears when the edit field has focus


-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/893d2af4-3a7b-41f8-b1e1-129aaf59bd89n%40googlegroups.com.

[tw5] Re: Minimal tweak: Automatic night mode

[Mohammad]

Works great! This is really smart solution. I played a little with 
hue-rotate and it is ful :-)

Thank you! 

On Friday, November 20, 2020 at 11:35:02 AM UTC+3:30 bimlas wrote:

> Found another bug (-_-' ) ...
> Change <> to <>

-- 
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/6e751a34-fca7-4175-8b08-87c0d22b56b9n%40googlegroups.com.

[tw5] Re: hint messages (help text) in input box

[Jean-Pierre Rivière]

Really cool and very fast answer indeed THANK YOU

I was about to write I forgot to mention that the $edit-text widget have 
a focusPopup property, which I have not found out how to use. I saw it 
apparently required the widget having css class tc-popup-handle. I put my 
help in focusPopup, but not directly: I use a tiddler name "grid" where I 
specify the help text (as focusPopup needs to be a tiddler title or perhaps 
more broadly a tw reference (?)). In my case, the reference was "grid##a3" 
for instance and in grid (a simple dictionary) I had "a3: A3" (just to show 
what cell you are editing). But when I clicked on the cell, it has the 
hidden effect to switch "a3: A3" to something like "a3: (42,142,225,24)".

While I'm at it, I cannot see any reference for style like tc-popup-handle 
in the standard tw docs. Is there a place to look at for them (apart source 
code and css classes maybe)?

Ads for tool-tips, accessibility rules insists on having some helps for all 
kinds of inputs. Surely input widgets would be better having a title option 
(it's simple and quick, event though it may not be sufficient and then 
popup mechanism already existing would surely bring the solution).

Regards.

Le vendredi 20 novembre 2020 à 11:51:48 UTC+1, Eric Shulman a écrit :

> On Friday, November 20, 2020 at 2:35:33 AM UTC-8 jn.pierr...@gmail.com 
> wrote:
>
>> I'd like to have a help message appear within an input box having the 
>> focus (we call it "bulle d'aide" in French -- Help bubble, literally).
>> I have seen mechanism for popup in tw, but this is not what I want, or 
>> not like that (I don't want to click to make it appear). I would rather 
>> have a standard help text mechanism.
>> a point is, this is not supported by the wiki markup so far.
>>
>
> Most of the input widgets ($edit-text, $checkbox, $radio) widgets don't 
> support a tooltip="..." parameter (note: $select DOES have a tooltip="..." 
> param)
>
> However, as an easy workaround, you can wrap the input widget side a 
>  that specifies a title="..." param, like this:
>
> 
> <$edit-text tiddler="temp" field="foo" />
> 
>
> Note: this method can also be used to add a mouseover tooltip to ANY 
> content, even plain text.  Thus:
>
> This text is before
>  foo baz baz mumble frotz gronk snork 
> snerfle plurm 
> this text is after
>
> 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/b42ed7fc-d30b-44eb-b8d8-084daacd87b4n%40googlegroups.com.

[tw5] Re: hint messages (help text) in input box

[Eric Shulman]

On Friday, November 20, 2020 at 2:35:33 AM UTC-8 jn.pierr...@gmail.com 
wrote:

> I'd like to have a help message appear within an input box having the 
> focus (we call it "bulle d'aide" in French -- Help bubble, literally).
> I have seen mechanism for popup in tw, but this is not what I want, or not 
> like that (I don't want to click to make it appear). I would rather have a 
> standard help text mechanism.
> a point is, this is not supported by the wiki markup so far.
>

Most of the input widgets ($edit-text, $checkbox, $radio) widgets don't 
support a tooltip="..." parameter (note: $select DOES have a tooltip="..." 
param)

However, as an easy workaround, you can wrap the input widget side a  
that specifies a title="..." param, like this:


<$edit-text tiddler="temp" field="foo" />


Note: this method can also be used to add a mouseover tooltip to ANY 
content, even plain text.  Thus:

This text is before
 foo baz baz mumble frotz gronk snork 
snerfle plurm 
this text is after

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/34b0d6a4-5d82-42c2-a6d7-4ab2d77f8139n%40googlegroups.com.

[tw5] accessibility support for links

[Jean-Pierre Rivière]

I am professionally concerned by a11y problems, checking website or webapps 
for compliance to WCAG rules. Being French, this means following RGAA for 
me, but this is only a facilitating tool for WCAG.

Whatever. I came upon two points that meant my support tw for RGAA stuff, 
being in French, should mention that outer links to WCAG stuff be in 
French. The standards linking doesn't allow for this. I wrote my own macro 
to elaborated a custom  link. But definitely, if I had to recover all 
the specifics of the standard linking mechanism, my macro would have been 
much more complex! So I think the standard markup (or at least the $link 
widget) should allow for specifying the language of the linked page.

BTW, my (crude!) macro:

\define enLink(label, url) $label$

an example of use (not too much of a hassle to write compared with 
[[label|url]] indeed):

>

(where it was shown I didn't need anything else for accessibility 
requirements for the kind of links I used within my project)

-- 
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/0f5fb8b2-a909-4aad-86fe-82666e392adbn%40googlegroups.com.

[tw5] Re: WikiWords vs Double Brackets

[TiddlyTweeter]

Ciao Soren

On Thursday, 19 November 2020 at 20:53:05 UTC+1 soren.b...@gmail.com wrote:

> I use WikiWords in my Zettelkasten 
> . Besides saving a couple of 
> keystrokes, I actually like them aesthetically ... 

And I think the restrictions in form 
>  help me 
> come up with concise names for things.


Right. I agree. Constraints can be highly productive of good use--when they 
match well the users cognitive process.
CamelCase is particularly interesting in that *its Semantics & Form 
co-incide*. There is no need to add additional [[bracket]] construction 
forms that envelope.
In that sense CamelCase is: efficient,  meaningful, pretty obvious, 
readable & MarkupMinimal.

Of course, usage hangs out on more than that. Often CamelCase is not 
appropriate, requires too much forethought, won't work for titles etc.

But it still has real uses & excellent efficiency in some many use cases.

Best wishes
TT

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

[tw5] hint messages (help text) in input box

[Jean-Pierre Rivière]

I'd like to have a help message appear within an input box having the focus 
(we call it "bulle d'aide" in French -- Help bubble, literally).

I have seen mechanism for popup in tw, but this is not what I want, or not 
like that (I don't want to click to make it appear). I would rather have a 
standard help text mechanism.

a point is, this is not supported by the wiki markup so far.

-- 
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/a6182329-1bd0-4cfa-a1e4-42bf9c45e1d1n%40googlegroups.com.

[tw5] Re: WikiWords vs Double Brackets

[TiddlyTweeter]

Hans

Good, direct point.

On Thursday, 19 November 2020 at 20:17:34 UTC+1 hww...@gmail.com wrote:

> From the (historical) perspective this links to one entry point to 
> TheOriginalWiki .  WardCunningham 
> is a fine example of the "minimalist" style of programming and CamelCase 
> was a relatively simple way of automatically generating links to the 30k+ 
> pages that evolved there.  It's been locked down for quite a while now but 
> it is quite useful as a reference for those of us that still retain some 
> knowledge of its content.
>

 Right. The Cunningham point was "automation of linking." CamelCase still 
is relevant in TW WHEN it can match a use case on naming well. Spaced 
naming is likely more used, but CamelCase is still highly efficient in 
that, in text body, it CREATES a link, even when its target does not yet 
exist. Clicking on it creates the linked Tiddler if it does not exist. THAT 
behavior makes for very efficient writing.

If you don't use that feature TW config lets you turn off its behaviour. 

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/83e1124b-b032-44de-a2bd-b7da4f307e2en%40googlegroups.com.

[tw5] Re: No-op filter expression

[Jens Odborg]

Use is operator without parameter:  [is[]]

On Thursday, November 19, 2020 at 8:39:01 PM UTC+1 soren.b...@gmail.com 
wrote:

> Is there a best practice for creating a filter step (or entire filter run) 
> that doesn't do anything (passes inputs through to outputs)?
>
> My use case: I'm using the *subfilter* operator where the subfilter is 
> pulled from a temp tiddler controlled by a checkbox. When the checkbox is 
> checked, I want to apply an additional filter; when it's unchecked I want 
> no additional criteria on top of what's already in the filter run before 
> coming to *subfilter*. I tried just leaving the temp tiddler blank, but 
> that causes there to be no results since an empty filter always has no 
> output.
>
> I got it to work using *search[] *for the no-filter condition, but I'm 
> not sure if there's a cleaner way to do this. Instinctively it feels like 
> that could be a bit slow, too, depending on the implementation.
>

-- 
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/daf6e641-a4bc-4484-8ab7-ce5664d584a4n%40googlegroups.com.

[tw5] Re: Minimal tweak: Automatic night mode

[bimlas]

Found another bug (-_-' ) ...
Change <> to <>

-- 
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/1f1b7ca6-03b1-4a30-b523-ac5662f20b04n%40googlegroups.com.