Re: [tw5] Re: Projectify 0.6.0

2020-12-24 Thread maki aea
i'm not sure if this is how the core filter works as i am still learning 
it, i've tried various different syntax to get my filter to do both due 
today and due yesterday and before, but couldn't find the single term, so 
am currently using the two terms with the follow-on term. i've submitted a 
pull request (sorry i think i probably did it the wrong way, hope it helps)

the bug shows up when we have no tasks due today, but at the same time as 
having any tasks due before today e.g. none today, but one due yesterday

hope the others will amend my suggestion with a correct answer!

happy new year nico! maki

On Tuesday, December 22, 2020 at 9:02:58 PM UTC Nicolas Petton wrote:

> maki aea  writes:
>
> > hi nico, thanks for this!
>
> Hi Maki!
>
> > i was doing some due filters just now and found something that might 
> work 
> > for your overdue
> >
> > in $:/plugins/nico/projectify/ui/buttons/Scheduled
> >
> > [ [days:due[0]] [!days:due[-1]] 
> +[!has[draft.of]!tag[done]tag[todo]limit[1] 
> > ]
> >
> > i'm not sure if this is what we are looking for, but maybe it'll be 
> > something in the right direction
> >
> > (sorry i probably should have sent a pull request!)
>
> Thanks, though I'm not sure what you mean. Have you found a bug in
> Projectify with the overdue list?
>
> Cheers,
> Nico
>

-- 
You received this message because you 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/7d8f0070-7163-4623-af0b-e7afdde176fcn%40googlegroups.com.


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

2020-12-24 Thread tony
Thank you very much Jeremy and all of the contributors for continuing to 
develop this wonderful tool/community. 

The upgrade to v5.123 was smooth sailing.

I'm largely ignorant of most of the inner workings and have barely 
scratched the depths of Tiddlywiki's algebra and yet TiddlyWiki is still so 
simple to use to collect thoughts, ideas, life into a web notebook.

For the longest time I've been inserting <$list 
filter="[all[current]backlinks[]]"/> for backlinks
only to realize after all these years References *were* Backlinks hidden in 
the Info Panel; so much for RTFM!

So, however small, this usability improvement is welcome semantic sanity:

   - renamed  "references" 
   to "backlinks" in the tiddler info panel

And with the setting for the Tiddler info panel to stay open, a boon to 
utility.

Thank you again and happy holidays!

Peace to all,
tony
On Thursday, December 24, 2020 at 6:03:06 AM UTC-8 jeremy...@gmail.com 
wrote:

> I’m delighted to announce that the new v5.1.23 release of TiddlyWiki is 
> now available:
>
> https://tiddlywiki.com/
> https://www.npmjs.com/package/tiddlywiki/v/5.1.23
>
> I’ve attached a thumbnail of the release note (
> https://tiddlywiki.com/#Release%205.1.23) to give a sense of the scale. 
> Usually here I would summarise the key new features, but on this occasion 
> there’s really too many to choose from. So instead I’d like to invite 
> everyone to reply here nominating their favourite feature. And of course 
> please do ask for clarifications if any of the changes aren’t clear.
>
> For all of us it’s been a strange year, with much heartbreaking suffering 
> around us. Back in April, I was delighted to get v5.1.22 out as part of a 
> clearing of the decks, just in case anything happened to me. As it’s turned 
> out, despite COVID’s best efforts, but entirely thanks to a very high level 
> of collaboration across the core development team, v5.1.23 has been one of 
> the most impressive releases for a long time. I can’t wait to see what 
> we’ll achieve in 2021.
>
> I’d like to thank everyone involved with the development, and of course a 
> huge thank you to everyone here who’s time and attention makes this project 
> what it is today. To corrupt an old adage, TiddlyWiki will die when the 
> last person speaks its name. Right now there’s a chorus of voices lifting 
> the project, and let’s hope that will long continue,
>
> 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/a1c31ef3-eeb7-4977-b6e2-bab16c8787dfn%40googlegroups.com.


[tw5] Re: Drag and drop - excision from the view for text tiddlers

2020-12-24 Thread Michael Wiktowy
That is very cool. That kind of functionality will prove very useful in 
quickly tiddlywiking a big flat text file ... something I do a lot of ... 
very manually at the moment.

I will have to study your 5.1.23-filter wizardry and figure out how to tag 
the newly created tiddler with the host tiddler and name it based on the 
highlighted content.

Thanks for sharing a very practical example.
/Mike

On Thursday, December 24, 2020 at 6:55:34 PM UTC-4 Mark S. wrote:

>
> Now that 5.1.23 has come out, I've added this code to 
> https://marxsal.github.io/various/playground.html so people can try it 
> directly.
>
>

-- 
You received this message because you 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/e1642348-569e-4d92-8095-598225bafbbbn%40googlegroups.com.


[tw5] Re: Saved title for action-createtiddler only available AFTER run ?

2020-12-24 Thread 'Mark S.' via TiddlyWiki
So now that 5.1.23, I can post the example I've been working on:

https://marxsal.github.io/various/playground.html#Excise%20from%20View%20Template%20Example

If you look at the code, you'll see that I have to use a tiddler that's 
made in advance of the drag/drop routine. The tiddler that's made during 
the routine is not available for use inside the routine.



On Saturday, December 19, 2020 at 6:46:51 AM UTC-8 Mark S. wrote:

> I'm not using a button. I'm using droppable. So all actions are happening 
> inside an action macro.
>
> The button example was only an example, and I'm afraid has confused the 
> issue. Ignore what happens with buttons.
> On Saturday, December 19, 2020 at 1:55:40 AM UTC-8 PMario wrote:
>
>> @Mark Use button actions like this, 
>>
>> \define actions()
>> ALL action widgets come here
>> \end
>>
>> <$button actions=<> >click
>>
>> Otherwise you beg for trouble.
>>
>> -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/bc46c57c-5b71-4d90-8919-6c368de510d7n%40googlegroups.com.


[tw5] Re: Git hub saver

2020-12-24 Thread 'Mark S.' via TiddlyWiki


On Thursday, December 24, 2020 at 4:07:08 PM UTC-8 wrote:

>
>>
> I believe we have always been able to save to any branch we want. The only 
> limitation is that only one branch for a given repository can be published 
> via github pages to be served over HTTP, which is a github limitation and 
> not one coming from TiddlyWiki. 
>
>
Ah, that is what it was. I knew there was something.
 

> Apologies if I haven't been the most eloquent today, I am probably a 
> little bit too exhausted to be explaining things.
>

'Tis the season to be harried ...
 

-- 
You received this message because you 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/23a5d7b7-0e3f-4579-b32f-c7b40dbca137n%40googlegroups.com.


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

2020-12-24 Thread TeeDub
I will have to look at the keyboard stuff.

Thank you very much for your work.

On Thursday, December 24, 2020 at 7:25:25 PM UTC-5 Mat wrote:

> Yes, what a Christmas gift! Thank you Jeremy and everyone who contributed!
> Favourite features... 
> - Keyboard handling - oh'yeah!
> - Single VarsWidget instead of multiple SetVariableWidgets is a "small but 
> big" one
> - and of course the new operators! I am particularly excied about the 
> operators; slugify, filter, toggle, and I know I'll use !is[draft]
>
> ...now if I can only find the *time *to tiddle fiddle more!
>
> <:-)
>
> On Thursday, December 24, 2020 at 3:03:06 PM UTC+1 Jeremy Ruston wrote:
>
>> I’m delighted to announce that the new v5.1.23 release of TiddlyWiki is 
>> now available:
>>
>> https://tiddlywiki.com/
>> https://www.npmjs.com/package/tiddlywiki/v/5.1.23
>>
>> I’ve attached a thumbnail of the release note (
>> https://tiddlywiki.com/#Release%205.1.23) to give a sense of the scale. 
>> Usually here I would summarise the key new features, but on this occasion 
>> there’s really too many to choose from. So instead I’d like to invite 
>> everyone to reply here nominating their favourite feature. And of course 
>> please do ask for clarifications if any of the changes aren’t clear.
>>
>> For all of us it’s been a strange year, with much heartbreaking suffering 
>> around us. Back in April, I was delighted to get v5.1.22 out as part of a 
>> clearing of the decks, just in case anything happened to me. As it’s turned 
>> out, despite COVID’s best efforts, but entirely thanks to a very high level 
>> of collaboration across the core development team, v5.1.23 has been one of 
>> the most impressive releases for a long time. I can’t wait to see what 
>> we’ll achieve in 2021.
>>
>> I’d like to thank everyone involved with the development, and of course a 
>> huge thank you to everyone here who’s time and attention makes this project 
>> what it is today. To corrupt an old adage, TiddlyWiki will die when the 
>> last person speaks its name. Right now there’s a chorus of voices lifting 
>> the project, and let’s hope that will long continue,
>>
>> 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/9064e519-01dd-4d75-afeb-c76c324b376bn%40googlegroups.com.


Re: [tw5] Wikify Difference

2020-12-24 Thread Thomas Stone
I was just trying to understand some of the differences between Wikified 
HTML and Transcluded content. Thank you for explaining.

On Thursday, December 24, 2020 at 4:23:13 AM UTC-8 jeremy...@gmail.com 
wrote:

> Hi Thomas
>
> The wikify widget doesn't support dynamic content because it produces a 
> static snapshot of the rendering. In fact, internal links always include 
> the `#` but you wouldn't normally see it because a JavaScript event handler 
> intercepts clicking on the link.
>
> What are you trying to achieve?
>
> Best wishes
>
> Jeremy
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 24 Dec 2020, at 10:52, Thomas Stone  wrote:
>
> 
>
> I was wondering why the WikifyWidget's HTML output of an internal link 
> includes a # link.
>
> ```
> \define test_link()[[a_test]]
>
> <$wikify name=str_text_out text=<> output="html">
> 1)  <> 
>   
>
> 2) <>  
> ```
>
> Both outputs look same, but clicking on link #1 opens the [[a_test]] 
> navigates the browser to the #a_test bookmark and tiddler at the top of the 
> story river. You can close the [[a_test]] tiddler, and link #2 can re-open 
> it, but link #1 doesn't work because the the browser address already shows 
> the #a_test bookmark.
>
>
> -- 
> You received this message because you 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/2538d53d-3755-4a53-a20f-bc10b55afc5dn%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/b52029ae-2f95-4fff-a21b-41daa79f3cb6n%40googlegroups.com.


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

2020-12-24 Thread Mat
Yes, what a Christmas gift! Thank you Jeremy and everyone who contributed!
Favourite features... 
- Keyboard handling - oh'yeah!
- Single VarsWidget instead of multiple SetVariableWidgets is a "small but 
big" one
- and of course the new operators! I am particularly excied about the 
operators; slugify, filter, toggle, and I know I'll use !is[draft]

...now if I can only find the *time *to tiddle fiddle more!

<:-)

On Thursday, December 24, 2020 at 3:03:06 PM UTC+1 Jeremy Ruston wrote:

> I’m delighted to announce that the new v5.1.23 release of TiddlyWiki is 
> now available:
>
> https://tiddlywiki.com/
> https://www.npmjs.com/package/tiddlywiki/v/5.1.23
>
> I’ve attached a thumbnail of the release note (
> https://tiddlywiki.com/#Release%205.1.23) to give a sense of the scale. 
> Usually here I would summarise the key new features, but on this occasion 
> there’s really too many to choose from. So instead I’d like to invite 
> everyone to reply here nominating their favourite feature. And of course 
> please do ask for clarifications if any of the changes aren’t clear.
>
> For all of us it’s been a strange year, with much heartbreaking suffering 
> around us. Back in April, I was delighted to get v5.1.22 out as part of a 
> clearing of the decks, just in case anything happened to me. As it’s turned 
> out, despite COVID’s best efforts, but entirely thanks to a very high level 
> of collaboration across the core development team, v5.1.23 has been one of 
> the most impressive releases for a long time. I can’t wait to see what 
> we’ll achieve in 2021.
>
> I’d like to thank everyone involved with the development, and of course a 
> huge thank you to everyone here who’s time and attention makes this project 
> what it is today. To corrupt an old adage, TiddlyWiki will die when the 
> last person speaks its name. Right now there’s a chorus of voices lifting 
> the project, and let’s hope that will long continue,
>
> 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/b621098f-f8ec-4284-a112-09593b7e2cf6n%40googlegroups.com.


[tw5] Re: Git hub saver

2020-12-24 Thread Saq Imtiaz

>
> So, I guess what you're saying is that we didn't need $:/GitHub/Branch 
> before and therefore I never created it (because the default was good 
> enough).
>

Precisely. The default value in 5.1.21 shown in the UI for the saver is 
what you wanted, so you never edited it and $:/Github/Branch was never 
created. The UI and the JS used the same default ("master") and saving 
worked fine.

Now in 5.1.23 you still get shown the same default in the UI ("master"), 
but the JavaScript uses another ("main"). Editing the branch name in the UI 
creates the $:/Github/Branch tiddler, so that is used instead of the 
JavaScript default value.
 

> The new question is, can we now save on any branch that we want? Like can 
> I have a "test" branch for experiments before moving to main/master ?
>

I believe we have always been able to save to any branch we want. The only 
limitation is that only one branch for a given repository can be published 
via github pages to be served over HTTP, which is a github limitation and 
not one coming from TiddlyWiki. 

Apologies if I haven't been the most eloquent today, I am probably a little 
bit too exhausted to be explaining things.
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/f9977d1c-4105-461a-a746-fa6738503540n%40googlegroups.com.


[tw5] Re: Git hub saver

2020-12-24 Thread 'Mark S.' via TiddlyWiki
Ok, think I got it.

When I go back to my last commit from 3 months ago, I see that there is no

$:/GitHub/ <#%24%3A%2FGitHub%2FUsername>Branch

So, I guess what you're saying is that we didn't need $:/GitHub/Branch 
before and therefore I never created it (because the default was good 
enough).

The new question is, can we now save on any branch that we want? Like can I 
have a "test" branch for experiments before moving to main/master ?

Thanks!

On Thursday, December 24, 2020 at 3:41:28 PM UTC-8 Mark S. wrote:

> On Thursday, December 24, 2020 at 3:14:52 PM UTC-8 wrote:
>
>>
>> As am I. I suggest re-reading my previous message with this in mind, as 
>> well as last looking at the links provided here and in the GitHub issue. An 
>> input field being filled in does not necessarily mean the underlying 
>> tiddler exists and has a value.
>>
>
> But ... it was working with 5.1.21. The field must have been filled in or 
> it wouldn't have worked. So how did it become unfilled? 
>
> I understand that just because a value is displayed doesn't mean there is 
> an underlying tiddler. But when and why did it disappear? It was there 
> previously, or it would not have been able to save.
>
> > I would wager you never entered a value for the branch, but rather used 
> the displayed default which is pre-filled as "master".
>  
> Why would I need to enter a branch value, when it already had one in it's 
> prior use on github? It not only APPEARED to have the field filled in, it 
> must have actually had the tiddler filled in or it would never have saved. 
> Or does the upgrade process strip out existing configuration?
>  
> In other words, why doesn't the underlying tiddler exist, or why wasn't it 
> used? I did not download "empty" and then try to save it. I was using an 
> existing TW on github which should already have had all fields filled in.
>
>

-- 
You received this message because you 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/36d53d23-0577-460d-8402-02bb52decbebn%40googlegroups.com.


[tw5] Re: Git hub saver

2020-12-24 Thread 'Mark S.' via TiddlyWiki


On Thursday, December 24, 2020 at 3:14:52 PM UTC-8 wrote:

>
> As am I. I suggest re-reading my previous message with this in mind, as 
> well as last looking at the links provided here and in the GitHub issue. An 
> input field being filled in does not necessarily mean the underlying 
> tiddler exists and has a value.
>

But ... it was working with 5.1.21. The field must have been filled in or 
it wouldn't have worked. So how did it become unfilled? 

I understand that just because a value is displayed doesn't mean there is 
an underlying tiddler. But when and why did it disappear? It was there 
previously, or it would not have been able to save.

> I would wager you never entered a value for the branch, but rather used 
the displayed default which is pre-filled as "master".
 
Why would I need to enter a branch value, when it already had one in it's 
prior use on github? It not only APPEARED to have the field filled in, it 
must have actually had the tiddler filled in or it would never have saved. 
Or does the upgrade process strip out existing configuration?
 
In other words, why doesn't the underlying tiddler exist, or why wasn't it 
used? I did not download "empty" and then try to save it. I was using an 
existing TW on github which should already have had all fields filled in.

-- 
You received this message because you 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/0cd2180d-2ee7-4050-b06b-503e00a4e79an%40googlegroups.com.


[tw5] Re: GitHub + Netlify = recursion!

2020-12-24 Thread Prestige
So, the wiki can be used over cloud for free? I mean, the node version?

On Tuesday, 22 December 2020 at 18:27:22 UTC+5:30 dix...@gmail.com wrote:

>
> Most of my web sites use the Eleventy SSG, changes push to GitHub, then 
> Netlify sees those changes and auto-rebuilds.
>
> This also works with TW (single-file). However, the GitHub Saver info is 
> *also* pushed to Netlify, which means that if I attempt to edit my TW from 
> the web site, it tries to save that back down to GitHub, which would then 
> trigger another rebuild. So I get javascript recursion errors.
>
> Honestly what I need is password-protection and a way to have my TW on the 
> web without the recursion problem. I tried using the node.js version of TW 
> and push it to GitHub Pages (instead of Netlify) but the save process never 
> completed.
>
> Help!
>

-- 
You received this message because you 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/b799b516-a649-4e5c-85ef-5ab04ba65c82n%40googlegroups.com.


[tw5] Re: Git hub saver

2020-12-24 Thread Saq Imtiaz


> I'm not talking about a brand-new setup on Github. I'm talking about an 
> existing one. So all the fields already had values. 
>

As am I. I suggest re-reading my previous message with this in mind, as 
well as last looking at the links provided here and in the GitHub issue. An 
input field being filled in does not necessarily mean the underlying 
tiddler exists and has a value.

-- 
You received this message because you 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/8d721c71-618e-4f3d-ae9e-99860980f96bn%40googlegroups.com.


[tw5] Re: Drag and drop - excision from the view for text tiddlers

2020-12-24 Thread 'Mark S.' via TiddlyWiki

Now that 5.1.23 has come out, I've added this code 
to https://marxsal.github.io/various/playground.html so people can try it 
directly.

-- 
You received this message because you 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/db7c1a11-8fda-4ff1-8cf6-8b2e764afcd7n%40googlegroups.com.


[tw5] Re: Git hub saver

2020-12-24 Thread 'Mark S.' via TiddlyWiki


On Thursday, December 24, 2020 at 1:17:47 PM UTC-8  wrote:

> I would wager you never entered a value for the branch, but rather used 
> the displayed default which is pre-filled as "master". 
> Thus the $:/Github/Branch tiddler was never created in your wiki (it isn't 
> new for 5.1.23). Like all the other tiddlers for the Github saver, it is 
> only created when you enter a value.
>
>
I'm not talking about a brand-new setup on Github. I'm talking about an 
existing one. So all the fields already had values. 

My TW was 5.1.21. It was on github and saving there. All the saver fields 
were filled in. I downloaded it, upgraded it, and then filled in the 
authorization token. ALL the other fields were showing their original 
values. But it wouldn't save -- until I wrote over the branch "master" with 
the word "master".  I did not need to write over any of the other saver 
fields.
 
So, if $:/Github/Branch already existed, did it get stripped out during the 
upgrade? Why wasn't it used, just like the path, repository, api fields ?

-- 
You received this message because you 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/91486378-f2ee-4530-af12-7942c4288c60n%40googlegroups.com.


[tw5] Re: Git hub saver

2020-12-24 Thread Saq Imtiaz
I would wager you never entered a value for the branch, but rather used the 
displayed default which is pre-filled as "master". 
Thus the $:/Github/Branch tiddler was never created in your wiki (it isn't 
new for 5.1.23). Like all the other tiddlers for the Github saver, it is 
only created when you enter a value.

Have a look at https://tiddlywiki.com/empty.html#%24%3A%2FControlPanel to 
see what I mean, the branch is pre-filled with a default value. Even 
backspacing by a single character and then re-typing it will actually 
create the tiddler. 

Now in 5.1.23 the displayed default value ("master"), and the default 
actually used by the saver ("main" in 5.1.23 whereas it used to be "master" 
in 5.1.22) are no longer the same, causing the save to fail.

Personally I think the pre-filled default value is deceiving and we should 
not use one. I've had similar issues in other contexts where the 
<$edit-text> widget gives the appearance that a tiddler exists but it just 
the default value being shown in the absence of the tiddler.

On Thursday, December 24, 2020 at 9:59:23 PM UTC+1 Mark S. wrote:

> So I guess that configuration tiddler $:/GitHub/Branch was added to 5.1.23 
> (it doesn't seem to be in 5.1.22) ?
> I'm trying to understand why my existing configuration didn't persist 
> through the upgrade process, no matter
> what the default attribute provided. All the other configurations (path, 
> api, repository, file name) persisted.
>
> On Thursday, December 24, 2020 at 11:49:59 AM UTC-8 saq.i...@gmail.com 
> wrote:
>
>> @Mark S
>>
>> I posted some details in the issue I created for this: 
>> https://github.com/Jermolene/TiddlyWiki5/issues/5317
>>
>> The text you see is from the default attribute of the <$edit-text> in the 
>> UI, see 
>> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/ControlPanel/Saving/GitHub.tid#L13
>>
>> When the underlying tiddler does not exist:
>> - the UI shows the branch as "master".
>> - the code after the recent changes, uses "main" instead.
>>
>> On Thursday, December 24, 2020 at 8:46:39 PM UTC+1 Mark S. wrote:
>>
>>> I don't understand. My branch was specified (it shows as "master" in the 
>>> saver panel). But I had to delete it and type it in again to get it to 
>>> work. So is there an internal 5.1.23 configuration file that has to be 
>>> overwritten?
>>>
>>> Thanks! 
>>>
>>> On Thursday, December 24, 2020 at 11:37:56 AM UTC-8 saq.i...@gmail.com 
>>> wrote:
>>>
 Yep, we have our first bug. The placeholder shown when the branch has 
 not been specified is "master", but the code uses "main" for the branch.

 The interim fix for users is fortunately easy, just empty and re-fill 
 the branch name.

 On Thursday, December 24, 2020 at 8:33:15 PM UTC+1 Saq Imtiaz wrote:

> Hmm. I am a bit surprised that worked. I wonder if the changes made to 
> the Github saver to reflect the change made by Github to the default 
> branch  (master vs main) got something wrong.
>
> On Thursday, December 24, 2020 at 8:30:50 PM UTC+1 Ste wrote:
>
>> Cheers Saq! 
>> Refilled in all fields and for some reason.. It works..! 
>>
>>
>> On Thursday, 24 December 2020 at 19:25:22 UTC Ste wrote:
>>
>>> Just reread my own post.. Let me clarify... Using the git hub saving 
>>> in tiddlywiki works in pre release but not from newly upgraded. This is 
>>> true both with the file on my phone or the new file uploaded to git hub 
>>> and 
>>> trying the github saver from there. 
>>> XMLHttpRequest error code: 401
>>> Sorry. It's a 401. Not a 404.. I'm losing the plot.. Mulled wine 
>>> time! 
>>>
>>> On Thursday, 24 December 2020 at 19:10:55 UTC Ste wrote:
>>>
 I'm sure it's my own muppetry and that I'm trying to do this on my 
 phone but, I can succesfully upload pre upgrade wiki but not post 
 upgrade 
 wiki to github using the git hub saving mechanism. I am getting a 404 
 error. Any one else finding this?
>>>
>>>

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


[tw5] Re: Git hub saver

2020-12-24 Thread 'Mark S.' via TiddlyWiki
So I guess that configuration tiddler $:/GitHub/Branch was added to 5.1.23 
(it doesn't seem to be in 5.1.22) ?
I'm trying to understand why my existing configuration didn't persist 
through the upgrade process, no matter
what the default attribute provided. All the other configurations (path, 
api, repository, file name) persisted.

On Thursday, December 24, 2020 at 11:49:59 AM UTC-8 saq.i...@gmail.com 
wrote:

> @Mark S
>
> I posted some details in the issue I created for this: 
> https://github.com/Jermolene/TiddlyWiki5/issues/5317
>
> The text you see is from the default attribute of the <$edit-text> in the 
> UI, see 
> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/ControlPanel/Saving/GitHub.tid#L13
>
> When the underlying tiddler does not exist:
> - the UI shows the branch as "master".
> - the code after the recent changes, uses "main" instead.
>
> On Thursday, December 24, 2020 at 8:46:39 PM UTC+1 Mark S. wrote:
>
>> I don't understand. My branch was specified (it shows as "master" in the 
>> saver panel). But I had to delete it and type it in again to get it to 
>> work. So is there an internal 5.1.23 configuration file that has to be 
>> overwritten?
>>
>> Thanks! 
>>
>> On Thursday, December 24, 2020 at 11:37:56 AM UTC-8 saq.i...@gmail.com 
>> wrote:
>>
>>> Yep, we have our first bug. The placeholder shown when the branch has 
>>> not been specified is "master", but the code uses "main" for the branch.
>>>
>>> The interim fix for users is fortunately easy, just empty and re-fill 
>>> the branch name.
>>>
>>> On Thursday, December 24, 2020 at 8:33:15 PM UTC+1 Saq Imtiaz wrote:
>>>
 Hmm. I am a bit surprised that worked. I wonder if the changes made to 
 the Github saver to reflect the change made by Github to the default 
 branch  (master vs main) got something wrong.

 On Thursday, December 24, 2020 at 8:30:50 PM UTC+1 Ste wrote:

> Cheers Saq! 
> Refilled in all fields and for some reason.. It works..! 
>
>
> On Thursday, 24 December 2020 at 19:25:22 UTC Ste wrote:
>
>> Just reread my own post.. Let me clarify... Using the git hub saving 
>> in tiddlywiki works in pre release but not from newly upgraded. This is 
>> true both with the file on my phone or the new file uploaded to git hub 
>> and 
>> trying the github saver from there. 
>> XMLHttpRequest error code: 401
>> Sorry. It's a 401. Not a 404.. I'm losing the plot.. Mulled wine 
>> time! 
>>
>> On Thursday, 24 December 2020 at 19:10:55 UTC Ste wrote:
>>
>>> I'm sure it's my own muppetry and that I'm trying to do this on my 
>>> phone but, I can succesfully upload pre upgrade wiki but not post 
>>> upgrade 
>>> wiki to github using the git hub saving mechanism. I am getting a 404 
>>> error. Any one else finding this?
>>
>>

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


[tw5] Re: Git hub saver

2020-12-24 Thread Saq Imtiaz
@Mark S

I posted some details in the issue I created for 
this: https://github.com/Jermolene/TiddlyWiki5/issues/5317

The text you see is from the default attribute of the <$edit-text> in the 
UI, see 
https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/ControlPanel/Saving/GitHub.tid#L13

When the underlying tiddler does not exist:
- the UI shows the branch as "master".
- the code after the recent changes, uses "main" instead.

On Thursday, December 24, 2020 at 8:46:39 PM UTC+1 Mark S. wrote:

> I don't understand. My branch was specified (it shows as "master" in the 
> saver panel). But I had to delete it and type it in again to get it to 
> work. So is there an internal 5.1.23 configuration file that has to be 
> overwritten?
>
> Thanks! 
>
> On Thursday, December 24, 2020 at 11:37:56 AM UTC-8 saq.i...@gmail.com 
> wrote:
>
>> Yep, we have our first bug. The placeholder shown when the branch has not 
>> been specified is "master", but the code uses "main" for the branch.
>>
>> The interim fix for users is fortunately easy, just empty and re-fill the 
>> branch name.
>>
>> On Thursday, December 24, 2020 at 8:33:15 PM UTC+1 Saq Imtiaz wrote:
>>
>>> Hmm. I am a bit surprised that worked. I wonder if the changes made to 
>>> the Github saver to reflect the change made by Github to the default 
>>> branch  (master vs main) got something wrong.
>>>
>>> On Thursday, December 24, 2020 at 8:30:50 PM UTC+1 Ste wrote:
>>>
 Cheers Saq! 
 Refilled in all fields and for some reason.. It works..! 


 On Thursday, 24 December 2020 at 19:25:22 UTC Ste wrote:

> Just reread my own post.. Let me clarify... Using the git hub saving 
> in tiddlywiki works in pre release but not from newly upgraded. This is 
> true both with the file on my phone or the new file uploaded to git hub 
> and 
> trying the github saver from there. 
> XMLHttpRequest error code: 401
> Sorry. It's a 401. Not a 404.. I'm losing the plot.. Mulled wine time! 
>
> On Thursday, 24 December 2020 at 19:10:55 UTC Ste wrote:
>
>> I'm sure it's my own muppetry and that I'm trying to do this on my 
>> phone but, I can succesfully upload pre upgrade wiki but not post 
>> upgrade 
>> wiki to github using the git hub saving mechanism. I am getting a 404 
>> error. Any one else finding this?
>
>

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


[tw5] Re: Git hub saver

2020-12-24 Thread 'Mark S.' via TiddlyWiki
I don't understand. My branch was specified (it shows as "master" in the 
saver panel). But I had to delete it and type it in again to get it to 
work. So is there an internal 5.1.23 configuration file that has to be 
overwritten?

