date:20210607

Mario,

I hope this is the appropriate thread?

I believe you already have the skills we need to use the local storage and 
save changes process I proposed elsewhere.

   - If I go to a site with the local storage plugin installed, not using 
   auto save, make it so the only way to reset the dirty flag, thus leave the 
   website tab is clicking a "logout" process. Thus logout process would (if 
   possible silently) save the changes with the following filter 
   [haschanged[]] [enlist{$:/temp/BrowserStorage/Log}] !readme.txt 
   - This save would in fact be a download to a download folder only. See 
   below for a download folder name. This is like your backup solution?
   - Then if this save can occur silently, like the backup solution you 
   have already designed (I think), the user keeps using the URL to get to the 
   site and uses local storage, to close the browser or tab they must use the 
   logout process (Which could look like the current save button).
   - If we can save silently it would not be as intrusive if the changes 
   backup need only occur when closing the tab or browser.
   - Then a mechaisium to detect either first visit (no changes saved yet) 
   or the possibly rare case of lost browser storage, where the user can 
   create a new "backup changes" or restore the last saved changes.
   - The value being all saves can be in the download folder or below, 
   perhaps a folder based on the url such that the folder will be unique to a 
   url, as is the local storage. That is the name determine where the changes 
   are saved, so if lost the previous save can be found.
   - A separate download of the whole wiki plus changes (the default save) 
   would be needed to move to another save mechanism, local copy or to access 
   in another browser., or another machine. 
  - If browsers share the download folder perhaps you can change 
  browsers on the same machine?
  - We could have a "full backup" method, similar to the download, as 
  well, to restore the whole wiki, even a new one at a public or private 
url.
   


Notes:

   - Perhaps cookies are less prone to loss than local storage, perhaps a 
   cookie could store the backup folder/filename? If not present on current 
   url/wiki prompt to load from downloads?

Tones

On Tuesday, 1 June 2021 at 22:31:06 UTC+10 PMario wrote:

> Hi,
> I do have a different idea, using the "local storage" plugin, but I want 
> to do more tests, since there is a behaviour, that I did see with an older 
> version. I want to be sure, that we are really able to avoid data loss. 
>
> Will post about my tests soon.
> -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/56767066-ae26-48f4-ac79-090169139da4n%40googlegroups.com.

Re: [tw5] Re: Is there a way to automatically save changes on TiddlyWiki?

2021-06-07 Thread Alessandra Carnevale


Gosh I realized I was using 5 plugins at the same time (I was scared of 
losing important data at this point!)
They were:
1) Timimi
2) Tiddlypouch for TiddlyWiki
3) Plugin containing specific configuration for the Online version of 
Noteself
4)The Pouchdb library as a TW5 plugin
5)TidllyWiki 5 core

I wasn't able to disable only the last one, and I am trying to follow the 
steps enlisted in your first advice.
If I see that the problem still persists, I will try to send you my 
TiddlyWiki.
Thank you so much for your help.

Il giorno sabato 5 giugno 2021 alle 18:20:31 UTC+9 PMario ha scritto:

> On Saturday, June 5, 2021 at 8:21:08 AM UTC+2 arlandri...@gmail.com wrote:
>  
>
>> Mario, this is what it happens, and it happens almost every time; I click 
>> on the tiddler that I want to open/edit, then I click on "edit this 
>> tiddler", then the whole content of the tiddler that I could have read 
>> until that very moment disappears! I am writing a thesis so it is all plain 
>> text. For this reason I am a bit scared of using tiddlywiki sometimes.
>>
>
> This is a "scaring" behaviour and definitely shouldn't happen.
>
> So which plugins do you use? TW doesn't have a built in revision system. 
> So I'm pretty sure that eiteher 1 of you plugins or the combination of 
> several plugins cause the problem. 
>  
> BACKUP FIRST
>
> 1 - You can try to disable all your plugins, and 
> 2 - See if the problem still happens. 
> 3 - Then activate the plugins 1 by 1. 
> 4 - Page reload will be needed for most of them
> 5 - Go to 2
>
> Or
> If you want I can have a look at your wiki. You can zip it and post it to 
> me privately if you want. The e-mail link can be found at github profile 
> page. https://github.com/pmario
>
> -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/541497cd-cccb-42c8-bbab-1508e289c23an%40googlegroups.com.

Re: [tw5] Re: Is there a way to automatically save changes on TiddlyWiki?

2021-06-07 Thread Alessandra Carnevale

Gosh I realized I was using 5 plugins at the same time (I was scared of
losing important data at this point!)
They were:
1) Timimi
2) Tiddlypouch for TiddlyWiki
3) Plugin containing specific configuration for the Online version of
Noteself
4)The Pouchdb library as a TW5 plugin
5)TidllyWiki 5 core

I wasn't able to disable only the first one, and I am trying to follow the
steps enlisted in your first advice.
If I see that the problem still persists, I will try to send you my
TiddlyWiki.
Thank you so much for your help.

On Sat, Jun 5, 2021 at 6:20 PM PMario  wrote:

> On Saturday, June 5, 2021 at 8:21:08 AM UTC+2 arlandri...@gmail.com wrote:
>
>
>> Mario, this is what it happens, and it happens almost every time; I click
>> on the tiddler that I want to open/edit, then I click on "edit this
>> tiddler", then the whole content of the tiddler that I could have read
>> until that very moment disappears! I am writing a thesis so it is all plain
>> text. For this reason I am a bit scared of using tiddlywiki sometimes.
>>
>
> This is a "scaring" behaviour and definitely shouldn't happen.
>
> So which plugins do you use? TW doesn't have a built in revision system.
> So I'm pretty sure that eiteher 1 of you plugins or the combination of
> several plugins cause the problem.
>
> BACKUP FIRST
>
> 1 - You can try to disable all your plugins, and
> 2 - See if the problem still happens.
> 3 - Then activate the plugins 1 by 1.
> 4 - Page reload will be needed for most of them
> 5 - Go to 2
>
> Or
> If you want I can have a look at your wiki. You can zip it and post it to
> me privately if you want. The e-mail link can be found at github profile
> page. https://github.com/pmario
>
> -mario
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/tUeWm_B07DQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/c4d37196-747b-487d-8876-b564824b2e05n%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/CAKp%2B3U0D%2BupH9OVwoZkUA5B5QP%3DuZ9QjyRo0%3DLwFrHf5sAN6ZQ%40mail.gmail.com.

Re: [tw5] Re: [Comment] My Ongoing Irritations with Google Groups

Soren,
My mistake.

Tones

On Tuesday, 8 June 2021 at 11:09:47 UTC+10 Soren Bjornstad wrote:

