from:"Jeremy Ruston"

[tw5] Re: Change layout (RTL/LTR) when editing tiddler

2023-04-22 Thread Jeremy Ruston

Thanks Amit, Mohammad,

I've created a PR with this change, please let me know how it works for you,

https://github.com/Jermolene/TiddlyWiki5/pull/7409

Best wishes

Jeremy

On Saturday, April 22, 2023 at 5:36:12 AM UTC+1 Mohammad wrote:

> To be seen correctly in Talk. The original post is re-formatted.
>
> found a possible solution, I've modified the `copyStyles` function in
> `$:/core/modules/editor/engines/framed.js`
> by adding `removeProperty('direction')`, it is no longer forces the 
> direction to `ltr`
>
> ```
> FramedEngine.prototype.copyStyles = function() {
> // Copy all styles
> $tw.utils.copyStyles(this.dummyTextArea,this.domNode);
> // Override the ones that should not be set the same as the dummy 
> textarea
> this.domNode.style.display = "block";
> this.domNode.style.width = "100%";
> this.domNode.style.margin = "0";
> // In Chrome setting -webkit-text-fill-color overrides the placeholder 
> text colour
> this.domNode.style["-webkit-text-fill-color"] = "currentcolor";
> this.domNode.style.removeProperty('direction'); /// <-- this will 
> remove the direction:ltr from the editor style
> };
> ```
> On Friday, April 21, 2023 at 11:37:34 PM UTC+3:30 Amit Shady wrote:
>
>> found a possible solution, I've modified the copyStyles function in
>> $:/core/modules/editor/engines/framed.js 
>> by adding removeProperty('direction'), it is no longer forces the 
>> direction to 'ltr'
>> FramedEngine.prototype.copyStyles = function() { // Copy all styles 
>> $tw.utils.copyStyles(this.dummyTextArea,this.domNode); // Override the 
>> ones that should not be set the same as the dummy textarea 
>> this.domNode.style.display 
>> = "block"; this.domNode.style.width = "100%"; this.domNode.style.margin 
>> = "0"; // In Chrome setting -webkit-text-fill-color overrides the 
>> placeholder text colour this.domNode.style["-webkit-text-fill-color"] = 
>> "currentcolor"; this.domNode.style.removeProperty('direction'); /// <-- 
>> this will remove the direction:ltr from the editor style };
>>
>> On Monday, April 17, 2023 at 9:05:29 PM UTC+3 Amit Shady wrote:
>>
>>> Hello,
>>>
>>> I'm facing an issue while editing a tiddler where I'm unable to switch 
>>> between RTL/TLR using the "Control+Shift" shortcut. I have noticed that 
>>> this problem is resolved when I hide the toolbar, but I haven't been able 
>>> to find any solutions to this issue online.
>>>
>>> Can anyone suggest a possible solution to fix this issue?
>>>
>>

-- 
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/995984e0-5150-4c7b-babd-81d383f7a1d2n%40googlegroups.com.

[tw5] Re: [TW5] How to embed a font (using @font-face and data-url)

2023-02-27 Thread Jeremy Ruston

Hi Lin OneTwo,

It isn't necessary to do the base64 encoding manually. Have a look at the 
font embedded in the "Startlight" theme that is accessed via the 
`<>` macro:

https://github.com/Jermolene/TiddlyWiki5/blob/master/themes/tiddlywiki/starlight/styles.tid

Best wishes

Jeremy

On Monday, February 27, 2023 at 4:00:21 PM UTC Lin Onetwo wrote:

> I encode it manually instead:
>
> 1. download the font file, for example, `FiraCode-VF.woff2`
> 2. `base64 
> '/Users/linonetwo/Downloads/Fira_Code_v6.2/woff2/FiraCode-VF.woff2' -o 
> '/Users/linonetwo/Downloads/Fira_Code_v6.2/woff2/FiraCode-VF.woff2.base64.txt'`
>
> as said in 
> https://stackoverflow.com/questions/26867893/converting-and-rendering-web-fonts-to-base64-keep-original-look
> 3. put base64 string in the `
> src: url('data:@file/octet-stream;base64,yourbase64');
>as said in 
> https://stackoverflow.com/questions/35120217/base64-encoded-opentype-font-face-using-data-uri
>
> An example: 
> https://github.com/tiddly-gittly/itonnote-theme/commit/ff75e1ae913d7443d89e7838b10ced8ef4c7e461
> 在2017年10月2日星期一 UTC+8 06:32:39 写道：
>
>> Hi all
>>
>> Like Mario and Josiah I prefer the SVG way. I tried to make the graphics 
>> accessible and translatable too. 
>>
>> So here’s a little plugin to add HarveyBalls to your wikis: 
>> http://tid.li/tw5/plugins.html#%24%3A%2Fplugins%2Ftelmiger%2FHarveyBalls 
>>
>> Make a backup, drag it over, try it and let me know how it goes. Answers 
>> might take some time.
>>
>> Have a good moonshine night!
>> Thomas
>>
>>
>> Am Sonntag, 1. Oktober 2017 11:04:23 UTC+2 schrieb PMario:
>>
>>>
>>> Why don't you implement them as SVGs. It will be much less trouble.  And 
>>> the SVGs should be simple.
>>>
>>> -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/675043ef-988d-47a9-ac8b-7533d050c923n%40googlegroups.com.

Re: [tw5] [TW5] Edit Tiddly Wiki files straight on Google Drive

2023-01-28 Thread Jeremy Ruston

This is a great shame. I’ve copied the text from Joshua's link below:

—
End of TiddlyDrive Support

Thank you for using TiddlyDrive. It was a fun project to make.

Unfortunately I am unable to continue working on the app. I am a self-supported 
developer and cannot keep up with the constant changes in Google's requirements 
and app maintenance. I wish I had the time, but even cave-dwelling programmers 
aren't autotrophs -- we gotta eat.

The app will still be available until Google has fully disabled it. As always, 
though, it is open source, so feel free to create a listing yourself.

—

Best wishes

Jeremy



On 28 Jan 2023, at 07:56, joshua...@gmail.com  wrote:

Sad news, I'm afraid.

https://github.com/tiddlydrive/tiddlydrive.github.io/blob/master/eol_notice.md

On Saturday, January 28, 2023 at 2:09:03 AM UTC+2 FFT wrote:
> Is the developer still working on this project? Thankfully it still works 
> well, except for not displaying the favicon. The problem is if it stops 
> working, I'm toast. Are there other google drive implementations similar in 
> function to TiddlyDrive?
> 
> On Tuesday, September 11, 2018 at 7:06:46 PM UTC-7 Justin Morgan wrote:
>> Hi Joshua,
>> 
>> Do you know if it's possible to display a favicon when using TiddlyDrive? 
>> The favicon I have set will display when I open my wiki locally but when I 
>> open it in GoogleDrive, all I see is the default favicon. It's not exactly a 
>> huge deal but it would be nice to be able to identify my wiki tab more 
>> easily (even if it's just the TW logo). BTW, this is an awesome project and 
>> your work on it is much appreciated.
>> 
>> Thanks!
>> 
>> On Saturday, October 21, 2017 at 11:35:10 AM UTC-4, Joshua Stubbs wrote:
>>> Hi, all.
>>> I made an app that lets one edit TiddlyWiki files saved in your Google 
>>> drive and then saving them back automagically. The page is here 
>>> https://chrome.google.com/webstore/detail/tiddly-drive/oaphhjhbbabdjnpjpiliepphpmnioolo
>>>  but I think you need to add it from the Google Drive web interface.
>>> 
>>> I even added an optional ability to save with ctrl + s hotkeys.
>>> 
>>> I hope you all find it useful. It's open source so all feedback and 
>>> contributions are welcome. I still have to set up some contribution 
>>> guidelines but we'll get there!
>>> 
>>> Kind regards. Joshua.
>>> 
>>> 
>>> 
>>> 


-- 
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/ce0fc1ca-1725-40d9-8645-8f22ace852dan%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/9D609EBC-B57D-4D39-B46F-DADEDC8EA305%40gmail.com.

[tw5] Announcing the release of v5.2.4

2022-12-13 Thread Jeremy Ruston

Cross-posted from 
https://talk.tiddlywiki.org/t/announcing-the-release-of-tiddlywiki-v5-2-4/5459

I’m delighted to announce the release of TiddlyWiki v5.2.4 at:

https://tiddlywiki.com/

Some highlights of the many new features and improvements – see the release 
note for the full list of changes:


   - New Twitter Achivist plugin to import the tweets and associated media 
   from a Twitter Archive as individual tiddlers
   - New Genesiss Widget that allows the dynamic construction of another 
   widget, where the name and attributes of the new widget can be dynamically 
   determined, without needing to be known in advance
   - New filter operators for reading and formatting JSON data: jsonget, 
   jsonindexes, jsontype, jsonextract and format:json
   - Added support for nested macro definitions
   - Updates to using the view template body cascade in the edit preview 
   and when opening tiddlers in new windows
   - Fixed folded tiddlers to ensure that the unfold button is always 
   visible
   - Fixed EditTextWidget to remove the default text “Type the text for the 
   tiddler ‘foo’”
   - Fixed truncated search results on narrow screens
   - Fixed table contents overflow on narrow screens
   - Fixed problem with lazy loading under Node.js deleting tiddler bodies 
   under certain circumstances
   
You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html

For Node.js users, the new version is available on npm at 
https://www.npmjs.com/package/tiddlywiki

As usual, please exercise caution when upgrading, and take care to keep 
backup copies of everything important.

I’d like to thank everyone who has contributed to this release. We’re 
keeping up a decent pace of releases at the moment and it’s great to see so 
many people involved.

Any questions or comments are welcome here, or via GitHub.

-- 
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/9c134474-d47c-4a18-b7e6-6a49b72e7367n%40googlegroups.com.

[tw5] Re: Use Case for Session Storage: Fibonacci Series

2022-12-10 Thread Jeremy Ruston

Great stuff Charlie, really inspired. I hope you will enjoy the new 
possibilities coming in https://github.com/Jermolene/TiddlyWiki5/pull/

Best wishes

Jeremy

On Saturday, December 10, 2022 at 3:43:19 PM UTC cj.v...@gmail.com wrote:

> I find the layout of the code above looks better when viewed in Google 
> Groups 
> .
>
> On Saturday, December 10, 2022 at 11:15:51 AM UTC-4 Charlie Veniot wrote:
>
>> And the TiddlyWiki syntax (no javascript) version: 
>> ```
>> \define fibo(fnmax fni:1 fnm2:0 fnm1:1)
>> <$list filter="[[$fnm2$]match[0]]">
>> F,,$fnm2$,, = $fnm2$
>> F,,$fnm1$,, = $fnm1$
>> 
>> <$vars fni={{{ [[$fni$]add[1]] }}}
>> fn={{{ [[$fnm1$]add[$fnm2$]] }}}>
>> F,,<>,, = <>
>> <$list filter="[[$fnmax$]compare:integer:gt]"><$macrocall 
>> $name=fibo fni=<> fnmax=$fnmax$ fnm2=$fnm1$ fnm1=<>/>
>> 
>> \end
>>
>> <>
>> ```
>> On Saturday, March 12, 2022 at 7:49:42 PM UTC-4 Charlie Veniot wrote:
>>
>>> TiddlyWiki instance available for play: 
>>> https://basicanywheremachine.neocities.org/SessionStorageForVariables.html
>>>
>>> On Saturday, March 12, 2022 at 11:07:54 AM UTC-4 Charlie Veniot wrote:
>>>

 [image: Screenshot 2022-03-12 11.05.36 AM.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/dc9dcc31-6ab8-400a-9ea7-3739da928fe8n%40googlegroups.com.

[tw5] Re: $set possible bug

2022-10-02 Thread Jeremy Ruston

Hi Samir

The syntax "value=<$transclude tiddler=stateColor index={{!!Phase}}>" is 
incorrect. It is not possible to use widgets as the value of attributes of 
other widgets.

Try this using this line instead:

<$set name="thisColor" value={{{ [[stateColor]getindex{!!Phase}] }}}>

Best wishes

Jeremy

On Wednesday, September 28, 2022 at 3:59:41 PM UTC+1 Samir S. wrote:

> Greetings,
>
> I may have discovered a bug related to the $set widget in tiddlywiki 5.2.2
>
> The following code outputs a correct result but the syntax is incorrect 
> (missing > on the $set statement).
>
> <$set name="thisColor" value=<$transclude tiddler=stateColor 
> index={{!!Phase}}>
> <$text text=<> />
> 
>
> the current tiddler has field Phase set to "étude" (index from the data 
> tiddler)
>
> The stateColor is a data tiddler with properties like
> étude: "#FF"
> révision: "#00FF00"
> rattrapage: "#FFC700"
>
> What do you think ?
>

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

Re: [tw5] Re: exporting tiddlers in html or raw?

2022-09-22 Thread Jeremy Ruston

Hi Lucas,

TiddlyWiki's web server only works when running under Node.js, and doesn't 
function in the browser.

The source for the Node.js "render" command shows how to render a tiddler 
through a template to an HTML file:

https://github.com/Jermolene/TiddlyWiki5/blob/51bdf60ee868cbf3943d086caa189c5d280b8f54/core/modules/commands/render.js#L52-L56

Best wishes

Jeremy.

On Wednesday, September 21, 2022 at 6:21:31 PM UTC+1 cj.v...@gmail.com 
wrote:

> Simple Export, a getting started tiddler for creating custom export formats 
> 
>
> On Wednesday, September 21, 2022 at 1:57:37 PM UTC-3 Lucas Szybalski wrote:
>
>> Hello,
>> That works manually.
>> but
>> As I've described in the email, I need it done programmatically. 
>>
>>
>> Thanks
>> Lucas
>>
>>
>> On Tue, Sep 20, 2022 at 3:47 PM Charlie Veniot  wrote:
>>
>>> Hello,
>>>
>>> Have you tried TiddlyWiki's HTML export? (image further below)
>>>
>>> If that doesn't do the trick, what is it that you are looking for? 
>>>
>>> If you want to create your own custom export, give me a couple of 
>>> minutes and I'll post a simple export to get things started.
>>>
>>> On Tuesday, September 20, 2022 at 3:18:43 PM UTC-3 Lucas Szybalski wrote:
>>>
 Hello,
 I wanted to export the tiddlers to html. I was looking for a way how. 

 1. I've noticed that there is some kind of built-in API server. 
 https://tiddlywiki.com/#WebServer%20API

 2. but I can't seem to be able to pull the json file either from there 
 or from my own wiki?
 [image: image.png]


 3. The goals is for me to being able to export either final html like:
 [image: image.png]
 4. or raw:
   
 [image: image.png]
 5. So I can later use a function to convert it to html?


 *I have access to a file as well, so if there is a command line tool 
 that does this, and I can import it from shell or python or node that 
 would 
 be great.*


 6. Am I correctly assuming that below Remarkable will do the job if I'm 
 able to get raw data? 

 (Sample code:
 const { Remarkable } = require('remarkable');
 let md = new Remarkable();

 function constructHtml(req) {
 let text = md.render(req);
 let response = {
 value: text
 }
 return response
 };


 7. I'm getting below when I do get url from python which tells me I'm 
 doing it wrong.
 [image: image.png]


 Thanks
 Lucas

 -- 
>>> 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/7b929afb-242d-4385-904e-2c06c7f7636fn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> http://wwwhww.news/u/cwSNkeLNXf 
>>
>

-- 
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/0e0052dc-a928-4b4c-8e9c-2a1e5546c541n%40googlegroups.com.

[tw5] Re: We invite you to http://wwwhww.news - beta release

2022-08-17 Thread Jeremy Ruston

Hi Lucas,

Congratulations on the new service, it works very smoothly.

For the benefit of others, I should say that Lucas got in touch with me a 
few months ago on LinkedIn, and I was pleased to encourage him.

I think I'm right in pointing out that the requirement to login with 
LinkedIn doesn't involve sharing any information other than your email 
address. It does of course require a LinkedIn account.

Best wishes

Jeremy.

On Wednesday, August 17, 2022 at 5:33:55 PM UTC+1 Lucas Szybalski wrote:

> Hello,
>
> I wanted to invite all tiddlywiki users or new users who are just 
> exploring tiddlywiki or people who want to start using tiddlywiki today. 
> Long story short, we have created a page where you can use the power of 
> tiddlywiki to just write your tidlers, stories, blog, whatever content you 
> want, while removing all the hustle of hosting, setting up. Just login and 
> start writing and sharing. 
>
> We would love for you to try it, and we hope this could be your home 
> moving forward. 
>
> Go to:
> http://wwwhww.news/
> When you login, you will be redirected to your tiddlywiki.
>
> If you want to see a preview you can check out mine @:
> http://wwwhww.news/u/cwSNkeLNXf
>
> PIng me back with any feedback or any other pain points you would like me 
> to solve.
>
> Start writing today. Forward this email to a friend who might be 
> interested.
>
> Thank you
> Lucas Szybalski
> https://www.linkedin.com/in/lucas-szybalski-84b4a097/
>
>

-- 
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/1f0b786e-1b0f-4e5a-9c20-76ab86bf5609n%40googlegroups.com.

[tw5] Announcing the release of TiddlyWiki v5.2.3

2022-08-02 Thread Jeremy Ruston

I’m delighted to announce the release of TiddlyWiki v5.2.3 at:

https://tiddlywiki.com/ 
There are over 60 improvements and fixes in this release. Some highlights:

Improved support for screen readers and other assistive technology
Improved display of stylesheet tiddlers
Checkbox widget improved with support for the indeterminate state and the 
ability to bind to a list field
New “insertafter” operator to match the existing “insertbefore” operator
More hackable rendering of tiddler subtitles
Added support for macro definitions that are scoped to the view template body
Improved palette support for dark mode
KaTeX updated to v0.16

See the release note for the full list of changes.

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html 
For Node.js users, the new version is available on npm:

https://www.npmjs.com/package/tiddlywiki 


As ever, exercise caution when upgrading, and be careful to keep backup copies 
of everything important.

My sincere thanks to everyone who has contributed to this release. It’s only a 
little over four months since the last release, and yet we’ve built up a 
compelling set of improvements.

The plan is that the next release will be v5.3.0 in the light of some 
significant improvements to transclusion that are under development here:

https://github.com/Jermolene/TiddlyWiki5/pull/ 


Any questions or comments are welcome here, or via GitHub.

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/009AC66C-A1F5-4AE9-B0D1-EF6C6CA67795%40gmail.com.

[tw5] Re: Turn off autosave for NodeJS

2022-07-06 Thread Jeremy Ruston

Suppressing synchronisation is not directly supported by the Node.js 
configuration currently. Instead, one can download a standalone snapshot of 
the wiki, modify it offline, and then subsequently import it back into the 
online wiki. This works well with tools like Quine for offline use.

On Wednesday, July 6, 2022 at 11:43:23 AM UTC+1 miket...@gmail.com wrote:

>
> I don't want every change to be saved on the server. Is it possible to 
> make it like a browser plugin? I made many changes and saved all at once. I 
> turned  Autosave  off (Do 
> not save changes automatically) globally in the settings, but the NodeJS 
> server is still updated in real time.

-- 
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/af93aa7e-efbe-40cd-b683-b1eff4c3aa5bn%40googlegroups.com.

Re: [tw5] Substring filter?

2022-05-09 Thread Jeremy Ruston

> It took me a while to find out, but filter operators are basically Javascript 
> only. so for future reference, I wrote a fancy substring operator myself. It 
> is available at
> https://sw-amt.ws/tiddly/tw-substring.html

Funnily enough, we are working on a new PR which allows custom filter operators 
to be defined in wikitext. There are more details here:

https://github.com/Jermolene/TiddlyWiki5/pull/#issuecomment-1119703393 


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/AAF24EA7-79AD-4AAD-88D2-F3FDA3B6A3F7%40gmail.com.

[tw5] Re: [TW5] Esperanto Translation (Alpha)

2022-03-26 Thread Jeremy Ruston

Great stuff Joshua – I hope you'll consider contributing your work to the 
core when you get to a suitable point – we already have a plugin for 
Interlingua, but it would be fitting to also have one for the original 
conlang.

Best wishes

Jeremy

On Saturday, March 26, 2022 at 7:37:17 AM UTC joshua...@gmail.com wrote:

> Thank you for your replies and feedback. It's a good question.
>
> I'm not sure if other languages translate it, but there are several things 
> worth considering: 
>
> *Brand name localisation isn't unheard of.*
>
> I gave the example of Wikipedia in the post. I've also heard that 
> Salvation Army shops are actually branded as Salvos in Australia because 
> that's what the locals call it.
>
> In both cases, the original brand name is still accessible (and not 
> un-recognisably different either).
> *Even if no other language translated TiddlyWiki, the fact that there is a 
> word for Wiki already makes TiddlyWiki feel a lot more stilted.*
>
> TiddlyWiki is a brand, yes, but this is an opportunity to make the brand 
> more living and dynamic.
>
> *It may look strange to non-Esperantists but the great thing is that 
> non-Esperantists will never have to see it. The only people who will see it 
> are the people who recognise it.*
>
> (All the urls, macros and code will still be the same)
>
> *There is a kind of symmetry that is lost if you have a sentence taking 
> about "TiddlyWiki" and then "Vikio".*
>
>
> All that being said, if the Esperantujo ends up preferring against it, we 
> can remove that localisation. I don't feel expectationally passionate about 
> it but I do think it's a nice flair.
>
>
> On Friday, March 25, 2022 at 10:19:03 PM UTC+2 PMario wrote:
>
>> On Friday, March 25, 2022 at 5:33:38 PM UTC+1 Mark S. wrote:
>>
>> Do other languages attempt to translate "TiddlyWiki" ? I would have 
>>> thought that that was a special term that would stay itself in most 
>>> languages.
>>>
>>
>> I'm with Mark here. TiddlyWiki is a "brand" name and shouldn't be 
>> translated.
>> -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/83f47424-ec6a-4949-bcf1-ceb3d6eee356n%40googlegroups.com.

[tw5] Announcing the release of TiddlyWiki v5.2.2

2022-03-25 Thread Jeremy Ruston

I'm delighted to announce the release of TiddlyWiki v5.2.2 at:

https://tiddlywiki.com/

The release is taking place now because of a serious bug affecting Chrome and
Edge versions 100 and 101. The bug makes it impossible to click the edit
toolbar buttons when editing a tiddler with these versions. As far as we can
tell, other functionality is unaffected.

Therefore it is strongly recommended to upgrade any wikis that are expected to
be edited by Chrome or Edge users on those versions.

Besides the fix for the Chrome/Edge issue, there are a number of other exciting
changes:

* An updated highlight plugin with support for more languages
* Fixing a long term bug with the ordering of tagged tiddlers
* A new shorthand syntax for setting CSS style properties
* Extended secondary window support to include positioning new windows, and
closing windows

See the release note for the full list of changes.

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html

For Node.js users, the new version is available on npm:

https://www.npmjs.com/package/tiddlywiki

As ever, exercise caution when upgrading, and be careful to keep backup copies
of everything important.

A huge thank you from me personally to all the contributors to this release who
have given up their time and effort to make things better. There are lots of
small improvements but the cumulative effect is to steadily increase the
flexibility and reliability of TiddlyWiki.

Any questions or comments are welcome here, or via GitHub.

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/686C719A-F15F-4200-A62E-C6E4AC62708B%40gmail.com.

Re: [tw5] New Release Banner Competition for v5.2.2

2022-03-25 Thread Jeremy Ruston

Congratulations Springer, it’s a great design, and as it’s turned out, the 
winner by an overwhelming margin.

It’s a shame to have had to rush the competition again, let’s hope that next 
time we can do it as usual.

Best wishes

Jeremy



> On 23 Mar 2022, at 13:54, springer  wrote:
> 
> 
> Off the cuff, and maybe too soon, but since there aren't many new features:
> 
> 
> 
> If anyone wants to propose a graphic idea for 5.2.2, let me know and I'll 
> post it at https://tw-logo-contest.tiddlyhost.com/ 
> 
> -Springer
> 
> On Wednesday, March 23, 2022 at 9:05:58 AM UTC-4 jeremy...@gmail.com wrote:
> As usual, I’d like to hold a competition to design the banner image that is 
> shown on the splash screen and within the opening HelloThere tiddler.
> 
> However, we find ourselves again in the situation where we have extremely 
> limited time. Due to a serious bug introduced by the next version of Chrome 
> we are trying to get v5.2.2 released in the next few days.
> 
> With that in mind, we’ll have to run the competition slightly differently 
> this time:
> Entries will be accepted until Friday morning at 8am UK time
> To speed things up, we’ll have to eschew voting, and I will once again choose 
> the winning image (I’m open to discussion here!)
> Ideally, the artwork should reflect some of the changes in the new version. 
> I’ve updated the release note for the prerelease:
> 
> https://tiddlywiki.com/ prerelease/
> 
> The other rules/guidelines for the competition are:
> The version number (with the correct punctuation) must be clear and readable 
> even when the banner is shown at a reduced size
> The image must be a PNG or JPEG of exactly 560x315 pixels
> The bottom 46 pixels will be obscured by the banner text “What’s new in 
> 5.2.2” when it is displayed within HelloThere
> The image need not include the word “TiddlyWiki”. The banner image is only 
> used in contexts where it is clear that it is about TiddlyWiki
> Feel free to enter an updated version of artwork that was a runner-up in a 
> previous competition
> Reply to this message with your entry, or any questions
> Please give lots of feedback here to encourage the artists
> Here are the posts about previous artwork competitions:
> 
> v5.2.1 - https://groups.google.com/g/tiddlywiki/c/GU0TPGNMPvw/m/y1SyQk_nAQAJ 
> 
> v5.2.0 - https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ 
> 
> v5.1.23 - https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ 
> 
> v5.1.22 - https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ 
> 
> v5.1.21 - https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ 
> 
> 
> The Chrome bug I was referring to is discussed here:
> 
> https://talk.tiddlywiki.org/t/imminent-release-of-tiddlywiki-v5-2-2-to-address-new-chrome-edge-bug/2829/5
>  
> 
> 
> Best wishes and many thanks,
> 
> 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/ad868177-3432-4f8c-bec5-5f6639d1aeddn%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/ACF27624-FB1D-4573-9309-8D257472EE3C%40gmail.com.

[tw5] New Release Banner Competition for v5.2.2

2022-03-23 Thread Jeremy Ruston

As usual, I’d like to hold a competition to design the banner image that is 
shown on the splash screen and within the opening HelloThere tiddler.

However, we find ourselves again in the situation where we have extremely 
limited time. Due to a serious bug introduced by the next version of Chrome we 
are trying to get v5.2.2 released in the next few days.

With that in mind, we’ll have to run the competition slightly differently this 
time:
Entries will be accepted until Friday morning at 8am UK time
To speed things up, we’ll have to eschew voting, and I will once again choose 
the winning image (I’m open to discussion here!)
Ideally, the artwork should reflect some of the changes in the new version. 
I’ve updated the release note for the prerelease:

https://tiddlywiki.com/prerelease/

The other rules/guidelines for the competition are:
The version number (with the correct punctuation) must be clear and readable 
even when the banner is shown at a reduced size
The image must be a PNG or JPEG of exactly 560x315 pixels
The bottom 46 pixels will be obscured by the banner text “What’s new in 5.2.2” 
when it is displayed within HelloThere
The image need not include the word “TiddlyWiki”. The banner image is only used 
in contexts where it is clear that it is about TiddlyWiki
Feel free to enter an updated version of artwork that was a runner-up in a 
previous competition
Reply to this message with your entry, or any questions
Please give lots of feedback here to encourage the artists
Here are the posts about previous artwork competitions:

v5.2.1 - https://groups.google.com/g/tiddlywiki/c/GU0TPGNMPvw/m/y1SyQk_nAQAJ
v5.2.0 - https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ
v5.1.23 - https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
v5.1.22 - https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
v5.1.21 - https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ

The Chrome bug I was referring to is discussed here:

https://talk.tiddlywiki.org/t/imminent-release-of-tiddlywiki-v5-2-2-to-address-new-chrome-edge-bug/2829/5

Best wishes and many thanks,

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/AE1E6456-55BC-4A84-A64F-0FF8BF8D0F80%40gmail.com.

Re: [tw5] The browser-storage plugin

2022-03-11 Thread Jeremy Ruston

Hi Charlie,

> Then that will be the glaring difference between my work and the plugin.

I still don’t understand what you meant. What is the glaring difference?

> Well, the plugin is really  for the benefit of a TiddlyWiki's owner.  What I 
> am doing is for the benefit of the TiddlyWiki viewers.

Are you referring to your idea of using local storage to transfer data between 
wikis in the same browser?

Best wishes

Jeremy

> 
> Something like that.  It is a moving target ...
> 
> On Friday, March 11, 2022 at 1:09:03 PM UTC-4 jeremy...@gmail.com 
>  wrote:
> 
>> Oh, I mean somebody else's TiddlyWiki putting things in my local storage 
>> without my "yes, I agree" (i.e. "yes, I opt-in") consent.
> 
> That's hard to prevent in general:  HTML pages don't need user permission to 
> write to local storage.
> 
> In the case of the browser-storage plugin, steps are taken to separate the 
> data from wikis on different file URIs (the key names used to store the 
> tiddlers are qualified with the location of the file).
> 
> Best wishes
> 
> Jeremy
> 
> 
>> 
>> On Friday, March 11, 2022 at 1:02:55 PM UTC-4 jeremy...@gmail.com 
>>  wrote:
>> Hi Charlie
>> 
>>> Quite awesome, except for one thing: it is opt-in by default, right?
>> 
>> I'm not sure what you mean. If you referring to the fact that on the demo 
>> that I linked the browser-storage plugin is activated by default, it is 
>> possible to leave it set disabled, and expose a checkbox or something for 
>> the user to enable it for themselves.
>> 
>> Best wishes
>> 
>> Jeremy
>> 
>> 
>>> Within the boundaries of the filter, it is an all-in / all-out option, by 
>>> default all-in for the viewer of that TiddlyWiki ?
>>> 
>>> I cannot stand "opt-in" by default, leaving the user with the manual effort 
>>> of opting out, whatever/wherever/whenever it is.
>>> 
>>> The thing I'm setting up, it is "opt-out" by default, and selective opt-in 
>>> for every little thing a viewer wants.  A manual step that could offer an 
>>> option of full-auto if I ever add that in.
>>> 
>>> If there is a way to do that kind of thing with the plug-in, that would be 
>>> a really wonderful thing to document.
>>> 
>>> On Friday, March 11, 2022 at 12:37:25 PM UTC-4 jeremy...@gmail.com <> wrote:
>>> Out of the box, the browser-storage plugin saves $:/state/ tiddlers (apart 
>>> from $:/state/temp/ tiddlers) and thus most of the UI state. There’s no 
>>> configuration beyond installing the plugin and restarting.
>>> 
>>> To make it save all configuration such as which toolbar buttons are hidden 
>>> would require changing the “save filter” to:
>>> 
>>> [prefix[$:/config/]] [prefix[$:/state/]] -[prefix[$:/state/popup/]]
>>> 
>>> Best wishes
>>> 
>>> Jeremy
>>> 
>>> 
 On 11 Mar 2022, at 13:26, Charlie Veniot > wrote:
 
>>> 
 It would be some nice if somebody put together a video and/or some 
 documentation on how somebody can plop a TiddlyWiki out there on the web, 
 and set it up so that viewers can set their own viewing preferences for 
 that TiddlyWiki, such that every time he/she visits that TiddlyWiki, it 
 always displays with their preferences.
 
 And whenever the author of that TiddlyWiki publishes a new version with 
 updated content, viewers still have their preferences working.
 
 That would be pretty cool.
 
 On Friday, March 11, 2022 at 4:44:31 AM UTC-4 jeremy...@gmail.com 
  wrote:
 Charlie's post on browser storage 
 (https://groups.google.com/g/tiddlywiki/c/l-1YLy0xpJo/m/mreI115qAgAJ 
 ) 
 prompted me to post a reminder about the official browser-storage plugin. 
 Charlie is exploring many interesting use cases for browser storage, but 
 that particular post covers the same functionality as the browser-storage 
 plugin.
 
 The browser-storage plugin automatically writes any modified tiddlers to 
 browser storage. It only writes tiddlers that match a filter, which one 
 can set to [all[]] to save all tiddlers, or something like 
 [prefix[$:/state/]] -[prefix[$:/state/popup/]] to just save state tiddlers.
 
 At startup, the browser-storage plugin reads tiddlers from local storage. 
 Any tiddlers that are identical to those built into the file are deleted 
 from local storage. Once the wiki is up and running, any tiddler changes 
 are written straight to local storage.
 
 To try it out:
 
 Visit 
 https://tiddlywiki.com/editions/full/#%24%3A%2Fplugins%2Ftiddlywiki%2Fbrowser-storage
  
 
 Click on the "settings" tab of the plugin
 Scroll down to the heading "Save Filter", and change it to "[all[]]"
 Create or modify some tiddlers
 Refresh the page
 Observe how the changes are restored
 As discussed in the

Re: [tw5] The browser-storage plugin

2022-03-11 Thread Jeremy Ruston


> Oh, I mean somebody else's TiddlyWiki putting things in my local storage 
> without my "yes, I agree" (i.e. "yes, I opt-in") consent.

That's hard to prevent in general:  HTML pages don't need user permission to 
write to local storage.

In the case of the browser-storage plugin, steps are taken to separate the data 
from wikis on different file URIs (the key names used to store the tiddlers are 
qualified with the location of the file).

Best wishes

Jeremy

> 
>> On Friday, March 11, 2022 at 1:02:55 PM UTC-4 jeremy...@gmail.com wrote:
>> Hi Charlie
>> 
>>> Quite awesome, except for one thing: it is opt-in by default, right?
>> 
>> I'm not sure what you mean. If you referring to the fact that on the demo 
>> that I linked the browser-storage plugin is activated by default, it is 
>> possible to leave it set disabled, and expose a checkbox or something for 
>> the user to enable it for themselves.
>> 
>> Best wishes
>> 
>> Jeremy
>> 
>> 
>>> Within the boundaries of the filter, it is an all-in / all-out option, by 
>>> default all-in for the viewer of that TiddlyWiki ?
>>> 
>>> I cannot stand "opt-in" by default, leaving the user with the manual effort 
>>> of opting out, whatever/wherever/whenever it is.
>>> 
>>> The thing I'm setting up, it is "opt-out" by default, and selective opt-in 
>>> for every little thing a viewer wants.  A manual step that could offer an 
>>> option of full-auto if I ever add that in.
>>> 
>>> If there is a way to do that kind of thing with the plug-in, that would be 
>>> a really wonderful thing to document.
>>> 
 On Friday, March 11, 2022 at 12:37:25 PM UTC-4 jeremy...@gmail.com wrote:
 Out of the box, the browser-storage plugin saves $:/state/ tiddlers (apart 
 from $:/state/temp/ tiddlers) and thus most of the UI state. There’s no 
 configuration beyond installing the plugin and restarting.
 
 To make it save all configuration such as which toolbar buttons are hidden 
 would require changing the “save filter” to:
 
 [prefix[$:/config/]] [prefix[$:/state/]] -[prefix[$:/state/popup/]]
 
 Best wishes
 
 Jeremy
 
>> On 11 Mar 2022, at 13:26, Charlie Veniot  wrote:
>> 
> It would be some nice if somebody put together a video and/or some 
> documentation on how somebody can plop a TiddlyWiki out there on the web, 
> and set it up so that viewers can set their own viewing preferences for 
> that TiddlyWiki, such that every time he/she visits that TiddlyWiki, it 
> always displays with their preferences.
> 
> And whenever the author of that TiddlyWiki publishes a new version with 
> updated content, viewers still have their preferences working.
> 
> That would be pretty cool.
> 
>>> On Friday, March 11, 2022 at 4:44:31 AM UTC-4 jeremy...@gmail.com wrote:
>>> Charlie's post on browser storage 
>>> (https://groups.google.com/g/tiddlywiki/c/l-1YLy0xpJo/m/mreI115qAgAJ) 
>>> prompted me to post a reminder about the official browser-storage 
>>> plugin. Charlie is exploring many interesting use cases for browser 
>>> storage, but that particular post covers the same functionality as the 
>>> browser-storage plugin.
>>> 
>>> The browser-storage plugin automatically writes any modified tiddlers 
>>> to browser storage. It only writes tiddlers that match a filter, which 
>>> one can set to [all[]] to save all tiddlers, or something like 
>>> [prefix[$:/state/]] -[prefix[$:/state/popup/]] to just save state 
>>> tiddlers.
>>> 
>>> At startup, the browser-storage plugin reads tiddlers from local 
>>> storage. Any tiddlers that are identical to those built into the file 
>>> are deleted from local storage. Once the wiki is up and running, any 
>>> tiddler changes are written straight to local storage.
>>> 
>>> To try it out:
>>> 
>>> Visit 
>>> https://tiddlywiki.com/editions/full/#%24%3A%2Fplugins%2Ftiddlywiki%2Fbrowser-storage
>>> Click on the "settings" tab of the plugin
>>> Scroll down to the heading "Save Filter", and change it to "[all[]]"
>>> Create or modify some tiddlers
>>> Refresh the page
>>> Observe how the changes are restored
>>> As discussed in the plugin readme, there are some gotchas with browser 
>>> storage, but it can still be useful in many situations.
>>> 
>>> 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/a96db56b-045c-43ab-8fd3-47fbaf130464n%40googlegroups.com.
 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "TiddlyWiki"

Re: [tw5] The browser-storage plugin

2022-03-11 Thread Jeremy Ruston

Hi Charlie

> Quite awesome, except for one thing: it is opt-in by default, right?

I'm not sure what you mean. If you referring to the fact that on the demo that 
I linked the browser-storage plugin is activated by default, it is possible to 
leave it set disabled, and expose a checkbox or something for the user to 
enable it for themselves.

Best wishes

Jeremy

> Within the boundaries of the filter, it is an all-in / all-out option, by 
> default all-in for the viewer of that TiddlyWiki ?
> 
> I cannot stand "opt-in" by default, leaving the user with the manual effort 
> of opting out, whatever/wherever/whenever it is.
> 
> The thing I'm setting up, it is "opt-out" by default, and selective opt-in 
> for every little thing a viewer wants.  A manual step that could offer an 
> option of full-auto if I ever add that in.
> 
> If there is a way to do that kind of thing with the plug-in, that would be a 
> really wonderful thing to document.
> 
>> On Friday, March 11, 2022 at 12:37:25 PM UTC-4 jeremy...@gmail.com wrote:
>> Out of the box, the browser-storage plugin saves $:/state/ tiddlers (apart 
>> from $:/state/temp/ tiddlers) and thus most of the UI state. There’s no 
>> configuration beyond installing the plugin and restarting.
>> 
>> To make it save all configuration such as which toolbar buttons are hidden 
>> would require changing the “save filter” to:
>> 
>> [prefix[$:/config/]] [prefix[$:/state/]] -[prefix[$:/state/popup/]]
>> 
>> Best wishes
>> 
>> Jeremy
>> 
 On 11 Mar 2022, at 13:26, Charlie Veniot  wrote:
 
>>> It would be some nice if somebody put together a video and/or some 
>>> documentation on how somebody can plop a TiddlyWiki out there on the web, 
>>> and set it up so that viewers can set their own viewing preferences for 
>>> that TiddlyWiki, such that every time he/she visits that TiddlyWiki, it 
>>> always displays with their preferences.
>>> 
>>> And whenever the author of that TiddlyWiki publishes a new version with 
>>> updated content, viewers still have their preferences working.
>>> 
>>> That would be pretty cool.
>>> 
> On Friday, March 11, 2022 at 4:44:31 AM UTC-4 jeremy...@gmail.com wrote:
> Charlie's post on browser storage 
> (https://groups.google.com/g/tiddlywiki/c/l-1YLy0xpJo/m/mreI115qAgAJ) 
> prompted me to post a reminder about the official browser-storage plugin. 
> Charlie is exploring many interesting use cases for browser storage, but 
> that particular post covers the same functionality as the browser-storage 
> plugin.
> 
> The browser-storage plugin automatically writes any modified tiddlers to 
> browser storage. It only writes tiddlers that match a filter, which one 
> can set to [all[]] to save all tiddlers, or something like 
> [prefix[$:/state/]] -[prefix[$:/state/popup/]] to just save state 
> tiddlers.
> 
> At startup, the browser-storage plugin reads tiddlers from local storage. 
> Any tiddlers that are identical to those built into the file are deleted 
> from local storage. Once the wiki is up and running, any tiddler changes 
> are written straight to local storage.
> 
> To try it out:
> 
> Visit 
> https://tiddlywiki.com/editions/full/#%24%3A%2Fplugins%2Ftiddlywiki%2Fbrowser-storage
> Click on the "settings" tab of the plugin
> Scroll down to the heading "Save Filter", and change it to "[all[]]"
> Create or modify some tiddlers
> Refresh the page
> Observe how the changes are restored
> As discussed in the plugin readme, there are some gotchas with browser 
> storage, but it can still be useful in many situations.
> 
> 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/a96db56b-045c-43ab-8fd3-47fbaf130464n%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/edeb8fc7-33b4-49fc-a99e-960244fc18a7n%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/32244625-9DBF-47DC-88FC-C61A249F81FD%40gmail.com.

Re: [tw5] The browser-storage plugin

2022-03-11 Thread Jeremy Ruston

Out of the box, the browser-storage plugin saves $:/state/ tiddlers (apart from 
$:/state/temp/ tiddlers) and thus most of the UI state. There’s no 
configuration beyond installing the plugin and restarting.

To make it save all configuration such as which toolbar buttons are hidden 
would require changing the “save filter” to:

[prefix[$:/config/]] [prefix[$:/state/]] -[prefix[$:/state/popup/]]

Best wishes

Jeremy

> On 11 Mar 2022, at 13:26, Charlie Veniot  wrote:
> 
> It would be some nice if somebody put together a video and/or some 
> documentation on how somebody can plop a TiddlyWiki out there on the web, and 
> set it up so that viewers can set their own viewing preferences for that 
> TiddlyWiki, such that every time he/she visits that TiddlyWiki, it always 
> displays with their preferences.
> 
> And whenever the author of that TiddlyWiki publishes a new version with 
> updated content, viewers still have their preferences working.
> 
> That would be pretty cool.
> 
> On Friday, March 11, 2022 at 4:44:31 AM UTC-4 jeremy...@gmail.com wrote:
> Charlie's post on browser storage 
> (https://groups.google.com/g/tiddlywiki/c/l-1YLy0xpJo/m/mreI115qAgAJ 
> ) 
> prompted me to post a reminder about the official browser-storage plugin. 
> Charlie is exploring many interesting use cases for browser storage, but that 
> particular post covers the same functionality as the browser-storage plugin.
> 
> The browser-storage plugin automatically writes any modified tiddlers to 
> browser storage. It only writes tiddlers that match a filter, which one can 
> set to [all[]] to save all tiddlers, or something like [prefix[$:/state/]] 
> -[prefix[$:/state/popup/]] to just save state tiddlers.
> 
> At startup, the browser-storage plugin reads tiddlers from local storage. Any 
> tiddlers that are identical to those built into the file are deleted from 
> local storage. Once the wiki is up and running, any tiddler changes are 
> written straight to local storage.
> 
> To try it out:
> 
> Visit 
> https://tiddlywiki.com/editions/full/#%24%3A%2Fplugins%2Ftiddlywiki%2Fbrowser-storage
>  
> 
> Click on the "settings" tab of the plugin
> Scroll down to the heading "Save Filter", and change it to "[all[]]"
> Create or modify some tiddlers
> Refresh the page
> Observe how the changes are restored
> As discussed in the plugin readme, there are some gotchas with browser 
> storage, but it can still be useful in many situations.
> 
> 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/a96db56b-045c-43ab-8fd3-47fbaf130464n%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/CDD28F05-4FB1-4254-84ED-FF54694AFBFA%40gmail.com.

[tw5] The browser-storage plugin

2022-03-11 Thread Jeremy Ruston

Charlie's post on browser storage
(https://groups.google.com/g/tiddlywiki/c/l-1YLy0xpJo/m/mreI115qAgAJ) prompted
me to post a reminder about the official browser-storage plugin. Charlie is
exploring many interesting use cases for browser storage, but that particular
post covers the same functionality as the browser-storage plugin.

The browser-storage plugin automatically writes any modified tiddlers to
browser storage. It only writes tiddlers that match a filter, which one can set
to [all[]] to save all tiddlers, or something like [prefix[$:/state/]]
-[prefix[$:/state/popup/]] to just save state tiddlers.

At startup, the browser-storage plugin reads tiddlers from local storage. Any
tiddlers that are identical to those built into the file are deleted from local
storage. Once the wiki is up and running, any tiddler changes are written
straight to local storage.

To try it out:

Visit
https://tiddlywiki.com/editions/full/#%24%3A%2Fplugins%2Ftiddlywiki%2Fbrowser-storage
Click on the "settings" tab of the plugin
Scroll down to the heading "Save Filter", and change it to "[all[]]"
Create or modify some tiddlers
Refresh the page
Observe how the changes are restored
As discussed in the plugin readme, there are some gotchas with browser storage,
but it can still be useful in many situations.

Best wishes

Jeremy.

Re: [tw5] Re: Dynamically modifying core tiddlers

2022-03-07 Thread Jeremy Ruston

Hi dam
> 
> Well, I've just seen that accessing the original shadows is possible using 
> the subtiddler attribute of the set widget. If there are also other ways, 
> please let me know. Automatizing the alert and diff log could be an idea for 
> a plugin, if there are none already doing the same thing.

You can also access subtiddlers directly with the view and transclude widgets. 
There's also a "subtiddlerfields" filter operator for reading the names of 
fields within a subtiddler.

Best wishes

Jeremy

> Thank you,
> dam
> 
>> On Sunday, March 6, 2022 at 4:21:52 PM UTC+1 damscal wrote:
>> Thank you very much Mario and Jeremy. I have proposed the additional cascade 
>> on github, hopefully it can be implemented in one of the future upgrades.
>> 
>> Coming back to the main topic, is there a standard way to 
>> reference/transclude a shadow tiddler that was replaced by a standard 
>> tiddler?
>> This would make possible overwriting a shadow tiddler with a standard 
>> tiddler that is dynamically derived from the shadow itself, even after a 
>> plugin upgrade.
>> 
>> Example:
>> user overwrites the shadow $:/plugin/some-tiddler with a standard tiddler of 
>> the same title
>> the original shadow tiddler can be accessed/referenced  with the title 
>> $:/plugin/some-tiddler/overwritten (or an equivalent way)
>> the user can write wikitext inside $:/plugin/some-tiddler which references 
>> $:/plugin/some-tiddler/overwritten , e.g. through something like {{{ 
>> [{$:/plugin/some-tiddler/overwritten}search-replace["text to 
>> replace"],["replace with this"]] }}}
>> when there is a plugin upgrade,  $:/plugin/some-tiddler/overwritten gets 
>> automatically updated. If the new version is different, a log reminds the 
>> user to review the diff to check that things aren't broken.
>> if the plugin upgrade makes the customisation obsolete, the user can simply 
>> delete  $:/plugin/some-tiddler
>> Thank you all,
>> Dam
>> 
>>> On Sunday, February 27, 2022 at 4:49:45 PM UTC+1 jeremy...@gmail.com wrote:
>>> Hi damscal
>>> 
>>> It's a good idea. The best way forward might be to propose a core change to 
>>> introduce an additional cascade for the template used to display the 
>>> content of a tag pill, so that users can have tags with custom appearances.
>>> 
>>> But to answer your question directly, there is no standardised way to 
>>> modify core templates without breaking subsequent upgrades. We try to 
>>> introduce mechanisms for common use cases to avoid modifying templates 
>>> directly, but it's still the last resort for people wanting to do 
>>> particularly intricate customisations.
>>> 
>>> Best wishes
>>> 
>>> Jeremy
>>> 
 On Sunday, February 27, 2022 at 3:33:26 PM UTC PMario wrote:
 Hi,
 If you would be a bit more specific, what you want to do exactly, it may 
 be possible to provide some pointers. ... May be your ideas are also 
 suitable to improve the core UI in a generic way. .. If so .. It may be 
 possible to implement some new stuff directly into the core. .
 -mario
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/c9a24c52-f8f5-4626-bada-b7909fa0c8a4n%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/DD66DA67-E1DD-4AE1-AB1D-8147C50D9793%40gmail.com.

[tw5] Re: Dynamically modifying core tiddlers

2022-02-27 Thread Jeremy Ruston

Hi damscal

It's a good idea. The best way forward might be to propose a core change to 
introduce an additional cascade for the template used to display the 
content of a tag pill, so that users can have tags with custom appearances.

But to answer your question directly, there is no standardised way to 
modify core templates without breaking subsequent upgrades. We try to 
introduce mechanisms for common use cases to avoid modifying templates 
directly, but it's still the last resort for people wanting to do 
particularly intricate customisations.

Best wishes

Jeremy

On Sunday, February 27, 2022 at 3:33:26 PM UTC PMario wrote:

> Hi,
> If you would be a bit more specific, *what* you want to do exactly, it 
> may be possible to provide some pointers. ... May be your ideas are also 
> suitable to improve the core UI in a generic way. .. If so .. It may be 
> possible to implement some new stuff directly into the core. .
> -mario
>

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

Re: [tw5] Major updates to Chromium native file system saver plugin

2022-02-20 Thread Jeremy Ruston

Hi Brian,

> I seem to recall https://tiddlywiki.fission.app/ 
>  implements such a launcher,

That’s right. TiddlyDesktop also has a similar architecture. The challenge with 
Fission is that images stored in ones Fission drive are not accessible via a 
URL; there’s just a JS API to retrieve specific files. I have experimented with 
using a service worker to map local URLs to the JS API, which I think might be 
a promising generic technique for working with non-URL-based storage.

> but currently that page has an endlessly spinning "Authorizing with fission" 
> message and the console has an "Uncaught (in promise) Error: Improperly 
> formatted header value: skeleton" in webnative.js, so I couldn't confirm my 
> memory.

I hope to be able to work on TiddlyWiki on Fission soon, and will make an 
update to the latest version of the SDK.

Best wishes

Jeremy

> I think the workflow implemented by the above two apps is "safer" than what I 
> saw in the TW chromium native file saver. With the TW native saver the 
> workflow looks like this:
> Load my native saver enabled TW using some url (possibly a file:// url)
> Click the Save button in HTML Native File System Saver modal
> From the file dialog select the same file I'm already editing
> Dialog box "a file with this name already exists, do you want to replace it?"
> Start sweating a little bit...if I've chosen the wrong file here, I might be 
> overwriting something important
> Sweat a little bit more especially if I've loaded it from a web url where it 
> isn't as easy to tell that I've selected the matching file or not
> Cross my fingers, click the "replace" button and hope for the best
> The bangle and diagrams.net  applications don't have 
> the same room for user error since you are prompted for what file to read and 
> then it automatically saves back to that same file. I find that workflow to 
> be less nerve-wracking.
> 
> Maybe with tiddlywiki's unique structure there is an even better workflow to 
> be had, I don't know. And maybe the TW nativesaver can already be used with a 
> better workflow and I just missed it.
>  
> On Fri, 18 Feb 2022 at 20:13, TW Tones  > wrote:
> Folks,
> 
> I believe this is already available on tiddlywiki.com 
>  at 
> https://tiddlywiki.com/#Saving%20on%20Browser%20with%20File%20System%20Access%20API
>  
> 
> 
> It is not yet comprehensively documented and it is hard for me to determine 
> what level of functionality and customisation is available to us. As a 
> solution only on Chromium browsers it is not yet global in application, so 
> understanding its value is even harder to determine.
> 
> I also ask myself "We require a click event to start the save dialogue" if 
> this could not be placed in a save button "lookalike" or another way to make 
> it user friendly. Ie just in time, not startup, Although in this thread 
> others suggest they do not need it.
> 
> Can someone write a user designer perspective and/or comparison with existing 
> methods?
> 
> My concerns;
> How to design online tiddlywikis with a non-intrusive saving mechanism users 
> can understand.
> Dealing with the contention possible with two parties editing the same site.
> I would appreciate it is someone can spell this out a little more for us who 
> need it, and can't easily understand this from the jargon and reading between 
> the lines in this discussion.
> 
> Thanks
> Tones
> On Wednesday, 9 February 2022 at 11:10:40 UTC+11 PMario wrote:
> Hi,
> I do like that option. 
> -mario
> 
> On Wednesday, February 9, 2022 at 12:11:06 AM UTC+1 dyllon...@gmail.com <> 
> wrote:
> It does work, though I think it is disruptive asking as soon as something is 
> done which triggers autosave. However, I have put in an option with version 
> 0.7.1 to disable the modal for those who don't like it.
> 
> On Sunday, February 6, 2022 at 1:46:16 AM UTC-8 PMario wrote:
> On Sunday, February 6, 2022 at 12:54:25 AM UTC+1 brian@gmail.com <> wrote:
> ...
> Now with the indexdb entry re-populated, the sequence looks like this:
> Reload the TW page
> Click the + button to create a new tiddler
> Click the checkmark to save the tiddler
> A dialog box asks me if I want to let the site edit the file. I click the 
> "edit file" button
> The file saves
> So it is working for me even without the settings modal. Do you see this same 
> behavior?
> 
> I also think the modal isn't needed. The API requires user interaction. ... 
> But I think the described behaviour is good. The permission is requested, 
> when the first save happens. Since this save is a user interaction it should 
> be good enough.
> 
> -mario
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit 
>

[tw5] Switching to https://talk.tiddlywiki.org

2022-01-31 Thread Jeremy Ruston

We started the new Discourse-based discussion forum at
https://talk.tiddlywiki.org/ in the middle of August.

We labelled as an experiment for several reasons.

First, it was new territory for the project to be hosting its own
infrastructure, and we would need arrangements to ensure a reliable service
with regular backups etc.

Secondly, while there were lots of complaints about Google Groups, we were all
accustomed to it, and any switch would be disruptive and risked alienating or
losing users.

As it's turned out, the reaction to the experiment has been somewhat polarised.
While many users are enthusiastically embracing talk.tiddlywiki.org there is a
significant group that have given clear feedback that they prefer the old
Google Group system.

So, it seems to me that the best way to proceed is to continue to operate both
forums. The Google Group is of course operationally free of charge for us, and
only requires very light intervention from administrators.

The tricky question is which forum should be the official forum for
announcements etc. I propose to fudge that for the moment, and just continue to
post announcements to both forums. It may not be sustainable to do that
forever, but it seems reasonable for us to move cautiously and gather feedback
when we can.

I have made two small changes to mark this transition:

1. Updated https://tiddlywiki.com/#Forums to link to talk.tiddlywiki.org
2. Updated the welcome text for this group to include a note that "the official
community forum is now talk.tiddlywiki.org – please consider posting there to
reach a more active audience."

I'd like to thank Boris Mann who set up the Discourse instance for us, and the
administrator team.

The new forum costs a small amount of money every month to keep it running. Our
goal is to cover those costs via contributions to the Open Collective platform.
It’s working well so far:

https://opencollective.com/tiddlywikidotorg

Best wishes

Jeremy.

Re: [tw5] Static render suppress URI encode

2022-01-25 Thread Jeremy Ruston

Hi Tristran

The templates that we use in the core for static rendering generally include a 
definition of `tv-wikilink-template` at the top of the template. For example, 
$:/core/templates/static.tiddler.html starts with the following line:

\define tv-wikilink-template() $uri_doubleencoded$.html

If you’re using a custom template then you can modify that declaration 
according to the instructions here:

https://tiddlywiki.com/#tv-wikilink-template%20Variable

Alternatively, you can omit the definition from the template and instead 
specify the variable as part of the render command.

Best wishes

Jeremy



> On 25 Jan 2022, at 15:31, Tristan  wrote:
> 
> 
> Unfortunately I was not able to figure out how to influence the filename 
> generation. My custom HTML template does not create anything other than the 
> content. I could not find where in the saving process Tiddlywiki messes with 
> my filenames so I could stop it and have it create a nested folder structure 
> as intended.
> 
> Does anyone use TW as I static site generator and willing to chip in?
> On Sunday, January 16, 2022 at 10:24:02 AM UTC Tristan wrote:
> To make prettier permalinks for my setup and making the URL hackable I 
> changed my render command. All files do get created but internal links are 
> still URI encoded and therefore do no longer work:
> 
> tiddlywiki . --render "[!is[system]]" "" "text/plain" 
> "$:/core/templates/static.tiddler.html" --render 
> "$:/core/templates/static.template.css" "static.css" "text/plain"
> 
> Tiddler 2022/010 results in a file 010.html inside 2022. But all links still 
> use default 2022%252F010%252F0.html which breaks all internal links. I think 
> I have to modify tv-wikilink-template in  
> $:/core/templates/static.tiddler.html but how?
> 
> -- 
> 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/426bee7b-b0bf-481a-a637-d7c7c2259c83n%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/0F2EC858-6C4F-47BF-A9C3-A4AD9E811042%40gmail.com.

Re: [Talk TW] [Google Group (Read Only)] [tw5] dynamically building a string by concatenation in a macro

2022-01-23 Thread Jeremy Ruston

My reply used the jargon because I was being brief.

It's really not as irregular as it appears; it's largely a matter of ones terms 
of reference. It's like the difference between an expression and a string 
literal `a=b+c` and `a="b+c"`, if you're familiar with programming languages.

A simple tranclusion like the following works in two distinct steps: first, it 
retrieves the text of the tiddler "foobar", and then it recursively processes 
the retrieved text as if it had appeared in the same place as the transclusion. 
This deals with any wikitext within it.

```
{{foobar}}
```

In the case of using a transclusion as an attribute we get the same actions: it 
retrieves the text of the transcluded tiddler and then treats the text as if it 
had appeared in the same place as the transclusion, which means that it is 
treated as a literal string.

```