Thanks! 

On Thursday, December 24, 2020 at 11:37:56 AM UTC-8 saq.i...@gmail.com 
wrote:

> Yep, we have our first bug. The placeholder shown when the branch has not 
> been specified is "master", but the code uses "main" for the branch.
>
> The interim fix for users is fortunately easy, just empty and re-fill the 
> branch name.
>
> On Thursday, December 24, 2020 at 8:33:15 PM UTC+1 Saq Imtiaz wrote:
>
>> Hmm. I am a bit surprised that worked. I wonder if the changes made to 
>> the Github saver to reflect the change made by Github to the default 
>> branch  (master vs main) got something wrong.
>>
>> On Thursday, December 24, 2020 at 8:30:50 PM UTC+1 Ste wrote:
>>
>>> Cheers Saq! 
>>> Refilled in all fields and for some reason.. It works..! 
>>>
>>>
>>> On Thursday, 24 December 2020 at 19:25:22 UTC Ste wrote:
>>>
 Just reread my own post.. Let me clarify... Using the git hub saving in 
 tiddlywiki works in pre release but not from newly upgraded. This is true 
 both with the file on my phone or the new file uploaded to git hub and 
 trying the github saver from there. 
 XMLHttpRequest error code: 401
 Sorry. It's a 401. Not a 404.. I'm losing the plot.. Mulled wine time! 

 On Thursday, 24 December 2020 at 19:10:55 UTC Ste wrote:

> I'm sure it's my own muppetry and that I'm trying to do this on my 
> phone but, I can succesfully upload pre upgrade wiki but not post upgrade 
> wiki to github using the git hub saving mechanism. I am getting a 404 
> error. Any one else finding this?



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


[tw5] Re: Git hub saver

2020-12-24 Thread Saq Imtiaz
Yep, we have our first bug. The placeholder shown when the branch has not 
been specified is "master", but the code uses "main" for the branch.

The interim fix for users is fortunately easy, just empty and re-fill the 
branch name.

On Thursday, December 24, 2020 at 8:33:15 PM UTC+1 Saq Imtiaz wrote:

> Hmm. I am a bit surprised that worked. I wonder if the changes made to the 
> Github saver to reflect the change made by Github to the default branch  
> (master vs main) got something wrong.
>
> On Thursday, December 24, 2020 at 8:30:50 PM UTC+1 Ste wrote:
>
>> Cheers Saq! 
>> Refilled in all fields and for some reason.. It works..! 
>>
>>
>> On Thursday, 24 December 2020 at 19:25:22 UTC Ste wrote:
>>
>>> Just reread my own post.. Let me clarify... Using the git hub saving in 
>>> tiddlywiki works in pre release but not from newly upgraded. This is true 
>>> both with the file on my phone or the new file uploaded to git hub and 
>>> trying the github saver from there. 
>>> XMLHttpRequest error code: 401
>>> Sorry. It's a 401. Not a 404.. I'm losing the plot.. Mulled wine time! 
>>>
>>> On Thursday, 24 December 2020 at 19:10:55 UTC Ste wrote:
>>>
 I'm sure it's my own muppetry and that I'm trying to do this on my 
 phone but, I can succesfully upload pre upgrade wiki but not post upgrade 
 wiki to github using the git hub saving mechanism. I am getting a 404 
 error. Any one else finding this?