> Tones, I think you are confusing Discord and Discourse as happened earlier 
> up the thread 
> . 
> They are totally unrelated and Discourse is for long-form writing and 
> discussions , not chat.
>
> On Monday, June 7, 2021 at 6:32:51 PM UTC-5 TW Tones wrote:
>
>> ha Ha "bad sMellers," Totally agree, I am one of them, not to mention 
>> typos
>>
>> Seriously being able to edit the top post was a great way of summarising 
>> the results that come out in the thread. A Simple standard to update the 
>> top post when a question is answered, and the answer etc... would add great 
>> value.
>>
>> On discourse, Its A chat not likely to have longer more serious content, 
>> thus fragmented and harder to read. Has its place but in my mode not as a 
>> replacement to Git hub.
>>
>> I still hole a light for Yammer, but I do not want to waste my time 
>> explaining why if few people even try it. As a knowledge curator it would 
>> be ideal. Many little groups and blogs can be created with the owners 
>> extracting links and even build collaborative documents. Its only gap was 
>> code blocks.
>>
>> Tones
>>
>>
>> \
>>
>> On Monday, 7 June 2021 at 22:28:09 UTC+10 TiddlyTweeter wrote:
>>
>>>  saq.i...@gmail.com wrote:
>>>
 Jeremy just so you are aware, the issues with posting via the web 
> interface go beyond just difficulty in making monospaced blocks. 
>

>>> IF you ONLY use this GG though EMAIL then you WON'T know what got LOST 
>>> recently ... (and other functions too ...)
>>>
>>>- CODE sections 
>>>- Ability to PRIVATELY REPLY to posters
>>>- Ability to RE-EDIT for spelling errors (a serious disaster for bad 
>>>sMellers, of which there are many, including me)
>>>
>>> Just observations
>>> TT
>>>  
>>>
>>

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

[tw5] Re: [Song] Wiki Wiki

2021-06-07 Thread David Gifford

So Seinfeld-y at certain moments

On Monday, June 7, 2021 at 3:41:16 PM UTC-5 TiddlyTweeter wrote:

> This is a nice "Wikki-Wikki" song too ... https://youtu.be/80HZCap3aWU  
> 
>
> On Monday, 7 June 2021 at 22:22:36 UTC+2 TiddlyTweeter wrote:
>
>> Here is remix of the previous ... https://youtu.be/Q1B9IdiAWnI
>>
>> On Monday, 7 June 2021 at 22:16:55 UTC+2 TiddlyTweeter wrote:
>>
>>> There are other wiki songs ... like ...  https://youtu.be/hISA_7WBNIs
>>>
>>> TiddlyTweeter wrote:
>>>
 https://youtu.be/QtnzvUfO0wE

>>>

-- 
You received this message because you 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/1795738d-6852-439c-9c74-6104a38327ffn%40googlegroups.com.

Re: [tw5] Re: [Comment] My Ongoing Irritations with Google Groups

2021-06-07 Thread Soren Bjornstad

Tones, I think you are confusing Discord and Discourse as happened earlier 
up the thread 
. They 
are totally unrelated and Discourse is for long-form writing and discussions 
, not chat.

On Monday, June 7, 2021 at 6:32:51 PM UTC-5 TW Tones wrote:

> ha Ha "bad sMellers," Totally agree, I am one of them, not to mention typos
>
> Seriously being able to edit the top post was a great way of summarising 
> the results that come out in the thread. A Simple standard to update the 
> top post when a question is answered, and the answer etc... would add great 
> value.
>
> On discourse, Its A chat not likely to have longer more serious content, 
> thus fragmented and harder to read. Has its place but in my mode not as a 
> replacement to Git hub.
>
> I still hole a light for Yammer, but I do not want to waste my time 
> explaining why if few people even try it. As a knowledge curator it would 
> be ideal. Many little groups and blogs can be created with the owners 
> extracting links and even build collaborative documents. Its only gap was 
> code blocks.
>
> Tones
>
>
> \
>
> On Monday, 7 June 2021 at 22:28:09 UTC+10 TiddlyTweeter wrote:
>
>>  saq.i...@gmail.com wrote:
>>
>>> Jeremy just so you are aware, the issues with posting via the web 
 interface go beyond just difficulty in making monospaced blocks. 

>>>
>> IF you ONLY use this GG though EMAIL then you WON'T know what got LOST 
>> recently ... (and other functions too ...)
>>
>>- CODE sections 
>>- Ability to PRIVATELY REPLY to posters
>>- Ability to RE-EDIT for spelling errors (a serious disaster for bad 
>>sMellers, of which there are many, including me)
>>
>> Just observations
>> TT
>>  
>>
>

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

Re: [tw5] Re: [Comment] My Ongoing Irritations with Google Groups

2021-06-07 Thread Charlie Veniot

I'm sorry, and squirming such that I can't help myself:  who is Yammer, and 
do his eyes light up when you hole the light ?

Yeah, I'm a bad sMeller too.  And a gudder-heeyoumured tinker too.

This is what happens when folk can't edit their posts.  To me, potential 
for hilarity which just has me loving this version of Google Groups a 
little bit more ...

On Monday, June 7, 2021 at 8:32:51 PM UTC-3 TW Tones wrote:

> ha Ha "bad sMellers," Totally agree, I am one of them, not to mention typos
>
> Seriously being able to edit the top post was a great way of summarising 
> the results that come out in the thread. A Simple standard to update the 
> top post when a question is answered, and the answer etc... would add great 
> value.
>
> On discourse, Its A chat not likely to have longer more serious content, 
> thus fragmented and harder to read. Has its place but in my mode not as a 
> replacement to Git hub.
>
> I still hole a light for Yammer, but I do not want to waste my time 
> explaining why if few people even try it. As a knowledge curator it would 
> be ideal. Many little groups and blogs can be created with the owners 
> extracting links and even build collaborative documents. Its only gap was 
> code blocks.
>
> Tones
>
>
> \
>
> On Monday, 7 June 2021 at 22:28:09 UTC+10 TiddlyTweeter wrote:
>
>>  saq.i...@gmail.com wrote:
>>
>>> Jeremy just so you are aware, the issues with posting via the web 
 interface go beyond just difficulty in making monospaced blocks. 

>>>
>> IF you ONLY use this GG though EMAIL then you WON'T know what got LOST 
>> recently ... (and other functions too ...)
>>
>>- CODE sections 
>>- Ability to PRIVATELY REPLY to posters
>>- Ability to RE-EDIT for spelling errors (a serious disaster for bad 
>>sMellers, of which there are many, including me)
>>
>> Just observations
>> TT
>>  
>>
>

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

[tw5] Re: Yet another workflow, adaptation and video to check out

Thanks for sharing David. I know it wasn't the central piece,  of your 
workflow video but I've learned much from your CSS modifications like 
"thinner frame" etc. that this shows and your previous plugin spends time 
on. I appreciate you taking the time to post these :)

On Monday, June 7, 2021 at 8:27:38 PM UTC-4 David Gifford wrote:

>
> Hi everyone
>
> I am really into my new (yes, another one!) workflow for notetaking from 
> reading. It is faster than previous versions for what I like to grab from 
> books.
>
> Video:  https://www.youtube.com/watch?v=d9fyIJjfkgo
>
> Try it out yourself: 
> https://giffmex.org/experiments/notelines2.experiment.html
>
> 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/3432ca47-a5bb-4905-b556-ac3df3b3a369n%40googlegroups.com.

[tw5] Yet another workflow, adaptation and video to check out

2021-06-07 Thread David Gifford


Hi everyone

I am really into my new (yes, another one!) workflow for notetaking from 
reading. It is faster than previous versions for what I like to grab from 
books.