```

Best wishes

Jeremy



--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 23 Jan 2022, at 12:32, CarloGgi via Talk TW  
> wrote:
> 
> 
> @jeremy thanks for the clarification. So it seems that you can correctly (in 
> the sense of *syntactically* correct) use a macro call as argument of a 
> widget attribute, but functionally fail to have it work as intended. This 
> shows clearly that TW is way too much stuffed with booby-traps and something 
> must be definitely done to make coding easier and safer for the average user. 
> 
> We need a stricter syntax, even at the expense of flexibility, to spare the 
> user from these pitfalls, and we need debugging tools to make him easily 
> single out the problem when syntax doesn't help. We cannot go on relying on 
> knowledge of how the parser and 'wikifier' behaves, it simply cannot be 
> viable if TW is to become widely used as is everybody's wish.
> I'm not a complete beginner in programming, and as a matter of fact I spend 
> 50% of coding time trying to debug obscure malfunctioning that mostly turns 
> out to require a developer-level knowledge of the parser to be worked out: I 
> dare say that this scares away a lot of would-be users after the first, 
> frustrating attempts.
> 
> In the meantime that TW morphs to something less tricky, a huge effort should 
> be done IMHO in bettering the documentation so that the user is aware of the 
> pitfalls left open by its syntax.
> 
> Thanks and regards,
> CG
> 
>> On Saturday, January 22, 2022 at 11:05:03 PM UTC+2 jeremy...@gmail.com wrote:
>> Hi Charlie
>> 
>>> I often say "first things first, consider upgrading", but 5.2.1 has the 
>>> same issue.  So I say stick with what you have if it is working no-worse 
>>> than the latest.
>> 
>> The problem is that the OP is using the macro "templatename" as an attribute 
>> value in the `<$action-createtiddler>` widget, which means that wikitext 
>> content will not be processed ("wikified"), so the transclusion in the macro 
>> is ignored.
>> 
>> The workaround is to use textual substitution within the macro (in other 
>> words the $param$ and $(var)$ syntax).
>> 
>>> As for bug-reporting, that, to me, is a crappy process that needs some 
>>> tender loving care, including a need to update the related circa 2014 
>>> documentation (ReportingBugs).
>> 
>> "Crappy"?
>> 
>> It would be more helpful to explain the specific problems you see, and 
>> perhaps suggest improvements.
>> 
>> Best wishes
>> 
>> Jeremy
>> 
>> 
>>> 
>>> Rock'n roll !
>>> 
>>> 
>>> 
>>> 
>>> 
>>>>> On Saturday, January 22, 2022 at 4:31:45 PM UTC-4 CarloGgi wrote:
>>>>> It worked like a charm, thanks! 
>>>>> If it is really a bug, is there a dedicated place to submit it for 
>>>>> analysis?
>>>>> 
>>>>> My TW version is 5.2.0
>>>>> 
>>>>> Thanks again and regards,
>>>>> CG
>>>>> 
>>>>>> On Saturday, January 22, 2022 at 9:57:46 PM UTC+2 cj.v...@gmail.com 
>>>>>> wrote:
>>>>>> TiddlyTalk is a pain.  Let me try pasting that code again so that it 
>>>>>> shows okay over there.
>>>>>> 
>>>>>> ```
>>>>>> <$button>
>>>>>>  <$action-createtiddler
>>>>>>  $basetitle="testTiddler"
>>>>>>  $template={{{ [[BASENAME-]addsuffix{!!grammar_class}] 
>>>>>> }}} >
>>>>>> 
>>>>>>

Re: [tw5] Re: dynamically building a string by concatenation in a macro

2022-01-22 Thread Jeremy Ruston

Hi Charlie

> I often say "first things first, consider upgrading", but 5.2.1 has the same 
> issue.  So I say stick with what you have if it is working no-worse than the 
> latest.

The problem is that the OP is using the macro "templatename" as an attribute 
value in the `<$action-createtiddler>` widget, which means that wikitext 
content will not be processed ("wikified"), so the transclusion in the macro is 
ignored.

The workaround is to use textual substitution within the macro (in other words 
the $param$ and $(var)$ syntax).

> As for bug-reporting, that, to me, is a crappy process that needs some tender 
> loving care, including a need to update the related circa 2014 documentation 
> (ReportingBugs).

"Crappy"?

It would be more helpful to explain the specific problems you see, and perhaps 
suggest improvements.

Best wishes

Jeremy

> 
> Rock'n roll !
> 
> 
> 
> 
> 
>> On Saturday, January 22, 2022 at 4:31:45 PM UTC-4 CarloGgi wrote:
>> It worked like a charm, thanks! 
>> If it is really a bug, is there a dedicated place to submit it for analysis?
>> 
>> My TW version is 5.2.0
>> 
>> Thanks again and regards,
>> CG
>> 
>>> On Saturday, January 22, 2022 at 9:57:46 PM UTC+2 cj.v...@gmail.com wrote:
>>> TiddlyTalk is a pain.  Let me try pasting that code again so that it shows 
>>> okay over there.
>>> 
>>> ```
>>> <$button>
>>>  <$action-createtiddler
>>>  $basetitle="testTiddler"
>>>  $template={{{ [[BASENAME-]addsuffix{!!grammar_class}] }}} >
>>> 
>>>  <$action-navigate $to=<>/>
>>>  
>>>  create new test tiddler
>>> 
>>> ```
>>> 
 On Saturday, January 22, 2022 at 3:53:48 PM UTC-4 Charlie Veniot wrote:
 I'm thinking you found a bug related to how the action-createtiddler 
 handles the $template parameter.
 
 In the meantime (i.e. until there is a fix or somebody can explain this 
 "feature" going on) ...
 
 The following seems to work A-1 for me in my testing (ignore the "pre" 
 tags):
 
 
 <$button>
  <$action-createtiddler
  $basetitle="testTiddler"
  $template={{{ [[BASENAME-]addsuffix{!!grammar_class}] }}} 
 >
 
  <$action-navigate $to=<>/>
  
  create new test tiddler
 
 
 
> On Saturday, January 22, 2022 at 2:07:59 PM UTC-4 CarloGgi wrote:
> hallo folks,
> i need to feed the $template parameter of an <$action-createtiddler> 
> widget with the correct template tiddler's name. The latter has a fixed 
> part 'BASENAME' and a parameterized (or variable) suffix, which is 
> choosen by means of a <$select> input. The idea is to have a macro build 
> the full name based on the choice made by using <$select>, like in:
> 
> \define templatename() BASENAME-{{!!grammar_class}}
> 
> the suffix, as you can imagine, is taken from field grammar_class which 
> is set by the <$select> widget control.
> 
> Now one would expect that things would work nice and easy writing this 
> code:
> 
> <$button> create new test tiddler
>  <$action-createtiddler 
>  $basetitle='testTiddler'
>  $template=<> >
>  <$action-navigate $to=<>/>
>  
> 
> 
> but disappointingly enough they do not! The new tiddler is created 
> indeed, but from NO TEMPLATE at all!
> Funny as it is, if we add a debug line like:
> 
> template's name: <> 
> 
> it displays correctly as
> 
> BASENAME-verb (or BASENAME-noun, or adjective, or whatever the 
> <$select> choice was)
> 
> Hard-coding the name in the macro makes the code work (just for testing 
> purposes, there is no point here to have a macro just echoing an 
> hard-coded string).
> 
> Now, before I ask why ON EARTH the above code doesn't work, let me say 
> that I expect for it to be because of how macros are parsed and when 
> macro substitution is made, in which case I will do a little comment on 
> it later.
> 
> Thanks everybody,
> CG 
> 
> -- 
> 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/13f797cd-fc5f-457d-b598-80cfa214a017n%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/9D458F71-1B89-4171-9E73-EDF1FDECA3D4%40gmail.com.

[tw5] Re: Transclusion Terminology

2022-01-17 Thread Jeremy Ruston

Hi Reinhard

Thanks for introducing the topic, as you can see it's an area of interest 
for a lot of us.

I had to search the docs to see whether I had used the terms 
transcluder/transcludee; I wouldn't have been surprised to find that I had 
because that terminology comes naturally to a programmer, as you note.

Generally, I rather relish introducing neologisms: it can be a powerful way 
to give people a conceptual blank slate on which to build meaning. The 
canonical example is the term "tiddler", which I started using when writing 
the code of the very first version of "TwiddlyWiki" (as it then was). I 
wanted to be able to write clear, readable function names but found that 
calling tiddlers conventional words like "node" or "object" gave rise to 
generic method names that were already overloaded with unwanted meanings. 
Introducing the term made the code cleaner, and so I soon started using it 
in the user interface too.

The trouble is that we have a very limited budget for new terms; each one 
acts as a little barrier for new users. So I try to avoid making neologisms 
unless absolutely necessary. And if there's an existing word that's a good 
fit then I try to reuse it (e.g. "plugins").

In this case, I think I've got away without these terms because of a twist 
in the way that I think about things: although transclusion always involves 
a transcludee, there isn't necessarily a transcluder. The thing doing the 
transcluding might be a dynamically constructed macro that doesn't have a 
1:1 relationship with a tiddler. Now, I appreciated that that is a rarified 
way of looking at things but it still guides me in writing the docs.

Anyhow, lots of interesting stuff in this area, thanks for bring it up.

Best wishes

Jeremy.

On Sunday, January 16, 2022 at 4:51:50 PM UTC reinhard...@gmail.com wrote:

> @TiddlyTweeter
>
> " Whom are you thinking needs the "*caller*" / "*callee*" differentiation"
>
> In the context of TiddlyWiki, nobody! I put it in just as an another 
> example for the "er"-"ee"-relationship (see for instance Suffixes -er and 
> -ee ). It 
> is useful as a common concept or abstraction to express that seemingly 
> non-related things (i.e. on process calling another, one function calling 
> another, one person calling another) have the same structure, and that 
> aspects that pertain to one instance of this concepts might be 
> transferrable to another instance of this concept (i.e. to save work).
>
> "Certainly any idea you *have* to be a full-on programmer to deep tweak 
> TW would be wrong."
>
> I don't know what you mean by "full-on programmer". TwiddlyWiki uses 
> several well established programming and 'page-description' languages 
> (HTML, CSS, Javascript, Markup) plus its own wikitext syntax for macros, 
> pragmas, etc. The mastery of each of these requires some amount of time and 
> practice. I guess, you didn't start out with transclusions and tweaking 
> TiddlyWiki when you first started using it?  Even if you don't consider 
> yourself a 'programmer', neverless programming is what you are doing when 
> you tweak TW.  But that's just semantics, nothing productive...
>
> So the lore, wisdom, principles, etc. of the programming community as a 
> whole might be applicable to TW as well. For instance, the general 
> programming principles, that function should do one thing and one thing 
> only or that a function should be as small as possible, apply to macros as 
> well.
>
> Have a neice evening,
> -Reinhard
>
>
>
>
> On Sunday, January 16, 2022 at 3:11:45 PM UTC+1 TiddlyTweeter wrote:
>
>> reinhard:  I have an extensive programming background*. *In Programming 
>> there it is never a question if a function is the *caller* or the 
>> *callee*, even with recursive functions. And in programming *recursion* is 
>> an advanced topic, that is definitely not for neophytes.
>>
>> Right. Sort of. BUT in TiddlyWiki many of the skilled tweakers are *not 
>> *professional 
>> programmers. That is part of it's character--practically it is used by folk 
>> of many kinds. Regarding the OP, I think it will appeal to the "hobbyist 
>> jacker" too ...who is the neophyte+. Certainly any idea you *have* to be 
>> a full-on programmer to deep tweak TW would be wrong. The whole thing we do 
>> here is testament that it isn't. 
>>
>> So in that context it might be worth revisiting your interesting OP. 
>>
>> Whom are you thinking needs the "*caller*" / "*callee*" differentiation?
>>
>> Anyway, happy today
>> TT
>>
>> On Sunday, 16 January 2022 at 14:06:45 UTC+1 reinhard...@gmail.com wrote:
>>
>>> @TiddlyTweeter
>>>
>>> " Overall I like where you coming from."
>>> And what might this be?
>>>
>>> *"Broadly, in documents, how do we explain complex nested transclusion 
>>> to neophytes?"*
>>>
>>> *I wouldn't even try!* IMHO, *recursion* and *complex nested 
>>> transclusions* are topics for people that are no longer neophytes.
>>>
>>> I'm

Re: [tw5] Wikify use case and trickery for tab-indented text

2022-01-03 Thread Jeremy Ruston

Hi Charlie

> On 3 Jan 2022, at 16:32, Charlie Veniot  wrote:
> 
> However, spaces and tabs are problematic for the "Wikify Viewer" tool because 
> HTML ignores whitespace (spaces and tabs), i.e. whitespace is not rendered.  

You can control how HTML displays whitespace with CSS:

https://developer.mozilla.org/en-US/docs/Web/CSS/white-space

Applying `white-space: pre;` should stop sequences of whitespace from being 
coalesced. It doesn’t help make tabs display better though.

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/3834DE13-BF41-4CAE-9ADA-1A3C0E118441%40gmail.com.

Re: [tw5] Filter to exclude tiddlers from includeWikis

2022-01-03 Thread Jeremy Ruston

Hi Louis,

> I'm running several TW 5.2.1 wikis on node and I use the includeWikis 
> properties in tiddlywiki.info file. Example wiki AAA has
> 
> "includeWikis": [
>{"path": "../BBB"}
> ]
> 
> Is there a filter expression I can use from within wiki AAA that will exclude 
> tiddlers from BBB?

No, there’s no automatic way to distinguish tiddlers from different wikis. 
You’d have to use tags or other manual criteria to distinguish them.

Best wishes

Jeremy


> 
> Thanks.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/316c974c-c76a-44b7-b1dd-794f8a246cc2n%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/1693C982-94AB-4029-ABFE-E8BD9B7399F9%40gmail.com.

[tw5] Re: external image handling seems laggy

2022-01-02 Thread Jeremy Ruston

Hi Gavin

This is now fixed in the prerelease:

https://github.com/Jermolene/TiddlyWiki5/commit/66ae1d6930796a9eb062fdb64a755adab8f39294

Let me know if it helps you accomplish your goal,

Best wishes

Jeremy

On Thursday, December 16, 2021 at 9:40:44 PM UTC Jeremy Ruston wrote:

> Hi Gavin,
>
> Has anyone implemented a smoother handling of loading and image via 
>> _canonical_uri_ in an image widget. Something like a CSS fade animation ?
>>
>
> I think we'd need a core modification for that: an additional class for 
> the image widget that is only applied when the image is successfully loaded.
>
> I've made a ticket here:
>
> https://github.com/Jermolene/TiddlyWiki5/issues/6346
>
> 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/5545f1d2-5d33-4b70-a7ab-ad4b63c8b33dn%40googlegroups.com.

[tw5] Re: external image handling seems laggy

2021-12-16 Thread Jeremy Ruston

Hi Gavin,

Has anyone implemented a smoother handling of loading and image via 
> _canonical_uri_ in an image widget. Something like a CSS fade animation ?
>

I think we'd need a core modification for that: an additional class for the 
image widget that is only applied when the image is successfully loaded.

I've made a ticket here:

https://github.com/Jermolene/TiddlyWiki5/issues/6346

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/f88e0ac9-3884-4d4e-9e3d-5bcd7ddbbd6dn%40googlegroups.com.

[tw5] Re: unable to manually install plugins.. tDesktop, Beaker, Firefox..

2021-12-11 Thread Jeremy Ruston

Hi Blase

> I'm unable to manually add plugins. I have working (writeable) copies of 
'Empty' TD5.21 on TiddlyDesktop, Beaker, and Firefox for OS X 10.15.17. 
I'll drag the link to the plugin into TW,  (e.g. '
$:/plugins/tiddlywiki/katex 
'

) the green import banner pops up, then the Import Tiddler opens, and I hit 
import. That creates a new Tiddler with a hyperlink to the plugin. But 
thats it. No new plugins are installed. Tested on all 3 platforms.

Just to double check, did you save changes and refresh the browser after 
importing the plugin? That step is needed for plugins that include 
JavaScript modules (which includes KaTeX).

Best wishes

Jeremy

On Saturday, December 11, 2021 at 6:17:42 AM UTC Mark S. wrote:

> It might be where you're dragging *from* -- it's 5.2.1, right? At least 
> if you're using the link you provided above.
>
> You could try dragging in the attached into your 5.1.23 edition..
>
> Or you can go into the control panel (back at 5.1.23), plugins, "Get More 
> Plugins" , plugins tab, search and install katex.
>
> On Friday, December 10, 2021 at 9:31:03 PM UTC-8 blaset...@gmail.com 
> wrote:
>
>> I tried 5.1.23, which had the same results.
>>
>> On Friday, December 10, 2021 at 7:59:56 PM UTC-5 Mark S. wrote:
>>
>>> Since you're not using Chrome, you might see if 5.2.0 works. 
>>>
>>> On Friday, December 10, 2021 at 3:14:56 PM UTC-8 blaset...@gmail.com 
>>> wrote:
>>>
 Hi guys,

 Apologies if I've missed something obvious. I'm just getting on my feet 
 with TW.

 I'm unable to manually add plugins. I have working (writeable) copies 
 of 'Empty' TD5.21 on TiddlyDesktop, Beaker, and Firefox for OS X 10.15.17. 
 I'll drag the link to the plugin into TW,  (e.g. '
 $:/plugins/tiddlywiki/katex 
 '

 ) the green import banner pops up, then the Import Tiddler opens, and I 
 hit 
 import. That creates a new Tiddler with a hyperlink to the plugin. But 
 thats it. No new plugins are installed. Tested on all 3 platforms.

 I've verbatim replicated every instructional or tutorial I can find, 
 and it seems like its really as simple as dragging to import. But my 
 outcome is always the same, nothing happens after importing.

 For example, this video tutorial literally spells it out step by step, 
 without room for error. And despite replicating the exact process (in all 
 3 
 platform instances), it never takes.

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

 Thanks for reading,
 Blase

-- 
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/f0e77010-0618-496c-a986-11cfd7515d84n%40googlegroups.com.

[tw5] Re: New Release Banner Super-speedy Competition for v5.2.1

2021-12-09 Thread Jeremy Ruston

Thanks Springer!

> Jeremy, I'm happy to streamline details or optimize the svg-png size 
(etc.) if that would be helpful.

I thought you'd done so – the image is already only 42KB :)

Best wishes

Jeremy


On Wednesday, December 8, 2021 at 3:41:20 AM UTC springer wrote:

> I'm tickled!  I had found Mohammad's svg for filters to be so visually 
> intuitive that I couldn't resist playing with it a bit more. Sometimes 
> trying something "just for yuks" is the way to go! 
>
> Jeremy, I'm happy to streamline details or optimize the svg-png size 
> (etc.) if that would be helpful.
>
> -Springer
>
> On Monday, December 6, 2021 at 12:23:10 PM UTC-5 jeremy...@gmail.com 
> wrote:
>
>> Thank you to everyone once again for your help. I'm afraid non-TW stuff 
>> has delayed me for a few days, but now we're back on track to make the 
>> release this week.
>>
>> I was just looking at Springer's collection of the entries at 
>> https://tw-logo-contest.tiddlyhost.com. My first thought was that I 
>> regret suggesting that I should choose the winner because it's too 
>> difficult with so many excellent entries.
>>
>> Two entries that particularly caught my eye are Springer's:
>>
>> [image: Unknown-..png]
>>
>> And Mohammad's:
>>
>> [image: Unknown-3.png]
>> I was just thinking that it would be nice to have those two designs 
>> combined when I came to this thread and saw Springer's mashup which seems 
>> to be pretty much what I wanted:
>>
>> [image: mashup.png]
>>
>> So, I am happy to declare that we have a winner. Congratulations to 
>> Springer and Mohammad, and my sincere thanks to everyone who has entered.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> On Monday, November 29, 2021 at 5:00:56 PM UTC springer wrote:
>>
>>> Mashup, for yuks:
>>>
>>> [image: mashup.png]
>>>
>>> On Monday, November 29, 2021 at 11:39:34 AM UTC-5 TiddlyTweeter wrote:
>>>
 My two cents. I think Mohammad's entry good. It visually conveys 
 filtering well.

 TT   

 On Monday, 29 November 2021 at 11:53:48 UTC+1 jeremy...@gmail.com 
 wrote:

> And thank you for all the entrants so far. The banner competition 
> always attracts great entries, but I particularly appreciate the skill of 
> designing under strict time constraints!
>
> Best wishes
>
> Jeremy
>
> >Some of you may like the below banner!
>
>
>
>
>> [image: drawing-optim.png]
>>
> On Tuesday, November 23, 2021 at 9:06:36 PM UTC+3:30 jeremy wrote:
>>
>>> As usual, I’d like to hold a competition to design the banner image 
>>> that is shown on the splash screen and within the opening HelloThere 
>>> tiddler.
>>>
>>> The unusual thing this time around is that we have very limited 
>>> time. Due to a serious bug introduced by the latest version of Chrome 
>>> we 
>>> are trying to get v5.2.1 released as soon as possible, perhaps as soon 
>>> as 
>>> this weekend.
>>>
>>> With that in mind, we’ll have to run the competition slightly 
>>> differently this time:
>>>
>>>- Entries will be accepted until Friday morning at 8am UK time
>>>- To speed things up, my plan is that I should choose the 
>>>winning image (I’m open to discussion here!)
>>>
>>> The artwork should reflect some of the changes in the new version. 
>>> I’ve updated the release note for the prerelease but at this point the 
>>> documentation for some of the new features is not complete.
>>>
>>> https://tiddlywiki.com/prerelease/
>>>
>>> The other rules/guidelines for the competition are:
>>>
>>>- The version number (with the correct punctuation) must be 
>>>clear and readable even when the banner is shown at a reduced size
>>>- The image must be a PNG or JPEG of exactly 560x315 pixels
>>>- The bottom 46 pixels will be obscured by the banner text 
>>>“What’s new in 5.2.1” when it is displayed within HelloThere
>>>- The image need not include the word “TiddlyWiki”. The banner 
>>>image is only used in contexts where it is clear that it is about 
>>> TiddlyWiki
>>>- Feel free to enter an updated version of artwork that was a 
>>>runner-up in a previous competition
>>>- Reply to this message with your entry, or any questions
>>>- Please give lots of feedback here to encourage the artists
>>>
>>> Here are the posts about previous artwork competitions:
>>>
>>> v5.2.0 - 
>>> https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ
>>> v5.1.23 - https://groups.google.com/g/
>>> tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>>> v5.1.22 - 
>>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>>> v5.1.21 - 
>>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>>
>>> The Chrome bug I was referring to is discussed here:
>>>
>>>

[tw5] Announcing the release of TiddlyWiki v5.2.1

2021-12-08 Thread Jeremy Ruston

I'm delighted to announce the release of TiddlyWiki v5.2.1 at:

https://tiddlywiki.com/ 

This release was brought forward in order to include critical bug fixes for 
problems with drag and drop on the latest Chrome 96 on Windows but has two 
significant new features:

A new, more flexible `<$let>` widget that should generally be used in 
preference to the existing `<$vars>` widget
A new cascade mechanism that makes it possible to cleanly give a tiddler a 
custom view template, amongst many other uses

Other improvements include:

Improved sidebar plugin listing (under More -> Plugins)
A new hidden setting for controlling the visibility of the editor preview pane 
on a per-tiddler basis
New trigonometric operators: acos, asin, atan, cos, sin and tan
New ActionSetMultipleFieldsWidget, new SetMultipleVariablesWidget and extended 
ActionSendMessageWidget for working with multiple 
variables/fields/indexes/parameters in one operation
Improved Polish and Chinese translations

See the release note for the full list of changes.

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html 

For Node.js users, the new version is available on npm:

https://www.npmjs.com/package/tiddlywiki 


As ever, exercise caution when upgrading, and be careful to keep backup copies 
of everything important.

A big thank you to everyone out there who has helped with this release. We’re 
making very significant progress in improving the flexibility and extensibility 
of TiddlyWiki, and I’m excited to see what the community makes with the new 
features.

Any questions or comments are welcome here, or via GitHub.

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/F7CCC5EC-5144-469A-ABC2-01CB3507353A%40gmail.com.

[tw5] Re: New Release Banner Super-speedy Competition for v5.2.1

2021-12-06 Thread Jeremy Ruston

Thank you to everyone once again for your help. I'm afraid non-TW stuff has 
delayed me for a few days, but now we're back on track to make the release 
this week.

I was just looking at Springer's collection of the entries at 
https://tw-logo-contest.tiddlyhost.com. My first thought was that I regret 
suggesting that I should choose the winner because it's too difficult with 
so many excellent entries.

Two entries that particularly caught my eye are Springer's:

[image: Unknown-..png]

And Mohammad's:

[image: Unknown-3.png]
I was just thinking that it would be nice to have those two designs 
combined when I came to this thread and saw Springer's mashup which seems 
to be pretty much what I wanted:

[image: mashup.png]

So, I am happy to declare that we have a winner. Congratulations to 
Springer and Mohammad, and my sincere thanks to everyone who has entered.

Best wishes

Jeremy


On Monday, November 29, 2021 at 5:00:56 PM UTC springer wrote:

> Mashup, for yuks:
>
> [image: mashup.png]
>
> On Monday, November 29, 2021 at 11:39:34 AM UTC-5 TiddlyTweeter wrote:
>
>> My two cents. I think Mohammad's entry good. It visually conveys 
>> filtering well.
>>
>> TT   
>>
>> On Monday, 29 November 2021 at 11:53:48 UTC+1 jeremy...@gmail.com wrote:
>>
>>> And thank you for all the entrants so far. The banner competition always 
>>> attracts great entries, but I particularly appreciate the skill of 
>>> designing under strict time constraints!
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>> >Some of you may like the below banner!
>>>
>>>
>>>
>>>
 [image: drawing-optim.png]

>>> On Tuesday, November 23, 2021 at 9:06:36 PM UTC+3:30 jeremy wrote:

> As usual, I’d like to hold a competition to design the banner image 
> that is shown on the splash screen and within the opening HelloThere 
> tiddler.
>
> The unusual thing this time around is that we have very limited time. 
> Due to a serious bug introduced by the latest version of Chrome we are 
> trying to get v5.2.1 released as soon as possible, perhaps as soon as 
> this 
> weekend.
>
> With that in mind, we’ll have to run the competition slightly 
> differently this time:
>
>- Entries will be accepted until Friday morning at 8am UK time
>- To speed things up, my plan is that I should choose the winning 
>image (I’m open to discussion here!)
>
> The artwork should reflect some of the changes in the new version. 
> I’ve updated the release note for the prerelease but at this point the 
> documentation for some of the new features is not complete.
>
> https://tiddlywiki.com/prerelease/
>
> The other rules/guidelines for the competition are:
>
>- The version number (with the correct punctuation) must be clear 
>and readable even when the banner is shown at a reduced size
>- The image must be a PNG or JPEG of exactly 560x315 pixels
>- The bottom 46 pixels will be obscured by the banner text 
>“What’s new in 5.2.1” when it is displayed within HelloThere
>- The image need not include the word “TiddlyWiki”. The banner 
>image is only used in contexts where it is clear that it is about 
> TiddlyWiki
>- Feel free to enter an updated version of artwork that was a 
>runner-up in a previous competition
>- Reply to this message with your entry, or any questions
>- Please give lots of feedback here to encourage the artists
>
> Here are the posts about previous artwork competitions:
>
> v5.2.0 - 
> https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ
> v5.1.23 - https://groups.google.com/g/
> tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
> v5.1.22 - 
> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
> v5.1.21 - 
> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>
> The Chrome bug I was referring to is discussed here:
>
> https://github.com/Jermolene/TiddlyWiki5/issues/6254
> https://github.com/Jermolene/TiddlyWiki5/pull/6261
>
> Plans for the v5.2.1 release are being discussed here:
>
> https://github.com/Jermolene/TiddlyWiki5/issues/6259
>
> Best wishes and many thanks,
>
> 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/9e4865b8-a1e1-4675-ba9d-a1c92ce3d413n%40googlegroups.com.

[tw5] Re: Please help us test v5.2.1-prerelease so we can expedite its release

2021-12-06 Thread Jeremy Ruston

Thank you to everyone for your help.

We've now added documentation for the new cascade mechanism:

https://tiddlywiki.com/prerelease/#Cascades

Again, any feedback or questions are welcome,

Best wishes

Jeremy

On Wednesday, December 1, 2021 at 3:48:32 PM UTC Stobot wrote:

> Don't know if you're looking for "no issue" replies or if it's just noise, 
> but I haven't run into any concerns on any of my wikis I've tested so far - 
> mostly Node on Windows so far. 
> On Wednesday, November 24, 2021 at 12:10:49 PM UTC-5 ma...@makiaea.org 
> wrote:
>
>> i'm sure it's just something weird in my source tiddlywiki but if i just 
>> upgrade as-is, it breaks. deselecting all tiddlers and selecting all 
>> tiddlers to upgrade (i.e. to include state tiddlers etc. -- lots of my 
>> tiddlers have state-tiddler-dependent moving parts) in the wizard seems to 
>> produce a working file. tested on mac chrome Version 96.0.4664.55 (Official 
>> Build) (arm64), mac monterey safari Version 15.1 (17612.2.9.1.20), and ios 
>> 14.3
>>
>> wanted to attach some files: original 20210120makiaea tiddlywiki; upgrade 
>> (broken) brings up $:/library/sjcl.js on startup; and upgrade-2 (working)
>>
>> but google groups complained the message was too long(!)
>>
>>>

-- 
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/93e14fb7-a65a-40aa-803c-3b18ef6543adn%40googlegroups.com.

Re: [tw5] [tw] Using Custom Font in Tiddler Editor

2021-12-02 Thread Jeremy Ruston

Hi Maurizio,

That’s great to hear, I’m sorry I didn’t mention that option before.

Best wishes

Jeremy

PS - do send a screenshot of what you’ve ended up with, it might inspire 
others...

> On 2 Dec 2021, at 08:47, Maurizio Torchio  wrote:
> 
> WOW! IT WORKS
> I'm... elated.
> 
> Il giorno giovedì 2 dicembre 2021 alle 09:10:26 UTC+1 jeremy...@gmail.com ha 
> scritto:
>> thank you Charlie and Jeremy! yes: mine is a font-face. 
>> the problem is: I love fonts! I use different fonts for different wiki, they 
>> embody the "soul" of the wiki (and I'd like to have the same font whether 
>> desktop or mobile, viewing or editing). that's why until now i used the edit 
>> widget for editing. but this means: no toolbar, and it can be annoying, 
>> especially on mobile. 
>> anyhow: thanks again for this priceless tool!
>> m. 
> 
> Have you tried using the CodeMirror plugin? It allows you to change the 
> editor font family through $:/ControlPanel settings panel
> 
> Best wishes
> 
> Jeremy
> 
> 
>> 
>> Il giorno mercoledì 1 dicembre 2021 alle 18:23:39 UTC+1 cj.v...@gmail.com 
>>  ha scritto:
>> Thanks for the info, Jeremy.  2-tier client server guy over here, so the 
>> innards of web browsers is foreign territory for this kid.
>> 
>> So whatever browser Maurizio is using, that approach I'm suggesting should 
>> work with some font-family available by default in whatever browser Maurizio 
>> is using, right?
>> 
>> On Wednesday, December 1, 2021 at 1:15:16 PM UTC-4 jeremy...@gmail.com <> 
>> wrote:
>> I think it's working for CJ because the "Brush Script MT" font is available 
>> by default in that browser, without needing to be defined by a font-face 
>> tag. That technique only works for built-in fonts because there's no way to 
>> inject the CSS font-face declaration into the iframe.
>> 
>> Best wishes
>> 
>> Jeremy
>> 
>> 
>> 
>> 
>> 
>> On Wednesday, December 1, 2021 at 5:03:36 PM UTC cj.v...@gmail.com <> wrote:
>> Just to confirm, I went to tiddlywiki.com , edited 
>> (i.e. clicked the "edit" button) that core tiddler, (1) added the style 
>> lines above the edit widget, and (2) altered the class for the edit widget, 
>> adding bubba as the third class.
>> 
>> Works A-1 for me.
>> 
>> Maybe Brush Script MT cursive doesn't work with your web browser?  (Another 
>> screenshot for the proof in the pudding, with an obnoxious font size, below.)
>> 
>> It is the font in the editor that you want adjusted, right?
>> 
>> Total aside: "bubba" because it is easy for me to find and remember.  I'm a 
>> huge fan of the movie Forrest Gump, and really liked "Bubba" in that movie.
>> 
>> 
>> 
>> On Wednesday, December 1, 2021 at 12:45:03 PM UTC-4 Charlie Veniot wrote:
>> I forgot to mention, you have to add that "bubba" class to the edit text 
>> widget.
>> 
>> As per the screenshot, the editor is showing that funky font.
>> 
>> However, it did strangely take half-a-minute or so for that font to take 
>> effect.
>> 
>> On Wednesday, December 1, 2021 at 11:45:47 AM UTC-4 torc...@gmail.com <> 
>> wrote:
>> thank you cj.v, but it didn't worked for me. 
>> it assign the class bubba to the iframe (just as 
>> $:/themes/tiddlywiki/vanilla/settings/editorfontfamily does) but... nothing 
>> changes.
>> i suspect it has to do with what Jeremy wrote:
>> 
>> "The reason that custom fonts doesn’t work with the editor toolbar is 
>> because of the way that it creates the textarea element within an embedded 
>> iframe (this is done so that the selection in the textarea isn’t lost when 
>> the user clicks on a toolbar button and the textarea loses focus).
>> 
>> The iframe doesn’t inherit any of the styles in the main document, so the 
>> code actually creates a hidden textarea and then reads back the styles, and 
>> then applies them to the textarea in the iframe. That means that any 
>> formatting applied to the textarea will be faithfully reproduced within the 
>> iframe. However, it only works for CSS properties applied directly to the 
>> textarea; it doesn’t transfer fonts, animations or other resources that can 
>> be defined in CSS.
>> 
>> (The code is here: 
>> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/editor/engines/framed.js
>>  
>> )
>> 
>> We could update things so that special stylesheets identified by a new 
>> system tag such as $:/tags/Stylesheet/FramedEditor would be automatically 
>> inserted within the iframe." 
>> 
>> Il giorno mercoledì 1 dicembre 2021 alle 14:57:19 UTC+1 cj.v...@gmail.com <> 
>> ha scritto:
>> G'day,
>> 
>> If you are not averse to changing core TiddlyWiki templates, you could add a 
>> style at the top of the content in $:/core/ui/EditTemplate/body/editor.
>> 
>> See my screenshot below, in which I set the font to Brush Script MT cursive.
>> 
>> It would be good for more experienced TiddlyWiki users to chime in on any 
>> downsides to this

Re: [tw5] [tw] Using Custom Font in Tiddler Editor

2021-12-02 Thread Jeremy Ruston

> thank you Charlie and Jeremy! yes: mine is a font-face. 
> the problem is: I love fonts! I use different fonts for different wiki, they 
> embody the "soul" of the wiki (and I'd like to have the same font whether 
> desktop or mobile, viewing or editing). that's why until now i used the edit 
> widget for editing. but this means: no toolbar, and it can be annoying, 
> especially on mobile. 
> anyhow: thanks again for this priceless tool!
> m. 

Have you tried using the CodeMirror plugin? It allows you to change the editor 
font family through $:/ControlPanel settings panel

Best wishes

Jeremy

> 
> Il giorno mercoledì 1 dicembre 2021 alle 18:23:39 UTC+1 cj.v...@gmail.com 
>  ha scritto:
> Thanks for the info, Jeremy.  2-tier client server guy over here, so the 
> innards of web browsers is foreign territory for this kid.
> 
> So whatever browser Maurizio is using, that approach I'm suggesting should 
> work with some font-family available by default in whatever browser Maurizio 
> is using, right?
> 
> On Wednesday, December 1, 2021 at 1:15:16 PM UTC-4 jeremy...@gmail.com 
>  wrote:
> I think it's working for CJ because the "Brush Script MT" font is available 
> by default in that browser, without needing to be defined by a font-face tag. 
> That technique only works for built-in fonts because there's no way to inject 
> the CSS font-face declaration into the iframe.
> 
> Best wishes
> 
> Jeremy
> 
> 
> 
> 
> 
> On Wednesday, December 1, 2021 at 5:03:36 PM UTC cj.v...@gmail.com <> wrote:
> Just to confirm, I went to tiddlywiki.com , edited 
> (i.e. clicked the "edit" button) that core tiddler, (1) added the style lines 
> above the edit widget, and (2) altered the class for the edit widget, adding 
> bubba as the third class.
> 
> Works A-1 for me.
> 
> Maybe Brush Script MT cursive doesn't work with your web browser?  (Another 
> screenshot for the proof in the pudding, with an obnoxious font size, below.)
> 
> It is the font in the editor that you want adjusted, right?
> 
> Total aside: "bubba" because it is easy for me to find and remember.  I'm a 
> huge fan of the movie Forrest Gump, and really liked "Bubba" in that movie.
> 
> 
> 
> On Wednesday, December 1, 2021 at 12:45:03 PM UTC-4 Charlie Veniot wrote:
> I forgot to mention, you have to add that "bubba" class to the edit text 
> widget.
> 
> As per the screenshot, the editor is showing that funky font.
> 
> However, it did strangely take half-a-minute or so for that font to take 
> effect.
> 
> On Wednesday, December 1, 2021 at 11:45:47 AM UTC-4 torc...@gmail.com <> 
> wrote:
> thank you cj.v, but it didn't worked for me. 
> it assign the class bubba to the iframe (just as 
> $:/themes/tiddlywiki/vanilla/settings/editorfontfamily does) but... nothing 
> changes.
> i suspect it has to do with what Jeremy wrote:
> 
> "The reason that custom fonts doesn’t work with the editor toolbar is because 
> of the way that it creates the textarea element within an embedded iframe 
> (this is done so that the selection in the textarea isn’t lost when the user 
> clicks on a toolbar button and the textarea loses focus).
> 
> The iframe doesn’t inherit any of the styles in the main document, so the 
> code actually creates a hidden textarea and then reads back the styles, and 
> then applies them to the textarea in the iframe. That means that any 
> formatting applied to the textarea will be faithfully reproduced within the 
> iframe. However, it only works for CSS properties applied directly to the 
> textarea; it doesn’t transfer fonts, animations or other resources that can 
> be defined in CSS.
> 
> (The code is here: 
> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/editor/engines/framed.js
>  
> )
> 
> We could update things so that special stylesheets identified by a new system 
> tag such as $:/tags/Stylesheet/FramedEditor would be automatically inserted 
> within the iframe." 
> 
> Il giorno mercoledì 1 dicembre 2021 alle 14:57:19 UTC+1 cj.v...@gmail.com <> 
> ha scritto:
> G'day,
> 
> If you are not averse to changing core TiddlyWiki templates, you could add a 
> style at the top of the content in $:/core/ui/EditTemplate/body/editor.
> 
> See my screenshot below, in which I set the font to Brush Script MT cursive.
> 
> It would be good for more experienced TiddlyWiki users to chime in on any 
> downsides to this approach.
> 
> (BTW: please ignore the goofy-looking "!!! EditTemplate body" ... that's me 
> entering little breadcrumbs to figure out which core tiddler is which.)
> 
> 
> 
> On Wednesday, December 1, 2021 at 6:19:45 AM UTC-4 torc...@gmail.com <> wrote:
> Hi everybody, any progress on this? (I really don't like see a different 
> fontfamily when editing)
> thank you so much for all the great work!
> 
> maurizio
> 
> Il giorno martedì 30 gennaio 2018 alle 21:09:06 UTC+1 Ton Gerner ha

[tw5] Re: [tw] Using Custom Font in Tiddler Editor

2021-12-01 Thread Jeremy Ruston

I think it's working for CJ because the "Brush Script MT" font is available 
by default in that browser, without needing to be defined by a font-face 
tag. That technique only works for built-in fonts because there's no way to 
inject the CSS font-face declaration into the iframe.

Best wishes

Jeremy





On Wednesday, December 1, 2021 at 5:03:36 PM UTC cj.v...@gmail.com wrote:

> Just to confirm, I went to tiddlywiki.com, edited (i.e. clicked the 
> "edit" button) that core tiddler, *(1)* added the style lines above the 
> edit widget, and *(2)* altered the class for the edit widget, adding 
> bubba as the third class.
>
> Works A-1 for me.
>
> Maybe Brush Script MT cursive doesn't work with your web browser?  
> (Another screenshot for the proof in the pudding, with an obnoxious font 
> size, below.)
>
> It is the font in the editor that you want adjusted, right?
>
> Total aside: "bubba" because it is easy for me to find and remember.  I'm 
> a huge fan of the movie Forrest Gump, and really liked "Bubba" in that 
> movie.
>
> [image: Screenshot 2021-12-01 12.58.38 PM.png]
>
> On Wednesday, December 1, 2021 at 12:45:03 PM UTC-4 Charlie Veniot wrote:
>
>> I forgot to mention, you have to add that "bubba" class to the edit text 
>> widget.
>>
>> As per the screenshot, the editor is showing that funky font.
>>
>> However, it did strangely take half-a-minute or so for that font to take 
>> effect.
>>
>> On Wednesday, December 1, 2021 at 11:45:47 AM UTC-4 torc...@gmail.com 
>> wrote:
>>
>>> thank you cj.v, but it didn't worked for me. 
>>> it assign the class bubba to the iframe (just as 
>>> $:/themes/tiddlywiki/vanilla/settings/editorfontfamily does) but... nothing 
>>> changes.
>>> i suspect it has to do with what Jeremy wrote:
>>>
>>> "The reason that custom fonts doesn’t work with the editor toolbar is 
>>> because of the way that it creates the textarea element within an embedded 
>>> iframe (this is done so that the selection in the textarea isn’t lost when 
>>> the user clicks on a toolbar button and the textarea loses focus).
>>>
>>> The iframe doesn’t inherit any of the styles in the main document, so 
>>> the code actually creates a hidden textarea and then reads back the styles, 
>>> and then applies them to the textarea in the iframe. That means that any 
>>> formatting applied to the textarea will be faithfully reproduced within the 
>>> iframe. However, it only works for CSS properties applied directly to the 
>>> textarea; it doesn’t transfer fonts, animations or other resources that can 
>>> be defined in CSS.
>>>
>>> (The code is here: 
>>> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/editor/engines/framed.js
>>> )
>>>
>>> We could update things so that special stylesheets identified by a new 
>>> system tag such as $:/tags/Stylesheet/FramedEditor would be automatically 
>>> inserted within the iframe." 
>>>
>>> Il giorno mercoledì 1 dicembre 2021 alle 14:57:19 UTC+1 
>>> cj.v...@gmail.com ha scritto:
>>>
 G'day,

 If you are not averse to changing core TiddlyWiki templates, you could 
 add a style at the top of the content in 
 $:/core/ui/EditTemplate/body/editor.

 See my screenshot below, in which I set the font to Brush Script MT 
 cursive.

 It would be good for more experienced TiddlyWiki users to chime in on 
 any downsides to this approach.

 *(BTW: please ignore the goofy-looking "!!! EditTemplate body" ... 
 that's me entering little breadcrumbs to figure out which core tiddler is 
 which.)*

 [image: Screenshot 2021-12-01 9.52.23 AM.png]

 On Wednesday, December 1, 2021 at 6:19:45 AM UTC-4 torc...@gmail.com 
 wrote:

> Hi everybody, any progress on this? (I really don't like see a 
> different fontfamily when editing)
> thank you so much for all the great work!
>
> maurizio
>
> Il giorno martedì 30 gennaio 2018 alle 21:09:06 UTC+1 Ton Gerner ha 
> scritto:
>
>> Hi Alfonso,
>>
>> If I remember correctly the following comes from Jeremy's TalkyTalky 
>>  which uses the Google font Lato:
>>
>> It contains the follwing stylesheet (a tiddler tagged with 
>> $:/tags/Stylesheet):
>>
>> \define register-font(family,title,style,weight)
>> @font-face {
>>   font-family: "$family$";
>>   font-style: $style$;
>>   font-weight: $weight$;
>>   src: url(<>) format("woff");
>> }
>> \end
>> \rules only filteredtranscludeinline transcludeinline macrodef 
>> macrocallinline
>>
>> /*
>> ** Fonts
>> */
>>
>> <> "900">>
>> <> "italic" "900">>
>> <> "700">>
>> <> "italic" "700">>
>> <> "normal" "100">>
>> <> "italic" "100">>
>> <> "400">>
>> <> "300">>
>> <> "italic" "300">>
>> <> "400">>
>>
>> Hope that helps.
>>
>> Cheers,
>>
>> Ton

Re: [tw5] Re: Bug in TW 5.2.0 in zoomin view.

2021-12-01 Thread Jeremy Ruston

Hi Siniy-Kit

> In TW 5.2.1-prereliase  everything is good. And it is great!

Excellent news, thanks for your help,

Best wishes

Jeremy

