date:20210818

Soren,

I too think this is a great idea. Some of the miss understandings are 
listed in my documents, built on Tobias's efforts before 
here https://anthonymuscio.github.io/#Standard%20Nomenclature and tiddlers 
pointed to there in.

   - In particular to support Jeremy's point see   ❷ Widget and HTML 
   attributes or parameters
   - The items that have strike through are incorrect and will point to 
   some of these.
   - I am happy if I get a critical review of these notes.
   - We and I, have often struggled with when we need to Wikify to get an 
   intermediate result rather than pass wiki text on to be rendered later.
   
By the way I love you work on Grok and support it totally but given my 
experience it is too verbose for me to work through, this is perfect for 
newer users for sure.  If you wanted to add content for more experienced 
users/designers/devs to review and contribute to, perhaps you could provide 
a special index for the different kind of user. I would be able to help 
more if you did. Although this kind of question here is a good approach.

Love your work
Tones


On Thursday, 19 August 2021 at 00:54:29 UTC+10 Jeremy Ruston wrote:

> Hi Soren,
>
> I'm working on adding a chapter (or back-matter section, not sure yet) 
> called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I have 
> two sections:
>
>
> Excellent idea, I think that will be very helpful.
>
>
>- Macros are not function calls
>- Constant strings cannot be combined with transclusions
>
> Are there other common misunderstandings – in terms of incorrect mental 
> models of how TiddlyWiki operates, or things one might expect to work that 
> don't – that come up here or elsewhere that you'd like to see documented in 
> such a section?
>
>
> The first one I thought of was the way that  >}}> 
> doesn't work, but I see that you covered that in the 2nd example.
>
> Feedback on the drafts of the two existing sections would be welcome as 
> well:
>
>
> https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
>   
> 
>  
>
>
> Excellent stuff, it's great to see how you can write from the perspective 
> of beginners while being such a knowledgable and advanced user yourself.
>
> Best wishes
>
> Jeremy
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/af072926-33d7-4414-840e-e0741671f52bn%40googlegroups.com
>  
> 
> .
>
>

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

[tw5] Re: seeing what the transfering of tiddlywiki to a more self-coded platform can look like

Jamm

Perhaps you could describe this with more detail, what are you trying to 
achieve, define "self-coded platform" etc.., because this forum is for a 
more general audience. Tiddlywiki is a non-trivial Quine which makes me ask 
is it not already a " self-coded platform ".

Otherwise if this is tiddlywiki as platform or development related please 
start a discussion on the dev 
channel https://github.com/Jermolene/TiddlyWiki5/discussions

Personally I am not a developer but I am a super user/designer, and often 
things can be done already, without development, javascript or other 
coding.  Developers with their development hammer often think everything is 
a coding nail. When in fact possibilities already exist be it widget, 
filters, editions, plugins that are already available. Eric and PMario (to 
name a few) are so well versed in TiddlyWIki you would be surprised how 
they can achieve anything, I am striving to be as good as they are, but 
from the designer perspective.

I consider TiddlyWiki is a platform, it can even generate new wikis, ie be 
its own software development kit. I am keen for newcomers to contribute 
their coding skills, but would prefer it be to address gaps rather reinvent 
something. Just my personal view.

But we are open to all ideas, so please spell yours out a little more, to a 
larger audience.

Regards
Tones

On Thursday, 19 August 2021 at 05:31:10 UTC+10 jamm...@gmail.com wrote:

> I'm looking to see what the transfering of tiddlywiki to a more self-coded 
> platform, such as jekyll, gatsby, or others, can look like. My concern is 
> the transition being difficult, long, etc. Any resources?
>

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

[tw5] Re: I Think I Hacked TiddlyWiki

Thanks all for considering this;

I think the best way to limit risks is to provide plugins in trusted 
libraries, from trusted sources. then people could also install these in an 
empty html and run a vulnerability test using a plugin designed to 
highlight risks. As soon as a library contains something doggy the 
community can react.  

To facilitate this I would like an easy way to collect and publish a 
library from a single file wiki, then the well known and trusted people can 
publish libraries that they themself can check or anyone in the community. 
Libraries contain plugins frozen in a moment of time, Only libraries so 
tested would be listed publicly. With all other sources the designer can 
run a (latest) vulnerability test published on tiddlywiki.com and if we 
must we can blacklist or whitelist plugins or "signatures" in this 
vulnerability tester.

In another discussion I am also calling for a hash tool which although not 
invulnerable would add another layer of testing, mostly to see which system 
tiddlers have being modified, and this would just make cheating more 
difficult.

The power we have on our side is the community and the ability to collect 
and centralise data in a way that "outsiders" have more work to do before 
they can compromise anyone to a large extent, ie make it harder and cause 
diminishing returns. We can also ensure we have trusted sources and be able 
to test them. In this light we may even benefit from people hacking, 
because we can identify the vectors and respond.

But finally I want to reinforce in many wiki editions or personal on my 
desktop/mobile only, I do not want features crippled, diminished or 
destroyed for when the wiki may be placed on an internet facing editable 
platform. This is why I think the vulnerability test tool has the greatest 
value. Horses for courses.

Regards
Tones

On Thursday, 19 August 2021 at 08:55:14 UTC+10 joshua@gmail.com wrote:

> I agree that there are a lot of possible open "attack vectors", and 
> keeping track of every one is not feasable.
>
> Good conversation so far. I think the primarily concern is that TW will 
> run obfuscated javascript without a refresh required. That should have an 
> option to "Sandbox" that behaviour somehow, and let superusers unlock it.
>
> Thanks for the discussion!
>
> Best,
> Joshua Fontany
>
> On Wednesday, August 18, 2021 at 9:44:03 AM UTC-7 Mark S. wrote:
>
>> Really, it gets back to trust and reputation.
>>
>> A TW coder could write a tiddler that contains no javascript tiddlers, 
>> but that, when run, creates a javascript  tiddler that will later get run. 
>> So you would never see javascript code during import. The core TW is 
>> already pretty huge. Adding patch after patch for each imagined scenario 
>> eventually renders TW less and less useful.
>>
>> Also, it hasn't been demonstrated what harm could be done even if your 
>> standalone code was infiltrated. Could keystrokes be sent back to a server? 
>> Could file blocks be written anywhere other than the download directory? Of 
>> course on node or especially on any multi-user platform things become more 
>> hazardous.  In theory any server-based solution (e.g. node) could write to 
>> your file system and possibly invoke code. In practice, I found it very 
>> difficult to set up even when I wanted something like that.
>>
>>
>>  
>>
>>
>> On Wednesday, August 18, 2021 at 9:22:27 AM UTC-7 R² wrote:
>>
>>> Excellent points John. Most users will indeed not review the full text 
>>> of every single tiddler they import. I'm now thinking that pointing out 
>>> which ones should indeed be reviewed more explicitly would be both easy and 
>>> worthwhile.
>>>
>>> At the tm-import-tiddlers widget level, any JS that's being imported 
>>> could be flagged, with a simple highlight inviting the user to review the 
>>> code before confirming the import when standard declared JS is detected, 
>>> and a more insistent alert when the code is hidden or obfuscated (as in 
>>> Finn's Base64 example). A simple exhaustive filter search should be able to 
>>> cover all or most cases, including content-type=application/javascript, 
>>>

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

Stephanie

It took a little time to wade through the combinations. I also found there 
are possibly many ways to do this.

The attached json has a view template that displays the detail or 
references if they exist according to your specs, the view template itself 
is for all other setting and the testn tiddlers demonstrate each of the 
formats. 

Here is the content of the viewtemplate
\define reference-only() {{!!reference}}.
\define page-reference() {{!!reference}}, {{!!details}}
\define not-page-reference()
<$list filter="[lowercase[]match]" 
variable=nul> 
{{!!reference}} — {{!!details}}

<$list filter="[lowercase[]!match]" 
variable=nul> 
{{!!reference}}. {{!!details}}

\end

<$list filter="[all[current]has[details]] [all[current]has[reference]] 
+[limit[1]]" variable=nul>
<$wikify name=details-start text="""{{{ [all[current]get[details]split[ 
]first[]] }}}""">
<$list filter="[all[current]get[details]]" variable=nul 
emptyMessage=<> >
   <$list filter="[match[p.]] [match[pp.]]" 
emptyMessage=<>  variable=nul>
   <>
   




Basically I define some alternative layouts with define, some with logic. 
These transclude the reference and details fields so any wiki text therein 
is rendered.

Then from  

   - first we test if we have anything todo - reference and/or details has 
   content
   - Then we get and wikify a filtered transclusion to get the first word
   - Then if not details exist we use the  reference-only layout
   - else if we do have details we test if it contains a page-reference and 
   use that layout if so
   - else (emptyMessage) we use the  not-page-reference layout
  - Every other case uses this.
   
To handle the first character upper or lower case I am simply testing to 
see if the first word matches all lower or not, it does the same job but 
could be tricked. eg "tHis" would trip the capital test. This can be 
refined, however I expect you would then edit it to correct it anyway.

So the main mechanism I use is the list widget with filtered tests and 
emptyMessage. As I asserted best put the formatting separate from the 
content/data.

Regards
Tones
On Thursday, 19 August 2021 at 09:48:02 UTC+10 joshua@gmail.com wrote:

> Stéphane,
>
> Some-one on GitHub in the bug report (link) mentioned that you can "view" 
> the raw text of a field with the View Widget.
>
> So, where as {{foo!!bar}} is a shortcut for 
>
> <$tiddler tiddler="foo"><$translcude tiddler=<> 
> field="bar"/>
>
> You can create a macro that uses the View Widget like so:
>
> ```
> \define viewField(tiddler,field)
> <$tiddler tiddler=$tiddler$><$view field=$field format="text"/>
> \end
>
> <> <>
> ```
> You could even use the View Widget directly if the defaults would do fine:
>
> ```
> <$tiddler  tiddler="tiddler a">
> <$view  field="foo"/><$view field="bar"/>
> 
> ```
>
> If you had wikitext in the field that needed to be proccessed, you could 
> use a different "format" value: https://tiddlywiki.com/#ViewWidget
>
> Best,
> Joshua Fontany
>
> On Wednesday, August 18, 2021 at 2:20:51 PM UTC-7 Misterel85 wrote:
>
>> Thank you for your very interesting and useful examples, Tones. I didn't 
>> know about `sentencecase`! I'll keep that post as a reference. 
>> And thank you very much for proposing your help.
>>
>> Sorry for not replying sooner. I've spent the last two days thinking 
>> those field connexion rules over for my project and I can say they are not 
>> that obvious to define. Anyway, here is something that would correspond to 
>> my needs, but it needs 'conditional transclusion'. So I gladly accept your 
>> offer.
>>
>> So, in order to manage my sources, I have a 'reference' field for general 
>> information and a 'details' field for any additional information, that I 
>> must transclude in that order: `reference` + `details`.
>>
>> Here's how I see things:
>>
>> * the value in 'details' may start with `p. ` (for page) or `pp. ` (for 
>> pages).
>> Then I would connect 'reference' and 'details' with `, ` (comma + 
>> whitespace).
>> For instance:
>> Doe, John. //My Great Exercise Book// (2019), pp. 28-32.
>>
>> * the value in 'details' may start with a word in lowercase: `exercise 
>> 2`, `chapter 4`, etc.
>> Then I would connect 'reference' and 'details' with ` — ` (whitespace + 
>> dash + whitespace).
>> For instance:
>> Doe, John. //My Great Exercise Book// (2019) — chapter 6 exercise 5 
>> p. 61.
>> 
>> * the value in details may start with the first word having a capital 
>> letter (uppercase), to start a short sentence.
>> Then I would connect 'reference' and 'details' with `. ` (period + 
>> whitespace).
>> For instance:
>> August 2018 training session with John Doe. See short video for this 
>> exercise on YouTube.
>>
>> * if the `details` field is empty, then I would need to end the 
>> transclusion of `reference` with `.` (period).
>>
>> I'm not too sure what I should do if the value in `details` field starts 
>> with a character that is not a letter, which may happen in very

[tw5] Re: Import tiddlers w/ json including custom fields

By the way, when I said that the example "imported correctly" for me, it 
indeed did not include some of the fields...for some reason I foolishly 
decided not to mention that when I imported it even though I noticed. I am 
not however seeing the message jkm was where $:/Import said there were no 
tiddlers to import. So I think there are two separate problems here, the 
existence of duplicate tiddlers *and* some of the fields not being strings.

On Wednesday, August 18, 2021 at 6:46:35 PM UTC-5 TW Tones wrote:

> I can totally recommend Joshua's JSON mangler in cases likele this and csv.
>
>
>
> On Thursday, 19 August 2021 at 04:22:26 UTC+10 jkm...@gmail.com wrote:
>
>> New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23
>>
>> I'm able to import tiddlers from json with the title and text fields.  
>> But when I try to do it with a custom field the import tiddler shows no 
>> items to import.  All my custom fields begin with *kba* and some 
>> additional alphanumeric characters.  The json is valid according to 
>> jsonchecker.com.  Is this permitted?  Do I need to enable a feature or 
>> preconfigure a system component?  I've done a few searches in the group but 
>> didn't see anything that applied.  All help is appreciated.
>>
>> Imports:
>> [
>>   {
>> "title": "19464",
>> "text": "How to change the default root password"
>>   },
>>   {
>> "title": "20508",
>> "text": "Best Practices"
>>   }
>> ]
>>
>> Doesn't import:
>> [
>>   {
>> "title": "19464",
>> "text": "How to change the default root password",
>> "kbalink": " https://www.someplace.net/ 19464",
>> "kbarating": 3,
>> "kbasev": 0,
>> "kbasource": "LKBA",
>> "kbastale": 0,
>> "kbatweak": "",
>> "kbatype": "How To"
>>   },
>>   {
>> "title": "20508",
>> "text": "Best Practices",
>> "kbalink": "https://www.someplace.net/20508;,
>> "kbarating": 5,
>> "kbasev": 0,
>> "kbasource": "LKBA",
>> "kbastale": 0,
>> "kbatweak": "",
>> "kbatype": "Info"
>>   }
>> ]
>>
>

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

[tw5] Re: Gitmbed beta: A tool that complements TW

Flanc,

I will check it out today. I hope you remain obsessed with tiddlywiki 
because your contributions are proving top be substantial. Let me know if I 
can help you from a Superuser (rather than developer perspective) but of 
course posting here or soon discourse will share the love.

Thanks again
Tones

On Thursday, 19 August 2021 at 10:21:19 UTC+10 flanc...@gmail.com wrote:

> Hello Everybody,
>
> Yet again, I have had a flash of creativity, and, like usual built a new 
> tool which I believe could complement TiddlyWiki. This time, the tool is a 
> Chrome extension (pending for Chrome Web Store) which allows embedding of 
> external content/embeds into GitHub and other social media sites. 
>
> *How does This Apply To TiddlyWiki?*
> Long story short, you can now embed TiddlyWiki's into your README.md on 
> github, your instagram.com posts, and anything else on the web.
>
> For a demo, go to https://gitmbed.finnsoftware.net, and scroll all the 
> way down to the bottom. You should see a "View with Gitmbed" button, which, 
> when you click, takes you to the official gitmbed repo. 
>
> As Gitmbed is currently pending to get into the web store, you can test 
> the extension following the "Load Unpacked" instructions on that repo (
> github.com/flancast90/gitmbed).
>
> I'd appreciate your feedback, as this will be my very first published 
> Chrome/Edge extension, as well as hopefully my very-first very popular 
> code/extension that I hope many will take advantage of. And, as usual, if 
> you appreciate my work, show it with a star on GitHub ⭐.
>
> Also, for any other developers wondering about how this can work, given 
> that GitHub and other sites block these kinds of embeds, just email me, or 
> read the explanation at gitmbed.finnsoftware.net or the given GitHub.
>

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

[tw5] Gitmbed beta: A tool that complements TW

2021-08-18 Thread Finn Lancaster

Hello Everybody,

Yet again, I have had a flash of creativity, and, like usual built a new
tool which I believe could complement TiddlyWiki. This time, the tool is a
Chrome extension (pending for Chrome Web Store) which allows embedding of
external content/embeds into GitHub and other social media sites.

*How does This Apply To TiddlyWiki?*
Long story short, you can now embed TiddlyWiki's into your README.md on
github, your instagram.com posts, and anything else on the web.

For a demo, go to https://gitmbed.finnsoftware.net, and scroll all the way
down to the bottom. You should see a "View with Gitmbed" button, which,
when you click, takes you to the official gitmbed repo.

As Gitmbed is currently pending to get into the web store, you can test the
extension following the "Load Unpacked" instructions on that repo
(github.com/flancast90/gitmbed).

I'd appreciate your feedback, as this will be my very first published
Chrome/Edge extension, as well as hopefully my very-first very popular
code/extension that I hope many will take advantage of. And, as usual, if
you appreciate my work, show it with a star on GitHub ⭐.

Also, for any other developers wondering about how this can work, given
that GitHub and other sites block these kinds of embeds, just email me, or
read the explanation at gitmbed.finnsoftware.net or the given GitHub.

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

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

Stéphane,

Some-one on GitHub in the bug report (link) mentioned that you can "view" 
the raw text of a field with the View Widget.

So, where as {{foo!!bar}} is a shortcut for 

<$tiddler tiddler="foo"><$translcude tiddler=<> 
field="bar"/>

You can create a macro that uses the View Widget like so:

```
\define viewField(tiddler,field)
<$tiddler tiddler=$tiddler$><$view field=$field format="text"/>
\end

<> <>
```
You could even use the View Widget directly if the defaults would do fine:

```
<$tiddler  tiddler="tiddler a">
<$view  field="foo"/><$view field="bar"/>

```

If you had wikitext in the field that needed to be proccessed, you could 
use a different "format" value: https://tiddlywiki.com/#ViewWidget

Best,
Joshua Fontany

On Wednesday, August 18, 2021 at 2:20:51 PM UTC-7 Misterel85 wrote:

> Thank you for your very interesting and useful examples, Tones. I didn't 
> know about `sentencecase`! I'll keep that post as a reference. 
> And thank you very much for proposing your help.
>
> Sorry for not replying sooner. I've spent the last two days thinking those 
> field connexion rules over for my project and I can say they are not that 
> obvious to define. Anyway, here is something that would correspond to my 
> needs, but it needs 'conditional transclusion'. So I gladly accept your 
> offer.
>
> So, in order to manage my sources, I have a 'reference' field for general 
> information and a 'details' field for any additional information, that I 
> must transclude in that order: `reference` + `details`.
>
> Here's how I see things:
>
> * the value in 'details' may start with `p. ` (for page) or `pp. ` (for 
> pages).
> Then I would connect 'reference' and 'details' with `, ` (comma + 
> whitespace).
> For instance:
> Doe, John. //My Great Exercise Book// (2019), pp. 28-32.
>
> * the value in 'details' may start with a word in lowercase: `exercise 2`, 
> `chapter 4`, etc.
> Then I would connect 'reference' and 'details' with ` — ` (whitespace + 
> dash + whitespace).
> For instance:
> Doe, John. //My Great Exercise Book// (2019) — chapter 6 exercise 5 p. 
> 61.
> 
> * the value in details may start with the first word having a capital 
> letter (uppercase), to start a short sentence.
> Then I would connect 'reference' and 'details' with `. ` (period + 
> whitespace).
> For instance:
> August 2018 training session with John Doe. See short video for this 
> exercise on YouTube.
>
> * if the `details` field is empty, then I would need to end the 
> transclusion of `reference` with `.` (period).
>
> I'm not too sure what I should do if the value in `details` field starts 
> with a character that is not a letter, which may happen in very rare cases. 
> And I can still alter the value accordingly:
> For instance:
> [[Comprehensive Exercise Website|www.to.the.link.com]] — "Exercises" 
> tab, bottom of page.
> might be replaced with:
> [[Comprehensive Exercise Website|www.to.the.link.com]]. See 
> "Exercises" tab, bottom of page.
>
> I hope the goals I have set are clearly explained and above all doable.
>
> I suppose that making liberal use of list filters and operators such as 
> 'split', 'join', 'append', 'match', it could be possible to build those 
> 'conditional field transclusions', but I don't think I could do that alone!
>
> Regards,
>
> -Stéphane
>
> Le lundi 16 août 2021 à 14:45:29 UTC+2, TW Tones a écrit :
>
>> Misterel,
>>
>> Perhaps my writing is not so helpful, but my advice is intended to make 
>> it simpler for you. I would be happy to write the code to resolve the 
>> concatenation of various text snippets into sentence like text. All I would 
>> need is samples of the text you whish to join (without presentation related 
>> hacks eg leading spaces etc...
>>
>> The first examples would be foo="This is foo"  bar="and this is bar." 
>> please join as a sentence.
>>
>> Feel free to be pragmatic and decline my offer but also feel free to ask.
>>
>> Here are some examples to look at, paste into a tiddler on tiddlywiki.com, 
>> add the foo and bar fields as before. 
>> See how alice and bob values are independent of the order in which they 
>> will be presented, used?
>>
>> \define full() {{!!foo}} {{!!bar}}
>> \define full2() $(foo)$ $(bar)$
>> \define full3() $(alice)$ and $(bob)$.
>>
>> ```
>> \define full() {{!!foo}} {{!!bar}}
>> \define full2() $(foo)$ $(bar)$
>> \define full3() $(alice)$ and $(bob)$.
>> ```
>>
>> <$vars
>> foo="This is foo"  
>> bar="and this is bar."
>> alice="this is Alice"
>> bob="this is Bob"
>> cat="this is cat"
>> >
>>
>> # `<> <>` <> <>
>> # `{{!!foo}} {{!!bar}}`  {{!!foo}} {{!!bar}}
>> # `{{{ [] [] +[join[ ]] }}}` {{{ [] [] +[join[ ]] }}}
>> # `<$text text={{{ [] [] +[join[ ]] }}}/>` <$text text={{{ 
>> [] [] +[join[ ]] }}}/>
>> # `<$text text={{{ [{!!foo}] [{!!bar}] +[join[ ]] }}}/>` <$text text={{{ 
>> [{!!foo}] [{!!bar}] +[join[ ]] }}}/>
>> #`<>` <>
>> #`<>` <>
>> #`<>` <> | {{{ [sentencecase[]] }}}
>> #`{{{ [] [] +[join[ and

[tw5] Re: Import tiddlers w/ json including custom fields

I can totally recommend Joshua's JSON mangler in cases likele this and csv.



On Thursday, 19 August 2021 at 04:22:26 UTC+10 jkm...@gmail.com wrote:

> New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23
>
> I'm able to import tiddlers from json with the title and text fields.  But 
> when I try to do it with a custom field the import tiddler shows no items 
> to import.  All my custom fields begin with *kba* and some additional 
> alphanumeric characters.  The json is valid according to jsonchecker.com.  
> Is this permitted?  Do I need to enable a feature or preconfigure a system 
> component?  I've done a few searches in the group but didn't see anything 
> that applied.  All help is appreciated.
>
> Imports:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password"
>   },
>   {
> "title": "20508",
> "text": "Best Practices"
>   }
> ]
>
> Doesn't import:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password",
> "kbalink": " https://www.someplace.net/ 19464",
> "kbarating": 3,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "How To"
>   },
>   {
> "title": "20508",
> "text": "Best Practices",
> "kbalink": "https://www.someplace.net/20508;,
> "kbarating": 5,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "Info"
>   }
> ]
>

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

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

I am in favor of stripping out leading and trailing whitespace in field 
Names during field creation and tiddler import.

Best,
Joshua F

On Wednesday, August 18, 2021 at 1:38:29 PM UTC-7 Soren Bjornstad wrote:

> I'll preface this by saying this probably belongs in a GitHub issue, and 
> I'll be happy to create one over there if we want one. But wanted to get 
> people's thoughts first, and ASAP because now is our last chance to do this 
> without breaking backwards compatibility (once 5.2.0 is released, it would 
> be pretty hard to change).
>
> Would it make sense to *prohibit leading and trailing whitespace in field 
> names*, even though we now allow whitespace elsewhere? In the prerelease, 
> it's not possible to add such fields within the GUI, but you can import 
> tiddlers that contain such fields, or create them with an action or 
> $edit-text widget. Fields with leading or trailing whitespace are almost 
> impossible to distinguish within the GUI, since there is already whitespace 
> before and after the name when it's displayed.
>
> In addition, if we continue to prohibit leading and trailing whitespace, I 
> think we would be able to allow whitespace in between filter steps, which 
> is a common annoyance for new users (but maybe I'm missing something there).
>
> I can't think of any situation in which someone would *want* leading or 
> trailing whitespace in a field name, except maybe to integrate with another 
> system which allowed it for some reason – as evidenced by the fact that the 
> GUI doesn't even let you create such a field. At any rate, it seems much 
> more confusing than helpful. Unix filenames have suffered enormously 
>  from being 
> overly permissive in what characters they allow, including leading and 
> trailing whitespace; my instinct tells me this is likely to be a continuing 
> irritation.
>
> On the minus side, someone would of course have to implement checks to 
> prevent these fields from being added.
>

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

[tw5] Re: Import tiddlers w/ json including custom fields

The "Deserializer" for "application/json" files that are Objects (with 
minimum "title" field), or Arrays of such objects, does include a check to 
see if the value is a string:
```
if(typeof incomingFields[f] === "string") { fields[f] = incomingFields[f]; }
```
This is stripping out your other data.

I have a set of JSON tools that helps around this issue: 
https://chronicles.wiki/TW5-JsonMangler/

The worflow would be to drag& drop the JSON file into a wiki with the 
plugin installed, and use the Import tools in the JSON tiddler's toolbar to 
import each object as its own tiddler.

You can even map json field names to tiddler field names, and there's some 
other options.

Best,

Joshua Fontany
On Wednesday, August 18, 2021 at 12:45:50 PM UTC-7 springer wrote:

> JKM, 
>
> After putting quotes around your numbers (and fixing where a So-called 
> "smart" quote had crept in during my editing, sorry about my earlier post, 
> now deleted), both records import fine for me.
>
> I have found that raw numbers for field content (as in your kbarating 
> field) will not work; only data enclosed in quote marks seems to work.
>
> Note the field data (beyond title and text) doesn't show in the import 
> preview tiddler. But the data should be in there, as you can confirm by 
> entering edit mode for the tiddlers once imported.
>
> -Springer
>
> On Wednesday, August 18, 2021 at 2:22:26 PM UTC-4 jkm...@gmail.com wrote:
>
>> New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23
>>
>> I'm able to import tiddlers from json with the title and text fields.  
>> But when I try to do it with a custom field the import tiddler shows no 
>> items to import.  All my custom fields begin with *kba* and some 
>> additional alphanumeric characters.  The json is valid according to 
>> jsonchecker.com.  Is this permitted?  Do I need to enable a feature or 
>> preconfigure a system component?  I've done a few searches in the group but 
>> didn't see anything that applied.  All help is appreciated.
>>
>> Imports:
>> [
>>   {
>> "title": "19464",
>> "text": "How to change the default root password"
>>   },
>>   {
>> "title": "20508",
>> "text": "Best Practices"
>>   }
>> ]
>>
>> Doesn't import:
>> [
>>   {
>> "title": "19464",
>> "text": "How to change the default root password",
>> "kbalink": " https://www.someplace.net/ 19464",
>> "kbarating": 3,
>> "kbasev": 0,
>> "kbasource": "LKBA",
>> "kbastale": 0,
>> "kbatweak": "",
>> "kbatype": "How To"
>>   },
>>   {
>> "title": "20508",
>> "text": "Best Practices",
>> "kbalink": "https://www.someplace.net/20508;,
>> "kbarating": 5,
>> "kbasev": 0,
>> "kbasource": "LKBA",
>> "kbastale": 0,
>> "kbatweak": "",
>> "kbatype": "Info"
>>   }
>> ]
>>
>

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

[tw5] Re: Error when using musicsheets widget

2021-08-18 Thread Eric Shulman

On Wednesday, August 18, 2021 at 3:28:33 PM UTC-7 Psalm 104:33 KJV wrote:

> I am a musician and enjoy researching and cataloging things. Tiddlywiki 
> combined with  the musicsheets  
> widget looks like my dream come true. 
> I have attempted to install the musicsheets widget several times, but 
> cannot seem to get past this error (attached). 
>

According to that error message, the *music-score/widgets/musicsheets.js* 
module needs to also have *music-score/abcjs-midi.js* installed.

*http://musicsheets.tiddlyspot.com/#%24%3A%2Fplugins%2Ftiddlywiki%2Fmusic-score*
indicates that , the "Music Sheets and Midi" plugin has the following 
components:

   - $:/plugins/tiddlywiki/music-score/abcjs-midi.css 
   

   - $:/plugins/tiddlywiki/music-score/abcjs-midi.js 
   

   - $:/plugins/tiddlywiki/music-score/readme 
   

   - $:/plugins/tiddlywiki/music-score/soundfonts/grand-piano.json 
   

   - $:/plugins/tiddlywiki/music-score/soundfonts/tuba.json 
   

   - $:/plugins/tiddlywiki/music-score/widgets/musicsheet.js 
   


Thus, to properly install the plugin, you should drag-and-drop
*http://musicsheets.tiddlyspot.com/#%24%3A%2Fplugins%2Ftiddlywiki%2Fmusic-score*
onto your TiddlyWiki and import it.  Then save-and-reload so all the 
components can be unpacked.

enjoy,
-e

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

[tw5] Re: I Think I Hacked TiddlyWiki

I agree that there are a lot of possible open "attack vectors", and keeping 
track of every one is not feasable.

Good conversation so far. I think the primarily concern is that TW will run 
obfuscated javascript without a refresh required. That should have an 
option to "Sandbox" that behaviour somehow, and let superusers unlock it.

Thanks for the discussion!

Best,
Joshua Fontany

On Wednesday, August 18, 2021 at 9:44:03 AM UTC-7 Mark S. wrote:

> Really, it gets back to trust and reputation.
>
> A TW coder could write a tiddler that contains no javascript tiddlers, but 
> that, when run, creates a javascript  tiddler that will later get run. So 
> you would never see javascript code during import. The core TW is already 
> pretty huge. Adding patch after patch for each imagined scenario eventually 
> renders TW less and less useful.
>
> Also, it hasn't been demonstrated what harm could be done even if your 
> standalone code was infiltrated. Could keystrokes be sent back to a server? 
> Could file blocks be written anywhere other than the download directory? Of 
> course on node or especially on any multi-user platform things become more 
> hazardous.  In theory any server-based solution (e.g. node) could write to 
> your file system and possibly invoke code. In practice, I found it very 
> difficult to set up even when I wanted something like that.
>
>
>  
>
>
> On Wednesday, August 18, 2021 at 9:22:27 AM UTC-7 R² wrote:
>
>> Excellent points John. Most users will indeed not review the full text of 
>> every single tiddler they import. I'm now thinking that pointing out which 
>> ones should indeed be reviewed more explicitly would be both easy and 
>> worthwhile.
>>
>> At the tm-import-tiddlers widget level, any JS that's being imported 
>> could be flagged, with a simple highlight inviting the user to review the 
>> code before confirming the import when standard declared JS is detected, 
>> and a more insistent alert when the code is hidden or obfuscated (as in 
>> Finn's Base64 example). A simple exhaustive filter search should be able to 
>> cover all or most cases, including content-type=application/javascript, 
>>

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

2021-08-18 Thread Eric Shulman

On Wednesday, August 18, 2021 at 1:57:26 PM UTC-7 PMario wrote:

> There has been a discussion recently, where a user needed to be able to 
> add whitespace as needed. And the description of the usecase made sense.
>

That discussion was related to having leading whitespace in a field 
*value*, not a field *name*, and then transcluding that field value into 
another tiddler.

-e

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

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

Mario,

I don't think the thread you linked is relevant. I'm talking about field 
*names*, not field values. And I don't see how it would break backwards 
compatibility with 5.1.x, because 5.1.x didn't allow *any* spaces in field 
names.

If I'm misunderstanding, please correct me (and can you link the 
discussions on GitHub?).

On Wednesday, August 18, 2021 at 3:57:26 PM UTC-5 PMario wrote:

> On Wednesday, August 18, 2021 at 10:38:29 PM UTC+2 Soren Bjornstad wrote:
>
>> I'll preface this by saying this probably belongs in a GitHub issue, and 
>> I'll be happy to create one over there if we want one. But wanted to get 
>> people's thoughts first, and ASAP because now is our last chance to do this 
>> without breaking backwards compatibility (once 5.2.0 is released, it would 
>> be pretty hard to change).
>>
>
> I think this won't happen because of backwards compatibility with 5.1.x. 
> There have been some discussions on github already. The conclusion was, we 
> keep the status quo and live with it. 
>
> There has been a discussion recently, where a user needed to be able to 
> add whitespace as needed. And the description of the usecase made sense. So 
> there are usecases. ... See: 
> https://groups.google.com/g/tiddlywiki/c/Cjy074MsfzM
>
> -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/6a244024-a0e2-4ff4-a855-cd72c190672en%40googlegroups.com.

[tw5] Error when using musicsheets widget

2021-08-18 Thread Psalm 104:33 KJV

Hello,

I am a musician and I love to research and catalog things. So when I found 
Tiddlywiki and musicsheets , it looked 
like my dreams had come true. 

Unfortunately I am getting an error (image attached).

I am using TW 5.1.23 on Chrome on OSX Catalina and Windows 10.

Can you please help?

Thank you!

(sorry if I posted this twice. I am new to using google groups and not sure 
if my first post went through)

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

[tw5] Error when using musicsheets widget

2021-08-18 Thread Psalm 104:33 KJV

Hello, 

I am a musician and enjoy researching and cataloging things. Tiddlywiki 
combined with  the musicsheets  widget 
looks like my dream come true. 

I have attempted to install the musicsheets widget several times, but 
cannot seem to get past this error (attached). 

I am using Tiddlywiki 5.1.23 on Chrome on OSX v10.15.7 and also on Windows 
10.

Can you guys please advise?

Thank you!

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

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

2021-08-18 Thread Abraham Samma

Plus, the Discourse site does not leak emails oh so liberally like GG!

On Thursday, August 19, 2021 at 12:39:09 AM UTC+3 abes...@gmail.com wrote:

> The Discourse interface makes it far better than GG, especially on mobile 
> imho. I think there are a couple of things the moderators and admins should 
> consider:
>
> 1. Allow cross-site replies; as seen above, it seems folks would prefer 
> being able to reply to GG posts from Discourse to ease the transition
> 2. Allow easy access to GG posts from Discourse, especially if the above 
> is technically unfeasible or difficult. Currently, one cannot easily click 
> somewhere on Discourse to go straight to the GG post. One has to either 
> manually search or click on some bookmarked link, and then find the post 
> manually.
>
> On Wednesday, August 18, 2021 at 3:34:45 AM UTC+3 clutterstack wrote:
>
>> I've logged in, but was unable to reply to a GG post over there, so came 
>> back here. :P
>>
>> I don't have a lot to say about it yet, but will come back to try it more.
>>
>> Best,
>> Chris
>>
>> On Tuesday, August 17, 2021 at 4:28:39 PM UTC-4 Mohammad wrote:
>>
>>> Also it should be mentioned that those who join the new forum will not 
>>> miss any post on Google Forum! as the new forum mirror GG forum!
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Wed, Aug 18, 2021 at 12:41 AM Saq Imtiaz  wrote:
>>>
 It would be great if we could get more community members to join the 
 new forum at https://talk.tiddlywiki.org/ and use it for discussions, 
 and provide feedback on how they find the user experience.

 Note that you can log in with a Google or Github account, or create a 
 new user account specifically for the forum.

 Saq

 On Tuesday, August 17, 2021 at 11:30:28 AM UTC+2 Jeremy Ruston wrote:

> The new Discourse forum at https://talk.tiddlywiki.org/ is an 
> experiment at this stage. At the moment, there's two way sync with Google 
> Groups, but if people like the new system then we will migrate fully over 
> to it.
>
> We'll be discussing it at the TiddlyWiki community call in a few hours 
> time:
>
>
> https://talk.tiddlywiki.org/t/aug-17th-2021-community-call-core-savers-syncers-upload-plugin-discourse-forum/28
>
> Best wishes
>
> Jeremy.
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 17 Aug 2021, at 09:23, Mohammad Rahmani  
> wrote:
>
> 
>
> Thanks for sharing BTC!
> I would like to have one central place to be informed about TW!
>
> Is this the one I wished?
>
>
>
> Best wishes
> Mohammad
>
>
> On Tue, Aug 17, 2021 at 12:22 PM BurningTreeC  
> wrote:
>
>> Hi tiddlywikians,
>>
>> there's this new TiddlyWiki forum at https://talk.tiddlywiki.org/
>>
>> Is the google group still a thing for you or are you going to move to 
>> the new Forum?
>>
>> just out of interest :)
>>
>> Best wishes,
>> BTC
>>
>> -- 
>> You received this message because you are subscribed to the Google 
>> Groups "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/d1c6b96b-968b-4f67-a602-f7dd1a17d905n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to tiddlywiki+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/CAAV1gMDVzrajBKsk-rNF910mhnV-a79UMD%3Dfk41ojdpkoReq_Q%40mail.gmail.com
>  
> 
> .
>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "TiddlyWiki" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to tiddlywiki+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/205a6ce9-0b82-46c2-bd59-7c0251da1864n%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

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

2021-08-18 Thread abes...@gmail.com

The Discourse interface makes it far better than GG, especially on mobile 
imho. I think there are a couple of things the moderators and admins should 
consider:

1. Allow cross-site replies; as seen above, it seems folks would prefer 
being able to reply to GG posts from Discourse to ease the transition
2. Allow easy access to GG posts from Discourse, especially if the above is 
technically unfeasible or difficult. Currently, one cannot easily click 
somewhere on Discourse to go straight to the GG post. One has to either 
manually search or click on some bookmarked link, and then find the post 
manually.

On Wednesday, August 18, 2021 at 3:34:45 AM UTC+3 clutterstack wrote:

> I've logged in, but was unable to reply to a GG post over there, so came 
> back here. :P
>
> I don't have a lot to say about it yet, but will come back to try it more.
>
> Best,
> Chris
>
> On Tuesday, August 17, 2021 at 4:28:39 PM UTC-4 Mohammad wrote:
>
>> Also it should be mentioned that those who join the new forum will not 
>> miss any post on Google Forum! as the new forum mirror GG forum!
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Wed, Aug 18, 2021 at 12:41 AM Saq Imtiaz  wrote:
>>
>>> It would be great if we could get more community members to join the new 
>>> forum at https://talk.tiddlywiki.org/ and use it for discussions, and 
>>> provide feedback on how they find the user experience.
>>>
>>> Note that you can log in with a Google or Github account, or create a 
>>> new user account specifically for the forum.
>>>
>>> Saq
>>>
>>> On Tuesday, August 17, 2021 at 11:30:28 AM UTC+2 Jeremy Ruston wrote:
>>>
 The new Discourse forum at https://talk.tiddlywiki.org/ is an 
 experiment at this stage. At the moment, there's two way sync with Google 
 Groups, but if people like the new system then we will migrate fully over 
 to it.

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


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

 Best wishes

 Jeremy.

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

 On 17 Aug 2021, at 09:23, Mohammad Rahmani  
 wrote:

 

 Thanks for sharing BTC!
 I would like to have one central place to be informed about TW!

 Is this the one I wished?



 Best wishes
 Mohammad


 On Tue, Aug 17, 2021 at 12:22 PM BurningTreeC  
 wrote:

> Hi tiddlywikians,
>
> there's this new TiddlyWiki forum at https://talk.tiddlywiki.org/
>
> Is the google group still a thing for you or are you going to move to 
> the new Forum?
>
> just out of interest :)
>
> Best wishes,
> BTC
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to tiddlywiki+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/d1c6b96b-968b-4f67-a602-f7dd1a17d905n%40googlegroups.com
>  
> 
> .
>
 -- 
 You received this message because you are subscribed to the Google 
 Groups "TiddlyWiki" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to tiddlywiki+...@googlegroups.com.

 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/CAAV1gMDVzrajBKsk-rNF910mhnV-a79UMD%3Dfk41ojdpkoReq_Q%40mail.gmail.com
  
 
 .

 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "TiddlyWiki" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to tiddlywiki+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/205a6ce9-0b82-46c2-bd59-7c0251da1864n%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/d649bdc1-4690-416a-b5d3-12d299c98a68n%40googlegroups.com.

[tw5] Re: How can I prevent TW from trimming leading space in field transclusion?

2021-08-18 Thread Misterel85

Thank you for your very interesting and useful examples, Tones. I didn't 
know about `sentencecase`! I'll keep that post as a reference. 
And thank you very much for proposing your help.

Sorry for not replying sooner. I've spent the last two days thinking those 
field connexion rules over for my project and I can say they are not that 
obvious to define. Anyway, here is something that would correspond to my 
needs, but it needs 'conditional transclusion'. So I gladly accept your 
offer.

So, in order to manage my sources, I have a 'reference' field for general 
information and a 'details' field for any additional information, that I 
must transclude in that order: `reference` + `details`.

Here's how I see things:

* the value in 'details' may start with `p. ` (for page) or `pp. ` (for 
pages).
Then I would connect 'reference' and 'details' with `, ` (comma + 
whitespace).
For instance:
Doe, John. //My Great Exercise Book// (2019), pp. 28-32.

* the value in 'details' may start with a word in lowercase: `exercise 2`, 
`chapter 4`, etc.
Then I would connect 'reference' and 'details' with ` — ` (whitespace + 
dash + whitespace).
For instance:
Doe, John. //My Great Exercise Book// (2019) — chapter 6 exercise 5 p. 
61.

* the value in details may start with the first word having a capital 
letter (uppercase), to start a short sentence.
Then I would connect 'reference' and 'details' with `. ` (period + 
whitespace).
For instance:
August 2018 training session with John Doe. See short video for this 
exercise on YouTube.

* if the `details` field is empty, then I would need to end the 
transclusion of `reference` with `.` (period).

I'm not too sure what I should do if the value in `details` field starts 
with a character that is not a letter, which may happen in very rare cases. 
And I can still alter the value accordingly:
For instance:
[[Comprehensive Exercise Website|www.to.the.link.com]] — "Exercises" 
tab, bottom of page.
might be replaced with:
[[Comprehensive Exercise Website|www.to.the.link.com]]. See "Exercises" 
tab, bottom of page.

I hope the goals I have set are clearly explained and above all doable.

I suppose that making liberal use of list filters and operators such as 
'split', 'join', 'append', 'match', it could be possible to build those 
'conditional field transclusions', but I don't think I could do that alone!

Regards,

-Stéphane

Le lundi 16 août 2021 à 14:45:29 UTC+2, TW Tones a écrit :

> Misterel,
>
> Perhaps my writing is not so helpful, but my advice is intended to make it 
> simpler for you. I would be happy to write the code to resolve the 
> concatenation of various text snippets into sentence like text. All I would 
> need is samples of the text you whish to join (without presentation related 
> hacks eg leading spaces etc...
>
> The first examples would be foo="This is foo"  bar="and this is bar." 
> please join as a sentence.
>
> Feel free to be pragmatic and decline my offer but also feel free to ask.
>
> Here are some examples to look at, paste into a tiddler on tiddlywiki.com, 
> add the foo and bar fields as before. 
> See how alice and bob values are independent of the order in which they 
> will be presented, used?
>
> \define full() {{!!foo}} {{!!bar}}
> \define full2() $(foo)$ $(bar)$
> \define full3() $(alice)$ and $(bob)$.
>
> ```
> \define full() {{!!foo}} {{!!bar}}
> \define full2() $(foo)$ $(bar)$
> \define full3() $(alice)$ and $(bob)$.
> ```
>
> <$vars
> foo="This is foo"  
> bar="and this is bar."
> alice="this is Alice"
> bob="this is Bob"
> cat="this is cat"
> >
>
> # `<> <>` <> <>
> # `{{!!foo}} {{!!bar}}`  {{!!foo}} {{!!bar}}
> # `{{{ [] [] +[join[ ]] }}}` {{{ [] [] +[join[ ]] }}}
> # `<$text text={{{ [] [] +[join[ ]] }}}/>` <$text text={{{ 
> [] [] +[join[ ]] }}}/>
> # `<$text text={{{ [{!!foo}] [{!!bar}] +[join[ ]] }}}/>` <$text text={{{ 
> [{!!foo}] [{!!bar}] +[join[ ]] }}}/>
> #`<>` <>
> #`<>` <>
> #`<>` <> | {{{ [sentencecase[]] }}}
> #`{{{ [] [] +[join[ and ]addsuffix[.]sentencecase[]] }}}` {{{ 
> [] [] +[join[ and ]addsuffix[.]sentencecase[]] }}}
> #`{{{ [] [] +[join[ and ]addsuffix[.]sentencecase[]] }}}` {{{ 
> [] [] +[join[ and ]addsuffix[.]sentencecase[]] }}}
>
>
> 
>
>
>
> Regards
> Tones 
>
> On Monday, 16 August 2021 at 19:54:36 UTC+10 Misterel85 wrote:
>
>> Tones,
>>
>> Oh, now I better see what you mean by 'separating the data from its 
>> presentation'.
>> It kind of reminds me of my attempts at concatenating genealogical data 
>> in LaTeX with AppleScript years ago. What you advise is something I more or 
>> less tried to do at the time.
>>
>> I fully agree with what you wrote, but your precious advice stumble over 
>> a huge impediment: my poor skills at programming in general, and Wikitext 
>> in particular! I have absolutely no programming or STEM background, 
>> unfortunately, and I am only a tinkerer.
>>
>> When I manage to copy-paste and adapt existing code snippets to meet my 
>> needs, I am very happy.
>>

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

On Wednesday, August 18, 2021 at 10:38:29 PM UTC+2 Soren Bjornstad wrote:

> I'll preface this by saying this probably belongs in a GitHub issue, and 
> I'll be happy to create one over there if we want one. But wanted to get 
> people's thoughts first, and ASAP because now is our last chance to do this 
> without breaking backwards compatibility (once 5.2.0 is released, it would 
> be pretty hard to change).
>

I think this won't happen because of backwards compatibility with 5.1.x. 
There have been some discussions on github already. The conclusion was, we 
keep the status quo and live with it. 

There has been a discussion recently, where a user needed to be able to add 
whitespace as needed. And the description of the usecase made sense. So 
there are usecases. ... See: 
https://groups.google.com/g/tiddlywiki/c/Cjy074MsfzM

-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/c51c30cf-fa53-42d8-a9d9-e44641fd5aa6n%40googlegroups.com.

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

Just realized some people might not be familiar with the term "leading and 
trailing whitespace"...I mean whitespace at the very beginning or end of 
the name. In the current prerelease, these are valid and distinct field 
names (with the quotes removed):

"my field"
" my field"
"my field "
"   my field  "

On Wednesday, August 18, 2021 at 3:38:29 PM UTC-5 Soren Bjornstad wrote:

> I'll preface this by saying this probably belongs in a GitHub issue, and 
> I'll be happy to create one over there if we want one. But wanted to get 
> people's thoughts first, and ASAP because now is our last chance to do this 
> without breaking backwards compatibility (once 5.2.0 is released, it would 
> be pretty hard to change).
>
> Would it make sense to *prohibit leading and trailing whitespace in field 
> names*, even though we now allow whitespace elsewhere? In the prerelease, 
> it's not possible to add such fields within the GUI, but you can import 
> tiddlers that contain such fields, or create them with an action or 
> $edit-text widget. Fields with leading or trailing whitespace are almost 
> impossible to distinguish within the GUI, since there is already whitespace 
> before and after the name when it's displayed.
>
> In addition, if we continue to prohibit leading and trailing whitespace, I 
> think we would be able to allow whitespace in between filter steps, which 
> is a common annoyance for new users (but maybe I'm missing something there).
>
> I can't think of any situation in which someone would *want* leading or 
> trailing whitespace in a field name, except maybe to integrate with another 
> system which allowed it for some reason – as evidenced by the fact that the 
> GUI doesn't even let you create such a field. At any rate, it seems much 
> more confusing than helpful. Unix filenames have suffered enormously 
>  from being 
> overly permissive in what characters they allow, including leading and 
> trailing whitespace; my instinct tells me this is likely to be a continuing 
> irritation.
>
> On the minus side, someone would of course have to implement checks to 
> prevent these fields from being added.
>

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

[tw5] Should we prohibit leading and trailing whitespace in field names in 5.2.0?

I'll preface this by saying this probably belongs in a GitHub issue, and
I'll be happy to create one over there if we want one. But wanted to get
people's thoughts first, and ASAP because now is our last chance to do this
without breaking backwards compatibility (once 5.2.0 is released, it would
be pretty hard to change).

Would it make sense to *prohibit leading and trailing whitespace in field
names*, even though we now allow whitespace elsewhere? In the prerelease,
it's not possible to add such fields within the GUI, but you can import
tiddlers that contain such fields, or create them with an action or
$edit-text widget. Fields with leading or trailing whitespace are almost
impossible to distinguish within the GUI, since there is already whitespace
before and after the name when it's displayed.

In addition, if we continue to prohibit leading and trailing whitespace, I
think we would be able to allow whitespace in between filter steps, which
is a common annoyance for new users (but maybe I'm missing something there).

I can't think of any situation in which someone would *want* leading or
trailing whitespace in a field name, except maybe to integrate with another
system which allowed it for some reason – as evidenced by the fact that the
GUI doesn't even let you create such a field. At any rate, it seems much
more confusing than helpful. Unix filenames have suffered enormously
from being
overly permissive in what characters they allow, including leading and
trailing whitespace; my instinct tells me this is likely to be a continuing
irritation.

On the minus side, someone would of course have to implement checks to
prevent these fields from being added.

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

[tw5] Re: Import tiddlers w/ json including custom fields

2021-08-18 Thread springer

JKM, 

After putting quotes around your numbers (and fixing where a So-called 
"smart" quote had crept in during my editing, sorry about my earlier post, 
now deleted), both records import fine for me.

I have found that raw numbers for field content (as in your kbarating 
field) will not work; only data enclosed in quote marks seems to work.

Note the field data (beyond title and text) doesn't show in the import 
preview tiddler. But the data should be in there, as you can confirm by 
entering edit mode for the tiddlers once imported.

-Springer

On Wednesday, August 18, 2021 at 2:22:26 PM UTC-4 jkm...@gmail.com wrote:

> New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23
>
> I'm able to import tiddlers from json with the title and text fields.  But 
> when I try to do it with a custom field the import tiddler shows no items 
> to import.  All my custom fields begin with *kba* and some additional 
> alphanumeric characters.  The json is valid according to jsonchecker.com.  
> Is this permitted?  Do I need to enable a feature or preconfigure a system 
> component?  I've done a few searches in the group but didn't see anything 
> that applied.  All help is appreciated.
>
> Imports:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password"
>   },
>   {
> "title": "20508",
> "text": "Best Practices"
>   }
> ]
>
> Doesn't import:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password",
> "kbalink": " https://www.someplace.net/ 19464",
> "kbarating": 3,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "How To"
>   },
>   {
> "title": "20508",
> "text": "Best Practices",
> "kbalink": "https://www.someplace.net/20508;,
> "kbarating": 5,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "Info"
>   }
> ]
>

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

[tw5] seeing what the transfering of tiddlywiki to a more self-coded platform can look like

2021-08-18 Thread Andrew Paul

I'm looking to see what the transfering of tiddlywiki to a more self-coded 
platform, such as jekyll, gatsby, or others, can look like. My concern is 
the transition being difficult, long, etc. Any resources?

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

[tw5] Re: Import tiddlers w/ json including custom fields

2021-08-18 Thread springer

JKM, This is not much of an answer, except two comments:
(1) I regularly import JSON strings with fields, needing no further 
configuration. (The import tiddler won't show the additional fields, but 
they'll be part of the tiddler after import, as you can see once you open 
in edit mode.)
(2) I have found that raw numbers for field content (as in your kbarating 
field) will not work; only data enclosed in quote marks seems to work.

I don't have time for much more testing, except to confirm that I can 
import your json data  (using copy-paste), and yet I also see a couple 
unexpected character errors, and I'm not sure why.

On Wednesday, August 18, 2021 at 2:22:26 PM UTC-4 jkm...@gmail.com wrote:

> New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23
>
> I'm able to import tiddlers from json with the title and text fields.  But 
> when I try to do it with a custom field the import tiddler shows no items 
> to import.  All my custom fields begin with *kba* and some additional 
> alphanumeric characters.  The json is valid according to jsonchecker.com.  
> Is this permitted?  Do I need to enable a feature or preconfigure a system 
> component?  I've done a few searches in the group but didn't see anything 
> that applied.  All help is appreciated.
>
> Imports:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password"
>   },
>   {
> "title": "20508",
> "text": "Best Practices"
>   }
> ]
>
> Doesn't import:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password",
> "kbalink": " https://www.someplace.net/ 19464",
> "kbarating": 3,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "How To"
>   },
>   {
> "title": "20508",
> "text": "Best Practices",
> "kbalink": "https://www.someplace.net/20508;,
> "kbarating": 5,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "Info"
>   }
> ]
>

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