Video:  https://www.youtube.com/watch?v=d9fyIJjfkgo

Try it out yourself: 
https://giffmex.org/experiments/notelines2.experiment.html

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/7d638304-d706-41f8-b427-b48a2693b807n%40googlegroups.com.

Re: [tw5] Re: [Comment] My Ongoing Irritations with Google Groups

ha Ha "bad sMellers," Totally agree, I am one of them, not to mention typos

Seriously being able to edit the top post was a great way of summarising 
the results that come out in the thread. A Simple standard to update the 
top post when a question is answered, and the answer etc... would add great 
value.

On discourse, Its A chat not likely to have longer more serious content, 
thus fragmented and harder to read. Has its place but in my mode not as a 
replacement to Git hub.

I still hole a light for Yammer, but I do not want to waste my time 
explaining why if few people even try it. As a knowledge curator it would 
be ideal. Many little groups and blogs can be created with the owners 
extracting links and even build collaborative documents. Its only gap was 
code blocks.

Tones

\

On Monday, 7 June 2021 at 22:28:09 UTC+10 TiddlyTweeter wrote:

>  saq.i...@gmail.com wrote:
>
>> Jeremy just so you are aware, the issues with posting via the web 
>>> interface go beyond just difficulty in making monospaced blocks. 
>>>
>>
> IF you ONLY use this GG though EMAIL then you WON'T know what got LOST 
> recently ... (and other functions too ...)
>
>- CODE sections 
>- Ability to PRIVATELY REPLY to posters
>- Ability to RE-EDIT for spelling errors (a serious disaster for bad 
>sMellers, of which there are many, including me)
>
> Just observations
> TT
>  
>

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

Re: [tw5] TiddlyWiki Documentation - Syntax

Sorry, 

I meant to add I think version three could be at the bottom of every 
definition with all parameters, copy or drag.

Tones

On Tuesday, 8 June 2021 at 09:21:02 UTC+10 TW Tones wrote:

> *Stobot et al*
> *I'm not that familiar with screen readers etc. but if you want to take a 
> crack at an example to help me understand, I'd be happy to look at it*
> Nor am I but alt apparently making use of alt text is important for images 
> at least. No what I am saying is making use of the other features like 
> mouse over, tooltips etc... Of late I have being getting into draggable 
> payloads, especially of content as I describe in *On syntax formats* 
> below. Just drag a syntax form into your tiddler and edit.
>
> *On Syntax formats*
> To me version one is almost useless, it resembles the list of parameters 
> already documented. But you still need to refer to the rest of the 
> document. Using version one as a code snipit still requires a lot of work. 
> I would favor version 2 but one for each of the different configurations, 
> ie a subset of parameters for each common form of the widget. 
>
> *The details widget.*
>
> I use the html one a lot more know since something changed to make it more 
> reliable. It does store the initial state (open or closed) just not the 
> ongoing state, and in a larger number of circumstances this is all you 
> need. Also keep in mind that even the existence of the details widget can 
> be inside a list/reveal itself which is conditional. It is ideal for more 
> or less content. Using the summary tag you can actually place macros in the 
> details "heading" to show the number of something there inside the details 
> tag (I do not think $details does this). 
>
> Not with standing this, there is the details widget in a plugin 
> https://tid.li/tw5/plugins.html#DetailsWidget and 14kb in size, but I 
> have not used it much lately.
>
> I wish we could get the equivalent of the old TWC nested sliders plugin 
> but perhaps this can be emulated in Mario's "Custom Markup" as he has also 
> demonstrated the the details widget can.
>
> *That reminds me;*
> We could document a lot more features and methods in tiddlywiki or a 
> separate wiki that are not just about widgets, macros tweaks and filters, 
> but also making use of html and css. For example using css to toggle 
> content display: none; and possibly classes such as nest nest1 nest2 would 
> stand in for the nested sliders plugin. 
>
>
>
> Although the reality is the Custom Markup plugin may be the most valuable 
> plugin since "relink" and possibly of even more consequence.
>
> Regards
> Tones
>
>
> On Monday, 7 June 2021 at 22:44:42 UTC+10 TiddlyTweeter wrote:
>
>>
>>- To TiddlyTweeter's point, if <$details> stored state, wouldn't it 
>>just be a less-flexible <$reveal>?
>>
>> RIGHT. Point is it is just a dumb state that requires NO state tiddlers 
>> at all. You can simply, directly, change the toggle state.
>>
>> It is mostly ONLY useful for ON/OFF situations. 
>> For that it is elegantly simple in code!
>>
>> TT
>>
>>
>> On Monday, 7 June 2021 at 13:15:15 UTC+2 Stobot wrote:
>>
>>> Great continued feedback. I'll keep going, but just to mass-reply:
>>>
>>> PMario
>>>
>>>- I agree that the "closed version" should be in a small general 
>>>syntax notes area - maybe right below the syntax block. Things like:
>>>   - Each attribute can be given as "Text Value", {{Trancluded 
>>>   Value}}, or <>
>>>- Still thinking through how to handle the "or" situations (need 
>>>tiddler value or tiddler and field, or just field, or tiddler and 
>>> index...)
>>>   - Soren had the one example which might be great. I currently 
>>>   don't understand it clearly though, so will think on how to simplify 
>>> it
>>>
>>> Tones
>>>
>>>- I'm not that familiar with screen readers etc. but if you want to 
>>>take a crack at an example to help me understand, I'd be happy to look 
>>> at it
>>>
>>> Ste
>>>
>>>- I'll check out the stretch text thing. Others have suggested 
>>>details which seems to have similar aims (though is non-core)
>>>
>>> Mohammad / Odin / TiddlyTweeter
>>>
>>>- I think version 1 is good myself, and version 3 for completeness. 
>>>Might think about the best method to include both - via some mechanism 
>>> like 
>>>stretch-text / details / reveal / tabs (most core-ish I think)
>>>
>>>  (PMario / TiddlyTweeter)
>>>
>>>- Funnily enough the *only* thing that I can see useful about the 
>>><$details> widget is that it *doesn't* store the state (which keeps size 
>>> & 
>>># of changes down).
>>>- To TiddlyTweeter's point, if <$details> stored state, wouldn't it 
>>>just be a less-flexible <$reveal>?
>>>
>>> Thanks all, I'll keep plugging along and circle back to get more 
>>> feedback in a while. 
>>>
>>> On Monday, June 7, 2021 at 5:47:53 AM UTC-4 TiddlyTweeter wrote:
>>>

 TiddlyTweeter wrote:
>
>> ... using either

Re: [tw5] TiddlyWiki Documentation - Syntax

*Stobot et al*
*I'm not that familiar with screen readers etc. but if you want to take a 
crack at an example to help me understand, I'd be happy to look at it*
Nor am I but alt apparently making use of alt text is important for images 
at least. No what I am saying is making use of the other features like 
mouse over, tooltips etc... Of late I have being getting into draggable 
payloads, especially of content as I describe in *On syntax formats* below. 
Just drag a syntax form into your tiddler and edit.