> 
> http://heeg.ru/shop2_3.html?id=10Q1RMs2QeKlvKywq7MGHSRltcDYXYTD5y2HFs0aygqE
> 
> понедельник, 29 ноября 2021 г. в 17:56:35 UTC+3, Siniy-Kit: 
>> Here  I have update my TW5 to 5.2.0  template. 
>> http://heeg.ru/shop2_3_.html?id=10Q1RMs2QeKlvKywq7MGHSRltcDYXYTD5y2HFs0aygqE#index
>> if I press back button (previous page) it scrolled to the bottom of the 
>> page. May be we can fix it by css styles?
>> 
>> вторник, 9 ноября 2021 г. в 19:57:29 UTC+3, jeremy...@gmail.com: 
>>> Hi Siniy-Kit,
>> 
>>> 
>>> I can confirm the problem with v5.2.0. I also checked v5.1.23 and it seems 
>>> to have the same problem.
>>> 
>>> Do you know when the problem was introduced? Did it indeed ever work 
>>> properly?
>>> 
>>> Best wishes
>>> 
>>> Jeremy
>>> 
>>> On Tuesday, November 9, 2021 at 4:45:33 PM UTC Jeremy Ruston wrote:
>>>> Hi Siniy-Kit
>>>> 
>>>> Thanks for the report, I'll investigate.
>>>> 
>>>> Best wishes
>>>> 
>>>> Jeremy
>>>> 
>>>> On Sunday, November 7, 2021 at 9:40:19 AM UTC Siniy-Kit wrote:
>>>>> Jeremy, help me please. I want to update my template to  new version, but 
>>>>> it works only with zoomin view. 
>>>>> 
>>>>> четверг, 28 октября 2021 г. в 15:52:49 UTC+3, Siniy-Kit: 
>>>>>> Old TW5 works good. But now it has bad auto scroll while navigating 
>>>>>> between tiddlers 
>>>>>> For example open this tiddler https://tiddlywiki.com/#Filter%20Operators 
>>>>>> then make zoomin view
>>>>>> 
>>>>>>  then go back to Filter Operators tiddler and press "range"
>>>>>> 
>>>>>> 
>>>>>> after click you will see this
>>>>>> 
>>>>>> 
>>>>>> I want to see the top of this tiddler, but it autoscroll to middle. Can 
>>>>>> we fix this bug? 
> 
> -- 
> 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/767e74c3-36a7-4b8c-a633-0bb7f13b5c24n%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/6D8FC6F6-CBE2-4A68-BA85-C1476CD7F211%40gmail.com.

[tw5] Re: New Release Banner Super-speedy Competition for v5.2.1

2021-11-29 Thread Jeremy Ruston

I meant to add a reminder for Mohammad that "5.2.1" should have a "v" 
prefix: "v5.2.1".

Best wishes

Jeremy

On Monday, November 29, 2021 at 10:53:48 AM UTC Jeremy Ruston wrote:

> And thank you for all the entrants so far. The banner competition always 
> attracts great entries, but I particularly appreciate the skill of 
> designing under strict time constraints!
>
> Best wishes
>
> Jeremy
>
> >Some of you may like the below banner!
>
>
>
>
>> [image: drawing-optim.png]
>>
> On Tuesday, November 23, 2021 at 9:06:36 PM UTC+3:30 jeremy wrote:
>>
>>> As usual, I’d like to hold a competition to design the banner image that 
>>> is shown on the splash screen and within the opening HelloThere tiddler.
>>>
>>> The unusual thing this time around is that we have very limited time. 
>>> Due to a serious bug introduced by the latest version of Chrome we are 
>>> trying to get v5.2.1 released as soon as possible, perhaps as soon as this 
>>> weekend.
>>>
>>> With that in mind, we’ll have to run the competition slightly 
>>> differently this time:
>>>
>>>- Entries will be accepted until Friday morning at 8am UK time
>>>- To speed things up, my plan is that I should choose the winning 
>>>image (I’m open to discussion here!)
>>>
>>> The artwork should reflect some of the changes in the new version. I’ve 
>>> updated the release note for the prerelease but at this point the 
>>> documentation for some of the new features is not complete.
>>>
>>> https://tiddlywiki.com/prerelease/
>>>
>>> The other rules/guidelines for the competition are:
>>>
>>>- The version number (with the correct punctuation) must be clear 
>>>and readable even when the banner is shown at a reduced size
>>>- The image must be a PNG or JPEG of exactly 560x315 pixels
>>>- The bottom 46 pixels will be obscured by the banner text 
>>>“What’s new in 5.2.1” when it is displayed within HelloThere
>>>- The image need not include the word “TiddlyWiki”. The banner image 
>>>is only used in contexts where it is clear that it is about TiddlyWiki
>>>- Feel free to enter an updated version of artwork that was a 
>>>runner-up in a previous competition
>>>- Reply to this message with your entry, or any questions
>>>- Please give lots of feedback here to encourage the artists
>>>
>>> Here are the posts about previous artwork competitions:
>>>
>>> v5.2.0 - 
>>> https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ
>>> v5.1.23 - https://groups.google.com/g/
>>> tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>>> v5.1.22 - 
>>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>>> v5.1.21 - 
>>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>>
>>> The Chrome bug I was referring to is discussed here:
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/issues/6254
>>> https://github.com/Jermolene/TiddlyWiki5/pull/6261
>>>
>>> Plans for the v5.2.1 release are being discussed here:
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/issues/6259
>>>
>>> Best wishes and many thanks,
>>>
>>> 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/2e0344aa-a86b-4c28-9d77-631df9f4438cn%40googlegroups.com.

[tw5] Re: New Release Banner Super-speedy Competition for v5.2.1

2021-11-29 Thread Jeremy Ruston

And thank you for all the entrants so far. The banner competition always 
attracts great entries, but I particularly appreciate the skill of 
designing under strict time constraints!

Best wishes

Jeremy

>Some of you may like the below banner!




> [image: drawing-optim.png]
> On Tuesday, November 23, 2021 at 9:06:36 PM UTC+3:30 jeremy wrote:
>
>> As usual, I’d like to hold a competition to design the banner image that 
>> is shown on the splash screen and within the opening HelloThere tiddler.
>>
>> The unusual thing this time around is that we have very limited time. Due 
>> to a serious bug introduced by the latest version of Chrome we are trying 
>> to get v5.2.1 released as soon as possible, perhaps as soon as this weekend.
>>
>> With that in mind, we’ll have to run the competition slightly differently 
>> this time:
>>
>>- Entries will be accepted until Friday morning at 8am UK time
>>- To speed things up, my plan is that I should choose the winning 
>>image (I’m open to discussion here!)
>>
>> The artwork should reflect some of the changes in the new version. I’ve 
>> updated the release note for the prerelease but at this point the 
>> documentation for some of the new features is not complete.
>>
>> https://tiddlywiki.com/prerelease/
>>
>> The other rules/guidelines for the competition are:
>>
>>- The version number (with the correct punctuation) must be clear and 
>>readable even when the banner is shown at a reduced size
>>- The image must be a PNG or JPEG of exactly 560x315 pixels
>>- The bottom 46 pixels will be obscured by the banner text 
>>“What’s new in 5.2.1” when it is displayed within HelloThere
>>- The image need not include the word “TiddlyWiki”. The banner image 
>>is only used in contexts where it is clear that it is about TiddlyWiki
>>- Feel free to enter an updated version of artwork that was a 
>>runner-up in a previous competition
>>- Reply to this message with your entry, or any questions
>>- Please give lots of feedback here to encourage the artists
>>
>> Here are the posts about previous artwork competitions:
>>
>> v5.2.0 - 
>> https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ
>> v5.1.23 - https://groups.google.com/g/
>> tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>> v5.1.22 - 
>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>> v5.1.21 - 
>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>
>> The Chrome bug I was referring to is discussed here:
>>
>> https://github.com/Jermolene/TiddlyWiki5/issues/6254
>> https://github.com/Jermolene/TiddlyWiki5/pull/6261
>>
>> Plans for the v5.2.1 release are being discussed here:
>>
>> https://github.com/Jermolene/TiddlyWiki5/issues/6259
>>
>> Best wishes and many thanks,
>>
>> 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/f7f98fe8-77a4-48dc-bed7-3b650bfd9240n%40googlegroups.com.

[tw5] Re: New Release Banner Super-speedy Competition for v5.2.1

2021-11-29 Thread Jeremy Ruston

Hi Atronoush

At this point, the Google Group is still the official forum for TiddlyWiki 
and talk.tiddlywiki.org is still classified as an experiment. I intend to 
revisit this once v5.2.1 is released.

Best wishes

Jeremy

On Monday, November 29, 2021 at 4:46:22 AM UTC Atronoush wrote:

> Hi Jeremy,
>  Most users are now on Talk! Is there any reason you have sent this 
> important post here in old forum!
>  I cannot to reply through Talk and I have to open the old page and reply 
> here!
>  This page is not mobile friendly and I like to use Talk!
>
> Thank you!
> On Tuesday, November 23, 2021 at 9:06:36 PM UTC+3:30 jeremy...@gmail.com 
> wrote:
>
>> As usual, I’d like to hold a competition to design the banner image that 
>> is shown on the splash screen and within the opening HelloThere tiddler.
>>
>> The unusual thing this time around is that we have very limited time. Due 
>> to a serious bug introduced by the latest version of Chrome we are trying 
>> to get v5.2.1 released as soon as possible, perhaps as soon as this weekend.
>>
>> With that in mind, we’ll have to run the competition slightly differently 
>> this time:
>>
>>- Entries will be accepted until Friday morning at 8am UK time
>>- To speed things up, my plan is that I should choose the winning 
>>image (I’m open to discussion here!)
>>
>> The artwork should reflect some of the changes in the new version. I’ve 
>> updated the release note for the prerelease but at this point the 
>> documentation for some of the new features is not complete.
>>
>> https://tiddlywiki.com/prerelease/
>>
>> The other rules/guidelines for the competition are:
>>
>>- The version number (with the correct punctuation) must be clear and 
>>readable even when the banner is shown at a reduced size
>>- The image must be a PNG or JPEG of exactly 560x315 pixels
>>- The bottom 46 pixels will be obscured by the banner text 
>>“What’s new in 5.2.1” when it is displayed within HelloThere
>>- The image need not include the word “TiddlyWiki”. The banner image 
>>is only used in contexts where it is clear that it is about TiddlyWiki
>>- Feel free to enter an updated version of artwork that was a 
>>runner-up in a previous competition
>>- Reply to this message with your entry, or any questions
>>- Please give lots of feedback here to encourage the artists
>>
>> Here are the posts about previous artwork competitions:
>>
>> v5.2.0 - 
>> https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ
>> v5.1.23 - https://groups.google.com/g/
>> tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>> v5.1.22 - 
>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>> v5.1.21 - 
>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>
>> The Chrome bug I was referring to is discussed here:
>>
>> https://github.com/Jermolene/TiddlyWiki5/issues/6254
>> https://github.com/Jermolene/TiddlyWiki5/pull/6261
>>
>> Plans for the v5.2.1 release are being discussed here:
>>
>> https://github.com/Jermolene/TiddlyWiki5/issues/6259
>>
>> Best wishes and many thanks,
>>
>> 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/b65d1aea-2ecb-47d2-9460-a615dfa5e106n%40googlegroups.com.

Re: [Talk TW] [Google Group (Read Only)] [tw5] No CSS while hosting Tiddlywiki on Node.js on Qnap NAS

2021-11-27 Thread Jeremy Ruston

Hi Matt

It looks like the problem is that your wiki is missing a theme plugin. Try 
adding this to your tiddlywiki.info file:


"themes": [
"tiddlywiki/vanilla",
"tiddlywiki/snowwhite"
],

For example:

https://github.com/Jermolene/TiddlyWiki5/blob/master/editions/empty/tiddlywiki.info

Best wishes

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 26 Nov 2021, at 23:04, Matt Kobe via Talk TW  
> wrote:
> 
> 
> Hi. I try to host Tiddlywiki Node.js on my Qnap NAS (with COntainer Station / 
> Docker). I managed to do it successfully but there are 2 problems: CSS is not 
> working (no template) and it doesn't save online.
> 
> Take a look: http://vielebny.myqnapcloud.com:5678/ 
> 
> What is wrong?
> It is hosted in Container Station with Node.js 17.1.0, Tiddlywiki 5.2.0
> 
> Steps I made inside Container: 
> 1. npm install -g tiddlywiki
> 2. tiddlywiki kompendium --init server
> 3. tiddlywiki kompendium --listen
> 4. forever start --spinSleepTime 1 
> ./usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js ./ --server 5678 
> $:/core/save/lazy-all "" "" "" "" 0.0.0.0 ""
> 
> On Synology DSM it worked like a charm. 
> -- 
> 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/bd316685-7300-44a0-8cb3-eb8e3c831f70n%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/00DF6292-E28D-425C-8CCD-EE1BD442D3DE%40gmail.com.

Re: [Talk TW] [Google Group (Read Only)] [tw5] No CSS while hosting Tiddlywiki on Node.js on Qnap NAS

2021-11-27 Thread Jeremy Ruston

Hi Matt

It looks like the problem is that your wiki is missing a theme plugin. Try 
adding this to your tiddlywiki.info file:


"themes": [
"tiddlywiki/vanilla",
"tiddlywiki/snowwhite"
],

For example:

https://github.com/Jermolene/TiddlyWiki5/blob/master/editions/empty/tiddlywiki.info

Best wishes

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 26 Nov 2021, at 23:04, Matt Kobe via Talk TW  
> wrote:
> 
> 
> Hi. I try to host Tiddlywiki Node.js on my Qnap NAS (with COntainer Station / 
> Docker). I managed to do it successfully but there are 2 problems: CSS is not 
> working (no template) and it doesn't save online.
> 
> Take a look: http://vielebny.myqnapcloud.com:5678/ 
> 
> What is wrong?
> It is hosted in Container Station with Node.js 17.1.0, Tiddlywiki 5.2.0
> 
> Steps I made inside Container: 
> 1. npm install -g tiddlywiki
> 2. tiddlywiki kompendium --init server
> 3. tiddlywiki kompendium --listen
> 4. forever start --spinSleepTime 1 
> ./usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js ./ --server 5678 
> $:/core/save/lazy-all "" "" "" "" 0.0.0.0 ""
> 
> On Synology DSM it worked like a charm. 
> -- 
> 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/bd316685-7300-44a0-8cb3-eb8e3c831f70n%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/6D978B93-F581-40ED-B20E-84C8D353B67E%40gmail.com.

Re: [tw5] New Release Banner Super-speedy Competition for v5.2.1

2021-11-26 Thread Jeremy Ruston

Thanks Stobot.

We’ll keep the competition over the weekend as we complete the work on v5.2.1

Best wishes

Jeremy

> On 23 Nov 2021, at 20:10, Stobot  wrote:
> 
> I'll start things off with some very simple options based on "Cascade" which 
> brings to mind waterfalls. I also happen to have a font named Cascadia Code.
> 
> 
> 
> 
> 
> On Tuesday, November 23, 2021 at 1:45:32 PM UTC-5 Ste wrote:
> Yay for trig!!! 
> Who doesn't love triangles 
> 
> On Tuesday, 23 November 2021 at 17:36:36 UTC jeremy...@gmail.com 
>  wrote:
> As usual, I’d like to hold a competition to design the banner image that is 
> shown on the splash screen and within the opening HelloThere tiddler.
> 
> The unusual thing this time around is that we have very limited time. Due to 
> a serious bug introduced by the latest version of Chrome we are trying to get 
> v5.2.1 released as soon as possible, perhaps as soon as this weekend.
> 
> With that in mind, we’ll have to run the competition slightly differently 
> this time:
> Entries will be accepted until Friday morning at 8am UK time
> To speed things up, my plan is that I should choose the winning image (I’m 
> open to discussion here!)
> The artwork should reflect some of the changes in the new version. I’ve 
> updated the release note for the prerelease but at this point the 
> documentation for some of the new features is not complete.
> 
> https://tiddlywiki.com/prerelease/ 
> 
> The other rules/guidelines for the competition are:
> The version number (with the correct punctuation) must be clear and readable 
> even when the banner is shown at a reduced size
> The image must be a PNG or JPEG of exactly 560x315 pixels
> The bottom 46 pixels will be obscured by the banner text “What’s new in 
> 5.2.1” when it is displayed within HelloThere
> The image need not include the word “TiddlyWiki”. The banner image is only 
> used in contexts where it is clear that it is about TiddlyWiki
> Feel free to enter an updated version of artwork that was a runner-up in a 
> previous competition
> Reply to this message with your entry, or any questions
> Please give lots of feedback here to encourage the artists
> Here are the posts about previous artwork competitions:
> 
> v5.2.0 - https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ 
> 
> v5.1.23 - https://groups.google.com/g/ 
> tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
> v5.1.22 - https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ 
> 
> v5.1.21 - https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ 
> 
> 
> The Chrome bug I was referring to is discussed here:
> 
> https://github.com/Jermolene/TiddlyWiki5/issues/6254 
> 
> https://github.com/Jermolene/TiddlyWiki5/pull/6261 
> 
> 
> Plans for the v5.2.1 release are being discussed here:
> 
> https://github.com/Jermolene/TiddlyWiki5/issues/6259 
> 
> 
> Best wishes and many thanks,
> 
> 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/b7b13b4c-bfa1-4486-b7b7-af8f3f602f13n%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/55056DCB-4C87-4213-98B0-08E517FF6778%40gmail.com.

[tw5] Re: TW 5.2.0 + CouchDB ?

2021-11-26 Thread Jeremy Ruston

CouchDB was already established when I started TiddlyWiki 5 in 2011, and 
I'd been following it with interest. Not only did it have solid 
synchronisation functionality, at the time it had intriguing features for 
hosting JavaScript applications, long before Node.js.

I think there were a few reasons that I didn't personally take CouchDB 
further in TiddlyWiki 5:

* TiddlyWiki's internal store needs to offer a synchronous API, but CouchDB 
offers only async APIs. That means there would always be a requirement for 
a sync process between TWs synchronous DB and the CouchDB API, which means 
that TW still has to handle synchronisation
* The difficulties of setting up and running a server of my own
* The lack of CouchDB online services

I was delighted to see Danielo's work with NoteSelf, and it deservedly 
attracted a lot of interest. It demonstrated that CouchDB can be 
retrofitted onto TW5 just like any other database with an async API.

Best wishes

Jeremy

On Thursday, November 25, 2021 at 3:01:05 PM UTC Mark S. wrote:

>
> That was it for me too. In the space of a month, it went from this 
> friendly, reasonably understandable thing, to this borg-like 
> mega-corporation thing. HAL*  doesn't really cater to "little people" -- 
> that's not their mission statement.
>  
> * Advance each letter one step
> On Thursday, November 25, 2021 at 4:09:23 AM UTC-8 swilson...@gmail.com 
> wrote:
>
>> @Jan
>> I was quite keen on noteself, had it set up and everything but then after 
>> the takeover, Couch DB moved past my tolerance for banging my head against 
>> software and it killed it for me.  I suspect that was true for others.
>>
>> On Monday, 22 November 2021 at 20:06:16 UTC cj.v...@gmail.com wrote:
>>
>>> That would be very cool.
>>>
>>> *Comments*
>>>
>>> Other than technical coolness, what would be the advantage of it?  From 
>>> just a user perspective (i.e. forget technical stuff) what reason would I 
>>> have to want that?
>>>
>>> You're talking technological "wowness", but bring it back to "in the 
>>> trenches" "daily usage" terms for a typical user: why should he/she care?
>>>
>>> To investigate how people use TiddlyWiki, what choices they make, and 
>>> why,  you will get more responses over at TiddlyTalk.  It has become the 
>>> fan-favourite.
>>>
>>> Me, I much prefer Google Groups, so I am very happy to reply here:
>>>
>>> *My use cases*
>>>
>>> *Personal TiddlyWiki*
>>>
>>> I store all of my personal TiddlyWiki instances on Google Drive.  
>>> TiddlyWiki aside, if I have no access to the internet, any computer is 
>>> useless to me.
>>>
>>> However, since I have offline access to my files on Google Drive, my 
>>> Chromebook isn't quite the brick folk would think it is ...
>>>
>>> Most important to me is to have access to all of my things in Google 
>>> Drive from any connected device anywhere.
>>>
>>> Having my TiddlyWiki instances tied to databases of a web browser on 
>>> some machine?  Nope, not for me.  Unless whatever you come up with has 
>>> auto-syn with the cloud, I won't be using it.
>>>
>>> A big draw to single-file TiddlyWiki: 10 years from now, however long a 
>>> TiddlyWiki has gathered dust, I can open it and everything will be right 
>>> thre.
>>>
>>> *Multi-User TiddlyWik*
>>>
>>> In this case, TiddlyWiki instances I've setup in virtual machines using 
>>> cloud services.
>>>
>>> So that I can take advantage of all the goodness that is nodejs 
>>> TiddlyWiki.  All of them tiddlers sitting in individual text files, right 
>>> where I want them.
>>>
>>> Although what you describe would be, I think, of no interest to me here, 
>>> the ability to have these TiddlyWiki instances able to access databases on 
>>> these servers, so that the TiddlyWiki instances could have access to data 
>>> coming from other systems?  That would get my attention.
>>>
>>> On Monday, November 22, 2021 at 6:26:58 AM UTC-4 V wrote:
>>>
 Hi. 

 I have been following the TW project for years and I am still very 
 surprised that the community continues to actively support super strange, 
 inconvenient and limited ways of saving and synchronizing – but at the 
 same 
 time all developments using normal technologies on which synchronization 
 could be easy, seamless and safe, such as CouchDB, are not supported in 
 official release and abandoned by community.

 Especially considering the new data storage format in JSON, with which 
 synchronization with object databases has never been easier. It's even 
 easier than maintaining the current server solution on files, which in 
 principle cannot work offline, unlike a solution based on 
 IndexedDB+PouchDB→CouchDB or IndexedDB→Mongo/Posrgres.

 I have used PouchDB adapter from NoteSelf, but it's outdated and 
 contains a lot of bugs. Other solutions were outdated even earlier.

 If IndexedDB/CouchDB solution were supported out of the box, there 
 would be no reason at all to use

Re: [tw5] Known issues with Google Chrome and pdf-Files?

2021-11-24 Thread Jeremy Ruston

Hi Uwe

How large is the PDF?

In the last couple of years Chrome added a limitation on the size of data URIs 
which means that embedded PDFs won't work above a megabyte or two.

The workaround is to save the PDFs separately, and embed them via a 
_canonical_uri tiddler.

Best wishes

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 24 Nov 2021, at 17:32, Uwe  wrote:
> 
> Hi dear helpers, 
> 
> are there any known issues with Google Chrome and pdf-Files? 
> 
> I use Version 96.0.4664.45 (Offizieller Build) (64-Bit) and a fresh 
> downloaded tiddlywiki 5.2.0
> 
> This works with Firefox 94.0.2 (64-Bit):
> 
> [ext[Skript_Facharbeit.pdf|./FW Abschlussarbeit 
> Anforderungen/Skript_Facharbeit.pdf]]
> 
> but not with Google Chrome. I get a new empty page which says "Gets loaded" 
> when I hover the empty tab. But the pdf-file gets never loaded.
> 
> I use timimi as plugins.
> 
> What can I do to solve the problem?
> 
> Greetings,
> 
> merlinuwe
> 
> 
> -- 
> 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/cb26ffc3-8196-4b6a-9e51-e5fe1404152dn%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/D909AED5-A0CF-4782-9777-012B2C8D0F7D%40gmail.com.

Re: [tw5] Sending tm-save-wiki while running as WebServer and avoiding the download dialog

2021-11-24 Thread Jeremy Ruston

Write access is all-or-nothing, so if you grant write access to anonymous users 
they will be able to change anything, not just the tags of interest.

It might be possible to modify $:/config/SyncFilter so that only the tagged 
tiddlers are synced, but at the moment that’s a per-wiki setting that would be 
shared between all users. That could be worked around by using the 
`includeWiki` mechanism to make a clone of the wiki with different settings, 
and then have anon and signed in users access the system through different URLs.

By the way, under Node.js there’s no need to send the tm-save-wiki message; 
changes are synced back to the server automatically. Sending the message just 
engages the usual saver mechanism as in the single file edition.

Best wishes

Jeremy

> On 24 Nov 2021, at 16:43, andres@gmail.com  
> wrote:
> 
> OK, let me preface this by saying that I am trying to selectively get around 
> the read-only mode on my wiki. 
> I usually run my main instance with anon access for readers and authenticated 
> for writers. It's great and does the job.
> But, I want to be able to allow changes by anons for some tiddlers. 
> specifically, I want users to be able to click a button which does an 
> ActionSendMessage of tm-add-tag or tm-remove-tag. But this button only shows 
> up in some tiddlers based on their tags.
> Now, I did add another sendmessage of tm-save-wiki to that button which does 
> save the changed tiddler. Unfortunately, i also triggers the download dialog 
> for the html file which is undesirable.  
> 
> Is there any way I can force a save without getting that dialog?
> Is there a better way I can do what I am trying to do?
> 
> -- 
> 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/545dc38f-4f8e-4652-8706-8aae21b7b42fn%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/27A9CC0E-86DA-445D-B9A7-1B43994BECF0%40gmail.com.

[tw5] Please help us test v5.2.1-prerelease so we can expedite its release

2021-11-23 Thread Jeremy Ruston

The latest v96 version of Chrome has introduced a change that causes some drag
and drop operations in TiddlyWiki to fail. It's so serious that we're planning
to bring forward the release of v5.2.1, and thus urgently need your help with
testing it.

https://tiddlywiki.com/prerelease

Two different fixes for the Chrome 96 issue are required, so there are two
tickets:

* FIXED: https://github.com/Jermolene/TiddlyWiki5/issues/6254 - bug with
dragging titles and links into the default tiddler editor
* IN PROGRESS: https://github.com/Jermolene/TiddlyWiki5/issues/6273 - bug with
dragging titles and links into CodeMirror

Please help us with by testing that your wikis and plugins work with the new
version. There are quite a few exciting new features that many of you will be
excited to test (not all of which are as yet fully documented), but the
feedback we really need is whether the new release accidentally breaks any
existing wikis or plugins.

With that in mind, you can upgrade to the prerelease at:

https://tiddlywiki.com/prerelease/upgrade.html

At this point, I would not recommend running the new version in production:
this is just for testing until we get a little more feedback.

As ever, the first rule of TiddlyWiki applies: make sure you have backed up
your data!

Questions and comments welcome.

Many thanks,

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

[tw5] New Release Banner Super-speedy Competition for v5.2.1

2021-11-23 Thread Jeremy Ruston

As usual, I’d like to hold a competition to design the banner image that is 
shown on the splash screen and within the opening HelloThere tiddler.

The unusual thing this time around is that we have very limited time. Due to a 
serious bug introduced by the latest version of Chrome we are trying to get 
v5.2.1 released as soon as possible, perhaps as soon as this weekend.

With that in mind, we’ll have to run the competition slightly differently this 
time:
Entries will be accepted until Friday morning at 8am UK time
To speed things up, my plan is that I should choose the winning image (I’m open 
to discussion here!)
The artwork should reflect some of the changes in the new version. I’ve updated 
the release note for the prerelease but at this point the documentation for 
some of the new features is not complete.

https://tiddlywiki.com/prerelease/