[tw5] Re: Import tiddlers w/ json including custom fields

Your second example imports as expected for me. Is it possible tiddlers 
with the titles in your JSON already exist in the wiki? I believe there is 
a bug in 5.1.23 where it doesn't explain that to you in the import dialog 
and just silently skips them.

On Wednesday, August 18, 2021 at 1:22:26 PM UTC-5 jkm...@gmail.com wrote:

> New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23
>
> I'm able to import tiddlers from json with the title and text fields.  But 
> when I try to do it with a custom field the import tiddler shows no items 
> to import.  All my custom fields begin with *kba* and some additional 
> alphanumeric characters.  The json is valid according to jsonchecker.com.  
> Is this permitted?  Do I need to enable a feature or preconfigure a system 
> component?  I've done a few searches in the group but didn't see anything 
> that applied.  All help is appreciated.
>
> Imports:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password"
>   },
>   {
> "title": "20508",
> "text": "Best Practices"
>   }
> ]
>
> Doesn't import:
> [
>   {
> "title": "19464",
> "text": "How to change the default root password",
> "kbalink": " https://www.someplace.net/ 19464",
> "kbarating": 3,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "How To"
>   },
>   {
> "title": "20508",
> "text": "Best Practices",
> "kbalink": "https://www.someplace.net/20508;,
> "kbarating": 5,
> "kbasev": 0,
> "kbasource": "LKBA",
> "kbastale": 0,
> "kbatweak": "",
> "kbatype": "Info"
>   }
> ]
>

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

[tw5] Import tiddlers w/ json including custom fields

2021-08-18 Thread John Mayes

New member here.  Windows, TiddlyDesktop v0.0.14, TW 5.1.23

I'm able to import tiddlers from json with the title and text fields.  But 
when I try to do it with a custom field the import tiddler shows no items 
to import.  All my custom fields begin with *kba* and some additional 
alphanumeric characters.  The json is valid according to jsonchecker.com.  
Is this permitted?  Do I need to enable a feature or preconfigure a system 
component?  I've done a few searches in the group but didn't see anything 
that applied.  All help is appreciated.

Imports:
[
  {
"title": "19464",
"text": "How to change the default root password"
  },
  {
"title": "20508",
"text": "Best Practices"
  }
]

Doesn't import:
[
  {
"title": "19464",
"text": "How to change the default root password",
"kbalink": " https://www.someplace.net/ 19464",
"kbarating": 3,
"kbasev": 0,
"kbasource": "LKBA",
"kbastale": 0,
"kbatweak": "",
"kbatype": "How To"
  },
  {
"title": "20508",
"text": "Best Practices",
"kbalink": "https://www.someplace.net/20508;,
"kbarating": 5,
"kbasev": 0,
"kbasource": "LKBA",
"kbastale": 0,
"kbatweak": "",
"kbatype": "Info"
  }
]

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

[tw5] Re: I Think I Hacked TiddlyWiki

2021-08-18 Thread 'Mark S.' via TiddlyWiki

Really, it gets back to trust and reputation.

A TW coder could write a tiddler that contains no javascript tiddlers, but 
that, when run, creates a javascript  tiddler that will later get run. So 
you would never see javascript code during import. The core TW is already 
pretty huge. Adding patch after patch for each imagined scenario eventually 
renders TW less and less useful.

Also, it hasn't been demonstrated what harm could be done even if your 
standalone code was infiltrated. Could keystrokes be sent back to a server? 
Could file blocks be written anywhere other than the download directory? Of 
course on node or especially on any multi-user platform things become more 
hazardous.  In theory any server-based solution (e.g. node) could write to 
your file system and possibly invoke code. In practice, I found it very 
difficult to set up even when I wanted something like that.

On Wednesday, August 18, 2021 at 9:22:27 AM UTC-7 R² wrote:

> Excellent points John. Most users will indeed not review the full text of 
> every single tiddler they import. I'm now thinking that pointing out which 
> ones should indeed be reviewed more explicitly would be both easy and 
> worthwhile.
>
> At the tm-import-tiddlers widget level, any JS that's being imported could 
> be flagged, with a simple highlight inviting the user to review the code 
> before confirming the import when standard declared JS is detected, and a 
> more insistent alert when the code is hidden or obfuscated (as in Finn's 
> Base64 example). A simple exhaustive filter search should be able to cover 
> all or most cases, including content-type=application/javascript,

[tw5] Re: I Think I Hacked TiddlyWiki

2021-08-18 Thread 'Mark S.' via TiddlyWiki

I never got the alert. I'm curious why some people are reporting that it 
worked. Also, "alert" is very public and generally pretty harmless. 
Possibly it could be used as part of a phishing scheme.  It's not clear to 
me that you could create code that could modify anything outside the iframe 
sandbox. The suggestion was made that it could download something. Is there 
a demo for that?

On Wednesday, August 18, 2021 at 6:52:32 AM UTC-7 joh@gmail.com wrote:

> Well, what I see is this:
>
> If you use TW, you use JavaScript. And if you use JavaScript code from 
> unknown / unsafe sources, you will run the risk of the code doing things 
> that it shouldn't be doing. That should actually be clear to everyone. But 
> that's not a problem for TW, but in principle for every website that takes 
> full advantage of the possibilities of HTML5. And at last, it's the problem 
> of all data: You have to trust in it.
>
> A particular security problem of TW is, of course, that TW has all the 
> tools to integrate new (dangerous) code in the simplest possible way, 
> without the user always being aware of what he is doing. The special thing 
> about it is not only that it is so easy to do. It is also particularly 
> difficult to understand and keep track of, because the file is constantly 
> being changed and saved.
>
> Of course, you can take the trouble to review the code you are adopting 
> and also ensure that no one else can insert their own code. But honestly, 
> who does it? We usually trust what we find - at least on the sites we know. 
> And what we are inserting is not always obvious. The example code above, 
> for example. In plain language it reads:
>
> 
> var keylog = [];
> document.addEventListener('keyup', function(e){
> keylog.push(e.which);
> alert(keylog);
> });
> 
>
> Which of you deciphered it before trying it out?
> TW Tones schrieb am Mittwoch, 18. August 2021 um 08:12:13 UTC+2:
>
>> Mark et al
>>
>> You said *TW wasn't built from the ground-up for mult-user, and it's 
>> definitely not how most people are using it. I'm sure products built as 
>> server-side entities (e.g. WikiMedia) have all sorts of protection against 
>> injected code. *
>>
>> I agree, yet we have Bob which makes this plausible at least where people 
>> who access the wiki are trusted such as in a team. Perhaps not secure on 
>> the internet where anyone can get to it. 
>>
>>- I think this may be a self fulfilling prophesy, we don't have 
>>secure methods to share online or run in a multi-user mode, so no one 
>> does.
>>- Because we don't have multi-user solutions on the internet people 
>>come to expect all the control they want on their own local wikis, I 
>> don't 
>>want the security tail wagging the dog, if I want to iframe sites I use, 
>> or 
>>use it to drag and drop patches between wikis, I would not like this 
>> being 
>>locked down.
>>- Despite me calling for this mulit-user functionality, see Check in 
>>and out critical to the use of tiddlywiki #5919 
>> with the 
>>simplest form serial editing using a check out and in facility I can't 
>> seem 
>>to get any traction on this.
>>
>> Given the discussion in this thread, perhaps we need a way to harden 
>> tiddlywiki for the internet, but I hope we don't harden it for the sole or 
>> LAN users or teams. It seems we may need to "bifurcate" to the risky and 
>> less risky environments, another possibility is being able to run a 
>> vulnerability check on a wiki.
>>
>> The best security will give us our cake and we can eat it too, the wrong 
>> security will mean we can't eat the cake, or look at it in the security of 
>> our own room.
>>
>> In closing of great importance are the many possible ways tiddlywiki can 
>> be made use of, but we need to maintain flexibility even when attempting to 
>> secure it the the "great unwashed internet", because it often has little or 
>> nothing to do with the internet. 
>>
>> Regards
>> Tones
>>
>>
>>
>> On Wednesday, 18 August 2021 at 13:33:11 UTC+10 Mark S. wrote:
>>
>>> TW wasn't built from the ground-up for mult-user, and it's definitely 
>>> not how most people are using it. I'm sure products built as server-side 
>>> entities (e.g. WikiMedia) have all sorts of protection against injected 
>>> code. 
>>>
>>> Anyone who can write and  save a tiddler can make a javascript tiddler, 
>>> or a widget, or overwrite a javascript filte operator, or maybe header 
>>> scripts, or maybe in-frame code. I guess you would have to think of all the 
>>> ways that code could be injected and then neutralize everything that 
>>> matched. But you'd have to do it before the tiddlers got written to the 
>>> common pool, and you'd have to either block legitimate uses of the iframe, 
>>> or figure out some way to detect that the frame doesn't contain js source 
>>> code.
>>>
>>>
>>>
>>> On Tuesday, August 17, 2021 at 7:06:05 PM UTC-7

[tw5] Re: I Think I Hacked TiddlyWiki

2021-08-18 Thread R²

Excellent points John. Most users will indeed not review the full text of 
every single tiddler they import. I'm now thinking that pointing out which 
ones should indeed be reviewed more explicitly would be both easy and 
worthwhile.

At the tm-import-tiddlers widget level, any JS that's being imported could 
be flagged, with a simple highlight inviting the user to review the code 
before confirming the import when standard declared JS is detected, and a 
more insistent alert when the code is hidden or obfuscated (as in Finn's 
Base64 example). A simple exhaustive filter search should be able to cover 
all or most cases, including content-type=application/javascript,

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

Ah! I knew it must be something easy - thanks for that! Lots to read up on 
:)

On Wednesday, August 18, 2021 at 11:52:06 AM UTC-4 PMario wrote:

> HI,
> The TiddlyWiki --listen command has a lot of additional parameters. See: 
> https://tiddlywiki.com/#ListenCommand
>
> tiddlywiki "path/to/wiki" --listen host=10.1.x.x   should do the trick. 
>
> -m
>
> On Wednesday, August 18, 2021 at 5:34:19 PM UTC+2 Stobot wrote:
>
>> Thanks for the continued conversation @pmario,
>>
>> So I'm aware of my IP and am fine with the ip:port need (as that's how 
>> it's done in BOB also), but the piece I'm stuck on is how to get node to 
>> serve it on my local IP address (though this is really not my area of 
>> expertise, so could be way over-complicating it). For example, to start 
>> each day I run this from the command line:
>>
>> tiddlywiki "C:\Users\...\wikiname" --listen
>>
>> and then it says "Serving on http://127.0.0.1:8080; in the console. How 
>> do I get it / change the command I'm running to put it at a 10.1.X.X 
>> address so that others on my LAN can get to it. It's not like they can 
>> enter my 127.0.0.1:8080 address from their computer and get to my wiki - 
>> right?
>>
>> note that I don't have admin access at this time (for IIS etc), can 
>> sometimes get it temporarily, but let's just call it a "difficult" path, 
>> though maybe not impossible. I like the domain name vs. IP though :)
>> On Wednesday, August 18, 2021 at 10:47:39 AM UTC-4 PMario wrote:
>>
>>> On Wednesday, August 18, 2021 at 4:45:31 PM UTC+2 PMario wrote:
>>>
>>> If you do have admin rights on your PC you can also define a "local 
 domain name" in the windows hosts file, if you have a fixed IP address. 
 eg: http://.lan:8080  .. 

>>>
>>> Oh ... I did forget. If others also need to know the local domain name, 
>>> they will also have to adjust their hosts file. Which needs admin rights.
>>>
>>> -m
>>>
>>

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

HI,
The TiddlyWiki --listen command has a lot of additional parameters. See: 
https://tiddlywiki.com/#ListenCommand

tiddlywiki "path/to/wiki" --listen host=10.1.x.x   should do the trick. 

-m

On Wednesday, August 18, 2021 at 5:34:19 PM UTC+2 Stobot wrote:

> Thanks for the continued conversation @pmario,
>
> So I'm aware of my IP and am fine with the ip:port need (as that's how 
> it's done in BOB also), but the piece I'm stuck on is how to get node to 
> serve it on my local IP address (though this is really not my area of 
> expertise, so could be way over-complicating it). For example, to start 
> each day I run this from the command line:
>
> tiddlywiki "C:\Users\...\wikiname" --listen
>
> and then it says "Serving on http://127.0.0.1:8080; in the console. How 
> do I get it / change the command I'm running to put it at a 10.1.X.X 
> address so that others on my LAN can get to it. It's not like they can 
> enter my 127.0.0.1:8080 address from their computer and get to my wiki - 
> right?
>
> note that I don't have admin access at this time (for IIS etc), can 
> sometimes get it temporarily, but let's just call it a "difficult" path, 
> though maybe not impossible. I like the domain name vs. IP though :)
> On Wednesday, August 18, 2021 at 10:47:39 AM UTC-4 PMario wrote:
>
>> On Wednesday, August 18, 2021 at 4:45:31 PM UTC+2 PMario wrote:
>>
>> If you do have admin rights on your PC you can also define a "local 
>>> domain name" in the windows hosts file, if you have a fixed IP address. 
>>> eg: http://.lan:8080  .. 
>>>
>>
>> Oh ... I did forget. If others also need to know the local domain name, 
>> they will also have to adjust their hosts file. Which needs admin rights.
>>
>> -m
>>
>

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