*On Syntax formats*
To me version one is almost useless, it resembles the list of parameters 
already documented. But you still need to refer to the rest of the 
document. Using version one as a code snipit still requires a lot of work. 
I would favor version 2 but one for each of the different configurations, 
ie a subset of parameters for each common form of the widget. 

*The details widget.*

I use the html one a lot more know since something changed to make it more 
reliable. It does store the initial state (open or closed) just not the 
ongoing state, and in a larger number of circumstances this is all you 
need. Also keep in mind that even the existence of the details widget can 
be inside a list/reveal itself which is conditional. It is ideal for more 
or less content. Using the summary tag you can actually place macros in the 
details "heading" to show the number of something there inside the details 
tag (I do not think $details does this). 

Not with standing this, there is the details widget in a 
plugin https://tid.li/tw5/plugins.html#DetailsWidget and 14kb in size, but 
I have not used it much lately.

I wish we could get the equivalent of the old TWC nested sliders plugin but 
perhaps this can be emulated in Mario's "Custom Markup" as he has also 
demonstrated the the details widget can.

*That reminds me;*
We could document a lot more features and methods in tiddlywiki or a 
separate wiki that are not just about widgets, macros tweaks and filters, 
but also making use of html and css. For example using css to toggle 
content display: none; and possibly classes such as nest nest1 nest2 would 
stand in for the nested sliders plugin. 

Although the reality is the Custom Markup plugin may be the most valuable 
plugin since "relink" and possibly of even more consequence.

Regards
Tones

On Monday, 7 June 2021 at 22:44:42 UTC+10 TiddlyTweeter wrote:

>
>- To TiddlyTweeter's point, if <$details> stored state, wouldn't it 
>just be a less-flexible <$reveal>?
>
> RIGHT. Point is it is just a dumb state that requires NO state tiddlers at 
> all. You can simply, directly, change the toggle state.
>
> It is mostly ONLY useful for ON/OFF situations. 
> For that it is elegantly simple in code!
>
> TT
>
>
> On Monday, 7 June 2021 at 13:15:15 UTC+2 Stobot wrote:
>
>> Great continued feedback. I'll keep going, but just to mass-reply:
>>
>> PMario
>>
>>- I agree that the "closed version" should be in a small general 
>>syntax notes area - maybe right below the syntax block. Things like:
>>   - Each attribute can be given as "Text Value", {{Trancluded 
>>   Value}}, or <>
>>- Still thinking through how to handle the "or" situations (need 
>>tiddler value or tiddler and field, or just field, or tiddler and 
>> index...)
>>   - Soren had the one example which might be great. I currently 
>>   don't understand it clearly though, so will think on how to simplify it
>>
>> Tones
>>
>>- I'm not that familiar with screen readers etc. but if you want to 
>>take a crack at an example to help me understand, I'd be happy to look at 
>> it
>>
>> Ste
>>
>>- I'll check out the stretch text thing. Others have suggested 
>>details which seems to have similar aims (though is non-core)
>>
>> Mohammad / Odin / TiddlyTweeter
>>
>>- I think version 1 is good myself, and version 3 for completeness. 
>>Might think about the best method to include both - via some mechanism 
>> like 
>>stretch-text / details / reveal / tabs (most core-ish I think)
>>
>>  (PMario / TiddlyTweeter)
>>
>>- Funnily enough the *only* thing that I can see useful about the 
>><$details> widget is that it *doesn't* store the state (which keeps size 
>> & 
>># of changes down).
>>- To TiddlyTweeter's point, if <$details> stored state, wouldn't it 
>>just be a less-flexible <$reveal>?
>>
>> Thanks all, I'll keep plugging along and circle back to get more feedback 
>> in a while. 
>>
>> On Monday, June 7, 2021 at 5:47:53 AM UTC-4 TiddlyTweeter wrote:
>>
>>>
>>> TiddlyTweeter wrote:

> ... using either *<$reveal>... *or ... to hide sections so 
> its not too overwhelming and the end-user can expand only the sections 
> they 
> need to see.

>>> PMario replied: 
>>>
 At the moment Jeremy doesn't accept PRs that contain the  
 element, because it doesn't store open/close state. 
 I think, we need a <$details> widget, that can

[tw5] Re: [Song] Wiki Wiki

NEVER confuse a  Wiki with a WICKIE, the German (Vicky The Viking) thing. 

https://www.youtube.com/watch?v=U-wF_TmZxy4

On Monday, 7 June 2021 at 23:24:22 UTC+2 TiddlyTweeter wrote:

> Si. PMario sarebbe un ottimo DJ.
> TT
>
> On Monday, 7 June 2021 at 23:11:05 UTC+2 Ste wrote:
>
>> Right! We need to get DJ Jerm and MC Mario on the case to mix up some 
>> tiddly beats :)
>>
>> That raised a smile :)
>>
>> On Monday, 7 June 2021 at 21:41:16 UTC+1 TiddlyTweeter wrote:
>>
>>> This is a nice "Wikki-Wikki" song too ... https://youtu.be/80HZCap3aWU  
>>> 
>>>
>>> On Monday, 7 June 2021 at 22:22:36 UTC+2 TiddlyTweeter wrote:
>>>
 Here is remix of the previous ... https://youtu.be/Q1B9IdiAWnI

 On Monday, 7 June 2021 at 22:16:55 UTC+2 TiddlyTweeter wrote:

> There are other wiki songs ... like ...  https://youtu.be/hISA_7WBNIs
>
> TiddlyTweeter wrote:
>
>> https://youtu.be/QtnzvUfO0wE
>>
>

-- 
You received this message because you 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/c1bf34a5-1617-4b2a-be9d-8b4c87f8fa1bn%40googlegroups.com.

[tw5] Re: [Song] Wiki Wiki

Si. PMario sarebbe un ottimo DJ.
TT

On Monday, 7 June 2021 at 23:11:05 UTC+2 Ste wrote:

> Right! We need to get DJ Jerm and MC Mario on the case to mix up some 
> tiddly beats :)
>
> That raised a smile :)
>
> On Monday, 7 June 2021 at 21:41:16 UTC+1 TiddlyTweeter wrote:
>
>> This is a nice "Wikki-Wikki" song too ... https://youtu.be/80HZCap3aWU  
>> 
>>
>> On Monday, 7 June 2021 at 22:22:36 UTC+2 TiddlyTweeter wrote:
>>
>>> Here is remix of the previous ... https://youtu.be/Q1B9IdiAWnI
>>>
>>> On Monday, 7 June 2021 at 22:16:55 UTC+2 TiddlyTweeter wrote:
>>>
 There are other wiki songs ... like ...  https://youtu.be/hISA_7WBNIs

 TiddlyTweeter wrote:

> https://youtu.be/QtnzvUfO0wE
>


-- 
You received this message because you 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/3df397b3-037e-4363-a6f3-579a98691382n%40googlegroups.com.

[tw5] Re: [Song] Wiki Wiki

2021-06-07 Thread Ste

Right! We need to get DJ Jerm and MC Mario on the case to mix up some 
tiddly beats :)

That raised a smile :)

On Monday, 7 June 2021 at 21:41:16 UTC+1 TiddlyTweeter wrote:

> This is a nice "Wikki-Wikki" song too ... https://youtu.be/80HZCap3aWU  
> 
>
> On Monday, 7 June 2021 at 22:22:36 UTC+2 TiddlyTweeter wrote:
>
>> Here is remix of the previous ... https://youtu.be/Q1B9IdiAWnI
>>
>> On Monday, 7 June 2021 at 22:16:55 UTC+2 TiddlyTweeter wrote:
>>
>>> There are other wiki songs ... like ...  https://youtu.be/hISA_7WBNIs
>>>
>>> TiddlyTweeter wrote:
>>>
 https://youtu.be/QtnzvUfO0wE

>>>

-- 
You received this message because you 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/f4e8272c-002d-4c7d-ad9f-0a13d75bb714n%40googlegroups.com.

[tw5] Re: [Song] Wiki Wiki

This is a nice "Wikki-Wikki" song too ... https://youtu.be/80HZCap3aWU  


On Monday, 7 June 2021 at 22:22:36 UTC+2 TiddlyTweeter wrote:

> Here is remix of the previous ... https://youtu.be/Q1B9IdiAWnI
>
> On Monday, 7 June 2021 at 22:16:55 UTC+2 TiddlyTweeter wrote:
>
>> There are other wiki songs ... like ...  https://youtu.be/hISA_7WBNIs
>>
>> TiddlyTweeter wrote:
>>
>>> https://youtu.be/QtnzvUfO0wE
>>>
>>

-- 
You received this message because you 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/dc2be820-92dc-4eb6-9b19-f3b75a149f2cn%40googlegroups.com.

[tw5] Re: [Song] Wiki Wiki

Here is remix of the previous ... https://youtu.be/Q1B9IdiAWnI

On Monday, 7 June 2021 at 22:16:55 UTC+2 TiddlyTweeter wrote:

> There are other wiki songs ... like ...  https://youtu.be/hISA_7WBNIs
>
> TiddlyTweeter wrote:
>
>> https://youtu.be/QtnzvUfO0wE
>>
>

-- 
You received this message because you 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/d0d5790e-8cef-4b3f-a56a-d4c31eb42cdcn%40googlegroups.com.

Re: [tw5] Re: German documentation / deutsche Dokumentation

2021-06-07 Thread Frank Bruns-Ballhausen

Hi Mario,

kaum ist man mal ein paar Tage weg... ;-)

Ok. Dann habe ich jetzt erstmal ein wenig zu tun. GitHub-Account, Videos 
anschauen und hier gleich mal auf deine Mails antworten.

 > Welche distro? ...
Linux Mint mit XFCE, aber ich komme auch mit anderen zurecht (als Linuxuser 
probiert man ja viel aus und ist nicht so festgelegt)

> Aber mit VisualStudio Code kann man eigentlich alles mit einer GUI machen.
Ich hoffe doch mit Atom auch, zumindest sieht das so aus.

> TiddlyWiki hat eine CLA Contributor License Agreement...
Die CLA unterschreibe ich gern aber da muss ich dann wohl erst die Videos 
anschauen.

> Es wäre gut geänderte Tiddler als JSON zu exportieren.
Es wäre wohl auch besser, wenn wir an dem selben Objekt arbeiten dann fällt 
das zum Glück weg. Von daher sehe ich jetzt zu das ich mich in Github 
einarbeite.

> Ich möchte die "user macros" _fbb/ ... so weit wie möglich reduzieren und 
die $:/editions/tw5.com/doc-macros übersetzen, wenn nötig.
Ich habe ja schon damit angefangen, allerdings müss ich die Tiddler die 
noch die _fbb's verwenden aufgespürt und geändert werden. Bis zum letzten 
Versionswechsel war übrigens auch bei der englischen Version, nicht alles 
nach dem gleichen Schema erstellt. 
Sollen wir/ich die _fbb's gleich auf "tw5.com/de/.." umschreiben?
Gibt es für das Übersetzen nicht die Möglichkeit in die Macros Variablen 
einzusetzen die an der Spracheinstellung hängen? Mir war so, als ob das für 
das 'wikitext-example-without-html'-Macro schn mal ging...

> Microsoft hat in den 2000ern versucht die Programmiersprachen für Word, 
Excel und Co "einzudeutschen". Das war ein "Schuss in beide Knie".
Oh ja ich weiss was du meinst. Auch heute ärgere ich mich noch häufig über 
Formel in Excel. In der Online-Version sind sie englisch die offline 
Variante braucht deutsch...

> Wir sollten das Format vereinheitlichen und dann als PR für den "Core" 
vorschlagen, wenn wir sicher sind, dass es für uns passt.
Freut mich wenn es dir auch gefällt. Aber welches Format meinst du an 
dieser Stelle? Ich würde übrigens an der Stelle die Verwendung der Farben 
irgend wie vereinfachen wollen. Und der übergebene Inhalt klemmt zur Zeit 
auch noch wenn man Macros übergibt.

> Bin mir nicht sicher, ob Du da was geändert hast, oder ich mir was 
"zerschossen" habe. .. 
Vielleicht beides? In der heruntergeladenen Variante von dir waren ja 
einige Tiddler nicht vorhanden (obwohl im Journal aufgelistet). Nach dem 
ich dann mit der neuen nodejs-basierten Variante meine vorhandene 
Offline-Variante überschrieben habe, ist mir das erst aufgefallen. Ich 
konnte dann die vorige Version wieder herstellen und habe dann in der 
nodejs-basierten 
Variante den Stand von vorher erarbeitet. Das steht jetzt online und davon 
sind die exportierten Dateien.

Jetzt wo ich aut GitHub bin (https://github.com/FBB-de), hab ich auch deine 
Mail :-) 

Ich melde mich wenn ich mich ein wenig eingearbeitet habe.

Schönen Abend noch, Frank

PMario schrieb am Montag, 7. Juni 2021 um 17:08:38 UTC+2:

> Hi,
> Meine email kannst Du auf https://github.com/pmario finden. 
> -m
>
> On Monday, June 7, 2021 at 5:07:14 PM UTC+2 PMario wrote:
>
>> Hi Frank, 
>>
>> Deine letzten Änderungen vom 2&3 Juni hab ich eingearbeitet. .. 
>> Allerdings habe ich bei meiner localen version einen Unterschied in the 
>> modified feldern, den ich mir nicht wirklich erklären kann. ... Bin mir 
>> nicht sicher, ob Du da was geändert hast, oder ich mir was "zerschossen" 
>> habe. .. 
>>
>> ---
>>
>> Ich habe eben eine Azure "free account" mit einer nodejs version 
>> erstellt. ... Ich möchte dort "Server Sent Events" aktivieren. Damit können 
>> wir dann eventuell gleichzeitig arbeiten ohne uns die Daten zu 
>> überschreiben. Mit Skype oder Discord aktiv, sollte das dann auch Spaß 
>> machen. 
>>
>> Wenn du mir eine PM schickst, dann gebe ich dir die URL, den Namen und 
>> das Passwort, damit du editieren kannst. 
>> Wir sollten uns einen Termin ausmachen, bei dem wir dann alles besprechen 
>> können. 
>>
>> Mit Azure ist es momentan nicht möglich mehrere User zu erstellen, da ich 
>> keine Klartext files mit Usernamen und Passwörtern auf den Servern 
>> herumliegen haben will. (Zumindest weiß ich nicht wie's geht ;)
>>
>> Für den KeyVault muss man aber bezahlen :/ ... Muss mal sehen, ob wir das 
>> auf TW Server Seite lösen können, oder ob die MS docu noch was "ausspuckt".
>>
>> mfg
>> 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/22bb0ed1-8418-40a7-a503-4c0450bfacc5n%40googlegroups.com.

[tw5] Re: [Song] Wiki Wiki

There are other wiki songs ... like ...  https://youtu.be/hISA_7WBNIs

TiddlyTweeter wrote:

> https://youtu.be/QtnzvUfO0wE
>

-- 
You received this message because you 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/3a92f4f9-38e5-435b-abf5-a85d6b59fe85n%40googlegroups.com.

[tw5] [Song] Wiki Wiki

https://youtu.be/QtnzvUfO0wE

-- 
You received this message because you 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/b86e75f7-84d7-4a33-9c6d-143fc0459cc6n%40googlegroups.com.

[tw5] Re: Simple authentication options for Bob

2021-06-07 Thread scot

Hi Ed,
not sure if you've seen this link on  TiddlyWikiLinks 
 or if it's relevant to your setup.

"Add Login to a Node.js App with Cloudflare Argo Tunnels". Detailed 
explanation of setting up TiddlyWiki 
 in a Digital Ocean droplet, 
with a CloudFlare  Argo 
tunnel providing secure publishing to a domain with built-in authentication 

https://mydigitalmark.com/add-login-to-nodejs-with-cloudflare-argo-tunnels/ 

Add Login to a Node.js App with Cloudflare Argo Tunnels

Scot

On Monday, 7 June 2021 at 16:16:56 UTC+1 PMario wrote:

> Hi Ed,
> It should be possible to activate basic auth on the Nginx level. It will 
> create a system popup and deny access, if the credentials are wrong. 
> That should be relatively simple for the start. 
>
> see: 
> https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/
> I didn't read it. I only did a short search q:-)
> -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/ed9a33e3-d38d-4bfb-ae3c-47070e1d7c28n%40googlegroups.com.

[tw5] Re: Simple authentication options for Bob

Hi Ed,
It should be possible to activate basic auth on the Nginx level. It will 
create a system popup and deny access, if the credentials are wrong. 
That should be relatively simple for the start. 

see: 
https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/
I didn't read it. I only did a short search q:-)
-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/0b060bcf-36ce-4763-8029-f9a82a6d758an%40googlegroups.com.

Re: [tw5] Re: German documentation / deutsche Dokumentation

Hi,
Meine email kannst Du auf https://github.com/pmario finden. 
-m

On Monday, June 7, 2021 at 5:07:14 PM UTC+2 PMario wrote:

> Hi Frank, 
>
> Deine letzten Änderungen vom 2&3 Juni hab ich eingearbeitet. .. Allerdings 
> habe ich bei meiner localen version einen Unterschied in the modified 
> feldern, den ich mir nicht wirklich erklären kann. ... Bin mir nicht 
> sicher, ob Du da was geändert hast, oder ich mir was "zerschossen" habe. .. 
>
> ---
>
> Ich habe eben eine Azure "free account" mit einer nodejs version erstellt. 
> ... Ich möchte dort "Server Sent Events" aktivieren. Damit können wir dann 
> eventuell gleichzeitig arbeiten ohne uns die Daten zu überschreiben. Mit 
> Skype oder Discord aktiv, sollte das dann auch Spaß machen. 
>
> Wenn du mir eine PM schickst, dann gebe ich dir die URL, den Namen und das 
> Passwort, damit du editieren kannst. 
> Wir sollten uns einen Termin ausmachen, bei dem wir dann alles besprechen 
> können. 
>
> Mit Azure ist es momentan nicht möglich mehrere User zu erstellen, da ich 
> keine Klartext files mit Usernamen und Passwörtern auf den Servern 
> herumliegen haben will. (Zumindest weiß ich nicht wie's geht ;)
>
> Für den KeyVault muss man aber bezahlen :/ ... Muss mal sehen, ob wir das 
> auf TW Server Seite lösen können, oder ob die MS docu noch was "ausspuckt".
>
> mfg
> 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/45bcfa4a-1c14-4076-afd1-08f5d47c8de9n%40googlegroups.com.

Re: [tw5] Re: German documentation / deutsche Dokumentation

Hi Frank,

Deine letzten Änderungen vom 2&3 Juni hab ich eingearbeitet. .. Allerdings
habe ich bei meiner localen version einen Unterschied in the modified
feldern, den ich mir nicht wirklich erklären kann. ... Bin mir nicht
sicher, ob Du da was geändert hast, oder ich mir was "zerschossen" habe. ..

---

Ich habe eben eine Azure "free account" mit einer nodejs version erstellt.
... Ich möchte dort "Server Sent Events" aktivieren. Damit können wir dann
eventuell gleichzeitig arbeiten ohne uns die Daten zu überschreiben. Mit
Skype oder Discord aktiv, sollte das dann auch Spaß machen.

Wenn du mir eine PM schickst, dann gebe ich dir die URL, den Namen und das
Passwort, damit du editieren kannst.
Wir sollten uns einen Termin ausmachen, bei dem wir dann alles besprechen
können.

Mit Azure ist es momentan nicht möglich mehrere User zu erstellen, da ich
keine Klartext files mit Usernamen und Passwörtern auf den Servern
herumliegen haben will. (Zumindest weiß ich nicht wie's geht ;)

Für den KeyVault muss man aber bezahlen :/ ... Muss mal sehen, ob wir das
auf TW Server Seite lösen können, oder ob die MS docu noch was "ausspuckt".

mfg
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/d635fe45-c009-4337-b484-61c921baeda6n%40googlegroups.com.

[tw5] Re: Simple authentication options for Bob

2021-06-07 Thread Ed Heil

Thanks, I'll look into this!

I ended up just using "security by obscurity" and putting the wikis on a 
subdomain that nobody but me happens to know about; it'll do for now.  But 
I'd like to see if I can do basic auth.

As things stand, Bob seems to randomly crash a lot (or else something on my 
DO droplet is randomly killing it -- the logs say "such-and-so PID killed" 
so I think the issue might be external to Bob).  Annoying but I can always 
ssh in and restart it and things are fine again.  And other than that Bob 
is working really well. It blows me away that it exists at all, thank you 
for it!
On Monday, June 7, 2021 at 3:38:12 AM UTC-4 inmy...@gmail.com wrote:

> I never used basic auth with Bob on nginx, but other people have and the 
> thing that is probably missing is proxying websockets.
>
> The information here should cover it 
> http://nginx.org/en/docs/http/websocket.html
>
> I am hoping that the day job will slow down enough soon so I can get back 
> to working on the secure wiki server and have a simple install script, but 
> I don't have any real idea how long it will be before I have time for that.
>
> On Saturday, June 5, 2021 at 12:01:01 AM UTC+2 Ed Heil wrote:
>
>>
>> I just got Bob working on a digital ocean droplet behind an nginx proxy 
>> (yay!) and I would like some kind of authentication going on.  The 
>> "credentials" system which works with basic tiddlywiki would be great.   
>> However, when I run it with something like:
>>
>> node ./tiddlywiki.js Wikis/BobWiki/ --wsserver credentials=creds.csv 
>> "readers=(anon)" "writers=(authenticated)"
>>
>> the credentials don't seem to have any effect at all.  Anyone can still 
>> edit it.
>>
>> are those even supposed to work with Bob?
>>
>> if not, are there any other simple actions?
>>
>> I tried just putting Basic Auth on in my nginx config, but that seemed to 
>> break Bob completely.
>>
>>
>>
>>
>>

-- 
You received this message because you 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/a449acd1-3966-4791-9cd8-33199668a31cn%40googlegroups.com.

Re: [tw5] TiddlyWiki Documentation - Syntax


   
   - To TiddlyTweeter's point, if <$details> stored state, wouldn't it just 
   be a less-flexible <$reveal>?

RIGHT. Point is it is just a dumb state that requires NO state tiddlers at 
all. You can simply, directly, change the toggle state.

It is mostly ONLY useful for ON/OFF situations. 
For that it is elegantly simple in code!

TT


On Monday, 7 June 2021 at 13:15:15 UTC+2 Stobot wrote:

> Great continued feedback. I'll keep going, but just to mass-reply:
>
> PMario
>
>- I agree that the "closed version" should be in a small general 
>syntax notes area - maybe right below the syntax block. Things like:
>   - Each attribute can be given as "Text Value", {{Trancluded 
>   Value}}, or <>
>- Still thinking through how to handle the "or" situations (need 
>tiddler value or tiddler and field, or just field, or tiddler and index...)
>   - Soren had the one example which might be great. I currently don't 
>   understand it clearly though, so will think on how to simplify it
>
> Tones
>
>- I'm not that familiar with screen readers etc. but if you want to 
>take a crack at an example to help me understand, I'd be happy to look at 
> it
>
> Ste
>
>- I'll check out the stretch text thing. Others have suggested details 
>which seems to have similar aims (though is non-core)
>
> Mohammad / Odin / TiddlyTweeter
>
>- I think version 1 is good myself, and version 3 for completeness. 
>Might think about the best method to include both - via some mechanism 
> like 
>stretch-text / details / reveal / tabs (most core-ish I think)
>
>  (PMario / TiddlyTweeter)
>
>- Funnily enough the *only* thing that I can see useful about the 
><$details> widget is that it *doesn't* store the state (which keeps size & 
># of changes down).
>- To TiddlyTweeter's point, if <$details> stored state, wouldn't it 
>just be a less-flexible <$reveal>?
>
> Thanks all, I'll keep plugging along and circle back to get more feedback 
> in a while. 
>
> On Monday, June 7, 2021 at 5:47:53 AM UTC-4 TiddlyTweeter wrote:
>
>>
>> TiddlyTweeter wrote:
>>>
 ... using either *<$reveal>... *or ... to hide sections so 
 its not too overwhelming and the end-user can expand only the sections 
 they 
 need to see.
>>>
>>>
>> PMario replied: 
>>
>>> At the moment Jeremy doesn't accept PRs that contain the  
>>> element, because it doesn't store open/close state. 
>>> I think, we need a <$details> widget, that can handle persistent state, 
>>> in the core first.
>>>
>>
>> HA!*  *is super simple. ADD "open" or remove it. 
>> *   Should be a doddle. *
>> It is NOT intelligent like *<$reveal> *which handles well complex 
>> situations, but in MANY use cases  binary sate is all you need.
>>
>> Side comment
>> TT
>>
>

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

Re: [tw5] Re: [Comment] My Ongoing Irritations with Google Groups

 saq.i...@gmail.com wrote:

> Jeremy just so you are aware, the issues with posting via the web 
>> interface go beyond just difficulty in making monospaced blocks. 
>>
>
IF you ONLY use this GG though EMAIL then you WON'T know what got LOST 
recently ... (and other functions too ...)

   - CODE sections 
   - Ability to PRIVATELY REPLY to posters
   - Ability to RE-EDIT for spelling errors (a serious disaster for bad 
   sMellers, of which there are many, including me)

Just observations
TT
 

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

Re: [tw5] Re: [Comment] My Ongoing Irritations with Google Groups

Stobot wrote:

> Oof, I have had *minor* annoyances with Google Groups posting, but sounds 
> like nothing near what you guys (Soren / Saq) have been having.


Never forget ME. I wrote the OP  :-) 
That is RHYMING SLANG too :-)

Issues are very much about HOW to OPTIMIZE search in the GG.

Jeremy & Soren found it more trivial than me.
It is an ongoing saga.

Best wishes
TT

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

[tw5] Re: Simple authentication options for Bob

Eagerly awaiting your return someday Jed! I have a monthly reminder to 
check the OokTech page and refresh, hoping you get a little closer :)