>>>
>>>

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


[tw5] Re: Git hub saver

2020-12-24 Thread Saq Imtiaz
Hmm. I am a bit surprised that worked. I wonder if the changes made to the 
Github saver to reflect the change made by Github to the default branch  
(master vs main) got something wrong.

On Thursday, December 24, 2020 at 8:30:50 PM UTC+1 Ste wrote:

> Cheers Saq! 
> Refilled in all fields and for some reason.. It works..! 
>
>
> On Thursday, 24 December 2020 at 19:25:22 UTC Ste wrote:
>
>> Just reread my own post.. Let me clarify... Using the git hub saving in 
>> tiddlywiki works in pre release but not from newly upgraded. This is true 
>> both with the file on my phone or the new file uploaded to git hub and 
>> trying the github saver from there. 
>> XMLHttpRequest error code: 401
>> Sorry. It's a 401. Not a 404.. I'm losing the plot.. Mulled wine time! 
>>
>> On Thursday, 24 December 2020 at 19:10:55 UTC Ste wrote:
>>
>>> I'm sure it's my own muppetry and that I'm trying to do this on my phone 
>>> but, I can succesfully upload pre upgrade wiki but not post upgrade wiki to 
>>> github using the git hub saving mechanism. I am getting a 404 error. Any 
>>> one else finding this?
>>
>>

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


[tw5] Re: Git hub saver

2020-12-24 Thread Ste
Cheers Saq! 
Refilled in all fields and for some reason.. It works..! 


On Thursday, 24 December 2020 at 19:25:22 UTC Ste wrote:

> Just reread my own post.. Let me clarify... Using the git hub saving in 
> tiddlywiki works in pre release but not from newly upgraded. This is true 
> both with the file on my phone or the new file uploaded to git hub and 
> trying the github saver from there. 
> XMLHttpRequest error code: 401
> Sorry. It's a 401. Not a 404.. I'm losing the plot.. Mulled wine time! 
>
> On Thursday, 24 December 2020 at 19:10:55 UTC Ste wrote:
>
>> I'm sure it's my own muppetry and that I'm trying to do this on my phone 
>> but, I can succesfully upload pre upgrade wiki but not post upgrade wiki to 
>> github using the git hub saving mechanism. I am getting a 404 error. Any 
>> one else finding this?
>
>

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


[tw5] Re: Git hub saver

2020-12-24 Thread Ste
Just reread my own post.. Let me clarify... Using the git hub saving in 
tiddlywiki works in pre release but not from newly upgraded. This is true 
both with the file on my phone or the new file uploaded to git hub and 
trying the github saver from there. 
XMLHttpRequest error code: 401
Sorry. It's a 401. Not a 404.. I'm losing the plot.. Mulled wine time! 

On Thursday, 24 December 2020 at 19:10:55 UTC Ste wrote:

> I'm sure it's my own muppetry and that I'm trying to do this on my phone 
> but, I can succesfully upload pre upgrade wiki but not post upgrade wiki to 
> github using the git hub saving mechanism. I am getting a 404 error. Any 
> one else finding this?

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


[tw5] Re: Git hub saver

2020-12-24 Thread Saq Imtiaz
Long shot, but whatever is entered for "target branch", remove it and 
re-enter. Check your repo to make sure you have the right branch name 
(master/main).

On Thursday, December 24, 2020 at 8:10:55 PM UTC+1 Ste wrote:

> I'm sure it's my own muppetry and that I'm trying to do this on my phone 
> but, I can succesfully upload pre upgrade wiki but not post upgrade wiki to 
> github using the git hub saving mechanism. I am getting a 404 error. Any 
> one else finding this?

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


[tw5] Git hub saver

2020-12-24 Thread Ste
I'm sure it's my own muppetry and that I'm trying to do this on my phone 
but, I can succesfully upload pre upgrade wiki but not post upgrade wiki to 
github using the git hub saving mechanism. I am getting a 404 error. Any 
one else finding this?

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


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

2020-12-24 Thread Mohammad Rahmani
Thanks Simon!
I will do it now!



Best wishes
Mohammad


On Thu, Dec 24, 2020 at 9:42 PM BurningTreeC 
wrote:

> I've left a post about the TiddlyWiki release over at hackernews (
> https://news.ycombinator.com/news)
>
> It's currently on the front page - so anybody's invited to go there and
> vote it up and leave a comment ;)
>
> BTC
>
> jeremy...@gmail.com schrieb am Donnerstag, 24. Dezember 2020 um 15:03:06
> UTC+1:
>
>> I’m delighted to announce that the new v5.1.23 release of TiddlyWiki is
>> now available:
>>
>> https://tiddlywiki.com/
>> https://www.npmjs.com/package/tiddlywiki/v/5.1.23
>>
>> I’ve attached a thumbnail of the release note (
>> https://tiddlywiki.com/#Release%205.1.23) to give a sense of the scale.
>> Usually here I would summarise the key new features, but on this occasion
>> there’s really too many to choose from. So instead I’d like to invite
>> everyone to reply here nominating their favourite feature. And of course
>> please do ask for clarifications if any of the changes aren’t clear.
>>
>> For all of us it’s been a strange year, with much heartbreaking suffering
>> around us. Back in April, I was delighted to get v5.1.22 out as part of a
>> clearing of the decks, just in case anything happened to me. As it’s turned
>> out, despite COVID’s best efforts, but entirely thanks to a very high level
>> of collaboration across the core development team, v5.1.23 has been one of
>> the most impressive releases for a long time. I can’t wait to see what
>> we’ll achieve in 2021.
>>
>> I’d like to thank everyone involved with the development, and of course a
>> huge thank you to everyone here who’s time and attention makes this project
>> what it is today. To corrupt an old adage, TiddlyWiki will die when the
>> last person speaks its name. Right now there’s a chorus of voices lifting
>> the project, and let’s hope that will long continue,
>>
>> 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/be4b2649-696d-4486-bcec-ac6818704a1fn%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/CAAV1gMC4PmyGT8iNAy9%3Dh4t%2BudOZJ%3D2feQfus%3DdHpigVSNoZKw%40mail.gmail.com.


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

2020-12-24 Thread BurningTreeC
I've left a post about the TiddlyWiki release over at hackernews 
(https://news.ycombinator.com/news)

It's currently on the front page - so anybody's invited to go there and 
vote it up and leave a comment ;)

BTC

jeremy...@gmail.com schrieb am Donnerstag, 24. Dezember 2020 um 15:03:06 
UTC+1:

> I’m delighted to announce that the new v5.1.23 release of TiddlyWiki is 
> now available:
>
> https://tiddlywiki.com/
> https://www.npmjs.com/package/tiddlywiki/v/5.1.23
>
> I’ve attached a thumbnail of the release note (
> https://tiddlywiki.com/#Release%205.1.23) to give a sense of the scale. 
> Usually here I would summarise the key new features, but on this occasion 
> there’s really too many to choose from. So instead I’d like to invite 
> everyone to reply here nominating their favourite feature. And of course 
> please do ask for clarifications if any of the changes aren’t clear.
>
> For all of us it’s been a strange year, with much heartbreaking suffering 
> around us. Back in April, I was delighted to get v5.1.22 out as part of a 
> clearing of the decks, just in case anything happened to me. As it’s turned 
> out, despite COVID’s best efforts, but entirely thanks to a very high level 
> of collaboration across the core development team, v5.1.23 has been one of 
> the most impressive releases for a long time. I can’t wait to see what 
> we’ll achieve in 2021.
>
> I’d like to thank everyone involved with the development, and of course a 
> huge thank you to everyone here who’s time and attention makes this project 
> what it is today. To corrupt an old adage, TiddlyWiki will die when the 
> last person speaks its name. Right now there’s a chorus of voices lifting 
> the project, and let’s hope that will long continue,
>
> 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/be4b2649-696d-4486-bcec-ac6818704a1fn%40googlegroups.com.


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

2020-12-24 Thread jtech108
Hello Jeremy and all,

Couldn't come at a better time!
Definitely will play with it over the holidays.
Thanks Jeremy for all the time and love you have put into Tiddlywiki.
Trust me, it shows. Even if this year has been kind of rough I thank the 
good Lord
for bright spots like these. Many blessings to all.

Merry Christmas and a healthy 2021,  
Julio
On Thursday, December 24, 2020 at 11:22:54 AM UTC-5 saq.i...@gmail.com 
wrote:

> *If you are using the single file version of TiddlyWiki, you can upgrade 
> here:*
>
> https://tiddlywiki.com/upgrade.html
>

-- 
You received this message because you 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/1218d3f4-bf47-46c0-b4d2-2cc177488514n%40googlegroups.com.


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

2020-12-24 Thread Ste
Hooray! Well that's my xmas day sorted.. The kids can do their own 
Christmas dinner ;) 
Thank you Jeremy and all.
Hope everyone has good Christmas! 
Ste
On Thursday, 24 December 2020 at 16:22:54 UTC saq.i...@gmail.com wrote:

> *If you are using the single file version of TiddlyWiki, you can upgrade 
> here:*
>
> https://tiddlywiki.com/upgrade.html
>

-- 
You received this message because you 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/a3ebc2ed-cc69-40ba-8ade-096dd8b94af0n%40googlegroups.com.


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

2020-12-24 Thread Saq Imtiaz
*If you are using the single file version of TiddlyWiki, you can upgrade 
here:*

https://tiddlywiki.com/upgrade.html

-- 
You received this message because you 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/0e54c357-6d11-459c-94ee-c7ae7334d760n%40googlegroups.com.


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

2020-12-24 Thread Saq Imtiaz
*If you are using the single file version of TiddlyWiki, you can upgrade 
here:*

https://tiddlywiki.com/upgrade.html

-- 
You received this message because you 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/0a3170d6-4775-4f08-a7ea-81fc324b1fe6n%40googlegroups.com.


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

2020-12-24 Thread Aidan Grey
Will there be one of those existingTW updaters for this release, or is it
just too complicated?

On Thu, Dec 24, 2020 at 8:47 AM Saq Imtiaz  wrote:

> This feels like a personal gift, on my last day of volunteering for the
> calendar year no less!
>
> What I am happiest about is the excellent and very productive
> collaboration that went into this release. When I actively re-joined the
> community earlier this year, I was somewhat concerned at the apparent lack
> of  developers contributing to the core. Fast forward to the end of the
> year and I think we are in a much healthier place, in no small part due to
> Jeremy making the time to facilitate the collaboration and contributions to
> the core.
>
> Other than that the features I am most excited about are the
> <$eventcatcher> and the improved keyboard handling.
> A big thank you for all the effort that went into this release and
> everyone that contributed.
>
> Cheers,
> Saq
>
> PS: Streams users, upgrade Streams *BEFORE* upgrading to TW 5.1.23:
> https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams
>
> --
> You received this message because you 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/05b0b6c2-f4f4-408d-9d2d-b1a47abe6549n%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/CAJu7H0YeqNR5BKALZe4jGBQqqzri%3DxpXBm2KKtpJLSh%2BB5_zcg%40mail.gmail.com.


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

2020-12-24 Thread Saq Imtiaz
*Streams users:*

Please remember to upgrade to the latest version of Streams (0.1.20) before 
upgrading to TW 5.1.23

https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams


On Thursday, December 10, 2020 at 10:17:39 AM UTC+1 Dominic Robinson wrote:

> Ahh - that makes sense.  Obvious really :)
>
> On Wednesday, December 9, 2020 at 7:04:00 PM UTC saq.i...@gmail.com wrote:
>
>> @Dom: As Si points out, the Alt+Enter shortcut tries to split the text at 
>> double line breaks. If you want to split at the cursor just press Enter.
>>
>> However, thanks to your bug report I did manage to find and fix an actual 
>> bug with the Alt+Enter handling.
>>
>> Cheers,
>> Saq
>>
>> On Wednesday, December 9, 2020 at 7:07:38 PM UTC+1 si wrote:
>>
>>> Hi Dom,
>>>
>>> It looks like you are making the same error that I did 
>>>  
>>> and have misunderstood the purpose of the shortcut.
>>>
>>> Alt+Enter should split a node that has multiple lines into separate 
>>> tiddlers, but in your GIF the text is all on one line, so there is nothing 
>>> to split.
>>>
>>> If you want to split the text into two tiddlers at the place where your 
>>> cursor is, just press Enter.
>>>
>>> On Wednesday, 9 December 2020 at 17:37:19 UTC Dominic Robinson wrote:
>>>
 @Saq - this is Chrome on Windows 10.

 Hopefully this gif will show you what you need.  The gif looping 
 doesn't help, but it shows an attempt to split the node with alt-enter and 
 the creation of a new empty one.

 Cheers
 Dom

 [image: streams-split-repro.gif]

 On Tuesday, December 8, 2020 at 5:40:40 PM UTC saq.i...@gmail.com 
 wrote:

> @Dom I am unable to re-create the issue with Stream 0.1.20 on Chrome 
> or Firefox on Windows 10.
>
>- What browser and OS are you using?
>- Can you please provide step by step instruction for re-creating 
>the issue on https://saqimtiaz.github.io/streams/ ?
>   - Please include:
>  - the exact text that you enter, 
>  - a screenshot of the resultant nodes, 
>  - and a screenshot of the *Recent* tab in the sidebar, so I 
>  can see what tiddlers have been created.
>   
> Thank you.
> Saq
>
> On Tuesday, December 8, 2020 at 6:07:22 PM UTC+1 Dominic Robinson 
> wrote:
>
>> @Saq, 0.1.20 seems to have the same issue.
>>
>> Dom
>>
>> On Thursday, December 3, 2020 at 10:19:03 PM UTC saq.i...@gmail.com 
>> wrote:
>>
>>> @Dom I have a fix. I want to give it until tomorrow to do some 
>>> further testing before I push a new version. Thank you again for the 
>>> bug 
>>> report.
>>
>>