Thanks for the continued conversation @pmario,

So I'm aware of my IP and am fine with the ip:port need (as that's how it's 
done in BOB also), but the piece I'm stuck on is how to get node to serve 
it on my local IP address (though this is really not my area of expertise, 
so could be way over-complicating it). For example, to start each day I run 
this from the command line:

tiddlywiki "C:\Users\...\wikiname" --listen

and then it says "Serving on http://127.0.0.1:8080; in the console. How do 
I get it / change the command I'm running to put it at a 10.1.X.X address 
so that others on my LAN can get to it. It's not like they can enter my 
127.0.0.1:8080 address from their computer and get to my wiki - right?

note that I don't have admin access at this time (for IIS etc), can 
sometimes get it temporarily, but let's just call it a "difficult" path, 
though maybe not impossible. I like the domain name vs. IP though :)
On Wednesday, August 18, 2021 at 10:47:39 AM UTC-4 PMario wrote:

> On Wednesday, August 18, 2021 at 4:45:31 PM UTC+2 PMario wrote:
>
> If you do have admin rights on your PC you can also define a "local domain 
>> name" in the windows hosts file, if you have a fixed IP address. 
>> eg: http://.lan:8080  .. 
>>
>
> Oh ... I did forget. If others also need to know the local domain name, 
> they will also have to adjust their hosts file. Which needs admin rights.
>
> -m
>

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

[tw5] Re: Refer to the same tiddler with multiple names

Hi Sandip, 
I did create a plugin named: uni-link. .. It will allow you to use an 
aliases field in your tiddler. This field can then be used to link to other 
tiddlers. 

Have a closer look at the original intro thread and the video on the plugin 
page. https://groups.google.com/g/tiddlywiki/c/35_6ltCXEvs/m/Ryl90gI_AwAJ
How you can add the library link to your wiki, so you can use the core 
Plugin installation mechanism is shown at: 
https://wikilabs.github.io/#GettingStarted

have fun!
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/94929439-90c4-4554-a13c-476ef36930e5n%40googlegroups.com.

Re: [tw5] Seeking common misunderstandings

2021-08-18 Thread Jeremy Ruston

Hi Soren,

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

Excellent idea, I think that will be very helpful.

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

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

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

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

Best wishes

Jeremy

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

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

On Wednesday, August 18, 2021 at 4:45:31 PM UTC+2 PMario wrote:

If you do have admin rights on your PC you can also define a "local domain 
> name" in the windows hosts file, if you have a fixed IP address. 
> eg: http://.lan:8080  .. 
>

Oh ... I did forget. If others also need to know the local domain name, 
they will also have to adjust their hosts file. Which needs admin rights.

-m

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

On Wednesday, August 18, 2021 at 4:01:11 PM UTC+2 Stobot wrote:

I start node each morning and it gives me the standard Serving on 
> http://127.0.0.1:8080 message, so I'd have to figure out how to get that 
> to a 10.1.X.X situation for LAN usage to multi-serve right? In BOB there's 
> some buttons to press, so the actual method of how to do this in base-node 
> is something I'm not aware of.  
>

On windows there are even better options. You can use IIS Internet 
Information Service to run your node server as a service on your computer. 
So as soon as it is switched on the server will be active. 

BUT ... In an enterprise environment you will probably _not_ be allowed to 
start IIS as a service on your PC ... 

If you do have admin rights on your PC you can also define a "local domain 
name" in the windows hosts file, if you have a fixed IP address. 
eg: http://.lan:8080  .. 
The port will need to be there :/ ... BUT if you would have access to IIS 
you could start it at port 80. So the address would be http://.lan 
... Which imo is much cooler than http:/10.1.0.10:8080  

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/183ef823-3f4a-45be-8980-78d04ccd2ef6n%40googlegroups.com.

[tw5] Re: Seeking common misunderstandings

Maybe this is derailing the thread, but I'm disinclined to post on 
Discourse when I'm looking for a broad audience (like in this post) since 
only a few people are over there so far. Is there anything we can do to to 
ease that? Is it possible to crosspost new threads from Discourse to GG for 
instance?

On Wednesday, August 18, 2021 at 9:35:14 AM UTC-5 saq.i...@gmail.com wrote:

> Yes that is exactly what I mean. The GG threads in Discourse are read only.
>
> It would help if people started new threads on Discourse, hopefully we 
> will see more of that in the next days.
> The plan is to migrate to Discourse and make this group read only after a 
> short period where we test out Discourse. So anyone that doesn't try using 
> Discourse in anger now will likely miss their chance to have a say in that 
> final decision.
> On Wednesday, August 18, 2021 at 4:30:33 PM UTC+2 Stobot wrote:
>
>> @saqimtiaz - I might be doing it wrong, but I haven't found a way to 
>> reply in Discourse to a GG thread, I assume you mean you'll start a new 
>> 'topic' in Discourse, or am I missing something? I only see the reply 
>> button in Discourse for Discourse-native conversations.
>>
>> This is making the "conversion" pretty painful. I'm monitoring Discourse, 
>> but for all replies I'm going into GG and finding the thread to reply to 
>> (like now).
>>
>> On Wednesday, August 18, 2021 at 10:16:04 AM UTC-4 saq.i...@gmail.com 
>> wrote:
>>
>>> Hi Soren,
>>>
>>> I posted a small list an hour ago but due to the vagaries of GG it 
>>> doesn't seem to have been posted. Re-writing is never fun but will do so 
>>> and post as a reply on Discourse a little later.
>>> Regards,
>>> Saq
>>>
>>> On Wednesday, August 18, 2021 at 3:30:43 PM UTC+2 Soren Bjornstad wrote:
>>>
 I'm working on adding a chapter (or back-matter section, not sure yet) 
 called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I 
 have two sections:

- Macros are not function calls
- Constant strings cannot be combined with transclusions

 Are there other common misunderstandings – in terms of incorrect mental 
 models of how TiddlyWiki operates, or things one might expect to work that 
 don't – that come up here or elsewhere that you'd like to see documented 
 in 
 such a section?

 Feedback on the drafts of the two existing sections would be welcome as 
 well:


 https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
   
 
>>>
>>>

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

[tw5] Re: Seeking common misunderstandings

2021-08-18 Thread Saq Imtiaz

Yes that is exactly what I mean. The GG threads in Discourse are read only.

It would help if people started new threads on Discourse, hopefully we will 
see more of that in the next days.
The plan is to migrate to Discourse and make this group read only after a 
short period where we test out Discourse. So anyone that doesn't try using 
Discourse in anger now will likely miss their chance to have a say in that 
final decision.
On Wednesday, August 18, 2021 at 4:30:33 PM UTC+2 Stobot wrote:

> @saqimtiaz - I might be doing it wrong, but I haven't found a way to reply 
> in Discourse to a GG thread, I assume you mean you'll start a new 'topic' 
> in Discourse, or am I missing something? I only see the reply button in 
> Discourse for Discourse-native conversations.
>
> This is making the "conversion" pretty painful. I'm monitoring Discourse, 
> but for all replies I'm going into GG and finding the thread to reply to 
> (like now).
>
> On Wednesday, August 18, 2021 at 10:16:04 AM UTC-4 saq.i...@gmail.com 
> wrote:
>
>> Hi Soren,
>>
>> I posted a small list an hour ago but due to the vagaries of GG it 
>> doesn't seem to have been posted. Re-writing is never fun but will do so 
>> and post as a reply on Discourse a little later.
>> Regards,
>> Saq
>>
>> On Wednesday, August 18, 2021 at 3:30:43 PM UTC+2 Soren Bjornstad wrote:
>>
>>> I'm working on adding a chapter (or back-matter section, not sure yet) 
>>> called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I 
>>> have two sections:
>>>
>>>- Macros are not function calls
>>>- Constant strings cannot be combined with transclusions
>>>
>>> Are there other common misunderstandings – in terms of incorrect mental 
>>> models of how TiddlyWiki operates, or things one might expect to work that 
>>> don't – that come up here or elsewhere that you'd like to see documented in 
>>> such a section?
>>>
>>> Feedback on the drafts of the two existing sections would be welcome as 
>>> well:
>>>
>>>
>>> https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
>>>   
>>> 
>>
>>

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

In powershell you can try 

ipconfig
or
Get-NetIPAddress | Format-Table

Your PC address will be the one with 10.1.x.x  in it. Mainly the one which 
comes form a Dhcp server

-m

On Wednesday, August 18, 2021 at 4:22:16 PM UTC+2 Stobot wrote:

> Windows 10
>
> On Wednesday, August 18, 2021 at 10:16:39 AM UTC-4 PMario wrote:
>
>> Hi,
>> Which OS do you have? 
>> -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/32d1dd4b-70d0-47b4-b59d-bdeea0c3bd68n%40googlegroups.com.

[tw5] Re: Seeking common misunderstandings

@saqimtiaz - I might be doing it wrong, but I haven't found a way to reply 
in Discourse to a GG thread, I assume you mean you'll start a new 'topic' 
in Discourse, or am I missing something? I only see the reply button in 
Discourse for Discourse-native conversations.

This is making the "conversion" pretty painful. I'm monitoring Discourse, 
but for all replies I'm going into GG and finding the thread to reply to 
(like now).

On Wednesday, August 18, 2021 at 10:16:04 AM UTC-4 saq.i...@gmail.com wrote:

> Hi Soren,
>
> I posted a small list an hour ago but due to the vagaries of GG it doesn't 
> seem to have been posted. Re-writing is never fun but will do so and post 
> as a reply on Discourse a little later.
> Regards,
> Saq
>
> On Wednesday, August 18, 2021 at 3:30:43 PM UTC+2 Soren Bjornstad wrote:
>
>> I'm working on adding a chapter (or back-matter section, not sure yet) 
>> called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I have 
>> two sections:
>>
>>- Macros are not function calls
>>- Constant strings cannot be combined with transclusions
>>
>> Are there other common misunderstandings – in terms of incorrect mental 
>> models of how TiddlyWiki operates, or things one might expect to work that 
>> don't – that come up here or elsewhere that you'd like to see documented in 
>> such a section?
>>
>> Feedback on the drafts of the two existing sections would be welcome as 
>> well:
>>
>>
>> https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
>>   
>> 
>
>

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

Windows 10

On Wednesday, August 18, 2021 at 10:16:39 AM UTC-4 PMario wrote:

> Hi,
> Which OS do you have? 
> -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/079fbc33-cbfd-4406-a1e0-381de944f5bdn%40googlegroups.com.

[tw5] Re: how to set a global variable with a tiddler field value

2021-08-18 Thread vpl

Hi,

Much much simplier .. indeed
I've turned around this simple solution for some time without finding it ..

Thanks a lot for your very quick help 

Regards

Le mercredi 18 août 2021 à 12:53:31 UTC+2, Eric Shulman a écrit :

> On Wednesday, August 18, 2021 at 3:25:22 AM UTC-7 vpl wrote:
>
>> In fact my problem was linked to a button action and thanks to  
>> https://tiddlytools.com/timer.html code sample I was able to find a work 
>> an option 
>> \define tasks_delete()
>> <$vars  projectId={{{ [get[projectId]] }}}>
>> <$reveal default="show" type="match" text="show">
>> <$button class="tc-button tt-button" tooltip="delete this alarm"> 
>> {{$:/core/images/delete-button}}
>> <$action-listops $tiddler=<> $field="tasks" 
>> $subfilter="-[[$(this_alarm)$]]" />
>>   
>> 
>> \end
>> The $reveal seems to be mandatory to get access to my projectId variable 
>> withing the button action-listops
>>
>
> Here's a trimmed down version that eliminates the unneeded excess syntax:
> \define tasks_delete()
> <$button class="tc-button" tooltip="delete this task"> 
> {{$:/core/images/delete-button}}
><$action-listops $tiddler={{{ [get[projectId]] }}} 
> $field="tasks" $subfilter="-[[$(this_alarm)$]]" />
> 
> \end
>
> Notes:
> * The $vars is not needed.  Instead, use $tiddler={{{ 
> [get[projectId]] }}} directly in the $action-listops 
> widget
> * Eliminate the $reveal and /$reveal.  Quite obviously, "show" will always 
> match "show", so this does nothing.
> * Remove "tt-button" from the $button class="...";  this is a TiddlyTools 
> custom classname that is almost certainly not defined in your TiddlyWiki.
> * Fix the tooltip text to say "task" instead of "alarm"
> * $(this_alarm)$ references a variable defined outside the tasks_delete() 
> macro and should probably be changed to whatever variable holds the name of 
> the task you are deleting.
>
> -e
>
>

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

Hi,
Which OS do you have? 
-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/63d75e31-4d26-433f-8fdb-b5abfee7de26n%40googlegroups.com.

[tw5] Re: Seeking common misunderstandings

2021-08-18 Thread Saq Imtiaz

Hi Soren,

I posted a small list an hour ago but due to the vagaries of GG it doesn't 
seem to have been posted. Re-writing is never fun but will do so and post 
as a reply on Discourse a little later.
Regards,
Saq

On Wednesday, August 18, 2021 at 3:30:43 PM UTC+2 Soren Bjornstad wrote:

> I'm working on adding a chapter (or back-matter section, not sure yet) 
> called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I have 
> two sections:
>
>- Macros are not function calls
>- Constant strings cannot be combined with transclusions
>
> Are there other common misunderstandings – in terms of incorrect mental 
> models of how TiddlyWiki operates, or things one might expect to work that 
> don't – that come up here or elsewhere that you'd like to see documented in 
> such a section?
>
> Feedback on the drafts of the two existing sections would be welcome as 
> well:
>
>
> https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
>   
> 

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

Interesting - I greatly appreciate the input/detail @pmario! 

In many (though not all) of my intended use cases, restricting others to 
*only add* operations (no changes) via UI trickery would be doable. My 
use-cases usually involve *me* setting something up a list of business 
decisions for review, and have others comment / approve / rate etc, which 
I'd usually store in the background as system tiddlers incorporating user 
names. In such a worflow the "conflicts" are not a real issue, and I can 
even handle the timing lag of it being propogated to others in most cases, 
though reducing that would be ideal.

I start node each morning and it gives me the standard Serving on 
http://127.0.0.1:8080 message, so I'd have to figure out how to get that to 
a 10.1.X.X situation for LAN usage to multi-serve right? In BOB there's 
some buttons to press, so the actual method of how to do this in base-node 
is something I'm not aware of.  

On Wednesday, August 18, 2021 at 8:12:07 AM UTC-4 PMario wrote:

> Followup,
>
> On Wednesday, August 18, 2021 at 2:03:53 PM UTC+2 PMario wrote:
> ... 
>
>> The function is called "syncFromServer". So if you open 1 wiki in 2 tabs 
>> of a browser you will informed, if someone opened a tiddler. A _red_ "draft 
>> of ... by " button will be shown in the bottom of the wiki window. 
>> The name will be only there if the username is set in the ConfigTiddler!
>>
>
> The server sent event plugin triggers the exact same mechanism. So it's 
> possible to create instant feedback without the need to modify core 
> functions. 
> The disadvantage here is, that there is quite some overhead over the wire. 
> The message flow is like this: 
>
>  1) Server informs the client about new data
>  2) Client reads all the tiddler meta-data without the text field
>  3) Client compares all titles to see if something changed.
>  4) If something changed the client reads ALL tiddlers including text 
> content
>  5) Client saves new data
>  6) TW UI shows new data.
>
> This workflow is OK for the current client implementation, since it runs 
> on a client-side timer. But the with SSE it could be like this: 
>
>  - 1) Server sends the changed data to the client
>  - 2) Client saves them
>   3) TW UI shows new data
>
> As you can see, there is a lot of room for improvements. Especially the 
> "Conflict Free Replicated Datatype" that Joshua mentioned would be an 
> interesting option here. 
>
> -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/b4699eb3-2ccc-4021-b266-157b20b40bd5n%40googlegroups.com.

[tw5] Re: I Think I Hacked TiddlyWiki

2021-08-18 Thread J. C. S.

Well, what I see is this:

If you use TW, you use JavaScript. And if you use JavaScript code from 
unknown / unsafe sources, you will run the risk of the code doing things 
that it shouldn't be doing. That should actually be clear to everyone. But 
that's not a problem for TW, but in principle for every website that takes 
full advantage of the possibilities of HTML5. And at last, it's the problem 
of all data: You have to trust in it.

A particular security problem of TW is, of course, that TW has all the 
tools to integrate new (dangerous) code in the simplest possible way, 
without the user always being aware of what he is doing. The special thing 
about it is not only that it is so easy to do. It is also particularly 
difficult to understand and keep track of, because the file is constantly 
being changed and saved.

Of course, you can take the trouble to review the code you are adopting and 
also ensure that no one else can insert their own code. But honestly, who 
does it? We usually trust what we find - at least on the sites we know. And 
what we are inserting is not always obvious. The example code above, for 
example. In plain language it reads:


var keylog = [];
document.addEventListener('keyup', function(e){
keylog.push(e.which);
alert(keylog);
});


Which of you deciphered it before trying it out?
TW Tones schrieb am Mittwoch, 18. August 2021 um 08:12:13 UTC+2:

> Mark et al
>
> You said *TW wasn't built from the ground-up for mult-user, and it's 
> definitely not how most people are using it. I'm sure products built as 
> server-side entities (e.g. WikiMedia) have all sorts of protection against 
> injected code. *
>
> I agree, yet we have Bob which makes this plausible at least where people 
> who access the wiki are trusted such as in a team. Perhaps not secure on 
> the internet where anyone can get to it. 
>
>- I think this may be a self fulfilling prophesy, we don't have secure 
>methods to share online or run in a multi-user mode, so no one does.
>- Because we don't have multi-user solutions on the internet people 
>come to expect all the control they want on their own local wikis, I don't 
>want the security tail wagging the dog, if I want to iframe sites I use, 
> or 
>use it to drag and drop patches between wikis, I would not like this being 
>locked down.
>- Despite me calling for this mulit-user functionality, see Check in 
>and out critical to the use of tiddlywiki #5919 
> with the 
>simplest form serial editing using a check out and in facility I can't 
> seem 
>to get any traction on this.
>
> Given the discussion in this thread, perhaps we need a way to harden 
> tiddlywiki for the internet, but I hope we don't harden it for the sole or 
> LAN users or teams. It seems we may need to "bifurcate" to the risky and 
> less risky environments, another possibility is being able to run a 
> vulnerability check on a wiki.
>
> The best security will give us our cake and we can eat it too, the wrong 
> security will mean we can't eat the cake, or look at it in the security of 
> our own room.
>
> In closing of great importance are the many possible ways tiddlywiki can 
> be made use of, but we need to maintain flexibility even when attempting to 
> secure it the the "great unwashed internet", because it often has little or 
> nothing to do with the internet. 
>
> Regards
> Tones
>
>
>
> On Wednesday, 18 August 2021 at 13:33:11 UTC+10 Mark S. wrote:
>
>> TW wasn't built from the ground-up for mult-user, and it's definitely not 
>> how most people are using it. I'm sure products built as server-side 
>> entities (e.g. WikiMedia) have all sorts of protection against injected 
>> code. 
>>
>> Anyone who can write and  save a tiddler can make a javascript tiddler, 
>> or a widget, or overwrite a javascript filte operator, or maybe header 
>> scripts, or maybe in-frame code. I guess you would have to think of all the 
>> ways that code could be injected and then neutralize everything that 
>> matched. But you'd have to do it before the tiddlers got written to the 
>> common pool, and you'd have to either block legitimate uses of the iframe, 
>> or figure out some way to detect that the frame doesn't contain js source 
>> code.
>>
>>
>>
>> On Tuesday, August 17, 2021 at 7:06:05 PM UTC-7 joshua@gmail.com 
>> wrote:
>>
>>> I am currently playing with "real-time multiplayer" capabilities for 
>>> TW5, so this is an interesting security vulnerability to be aware of.
>>>
>>> My primary concern was "what if a malicious user connected a 
>>> MIS-IDENTIFIED wiki to a real-time server. It has a bunch of malicious 
>>> tiddlers, and it DOES NOT have a bunch of tiddlers that exist in the server 
>>> copy."
>>>
>>> The real-time sync, once authenticated and authorized, would just 
>>> absoloutely wreck the server-copy of the wiki in this instance.
>>>
>>> Similarly, being able to some-how sync

[tw5] Seeking common misunderstandings

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

   - Macros are not function calls
   - Constant strings cannot be combined with transclusions

Are there other common misunderstandings – in terms of incorrect mental 
models of how TiddlyWiki operates, or things one might expect to work that 
don't – that come up here or elsewhere that you'd like to see documented in 
such a section?

Feedback on the drafts of the two existing sections would be welcome as 
well:

https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
  


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

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

Folks,

I watched the video which was too late at night for me to attend. You all 
have my support and I am ready to contribute. You are all going in the 
direction I have wanted for some time so you have a happy chappy here.

I was not able to receive a confirmation email or sign up to talk 
tiddlywiki, but will try again in 12 hours.

I am very happy with the choice of discourse for a range or reasons 

Regards
Tones
On Wednesday, 18 August 2021 at 14:16:10 UTC+10 Saq Imtiaz wrote:

> A video from the community call as well as slides are now available at the 
> new community forum:
>
> https://talk.tiddlywiki.org/t/aug-17th-2021-community-call-core-savers-syncers-upload-plugin-discourse-forum/28
>
> You will also find a thread there in the Plugins section for feedback on 
> the beta release of the FileUploads plugin.
>

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

Followup,

On Wednesday, August 18, 2021 at 2:03:53 PM UTC+2 PMario wrote:
... 

> The function is called "syncFromServer". So if you open 1 wiki in 2 tabs 
> of a browser you will informed, if someone opened a tiddler. A _red_ "draft 
> of ... by " button will be shown in the bottom of the wiki window. 
> The name will be only there if the username is set in the ConfigTiddler!
>

The server sent event plugin triggers the exact same mechanism. So it's 
possible to create instant feedback without the need to modify core 
functions. 
The disadvantage here is, that there is quite some overhead over the wire. 
The message flow is like this: 

 1) Server informs the client about new data
 2) Client reads all the tiddler meta-data without the text field
 3) Client compares all titles to see if something changed.
 4) If something changed the client reads ALL tiddlers including text 
content
 5) Client saves new data
 6) TW UI shows new data.

This workflow is OK for the current client implementation, since it runs on 
a client-side timer. But the with SSE it could be like this: 

 - 1) Server sends the changed data to the client
 - 2) Client saves them
  3) TW UI shows new data

As you can see, there is a lot of room for improvements. Especially the 
"Conflict Free Replicated Datatype" that Joshua mentioned would be an 
interesting option here. 

-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/ac142d55-8998-41b5-9b72-863c2f922a20n%40googlegroups.com.

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

On Wednesday, August 18, 2021 at 1:30:01 PM UTC+2 Stobot wrote:

> Ok, think my post went somewhere else (sorry if someone got that directly)

It did land in my PM inbox. .. No problem :)

> Newbie question for Charlie or others: How did you get Node.js version to 
> serve to multiple people? I use Node.js for my personal stuff and BOB for 
> multi-user but I have a lot of issues with BOB during 
> disconnects/reconnects that I don't have with "normal" node. 
>

I'm not mentioned directly, but I'll post anyway. ... The nodejs server 
could always serve the wiki to multiple people. ... BUT you shouldn't 
modify it at the same time. 

Arlen did create a "server sent events" plugin, that doesn't need 
web-sockets, but it is "unidirectional". So it allows the server to send 
messages to the client in 1 way only. The advantage is, that it is simpler 
to implement. .. 

If TW runs with nodejs, there is a function in the client that reads all 
tiddler-titles from the server every minute. If there was a change that the 
server knows about, it will load "all-tiddlers" from the server, including 
new ones. 

The function is called "syncFromServer". So if you open 1 wiki in 2 tabs of 
a browser you will informed, if someone opened a tiddler. A _red_ "draft of 
... by " button will be shown in the bottom of the wiki window. The 
name will be only there if the username is set in the ConfigTiddler!

The maximum delay is 1 minute. This function is in there for quite some 
time already. 

The problem is, that 1 minute delay can be way to long, if 2 persons want 
to edit at the same time. ... Server-sent-events works almost instantly. 
... BUT it has some flaws at the moment, that I did describe in the other 
post. 

-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/459fb5e1-2ac1-458f-83bb-d7f6d588e55en%40googlegroups.com.

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

Ok, think my post went somewhere else (sorry if someone got that directly)

Newbie question for Charlie or others: How did you get Node.js version to 
serve to multiple people? I use Node.js for my personal stuff and BOB for 
multi-user but I have a lot of issues with BOB during 
disconnects/reconnects that I don't have with "normal" node. 

Joshua: I eagerly wait to hear about your multi-user solution coming soon! 
As I mentioned to Boris and others when the open collective first started, 
I was happy to support the collective generally, but I would be most 
inclined to donate around future multi-user development, as that opens up a 
lot of things for me. Let me know if I can help in any way!

On Wednesday, August 18, 2021 at 4:50:36 AM UTC-4 PMario wrote:

> On Wednesday, August 18, 2021 at 4:27:18 AM UTC+2 joshua@gmail.com 
> wrote:
>
> Aside: I also noticed that if you "Close" an open draft tiddler with the 
>> `X` button, that it deletes the draft from the wiki, and this really 
>> disturbs drafts from other users that are being edited live note to 
>> self to file a bug report on that.
>>
>
> The (x) button top right at the edit tiddler toolbar is the "discard 
> changes" button. It needs to delete the draft tiddler. This behaviour can't 
> be changed. 
>
> If you click the x-button in the right sidebar : Open tab it only removes 
> the tiddler from the story river. 
>
> So plugins that want to implement a different behaviour have to replace 
> the cancel button depending on the user name. 
> So if the user-name in the wiki is the same as the user-name shown in the 
> draft tiddler they need to see the "core cancel button". ... 
> If it is different they need to see the plugin-cancel-button. 
>
> Replacing the core button, without modifying it is easy: Set $:/
> config/EditToolbarButtons/Visibility/$:/core/ui/Buttons/cancel to 
> "hidden" and it will be gone. 
>
> The new "Remove draft from story river" button can have a similar icon but 
> only removes the tiddler from the story river. 
>
> The same function from "sidebar : Open" can be used. Creating a new 
> plugin-cancel-button is simple just tag it $:/tags/EditToolbar 
>
> -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/fea6399b-6ee0-43df-aee5-258c8127ca1an%40googlegroups.com.