On Monday, June 7, 2021 at 3:38:12 AM UTC-4 inmy...@gmail.com wrote:

> I never used basic auth with Bob on nginx, but other people have and the 
> thing that is probably missing is proxying websockets.
>
> The information here should cover it 
> http://nginx.org/en/docs/http/websocket.html
>
> I am hoping that the day job will slow down enough soon so I can get back 
> to working on the secure wiki server and have a simple install script, but 
> I don't have any real idea how long it will be before I have time for that.
>
> On Saturday, June 5, 2021 at 12:01:01 AM UTC+2 Ed Heil wrote:
>
>>
>> I just got Bob working on a digital ocean droplet behind an nginx proxy 
>> (yay!) and I would like some kind of authentication going on.  The 
>> "credentials" system which works with basic tiddlywiki would be great.   
>> However, when I run it with something like:
>>
>> node ./tiddlywiki.js Wikis/BobWiki/ --wsserver credentials=creds.csv 
>> "readers=(anon)" "writers=(authenticated)"
>>
>> the credentials don't seem to have any effect at all.  Anyone can still 
>> edit it.
>>
>> are those even supposed to work with Bob?
>>
>> if not, are there any other simple actions?
>>
>> I tried just putting Basic Auth on in my nginx config, but that seemed to 
>> break Bob completely.
>>
>>
>>
>>
>>

-- 
You received this message because you 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/b81f6562-424f-4e63-8721-6752050c4c9dn%40googlegroups.com.

Re: [tw5] Re: [Comment] My Ongoing Irritations with Google Groups

Oof, I have had *minor* annoyances with Google Groups posting, but sounds 
like nothing near what you guys (Soren / Saq) have been having. That does 
make things more urgent in my opinion. 