-- 
You received this message because you 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/f05aabd9-a57b-47a7-8df7-5c1f1856ca73n%40googlegroups.com.


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

2020-12-24 Thread Saq Imtiaz
This feels like a personal gift, on my last day of volunteering for the 
calendar year no less!

What I am happiest about is the excellent and very productive collaboration 
that went into this release. When I actively re-joined the community 
earlier this year, I was somewhat concerned at the apparent lack of  
developers contributing to the core. Fast forward to the end of the year 
and I think we are in a much healthier place, in no small part due to 
Jeremy making the time to facilitate the collaboration and contributions to 
the core.

Other than that the features I am most excited about are the 
<$eventcatcher> and the improved keyboard handling.
A big thank you for all the effort that went into this release and everyone 
that contributed.

Cheers,
Saq

PS: Streams users, upgrade Streams *BEFORE* upgrading to TW 5.1.23
: https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams

-- 
You received this message because you 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/05b0b6c2-f4f4-408d-9d2d-b1a47abe6549n%40googlegroups.com.


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

2020-12-24 Thread Mohammad Rahmani
Hi Jeremy,
 Many thanks for all your efforts. Tiddlywiki 5.1.23 has a lot of new
features

I love all new features, but I can name among them:

1. The new slugify operator let me create static sites directly from the
browser, I love it!
2. New filter operators e.g. search-replace, cycle, toggle
4. New keyboard enabled shortcuts
5. JSZip plugin
6. New import UI

I appreciate all the efforts, time and talents of all members of the core
developer team, among them I would like to name Simon, Saq, Jousha, Mario,
Jed, Cameron, and many others.

This is a new year gift to the Tiddlywiki community. Thank you Jeremy!

Merry Christmas and Happy New Year!

With the best wishes
Mohammad


On Thu, Dec 24, 2020 at 5:32 PM Jeremy Ruston 
wrote:

> I’m delighted to announce that the new v5.1.23 release of TiddlyWiki is
> now available:
>
> https://tiddlywiki.com/
> https://www.npmjs.com/package/tiddlywiki/v/5.1.23
>
> I’ve attached a thumbnail of the release note (
> https://tiddlywiki.com/#Release%205.1.23) to give a sense of the scale.
> Usually here I would summarise the key new features, but on this occasion
> there’s really too many to choose from. So instead I’d like to invite
> everyone to reply here nominating their favourite feature. And of course
> please do ask for clarifications if any of the changes aren’t clear.
>
> For all of us it’s been a strange year, with much heartbreaking suffering
> around us. Back in April, I was delighted to get v5.1.22 out as part of a
> clearing of the decks, just in case anything happened to me. As it’s turned
> out, despite COVID’s best efforts, but entirely thanks to a very high level
> of collaboration across the core development team, v5.1.23 has been one of
> the most impressive releases for a long time. I can’t wait to see what
> we’ll achieve in 2021.
>
> I’d like to thank everyone involved with the development, and of course a
> huge thank you to everyone here who’s time and attention makes this project
> what it is today. To corrupt an old adage, TiddlyWiki will die when the
> last person speaks its name. Right now there’s a chorus of voices lifting
> the project, and let’s hope that will long continue,
>
> 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/C7031490-486F-4FC3-A82A-EF1A0689C5FF%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/CAAV1gMAkD-tR9vNUwJVKfNWX_bm_XEgofe%2BJ8HSyMZj_cZvsCw%40mail.gmail.com.


Re: [tw5] Re: Paid Theme Design?

2020-12-24 Thread Aidan Grey
>
> Rather than start altering the layout perhaps you can create a tiddler for
> viewing other tiddlers that contain the text. You can then use fluid story
> fixed sidebar, with the sidebar closed to see a wide tiddler that contains
> your two page layout, you custom background and various icons. Once
> complete it could be redesigned as a new layout if necessary but to me a
> view tiddler is better because then your "reader" could be used in any
> tiddler and wiki.


A mockup is a great idea! I'll get drawing or something...

And a "view tiddler": if it provides me with the  view I am asking for,
then I'd be happy as a clam. Can you edit a tiddler directly though the
view tiddler, or is it just a transclusion?

On Wed, Dec 23, 2020 at 8:40 PM TW Tones  wrote:

> On reviewing your requirements, a little more clarity and perhaps a mock
> up would help.
>
> Rather than start altering the layout perhaps you can create a tiddler for
> viewing other tiddlers that contain the text. You can then use fluid story
> fixed sidebar, with the sidebar closed to see a wide tiddler that contains
> your two page layout, you custom background and various icons. Once
> complete it could be redesigned as a new layout if necessary but to me a
> view tiddler is better because then your "reader" could be used in any
> tiddler and wiki.
>
> Tones
>
> On Sunday, 20 December 2020 at 03:06:00 UTC+11 taale...@gmail.com wrote:
>
>> >> There are theme designers that may take up this. But first what are
>> you requiring from this new theme?
>>
>> My  experience historically has been not so great - I think this is the
>> third time? I've done what I can on my own, but I also  gave up on a lot of
>> ideas, as just way outside my expertise.
>>
>> I guess I have two main ideas, both build off of / reflect things that
>> others have asked for or suggested. I thought that maybe supporting
>> someone's time money wise might be appreciated. At any rate, here's what
>> I'm looking for:
>>
>> 1) A new plugin for color tweaking: something where we could pick our
>> colors in TW, and see changes immediately. Would obviously need to include
>> some work to make all the uncommon bits visible (alerts, for example).
>>
>> 2) The new Notebook theme is awesome, but made me pine for one of my
>> original thoughts again - the manuscript!
>> * a two-panel layout (like an open book) that can become "single page" as
>> needed depending on browser width
>> * the "book" sits on a table/like background, of course, possibly with
>> some other items visible for aesthetic purposes (inkwell and quill!)
>> * "turny corners" to move to next page / prev page of a tiddler "page"
>> * editing would be a single panel on the page, like normal
>> * There's a bookmark, and I have two ideas here:
>> IDEA 1:  the part of the bookmark showing has the main tool buttons
>> (New/Home/Save, etc.) as well as navigation buttons - previous tiddler aka
>> chapter, maybe last 5 tiddlers. Idea is basically to allow for tiddlers as
>> static "pages" but still have fairly easy navigation (an idea would be to
>> have temporary additional "bookmarks/tags" on the sides of the "book" for
>> quick navigation to other "open"  tiddlers)
>> IDEA 2: put new/save/home buttons on the object on the table (click on
>> the inkwell to create a new page/tiddler, quill to save, etc) and keep the
>> bookmark super simple, possibly with links to "home" pages or fave tiddlers
>> * Clicking on bookmark takes you to "front page" - that has the main tool
>> tabs (Search / Open / Recent / Tools / etc.) and the TOC
>> * Layout on front page with bookmark would be, from right to left (or
>> left to right?),  with TOC,  on top layer of right
>> page with buttons as normal at top, and buttons for the various "tabs" in
>> normal layouts, and then the rest of the right page   "behind" the
>> bookmark, which would show all the other details - the tools list and
>> buttons, the open tiddlers, and so on.
>>
>> I know I'm going overboard with the aesthetic functionality here, but...
>> I do have reasons, it doesn't hurt to list off all the hopes, no matter
>> what, and I think it would make for an awesome website
>>
>> On Fri, Dec 18, 2020 at 9:33 PM TW Tones  wrote:
>>
>>> There are theme designers that may take up this. But first what are you
>>> requiring from this new theme?
>>>
>>> In the pre-release there is a way to change layouts if you have more
>>> than one, ie the structure, but otherwise themes usually consist of colour
>>> pallets and css tweaking of existing elements.
>>>
>>> There is a reasonable chance this can be accomplished by the community
>>> helping you.
>>>
>>> Tones
>>> On Saturday, 19 December 2020 at 08:54:20 UTC+11 taale...@gmail.com
>>> wrote:
>>>
 Would anyone be up for designing a TiddlyWiki theme, that:
 1) I would pay for your time
 2) Would be free to the community once done

 If _anyone_ is interested, I will share my needs. But historically,
 it's been a big 

Re: [tw5] Re: Paid Theme Design?

2020-12-24 Thread Aidan Grey
Hello again!

Well, to be fair, you only posted details 4 days ago, and in the West, it's
> only 2 days from Christmas. People not locked down by Covid may be
> travelling, and people that are locked down are probably dealing with a lot
> of disruption.


True that - I had forgotten about the potential impact of the holidays.
That said, it's not been all that different from past experience, with the
exception of MORE engagement! So, thanks to you for the comments and
getting more involvement :)


>
>> 1) A new plugin for color tweaking: something where we could pick our
>>> colors in TW, and see changes immediately. Would obviously need to include
>>> some work to make all the uncommon bits visible (alerts, for example).
>>> That sounds doable. I'm surprised someone hasn't already done it. I
>>> think only a human will be able to see whether the uncommon bits are
>>> visible. I guess the display could show examples of most of the usages, so
>>> they could be tweaked on the spot before applying. Maybe someone will pop
>>> up with "that's already been done!"
>>
>>
Not done, that I know of, but it has been requested by others. I think it
would make a huge difference in terms of theme development, at least from
the color side.