[tw5] Generating Static Sites & Plugins

2021-08-18 Thread Louis Davout

So I'm using the render command to generate a static site. I'm also using 
some plugins that at the very least include css such as TW-Shiraz. Is there 
a best practice for getting this to work or do I need to manually modify my 
render template to include references to all the css files used and copy 
via script all those css files to my exported directory?

Thanks.

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

[tw5] Re: how to set a global variable with a tiddler field value

2021-08-18 Thread Eric Shulman

On Wednesday, August 18, 2021 at 3:25:22 AM UTC-7 vpl wrote:

> In fact my problem was linked to a button action and thanks to  
> https://tiddlytools.com/timer.html code sample I was able to find a work 
> an option 
> \define tasks_delete()
> <$vars  projectId={{{ [get[projectId]] }}}>
> <$reveal default="show" type="match" text="show">
> <$button class="tc-button tt-button" tooltip="delete this alarm"> 
> {{$:/core/images/delete-button}}
> <$action-listops $tiddler=<> $field="tasks" 
> $subfilter="-[[$(this_alarm)$]]" />
>   
> 
> \end
> The $reveal seems to be mandatory to get access to my projectId variable 
> withing the button action-listops
>

Here's a trimmed down version that eliminates the unneeded excess syntax:
\define tasks_delete()
<$button class="tc-button" tooltip="delete this task"> 
{{$:/core/images/delete-button}}
   <$action-listops $tiddler={{{ [get[projectId]] }}} 
$field="tasks" $subfilter="-[[$(this_alarm)$]]" />

\end

Notes:
* The $vars is not needed.  Instead, use $tiddler={{{ 
[get[projectId]] }}} directly in the $action-listops widget
* Eliminate the $reveal and /$reveal.  Quite obviously, "show" will always 
match "show", so this does nothing.
* Remove "tt-button" from the $button class="...";  this is a TiddlyTools 
custom classname that is almost certainly not defined in your TiddlyWiki.
* Fix the tooltip text to say "task" instead of "alarm"
* $(this_alarm)$ references a variable defined outside the tasks_delete() 
macro and should probably be changed to whatever variable holds the name of 
the task you are deleting.

-e

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

[tw5] Refer to the same tiddler with multiple names

2021-08-18 Thread Sandip Deshmukh

There are times when I would like to call a tiddler by multiple names. This 
is true especially about names of people, places, etc.

In Wikipedia, one can see mentions like this:

"JFK", "John Kennedy", and "Jack Kennedy" redirect here

Does similar functionality exist in tiddlywiki? It will mean [[JFK]] [[John 
Kennedy]] refer to this tiddler and backlinks of that tiddler show all 
tiddlers where either of the names are used.

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

[tw5] Re: how to set a global variable with a tiddler field value

2021-08-18 Thread vpl

Thanks a lot for this detailed answer which is going beyond my current 
expertise and understanding of these languages suptilities
In fact my problem was linked to a button action and thanks to  
https://tiddlytools.com/timer.html code sample I was able to find a work an 
option 

\define tasks_delete()
<$vars  projectId={{{ [get[projectId]] }}}>
<$reveal default="show" type="match" text="show">
<$button class="tc-button tt-button" tooltip="delete this alarm"> 
{{$:/core/images/delete-button}}
<$action-listops $tiddler=<> $field="tasks" 
$subfilter="-[[$(this_alarm)$]]" />
  

\end

The $reveal seems to be mandatory to get access to my projectId variable 
withing the button action-listops

Thanks a lot for  your help

Regards

Vpl

Le mardi 17 août 2021 à 17:06:55 UTC+2, Soren Bjornstad a écrit :

> vpl,
>
> First of all, the syntax for incorporating a variable into a filter 
> expression is not <> but :
>
> \define test_project() {{{ [get[projectId]] }}}
>
> However, this still may not work, depending on how you use the macro. It's 
> tempting to think of macro transclusions as "function calls", where when 
> you say <> you get the result of evaluating their contents as 
> wikitext. But this is not how macros work – instead, *the exact text of 
> the macro* (with any $text substitutions$ the macro might include) is 
> inserted wherever the <> is used, which in this case is 
> a filter expression in triple curly braces.
>
> Now, this will still work fine if you just say, for instance:
>
> <>
>
> In this case, TW replaces <> with {{{ 
> [get[projectId]] }}}, then sees that wikitext in the body of a 
> tiddler, evaluates it, and gets the project ID. But it won't work if you 
> try to use it within another filter expression, or as the value of an HTML 
> or widget attribute, e.g., suppose you had a tiddler whose title was this 
> project ID and wanted to transclude it:
>
> <$transclude tiddler=<>/>
>
> In this case, TW will be looking for a tiddler called "{{{ 
> [get[projectId]] }}}", and it presumably won't find it.
>
> If you need to, you can get around this with the $wikify widget:
>
> <$wikify name="myProjectId" text=<>>
>   <$transclude tiddler="myProjectId"/>
> 
>
> In this case, you explicitly tell TW to evaluate the wikitext "{{{ 
> [get[projectId]] }}}", then use the result to transclude the 
> appropriate tiddler.
>
> You can read more on this in the Wikification section 
>  of *Grok TiddlyWiki*.
> On Tuesday, August 17, 2021 at 9:56:51 AM UTC-5 vpl wrote:
>
>> Hi,
>>
>> I want to define a global variable in my script with the value contained 
>> into a tiddler field
>> When I hard code the global variable like
>>
>> \define test_project() project-1
>>
>> I can use the <> variable without issue 
>>
>> But when I want this <> to be initialised to a tiddler's  
>> field like the following this does not work
>>
>> \define test_project() {{{ [<>get[projectId]] }}}
>>
>> Any "magic" idea ..??
>>
>> Thanks a lot for your support
>>
>> Regards vpl
>>
>

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

[tw5] Re: TiddlyWikis on node.js: includeWikis: configuration BEFORE includes

Hi,
As Joshua pointed out it mainly is a convenience function for developers. 
And as such it has some rough edges. 
One of them you found out. 

The second one is, that you can't define the "bag" that is used to store 
completely new tiddlers. It is hardcoded by in the server tiddlywiki.info 
file. 

"config": {
"default-tiddler-location": "../tw5.com/tiddlers"
}

That's the main reason, why you needed to modify the .info file 2 times to 
rename your site-title and why we need to work with a clunky tiddler as: $:/
config/OriginalTiddlerPaths (which remembers the paths of existing 
tiddlers) and $:/config/FileSystemPaths  which defines the paths of new 
tiddlers. ... :/ 

Most of the TW server functions know already about: recipe, bag and 
permissions field, but they don't use them atm. 

-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/8f989bfd-8248-4469-be06-883504bb871en%40googlegroups.com.

[tw5] Re: Speech To Text v1.0.6 Released - Piping of Text into inputs and textareas

2021-08-18 Thread Ste

That is very cool!

On Wednesday, 18 August 2021 at 08:53:25 UTC+1 BurningTreeC wrote:

> The plugin works best on Chrome/Chromium browsers and using the NodeJs 
> configuration
>
> file:/// urls don't keep the permission for microphone access but https:// 
> urls do. The NodeJs configuration by default serves the wiki at 
> https://127.0.0.1:8080 and Chrome/Chromium can grant permissions to 
> microphone access permanently to this url
>
> If you have questions how to set up a Wiki under NodeJs, please ask and we 
> can help you here
>
> Best wishes,
> Simon
>
> BurningTreeC schrieb am Mittwoch, 18. August 2021 um 08:18:13 UTC+2:
>
>> I hope we can get some feedback from users if there are any
>>
>> BurningTreeC schrieb am Dienstag, 17. August 2021 um 17:31:59 UTC+2:
>>
>>>
>>> Finn Lancaster and I (Simon Huber alias BurningTreeC) are proud to 
>>> announce the release of v1.0.6 of the Speech to Text plugin 
>>> 
>>>
>>> It comes with the following changes and additions
>>>
>>>
>>>- Insertion of text into inputs and textareas (including CodeMirror) 
>>>using the "Ok Wiki insert" command
>>>- More precise configuration of commands in your own language
>>>- Bug fixes, especially RSOD when trying to start recording while 
>>>it's already running
>>>- Configuration option to start recording automatically when the 
>>>wiki starts up
>>>- Configuration option for your own commands to stop listening
>>>- Configuration option for your own commands to insert text into 
>>>inputs and textareas
>>>
>>>
>>> Please let us know how you like this version of the plugin
>>>
>>> Best wishes
>>>
>>>

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

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

On Wednesday, August 18, 2021 at 4:27:18 AM UTC+2 joshua@gmail.com 
wrote:

Aside: I also noticed that if you "Close" an open draft tiddler with the 
> `X` button, that it deletes the draft from the wiki, and this really 
> disturbs drafts from other users that are being edited live note to 
> self to file a bug report on that.
>

The (x) button top right at the edit tiddler toolbar is the "discard 
changes" button. It needs to delete the draft tiddler. This behaviour can't 
be changed. 

If you click the x-button in the right sidebar : Open tab it only removes 
the tiddler from the story river. 

So plugins that want to implement a different behaviour have to replace the 
cancel button depending on the user name. 
So if the user-name in the wiki is the same as the user-name shown in the 
draft tiddler they need to see the "core cancel button". ... 
If it is different they need to see the plugin-cancel-button. 

Replacing the core button, without modifying it is easy: Set $:/
config/EditToolbarButtons/Visibility/$:/core/ui/Buttons/cancel to "hidden" 
and it will be gone. 

The new "Remove draft from story river" button can have a similar icon but 
only removes the tiddler from the story river. 

The same function from "sidebar : Open" can be used. Creating a new 
plugin-cancel-button is simple just tag it $:/tags/EditToolbar 

-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/2865d117-7f76-4189-ba83-f703d6208d94n%40googlegroups.com.

[tw5] Re: Speech To Text v1.0.6 Released - Piping of Text into inputs and textareas

2021-08-18 Thread BurningTreeC

The plugin works best on Chrome/Chromium browsers and using the NodeJs 
configuration

file:/// urls don't keep the permission for microphone access but https:// 
urls do. The NodeJs configuration by default serves the wiki at 
https://127.0.0.1:8080 and Chrome/Chromium can grant permissions to 
microphone access permanently to this url

If you have questions how to set up a Wiki under NodeJs, please ask and we 
can help you here

Best wishes,
Simon

BurningTreeC schrieb am Mittwoch, 18. August 2021 um 08:18:13 UTC+2:

> I hope we can get some feedback from users if there are any
>
> BurningTreeC schrieb am Dienstag, 17. August 2021 um 17:31:59 UTC+2:
>
>>
>> Finn Lancaster and I (Simon Huber alias BurningTreeC) are proud to 
>> announce the release of v1.0.6 of the Speech to Text plugin 
>> 
>>
>> It comes with the following changes and additions
>>
>>
>>- Insertion of text into inputs and textareas (including CodeMirror) 
>>using the "Ok Wiki insert" command
>>- More precise configuration of commands in your own language
>>- Bug fixes, especially RSOD when trying to start recording while 
>>it's already running
>>- Configuration option to start recording automatically when the wiki 
>>starts up
>>- Configuration option for your own commands to stop listening
>>- Configuration option for your own commands to insert text into 
>>inputs and textareas
>>
>>
>> Please let us know how you like this version of the plugin
>>
>> Best wishes
>>
>>

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

Re: [tw5] Installing plugins in Android

2021-08-18 Thread Sandip Deshmukh

Thanks.That did it.



On Monday, August 16, 2021 at 10:36:49 PM UTC+5:30 jeremy...@gmail.com 
wrote:

> Hi Sandip
>
>
> On 16 Aug 2021, at 16:01, Sandip Deshmukh  wrote:
>
> A newbie here. So, bear with me if this is a basic question.
>
> On my desktop, I am able to install several plugins not listed in 
> tiddlywiki official directory by dragging the buttons to my wiki.
>
> But how do I do the same on my Android phone? Dragging is not possible 
> there.
>
>
> You should be able to use the “import” button in the “Tools” tab of the 
> sidebar to import the JSON file containing the plugin,
>
> 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/f8b37185-70f0-4a3a-bdd1-9f5677d59858n%40googlegroups.com.

[tw5] Re: Speech To Text v1.0.6 Released - Piping of Text into inputs and textareas

2021-08-18 Thread BurningTreeC

I hope we can get some feedback from users if there are any

BurningTreeC schrieb am Dienstag, 17. August 2021 um 17:31:59 UTC+2:

>
> Finn Lancaster and I (Simon Huber alias BurningTreeC) are proud to 
> announce the release of v1.0.6 of the Speech to Text plugin 
> 
>
> It comes with the following changes and additions
>
>
>- Insertion of text into inputs and textareas (including CodeMirror) 
>using the "Ok Wiki insert" command
>- More precise configuration of commands in your own language
>- Bug fixes, especially RSOD when trying to start recording while it's 
>already running
>- Configuration option to start recording automatically when the wiki 
>starts up
>- Configuration option for your own commands to stop listening
>- Configuration option for your own commands to insert text into 
>inputs and textareas
>
>
> Please let us know how you like this version of the plugin
>
> Best wishes
>
>

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

[tw5] Re: I Think I Hacked TiddlyWiki