The other rules/guidelines for the competition are:
The version number (with the correct punctuation) must be clear and readable 
even when the banner is shown at a reduced size
The image must be a PNG or JPEG of exactly 560x315 pixels
The bottom 46 pixels will be obscured by the banner text “What’s new in 5.2.1” 
when it is displayed within HelloThere
The image need not include the word “TiddlyWiki”. The banner image is only used 
in contexts where it is clear that it is about TiddlyWiki
Feel free to enter an updated version of artwork that was a runner-up in a 
previous competition
Reply to this message with your entry, or any questions
Please give lots of feedback here to encourage the artists
Here are the posts about previous artwork competitions:

v5.2.0 - https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/JpxoQdZrAwAJ
v5.1.23 - https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
v5.1.22 - https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
v5.1.21 - https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ

The Chrome bug I was referring to is discussed here:

https://github.com/Jermolene/TiddlyWiki5/issues/6254
https://github.com/Jermolene/TiddlyWiki5/pull/6261

Plans for the v5.2.1 release are being discussed here:

https://github.com/Jermolene/TiddlyWiki5/issues/6259

Best wishes and many thanks,

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/E49F1905-026D-4DE6-B133-48159FC5D2FA%40gmail.com.

[tw5] Re: negative numbers in RevealWidget comparison not ... mathematically accurate?

2021-11-22 Thread Jeremy Ruston

The issue here is that the reveal widget only performs string comparisons, 
and doesn't understand numbers at all.

More complex comparisons including numeric operations can be performed with 
the list widget and filter.

Best wishes

Jeremy

On Monday, November 22, 2021 at 3:56:53 AM UTC cj.v...@gmail.com wrote:

> G'day, 
>
> I think gt and lt in reveal widgets, only works with positive integers.
>
> On Sunday, November 21, 2021 at 10:45:58 PM UTC-4 andres@gmail.com 
> wrote:
>
>> I might be missing something, but given this demo here:
>>
>>   0 gt -5: <$reveal type="gt" default=0  text=-5>yes
>> -1 gt -5: <$reveal type="gt" default=-1 text=-5>yes
>> 
>> -5 gt -1: <$reveal type="gt" default=-5 text=-1>yes
>> 
>>  0 lt -5: <$reveal type="lt" default=0  text=-5>yes
>> 
>> -5 lt  0: <$reveal type="lt" default=-5 text=0>yes
>> 
>> -1 lt -5: <$reveal type="lt" default=-1 text=-5>yes
>> 
>> -5 lt -1: <$reveal type="lt" default=-5 text=-1>yes 
>>
>> I get the following output:
>>
>>  0 gt -5: yes
>> -1 gt -5: 
>> -5 gt -1: yes  <-- -5 is less than -1, not greater
>>  0 lt -5: 
>> -5 lt  0: yes
>> -1 lt -5: yes  <-- -1 is greater than -5, not less
>> -5 lt -1: 
>>
>> Is this a known issue?
>>
>>

-- 
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/3c61d952-bc51-4732-9da9-f32d71c1d158n%40googlegroups.com.

[tw5] Re: gg VS talkW

2021-11-11 Thread Jeremy Ruston

And I meant to add that as Eric suggests, I intend to leave the Google 
Group open, with both forums being used for official postings for the 
moment.

Best wishes

Jeremy

On Thursday, November 11, 2021 at 6:30:17 PM UTC Jeremy Ruston wrote:

> I plan to update tiddlywiki.com to link to talk.tiddlywiki.org shortly, 
> and I think that will be the point where it stops being an experiment.
>
> Best wishes
>
> Jeremy
>
> On Thursday, November 11, 2021 at 5:24:07 PM UTC cj.v...@gmail.com wrote:
>
>> It is all about perspective.  I don't find TiddlyTalk better at all.  It 
>> is a challenge to use the thing.
>>
>> If want to say it is better for the great majority, fine.  But a blanket 
>> statement that it is better, that's it, that's all, for everybody is a load 
>> of poop.
>>
>> On Thursday, November 11, 2021 at 11:52:00 AM UTC-4 Mat wrote:
>>
>>> Google group forum header:
>>>
>>> > Visit our new, *experimental* Discourse discussion: 
>>> talk.tiddlywiki.org
>>>
>>> How long talk.tw gonna be expremental? And whats it take to prove is 
>>> better? And what if is better, we gonna shut this here down then?
>>>
>>> <:-)
>>>
>>

-- 
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/06b619cb-4e7b-43df-9ca1-eaa1c2e8ba09n%40googlegroups.com.

[tw5] Re: gg VS talkW

2021-11-11 Thread Jeremy Ruston

I plan to update tiddlywiki.com to link to talk.tiddlywiki.org shortly, and 
I think that will be the point where it stops being an experiment.

Best wishes

Jeremy

On Thursday, November 11, 2021 at 5:24:07 PM UTC cj.v...@gmail.com wrote:

> It is all about perspective.  I don't find TiddlyTalk better at all.  It 
> is a challenge to use the thing.
>
> If want to say it is better for the great majority, fine.  But a blanket 
> statement that it is better, that's it, that's all, for everybody is a load 
> of poop.
>
> On Thursday, November 11, 2021 at 11:52:00 AM UTC-4 Mat wrote:
>
>> Google group forum header:
>>
>> > Visit our new, *experimental* Discourse discussion: talk.tiddlywiki.org
>>
>> How long talk.tw gonna be expremental? And whats it take to prove is 
>> better? And what if is better, we gonna shut this here down then?
>>
>> <:-)
>>
>

-- 
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/97f4b373-2d02-4715-b2f2-311716029f63n%40googlegroups.com.

[tw5] Re: Export multiple tiddlers by filter to single JSON file from command-line

2021-11-09 Thread Jeremy Ruston

Hi Cade

The render command outputs one file for each tiddler. In this case, the 
files are all called "ChangeLog.json", so they overwrite one another.

The fix is to use a filter expression for the output filename, and generate 
a filename from the title:

tiddlywiki "Data Mart User Manual" --render "[field:change.from[7.0SU2 
(7.0.Local)]][field:change.to[9.0 (9.0.Local)]]" 
"[encodeuricomponent[]addsuffix[.json]]" text/plain 
"$:/core/templates/json-tiddler"

Best wishes

Jeremy

On Tuesday, November 9, 2021 at 5:31:41 PM UTC Cade Roux wrote:

> I am sending a filter to --render but it is only putting one tiddler in 
> the json file.
>
> Current command line:
>
> tiddlywiki "Data Mart User Manual" --render "[field:change.from[7.0SU2 
> (7.0.Local)]][field:change.to[9.0 (9.0.Local)]]" ChangeLog.json 
> text/plain "$:/core/templates/json-tiddler"
>
> Thanks,
>
> Cade
>

-- 
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/8409787f-2e36-490b-b4be-d5034a339bb0n%40googlegroups.com.

[tw5] Re: Bug in TW 5.2.0 in zoomin view.

2021-11-09 Thread Jeremy Ruston

Hi Siniy-Kit,

I can confirm the problem with v5.2.0. I also checked v5.1.23 and it seems 
to have the same problem.

Do you know when the problem was introduced? Did it indeed ever work 
properly?

Best wishes

Jeremy

On Tuesday, November 9, 2021 at 4:45:33 PM UTC Jeremy Ruston wrote:

> Hi Siniy-Kit
>
> Thanks for the report, I'll investigate.
>
> Best wishes
>
> Jeremy
>
> On Sunday, November 7, 2021 at 9:40:19 AM UTC Siniy-Kit wrote:
>
>> Jeremy, help me please. I want to update my template to  new version, but 
>> it works only with zoomin view. 
>>
>> четверг, 28 октября 2021 г. в 15:52:49 UTC+3, Siniy-Kit: 
>>
>>> Old TW5 works good. But now it has bad auto scroll while navigating 
>>> between tiddlers 
>>> For example open this tiddler https://tiddlywiki.com/#Filter%20Operators 
>>> then make zoomin view
>>> [image: Снимок экрана 2021-10-28 154440.png]
>>>  then go back to Filter Operators tiddler and press "range"
>>> [image: Снимок экрана 2021-10-28 154716.png]
>>>
>>> after click you will see this
>>> [image: Снимок экрана 2021-10-28 154853.png]
>>>
>>> I want to see the top of this tiddler, but it autoscroll to middle. Can 
>>> we fix this bug? 
>>>
>>

-- 
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/3864b03a-816a-4878-b703-9b1fa4651fdbn%40googlegroups.com.

[tw5] Re: Bug in TW 5.2.0 in zoomin view.

2021-11-09 Thread Jeremy Ruston

Hi Siniy-Kit

Thanks for the report, I'll investigate.

Best wishes

Jeremy

On Sunday, November 7, 2021 at 9:40:19 AM UTC Siniy-Kit wrote:

> Jeremy, help me please. I want to update my template to  new version, but 
> it works only with zoomin view. 
>
> четверг, 28 октября 2021 г. в 15:52:49 UTC+3, Siniy-Kit: 
>
>> Old TW5 works good. But now it has bad auto scroll while navigating 
>> between tiddlers 
>> For example open this tiddler https://tiddlywiki.com/#Filter%20Operators 
>> then make zoomin view
>> [image: Снимок экрана 2021-10-28 154440.png]
>>  then go back to Filter Operators tiddler and press "range"
>> [image: Снимок экрана 2021-10-28 154716.png]
>>
>> after click you will see this
>> [image: Снимок экрана 2021-10-28 154853.png]
>>
>> I want to see the top of this tiddler, but it autoscroll to middle. Can 
>> we fix this bug? 
>>
>

-- 
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/eaa5db65-1f62-4579-9dd9-e21d9cd96effn%40googlegroups.com.

[tw5] Re: Tiddlywiki file suddently corrupted on save (commas missing in TW inner JSON file)

2021-10-29 Thread Jeremy Ruston

Hi Eric,

Thanks for the detailed report. There is some conditional logic in the JSON 
tiddler output template to handle including a comma before every tiddler 
except the first. It seems that that logic has got corrupted, but it's not 
immediately obvious how.

Are you using any TW plugins? Does the wiki include any JavaScript modules 
(ie tiddlers with type "application/javascript")?

Best wishes

Jeremy


On Friday, October 29, 2021 at 4:19:43 PM UTC+1 Eric N wrote:

> Hi all,
>
> Today I opened my TW file to work on it, and it was blank. Last time I 
> used it it was perfect.
>
> I tried to import that broken file into a fresh empty TW: error message 
> saying that the JSON file was broken, "missing , or ]".
>
> So I checked the file and I had approx 100 instances of "}{" instead of 
> "},{". Weird.
>
> Fixed them all, then I could open the file again and retrieved my work. 
> BUT… I added a new simple tiddler, and saved, and the file got broken 
> again. Was back with my 100 "}{".
>
> Tried to import the fixed file into a fresh empty TW, and add a simple 
> tiddler then saved: got a broken TW file with 100 "}{".
>
> Does anyone knows what is happening ?
>
> Versions:
> - MacOS 11.6
> - Firefox 93.0
> - TW 5.2.0
>
> Best,
> Eric
>
>
>

-- 
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/9e05208c-6888-4a68-b588-9ce750f7d22en%40googlegroups.com.

Re: [tw5] EditTextWidget and the "trap"

2021-10-21 Thread Jeremy Ruston

Hi Charlie,

> 
> From https://tiddlywiki.com/#EditTextWidget:
> 
> One trap to be aware of is that the edit text widget cannot be used to edit a 
> field of the tiddler that contains it. Each keypress results in the tiddler 
> being re-rendered, which loses the cursor position within the text field.
> 
> I thought that was resolved in TW5.2.0.  Based on current documentation, me 
> thinks I likely misunderstood whether or not TW5.2.0 resolved the "trap."

Good catch, we missed that. I’ve updated the docs to reflect the changes in 
v5.2.0.

> Regardless, do note: in some circumstances, the trap does not apply. However, 
> in other circumstances, the trap does apply.  Although not a problem in 
> certain circumstances, I'm thinking best to always avoid use of edit text 
> widget to edit a field of a tiddler in which the edit text widget exists.
> 
> Please download the attached and drag into TiddlyWiki.com to be aware of the 
> trap.
> 
> Apologies if I missed any already existing discussion about this.

The second example in your test tiddler looks like this:

<$vars var2={{!!field2}}>

''__Field 2:__''
<$edit-text field="field2" />

Field 2:<$text text={{{[get[field2]] }}}/>



The problem here is actually not the `<$edit-text>` widget but the `<$vars>` 
widget – it (and all the widgets it contains) gets refreshed each time the 
value of field2 changes.

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/57EC57CE-1FF3-4A07-B689-743CB1589AA2%40gmail.com.

Re: [tw5] Announcing the release of TiddlyWiki v5.2.0

2021-10-04 Thread Jeremy Ruston

> Congrats!  This is very exciting.  Does this affect node.js' storage of 
> tiddlers at all at this time?  i.e. Are they stored as json, or in the .tid 
> file format still?

No, the JSON store area is only used with the single file edition. There are no 
major changes to the way that tiddler files are stored under Node.js

Best wishes

Jeremy

> 
> Matt Lauber
> 
>> On Sunday, October 3, 2021 at 12:38:40 PM UTC-4 jason...@gmail.com wrote:
>> Thank you !!
>> 
>>> On Sun, Oct 3, 2021, 16:41 Jeremy Ruston  wrote:
>>> I'm delighted to announce the release of TiddlyWiki v5.2.0 at:
>>> 
>>> https://tiddlywiki.com/
>>> 
>>> This release is a huge release. It has been under development for 286 days, 
>>> and includes improvements from 33 individual contributors on GitHub. 
>>> There's a graph on GitHub that shows clearly how many people now regularly 
>>> contribute to TiddlyWiki's development:
>>> 
>>> https://github.com/Jermolene/TiddlyWiki5/graphs/contributors?from=2020-12-24=2021-10-03=c
>>> 
>>> My sincere thanks to everyone who has contributed or helped in any way.
>>> 
>>> With v5.2.0 we've been able to address some long-standing frustrations:
>>> 
>>> • It is now possible to use the edit widgets with a different field of 
>>> the current tiddler
>>> • The characters used in fieldnames are no longer restricted to 
>>> lowercase letters, digits, and simple punctuation
>>> • Images can now be dragged directly into the tiddler editor to import 
>>> them and insert [img[foo]] at the cursor position. The title of the image 
>>> tiddler can be edited too
>>> • Macro calls can now be nested. For example <>> <>">>
>>> 
>>> See the release note for the full list of changes:
>>> 
>>> • Some significant performance improvements
>>> • Usability improvements
>>> • New and improved widgets
>>> • New and improved filters
>>> • Improvements to the Markdown, XLSX, KaTeX, Freelinks, Menubar and 
>>> BibTeX plugins
>>> • Improved translations for Catalan, Chinese, French, German and Spanish
>>> • A new Polish translation
>>> 
>>> You can upgrade your existing single file wikis here:
>>> 
>>> https://tiddlywiki.com/upgrade.html
>>> 
>>> For Node.js users, the new version is available on npm:
>>> 
>>> https://www.npmjs.com/package/tiddlywiki
>>> 
>>> As ever, exercise caution when upgrading, and be careful to keep backup 
>>> copies of everything important.
>>> 
>>> Any questions or comments are welcome here, or via GitHub.
>>> 
>>> Finally, I'd like to again express my thanks to everyone helping with this 
>>> project. It's been a difficult time for all of us, but the steady progress 
>>> we're making on TiddlyWiki inspires me for a future where diverse people 
>>> can work together to achieve sustained, meaningful change.
>>> 
>>> 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/CA42E2B7-A3C1-4535-83FA-DBD37DD175B6%40gmail.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/db556eaf-1df6-466e-b658-8936f7af2b44n%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/8422FE14-5FAD-47A9-B5D5-9B5B4872EDF7%40gmail.com.

[tw5] Announcing the release of TiddlyWiki v5.2.0

2021-10-03 Thread Jeremy Ruston

I'm delighted to announce the release of TiddlyWiki v5.2.0 at:

https://tiddlywiki.com/ 

This release is a huge release. It has been under development for 286 days, and 
includes improvements from 33 individual contributors on GitHub. There's a 
graph on GitHub that shows clearly how many people now regularly contribute to 
TiddlyWiki's development:

https://github.com/Jermolene/TiddlyWiki5/graphs/contributors?from=2020-12-24=2021-10-03=c
 


My sincere thanks to everyone who has contributed or helped in any way.

With v5.2.0 we've been able to address some long-standing frustrations:

• It is now possible to use the edit widgets with a different field of 
the current tiddler
• The characters used in fieldnames are no longer restricted to 
lowercase letters, digits, and simple punctuation
• Images can now be dragged directly into the tiddler editor to import 
them and insert [img[foo]] at the cursor position. The title of the image 
tiddler can be edited too
• Macro calls can now be nested. For example <>">>

See the release note for the full list of changes:

• Some significant performance improvements
• Usability improvements
• New and improved widgets
• New and improved filters
• Improvements to the Markdown, XLSX, KaTeX, Freelinks, Menubar and 
BibTeX plugins
• Improved translations for Catalan, Chinese, French, German and Spanish
• A new Polish translation

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html 

For Node.js users, the new version is available on npm:

https://www.npmjs.com/package/tiddlywiki 


As ever, exercise caution when upgrading, and be careful to keep backup copies 
of everything important.

Any questions or comments are welcome here, or via GitHub.

Finally, I'd like to again express my thanks to everyone helping with this 
project. It's been a difficult time for all of us, but the steady progress 
we're making on TiddlyWiki inspires me for a future where diverse people can 
work together to achieve sustained, meaningful change.

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/CA42E2B7-A3C1-4535-83FA-DBD37DD175B6%40gmail.com.

Re: [tw5] Final Call for Testing for TiddlyWiki v5.2.0

2021-10-02 Thread Jeremy Ruston

>> https://tiddlywiki.com/prerelease/plugins/tiddlywiki/innerwiki/ - this wiki 
>> doesn't look right to me. Are there issues with the new release and the 
>> innerwiki plugin? On that page I'm seeing all the innerwikis are blank. Only 
>> the SVG overlays appear.
> 
> That's very helpful thank you, I am now looking into it,

The problem is now fixed, thanks again for picking it up,

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/030C32C9-A67E-4272-8537-4053E6F52050%40gmail.com.

Re: [tw5] Final Call for Testing for TiddlyWiki v5.2.0

2021-10-02 Thread Jeremy Ruston

Hi Brian
> https://tiddlywiki.com/prerelease/plugins/tiddlywiki/innerwiki/ - this wiki 
> doesn't look right to me. Are there issues with the new release and the 
> innerwiki plugin? On that page I'm seeing all the innerwikis are blank. Only 
> the SVG overlays appear.

That's very helpful thank you, I am now looking into it,

Best wishes

Jeremy

> 
> Brian 
> -- 
> 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/CAO5X8Cxy_sMTtaip7qss2krjsPu7nf58aeanNYR3hKOV4P9S4g%40mail.gmail.com.

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

Re: [tw5] Re: Final Call for Testing for TiddlyWiki v5.2.0

2021-10-01 Thread Jeremy Ruston

> My main project is impacted. Some of my macros dealing with json tiddlers 
> are broken. They use the two plugins //modloader// and //json mangler//.

Thank you – any details here would be helpful. What versions of those plugins 
are you using? Which macros are affected?

> On the positive side, it seems that my tiddlers that were too large are now 
> automatically corrected to fit in the current width of the main story.

Excellent – do you mean that the tiddler content previously overflowed its 
background? Perhaps you could share a screenshot?

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/F37F37CE-9D39-4A7C-A082-4D5B66B84412%40gmail.com.

Re: [tw5] Re: Final Call for Testing for TiddlyWiki v5.2.0

2021-10-01 Thread Jeremy Ruston

> Is there a way to test the 5.20 final RC with server mode (simple way) 
> please?

The "master" branch at GitHub contains the prerelease. There are instructions 
here:

https://tiddlywiki.com/#Installing%20TiddlyWiki%20Prerelease%20on%20Node.js

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/C9178A87-91C7-4CF0-BBA8-F044377370FD%40gmail.com.

Re: [tw5] how to add JavaScript to global ?

2021-10-01 Thread Jeremy Ruston

> I post 3 same  posts  about this topic on google group but all of them been 
> deleted, I don't know why if I break the law of the discuss please let me 
> know first I will correct the error. 

Apologies, your posts appear to have been held up in Google's spam protection 
system. I've now approved them all and so you may want to delete the earlier 
ones.

For some reason, for the last several months Google has been flagging many more 
messages than usual, it's a great nuisance.

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/FA88BF89-BD15-4790-AD07-AA8FEA20BC14%40gmail.com.

[tw5] Final Call for Testing for TiddlyWiki v5.2.0

2021-10-01 Thread Jeremy Ruston

The upcoming TiddlyWiki v5.2.0 is now – finally – ready for release. I’m hoping
to get it out over the weekend so this is a final request for help with last
minute checks.

It’s a huge release, with many very significant changes from a diverse range of
contributors. Please join me in thanking them all for working so hard to make
this release such an exciting one.

It would be useful to have feedback on the release note, and whether the
descriptions of the changes make sense. Some of the changes are necessarily
technical things that won’t concern all users, but the aim is for the writing
to be clear enough that anyone can get the general drift.

https://tiddlywiki.com/prerelease/#Release%205.2.0

It would also be a great help if you could try an experimental upgrade of your
own wikis, and give them a once over to make sure everything still works as
expected.

It is recommended to not actually switch over to the new version at this point;
just give it a try with your own data, but don’t upgrade fully until the
official release.

The upgrader is at:

https://tiddlywiki.com/prerelease/upgrade.html

Any feedback or questions are welcome,

Best wishes

Jeremy.

Re: [tw5] A question about Widgets

2021-09-29 Thread Jeremy Ruston

Hi Dhruv,

> I've recently discovered TiddlyWiki and it's excellent. I've always wanted 
> notes that are somewhat interactive-automatic reminders based on the data I 
> put in, managing tasks right inside notes etc.-and TW seems to be wonderful 
> for that sort of thing.

Thank you! It's good to hear TiddlyWiki discovery stories.

> to that effect, though, I needed some custom functionality. I'd like to have 
> timers, where I'd get an audio indication when the timer is done.

There may already be plugins that provide this functionality, I think Eric 
Shulman has some timer tools, and I hope he'll jump in.

> After reading around for a while, making a custom action widget seems my best 
> bet-I'd like to use webaudio, and from what I know JS macros don't allow me 
> access to the DOM.

It's correct that JS macros can't access the DOM.

However, here an action widget may not work either.

> What I want to know is...is there a way to have persistent data inside 
> widgets, such that an expensive computation only takes place once, perhaps 
> when the wiki starts?

No, instances of widgets are ephemeral: they are destroyed and rebuilt as the 
refresh process proceeds. Only the tiddler store can be used for storing state 
data by widgets.

> right now I'm planning to store sound files as base64-encoded data, either 
> inside the widget directly or as a tiddler (somewhat ugly, to be sure, but it 
> seems like the most portable solution) and decoding this data into an audio 
> buffer would take non-negligible time. I would prefer not having to create an 
> audio buffer each refresh cycle.

Not ugly at all: TiddlyWiki handles images the same way, and it works 
surprisingly well with modern browsers.

> More fundamentally...my question is-do widgets get recreated every refresh 
> cycle? or do they only get created once, perhaps when wikification happens, 
> and then they just have refresh called on them?

The lifecycle of a widget is that it gets created, refreshed zero or more 
times, and then destroyed. Many widgets do indeed cache information in the 
widget object instance, but... 

> (Maybe a startup plugin would work well for this, too. I'm not quite 
> sure-I've read quite too much in the past few days, without having enough 
> actual experience to turn all my knowledge into a working product.)

...Yes – anything more substantial is better handled via a "daemon": a long 
lived, global JavaScript object instance to which widgets send messages. In 
TiddlyWiki, daemons are packaged as startup modules.

Here, it sounds like a "tm-play-sound" message with a parameter indicating the 
tiddler containing the sound sample to play would be a reasonable starting 
point.

I don't know if there's any prior work on audio in TiddlyWiki, but I'd 
certainly be interested in improving core support. The blocker in the past was 
always that browsers could only capture audio in enormous WAV format, but by 
now perhaps they can capture straight to compressed MP3.

Best wishes

Jeremy

> 
> Thanks,
> Dhruv
> -- 
> 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/da4533d4-6e49-4205-8aec-bc585c6a89e1n%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/C0CE88B0-6239-4D5B-991D-BD5303DDFE12%40gmail.com.

Re: [tw5] Counting specific words

2021-09-23 Thread Jeremy Ruston

Hi Jean-Pierre
> You made an error in your macro, Jeremy. You should have used $arg$ instead 
> of .

It's actually not an error: it's an alternative way to access the parameters of 
macros. It avoids the problem that otherwise the code would fail with a tiddler 
title containing a closing square bracket.

There are docs here under "Parameters as Variables <<__...__>>":

https://tiddlywiki.com/#Macro%20Definitions%20in%20WikiText

> But it is false nonetheless because it would, for example, cut word "totem" 
> if asked for word "to". My regular expression does not do that thanks to the 
> \b at both ends of the arguments.

Yes, I did that quickly, but indeed I think that splitregexp would be needed to 
make it practical, both to resolve the word boundary issue and the case 
sensitivity issue.

Best wishes

Jeremy.

> 
>> Le jeudi 23 septembre 2021 à 16:45:46 UTC+2, jeremy...@gmail.com a écrit :
>> Another technique is to use the “split” operator to split the string by the 
>> word:
>> 
>> \define count-words(title,word)
>> <$text text={{{ [<__title__>get[text]split<__word__>count[]subtract[1]] }}}/>
>> \end
>> 
>> <>
>> 
>> Using the splitregexp operator instead allows would allow splitting case 
>> insensitively, which might be more useful.
>> 
>> Best wishes
>> 
>> Jeremy.
>> 
 On 23 Sep 2021, at 15:37, Jean-Pierre Rivière  
 wrote:
 