*Plugins*
As we contemplate migrating the community to another platform, aside from 
making it nicer / more stable to post, and making it easier to find posts, 
I'd personally be most interested in the potential for using the same 
platform for "plugins". I bring this up, because this could/would compete 
with the current links.tiddlywiki.com effort. Don't get me wrong, I love 
the concept, but I think it could be improved on, and I think those 
improvements would be easy/built-in on another forum platform. Most notably 
to make it easy for *all* users to upvote to get some ranking going. I 
think this is helpful for the new-user experience. When I start with other 
software that has user-plugin capabilities (image editing software 
paint.net - forums.getpaint.net for instance) I'll usually go to the 
plugins and expect to see the most common popular ones up top and look at 
those first. The thing about *user-generated* plugins is that you *don't 
know* if those plugins work now, or if they'll continue to work. But, as a 
shortcut if you know they're very widely used, and greatly liked you can 
feel a little more confident that someone is either maintaining it, or 
would take it over if it became abandoned. I realize that there is a way 
for people to contribute (reading the "How To Contribute" page now), but 
given that it requires doing a "Github pull request" which even *I* don't 
understand, let's just agree it could be a bit easier for new users without 
developer backgrounds. 

*Maintenance*
On a related note, there's discussion here about some level of maintenance 
of the information - Jeremy has brought it up a couple of times in this 
thread. Obviously one way to get that is to have a good ranking / voting 
system like I mention above. I'm also curious if anyone here has any 
knowledge of "free internships"? At my company we have an intern program 
that's obviously not free, but I feel like I've heard of some voluntary 
open-source software companies having / working with people who are willing 
to work on a free internship - basically just for resume building. Maybe 
that's something that somebody here knows could be an option?

On Monday, June 7, 2021 at 4:05:40 AM UTC-4 saq.i...@gmail.com wrote:

>
>> However, the editing experience, while it used to be tolerable, has 
>> become horrendous since the latest UI “upgrade”. I regularly have the 
>> screen get corrupted or lose data (wtf, how did this become acceptable), 
>> and doing code formatting is a huge pain now.
>>
>>
>> I generally compose via email but my understanding is that it is no 
>> longer straightforward to make monospaced blocks, which does indeed seem 
>> pretty poor.
>>
>  
> Jeremy just so you are aware, the issues with posting via the web 
> interface go beyond just difficulty in making monospaced blocks. Like 
> Soren, I often experience that the UI glitches out and I lose what I have 
> written. Combined with the difficulties in replying from mobile, I find 
> myself rarely having enough motivation to participate in the group now. 
>
> I've tried to attach a screenshot of what writing this post was like... 
>
> [image: Screenshot 2021-06-07 100214.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/991f387a-e5bd-42ca-a3dd-6df12eaa96e4n%40googlegroups.com.

Re: [tw5] TiddlyWiki Documentation - Syntax

Great continued feedback. I'll keep going, but just to mass-reply:

PMario

   - I agree that the "closed version" should be in a small general syntax 
   notes area - maybe right below the syntax block. Things like:
  - Each attribute can be given as "Text Value", {{Trancluded Value}}, 
  or <>
   - Still thinking through how to handle the "or" situations (need tiddler 
   value or tiddler and field, or just field, or tiddler and index...)
  - Soren had the one example which might be great. I currently don't 
  understand it clearly though, so will think on how to simplify it
   
Tones

   - I'm not that familiar with screen readers etc. but if you want to take 
   a crack at an example to help me understand, I'd be happy to look at it

Ste

   - I'll check out the stretch text thing. Others have suggested details 
   which seems to have similar aims (though is non-core)

Mohammad / Odin / TiddlyTweeter

   - I think version 1 is good myself, and version 3 for completeness. 
   Might think about the best method to include both - via some mechanism like 
   stretch-text / details / reveal / tabs (most core-ish I think)

 (PMario / TiddlyTweeter)

   - Funnily enough the *only* thing that I can see useful about the 
   <$details> widget is that it *doesn't* store the state (which keeps size & 
   # of changes down).
   - To TiddlyTweeter's point, if <$details> stored state, wouldn't it just 
   be a less-flexible <$reveal>?

Thanks all, I'll keep plugging along and circle back to get more feedback 
in a while. 

On Monday, June 7, 2021 at 5:47:53 AM UTC-4 TiddlyTweeter wrote:

>
> TiddlyTweeter wrote:
>>
>>> ... using either *<$reveal>... *or ... to hide sections so its 
>>> not too overwhelming and the end-user can expand only the sections they 
>>> need to see.
>>
>>
> PMario replied: 
>
>> At the moment Jeremy doesn't accept PRs that contain the  
>> element, because it doesn't store open/close state. 
>> I think, we need a <$details> widget, that can handle persistent state, 
>> in the core first.
>>
>
> HA!*  *is super simple. ADD "open" or remove it. 
> *   Should be a doddle. *
> It is NOT intelligent like *<$reveal> *which handles well complex 
> situations, but in MANY use cases  binary sate is all you need.
>
> Side comment
> TT
>

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

Re: [tw5] TiddlyWiki Documentation - Syntax



> TiddlyTweeter wrote:
>
>> ... using either *<$reveal>... *or ... to hide sections so its 
>> not too overwhelming and the end-user can expand only the sections they 
>> need to see.
>
>
PMario replied: 

> At the moment Jeremy doesn't accept PRs that contain the  
> element, because it doesn't store open/close state. 
> I think, we need a <$details> widget, that can handle persistent state, 
> in the core first.
>

HA!*  *is super simple. ADD "open" or remove it. 
*   Should be a doddle. *
It is NOT intelligent like *<$reveal> *which handles well complex 
situations, but in MANY use cases  binary sate is all you need.

Side comment
TT

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

Re: [tw5] Re: German documentation / deutsche Dokumentation

On Monday, June 7, 2021 at 10:09:54 AM UTC+2 PMario wrote:

Wir können einige macros + text und CSS an die "Deutsche" Mentalität 
> anpassen, aber wir sollten die Namen unbedingt behalten. ... 
>

zB: Mir gefällt folgende Änderung sehr gut. 

[image: doc-improvement-example.gif]
Wir sollten das Format vereinheitlichen und dann als PR für den "Core" 
vorschlagen, wenn wir sicher sind, dass es für uns passt. 

-mar

-- 
You received this message because you 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/cfd25c55-fa7a-49a4-a442-6095b02f4ab7n%40googlegroups.com.

Re: [tw5] TiddlyWiki Documentation - Syntax

On Monday, May 31, 2021 at 10:06:33 AM UTC+2 TiddlyTweeter wrote:

... using either *<$reveal>... *or ... to hide sections so its not 
> too overwhelming and the end-user can expand only the sections they need to 
> see.

At the moment Jeremy doesn't accept PRs that contain the  element, 
because it doesn't store open/close state. 
I think, we need a <$details> widget, that can handle persistent state, in 
the core first. 

-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/66c42839-81a5-40cd-8a91-692a8c311d9dn%40googlegroups.com.

Re: [tw5] TiddlyWiki Documentation - Syntax

On Saturday, May 29, 2021 at 6:10:32 PM UTC+2 Stobot wrote:

Examples - more complex = Edit-text
> [image: edit-text-widget.PNG]
>

I personally would favour Version 1 for the Intro overview. 

The valure-options as shown in Versioin 2 should be part of the detailed 
description in the "Attributes table"

Just my thoughts.
-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/fab36a70-5fbb-44c2-9060-f6eb3d889794n%40googlegroups.com.

Re: [tw5] Re: German documentation / deutsche Dokumentation