2) The new Notebook theme is awesome, but made me pine for one of my
>> original thoughts again - the manuscript!
>> * a two-panel layout (like an open book) that can become "single page" as
>> needed depending on browser width
>>
> * the "book" sits on a table/like background, of course, possibly with
>> some other items visible for aesthetic purposes (inkwell and quill!)
>>
> * "turny corners" to move to next page / prev page of a tiddler "page"
>> * editing would be a single panel on the page, like normal
>> * There's a bookmark, and I have two ideas here:
>> IDEA 1:  the part of the bookmark showing has the main tool buttons
>> (New/Home/Save, etc.) as well as navigation buttons - previous tiddler aka
>> chapter, maybe last 5 tiddlers. Idea is basically to allow for tiddlers as
>> static "pages" but still have fairly easy navigation (an idea would be to
>> have temporary additional "bookmarks/tags" on the sides of the "book" for
>> quick navigation to other "open"  tiddlers)
>> IDEA 2: put new/save/home buttons on the object on the table (click on
>> the inkwell to create a new page/tiddler, quill to save, etc) and keep the
>> bookmark super simple, possibly with links to "home" pages or fave tiddlers
>>
>
Putting a bookmark in the *sidebar* for idea #2 sounds doable. Or were you
> thinking of getting rid of the sidebar? Like a complete re-arrangement of
> elements?


The latter - rearrange the elements altogether. Sidebar components would be
moved to the right page of the book, to the bookmark, or to the "tabs"...

Tones has requested a mock up, and I think that's a great idea working
on it



On Wed, Dec 23, 2020 at 12:51 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

>
>
> On Wednesday, December 23, 2020 at 10:25:56 AM UTC-8 wrote:
>
>> See? Crickets :)
>>
>>
> Well, to be fair, you only posted details 4 days ago, and in the West,
> it's only 2 days from Christmas. People not locked down by Covid may be
> travelling, and people that are locked down are probably dealing with a lot
> of disruption.
>
>
>>
>>> 1) A new plugin for color tweaking: something where we could pick our
>>> colors in TW, and see changes immediately. Would obviously need to include
>>> some work to make all the uncommon bits visible (alerts, for example).
>>>
>>>
> That sounds doable. I'm surprised someone hasn't already done it. I think
> only a human will be able to see whether the uncommon bits are visible. I
> guess the display could show examples of most of the usages, so they could
> be tweaked on the spot before applying. Maybe someone will pop up with
> "that's already been done!"
>
> 2) The new Notebook theme is awesome, but made me pine for one of my
>>> original thoughts again - the manuscript!
>>> * a two-panel layout (like an open book) that can become "single page"
>>> as needed depending on browser width
>>>
>>
> If it was me, I'd be tempted to lift Saq/Gifford's code from Stroll, since
> that's the main place I've seen double panels before.
>
>
>> * the "book" sits on a table/like background, of course, possibly with
>>> some other items visible for aesthetic purposes (inkwell and quill!)
>>>
>>
> BTW, there was a project to make a complete book out of TW. I don't think
> it had two pages, and I don't think the code was released.
>
>
>> * "turny corners" to move to next page / prev page of a tiddler "page"
>>> * editing would be a single panel on the page, like normal
>>> * There's a bookmark, and I have two ideas here:
>>> IDEA 1:  the part of the bookmark showing has the main tool buttons
>>> (New/Home/Save, etc.) as well as navigation buttons - previous tiddler aka
>>> chapter, maybe last 5 tiddlers. Idea is basically to allow for tiddlers as
>>> static 

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

2020-12-24 Thread BurningTreeC
Hi Jeremy, thank you for all your patience and this great release :)

My favourite features are:


   - the eventcatcher widget
   - keyboard-navigation of dropdowns
   - the new filter operators
   

Merry Christmas and a healthy new year 2021,
Simon

jeremy...@gmail.com schrieb am Donnerstag, 24. Dezember 2020 um 15:03:06 
UTC+1:

> I’m delighted to announce that the new v5.1.23 release of TiddlyWiki is 
> now available:
>
> https://tiddlywiki.com/
> https://www.npmjs.com/package/tiddlywiki/v/5.1.23
>
> I’ve attached a thumbnail of the release note (
> https://tiddlywiki.com/#Release%205.1.23) to give a sense of the scale. 
> Usually here I would summarise the key new features, but on this occasion 
> there’s really too many to choose from. So instead I’d like to invite 
> everyone to reply here nominating their favourite feature. And of course 
> please do ask for clarifications if any of the changes aren’t clear.
>
> For all of us it’s been a strange year, with much heartbreaking suffering 
> around us. Back in April, I was delighted to get v5.1.22 out as part of a 
> clearing of the decks, just in case anything happened to me. As it’s turned 
> out, despite COVID’s best efforts, but entirely thanks to a very high level 
> of collaboration across the core development team, v5.1.23 has been one of 
> the most impressive releases for a long time. I can’t wait to see what 
> we’ll achieve in 2021.
>
> I’d like to thank everyone involved with the development, and of course a 
> huge thank you to everyone here who’s time and attention makes this project 
> what it is today. To corrupt an old adage, TiddlyWiki will die when the 
> last person speaks its name. Right now there’s a chorus of voices lifting 
> the project, and let’s hope that will long continue,
>
> 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/0a21fd32-95df-4ba1-87c5-e255923b8313n%40googlegroups.com.


[tw5] Announcing the release of TiddlyWiki v5.1.23

2020-12-24 Thread Jeremy Ruston
I’m delighted to announce that the new v5.1.23 release of TiddlyWiki is now 
available:

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

I’ve attached a thumbnail of the release note 
(https://tiddlywiki.com/#Release%205.1.23) to give a sense of the scale. 
Usually here I would summarise the key new features, but on this occasion 
there’s really too many to choose from. So instead I’d like to invite everyone 
to reply here nominating their favourite feature. And of course please do ask 
for clarifications if any of the changes aren’t clear.

For all of us it’s been a strange year, with much heartbreaking suffering 
around us. Back in April, I was delighted to get v5.1.22 out as part of a 
clearing of the decks, just in case anything happened to me. As it’s turned 
out, despite COVID’s best efforts, but entirely thanks to a very high level of 
collaboration across the core development team, v5.1.23 has been one of the 
most impressive releases for a long time. I can’t wait to see what we’ll 
achieve in 2021.

I’d like to thank everyone involved with the development, and of course a huge 
thank you to everyone here who’s time and attention makes this project what it 
is today. To corrupt an old adage, TiddlyWiki will die when the last person 
speaks its name. Right now there’s a chorus of voices lifting the project, and 
let’s hope that will long continue,

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/C7031490-486F-4FC3-A82A-EF1A0689C5FF%40gmail.com.


Re: [tw5] Showing off: Muuri StoryView 0.2.0 Prerelease

2020-12-24 Thread BurningTreeC
The Demo ca be found here: https://burningtreec.github.io/tiddlywiki-muuri

BurningTreeC schrieb am Donnerstag, 24. Dezember 2020 um 14:44:15 UTC+1:

> I just want to ask the community if you think that the Sidebar Grid shown 
> in the Demo should be part of the plugin and in what ways it could be 
> useful. What do you think?
>
> best wishes and merry Christmas,
> BTC
>
> BurningTreeC schrieb am Dienstag, 22. Dezember 2020 um 19:29:18 UTC+1:
>
>> Hi Jan,
>>
>> Thank you!
>>
>> > It could be an idea to move the Tiddler-controls to a vertical bar and 
>> to reduce the size of the titles gradually while augmentign the number of 
>> columns.
>>
>> Yes I was thinking about the vertical tiddler controls. Reducing the size 
>> of the titles gradually is a good idea, I'll give it a try!
>>
>> best wishes
>> Jan schrieb am Dienstag, 22. Dezember 2020 um 10:11:57 UTC+1:
>>
>>> Hi Simon,
>>> very beautifull. Great to see how muuri is constantly evolving. The 
>>> handling is very smooth and logical.
>>> It could be an idea to move the Tiddler-controls to a vertical bar and 
>>> to reduce the size of the titles gradually while augmentign the number of 
>>> columns.
>>> Best wishes Jan
>>> Jan
>>>
>>> Am 20.12.2020 um 11:45 schrieb BurningTreeC:.
>>>
>>>
>>> Hi TiddlyWiki folks,
>>>
>>> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>>>
>>> It contains various Bugfixes and can overall be considered more stable
>>>
>>> New Feature:
>>>
>>>- Drop Actions: actions triggered when dropping an item from one 
>>>grid into another grid 
>>>   - the actionTiddler and modifier variables are available within 
>>>   the action-string, containing the title of the dragged item 
>>> respectively 
>>>   the modifier keys held while dragging 
>>>
>>> Missing Feature:
>>>
>>>- A configuration panel. I'm currently overhauling it.
>>>
>>> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>>>
>>> On the Demo page there's a Sidebar Grid where you can drop tiddlers 
>>> into. Holding shift while dragging adds a tag to that Tiddler. Holding 
>>> ctrl-shift while dragging shifts the Tiddler to edit mode.
>>>
>>> That's just a Demo of what can be built with the Muuri StoryView.
>>>
>>> If we think about it - having a Muuri StoryView in the main river on the 
>>> left and having one or two Grids in the SideBar with some defined 
>>> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>>>
>>>
>>> As always, I'm open for critics and ideas, just leave me a post
>>>
>>> all the best, 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/8454e0f9-79b9-4954-a38d-c33fc8fb4008n%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/8553af54-1b01-4ed3-aa86-39f6c08fe3d5n%40googlegroups.com.


Re: [tw5] Showing off: Muuri StoryView 0.2.0 Prerelease

2020-12-24 Thread BurningTreeC
I just want to ask the community if you think that the Sidebar Grid shown 
in the Demo should be part of the plugin and in what ways it could be 
useful. What do you think?

best wishes and merry Christmas,
BTC

BurningTreeC schrieb am Dienstag, 22. Dezember 2020 um 19:29:18 UTC+1:

> Hi Jan,
>
> Thank you!
>
> > It could be an idea to move the Tiddler-controls to a vertical bar and 
> to reduce the size of the titles gradually while augmentign the number of 
> columns.
>
> Yes I was thinking about the vertical tiddler controls. Reducing the size 
> of the titles gradually is a good idea, I'll give it a try!
>
> best wishes
> Jan schrieb am Dienstag, 22. Dezember 2020 um 10:11:57 UTC+1:
>
>> Hi Simon,
>> very beautifull. Great to see how muuri is constantly evolving. The 
>> handling is very smooth and logical.
>> It could be an idea to move the Tiddler-controls to a vertical bar and to 
>> reduce the size of the titles gradually while augmentign the number of 
>> columns.
>> Best wishes Jan
>> Jan
>>
>> Am 20.12.2020 um 11:45 schrieb BurningTreeC:.
>>
>>
>> Hi TiddlyWiki folks,
>>
>> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>>
>> It contains various Bugfixes and can overall be considered more stable
>>
>> New Feature:
>>
>>- Drop Actions: actions triggered when dropping an item from one grid 
>>into another grid 
>>   - the actionTiddler and modifier variables are available within 
>>   the action-string, containing the title of the dragged item 
>> respectively 
>>   the modifier keys held while dragging 
>>
>> Missing Feature:
>>
>>- A configuration panel. I'm currently overhauling it.
>>
>> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>>
>> On the Demo page there's a Sidebar Grid where you can drop tiddlers into. 
>> Holding shift while dragging adds a tag to that Tiddler. Holding ctrl-shift 
>> while dragging shifts the Tiddler to edit mode.
>>
>> That's just a Demo of what can be built with the Muuri StoryView.
>>
>> If we think about it - having a Muuri StoryView in the main river on the 
>> left and having one or two Grids in the SideBar with some defined 
>> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>>
>>
>> As always, I'm open for critics and ideas, just leave me a post
>>
>> all the best, 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/8454e0f9-79b9-4954-a38d-c33fc8fb4008n%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/950df8be-1420-4232-aecc-973793b33d2en%40googlegroups.com.


Re: [tw5] Wikify Difference

2020-12-24 Thread Jeremy Ruston
Hi Thomas

The wikify widget doesn't support dynamic content because it produces a static 
snapshot of the rendering. In fact, internal links always include the `#` but 
you wouldn't normally see it because a JavaScript event handler intercepts 
clicking on the link.

What are you trying to achieve?

Best wishes

Jeremy

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

> On 24 Dec 2020, at 10:52, Thomas Stone  wrote:
> 
> 
> I was wondering why the WikifyWidget's HTML output of an internal link 
> includes a # link.
> 
> ```
> \define test_link()[[a_test]]
> 
> <$wikify name=str_text_out text=<> output="html">
> 1)  <> 
>   
> 
> 2) <>  
> ```
> 
> Both outputs look same, but clicking on link #1 opens the [[a_test]] 
> navigates the browser to the #a_test bookmark and tiddler at the top of the 
> story river. You can close the [[a_test]] tiddler, and link #2 can re-open 
> it, but link #1 doesn't work because the the browser address already shows 
> the #a_test bookmark.
> 
> 
> -- 
> You received this message because you 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/2538d53d-3755-4a53-a20f-bc10b55afc5dn%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/959A8B11-BF09-4349-86DD-7F70E881CA8D%40gmail.com.


[tw5] Wikify Difference

2020-12-24 Thread Thomas Stone
I was wondering why the WikifyWidget's HTML output of an internal link 
includes a # link.

```
\define test_link()[[a_test]]

<$wikify name=str_text_out text=<> output="html">
1)  <> 
  

2) <>  
```

Both outputs look same, but clicking on link #1 opens the [[a_test]] 
navigates the browser to the #a_test bookmark and tiddler at the top of the 
story river. You can close the [[a_test]] tiddler, and link #2 can re-open 
it, but link #1 doesn't work because the the browser address already shows 
the #a_test bookmark.


-- 
You received this message because you 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/2538d53d-3755-4a53-a20f-bc10b55afc5dn%40googlegroups.com.


[tw5] Switch Story View

2020-12-24 Thread Mohammad Rahmani
Question:

You have ten tiddlers tid1, tid2, tid3,... tid10 are open in the story
view. When you switch story views e.g. from classic to zoomin which tiddler
will be in the view? What is the logic behind this and how one can change
it?



Best wishes
Mohammad

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


Re: [tw5] Re: [TW5] Introducing TiddlyTables a plugin for creating sortable tables.

2020-12-24 Thread arun babu
Thanks Alan for the reply. Don’t be sorry. It has been a tough time for all
of us. Happy to hear from you. Waiting for further updates on tiddlytables
once u r ready. Will give my suggestions as I use it more. May be you can
start a GitHub page for the plug in as a beginning. Merry Christmas!

On Thu, Dec 24, 2020 at 12:29 PM aeroc...@gmail.com 
wrote:

> Arunn,
> Sorry for the delay and thank you for your kind words. I am happy to hear
> you are finding my plugin useful. I have a few ideas for enhancements, but
> there has been no development since January. This year has been
> challenging, and as you mentioned, it has been difficult to find time. I
> have been quietly watching TW developments and I am always excited to see
> new features. I am especially excited for the 5.1.23 release that finally
> gives us keyboard-driven-input macros. I think this is a good release to
> base a new version of TiddlyTables on. At the top of my list of things to
> do is a rewrite of the pagination system, which is a little clunky in my
> opinion. I have also pondered how to integrate it more seamlessly with the
> core and make operation and styling more standard. Any ideas/feedback are
> welcome and greatly appreciated.
>
> Tones,
> You are correct. I love TiddlyWiki but it doesn't pay the bills. I wish it
> did.
> On Wednesday, December 23, 2020 at 6:08:01 PM UTC-6 TW Tones wrote:
>
>> I suppose *"there is no news regarding the further development"*
>> because we operate on voluntary contributions of time. People also need
>> feedback that there solutions are useful to justify what is working for no
>> return. This is fine in a community spirit but sometimes life and
>> livelihood compete with community work. I for one could deliver a pile of
>> published solutions however I am not working much and need to build a
>> business.
>>
>> We do need to find ways to inject a little demand and output for those
>> seeking a living.
>>
>> Regards
>> Tones
>>
>>
>>
>>
>> On Wednesday, 23 December 2020 at 18:58:15 UTC+11 arunn...@gmail.com
>> wrote:
>>
>>> Tones
>>>
>>> I know that its a successful tool already. But i was thinking why there
>>> is no news regarding the further development of such a great plug in for
>>> the last 10 months. Probably the developer is busy in his life and wouldn't
>>> have got time to allocate for further updates. I should thank Alan for
>>> developing tiddlytables and for being an inspiration for similar pllug ins.
>>>
>>> On Wednesday, December 23, 2020 at 6:17:07 AM UTC+5:30 TW Tones wrote:
>>>
 arunn

 Thread activity is unfortunately not a way to measure the success of a
 tool, but yes, its a great implementation

 Tones

 On Wednesday, 23 December 2020 at 07:31:35 UTC+11 arunn...@gmail.com
 wrote:

> Today only i got to explore this powerful tool and i was surprised to
> see the lack of activity in this thread. Hope your fine Alan.
>
> On Tuesday, February 11, 2020 at 5:56:42 AM UTC+5:30
> aeroc...@gmail.com wrote:
>
>> myfta,
>>
>> *Column Templates *are used to modify the text or functionality of
>> columns.
>> There are three kinds of column templates: header, body and footer
>> templates, and there are several built in.
>> Click "manage column templates" under "Columns" in the edit menu to
>> choose a different template for a particular field/index.
>> This link
>> 
>> has more information about the template concept.
>>
>> *CSS* is used to modify the appearance of columns.
>> There are a few built in stylesheets that can be edited under "Theme
>> (Stylesheet)" section of the edit menu.
>>
>> Hope this helps,
>> Alan
>>
>>
>>
>> On Monday, February 10, 2020 at 1:42:04 PM UTC-6, myfta wrote:
>>>
>>> So how might I format the column headings from my field names to
>>> something perhaps more user-friendly and formatted differently?
>>>
>>>
>>>
>>> On Monday, 9 September 2019 20:01:41 UTC+1, Alan Aldrich wrote:

 Greetings All, I am a long time fan of TiddlyWiki but new to the
 community. First and foremost, I would like to thank Jeremy for 
 creating
 TiddlyWiki and everyone who supports it. As a way to learn the ins and 
 outs
 of TiddlyWiki I started a "table builder" plugin that I have been 
 gradually
 improving in my spare time. I finally got around to finishing it up
 recently and would like to share it with the community.

 The ability for the entire wiki to import/export to/from a
 spreadsheet is a fascinating feature of TiddlyWiki, and I wanted to 
 build
 on that strength by creating a simple way to query data in the wiki and
 display it in a tabular way. I am calling it TiddlyTables. The 
 following