>>> Here it is.
>>> 
>>> ```
>>> \define count-word(word, tid)
>>> {{{ 
>>> [[$tid$]get[text]search-replace:gi:regexp[\b$word$\b],[þ]dump:v[first]search-replace:g:regexp,[]dump:v[final]length[]]
>>>  }}}
>>> \end
>>> 
>>> <>
>>> ```
>>> 
>>> I use a char that should never be within the tiddler, þ in my example. You 
>>> can use another rare character is old English is concerned! I replace every 
>>> occurrence of the word with it, then remove any other character then count 
>>> the length of the result. If you want case sensitive search, just omit the 
>>> `i` flag in the first `search-replace`.
>>> 
> Le mercredi 22 septembre 2021 à 15:14:55 UTC+2, mohamed.e...@vodafone.com 
> a écrit :
> Hi ,
> 
> is there a way to count the number of occurrences of a specific word in a 
> tiddler
> 
> I have serached , but could only find a plugin that counts the total 
> number of words, or total number characters.
> 
>  
 
 
>>> -- 
>>> 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/a30f622a-627f-41a5-a532-4015e0f3faaen%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/ab5296b2-f778-4334-9eef-1892487d6f19n%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/221E8FD9-028C-4828-9326-012B89E321C2%40gmail.com.

Re: [tw5] Counting specific words

2021-09-23 Thread Jeremy Ruston

Another technique is to use the “split” operator to split the string by the 
word:

\define count-words(title,word)
<$text text={{{ [<__title__>get[text]split<__word__>count[]subtract[1]] }}}/>
\end

<>

Using the splitregexp operator instead allows would allow splitting case 
insensitively, which might be more useful.

Best wishes

Jeremy.

> On 23 Sep 2021, at 15:37, Jean-Pierre Rivière  
> wrote:
> 
> Here it is.
> 
> ```
> \define count-word(word, tid)
> {{{ 
> [[$tid$]get[text]search-replace:gi:regexp[\b$word$\b],[þ]dump:v[first]search-replace:g:regexp,[]dump:v[final]length[]]
>  }}}
> \end
> 
> <>
> ```
> 
> I use a char that should never be within the tiddler, þ in my example. You 
> can use another rare character is old English is concerned! I replace every 
> occurrence of the word with it, then remove any other character then count 
> the length of the result. If you want case sensitive search, just omit the 
> `i` flag in the first `search-replace`.
> 
> Le mercredi 22 septembre 2021 à 15:14:55 UTC+2, mohamed.e...@vodafone.com a 
> écrit :
> Hi ,
> 
> is there a way to count the number of occurrences of a specific word in a 
> tiddler
> 
> I have serached , but could only find a plugin that counts the total number 
> of words, or total number characters.
> 
>  
> 
> -- 
> 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/a30f622a-627f-41a5-a532-4015e0f3faaen%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/A3605A80-A13D-4390-A07D-E2A61891BA18%40gmail.com.

Re: [tw5] Re: Question about the TiddlyWiki GG

2021-09-16 Thread Jeremy Ruston

Hi CJ

> Thanks for the confirmation, Jeremy.  That is the way I like things.
> 
> And the push I needed to bail on TiddlyTalk completely.

I think the incident was a momentary misjudgement on the part of an individual. 
It has led to a healthy discussion about what users expect when they write a 
post, and I think the conclusion is that the power to edit should only be used 
in exceptional circumstances. The admins have always had the power to delete 
posts and avoided exercising it except for spam, and so I don't see a reason to 
think that the new power to edit posts would be abused either.

But of course I understand from your comments elsewhere that you have other 
concerns with talk.tiddlywiki.org about usability and simplicity which may well 
be more significant factors in your decisions. I'd just like to say that it is 
an experiment; we're feeling our way to what is right for this community, and 
so necessarily it will take a little time for things to settle down.

Best wishes

Jeremy

> 
> Re TiddlyTalk, I don't know which is worse:  that people's posts can be 
> edited by moderators, or that there is no clear "Terms of Use" or other 
> indicator that posts can be edited by moderators.  I recommend that 
> TiddlyTalk make it very clear that moderators can and do edit posts, and make 
> it very clear what the intent and related policies are.
> 
> BTW, it isn't about trust.  Sure I trust the moderators.  I also trust that 
> to err is human.  We are human
> 
> An analogy:
> 
> Jack arrives at the pub with two black eyes, and the lads ask: "What's with 
> the black eyes?"
> 
> Jack points at his left one and says:  "I was at the concert in the park last 
> night.  In front of me is a lady in a summer dress, and she has a serious 
> wedgie, the dress right up the crack of the bum and it looks ridiculously 
> uncomfortable.  So I decided to help her out by gently tugging on the dress 
> at bum level to remove the wedgie.  That's when she turned around and punched 
> me right in the left eye."
> 
> The lads:  "Oh man.  You moron.  Why the right black eye?"
> 
> Jack:  "When I came to, I realized that I had really upset the lady, and I 
> felt awful about it.  So after I got up off the ground, I stuck out these 
> three fingers with my hand like so, and poked the dress back in."
> 
> The intentions may be good, but are they appropriate?
> 
> Just because one can do something, should one really do it?
> 
> And if you have given yourself the right to do something, should that right 
> be very well indicated and should there be an opportunity for consent?  (i.e. 
> if the user does not give consent, then user cannot join.)
> 
> Something like that.
> 
>> On Thursday, September 16, 2021 at 9:31:57 AM UTC-3 jeremy...@gmail.com 
>> wrote:
>> Hi CJ
>> 
>> That's correct, Google Groups allows admins to delete posts and to reply to 
>> the author, but nothing else.
>> 
>> Best wishes
>> 
>> Jeremy
>> 
>>> On Thursday, September 16, 2021 at 1:19:39 PM UTC+1 cj.v...@gmail.com wrote:
>>> Am I correct in saying that GG moderators do not and cannot edit posts by 
>>> members?
> 
> -- 
> 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/59dc52bb-0fe0-414b-885a-6d97bb764505n%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/FF89D079-56D8-494B-8600-675F3B1FBFAD%40gmail.com.

[tw5] Re: Question about the TiddlyWiki GG

2021-09-16 Thread Jeremy Ruston

Hi CJ

That's correct, Google Groups allows admins to delete posts and to reply to 
the author, but nothing else.

Best wishes

Jeremy

On Thursday, September 16, 2021 at 1:19:39 PM UTC+1 cj.v...@gmail.com wrote:

> Am I correct in saying that GG moderators do not and cannot edit posts by 
> members?

-- 
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/0e235af7-29a0-46b9-9dc4-46ef0e867996n%40googlegroups.com.

Re: [tw5] Re: ISO week date format template

2021-09-14 Thread Jeremy Ruston

OK, I'm thinking now:

* To change the token for week number to `dd`
* To add a new token for day of year `` and `0`

Best wishes

Jeremy

On Tuesday, September 14, 2021 at 12:34:53 PM UTC+1 PMario wrote:

> On Tuesday, September 14, 2021 at 10:19:10 AM UTC+2 Jeremy Ruston wrote:
>
> If we stick with `` for day of week, perhaps we'd use `d` for day 
>> of year? 
>
>
> They are very similar. For me it's difficult to recognise a difference. 
> ... 
>  
>
>> Perhaps that's excessively long, but it does seem like a very unusual 
>> requirement in any case; only users who were looking for it would want it, 
>> if you see what I mean.
>
>
> You are right. Only users that search for it will use it. 
>  
>
>> > I think 0dd and dd should be an option. I think 0dd is needed to get 
>> easy default sort order. 
>>
>> The day of week is a number from 1 to 7, so zero padding doesn't seem 
>> useful.
>>
>
> Right. My bad. 
>
> But d day of year may have 1 or 2 leading zeros. ... 
>
> -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/151aa0b9-7b3c-4056-90e5-46e1d2686f89n%40googlegroups.com.

Re: [tw5] how to use the tm-navigate command?

2021-09-14 Thread Jeremy Ruston

The tm-navigate message cannot be issued directly from wikitext, instead you 
can use the <$action-navigate> widget:

https://tiddlywiki.com/#ActionNavigateWidget

Best wishes

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 14 Sep 2021, at 09:26, imleg...@gmail.com  wrote:
> 
> I do a lot of rearch and can't find a example. 
> 
> I check the manual and follow it, then write the command like this: 
> 
> <$action-sendmessage $message="tm-navigate" $param="$:/ControlPanel" 
> $event="navigateTo"/>
> 
> But it not worked. How to use it.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/77d7a949-9a22-4381-9d54-59a5febee7f6n%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/EE41A0CA-6974-4381-B318-D3E32C9B65B9%40gmail.com.

Re: [tw5] Re: ISO week date format template

2021-09-14 Thread Jeremy Ruston

> The "dd" format is reminding of the n umerical notation in the month 
date, but at the same time may be confusingly similar and suggesting a two 
digit representation. "" feels more related to the existing weekday 
name notations, one could think that longer token indicates lesser units in 
this case. I'm not sure which one to prefer.

That's roughly my thinking too. In particular, there is a precedent for 
longer tokens generating shorter substitutions.

> How could a day of year-token fit into this? yDDD?

If we stick with `` for day of week, perhaps we'd use `d` for day 
of year? Perhaps that's excessively long, but it does seem like a very 
unusual requirement in any case; only users who were looking for it would 
want it, if you see what I mean.

> I think 0dd and dd should be an option. I think 0dd is needed to get easy 
default sort order. 

The day of week is a number from 1 to 7, so zero padding doesn't seem 
useful.

Best wishes

Jeremy

On Tuesday, September 14, 2021 at 7:38:18 AM UTC+1 PMario wrote:

> On Monday, September 13, 2021 at 8:46:04 PM UTC+2 Jeremy Ruston wrote:
>
> Now that I started to write out the rationale for the choice of "", 
>> I'm realising that perhaps I think "dd" might be a better choice. What do 
>> others think?
>>
>
> I think 0dd and dd should be an option. I think 0dd is needed to get easy 
> default sort order. 
>
> -mario
>
>

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

Re: [tw5] Re: ISO week date format template

2021-09-13 Thread Jeremy Ruston

> Nice to hear it is already taken care of, thank you.
> I was almost on my way to make a pull request myself, as an exercise in 
> contributing to an open source project, but I am not sure about the customs, 
> if I should create an issue first.

It's probably usually best to open an issue (or comment on an existing one) for 
discussion before preparing a PR to minimise the chances of it subsequently 
being rejected for a reason you haven't foreseen. We are always keen to welcome 
new contributors, and you'll find plenty of help and encouragement when you 
need it.

> Of curiosity, may I ask why you chose "" as the token for week date 
> number, instead of the "D" symbol used in the ISO 8601 formats notation?

We don't currently use any single character tokens, originally to minimise the 
chances of triggering any boilerplate text in the template (ie, a format string 
could be "The year is ").

Now that I started to write out the rationale for the choice of "", I'm 
realising that perhaps I think "dd" might be a better choice. What do others 
think?

Best wishes

Jeremy

> 
> 
>> On Sunday, 12 September 2021 at 12:58:44 UTC+2 jeremy... wrote:
>> Thanks CJ for the cunning workaround. For v5.2.0 I've now added a new date 
>> format string token "" for directly obtaining the ISO weekday number (ie 
>> 1=Monday, 7=Sunday):
>> 
>> https://tiddlywiki.com/prerelease/#DateFormat
>> 
>> (It'll take a few minutes from this posting until the change shows up).
>> 
>> Best wishes
>> 
>> Jeremy.
>> 
>>> On Sunday, September 12, 2021 at 11:26:51 AM UTC+1 J N wrote:
>>> Thank you for the suggested workaround.
>>> 
>>> Is it possible to define that operation in a tiddler and then refer to the 
>>> value in a template for creating a new journal entry?
>>> 
>>> If so, maybe one could also use JavaScript directly to provide the value 
>>> for the tiddler template.
>>> 
>>> 
 On Saturday, 11 September 2021 at 15:19:35 UTC+2 cj.v wrote:
   Oops, typo in the last "search-replace"  
 
 "[Thu],[7]" should be "[Sun],[7]"
 
 The dangers of mindless cut and paste ...
 
> On Saturday, September 11, 2021 at 12:49:23 AM UTC-3 Charlie Veniot wrote:
> G'day,
> 
> Just to get the conversation started, try this in a new tiddler in some 
> tiddlywiki:
> 
> <$vars dateNow= <>>
> 
> {{{ 
> [search-replace:[Mon],[1]search-replace:[Tue],[2]search-replace:[Wed],[3]search-replace:[Thu],[4]search-replace:[Fri],[5]search-replace:[Sat],[6]search-replace:[Thu],[7]]
>  }}}
> 
> 
> 
> 
> 
> -- 
> 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/4101de67-bd22-489b-bdd7-3b98ab99be3fn%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/09BB5EEE-4634-4EC0-BD73-7C914156AC60%40gmail.com.

[tw5] Re: ISO week date format template

2021-09-12 Thread Jeremy Ruston

Thanks CJ for the cunning workaround. For v5.2.0 I've now added a new date 
format string token "" for directly obtaining the ISO weekday number 
(ie 1=Monday, 7=Sunday):

https://tiddlywiki.com/prerelease/#DateFormat

(It'll take a few minutes from this posting until the change shows up).

Best wishes

Jeremy.

On Sunday, September 12, 2021 at 11:26:51 AM UTC+1 J N wrote:

> Thank you for the suggested workaround.
>
> Is it possible to define that operation in a tiddler and then refer to the 
> value in a template for creating a new journal entry?
>
> If so, maybe one could also use JavaScript directly to provide the value 
> for the tiddler template.
>
>
> On Saturday, 11 September 2021 at 15:19:35 UTC+2 cj.v wrote:
>
>> *  Oops, typo in the last "search-replace"  *
>>
>> "[Thu],[7]" should be "[Sun],[7]"
>>
>> The dangers of mindless cut and paste ...
>>
>> On Saturday, September 11, 2021 at 12:49:23 AM UTC-3 Charlie Veniot wrote:
>>
>>> G'day,
>>>
>>> Just to get the conversation started, try this in a new tiddler in some 
>>> tiddlywiki:
>>>
>>> <$vars dateNow= <>>
>>>
>>> {{{ 
>>> [search-replace:[Mon],[1]search-replace:[Tue],[2]search-replace:[Wed],[3]search-replace:[Thu],[4]search-replace:[Fri],[5]search-replace:[Sat],[6]search-replace:[Thu],[7]]
>>>  
>>> }}}
>>>
>>> 
>>>
>>>
>>>

-- 
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/658a023e-60be-4ae1-8dc7-4813b0fe7e3en%40googlegroups.com.

[tw5] Re: Can a tiddler be setup to not allow being overwritten?

2021-09-08 Thread Jeremy Ruston

Tthis is one of those reasonable sounding features that has a surprising 
degree of inwardness when one looks into it. Implementing true read-only 
tiddlers would have a substantial impact on the architecture of TiddlyWiki:

* At the moment, write operations cannot fail, and so there is no error 
handling in wikitext. If we introduce operations that can fail it seems 
likely that we'd also have to incorporate error handling features, which 
would considerably complicate even simple operations
* Performing the access control lookups would have an impact on 
performance. The core is architected so that lookup operations on the 
tiddler store are as fast as possible (a single JS object lookup), and so 
adding even a little bit more logic will end up multiplying the overall 
execution time of the store component many times over

So, it was an explicit early design decision that operations on the tiddler 
store cannot fail. Note that client-server configurations have much more 
scope to block tiddler modifications being synced in one direction or the 
other.

Best wishes

Jeremy

On Tuesday, September 7, 2021 at 1:09:01 AM UTC+1 cj.v...@gmail.com wrote:

> Just to re-iterate, there are several ways an important tiddler can be 
> unintentionally fricasseed.
>
> The most likely from a brain-fart moment, examples off the top o' me 
> noggin':
>
>- delete button
>- drag and drop a crap version that overwrites the good version
>- bad set-field (or other action widget) that deletes a tiddler, or 
>completely/partially overwrites the tiddler
>
> I'm sure there are other Darwin Award moments, like creating and saving a 
> new tiddler with the name of an already existing tiddler, and being just 
> plain old too numb-in-the-moment-deer-in-the-headlights to really clue into 
> the pending "this is going to leave a scar" moment.
>
> Just when one thinks one can trust oneself to not pull an award-winning 
> dumb move, the IQ-stealing fairy is waiting just around the corner for a 
> clobbering.
>
>
>
> On Monday, September 6, 2021 at 8:50:16 PM UTC-3 TW Tones wrote:
>
>> On Talk.tiddlywiki.com I would mention Mario and Charlie here. 
>>
>> Mario I would like to support part of what Charlie seems to be concerned 
>> with. I have a few wikis where I have delete inhibit on selected tiddlers, 
>> typically the master tiddler that is a compound tiddler, meaning it has 
>> many subtiddlers. Deleting that would result in loss. I have the real 
>> delete button behind more, so I can get to it. I also have edit inhibit 
>> because I rarely change the master tiddler but want to edit the 
>> subtiddlers. A conditional edit button simply helps stop me clicking on the 
>> wrong edit button. All this can be circumvented, but it helps improve the 
>> user Interface by avoiding the display of buttons that are not relevant and 
>> could initiate actions that cause a waste of time if not damage.
>>
>> Tones
>>
>>
>> On Monday, 6 September 2021 at 19:07:42 UTC+10 PMario wrote:
>>
>>> On Monday, September 6, 2021 at 3:01:25 AM UTC+2 cj.v...@gmail.com 
>>> wrote:
>>>
>>> No worries.  I'll train my thoughts on obfuscation, risk-mitigation 
 design/strategies, and automated monitoring/repairing processes.

>>>
>>> IMO obfuscation is wasting time, other than removing the buttons, that 
>>> are not needed. Which I would define as "modifying the UI according to the 
>>> usecase" ;)
>>>
>>> With nodejs you should be able to establish a "batch process" that runs 
>>> once a day and checks, if some important shadow tiddlers have been 
>>> overwritten. I would consider this as "Plan B".
>>>
>>> Plan A - IMO the easiest way would be to trust your users and tell them 
>>> what's going on, and what's important. Having Plan B will then only be 
>>> needed if someone changes something by accident. 
>>>
>>> just a thought
>>> mario
>>>
>>>

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

Re: [tw5] Create a wiki save button inside a tiddler?

2021-09-07 Thread Jeremy Ruston

Hi Mike

Include the following text to make a copy of the “save wiki” button wherever 
you need it:

{{$:/core/ui/Buttons/save-wiki}}

Best wishes

Jeremy

> On 7 Sep 2021, at 08:30, mikjs...@gmail.com  wrote:
> 
> 
> Is it possible to create a wiki save button inside a tiddler? I use 
> AndTidWiki on Android and have a default tiddler which is the main screen for 
> my GtD. It would be much more helpful to have a save whole wiki button here 
> rather than having to screen up to the main panel each time
> 
> Thanks!
> 
> mike
> 
> -- 
> 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/a601f2e0-bba6-48ca-854a-14086bba468bn%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/33A388BD-E511-464C-8F98-655C99360909%40gmail.com.

[tw5] New TiddlyDesktop v0.0.15-prerelease.2

2021-08-28 Thread Jeremy Ruston

A new v0.0.15-prerelease.2 of TiddlyDesktop is available here:

https://github.com/Jermolene/TiddlyDesktop/releases/tag/v0.0.15-prerelease.3 


Compared to v0.0.14, this new version:
Updates nw.js to v0.55.0 with the latest version of Chromium
Fixes problems with confirm/alert/prompt with the latest version of Chromium
Please reply with any feedback or questions,

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/21BDB0EB-5A44-4C7E-AD0D-21EF2223C09B%40gmail.com.

Re: [tw5] Delete of tiddlers: Trying to setup consistent confirmation messages

2021-08-27 Thread Jeremy Ruston

Hi Charlie

You may be running into something a little strange: we only request
confirmation when deleting a tiddler that has a non-blank text field. I
think it was a well meaning attempt to reduce the chattiness of the UI when
deleting inadvertently created new tiddlers, but it's probably something we
should review now.

Best wishes

Jeremy



On Fri, 27 Aug 2021 at 19:54, Charlie Veniot  wrote:

> G'day all,
>
> I just noticed some inconsistent behaviour (maybe inconsistent by design?)
> with the delete tiddler button:
>
>- for a tiddler in edit mode, clicking the delete button prompts with
>a confirmation "Do you wish to delete ...", which gives the opportunity to
>cancel if the button was clicked by mistake
>- for a tiddler in view mode, clicking the delete button does not
>prompt with any confirmation at all, immediately deleting (so not
>opportunity to cancel a possible mistake.)
>
> I find that inconsistency annoying.  I'd like to fix that in my
> TiddlyWikis, but I'm not sure how to go about it.  Looking at
> the $:/core/ui/Buttons/delete hasn't given me any clues.
>
> Could somebody point me in the right direction to setup consistent
> behaviour upon pressing the delete button?
>
> --
> 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/fbae88e1-99b6-4584-8cc4-651c3a6ba2b5n%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/fbae88e1-99b6-4584-8cc4-651c3a6ba2b5n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

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

Re: [Talk] [Google Group (Read Only)] [tw5] 2D tiddler grid (?): nulis.io

2021-08-27 Thread Jeremy Ruston

Thanks Anders, it's very nicely done.

It is fully open source; there's more information on their GitHub page 
https://github.com/lumenwrites/nulis

Worth noting that it is heavily inspired by Gingko, which came out a few years 
ago:

https://gingkoapp.com/

At some point I was in touch with the creator of Gingko and learned that it in 
turn was somewhat inspired by TiddlyWiki...

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/17594847-03A5-4A7F-9526-CB4CBE6990E3%40gmail.com.

Re: [tw5] "I moved to Discourse" - add your name too?

2021-08-25 Thread Jeremy Ruston


Hi Ed

Apologies, I'm taking a short holiday break, but wanted to jump in to 
reassure you (and others) of a few points:

a) talk.tiddlywiki.org is an experiment for the moment, but my hope is that 
we will migrate all of our Google Groups to the new service (and set the 
old groups to "read-only" so that they will continue to be available as an 
archive)

b) the idea of migrating from Google Groups has been floating around for 
many years, but I've always been very cautious about. A great friend of 
TiddlyWiki called Boris Mann kindly offered to help get us set up on the 
new platform, an offer which was meaningful because he already runs several 
other instances of Discourse

c) It has to be an experiment because we want to bring everyone with us to 
the new platform. There's been a lot of great feedback about what people 
like about the new forum, and what they struggle with. The volunteers are 
working hard to tweak the system to suit everyone

d) My own experience is that Discourse is superior to Google Groups in 
almost every way, but I don't underestimate the friction of making the 
change

Lastly, thank you for sharing your situation with us. Your perspective is 
inspiring, and there's a lot for us to learn about inclusivity. In the 
software development industry a certain amount of lip service is paid to 
accommodating users with visual, auditory or motor difficulties, but very 
little to cognitive impairment. I suffered from some of it when my long 
COVID was at its worst, which certainly left me thinking that these 
considerations would only increase in importance.

Best wishes

Jeremy



On Wednesday, August 25, 2021 at 12:18:33 PM UTC+1 barro...@gmail.com wrote:

> Someone say herding cats?  Let me testify, just like with walking into 
> Mordor, you don't just herd cats.  You lead them.  And if they don't feel 
> like following, it probably won't be happening...
>
> Yes, I know I'm no help...
>
> Will Discourse threads be indexed by Google in general?  I'm sure a few 
> people (myself included) depend on the ease of being able to find TW info 
> from this group (as well as TW official static pages) on normal Google web 
> search results (I believe TW Reddit content also will come up in web 
> searches)
> On Tuesday, August 24, 2021 at 11:14:09 PM UTC-4 eddi...@gmail.com wrote:
>
>> [image: My Brain.jpg]
>>
>> Thank You! I do have trouble communicating my thoughts clearly and keep 
>> this photo on my phone when I run into situations where I think I may need 
>> to explain why (they do this yearly and there has been no change in the 3/4 
>> inch diameter hole in a very big head LOL). I am not looking for pity but 
>> hoping to help make your point. We are all using TiddlyWiki with our own 
>> understanding and skills. You are also absolutely right, the condensed 
>> updates are as much or more than I can handle personally as is (you guys 
>> are way too busy!) LOL. I keep up with these just to make sure what few 
>> plugins I use are not known or expected to break as TW evolves. Also, I 
>> think it is important that Jeremy has a say in which he wants to use. 
>> Realizing of course the real discussion is happening in GIT but all of that 
>> is way over my head now anyway. Still his announcements about new features 
>> and explanations on how to use those when questions come up here as well as 
>> the base TiddlyWiki without addons or plugins (or at least as minimal a set 
>> as possible) have been extremely helpful to me. So where he goes I need to 
>> go because he knows when he adds new features he needs to make the 
>> explanations and use of them as intuitive and user friendly (there's an old 
>> term!) as possible and most likely with those explanations in mind. 
>> TiddlyWiki itself is the best example that I can think of due to its 
>> simplicity in a way. It has amazing capabilities but an ease of use 
>> unparalleled by programs that have almost none of the customization 
>> capabilities allowing it to be used as needed. I have seen efforts to write 
>> books and manuals fail not due to a lack of effort, knowledge, or ability 
>> but a lack of being able to keep up with the pace TW5 evolves which is an 
>> amazing example of how much work Jeremy and those who help him have 
>> put into this over the years! To me this group does represent a record of 
>> all that effort and progress he might prefer continues here? 
>>
>> But not trying to argue for or against with anyone. LOL I know longer 
>> have those skills either (happily). I am Just trying to keep up, which is 
>> probably a fool's errand anyway but, also offer a reminder that unless 
>> there is a fork planned I personally feel no one should just take the 
>> community he has built here and put it over there without him at least 
>> being a part of that decision.  
>>
>> Thanks!
>>
>>
>> On Mon, Aug 23, 2021 at 10:20 PM strikke...@gmail.com <
>> strikke...@gmail.com> wrote:
>>
>>> Tony,
>>> Ed did not complain. He would not

Re: [tw5] Re: I Think I Hacked TiddlyWiki

2021-08-22 Thread Jeremy Ruston



With a bit of creativity, practically anything is possible! You’re right in 
> that the JS could not have DIRECT access to the user’s file system, but as 
> explained in 
>
> https://nakedsecurity.sophos.com/2016/06/20/ransomware-thats-100-pure-javascript-no-download-required/,
>  
> one could simply use JS to connect to a server to install a malicious exe, 
> which it could then run. 
> Essentially, the JS could easily apply a cipher to the file to thus 
> “encrypt it”, and use the exe to rewrite the file content with this 
> encrypted text. 
> The exe could also handle deletion of backups, or pretty much anything 
> else needed. 
>

Hmm that article is about tricking users into double-clicking on .JS files 
so that they run under the Windows Scripting Host, and doesn't really cover 
the situation of TiddlyWiki.

Best wishes

Jeremy

 

>
> On Sat, Aug 21, 2021 at 7:02 PM Scott Simmons (Secret-HQ) <
> goo...@secret-hq.com> wrote:
>
>> On Tuesday, August 17, 2021 at 9:12:15 AM UTC-4 flanc...@gmail.com wrote:
>>
>> What makes this more dangerous than the iframe is that it has DIRECT 
>>> ACCESS to your TW instance, so practically anything can be done. For 
>>> example, I could steal your tiddlywiki instance, encrypt it, and hold it 
>>> for ransom, as soon as your page loaded.
>>>
>>
>> Just to make sure I'm understanding correctly:  That *particular* attack 
>> wouldn't yield much fruit, would it?  The attacker would have an encrypted 
>> version of TiddlyWiki only xe could access, but the original user would 
>> still have the version xe opened on xir local hard drive or the Web site xe 
>> loaded the page from in the first place.  All that would be encrypted for 
>> ransom would be the session-specific instance of that file, not the source 
>> file (which the browser can't encrypt and save over on the fly).
>>
>> Or am I misunderstanding?
>>
>> -- 
>> 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/25edd7f6-9dcc-4109-8fb8-51884c6382acn%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/9f71bb5b-0882-41f5-ac01-b7e4305f0cb5n%40googlegroups.com.

Re: [tw5] Seeking common misunderstandings

2021-08-18 Thread Jeremy Ruston

Hi Soren,

> I'm working on adding a chapter (or back-matter section, not sure yet) called 
> "Common Misunderstandings" to Grok TiddlyWiki. Currently I have two sections:

Excellent idea, I think that will be very helpful.

> Macros are not function calls
> Constant strings cannot be combined with transclusions
> Are there other common misunderstandings – in terms of incorrect mental 
> models of how TiddlyWiki operates, or things one might expect to work that 
> don't – that come up here or elsewhere that you'd like to see documented in 
> such a section?

The first one I thought of was the way that  >}}> doesn't 
work, but I see that you covered that in the 2nd example.

> Feedback on the drafts of the two existing sections would be welcome as well:
> 
> https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
>  

Excellent stuff, it's great to see how you can write from the perspective of 
beginners while being such a knowledgable and advanced user yourself.

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/af072926-33d7-4414-840e-e0741671f52bn%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/5FB899DA-51D2-4BE9-BF71-3804717CA118%40gmail.com.

Re: [tw5] Do you already use https://talk.tiddlywiki.org/ ?

2021-08-17 Thread Jeremy Ruston

The new Discourse forum at https://talk.tiddlywiki.org/ is an experiment at 
this stage. At the moment, there's two way sync with Google Groups, but if 
people like the new system then we will migrate fully over to it.

We'll be discussing it at the TiddlyWiki community call in a few hours time:

https://talk.tiddlywiki.org/t/aug-17th-2021-community-call-core-savers-syncers-upload-plugin-discourse-forum/28

Best wishes

Jeremy.

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 17 Aug 2021, at 09:23, Mohammad Rahmani  wrote:
> 
> 
> Thanks for sharing BTC!
> I would like to have one central place to be informed about TW!
> 
> Is this the one I wished?
> 
> 
> 
> Best wishes
> Mohammad
> 
> 
>> On Tue, Aug 17, 2021 at 12:22 PM BurningTreeC  
>> wrote:
>> Hi tiddlywikians,
>> 
>> there's this new TiddlyWiki forum at https://talk.tiddlywiki.org/
>> 
>> Is the google group still a thing for you or are you going to move to the 
>> new Forum?
>> 
>> just out of interest :)
>> 
>> Best wishes,
>> BTC
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/d1c6b96b-968b-4f67-a602-f7dd1a17d905n%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/CAAV1gMDVzrajBKsk-rNF910mhnV-a79UMD%3Dfk41ojdpkoReq_Q%40mail.gmail.com.

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

Re: [tw5] Stupid Question: Add button to ViewBar(?) with JS Only.

2021-08-16 Thread Jeremy Ruston

Hi Finn

Thanks Jeremy! I was able to get the button to show-up! I have a few more 
> stupid questions, if you have the time, mainly related to styling these 
> buttons and to wikitext.
>
> Firstly, I would like the colour of the button to change onhover. While 
> this is simple to do with CSS, I imagine it needs some sort of special 
> stylesheet (styles.tid, perhaps), to do this. It would be great if you 
> could share the syntax needed for this.
>

As you inferred, there are two parts: (a) assign a class to the button and 
(b) create a stylesheet with a :hover rule. Stylesheets are ordinary 
tiddlers with the tag "$:/tags/Stylesheet", and (usually) the type 
"text/css".

For dynamic effects, one can also use the wikitext type 
"text/vnd.tiddlywiki" and use wikitext primitives like <$list> to generate 
stylesheet rules dynamically.
 

> Next and lastly, I am a bit confused as to how to implement this with JS. 
> I would like to be able to get the tiddler text, and then call a JS 
> function with this JS text as an argument. How could I go about getting the 
> tiddler text when the button is clicked, and then have this transfer over 
> to JS for the function call?
>

It sounds like you want to make a view toolbar button that calls a JS 
function to do something with the text of a tiddler. There are quite a few 
ways to do that, and the precise details will depend on what you're trying 
to achieve. What does the JS function do with the text? Does it need to 
update the tiddler value in the store?

The key types of JS modules in TW5 are as follows:

* JS macros for simple deterministic text transformations that don't have 
any side effects (eg they cannot modify the tiddler store)
* Widgets for dynamic components that reflect values in the tiddler store, 
and automatically refresh if the values in the store change
* Filter operators for operations on lists of items. Again, they mustn't 
have side effects
* Savers for saving entire TiddlyWiki HTML files
* SyncAdaptors for saving/loading individual tiddlers to remote servers

There are some docs at https://tiddlywiki.com/dev, and it's worth browsing 
the code over at GitHub:

https://github.com/Jermolene/TiddlyWiki5/tree/master/core/modules

Sorry if these questions are a bit basic, but I have yet to find a good 
> resource for learning WikiText/TW Syntax, so I have to rely on the 
> community and you. 
>

Not at all. It sounds like you've plenty of experience of HTML, CSS and JS 
which puts you in a great position. Some of it will be a matter of 
unlearning some of the usual ways of doing things. TiddlyWiki is a 
different beast: it tries to make it easy to write complex apps 
declaratively by composing a small number of higher level primitives. But 
it also tries to have it's cake and eat it, in the way that it tries to 
expose the underlying flexibility of HTML, CSS and JS.

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/9c0c867b-1876-42b6-b987-bf4af5e671a1n%40googlegroups.com.

Re: [tw5] Stupid Question: Add button to ViewBar(?) with JS Only.

2021-08-16 Thread Jeremy Ruston

> I've been working on my plugin 
> (www.github.com/flancast90/text-to-speech-in-tw5), and would like to add a 
> button to the tiddler viewBar (I think that's what it's called, the place 
> containing the More Actions, Lose, etc. buttons).
> 
> Is there a way I can do this in JS only? I am quite lost, so I'll need to 
> know the file structure, code, etc.

Adding a new view toolbar button requires a tiddler with the tag 
$:/tags/ViewToolbar, a “caption” field, an optional “description” field, and 
the “text” field containing the button itself (and any associated dropdowns). 
See the core buttons for examples:

https://github.com/Jermolene/TiddlyWiki5/tree/master/core/ui/ViewToolbar 


So, the usual approach is to bundle JS modules along with any necessary 
wikitext tiddlers into a plugin so that they can be distributed/updated as a 
single unit.

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/B007F351-61B4-42A1-92C5-B8B5A15BE1F5%40gmail.com.

Re: [tw5] Just a goofy thought: a way to get javascript into a Tiddler

2021-08-16 Thread Jeremy Ruston

Hi Finn

> On 16 Aug 2021, at 17:22, Finn Lancaster  wrote:
> 
> I don't have much experience with JS macros in TW, but I can imagine it would 
> be the same, especially if there is no sanitisation whatsoever. As to 
> eliminating iframes, normally there is no way to break-out of it. However, in 
> the case of my Proof-of-Concept with TW, the localStorage is global, and can 
> be accessed by ANY SITE. This is just one more reason I believe TW should use 
> browser cookies: they are not accessible from inside iframe, and have more 
> options for security and access.

A big part of the problem is that browsers treat all file:// URIs as a single 
origin, and don’t apply the usual same origin checks. That means that it is 
pretty much impossible to securely use local storage from a file:// URI.  For 
the same reason, browser cookies are no better than local storage.

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/BB56CA48-E0B5-4499-AF5B-7C357788DB01%40gmail.com.

Re: [tw5] Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

2021-08-15 Thread Jeremy Ruston

Hi Josiah

> A compounding factor is that devs of older stuff are often NOT around to fix 
> for compliance with new.
> The issue is the users who relied on what they thought were kosher tools that 
> STOP working that the author won't fix.

Indeed.

>  Jeremy: |  do plan to update the release note with a more prominent warning 
> of the impact of this change.
> 
> Good! IMHO, it might also be worth mentioning that their tool of concern 
> would continue to run fine under previous versions of TW. 
> For working apps mostly it is NOT needed you upgrade! 
> (("Upgradeitis" is a serious modern disease. :-))

>From the core perspective we really want people to upgrade actively used wikis 
>to each new version because it’s expensive and complex to offer support for 
>old versions. For example, if we had a user on v5.1.23 who was holding back 
>updating to v5.2.0 then that user wouldn’t be able to benefit from bug fixes 
>in subsequent releases. If they reported a bug that was then fixed by the core 
>team they wouldn’t be able to get the fix without updating.

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/5FED7921-F486-4CB1-9EF1-60A674723458%40gmail.com.

Re: [tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

2021-08-15 Thread Jeremy Ruston

> But it is slightly worrying that Simon Kilner's(?) TOGGLER macro (actually a 
> re-write of something originally on Classic?) is kinda deprecated now. And 
> NEVER was BEFORE.
> 
> The tool WORKED forever already.
> 
> And your formal explanation kinda misses the point that IF it was working, 
> why is it NOT working now?

It's the price for fixing the ability to edit a field within the same tiddler, 
which has been a perennial problem/bug that affects many users.

There's definitely a tension with breaking these macros, but there's a couple 
of points:

* More users encounter the edit-field-of-same-tiddler problem than would be 
running some old broken macro
* These macros were broken to begin with, and in many/most cases the authors 
chose to ignore warnings
* It should usually be easy to fix: wrap the macro invocation in a <$tiddler> 
widget referencing the tiddler in question

With reference to the second point, we've always tried to educate developers on 
the proper way to write macros. Literally every time a developer posts about a 
JS macro that they're writing, my first angle is to look to see if it follows 
the rules, and to provide feedback if not.

In many cases, of course, developers aren't very interested, and work on the 
basis of "it works for me so why should I change it", which of course in the 
end can be very damaging to the community unless the limitations are very 
carefully documented.

I do plan to update the release note with a more prominent warning of the 
impact of this change.

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/3A4AD25B-76DD-4DD4-ADC4-F8A6BD557180%40gmail.com.

Re: [tw5] Re: TiddlyWiki Community Call and File Uploads Plugin

2021-08-14 Thread Jeremy Ruston

> above.
>>>>
>>>> The call will include:
>>>>
>>>>- a progress update on my work on the *Uploads plugin* funded by
>>>>Open Collective
>>>>- a summary of some rather exciting and promising avenues for core
>>>>development in the areas of *Savers and Syncers* that has come out
>>>>of discussions around the Uploads plugin
>>>>- an update on the *Open Collective* model for funding TiddlyWiki
>>>>work and what we have learned from it thus far
>>>>- some news from Jeremy and Boris regarding improvements to
>>>>TiddlyWiki *community infrastructure*.
>>>>
>>>> I have been slowly working away on the TiddlyWiki file uploads plugin as
>>>> was previously announced
>>>> <https://groups.google.com/g/tiddlywiki/c/21yCCLI0E7s/m/vf04ZBxfAwAJ>.
>>>> The majority of the work thus far has consisted of brainstorming around the
>>>> architecture and some very involved but promising and productive
>>>> discussions with Jeremy around how such a plugin would integrate with the
>>>> core, and the direction that the core might take in the future with regards
>>>> to saving and syncing mechanisms.
>>>>
>>>> In particular we have identified some exciting opportunities to explore
>>>> in due course for a rethinking of the saver and syncer mechanisms that may
>>>> amongst other things eventually make file uploads a core TiddlyWiki ability
>>>> alongside saving and syncing and static file publishing.
>>>>
>>>> This has necessitated a change in approach to the File Uploads plugin
>>>> so as to not introduce changes to the TiddlyWiki core at this time which
>>>> may clash with the long term direction of development, and still make the
>>>> Uploads plugin available in a timely manner for those that need this
>>>> functionality today. I currently have a minimal working prototype that
>>>> uploads images imported into TiddlyWiki to Fission, though with no UI or
>>>> error handling as of yet and desperately in need of some heavy refactoring
>>>> to better be able to support different storage back ends. I hope to present
>>>> a demo of an early version of the plugin on the call.
>>>>
>>>> I would like to take the opportunity here to thank Boris and Fission.
>>>> Despite Boris having chipped in for the vast majority of the funding for
>>>> this plugin as it is something he needs in his own TiddlyWiki usage, not
>>>> only has he been patient and supportive as we focus on long term core
>>>> planning first, but Fission has actively been facilitating those
>>>> discussions.
>>>>
>>>> Regards,
>>>> Saq
>>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/5a365bea-3c1b-4bb2-8f9e-eaa36d2f682dn%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/5a365bea-3c1b-4bb2-8f9e-eaa36d2f682dn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

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

Re: [tw5] Re: Using <$list> widget to generate table rows

2021-08-12 Thread Jeremy Ruston

Hi Louis

As you've discovered, the wikitext table syntax is very simple, and doesn't 
support dynamic generation. The philosophy of TiddlyWiki's wikitext syntax is 
to provide easy-to-type shortcuts for common idioms that expand to sequences of 
widgets. In designing the wikitext syntax we are able to favour simplicity over 
flexibility because it is always possible for users to drop down into "raw 
widgets" to get the finest possible degree of control.

One can visualise the various elements of wikitext as a hierarchy of 
complexity/flexibility:

* Wikitext syntax is simple, easy to type and remember
* Macros add dynamic effects with the simplest possible syntax (because there 
are no closing tags to get mismatched)
* Widgets (and HTML) provide the base level of elementary primitives

Best wishes

Jeremy.

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 9 Aug 2021, at 22:02, Louis Davout  wrote:
> 
> 
> Well this works:
> 
> \define davout-list(levels: "1,3,5")
> 
> LevelBlah
> <$list filter="[[$levels$]split[,]]" variable="level">
> <> Blah
> 
> 
> \end
>> On Monday, August 9, 2021 at 9:53:34 AM UTC-4 Louis Davout wrote:
>> \define davout-list(levels: "1,3,5")
>> | ! Level | ! Blah |
>> <$list filter="[[$levels$]split[,]]" variable="level">
>> 
>> | <> | Blah |
>> 
>> 
>> \end 
>> 
>> Removes the  tags but makes each row into its own table.
>> 
>>> On Monday, August 9, 2021 at 9:46:15 AM UTC-4 Louis Davout wrote:
>>> 
>>> I'm trying to use the <$list> widget generate table rows. One is this even 
>>> possible. Two How? Here is simplified version of code I've tried. 
>>> 
>>> \define davout-list(levels: "1,3,5")
>>> | ! Level | ! Blah |
>>> <$list filter="[[$levels$]split[,]]" variable="level">
>>> | <> | Blah |
>>> 
>>> \end
>>> 
>>> \define davout-list2(levels: "1,3,5")
>>> | ! Level | ! Blah |
>>> <$list filter="[[$levels$]split[,]]" variable="level">
>>> | <> | Blah |
>>> <$wikify name=wikifiedRow text=| <> | Blah |>
>>> <>
>>> 
>>> 
>>> \end
>>> 
>>> <>
>>> 
>>> <>
>>> 
>>> The html it generates:
>>>  Level>> align="center"> Blah
>>> | 1 | Blah |
>>> 
>>> | 3 | Blah |
>>> 
>>> | 5 | Blah |
>>>  Level>> align="center"> Blah
>>> | 1 | Blah |
>>>  | Blah |
>>> |
>>> 
>>> 
>>> | 3 | Blah |
>>>  | Blah |
>>> |
>>> 
>>> 
>>> | 5 | Blah |
>>>  | Blah |
>>> |
>>> 
>>> 
>>> 
>>> It's closing the table and generating  tags.
>>> -
>>> A more general question. It's been stated that macros are text substitution 
>>> not functions that return a value. And they don't "evaluate". I've seen 
>>> first hand they don't return a value, but they do seem to at least execute 
>>> some code. For example they do call other macros:
>>> 
>>> \define a()
>>> <>
>>> \end
>>> 
>>> \define b(where)
>>> $where$
>>> \end
>>> 
>>> <>
>>> 
>>> produces:
>>> here
>>> 
>>> So what are the rules for what macros will and will not "execute"?
>>> 
>>> Thanks.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/c17202a8-3ee6-47b5-a9e1-d5f4b2f04563n%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/759AAEBB-8EAA-4D62-9355-254F9336013C%40gmail.com.

Re: [tw5] Re: Better indexes through semantic modeling

2021-08-12 Thread Jeremy Ruston

Hi Soren

Thank you for sharing, as ever your writing is admirably clear and concise, and 
it's a pleasure to follow your thought processes.

I tweeted your post as TiddlyWiki:

https://twitter.com/TiddlyWiki/status/1425837197844910080

Many thanks,

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 12 Aug 2021, at 08:03, PMario  wrote:
> 
> 
>> On Thursday, August 12, 2021 at 1:31:00 AM UTC+2 springer wrote:
>> Soren,
>> 
>> In your "better indexes" essay you write:
>> If we do have the full text included in each locus, we may want to write a 
>> summary anyway and store it along with the full text: this way, we’ll be 
>> able to create an outline later and more easily see what parts of the 
>> document we’re hopping between.
>> 
>> And it reminds me how certain enlightenment texts were printed with a 
>> running outer-margin summary distilling key points (and of course the 
>> cognitive work of spelling out those side-notes is considerable!). For 
>> example, see the side-notes starting at p 49 (pdf-pagination) on this Adam 
>> Smith manuscript: 
>> https://oll-resources.s3.us-east-2.amazonaws.com/oll3/store/titles/237/0206-01_Bk.pdf
>> 
>> For some tiddlywiki projects, I've started to employ a super-condensed 
>> summary field (call it, say, the tldr field) that can be displayed for 
>> certain purposes. Unlike the main body of the tiddler, the tldr is 
>> text-only, maximum of a single sentence. (And if I can't summarize the 
>> tiddler in one sentence, then it needs to be more than one tiddler. ;) ) Of 
>> course, the fact that tw's standard search interface doesn't peek beyond 
>> title and text field means this solution requires some building-around to be 
>> useful. 
> 
> As I did read that section, I did think in a similar direction. I was 
> thinking about a "teaser" text that is shown in "Blog overview listings". 
> Sometimes it's the first paragraph of the text itself and sometimes it is a 
> short summary, that comes later in the text. 
> 
> --
> 
> I did create a field-search plugin, that lets you configure additional fields 
> that are shown in the search results. See: 
> https://wikilabs.github.io/editions/field-search/
> 
> -mario
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/e2a64d39-7a9e-4439-95f3-3dbfc4d4824cn%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/6DAC9EF9-528F-4606-84BD-D85E93FBFDCE%40gmail.com.

Re: [tw5] Tiddlywiki functionality from within javascript macro

2021-08-12 Thread Jeremy Ruston

Hi Louis,

I'm glad you found the answer. Just to say that GitHub Discussions can be more 
suited for developer/JS discussions because it has better support for code 
blocks and linking to code etc

https://github.com/Jermolene/TiddlyWiki5/discussions

Best wishes

Jeremy.

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 12 Aug 2021, at 10:46, Louis Davout  wrote:
> 
> Is Tiddlywiki functionality, such as running filters, available from within 
> a javascript macro? I've found the code for $tw.utils and how you can get 
> access to a tiddler object via this.wiki.getTiddler(title). But I haven't 
> come across anything for using filters. Thanks.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/6c55e3b8-2648-4abf-b210-f7de7ed00c93n%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/9F003B91-EBB3-41E9-8BEF-A35D7FAE108F%40gmail.com.

Re: [tw5] Re: Do TW Versions prior to 2011 still exist?

2021-08-11 Thread Jeremy Ruston

Just to add that the most recent version of TiddlyWiki Classic v2.x.x can be 
found at:

https://classic.tiddlywiki.com/

The full code history can be found at:

https://github.com/tiddlywiki/tiddlywiki

Best wishes

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 11 Aug 2021, at 21:17, strikke...@gmail.com  
> wrote:
> 
> 
> Archive
> 
> Lots of fun to be had ;-)
> 
> 
>> On Wednesday, August 11, 2021 at 8:36:02 PM UTC+2 dougla...@gmail.com wrote:
>> Hello everyone,
>> 
>> I would like to explore some of the earliest versions of TiddlyWiki.  I can 
>> access the first few commits on the original 2011 GitHub repo for the 
>> original version, but I am aware that TiddlyWiki has been around since much 
>> earlier than 2011.  For example, Jeremy Ruston gave a talk at the 2006 
>> BlogTalk Conference about it.
>> 
>> Are any of these earlier versions still available for downloading or for 
>> code review?
>> 
>> Thanks so much!
> 
> -- 
> 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/9c21ef35-0d8c-4d0f-9bbe-04ad2619e6d4n%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/76BE161B-F656-4F74-98C9-71E6608A1CC6%40gmail.com.

Re: [tw5] CSS for tooltips in TiddlyWiki?

2021-08-08 Thread Jeremy Ruston

Hi Dave,

Sadly, browsers do not allow web pages to apply styles to tooltips.

It is possible to create fake tooltips in CSS and JavaScript that can be 
styled, but these approaches compromise accessibility and compatibility.

Another point to bear in mind is that there's no guarantee that all users will 
be able to see tooltips because they are not compatible with touch screens.

Best wishes

Jeremy.

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 8 Aug 2021, at 14:43, David Gifford  wrote:
> 
> 
> Hi everyone
> 
> I would like to style the tooltip that comes up when hovering over a link. 
> 
> I tried a snippet I found online for regular tooltips, but that created a 
> second tooltip, so both appear near each other. I would just like to style 
> the one for TiddlyWiki links created with the link widget below. I want to 
> use it to display short inline hidden notes.
> 
> <$link to="." tooltip="this is the tooltip">**
> 
> Anyone know the CSS for TW tooltips? I skimmed vanilla base but did not find 
> anything.
> 
> Thanks in advance, Dave
> 
> 
> -- 
> 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/f0190c56-7eac-4d4a-9033-81a1059e6ea0n%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/E9BD516D-EFFE-4FA1-A34D-4E13D992BD2F%40gmail.com.

Re: [tw5] How do I store fields inside *.md files? As if it were a .tid file, without separating fields to the .meta file

2021-08-05 Thread Jeremy Ruston

We actually have a similar situation with .js files. As you know, they can 
contain front matter like this:

/*\
title: $:/core/modules/commands/build.js
type: application/javascript
module-type: command

Command to build a build target

\*/
(function(){

But one can also include a .meta file. Any fields specified there are processed 
before the front matter fields, so the values there take precedence.

We should therefore be able to follow the same approach with .md files

Best wishes

Jeremy


> On 5 Aug 2021, at 16:53, PMario  wrote:
> 
> On Thursday, August 5, 2021 at 2:56:28 PM UTC+2 Jeremy Ruston wrote:
> ...
> I certainly would draw the line at integrating a full YAML parser, but 
> there’s no reason why we couldn’t parse a simple subset of YAML fields from 
> MD files. 
> 
> I do agree here. The only thing we would need to implement, would be to 
> search for the --- markers, strip them out and convert the rest using the TW 
> parser. ... 
> 
> There is still the problem with the default nodejs behaviour, that it splits  
>  type: text/markdown  files into 2 elements. We would need to change that 
> back to write a single .md file with the "front-matter" stuff at the top. 
> 
> So we will need to support 2 versions. The problem is that it seems they 
> didn't change the file extension. So we do have no real indicator if a file 
> contains front-matter content or not. ... 
> 
> -mario
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+unsubscr...@googlegroups.com 
> <mailto:tiddlywiki+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/11ee592e-dae3-4e9a-bd75-1b879160d110n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywiki/11ee592e-dae3-4e9a-bd75-1b879160d110n%40googlegroups.com?utm_medium=email_source=footer>.

-- 
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/B6432C00-25D7-482D-8B2C-9CC3EC915352%40gmail.com.

Re: [tw5] How do I store fields inside *.md files? As if it were a .tid file, without separating fields to the .meta file

2021-08-05 Thread Jeremy Ruston

> Agreed. If we do add support for meta data in markdown files it would then be 
> prudent to consider the YAML frontmatter format which is becoming quite 
> commonplace:
> https://jekyllrb.com/docs/front-matter/ 
> https://gohugo.io/content-management/front-matter/
> 
> Now I better duck before Jeremy throws something at me for mentioning YAML

I certainly would draw the line at integrating a full YAML parser, but there’s 
no reason why we couldn’t parse a simple subset of YAML fields from MD files.

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/9873F926-F9C9-49CA-9658-A1955631A676%40gmail.com.

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 5449 matches

Mail list logo