[tw5] Re: Remove the same tag on many tiddles but not the tiddle itself

2022-04-01 Thread TW Tones
The is an action send message to remove a tag and you can do this to 
multiple tiddlers at once. You can choose to exclude the current tiddler 
"-[]" or in the same button trigger add it back with 
tm-add-tag on the current tiddler.

<$button...
<$list filter=
action widgets for each listed tiddler

Button name




On Friday, 1 April 2022 at 20:24:35 UTC+11 PMario wrote:

> Hi,
> Have a closer look at https://tiddlywiki.com/#ActionListopsWidget .. 
> There may be the info you need. 
> -mairo
>
>

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


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

2022-04-01 Thread TW Tones
 *Custom Target/tab: *

I have now tested opening the current wiki in a new tab with the target 
set, so that if bookmarked, subsequent visits with the bookmark open the 
same named tab. I knew this worked however;

   - At the very same time a link opens a new tab, the current tab can 
   initiate a modal with no exit, requesting the user closes the tab.
   - If combined with the other interactions demanded by the "Chromium 
   native file system saver plugin" the complexity is further reduced.
   - I re-tested the fact that bookmarks and/or pinned tabs (with a target 
   set) retain knowledge of the target name used to open them
   
Just to clarify my suggestions in this thread relate to using the " Chromium 
native file system saver plugin" to make a "wiki your own" with local 
saving - non-multiuser, it is multi-user in a sense each user ends up with 
their own wiki.
I am also endeavoring to find solutions to make using this "saver" as 
simple to use as possible so it works for new users.

See for more on requirements for multi-user my comments at 
https://talk.tiddlywiki.org/t/multi-user-alternative-to-tiddlywiki/2899/24?u=tw_tones


On Saturday, 2 April 2022 at 15:43:33 UTC+11 TW Tones wrote:

> On Saturday, 2 April 2022 at 05:55:53 UTC+11 dyllon...@gmail.com wrote:
>
>>
>>- *Copy path to clipboard:* That's a good idea and should be possible 
>>when loaded as file://. UI design is a consideration here to make it 
>> clear 
>>to users when copying the path.
>>
>> It can be hidden within a custom/or customized save button once we are 
> confident the user is informed.
>  
>
>>
>>- *Custom Target/tab: *Do you mean something like  Open Links in a 
>>New Tab, Or Re-Use Already Existing Tab (usefulangle.com) 
>><https://usefulangle.com/post/337/html-open-links-in-same-tab>? I 
>>think this only works when clicking on links from a common page.
>>
>> yes, as per your link, a vanilla browser target.The trick here is once 
> establishing that the user wants to revisit a site, and or have a local 
> copy that we use the target parameter when constructing a link to the 
> address we want in a named tab. Following that link once makes it a named 
> tab, and future links to the same target open the same tab.
> Ideally we may be able to name the current tabs target (not sure we can), 
> worst case we open a new tab, closing the original tab. The key is to trap 
> it into A bookmark to open the site in future.
>  
> https://tiddlywiki.com/#Saving%20on%20Browser%20with%20File%20System%20Access%20API;
>  
> target="tiddlywiki.com">Saving on Browser with File System Access API
> https://tiddlywiki.com/#HelloThere; target="tiddlywiki.com
> ">~HelloThere
>
>>
>>- *Local storage: *Not really all that safe since we can't guarantee 
>>that changes will be flushed to disk before leaving the browser 
>>
>>  From my own experiments this has never being a problem, and if the 
> changes are committed to disk with "Chromium native file system saver 
> plugin" this is a non-issue. All it does is defer the saving of changes to 
> a save wiki step, ie no need to auto-save. 
>
>>
>>- If going with that kind of approach, I would rather just use a JS 
>>lock which can work with tabs in the same browser window.
>>
>> I do not know what JS Lock is to compare. Can you enlighten me please.
>  
>
>>
>>- *File Associations: *Might work, though that requires some platform 
>>specific code such as an installer to setup the associations.
>>
>> For windows this is a simple registry entry. A very simple install, done 
> once for all tiddlywikis. But the truth is we should build some installers 
> for each OS.
>
> For Timimi, there is obviously the solution of disabling the saver via a 
>> setting, but that obviously sucks if you have multiple people using the 
>> wiki. It'd be nice if there was a way to specify a priority for savers, but 
>> I don't think there is one right now. I don't want to add a bunch of custom 
>> logic to this saver for other specific savers. I could add in some special 
>> field containing JS that can be modified for determining whether to enable 
>> this saver or not, but that seems like a lot of complexity for users.
>>
>
> I need to test this as the two may be possible at the same time, but it 
> could be a matter of manual disabling "Saving on Browser with File System 
> Access API" buy asking the user on first save, "*un-Check if you have 
> Timimi installed" as its not required. *Its all about finessing the 
> interface and options. 
&g

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

2022-04-01 Thread TW Tones


On Saturday, 2 April 2022 at 05:55:53 UTC+11 dyllon...@gmail.com wrote:

>
>- *Copy path to clipboard:* That's a good idea and should be possible 
>when loaded as file://. UI design is a consideration here to make it clear 
>to users when copying the path.
>
> It can be hidden within a custom/or customized save button once we are 
confident the user is informed.
 

>
>- *Custom Target/tab: *Do you mean something like  Open Links in a New 
>Tab, Or Re-Use Already Existing Tab (usefulangle.com) 
>? I 
>think this only works when clicking on links from a common page.
>
> yes, as per your link, a vanilla browser target.The trick here is once 
establishing that the user wants to revisit a site, and or have a local 
copy that we use the target parameter when constructing a link to the 
address we want in a named tab. Following that link once makes it a named 
tab, and future links to the same target open the same tab.
Ideally we may be able to name the current tabs target (not sure we can), 
worst case we open a new tab, closing the original tab. The key is to trap 
it into A bookmark to open the site in future.
 
https://tiddlywiki.com/#Saving%20on%20Browser%20with%20File%20System%20Access%20API;
 
target="tiddlywiki.com">Saving on Browser with File System Access API
https://tiddlywiki.com/#HelloThere; 
target="tiddlywiki.com">~HelloThere

>
>- *Local storage: *Not really all that safe since we can't guarantee 
>that changes will be flushed to disk before leaving the browser 
>
>  From my own experiments this has never being a problem, and if the 
changes are committed to disk with "Chromium native file system saver 
plugin" this is a non-issue. All it does is defer the saving of changes to 
a save wiki step, ie no need to auto-save. 

>
>- If going with that kind of approach, I would rather just use a JS 
>lock which can work with tabs in the same browser window.
>
> I do not know what JS Lock is to compare. Can you enlighten me please.
 

>
>- *File Associations: *Might work, though that requires some platform 
>specific code such as an installer to setup the associations.
>
> For windows this is a simple registry entry. A very simple install, done 
once for all tiddlywikis. But the truth is we should build some installers 
for each OS.

For Timimi, there is obviously the solution of disabling the saver via a 
> setting, but that obviously sucks if you have multiple people using the 
> wiki. It'd be nice if there was a way to specify a priority for savers, but 
> I don't think there is one right now. I don't want to add a bunch of custom 
> logic to this saver for other specific savers. I could add in some special 
> field containing JS that can be modified for determining whether to enable 
> this saver or not, but that seems like a lot of complexity for users.
>

I need to test this as the two may be possible at the same time, but it 
could be a matter of manual disabling "Saving on Browser with File System 
Access API" buy asking the user on first save, "*un-Check if you have 
Timimi installed" as its not required. *Its all about finessing the 
interface and options. 

   - Is there a simple way to disable "Saving on Browser with File System 
   Access API" with a click?, or could you build one in? For Timimi, there is 
   obviously the solution of disabling the saver via a setting, but that 
   obviously sucks if you have multiple people using the wiki. It'd be nice if 
   there was a way to specify a priority for savers, but I don't think there 
   is one right now. I don't want to add a bunch of custom logic to this saver 
   for other specific savers. I could add in some special field containing JS 
   that can be modified for determining whether to enable this saver or not, 
   but that seems like a lot of complexity for users. 

I just had a thought, can we interfere with the reload button to open the 
wiki in a "target tab"? Otherwise we just ask;

   - Please open the following link and bookmark the site, and pin the tab 
   (if desired) closing this existing tab.
   - Perhaps also there is a possibility to make use of the "new Window" 
   open and close features of TW 5.2.2

Regards
Tones

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


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

2022-03-26 Thread TW Tones
Brian;


>>- *Copy path to clipboard*: If we want to save a tiddlywiki to an 
>>existing location, as may be forced when reloading the wiki or browser, 
>> we 
>>already have the full path and filename available in the browser, it just 
>>needs to be available to the save as dialogue.
>>
>> Does this one have any technical barrier for you? Sounds like you have it 
> figured out. Sounds like a useful approach as long as the tiddlywiki is 
> loaded from a file url.
>

The only issue is the user needs to be told and/or reminded they can use 
crtl-v in the file dialogue. Its a trick and not commonly used, although 
easy to use. This is why if we can rely on local storage for small changes 
(no auto-save) and trigger a modal when saving we can present a modal to 
guide the user and address the need for the button click.

 

> [...]
>
>>
>>- *Custom Target/tab:* If we want to protect against opening the same 
>>wiki in a tab, one trick is after the first save (knowing the full path 
>> and 
>>filename) we can construct a html link with an appropriate target 
>>attribute, then navigate to that (if possible closing the original tab), 
>>thus the wiki is now running in a tab with a named target.
>>
>> What needs to know the full path and filename here? The user will know 
> and the browser will know, but the functionality running in the web page 
> (i.e. the tiddlywiki instance) will not know. It only has access to the 
> filename minus the directory location. The directory location is hidden 
> from it.
>

The full path and directory is known by a tiddlywiki loaded from file. If a 
user stores the full path and filename in a wiki it also known to that wiki 
(eg store in a cookie)

>
> The user has the information required to construct the html link you 
> mention, but the tiddlywiki page does not.
> [...]
>
 
Unless it is given and stores the full path and filename, however if we 
have a bookmarklet it can store the the full path and filename including a 
target tab. Clicking the same bookmark will always open in the same tab 
avoiding the opening of multiple tabs and the  global file:// issues(see 
next notes)

>
>>- 
>>   - This should help given the global file:// issues
>>   
>> I'm not sure what you mean here.
>

Just the "problem" with all file tiddlywikis having access to the same 
file:// domain. However it could be used for communication between wikis if 
we wanted. However as a rule we want a file:// tiddly wiki opened only once 
in a browser (or any browser) so there is not "contention"
 

>
>>- *Bookmarklet*: Perhaps extending the value of Custom Target/tab and 
>>because there is value using it, we can consider the use of a bookmarklet 
>>both with a target and a payload if necessary. 
>>
>> What do you mean by "payload"? Could you give an example? 
>
>>
>>- An example may be so if the user returned to the source site, 
>>published on the internet the bookmarklette can recall you already have a 
>>local copy and with a click. When saving from the source URL for the 
>> first 
>>time we could prompt the user to use their saved bookmark if they want to 
>>access their local copy, to not create a new one, or override and 
>> existing 
>>one.
>>
>> I'm not sure how the bookmarklet would know you already have a local copy 
>

The bookmarklet only exists if you created it from a local copy, it 
contains the link and target but can include a payload ie a tiddler 
containing details about the local copy. Thus the bookmarklete knows you 
have a local copy.

A trick that can be used is on arriving at an internet site we want to save 
a local copy we use the existing mechanism to save the local copy, then we 
can open that copy (ideally closing the internet tab #1). Once you have 
opened the local copy, you have access to the full path. Now so we do not 
loose the link to the local copy we can provide a link (we build it and can 
add a payload) for users to drag into their favorites and bookmarks.

#1 - before closing the internet tab

   - Save a cookie (or more) for that site indicating the existence of a 
   local copy.
   - When our internet wiki loads it can test for these cookies, and advise 
   the user a local copy exists. 
   - It can then ask ONCE the bookmark to be clicked, dropping the "payload 
  tiddler", then the internet site can also save the full path into the 
  cookie(s)
   - Subsequent visits to the internet site in the same browser can list 
   all local copies of itself and provide links to its target tab OR allow new 
   copies to be saved locally.

I know my replies are somewhat convoluted but this is a somewhat complex 
problem with substantial features if we can achieve it. I believe we just 
need a little more tweaking and a strong guided workflow.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop 

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

2022-03-24 Thread TW Tones
Folks,

I am watching this with "bated breath" ( *in a nervous and excited state 
anticipating what will happen*) however as I do not understand the 
technical part of the saver I am finding it hard to contribute.

It seems to me this is approaching the "Nirvana" of savable wikis without 
any additional installation of servers, savers or Browser addons. This will 
transform how people can acquire, use and distribute wikis to naive users. 
It just needs a little more work. 

What follows is some 'innovative' solutions I have developed that may be 
able to smooth the path to a solution with the least "resistance" of not 
almost transparent.

   - You may also find these tips and tricks powerful in their own right.
   - 'Innovative because' "I see few if anyone using them" 


I believe I can add a lot here but there remains a slight technical barrier 
for me. What I want to see is to minimize user interaction including 
between reloads, and when forced interaction is necessary, improve and 
guide the user for minimum complexity. Here are a few techniques that may 
help overcome the barriers.

   - *Copy path to clipboard*: If we want to save a tiddlywiki to an 
   existing location, as may be forced when reloading the wiki or browser, we 
   already have the full path and filename available in the browser, it just 
   needs to be available to the save as dialogue. 
   - I have created a save button with additional actions that copies the 
  contents of $:/info/url/full to the clipboard, where ctrl-V pastes 
  the full path and filename and I just click save.
  - This would save the need to remember the full path and filename and 
  reduce the error of selecting the wrong file
  - Remember also
 - the full path tells you if the wiki is at a file location which 
 is a useful piece of information
 - If we have a modal pop up as mentioned below in "Bait and 
 switch", this can be explained for the user, perhaps a variation for 
the 
 detected OS.
 - *Custom Target/tab:* If we want to protect against opening the 
   same wiki in a tab, one trick is after the first save (knowing the full 
   path and filename) we can construct a html link with an appropriate target 
   attribute, then navigate to that (if possible closing the original tab), 
   thus the wiki is now running in a tab with a named target. 
   - If we bookmark or pin the tab this remains the target. If clicked in 
  future it will open the very same tab, never another new tab.
 - Warns if unsaved changes exist in the tab.
 - This should help given the global file:// issues 
  - *Bookmarklet*: Perhaps extending the value of Custom Target/tab and 
   because there is value using it, we can consider the use of a bookmarklet 
   both with a target and a payload if necessary. An example may be so if the 
   user returned to the source site, published on the internet the 
   bookmarklette can recall you already have a local copy and with a click. 
   When saving from the source URL for the first time we could prompt the user 
   to use their saved bookmark if they want to access their local copy, to not 
   create a new one, or override and existing one.
   - *Bait and switch: *Using the existing save button or a customized copy 
   which does more work than the default save button, on this occasion opening 
   a modal with an explanation rather than adding another tiddler and set of 
   instructions would be wise. One could also allow the full path top be 
   copied to the clipbord etc... 
   - However this modal would not be displayed if it can go ahead and save 
  automatically. 
  - *Local storage:* As long as one does not tax the local storage 
   much, it can act as a fairly safe space to store changes, and if when 
   closing the tab the dirty indicator triggered the Native file save, then 
   all tiddlers are saved to file and the local storage vacated. 
   - The point here is automated save is not necessary but can be optional. 
  The user should be able to choose when they invoke the file saving.
   - *File Associations: *Most browsers on opening a tiddlywiki file, what 
   ever its name, detect its html and opens it as expected. This allows us to 
   save tiddlywikis as for example a empty.tw file. Helping distinguish it 
   from all other html files. Then we can provide (yes install) a file 
   association to force such files to be opened in a particular browser, in 
   this case the one with local storage for that wiki such as the one 
   containing the IndexDB. Perhaps a .twc (tiddlywiki chrome) or .twf firefox 
   or .twe tiddlywiki edge would be useful.
  - Browsers also enable handlers for given extension/mime types to be 
  set, which may be another avenue to improve user interaction more eg .tw*
  - *Note:* For me, if my default browser, or all browsers have the 
   Timimi extension installed it does not matter in which 

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

2022-02-22 Thread TW Tones
Dylon,

*One of the reasons for introducing the save button at startup is so the 
plugin can quickly read the original file and compute its file hash as soon 
as possible.*

In some of my own experiments, in a startup action if the wiki is available 
for editing I immediately save and reload it to indicate this session "owns 
it". Similarly when finished the final save needs to release it.

   - With a splash screen advising its loading this may be ok because in 
   need only be done once per session (that has the wiki for edit/save) even 
   on larger wikis.


I have come across two issues;

   - The browser session needs a finger print to be saved in local storage, 
   so this can be compared with the loaded copy of the wiki to check ownership
  - I have found an almost unique fingerprint
   - If the wiki is on file:// I have not found how to get a seperate 
   finger print for each tab, so it could be opened in more than one tab and 
   save will only save the current tabs changes.

Have you found a way to open a file:// wiki in two tabs and not confuse the 
session?

On Wednesday, 23 February 2022 at 13:09:32 UTC+11 dyllon...@gmail.com wrote:

> For contention, the current version actually does provide some integrity 
> measures. One of the reasons for introducing the save button at startup is 
> so the plugin can quickly read the original file and compute its file hash 
> as soon as possible.
>
> One the first save (i.e. when you click the button on the launch modal), 
> the hash of the serialized wiki is recorded. On subsequent saves, the 
> plugin compares the hash of the new version to the hash of the old version 
> to see if the file has changed unexpectedly (i.e. changes were made in a 
> different browser pane or it is on a network drive and someone else changed 
> it).
>
> I'm hesitant to rely too much on Tiddlywiki internals to try and maintain 
> forward compatibility, but it would be nice if this check were possible 
> without triggering an actual save. The other reason is to avoid unexpected 
> prompts when autosaving things obviously.
>
> I will also admit that as a software developer, I'm not the best person at 
> making people understand the saving mechanism without overwhelming them 
> with technical details.
>
> As for using a more intuitive save button, I'm welcome to suggestions 
> and/or pull requests so long as things scale for different browser/wiki 
> layouts and it doesn't pull in any large images (an SVG or something would 
> probably be ok). I agree the button used right now is kind of ugly. Another 
> thing to keep in mind with suggestions is that people might be using 
> different color schemes which I'd like the plugin to try and respect.
>
> Thanks for your feedback!
>
> On Friday, February 18, 2022 at 5:13:26 PM UTC-8 TW Tones wrote:
>
>> Folks,
>>
>> I believe this is already available on tiddlywiki.com at 
>> https://tiddlywiki.com/#Saving%20on%20Browser%20with%20File%20System%20Access%20API
>>
>> It is not yet comprehensively documented and it is hard for me to 
>> determine what level of functionality and customisation is available to us. 
>> As a solution only on Chromium browsers it is not yet global in 
>> application, so understanding its value is even harder to determine.
>>
>> I also ask myself "We require a click event to start the save dialogue" 
>> if this could not be placed in a save button "lookalike" or another way to 
>> make it user friendly. Ie just in time, not startup, Although in this 
>> thread others suggest they do not need it.
>>
>> Can someone write a user designer perspective and/or comparison with 
>> existing methods?
>>
>> My concerns;
>>
>>- How to design online tiddlywikis with a non-intrusive saving 
>>mechanism users can understand.
>>- Dealing with the contention possible with two parties editing the 
>>same site.
>>
>> I would appreciate it is someone can spell this out a little more for us 
>> who need it, and can't easily understand this from the jargon and reading 
>> between the lines in this discussion.
>>
>> Thanks
>> Tones
>> On Wednesday, 9 February 2022 at 11:10:40 UTC+11 PMario wrote:
>>
>>> Hi,
>>> I do like that option. 
>>> -mario
>>>
>>> On Wednesday, February 9, 2022 at 12:11:06 AM UTC+1 dyllon...@gmail.com 
>>> wrote:
>>>
>>>> It does work, though I think it is disruptive asking as soon as 
>>>> something is done which triggers autosave. However, I have put in an 
>>>> option 
>>>> with version 0.7.1 to disable the modal for those who don't like it.
>>>>

[tw5] Re: Is there an easy way for a MultiUser Tiddly Wiki?

2022-02-18 Thread TW Tones
Benedikt

Can you raise This in https://talk.tiddlywiki.org ?

The true and mature multi-user "edit" method is the bob.exe and bob plugin 
methods, but this is currently behind in tiddlywiki releases. We may be 
able to upgrade the non-bob.exe to 5.2.1 manually but then you need to 
ensure its safe on your LAN or the internet.

I have done a lot of work on the serial editing method so one user checks 
out the wiki at a time but it is not published it yet.

TW_Tones

On Friday, 18 February 2022 at 02:24:17 UTC+11 benedikt@web.de wrote:

> Hi everyone,
>
> I'm using TiddlyWiki for some years as my personal knowledge-base and I 
> love it.
>
> I'm also a member of a community for Multiprojektmanagement. I've shown my 
> TiddlyWiki to my peers and they like it. 
> Now we have the idea to use Tiddly Wiki as our shared knowledge-base. 
> Is there an easy way for setting up a Multiuser TiddlyWiki where everyone 
> can read and write, in best case simultaneously?
>
> I found Tiddlyhost - but it seems that only the owner can save changes.
> I read about a MultiUser-Plugin for Node-js. But we are no "techis" and 
> have no idea how to set up TiddlyWiki in a node.js.
> If I store it simply in a cloud and two users open the file, only the last 
> save is stored. The second user is not informed that someone else is 
> working on it.
>
> What we are looking for is a wiki, stored in a cloud like sharepoint, 
> onedrive, ... with Multiuser-Capabilities.
>
> Thanks for any ideas
>
> Benedikt
>

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


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

2022-02-18 Thread TW Tones
Folks,

I believe this is already available on tiddlywiki.com 
at 
https://tiddlywiki.com/#Saving%20on%20Browser%20with%20File%20System%20Access%20API

It is not yet comprehensively documented and it is hard for me to determine 
what level of functionality and customisation is available to us. As a 
solution only on Chromium browsers it is not yet global in application, so 
understanding its value is even harder to determine.

I also ask myself "We require a click event to start the save dialogue" if 
this could not be placed in a save button "lookalike" or another way to 
make it user friendly. Ie just in time, not startup, Although in this 
thread others suggest they do not need it.

Can someone write a user designer perspective and/or comparison with 
existing methods?

My concerns;

   - How to design online tiddlywikis with a non-intrusive saving mechanism 
   users can understand.
   - Dealing with the contention possible with two parties editing the same 
   site.

I would appreciate it is someone can spell this out a little more for us 
who need it, and can't easily understand this from the jargon and reading 
between the lines in this discussion.

Thanks
Tones
On Wednesday, 9 February 2022 at 11:10:40 UTC+11 PMario wrote:

> Hi,
> I do like that option. 
> -mario
>
> On Wednesday, February 9, 2022 at 12:11:06 AM UTC+1 dyllon...@gmail.com 
> wrote:
>
>> It does work, though I think it is disruptive asking as soon as something 
>> is done which triggers autosave. However, I have put in an option with 
>> version 0.7.1 to disable the modal for those who don't like it.
>>
>> On Sunday, February 6, 2022 at 1:46:16 AM UTC-8 PMario wrote:
>>
>>> On Sunday, February 6, 2022 at 12:54:25 AM UTC+1 brian@gmail.com 
>>> wrote:
>>> ...
>>>
 Now with the indexdb entry re-populated, the sequence looks like this:

1. Reload the TW page
2. Click the + button to create a new tiddler
3. Click the checkmark to save the tiddler
4. A dialog box asks me if I want to let the site edit the file. I 
click the "edit file" button
5. The file saves

 So it is working for me even without the settings modal. Do you see 
 this same behavior?

>>>
>>> I also think the modal isn't needed. The API requires user interaction. 
>>> ... But I think the described behaviour is good. The permission is 
>>> requested, when the first save happens. Since this save is a user 
>>> interaction it should be good enough.
>>>
>>> -mario
>>>
>>

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


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

2021-11-22 Thread TW Tones
My Guess is its only problem is with Negatives as charlie suggested;

1 lt 10: <$reveal type="lt" default=1 text=10>yes

So adding to the documentation "compares positive numbers only" is 
sufficient to correct it, until perhaps it is improved!

It should be quite easy to swap the negatives for positives to make it 
work, even if you need to convert them for display as negative numbers, and 
reverse the conditions eg lt for gt.

Tones

On Monday, 22 November 2021 at 13:45:58 UTC+11 andres@gmail.com wrote:

> I might be missing something, but given this demo here:
>
>   0 gt -5: <$reveal type="gt" default=0  text=-5>yes
> -1 gt -5: <$reveal type="gt" default=-1 text=-5>yes
> 
> -5 gt -1: <$reveal type="gt" default=-5 text=-1>yes
> 
>  0 lt -5: <$reveal type="lt" default=0  text=-5>yes
> 
> -5 lt  0: <$reveal type="lt" default=-5 text=0>yes
> 
> -1 lt -5: <$reveal type="lt" default=-1 text=-5>yes
> 
> -5 lt -1: <$reveal type="lt" default=-5 text=-1>yes 
>
> I get the following output:
>
>  0 gt -5: yes
> -1 gt -5: 
> -5 gt -1: yes  <-- -5 is less than -1, not greater
>  0 lt -5: 
> -5 lt  0: yes
> -1 lt -5: yes  <-- -1 is greater than -5, not less
> -5 lt -1: 
>
> Is this a known issue?
>
>

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


[tw5] Re: Tiddlers are dense and long

2021-10-16 Thread TW Tones
I would support Charlies comment by pointing out a case for long tiddlers 
(when search is a available to you) that some people just find it easier 
not to break information up into smaller pieces, sometimes this draws your 
attention to the fact you are almost repeating yourself. If and when you 
must then consider breaking it up. "Horses for courses".

On Saturday, 16 October 2021 at 03:17:15 UTC+11 cj.v...@gmail.com wrote:

> G'day,
>
> The best practices are the ones that fit you, and they incrementally 
> evolve as you evolve making all kinds of discoveries.
>
> When you find your workflows and organization becoming unwieldy, then 
> you'll know you need to change something.  (Change when it "costs", in 
> whatever way imaginable, too much not to change.)
>
> So keep doing what you are doing, but find little moments to read about 
> features in TiddlyWiki, about plugins, about all things 
> information/knowledge/documentation management.
>
> Take all that you read and park each in the back of your mind, so that 
> when you do run into things getting unwieldy, you'll have a "wait a minute, 
> I read something about that", if not enough for you to know what to do, 
> you'll know enough to ask the kinds of questions that get you help right 
> pronto.
>
> Find little reads like What Do We Mean by Componentization (for 
> Knowledge)? 
> ,
>  
> and investigate features like transclusion 
>  (and the great "Excise 
> " feature Tones mentioned) and 
> the terrific "Details widget" plugin 
>  by 
> Thomas Elmiger .
>
> Cheers !
> On Thursday, October 14, 2021 at 1:52:53 PM UTC-3 rikagol...@gmail.com 
> wrote:
>
>> I use my Tiddlywiki as a Zettelkaten (work in process!) and some of my 
>> Tiddlers are quite long. I title the Tiddler with a unique piece of 
>> information, in my own words, and then I include a description and 
>> resources. Some of my Tiddlers get very long...maybe too long. Is there a 
>> best practice for Tiddler length and what to include in the Tiddler?
>
>

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


[tw5] Re: Update MetaTabs

2021-10-14 Thread TW Tones
Perhaps share a link to them?

On Friday, 15 October 2021 at 11:44:08 UTC+11 komet...@gmail.com wrote:

> Are there any plans to update MetaTabs? Looks the last update was a few 
> years ago.

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


[tw5] Re: Tiddlers are dense and long

2021-10-14 Thread TW Tones
Also the editoolbar button "Excise" is great for breaking one tiddler into 
more than one link, tag or transclusion available.

There are often natural break locations like with a heading and all its 
"children" or things that you may reuse.

On Friday, 15 October 2021 at 03:52:53 UTC+11 rikagol...@gmail.com wrote:

> I use my Tiddlywiki as a Zettelkaten (work in process!) and some of my 
> Tiddlers are quite long. I title the Tiddler with a unique piece of 
> information, in my own words, and then I include a description and 
> resources. Some of my Tiddlers get very long...maybe too long. Is there a 
> best practice for Tiddler length and what to include in the Tiddler?

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


[tw5] Re: Some coding fun: "check boxes" that add/subtract from same field

2021-10-06 Thread TW Tones
It is interesting the conversation in the github discussion  issue request 
for a real solution . 

But twMat I think your solution is a* real solution* and does not 
necessarily need a core widget improvement, but it would be good, since 
this could be a common use feature.

I suppose the conversation could/should continue there in github, but I was 
wondering if a simple solution would be if the checkbox widgets checked and 
unchecked fields accepted filters that is they were treated as strings like 
currently unless they start with a "[" and if so first evaluate the filter 
to obtain the value. However the below may be a better solution. Because 
otherwise the two filters may need to match and I am not sure filters can 
handle the two purposes that checked and unchecked provide. 

The trick is these fields are used for two purposes one is to test the 
other is to set the state. This is easily the same thing when a simple 
string toggle is in place, but not if we want to use listops to handle 
multiple values in a field.

Then I thought if the string is prefixed with either a + or a - this 
implies it is a list ops function. So if the checkbox widget encounters a 
string with one of these prefixing it it uses list ops instead.

The following could be applied to any field however it replicates 
manipulating tags.
```<$checkbox field="tags" checked="+mytag" unchecked="-mytag" default=" 
-mytag"> Is it open?```

So if the +mytag was encountered the checked test would be 
`[contains:tags[mytag]]` and the unchecked `[!contains:tags[mytag]]`
and the reverse of the +- is reversed.

The action on click for each would be to provide the "signed value" to the 
listops subfilter.

We should however allow pseudo filters still to be passed eg; "+[[a 
tag/value with spaces]]" or "+[has[fieldname]then[client]else[friend]]" as 
long as they resolved to a string that can be given to the contains test 
and listops subfilter.

What do you think?
Perhaps I post it over there?


On Wednesday, 6 October 2021 at 23:33:53 UTC+11 cj.v...@gmail.com wrote:

> Your images are quite nice.  Besides, "real" checkboxes in HTML, aren't 
> they pretty much images?
>
> I say un-Beta that bad boy.
>
> On Wednesday, October 6, 2021 at 5:56:07 AM UTC-3 Mat wrote:
>
>> Thanks for referencing my old  http://toggle-in-field.tiddlyspot.com/
>>
>> One reason for it to be in beta is because of the (somewhat embarrassing) 
>> use of faux checkboxes (they're images!)
>>
>> I obviously agree there is a need for this, so I made an issue request 
>> for a real solution 
>> . If you agree 
>> with the request, please give it a like or comment in the thread there. I 
>> was hoping this would be solved with the latest TW release but evidently it 
>> was not.
>>
>> <:-)
>>
>

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


[tw5] Re: To structure or not to structure? Depends, eh?

2021-10-04 Thread TW Tones
Thanks Charlie,

But thanks to your inspiration for raising the the "conceptual issue", in a 
way it allowed me to state my thinking on the subject. 

Ideas, I feel I have failed to express so far.

Tones


On Tuesday, 5 October 2021 at 13:50:57 UTC+11 cj.v...@gmail.com wrote:

> Crap.  Forgot to say: your post is a damned fine contribution to the 
> knowledge base.
>
> On Monday, October 4, 2021 at 9:13:29 PM UTC-3 TW Tones wrote:
>
>> Charlie,
>>
>> There is in fact a middle way between structured and unstructured. An 
>> example would be if you were building a contact database and when it came 
>> to meeting extended family at holiday times and asked them for their phone 
>> number, you also noted down their parents names. You could even record 
>> there children's names and more but if you only recorded their parents 
>> names this would be fine. What then happens is over time as you speak to 
>> each member of the family and get their parents name the family tree 
>> hierarchy simply "emerges" from the details.
>>
>> You can see here that in the above example we have established that a 
>> hierarchy exists in the real world and ensure we simply collect enough 
>> information each time we talk to someone "Their parents" that the hierarchy 
>> builds over time. Such hierarchies need to tolerate missing information, 
>> but they can actually help us discover what information is missing, Which 
>> we can then seek.
>>
>> There are plenty of hierarchies that exist in the real world that almost 
>> need not be stated like family trees and
>> earth > Country > state > county > town > street > number 
>> If one assumes these exist in the first place, it informs us of what it 
>> takes to get a full address, but a fuzzy hierarchy and tolerance for 
>> missing information. for example you may only record a state/town for where 
>> a cousin lives, you can assume the planet, country and county and perhaps 
>> for now live without knowing street and number.
>>
>> The thing is by being aware of hierarchies that exist or you discover, 
>> and accounting for there existence, but not "slavishly" trying to build 
>> them, these hierarchies' just emerge from the shadows over time. In many 
>> ways this helps the unstructured data trend towards more complete 
>> information over time.
>>
>> To me this is where an unstructured database can exist, in such a way 
>> that overtime, the obvious, but even hidden structures start to emerge. And 
>> you see here there is not problem having both at once. In fact within our 
>> unstructured database there will be other emerging structures like lists, 
>> tables, networks and common attributes or values. For example, if someone 
>> has the "same home phone number" (land line) as another person, perhaps 
>> they live at the same address? We may learn they live together, even 
>> although we don't have their address (however we have the phone number 
>> which we can and ask for the address).
>>
>> This ability for tiddlywiki to accommodate the unstructured through to 
>> multiple and incomplete structures is, I believe, one of tiddlywiki's key 
>> attributes that can empower its application universally.
>>
>> Regards
>> Tones
>>
>> On Saturday, 2 October 2021 at 00:34:22 UTC+10 cj.v...@gmail.com wrote:
>>
>>> In my latest "brain-age" game (Coding Fun: My take on recipe ingredients 
>>> <https://groups.google.com/g/tiddlywiki/c/Ug8IsxJX0z8>), I've gone 
>>> all-in with structured data.
>>>
>>> *(Aside: I tend to prefer using data tiddlers over fields, but that's 
>>> the kind of conversation that deserves its own thread.)*
>>>
>>> Although structured data is very cool, I usually much prefer the 
>>> loosey-goosey unstructured data.
>>>
>>> Like just about all things, which is better (structured or unstructured)
>>>
>>>- it depends
>>>
>>> Structured data involves big effort up front, but with substantial 
>>> benefits later.
>>>
>>>- However, structure done wrong (big analysis up front did not 
>>>consider some things until elucidation happened while knee-deep in the 
>>>thick of it) can involve big effort re-jigging things if "quickly 
>>>adjustable re-design" wasn't built it.  (Maintaining documentation, even 
>>> if 
>>>just bread-crumbs, makes a re-jigging effort so much easier, but even 
>>>maintaining bread-crumbs can be some

[tw5] Re: To structure or not to structure? Depends, eh?

2021-10-04 Thread TW Tones
Charlie,

There is in fact a middle way between structured and unstructured. An 
example would be if you were building a contact database and when it came 
to meeting extended family at holiday times and asked them for their phone 
number, you also noted down their parents names. You could even record 
there children's names and more but if you only recorded their parents 
names this would be fine. What then happens is over time as you speak to 
each member of the family and get their parents name the family tree 
hierarchy simply "emerges" from the details.

You can see here that in the above example we have established that a 
hierarchy exists in the real world and ensure we simply collect enough 
information each time we talk to someone "Their parents" that the hierarchy 
builds over time. Such hierarchies need to tolerate missing information, 
but they can actually help us discover what information is missing, Which 
we can then seek.

There are plenty of hierarchies that exist in the real world that almost 
need not be stated like family trees and
earth > Country > state > county > town > street > number 
If one assumes these exist in the first place, it informs us of what it 
takes to get a full address, but a fuzzy hierarchy and tolerance for 
missing information. for example you may only record a state/town for where 
a cousin lives, you can assume the planet, country and county and perhaps 
for now live without knowing street and number.

The thing is by being aware of hierarchies that exist or you discover, and 
accounting for there existence, but not "slavishly" trying to build them, 
these hierarchies' just emerge from the shadows over time. In many ways 
this helps the unstructured data trend towards more complete information 
over time.

To me this is where an unstructured database can exist, in such a way that 
overtime, the obvious, but even hidden structures start to emerge. And you 
see here there is not problem having both at once. In fact within our 
unstructured database there will be other emerging structures like lists, 
tables, networks and common attributes or values. For example, if someone 
has the "same home phone number" (land line) as another person, perhaps 
they live at the same address? We may learn they live together, even 
although we don't have their address (however we have the phone number 
which we can and ask for the address).

This ability for tiddlywiki to accommodate the unstructured through to 
multiple and incomplete structures is, I believe, one of tiddlywiki's key 
attributes that can empower its application universally.

Regards
Tones

On Saturday, 2 October 2021 at 00:34:22 UTC+10 cj.v...@gmail.com wrote:

> In my latest "brain-age" game (Coding Fun: My take on recipe ingredients 
> ), I've gone all-in 
> with structured data.
>
> *(Aside: I tend to prefer using data tiddlers over fields, but that's the 
> kind of conversation that deserves its own thread.)*
>
> Although structured data is very cool, I usually much prefer the 
> loosey-goosey unstructured data.
>
> Like just about all things, which is better (structured or unstructured)
>
>- it depends
>
> Structured data involves big effort up front, but with substantial 
> benefits later.
>
>- However, structure done wrong (big analysis up front did not 
>consider some things until elucidation happened while knee-deep in the 
>thick of it) can involve big effort re-jigging things if "quickly 
>adjustable re-design" wasn't built it.  (Maintaining documentation, even 
> if 
>just bread-crumbs, makes a re-jigging effort so much easier, but even 
>maintaining bread-crumbs can be some effort.)
>- Building structure for possible future needs that never happen, that 
>makes big effort up-front not so pretty re the cost-benefit ratio
>
> Unstructured data involves little effort up-front (immediate benefit), but 
> could require big effort later: i.e. having to move all of that 
> unstructured data into fields when structure is needed.
>
> Way too many thoughts about it all to write here.  I'd need a dedicated 
> TiddlyWiki.
>
> All of that to say that my "brain-age" game of structured recipe 
> ingredients may turn into an expanded game that pits structured recipe 
> ingredients head-to-head with unstructured ingredients.
>
> Proof in the pudding, advantages and disadvantages to both, maybe some 
> trickery.
>
> Maybe via a shared TiddlyWiki running on nodejs, on a virtual machine, if 
> anybody is interested.  I do have, I think, enough credit in my Google 
> Compute Engine to setup a virtual machine for some collaborative 
> "brain-age" structured vs unstructured recipe tomfoolery for a couple of 
> months...
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 

[tw5] Re: Just a Filtering Code Pattern

2021-09-27 Thread TW Tones
JP,

One way of handling all tags on the current tiddler is not to use the 
various tag operators but address the tags field directly.

[all[current]get[tags]] returns the content of the tags field which 
includes all tags.

Does this meet with your requirement?

On Monday, 27 September 2021 at 22:08:07 UTC+10 jn.pierr...@gmail.com wrote:

> Just a thought: it would be fine if the tagging operator could have a 
> "all" parameter which would select tiddlers tagging all of the tags in 
> input (currently, that's "any tag is enough").
>
> Thus we would have a simple and readable solution as:
>
> {{{ [tag1 tag2 tag3 tag4 +[tagging:all[]]] }}}
>
> Le lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>
>> Hello all ! 
>> The filter syntax provided by @Álvaro  is very neat but doesnt match the 
>> requirements of cj.v : counting the tiddlers with 4 specifics tags and 
>> only those tiddlers.
>>
>> See this screenshot  :
>>
>> https://i.imgur.com/lVlsYZt.png
>>
>> I think it's because the commas imply an OR condition, but here we want 
>> an AND :)
>>
>> So with a a tiny bit of tweaking the correct filter is : 
>>
>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Here's a live demo : 
>>
>>
>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>
>>> - In the fields cases we have a workaround with `fields` operator. It 
>>> has suffixs (exclude, include)
>>> - I think that there in't any tiddler with those tags. The search is the 
>>> tiddler with all these tags (¿and any other?)
>>>
>>> In the case of titles, you find a issue, but I don't know its reason. I 
>>> was trying to find a workaround but i wasn't lucky. I also found that the 
>>> match operator doesn't support multiple parameters.
>>>
>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones 
>>> escribió:
>>>
>>>> Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] 
>>>> }}}
>>>>
>>>> On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:
>>>>
>>>>> Very interesting. 
>>>>>
>>>>> I think he documentation should be expanded to detail this. Multiple 
>>>>> parameters to operators are only documented in a few operators, but if I 
>>>>> read this correctly they can work on operators in *general*?
>>>>>
>>>>> If general you may expect this to work ```{{{ 
>>>>> [title[tid1],[tid2],[tid3]] }}}``` it does not.
>>>>> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
>>>>> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>>>>>
>>>>>> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
>>>>>> containing
>>>>>> ```
>>>>>> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
>>>>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>>>> ```
>>>>>>
>>>>>> and another tiddler with the four tags (note capitalization and 
>>>>>> spaces in the tag values).
>>>>>>
>>>>>> It *does* seem to work on both versions of TW
>>>>>> -e
>>>>>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>>>>>
>>>>>>> Alvaro;
>>>>>>>
>>>>>>> You suggested something like this
>>>>>>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>>>>>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>>>>>
>>>>>>> As far as I can see this does not work on the pre-release and the 
>>>>>>> t6ag format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not 
>>>>>>> documented
>>>>>>>
>>>>>>> Does not work. So I asked if you tested this?
>>>>>>>
>>>>>>>
>>>>>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>>>>>
>>>>>>>> I don't know if I understand you.
>>>>>>>>

[tw5] Re: Just a Filtering Code Pattern

2021-09-25 Thread TW Tones
Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] }}}

On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:

> Very interesting. 
>
> I think he documentation should be expanded to detail this. Multiple 
> parameters to operators are only documented in a few operators, but if I 
> read this correctly they can work on operators in *general*?
>
> If general you may expect this to work ```{{{ [title[tid1],[tid2],[tid3]] 
> }}}``` it does not.
> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>
>> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
>> containing
>> ```
>> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>> ```
>>
>> and another tiddler with the four tags (note capitalization and spaces in 
>> the tag values).
>>
>> It *does* seem to work on both versions of TW
>> -e
>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>
>>> Alvaro;
>>>
>>> You suggested something like this
>>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>
>>> As far as I can see this does not work on the pre-release and the t6ag 
>>> format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not documented
>>>
>>> Does not work. So I asked if you tested this?
>>>
>>>
>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>
>>>> I don't know if I understand you.
>>>>
>>>>
>>>> El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones 
>>>> escribió:
>>>>
>>>>> Alvaro;
>>>>>
>>>>> Have you tested this?
>>>>>
>>>>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>>>>> :filter[tags[]count[]compare:eq[4]]  }}}
>>>>>
>>>>> I cant see it working. Here 
>>>>> <https://tiddlywiki.com/#Filter%20Parameter> is says 
>>>>>
>>>>> * NEW IN: 5.1.23 Filter operators support multiple parameters which 
>>>>> are separated by a  ,  character.*
>>>>>
>>>>> *For example: [param1],[param2] or ,{param2}*
>>>>> However as far as I can see only if such multiple parameters are 
>>>>> documented in the operator in question.
>>>>>
>>>>> Tones
>>>>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>>>>
>>>>>> It works fine. I tried to find a alternative, but I wasn't lucky.
>>>>>>
>>>>>> When I resee your filter, I remember about the multiple parameters in 
>>>>>> filter operator with commas (from last version, 5.1.23). And we can add 
>>>>>> a 
>>>>>> second filter run that it applies your filter to result of first run. 
>>>>>> Then 
>>>>>> you can rewrite your filter something like this (in filtering 
>>>>>> transclusion)
>>>>>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>>>>>> :filter[tags[]count[]compare:eq[4]]  }}}
>>>>>>
>>>>>> Although maybe it be less understandble for you.
>>>>>>
>>>>>>
>>>>>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
>>>>>> jn.pierr...@gmail.com escribió:
>>>>>>
>>>>>>> That's fine by me.
>>>>>>>
>>>>>>> And yes filters are fun even if sometimes a bit tricky.
>>>>>>>
>>>>>>> So for the fun of it, you could arrange your filter so that the 
>>>>>>> input would be the 4 tags you want.
>>>>>>>
>>>>>>> something like that:
>>>>>>>
>>>>>>> \define fun(tags)
>>>>>>> <$set variable=occ filter="[[$tags]put your filter code 
>>>>>>> here...count[]]">Seen <> tiddlers with tags $tags$
>>>>>>> \end
>>>>>>>
>>>>>>> Sometimes, this fun has you coding javascript filter operator. Would 
>>>>>>> this be the case here? I have not thought about it yet.
>>>>>>>
>>>>>>> cheers,
>>>>>>>
>>>>>>>
>>>>>>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a 
>>>>>>> écrit :
>>>>>>>
>>>>>>>> Me and my interest in brain age games, I couldn't help but play 
>>>>>>>> around with a filter to find all tiddlers that have all four specified 
>>>>>>>> tags, but only those four tags.
>>>>>>>>
>>>>>>>> You'll find three tiddlers in the attached json.  Download the 
>>>>>>>> file, and drag into some TiddlyWiki instance (TiddlyWiki.com !) to 
>>>>>>>> take a 
>>>>>>>> gander.
>>>>>>>>
>>>>>>>> There are all kinds of ways to go about doing this sort of thing, 
>>>>>>>> with some filter operators maybe better suited, but I find the result 
>>>>>>>> a bit 
>>>>>>>> easier for me to understand (more logical to me, or maybe more 
>>>>>>>> self-explanatory, because of the way my brain works, I suppose.)  
>>>>>>>> Maybe 
>>>>>>>> just a difference between top-down view vs bottom-up view or something 
>>>>>>>> ...
>>>>>>>>
>>>>>>>> Yeah, I find filters fun.
>>>>>>>>
>>>>>>>

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


[tw5] Re: Just a Filtering Code Pattern

2021-09-25 Thread TW Tones
Very interesting. 

I think he documentation should be expanded to detail this. Multiple 
parameters to operators are only documented in a few operators, but if I 
read this correctly they can work on operators in *general*?

If general you may expect this to work ```{{{ [title[tid1],[tid2],[tid3]] 
}}}``` it does not.
or {{{ [all[current]get[caption],[description]] }}}``` it does not.
On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:

> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
> containing
> ```
> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
> :filter[tags[]count[]compare:eq[4]] }}}
> ```
>
> and another tiddler with the four tags (note capitalization and spaces in 
> the tag values).
>
> It *does* seem to work on both versions of TW
> -e
> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>
>> Alvaro;
>>
>> You suggested something like this
>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> As far as I can see this does not work on the pre-release and the t6ag 
>> format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not documented
>>
>> Does not work. So I asked if you tested this?
>>
>>
>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>
>>> I don't know if I understand you.
>>>
>>>
>>> El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones 
>>> escribió:
>>>
>>>> Alvaro;
>>>>
>>>> Have you tested this?
>>>>
>>>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>>>> :filter[tags[]count[]compare:eq[4]]  }}}
>>>>
>>>> I cant see it working. Here 
>>>> <https://tiddlywiki.com/#Filter%20Parameter> is says 
>>>>
>>>> * NEW IN: 5.1.23 Filter operators support multiple parameters which are 
>>>> separated by a  ,  character.*
>>>>
>>>> *For example: [param1],[param2] or ,{param2}*
>>>> However as far as I can see only if such multiple parameters are 
>>>> documented in the operator in question.
>>>>
>>>> Tones
>>>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>>>
>>>>> It works fine. I tried to find a alternative, but I wasn't lucky.
>>>>>
>>>>> When I resee your filter, I remember about the multiple parameters in 
>>>>> filter operator with commas (from last version, 5.1.23). And we can add a 
>>>>> second filter run that it applies your filter to result of first run. 
>>>>> Then 
>>>>> you can rewrite your filter something like this (in filtering 
>>>>> transclusion)
>>>>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>>>>> :filter[tags[]count[]compare:eq[4]]  }}}
>>>>>
>>>>> Although maybe it be less understandble for you.
>>>>>
>>>>>
>>>>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
>>>>> jn.pierr...@gmail.com escribió:
>>>>>
>>>>>> That's fine by me.
>>>>>>
>>>>>> And yes filters are fun even if sometimes a bit tricky.
>>>>>>
>>>>>> So for the fun of it, you could arrange your filter so that the input 
>>>>>> would be the 4 tags you want.
>>>>>>
>>>>>> something like that:
>>>>>>
>>>>>> \define fun(tags)
>>>>>> <$set variable=occ filter="[[$tags]put your filter code 
>>>>>> here...count[]]">Seen <> tiddlers with tags $tags$
>>>>>> \end
>>>>>>
>>>>>> Sometimes, this fun has you coding javascript filter operator. Would 
>>>>>> this be the case here? I have not thought about it yet.
>>>>>>
>>>>>> cheers,
>>>>>>
>>>>>>
>>>>>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a 
>>>>>> écrit :
>>>>>>
>>>>>>> Me and my interest in brain age games, I couldn't help but play 
>>>>>>> around with a filter to find all tiddlers that have all four specified 
>>>>>>> tags, but only those four tags.
>>>>>>>
>>>>>>> You'll find three tiddlers in the attached json.  Download the file, 
>>>>>>> and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a 
>>>>>>> gander.
>>>>>>>
>>>>>>> There are all kinds of ways to go about doing this sort of thing, 
>>>>>>> with some filter operators maybe better suited, but I find the result a 
>>>>>>> bit 
>>>>>>> easier for me to understand (more logical to me, or maybe more 
>>>>>>> self-explanatory, because of the way my brain works, I suppose.)  Maybe 
>>>>>>> just a difference between top-down view vs bottom-up view or something 
>>>>>>> ...
>>>>>>>
>>>>>>> Yeah, I find filters fun.
>>>>>>>
>>>>>>

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


[tw5] Re: Just a Filtering Code Pattern

2021-09-25 Thread TW Tones
Alvaro;

You suggested something like this
{{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
:filter[tags[]count[]compare:eq[4]] }}}

As far as I can see this does not work on the pre-release and the t6ag 
format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not documented

Does not work. So I asked if you tested this?


On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:

> I don't know if I understand you.
>
>
> El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones escribió:
>
>> Alvaro;
>>
>> Have you tested this?
>>
>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>> :filter[tags[]count[]compare:eq[4]]  }}}
>>
>> I cant see it working. Here <https://tiddlywiki.com/#Filter%20Parameter> 
>> is says 
>>
>> * NEW IN: 5.1.23 Filter operators support multiple parameters which are 
>> separated by a  ,  character.*
>>
>> *For example: [param1],[param2] or ,{param2}*
>> However as far as I can see only if such multiple parameters are 
>> documented in the operator in question.
>>
>> Tones
>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>
>>> It works fine. I tried to find a alternative, but I wasn't lucky.
>>>
>>> When I resee your filter, I remember about the multiple parameters in 
>>> filter operator with commas (from last version, 5.1.23). And we can add a 
>>> second filter run that it applies your filter to result of first run. Then 
>>> you can rewrite your filter something like this (in filtering transclusion)
>>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>>> :filter[tags[]count[]compare:eq[4]]  }}}
>>>
>>> Although maybe it be less understandble for you.
>>>
>>>
>>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
>>> jn.pierr...@gmail.com escribió:
>>>
>>>> That's fine by me.
>>>>
>>>> And yes filters are fun even if sometimes a bit tricky.
>>>>
>>>> So for the fun of it, you could arrange your filter so that the input 
>>>> would be the 4 tags you want.
>>>>
>>>> something like that:
>>>>
>>>> \define fun(tags)
>>>> <$set variable=occ filter="[[$tags]put your filter code 
>>>> here...count[]]">Seen <> tiddlers with tags $tags$
>>>> \end
>>>>
>>>> Sometimes, this fun has you coding javascript filter operator. Would 
>>>> this be the case here? I have not thought about it yet.
>>>>
>>>> cheers,
>>>>
>>>>
>>>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a 
>>>> écrit :
>>>>
>>>>> Me and my interest in brain age games, I couldn't help but play around 
>>>>> with a filter to find all tiddlers that have all four specified tags, but 
>>>>> only those four tags.
>>>>>
>>>>> You'll find three tiddlers in the attached json.  Download the file, 
>>>>> and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a 
>>>>> gander.
>>>>>
>>>>> There are all kinds of ways to go about doing this sort of thing, with 
>>>>> some filter operators maybe better suited, but I find the result a bit 
>>>>> easier for me to understand (more logical to me, or maybe more 
>>>>> self-explanatory, because of the way my brain works, I suppose.)  Maybe 
>>>>> just a difference between top-down view vs bottom-up view or something ...
>>>>>
>>>>> Yeah, I find filters fun.
>>>>>
>>>>

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


Re: [tw5] Counting specific words

2021-09-24 Thread TW Tones
I would just add all the solutions here it are counting words in a title or 
string or the text field. None are attempting to render the tiddler first 
so that lists transclusions and macros etc.. are first expanded.

You can use the wikify widget to wikify the result into a variable and pass 
that to the word count.

Tones

On Saturday, 25 September 2021 at 10:07:16 UTC+10 mohamed...@hotmail.com 
wrote:

> Thank you very much,
>
> both work, also one more question , to get anywhere remotely close to 
> writing code like this  for tiddly wiki , what language should i try to 
> learn, i have no coding skills, and was just wondering if i would invest my 
> time in learning a bit, what language should i be looking at?
>
> thanks again
>
> On Thursday, September 23, 2021 at 11:32:19 PM UTC+2 jn.pierr...@gmail.com 
> wrote:
>
>> actually, https://tiddlywiki.com/#Macro%20Definitions%20in%20WikiText is 
>> very confusing! It took me a lot of time to make any sense out of it for 
>> the special case like using <<< and after my own tests, I have failed to 
>> see that as useful.
>>
>> Your code is actual code and it would be good to use it rather than the 
>> current example.
>>
>> I was sure you coded  instead of <__arg__> and I had copied it and 
>> executed. It was not functioning as it should. But I can no more remember 
>> why: was it the problem I told about why regexp was better or was it that 
>> it did nothing?
>>
>> Anyway, thank you for your correction about what I told. I have yet again 
>> something about tiddlywiki today! And I could use it, definitely.
>>
>>
>>
>>
>>
>> Le jeudi 23 septembre 2021 à 18:04:26 UTC+2, jeremy...@gmail.com a 
>> écrit :
>>
>>> Hi Jean-Pierre
>>>
>>> You made an error in your macro, Jeremy. You should have used $arg$ 
>>> instead of .
>>>
>>>
>>> It's actually not an error: it's an alternative way to access the 
>>> parameters of macros. It avoids the problem that otherwise the code would 
>>> fail with a tiddler title containing a closing square bracket.
>>>
>>> There are docs here under "Parameters as Variables <<__...__>>":
>>>
>>> https://tiddlywiki.com/#Macro%20Definitions%20in%20WikiText
>>>
>>> But it is false nonetheless because it would, for example, cut word 
>>> "totem" if asked for word "to". My regular expression does not do that 
>>> thanks to the \b at both ends of the arguments.
>>>
>>>
>>> Yes, I did that quickly, but indeed I think that splitregexp would be 
>>> needed to make it practical, both to resolve the word boundary issue and 
>>> the case sensitivity issue.
>>>
>>> Best wishes
>>>
>>> Jeremy.
>>>
>>>
>>> Le jeudi 23 septembre 2021 à 16:45:46 UTC+2, jeremy...@gmail.com a 
>>> écrit :
>>>
 Another technique is to use the “split” operator to split the string by 
 the word:

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

 <>

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

 Best wishes

 Jeremy.

 On 23 Sep 2021, at 15:37, Jean-Pierre Rivière  
 wrote:

 Here it is.

 ```
 \define count-word(word, tid)
 {{{ 
 [[$tid$]get[text]search-replace:gi:regexp[\b$word$\b],[þ]dump:v[first]search-replace:g:regexp,[]dump:v[final]length[]]
  
 }}}
 \end

 <>
 ```

 I use a char that should never be within the tiddler, þ in my example. 
 You can use another rare character is old English is concerned! I replace 
 every occurrence of the word with it, then remove any other character then 
 count the length of the result. If you want case sensitive search, just 
 omit the `i` flag in the first `search-replace`.

 Le mercredi 22 septembre 2021 à 15:14:55 UTC+2, mohamed.e...@
 vodafone.com a écrit :

> Hi ,
>
> is there a way to count the number of occurrences of a specific word 
> in a tiddler
>
> I have serached , but could only find a plugin that counts the total 
> number of words, or total number characters.
>
>  
>

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


 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "TiddlyWiki" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to tiddlywiki+...@googlegroups.com.
>>>
>>> To view 

[tw5] Re: Just a Filtering Code Pattern

2021-09-24 Thread TW Tones
Alvaro;

Have you tested this?

{{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
:filter[tags[]count[]compare:eq[4]]  }}}

I cant see it working. Here  is 
says 

* NEW IN: 5.1.23 Filter operators support multiple parameters which are 
separated by a  ,  character.*

*For example: [param1],[param2] or ,{param2}*
However as far as I can see only if such multiple parameters are documented 
in the operator in question.

Tones
On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:

> It works fine. I tried to find a alternative, but I wasn't lucky.
>
> When I resee your filter, I remember about the multiple parameters in 
> filter operator with commas (from last version, 5.1.23). And we can add a 
> second filter run that it applies your filter to result of first run. Then 
> you can rewrite your filter something like this (in filtering transclusion)
> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
> :filter[tags[]count[]compare:eq[4]]  }}}
>
> Although maybe it be less understandble for you.
>
>
> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
> jn.pierr...@gmail.com escribió:
>
>> That's fine by me.
>>
>> And yes filters are fun even if sometimes a bit tricky.
>>
>> So for the fun of it, you could arrange your filter so that the input 
>> would be the 4 tags you want.
>>
>> something like that:
>>
>> \define fun(tags)
>> <$set variable=occ filter="[[$tags]put your filter code 
>> here...count[]]">Seen <> tiddlers with tags $tags$
>> \end
>>
>> Sometimes, this fun has you coding javascript filter operator. Would this 
>> be the case here? I have not thought about it yet.
>>
>> cheers,
>>
>>
>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a 
>> écrit :
>>
>>> Me and my interest in brain age games, I couldn't help but play around 
>>> with a filter to find all tiddlers that have all four specified tags, but 
>>> only those four tags.
>>>
>>> You'll find three tiddlers in the attached json.  Download the file, and 
>>> drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
>>>
>>> There are all kinds of ways to go about doing this sort of thing, with 
>>> some filter operators maybe better suited, but I find the result a bit 
>>> easier for me to understand (more logical to me, or maybe more 
>>> self-explanatory, because of the way my brain works, I suppose.)  Maybe 
>>> just a difference between top-down view vs bottom-up view or something ...
>>>
>>> Yeah, I find filters fun.
>>>
>>

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


[tw5] Re: how to add a button to the top right of the tiddler to copy the title ?

2021-09-24 Thread TW Tones
I know I am late to the GG party, spending more time in Discourse now,

Try my attached json on tiddlywiki.com. It contains;

   - A button to copy the current title
   - A button to copy the current tiddler text
   - A neat little trick to link to the last tiddler and or copy buttons 
   from the sidebar

The buttons are effective in the control panel appearance toolbars, uncheck 
to hide behind more.

If needed I can also find buttons I made to copy the "current tiddler" in 
the following forms;

   - [[current tiddler]]
   - {{current tiddler}}

Regards
Tones


On Sunday, 19 September 2021 at 15:31:57 UTC+10 imleg...@gmail.com wrote:

> Done, two tiddlers needed one for logic one for button image. Thanks. 
>
> On Sunday, September 19, 2021 at 8:50:56 AM UTC+8 Télumire wrote:
>
>> Oups sorry theok was faster than me ahah
>>
>> Le dimanche 19 septembre 2021 à 02:49:54 UTC+2, Télumire a écrit :
>>
>>> You also need to add the tag $:/tags/ViewToolbar if you want your 
>>> button to be displayed in the view toolbar (which is at the right of the 
>>> tiddler title).
>>>
>>> If you want your button to be really in the title itself and not in the 
>>> toolbar, then you can use the field icon, which display the content of the 
>>> tiddler in the title, then with css move the icon to the right, e.g : 
>>> https://telumire.github.io/TW-tips/index.html#tasker%20button%20at%20the%20right%20of%20the%20title
>>>
>>> Le samedi 18 septembre 2021 à 16:55:49 UTC+2, cj.v...@gmail.com a 
>>> écrit :
>>>
 To study and copy for the creation of your own button:

 $:/core/ui/Buttons/edit *(you need to at least have a tiddler like 
 this for your button)*
 $:/core/images/edit-button *(nice to have one like this, even if your 
 image is just an emoji or whatever)*
 $:/language/Buttons/Edit/Caption  *(maybe nice to have one like this)*
 $:/language/Buttons/Edit/Hint  *(maybe nice to have one like this)*

 On Saturday, September 18, 2021 at 10:42:35 AM UTC-3 imleg...@gmail.com 
 wrote:

> <$button message="tm-copy-to-clipboard" param=<>>
> Copy date to clipboard
> 
>
> I know the command is something like this, but I don't know how to add 
> a button to the top right beside the edit clone tiddler. 
>


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


copy-text-title-buttons.json
Description: application/json


[tw5] Re: "Loud Tones?" on Discourse discussion: talk.tiddlywiki.org

2021-09-18 Thread TW Tones
Charlie,

I understand your concerns and will argue for GG continuing, visit 
occasionally and hopefully one day we will find ways to make Discourse more 
acceptable for you. Of course no final decision has being made yet. This is 
my personal position.

Tones

On Saturday, 18 September 2021 at 15:58:22 UTC+10 cj.v...@gmail.com wrote:

> It would be good for the discourse forum to indicate that moderators can 
> also edit members' posts to benefit the community.
>
> That should be mentioned prominently in terms of use or something.
>
> That aside, I wish you and other members all the best over in the 
> discourse forum.  You've put together a nice list of benefits, so totally 
> makes sense why members have flocked over to that forum.
>
> Me, I'll pop in once in a blue moon, but I will  stay over here in the GG 
> forum because this one is much more accommodating re cognitive disability 
> challenges.
>
>
>
> On Friday, September 17, 2021 at 10:16:20 PM UTC-3 TW Tones wrote:
>
>> Oh,  and you can edit to correct your post :)
>>
>> I have *just run across the road and discovered that side is much 
>> greener* :) 
>>
>> On Saturday, 18 September 2021 at 11:12:42 UTC+10 TW Tones wrote:
>>
>>> Folks,
>>>
>>> As you may know I am a regular contributor to the community. I just want 
>>> to let you know although I will always support the use of Google Groups, *I 
>>> am now only an occasional visitor here.* Without entering into the 
>>> detailed evaluations and comparisons these are *my reasons why*;
>>>
>>>- Discourse fixed a number of problems introduced to Google Groups 
>>>of late eg code highlighting.
>>>- Discourse has all the standard features of most of the advance 
>>>community tools.
>>>- It can almost resemble a chat if more than one person is on line.
>>>- I do not use any email features only online.
>>>- Its easier to keep track of what I have done or when others post 
>>>and reply
>>>- Its nice to use emoticon reactions rather than a whole (email) 
>>>reply to indicate support, or thank someone.
>>>- *I can deal with a larger volume of activity in the same time*
>>>- Private messaging without using email is possible (off line 
>>>discussions)
>>>- I can support new users to Discourse, as I certainly want us to 
>>>move, so of course I support it.
>>>- Given the way users have being treated by google eg; destroyed 
>>>mobile view I no longer trust Google Groups in the long term.
>>>
>>> There are too many features to name here that I appreciate in Discourse, 
>>> but most are reusable skills, because they are available in many other 
>>> community solutions, but not in Google Groups, which after all is a 
>>> glorified mail list.
>>>
>>> I did not choose Discourse, but because it has gained some momentum and 
>>> is more than adequate if not very good *"I just want to leave".* I 
>>> tried to encourage a move many times, but most communities are like herding 
>>> cats, but now in the case of Discourse its more like "herding sheep" and a 
>>> pile of us sheeple, have *just run across the road and discovered than 
>>> side is much greener* :) 
>>>
>>> I understand there are community members who feel one or more of the 
>>> following;
>>>
>>>- finding the transition difficult, 
>>>- need solutions to help on the new platform
>>>- are not familiar with these sophisticated solutions
>>>- don't like changing something that works for them.
>>>
>>> I urge you to come over and connect with me @TW_Tones 
>>> <https://talk.tiddlywiki.org/u/TW_Tones> I will do all I can to help 
>>> you learn how to use discourse and transition (others will help as well).
>>>
>>> Tones
>>>
>>

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


[tw5] Re: "Loud Tones?" on Discourse discussion: talk.tiddlywiki.org

2021-09-17 Thread TW Tones
Oh,  and you can edit to correct your post :)

I have *just run across the road and discovered that side is much greener*
 :) 

On Saturday, 18 September 2021 at 11:12:42 UTC+10 TW Tones wrote:

> Folks,
>
> As you may know I am a regular contributor to the community. I just want 
> to let you know although I will always support the use of Google Groups, *I 
> am now only an occasional visitor here.* Without entering into the 
> detailed evaluations and comparisons these are *my reasons why*;
>
>- Discourse fixed a number of problems introduced to Google Groups of 
>late eg code highlighting.
>- Discourse has all the standard features of most of the advance 
>community tools.
>- It can almost resemble a chat if more than one person is on line.
>- I do not use any email features only online.
>- Its easier to keep track of what I have done or when others post and 
>reply
>- Its nice to use emoticon reactions rather than a whole (email) reply 
>to indicate support, or thank someone.
>- *I can deal with a larger volume of activity in the same time*
>- Private messaging without using email is possible (off line 
>discussions)
>- I can support new users to Discourse, as I certainly want us to 
>move, so of course I support it.
>- Given the way users have being treated by google eg; destroyed 
>mobile view I no longer trust Google Groups in the long term.
>
> There are too many features to name here that I appreciate in Discourse, 
> but most are reusable skills, because they are available in many other 
> community solutions, but not in Google Groups, which after all is a 
> glorified mail list.
>
> I did not choose Discourse, but because it has gained some momentum and is 
> more than adequate if not very good *"I just want to leave".* I tried to 
> encourage a move many times, but most communities are like herding cats, 
> but now in the case of Discourse its more like "herding sheep" and a pile 
> of us sheeple, have *just run across the road and discovered than side is 
> much greener* :) 
>
> I understand there are community members who feel one or more of the 
> following;
>
>- finding the transition difficult, 
>- need solutions to help on the new platform
>- are not familiar with these sophisticated solutions
>- don't like changing something that works for them.
>
> I urge you to come over and connect with me @TW_Tones 
> <https://talk.tiddlywiki.org/u/TW_Tones> I will do all I can to help you 
> learn how to use discourse and transition (others will help as well).
>
> Tones
>

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


[tw5] "Loud Tones?" on Discourse discussion: talk.tiddlywiki.org

2021-09-17 Thread TW Tones
Folks,

As you may know I am a regular contributor to the community. I just want to 
let you know although I will always support the use of Google Groups, *I am 
now only an occasional visitor here.* Without entering into the detailed 
evaluations and comparisons these are *my reasons why*;

   - Discourse fixed a number of problems introduced to Google Groups of 
   late eg code highlighting.
   - Discourse has all the standard features of most of the advance 
   community tools.
   - It can almost resemble a chat if more than one person is on line.
   - I do not use any email features only online.
   - Its easier to keep track of what I have done or when others post and 
   reply
   - Its nice to use emoticon reactions rather than a whole (email) reply 
   to indicate support, or thank someone.
   - *I can deal with a larger volume of activity in the same time*
   - Private messaging without using email is possible (off line 
   discussions)
   - I can support new users to Discourse, as I certainly want us to move, 
   so of course I support it.
   - Given the way users have being treated by google eg; destroyed mobile 
   view I no longer trust Google Groups in the long term.

There are too many features to name here that I appreciate in Discourse, 
but most are reusable skills, because they are available in many other 
community solutions, but not in Google Groups, which after all is a 
glorified mail list.

I did not choose Discourse, but because it has gained some momentum and is 
more than adequate if not very good *"I just want to leave".* I tried to 
encourage a move many times, but most communities are like herding cats, 
but now in the case of Discourse its more like "herding sheep" and a pile 
of us sheeple, have *just run across the road and discovered than side is 
much greener* :) 

I understand there are community members who feel one or more of the 
following;

   - finding the transition difficult, 
   - need solutions to help on the new platform
   - are not familiar with these sophisticated solutions
   - don't like changing something that works for them.

I urge you to come over and connect with me @TW_Tones 
 I will do all I can to help you 
learn how to use discourse and transition (others will help as well).

Tones

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


[tw5] Re: Automatically generate static website in Node

2021-09-15 Thread TW Tones
Mark,

I would suggest a mechaisium could be built within the single file wiki to 
package only modified static tiddlers for upload to a host as well.

Also many tiddlywiki.html files are smaller than most images, thus a full 
upload not an issue.

I am not contradicting you only pointing out it is possible even if no one 
has done it yet. It is not a "hard limit".

Regards
Tones

On Thursday, 16 September 2021 at 01:56:49 UTC+10 Mark S. wrote:

> One of the advantages of node is that it only needs to write tiddlers that 
> have changed, rather than the entire TW file. If you "published" a TW 
> automatically, you would undermine this feature.
>
> You can create a standalone any time you want just by clicking on the save 
> button and picking the appropriate save option and location.
>
> If you want to do it the other way, push your tiddlers to GitHub and then 
> automatically publish a page to GH pages, then Saq has a clever technique 
> for you to use:
>
> https://github.com/saqimtiaz/TW5-github-actions-example
>
> On Tuesday, September 14, 2021 at 10:35:59 AM UTC-7 rikagol...@gmail.com 
> wrote:
>
>> Hi All!
>>
>> I am using NodeJS right now to auto save Tiddlers. I love it!
>>
>> I expected that a static website (index.html) would get built 
>> automatically on save, but that's not happening. What's an easy way to 
>> automatically build a static website on each autosave? (I'm thinking ahead 
>> to when I will host my site on Github). 
>>
>> 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/60c2a2a1-50e4-40b9-9cfe-5f03df7a4357n%40googlegroups.com.


[tw5] Re: TiddlyWiki "Trail Mix" video: Startup Actions + other little things

2021-09-12 Thread TW Tones
CJ,

Love your video and how it will empower new users with some features of 
value. 

You have a good voice for calm instruction but not monotonous. Do continue 
with your videos.

Regards
Tones
On Sunday, 12 September 2021 at 08:06:28 UTC+10 cj.v...@gmail.com wrote:

> *(Related tiddlers in attached JSON.  Download and drag/drop into some 
> TiddlyWiki for import.)*
>
> https://www.youtube.com/watch?v=3QykVmZoemg
>

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


[tw5] Re: Increase width of the sidebar

2021-09-07 Thread TW Tones
Well, 

To be clear it answers the original request. It allows you to change the 
sidebar width. Be it increase or reduce.

Even if you do not use the tool by looking inside it you can see what it 
changes. And make this change manually.

Tones
On Tuesday, 7 September 2021 at 18:33:39 UTC+10 heusmich wrote:

> OK, thanks for the tool, I tried it but I think I don´t need it.
>
> strikke...@gmail.com schrieb am Dienstag, 7. September 2021 um 10:01:56 
> UTC+2:
>
>> You can download the link from TW Tones - go to tiddlywiki.com , import 
>> it. Then you can see how it works and if you like it.
>>
>> In short you get a new page control - not shown - but you can select in 
>> from the sidebar Tools tab. Clicking that button opens a modal to select 
>> the necessary values. That is good for easy experimentation until you find 
>> the right solution for you.
>> On Tuesday, September 7, 2021 at 9:23:37 AM UTC+2 heusmich wrote:
>>
>>> Before I install it, what exactly does it do?
>>>
>>> TW Tones schrieb am Dienstag, 7. September 2021 um 01:52:54 UTC+2:
>>>
>>>> I made this tool for interactive sidebar width
>>>>
>>>> see attached
>>>>
>>>> On Tuesday, 7 September 2021 at 07:10:31 UTC+10 heusmich wrote:
>>>>
>>>>> Yes, this is working.
>>>>> Thx!
>>>>> :D
>>>>>
>>>>> strikke...@gmail.com schrieb am Montag, 6. September 2021 um 23:00:39 
>>>>> UTC+2:
>>>>>
>>>>>> Fluid story, fixed sidebar - then go to the bottom - to sidebar width 
>>>>>> - enter what you want for the sidebar, and the rest will be used for 
>>>>>> story. 
>>>>>> If that does not work for you - I really do not know.
>>>>>>
>>>>>> On Monday, September 6, 2021 at 10:45:45 PM UTC+2 heusmich wrote:
>>>>>>
>>>>>>> Normally I use fluid story, fixed sidebar. But then six seventh of 
>>>>>>> my screen are used for the story and one seventh is used for the 
>>>>>>> sidebar.
>>>>>>> When I change it to fixed story, fluid sidebar, then three fourth of 
>>>>>>> the screen are used for the sidebar and only one fourth for the story.
>>>>>>> All the settings for "Story right", "Story width" and so on stay the 
>>>>>>> same.
>>>>>>> It would be nice if I could manually change the width of the sidebar 
>>>>>>> and then the rest of the screen will automatically be used for the 
>>>>>>> story, 
>>>>>>> or vice versa.
>>>>>>>
>>>>>>> strikke...@gmail.com schrieb am Montag, 6. September 2021 um 
>>>>>>> 22:21:46 UTC+2:
>>>>>>>
>>>>>>>> You found the right place. In Theme Tweaks Options, what are your 
>>>>>>>> setting - for Sidebar layout. Check that it is fixed story, fluid 
>>>>>>>> sidebar. 
>>>>>>>> Then see if your setting change. If it does not work. Do you have any 
>>>>>>>> stylesheets installed - that could have effect on the sidebar width.
>>>>>>>>
>>>>>>>> On Monday, September 6, 2021 at 9:40:04 PM UTC+2 heusmich wrote:
>>>>>>>>
>>>>>>>>> Hi @all,
>>>>>>>>>
>>>>>>>>> Is it somehow possible to increase the width of the sidebar?
>>>>>>>>> Meanwhile I have a lot of tiddlers and sub-tiddlers, that I often 
>>>>>>>>> have to scroll to the right to see the tiddlers when navigating in my 
>>>>>>>>> sidebar.
>>>>>>>>> Under Control Panel > Appearance > Theme Tweeks I can find some 
>>>>>>>>> settings, but they don´t seem to change anything.
>>>>>>>>> So if possible I would double the width of the sidebar, then it 
>>>>>>>>> would be much better for me.
>>>>>>>>>
>>>>>>>>> Best regards
>>>>>>>>>
>>>>>>>>

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


[tw5] Re: Increase width of the sidebar

2021-09-06 Thread TW Tones
I made this tool for interactive sidebar width

see attached

On Tuesday, 7 September 2021 at 07:10:31 UTC+10 heusmich wrote:

> Yes, this is working.
> Thx!
> :D
>
> strikke...@gmail.com schrieb am Montag, 6. September 2021 um 23:00:39 
> UTC+2:
>
>> Fluid story, fixed sidebar - then go to the bottom - to sidebar width - 
>> enter what you want for the sidebar, and the rest will be used for story. 
>> If that does not work for you - I really do not know.
>>
>> On Monday, September 6, 2021 at 10:45:45 PM UTC+2 heusmich wrote:
>>
>>> Normally I use fluid story, fixed sidebar. But then six seventh of my 
>>> screen are used for the story and one seventh is used for the sidebar.
>>> When I change it to fixed story, fluid sidebar, then three fourth of the 
>>> screen are used for the sidebar and only one fourth for the story.
>>> All the settings for "Story right", "Story width" and so on stay the 
>>> same.
>>> It would be nice if I could manually change the width of the sidebar and 
>>> then the rest of the screen will automatically be used for the story, or 
>>> vice versa.
>>>
>>> strikke...@gmail.com schrieb am Montag, 6. September 2021 um 22:21:46 
>>> UTC+2:
>>>
 You found the right place. In Theme Tweaks Options, what are your 
 setting - for Sidebar layout. Check that it is fixed story, fluid sidebar. 
 Then see if your setting change. If it does not work. Do you have any 
 stylesheets installed - that could have effect on the sidebar width.

 On Monday, September 6, 2021 at 9:40:04 PM UTC+2 heusmich wrote:

> Hi @all,
>
> Is it somehow possible to increase the width of the sidebar?
> Meanwhile I have a lot of tiddlers and sub-tiddlers, that I often have 
> to scroll to the right to see the tiddlers when navigating in my sidebar.
> Under Control Panel > Appearance > Theme Tweeks I can find some 
> settings, but they don´t seem to change anything.
> So if possible I would double the width of the sidebar, then it would 
> be much better for me.
>
> Best regards
>


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


sideBar-width.json
Description: application/json


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

2021-09-06 Thread TW Tones
On Talk.tiddlywiki.com I would mention Mario and Charlie here. 

Mario I would like to support part of what Charlie seems to be concerned 
with. I have a few wikis where I have delete inhibit on selected tiddlers, 
typically the master tiddler that is a compound tiddler, meaning it has 
many subtiddlers. Deleting that would result in loss. I have the real 
delete button behind more, so I can get to it. I also have edit inhibit 
because I rarely change the master tiddler but want to edit the 
subtiddlers. A conditional edit button simply helps stop me clicking on the 
wrong edit button. All this can be circumvented, but it helps improve the 
user Interface by avoiding the display of buttons that are not relevant and 
could initiate actions that cause a waste of time if not damage.

Tones


On Monday, 6 September 2021 at 19:07:42 UTC+10 PMario wrote:

> On Monday, September 6, 2021 at 3:01:25 AM UTC+2 cj.v...@gmail.com wrote:
>
> No worries.  I'll train my thoughts on obfuscation, risk-mitigation 
>> design/strategies, and automated monitoring/repairing processes.
>>
>
> IMO obfuscation is wasting time, other than removing the buttons, that are 
> not needed. Which I would define as "modifying the UI according to the 
> usecase" ;)
>
> With nodejs you should be able to establish a "batch process" that runs 
> once a day and checks, if some important shadow tiddlers have been 
> overwritten. I would consider this as "Plan B".
>
> Plan A - IMO the easiest way would be to trust your users and tell them 
> what's going on, and what's important. Having Plan B will then only be 
> needed if someone changes something by accident. 
>
> just a thought
> mario
>
>

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


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

2021-09-06 Thread TW Tones
Charlie,

*My problem is about preventing tiddlers from being overwritten by an 
import or by a new tiddler getting created and saved with a name of a 
tiddler that already exists.  That's not solved.*

But in my earlier reply, I think we can solve this issue by moving the 
"readonly" tiddlers to a plugin where they become shadow tiddlers. 
Effectively thus protected tiddlers, Unless the plugin is deleted they will 
always be there "in the shadows", it would then be simple to detect any 
edited tiddlers and delete the update reverting to the shadow. Keep in mind 
the shadow tiddlers can be any name not just system tiddlers.

I can pursue this for you if you want?

I would make;

   - An easy way to move a selected tiddler into the safety of a plugin, 
   making it a "protected tiddler".
   - Provide away to detect edited "protected tiddlers" and restore them 
   automatically.

Regards
Tones

On Monday, 6 September 2021 at 15:54:13 UTC+10 cj.v...@gmail.com wrote:

> Well, "Tiddly Locking" isn't a solution to my problem in this thread.
>
> My problem is about preventing tiddlers from being overwritten by an 
> import or by a new tiddler getting created and saved with a name of a 
> tiddler that already exists.  That's not solved.
>
> Tiddly Locking is great, is something I use, but has nothing to do with 
> this thread.
>
> On Monday, September 6, 2021 at 2:34:45 AM UTC-3 TW Tones wrote:
>
>> Charlie,
>>
>> Good to hear. Since you question was answered with "Tiddly locking" could 
>> you point to that as a solution for future readers in this thread ?
>>
>> Tones
>>
>> On Monday, 6 September 2021 at 15:15:49 UTC+10 cj.v...@gmail.com wrote:
>>
>>> G'day Tones,
>>>
>>> I've got editing and delete of important tiddlers blocked via tiddler 
>>> locking.  That's easy and good.
>>>
>>> The only thing I have to handle, even if 99% unlikely, is certain 
>>> tiddlers getting overwritten by any tech-savvy (well, TiddlyWiki-savvy) 
>>> individual.
>>>
>>> Since that can't really be prevented, then a scheduled process to 
>>> compare files should be pretty easy (for all of these TiddlyWiki instances 
>>> on node.js)  Just a matter of comparing "end-user" tiddlers to 
>>> "architecture/infrastructure/farm/admin/etc .) tiddlers, and having the 
>>> process delete anything that shouldn't exist in end-users' tiddler folders.
>>>
>>> Maybe another little process to raise the redflag as soon as there's a 
>>> blip.
>>>
>>> I am avoiding plugins and staying pure node.js and tiddlywiki for as 
>>> much as I can, an exercise to really get a good feel for how TiddlyWiki 
>>> works on node.js.  For the near future.
>>>
>>> All of these goodies you mention in my back-pocket for now.  Thanks !
>>> On Monday, September 6, 2021 at 1:03:27 AM UTC-3 TW Tones wrote:
>>>
>>>> Charlie,
>>>>
>>>> A few ideas;
>>>>
>>>> One way would be to stash a copy away, perhaps inside a JSON tiddler,  
>>>> similar to Mohammad's trash plugin but just on editing. This kind of 
>>>> solution can intercept User interface edit/delete however batch processes 
>>>> can by pass this. 
>>>>
>>>> Some solutions like noteself to keep all versions, so you could restore 
>>>> from there, after running an automated are tiddlers missing check, perhaps 
>>>> before saving.
>>>>
>>>> You could also modify the delete button to refuse to delete if a 
>>>> tiddler contains a field delete-inhibit=yes or just exists. I have already 
>>>> made an alternate edit button which honors edit-inhibit and just hide the 
>>>> original edit behind the more button. On some wikis we may want to hide 
>>>> the 
>>>> more button so they can not access (directly) the buttons we do not want 
>>>> them to use and only provide them alternatives, we want them to use. When 
>>>> the cant edit or delete you can actually just hide that alternative button.
>>>>
>>>> Another is to take a set of tiddlers, and move them into a plugin, 
>>>> delete the tiddler version. They then become shadows, and if edited you 
>>>> simply delete the tiddler to return to the shadow copy. The only way to 
>>>> delete the shadows is to delete the plugin itself, so the user needs to 
>>>> undertake additional steps. This can avoid batch processes deleting the 
>>>> tiddlers.
>>>>
>>>>

[tw5] Re: More playing around with TiddlyWiki on node.js: the makings of a distributed database

2021-09-05 Thread TW Tones
Thanks for sharing your solution to the community.

On Monday, 6 September 2021 at 15:42:25 UTC+10 cj.v...@gmail.com wrote:

> G'day Tones,
>
> Nah, in this scenario I've dreamed up (to really get to know TiddlyWiki on 
> node.js), I'm sticking to a minimalist approach and not adding any plugins 
> or extras, pushing as far as I can with just TiddlyWiki and a little bit of 
> help via symlinks.
>
> In this scenario, each sales rep has access to just his/her TiddlyWiki, 
> private yet having shareable bits.  Distributed data, with clear ownership 
> of data (of customer files).
>
> Each sales rep deals with only one TiddlyWiki, and no futzing about with 
> drag and drop of tiddlers from one wiki to another.
>
> No multi-user TiddlyWikis, no sharing of tiddlers except for view-only 
> tiddlers that have lists of customers.
>
> Ultimately, users will have no clue they are using TiddlyWiki.  It will 
> feel and look just like any database application.
>
> At the moment, still looks like TiddlyWiki as I iron out the overall 
> architecture first.  It is looking pretty cool so far.  
>
> So far includes (short list):
>
>- Architecture/Framework/System TiddlyWiki
>   - Including edited Tiddler "Save" and "Delete" to do extra actions 
>   upon save and delete of tiddlers tagged customer
>   - Tiddler Locking mechanism to prevent editing/deletion of tiddlers 
>   from this TiddlyWiki
>- "Big DB" TiddlyWiki
>   - This TiddlyWiki has nothing but symlinks to each of the customer 
>   list JSON tiddlers for each SalesRep TiddlyWiki
>   - By including this TiddlyWiki, each of the Sales Rep TiddlyWikis 
>   gets the aggregated list of all customers from all sales reps
>- Individual Sales Rep TiddlyWikis
>   - These include the first two TiddlyWikis
>   - Every time a new customer gets added/edited/deleted or loses the 
>   "customer" tag, that sales rep's customer list JSON gets updated
>
> Yeah, pretty cool setup for a shoe-string budget scenario.
>
> All happily running on my Chromebook.  Gets my geek mojo going something 
> silly.
> On Monday, September 6, 2021 at 1:11:27 AM UTC-3 TW Tones wrote:
>
>> Charlie,
>>
>> Have you considered creating a third node Wiki "Customer List", using bob 
>> so more than one user can access it at a time?
>>
>> Then both Sales Reps wikis can have this  "Customer List" in a tiddler 
>> with and an iframe to the customer list and freely drag "customer" tiddlers 
>> to and from the customer list. If you provision, "add new customers" only 
>> in the customer list, then it will always be used for new customers and 
>> remain the primary "source of truth". From which all sales reps obtain the 
>> customer details.
>>
>> Regards
>> Tones
>>
>> On Sunday, 5 September 2021 at 07:07:55 UTC+10 cj.v...@gmail.com wrote:
>>
>>> Oops, errata:
>>>
>>> The other sales rep (say Sales Rep 2) has a file in the tiddlers folder 
>>> that is a symlink to the "Sales Rep 1 Customer List."  So that sales rep 
>>> has his/her own view-only "Sales Rep 2 Customer List" that gets updated 
>>> (automatically and behind the scenes) upon new/edit/delete of customer 
>>> tiddlers, and also has view access to "Sales Rep *1* *(not 2)* Customer 
>>> List".
>>>
>>> On Saturday, September 4, 2021 at 5:53:52 PM UTC-3 Charlie Veniot wrote:
>>>
>>>> Say I have two sales reps, each with his/her own private TiddlyWiki on 
>>>> node.js.
>>>>
>>>> Neither sales rep has access of any kind to the other sales rep's 
>>>> TiddlyWiki.
>>>>
>>>> However, each sales rep does have view access to one tiddler from the 
>>>> other sales rep's TiddlyWiki: other sales rep's list of customers.
>>>>
>>>> When a sales rep saves a new customer tiddler, the save process updates 
>>>> (behind the scenes and upon any new/edit/delete of a customer) that sales 
>>>> rep's customer list tiddler (say "Sales Rep 1 Customer List"), a view-only 
>>>> json data tiddler, with each index being kind of like a 
>>>> comma-separated-value record for a customer.
>>>>
>>>> The other sales rep (say Sales Rep 2) has a file in the tiddlers folder 
>>>> that is a symlink to the "Sales Rep 1 Customer List."  So that sales rep 
>>>> has his/her own view-only "Sales Rep 2 Customer List" that gets updated 
>>&g

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

2021-09-05 Thread TW Tones
Charlie,

Good to hear. Since you question was answered with "Tiddly locking" could 
you point to that as a solution for future readers in this thread ?

Tones

On Monday, 6 September 2021 at 15:15:49 UTC+10 cj.v...@gmail.com wrote:

> G'day Tones,
>
> I've got editing and delete of important tiddlers blocked via tiddler 
> locking.  That's easy and good.
>
> The only thing I have to handle, even if 99% unlikely, is certain tiddlers 
> getting overwritten by any tech-savvy (well, TiddlyWiki-savvy) individual.
>
> Since that can't really be prevented, then a scheduled process to compare 
> files should be pretty easy (for all of these TiddlyWiki instances on 
> node.js)  Just a matter of comparing "end-user" tiddlers to 
> "architecture/infrastructure/farm/admin/etc .) tiddlers, and having the 
> process delete anything that shouldn't exist in end-users' tiddler folders.
>
> Maybe another little process to raise the redflag as soon as there's a 
> blip.
>
> I am avoiding plugins and staying pure node.js and tiddlywiki for as much 
> as I can, an exercise to really get a good feel for how TiddlyWiki works on 
> node.js.  For the near future.
>
> All of these goodies you mention in my back-pocket for now.  Thanks !
> On Monday, September 6, 2021 at 1:03:27 AM UTC-3 TW Tones wrote:
>
>> Charlie,
>>
>> A few ideas;
>>
>> One way would be to stash a copy away, perhaps inside a JSON tiddler,  
>> similar to Mohammad's trash plugin but just on editing. This kind of 
>> solution can intercept User interface edit/delete however batch processes 
>> can by pass this. 
>>
>> Some solutions like noteself to keep all versions, so you could restore 
>> from there, after running an automated are tiddlers missing check, perhaps 
>> before saving.
>>
>> You could also modify the delete button to refuse to delete if a tiddler 
>> contains a field delete-inhibit=yes or just exists. I have already made an 
>> alternate edit button which honors edit-inhibit and just hide the original 
>> edit behind the more button. On some wikis we may want to hide the more 
>> button so they can not access (directly) the buttons we do not want them to 
>> use and only provide them alternatives, we want them to use. When the cant 
>> edit or delete you can actually just hide that alternative button.
>>
>> Another is to take a set of tiddlers, and move them into a plugin, delete 
>> the tiddler version. They then become shadows, and if edited you simply 
>> delete the tiddler to return to the shadow copy. The only way to delete the 
>> shadows is to delete the plugin itself, so the user needs to undertake 
>> additional steps. This can avoid batch processes deleting the tiddlers.
>>
>> I have felt that for some time introducing delete-inhibit and 
>> edit-inhibit fields/flags on at least some tiddlers would be a helpful 
>> option. For example the plugin mentioned in the last paragraph.
>>
>> I am yet to work out how but I believe the new eventCatcher widget or the 
>> existing LinkCatcherWidget or ActionConfirmWidget can help here.
>>
>> One idea would be trapping using the action confirm widget on the delete 
>> step, and on confirmation make a backup copy of the tiddler.
>>
>> Tones
>>
>> On Monday, 6 September 2021 at 11:01:25 UTC+10 cj.v...@gmail.com wrote:
>>
>>> Trying to achieve a robust architecture for a farm of node.js 
>>> TiddlyWikis that together form a distributed database, with end-user level 
>>> (and private) TiddlyWikis that have certain types of tiddlers that are 
>>> automagically shared (and the rest private), and system-level TiddlyWikis 
>>> that tie all of the architecture together along with user-interface stuff, 
>>> etc. etc. etc.
>>>
>>> Sure, not very likely end-user folk could muck things up, but a robust 
>>> system really should never allow an end-user to break their TiddlyWiki (in 
>>> this farm idea of mine) by somehow replacing any key component tiddler.
>>>
>>> No worries.  I'll train my thoughts on obfuscation, risk-mitigation 
>>> design/strategies, and automated monitoring/repairing processes.
>>>
>>> All part of a big idea that ties together, in part:
>>>
>>>- A brewing idea: TiddlyWiki on node.js: check for changes 
>>><https://groups.google.com/g/tiddlywiki/c/GMagvXTOxLI/m/POV20R69AwAJ>
>>>- More playing around with TiddlyWiki on node.js: the makings of a 
>>>distributed database 
>>><https://groups.google.com/g/tiddlywiki/c/OuYwkSgPBDo/m/egsk9fho

[tw5] Re: More playing around with TiddlyWiki on node.js: the makings of a distributed database

2021-09-05 Thread TW Tones
Charlie,

Have you considered creating a third node Wiki "Customer List", using bob 
so more than one user can access it at a time?

Then both Sales Reps wikis can have this  "Customer List" in a tiddler with 
and an iframe to the customer list and freely drag "customer" tiddlers to 
and from the customer list. If you provision, "add new customers" only in 
the customer list, then it will always be used for new customers and remain 
the primary "source of truth". From which all sales reps obtain the 
customer details.

Regards
Tones

On Sunday, 5 September 2021 at 07:07:55 UTC+10 cj.v...@gmail.com wrote:

> Oops, errata:
>
> The other sales rep (say Sales Rep 2) has a file in the tiddlers folder 
> that is a symlink to the "Sales Rep 1 Customer List."  So that sales rep 
> has his/her own view-only "Sales Rep 2 Customer List" that gets updated 
> (automatically and behind the scenes) upon new/edit/delete of customer 
> tiddlers, and also has view access to "Sales Rep *1* *(not 2)* Customer 
> List".
>
> On Saturday, September 4, 2021 at 5:53:52 PM UTC-3 Charlie Veniot wrote:
>
>> Say I have two sales reps, each with his/her own private TiddlyWiki on 
>> node.js.
>>
>> Neither sales rep has access of any kind to the other sales rep's 
>> TiddlyWiki.
>>
>> However, each sales rep does have view access to one tiddler from the 
>> other sales rep's TiddlyWiki: other sales rep's list of customers.
>>
>> When a sales rep saves a new customer tiddler, the save process updates 
>> (behind the scenes and upon any new/edit/delete of a customer) that sales 
>> rep's customer list tiddler (say "Sales Rep 1 Customer List"), a view-only 
>> json data tiddler, with each index being kind of like a 
>> comma-separated-value record for a customer.
>>
>> The other sales rep (say Sales Rep 2) has a file in the tiddlers folder 
>> that is a symlink to the "Sales Rep 1 Customer List."  So that sales rep 
>> has his/her own view-only "Sales Rep 2 Customer List" that gets updated 
>> (automatically and behind the scenes) upon new/edit/delete of customer 
>> tiddlers, and also has view access to "Sales Rep 2 Customer List".
>>
>> So each sales rep has access to their own customer tiddlers, but also has 
>> access to his/her own customer list + the other sales rep's customer list, 
>> which can then be merged into a consolidated customer list.
>>
>> Essentially, each private TiddlyWiki on node.js, hosts CSV-like json data 
>> tiddlers, and those data tiddlers are made shareable via symlinks, and all 
>> of the data tiddlers become components of a distributed database for 
>> querying/reporting/whatever.
>>
>> Just throwing that out there in case anybody else geeks out on, as much 
>> as I do, this kind of architectural experimentation.
>>
>

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


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

2021-09-05 Thread TW Tones
Charlie,

A few ideas;

One way would be to stash a copy away, perhaps inside a JSON tiddler,  
similar to Mohammad's trash plugin but just on editing. This kind of 
solution can intercept User interface edit/delete however batch processes 
can by pass this. 

Some solutions like noteself to keep all versions, so you could restore 
from there, after running an automated are tiddlers missing check, perhaps 
before saving.

You could also modify the delete button to refuse to delete if a tiddler 
contains a field delete-inhibit=yes or just exists. I have already made an 
alternate edit button which honors edit-inhibit and just hide the original 
edit behind the more button. On some wikis we may want to hide the more 
button so they can not access (directly) the buttons we do not want them to 
use and only provide them alternatives, we want them to use. When the cant 
edit or delete you can actually just hide that alternative button.

Another is to take a set of tiddlers, and move them into a plugin, delete 
the tiddler version. They then become shadows, and if edited you simply 
delete the tiddler to return to the shadow copy. The only way to delete the 
shadows is to delete the plugin itself, so the user needs to undertake 
additional steps. This can avoid batch processes deleting the tiddlers.

I have felt that for some time introducing delete-inhibit and edit-inhibit 
fields/flags on at least some tiddlers would be a helpful option. For 
example the plugin mentioned in the last paragraph.

I am yet to work out how but I believe the new eventCatcher widget or the 
existing LinkCatcherWidget or ActionConfirmWidget can help here.

One idea would be trapping using the action confirm widget on the delete 
step, and on confirmation make a backup copy of the tiddler.

Tones

On Monday, 6 September 2021 at 11:01:25 UTC+10 cj.v...@gmail.com wrote:

> Trying to achieve a robust architecture for a farm of node.js TiddlyWikis 
> that together form a distributed database, with end-user level (and 
> private) TiddlyWikis that have certain types of tiddlers that are 
> automagically shared (and the rest private), and system-level TiddlyWikis 
> that tie all of the architecture together along with user-interface stuff, 
> etc. etc. etc.
>
> Sure, not very likely end-user folk could muck things up, but a robust 
> system really should never allow an end-user to break their TiddlyWiki (in 
> this farm idea of mine) by somehow replacing any key component tiddler.
>
> No worries.  I'll train my thoughts on obfuscation, risk-mitigation 
> design/strategies, and automated monitoring/repairing processes.
>
> All part of a big idea that ties together, in part:
>
>- A brewing idea: TiddlyWiki on node.js: check for changes 
>
>- More playing around with TiddlyWiki on node.js: the makings of a 
>distributed database 
>
>
> On Sunday, September 5, 2021 at 8:18:19 PM UTC-3 PMario wrote:
>
>> On Sunday, September 5, 2021 at 8:36:26 PM UTC+2 cj.v...@gmail.com wrote:
>> ...
>>
>>> Is there an easy way to protect such a tiddler?
>>>
>>
>> No. In TW you can overwrite every core tiddler if you like. So there is 
>> no way to write-protect a tiddler. 
>> What do you want to achieve?
>> -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/c5073b5f-d0b0-452b-8cbe-87ad12020d52n%40googlegroups.com.


[tw5] Re: implementing external image path in shiraz image-card macro?

2021-09-01 Thread TW Tones
As soon as you want to pass something to a macro that is not in a value 
format you can use the macrocall widget, even on your own macros

<$macrocall $name="image-card" img=<>  width="" 
align:"left" caption="" title="" text="" footer="" pos="top" alt=""/>

But you man not even need to pass the nul values 

<$macrocall $name="image-card" img=<>  width="" 
align:"left" pos="top"/>

Tony 
fellow Aussie 
see https://www.meetup.com/sydney-twig-tiddlywiki-interest-group/
On Wednesday, 1 September 2021 at 20:51:12 UTC+10 rwi...@museum.vic.gov.au 
wrote:

> Hi all
>
> I have been using the very handy ximg macro of Tobias Beer [
> http://tobibeer.github.io/tb5/#External%20Image%20Path]  to provide a URL 
> where my images live.  Works great, except that I now wish to use  the 
> image-card macro from the shiraz plugin for more options to display 
> images.  According to https://tiddlywiki.com/#MacroCallWidget :  
> Macro parameters are specified as widget attributes, thus allowing 
> indirection via {{title!!field}}, <> or {{{filter}}}
>
> so i have tried including <> within the standard 
> syntax  
> < title:"" text:"" footer:"" pos:"top" alt:"">> 
>
> to get
>
> <>"  width:"" align:"left" 
> caption:"" title:"" text:"" footer:"" pos:"top" alt:"">>
>
> but having tried various modifications I now surmise that nesting 
> MacroCallWidgets is not allowed.  Nor could I find this addressed in the 
> group archives
>
> No doubt the solution is dead simple but not for beginners like me.  I'd 
> be grateful for help
>
> very many thanks, Robin
>
> [I would have posted this to the new Talk Tiddlywiki discourse but I'm 
> _still_ waiting for my confirmation email to complete registration]
>
>
>
>
>

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


[tw5] Re: [FUN Fact] How many conversations in this group has NO Title?

2021-09-01 Thread TW Tones
I expect is is the result of the Author deleting the lead post in some 
cases.

On Monday, 30 August 2021 at 23:28:36 UTC+10 taace...@gmail.com wrote:

> After processing more than 10,000 conversation (out of 25K) and more that 
> 90,000 messages (out of 190K) , we found the following 3:-
>
> https://groups.google.com/g/tiddlywiki/c/OyT4boK4_QQ,
> https://groups.google.com/g/tiddlywiki/c/r9l2XcYGhIU,
> https://groups.google.com/g/tiddlywiki/c/kgX6GV32jKA
>
> P.S. : this is a part of the TiddlyWiki Projects (25K & Goodfellas)  The 
> History Show of the GG Community 
> 
>
> Regards
> Taacees
>

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


[tw5] Re: How to make the web bookmark like notion?

2021-08-31 Thread TW Tones
imleg,

If I follow the links to https://github.com/akhater/TiddlyWiki-EasyBookmark 
it suggests you need to key an API key, did you?

There is talk of something similar in discourse (Reference unavailable), 
other words may be "preview"

Tones

On Tuesday, 31 August 2021 at 20:23:56 UTC+10 imleg...@gmail.com wrote:

> What insert the url link into the tiddler, and the url will become a small 
> preview of the web site just like the notion web bookmark. How to make it? 
>
> https://github.com/akhater/TiddlyWiki-EasyBookmark
>
> I found this link. But after I follow the step noting happens.
>
>
>

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


[tw5] Re: TiddlyWiki discussion forum: a thought about choice of forum

2021-08-31 Thread TW Tones
Cj,

I think something like this would be a good idea. Perhaps something 
discussed in Discourse that creates Discourse posts from a tiddler could be 
setup in a dedicated category for this, and with the first post being a 
Wiki type post so we can accrue documentation and examples over time. With 
the thread itself a permanent conversation about that documentation tiddler.

Tones

On Wednesday, 1 September 2021 at 00:40:38 UTC+10 cj.v...@gmail.com wrote:

> With all the talk about TiddlyTalk and longterm discussions about Google 
> Drive, I just had this thought.
>
> It would be pretty cool if documentation Tiddlers at TiddlyWiki.com (or 
> wherever) could have, in the footers of those tiddlers, embedded iFrame of 
> related discussion topics from the forum showing "right there."
>
> So if, for example, I'm looking at the "addprefix Operator", I could see 
> possibly relevant discussions about that in the forum, right there (at my 
> fingertips) as part of documentation related to that filter operator.
>
> I suppose things could be curated somehow.  Maybe discussion threads could 
> be tagged such that relevant discussions would show for a particular 
> tiddler.  So only threads with the "addprefix" tag would show for that 
> tiddler, with maybe a check box that, when checked, gets any discussion 
> with the word "addprefix" anywhere in the discussion.
>
> Yeah, I dream fully integrated, intertwined, intermingled, intertwingled.
>
> I've only played around a little bit with this concept in Google Sites, 
> embedding Google Group instances in various Google Site pages to view 
> discussion related to a particular page's topic.
>

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


[tw5] Re: Highlighting duplicates in lists

2021-08-30 Thread TW Tones
Mohamad,

Sorry, I did not mean to imply you were not putting in the effort, more 
that you needed to direct it elsewhere first.

Although it is great to see you are keen and jumping into it, it can just 
make it a little hard to support you. Don't be shy to keep asking, but 
trust in your ability to learn yourself as well.

Tones

On Tuesday, 31 August 2021 at 07:42:21 UTC+10 mohamed...@hotmail.com wrote:

> Thanks tones 
>
> actually my problem is not lack of effort but  rather lack of knowledge  
> :( , i try many different things before coming back, its just like you said 
> i am guilty of trying to plug in the code rather than fully understanding it
>
> well then ..i guess its time for me to up my game with the filter syntax 
> first  before attempting anything else
>
> i guess for now the thread can be closed, but thanks again for you help :)
>
>
>
> On Monday, August 30, 2021 at 2:25:28 AM UTC+2 TW Tones wrote:
>
>> Mohamad,
>>
>> Part of the issue here is you have not yet learned the basic syntax of 
>> tiddlywiki yet, we all start somewhere, my instructions should have being 
>> self evident if you had just rudimentary tiddlywiki syntax, all of which I 
>> learned from TiddlyWiki.com 
>>
>> I did answer this latest question here 
>> <https://groups.google.com/g/TiddlyWiki/c/ahbcnXqVgl8/m/zoVC1ppaAQAJ> and 
>> you can put *{{{ [all[current]get[date-field]format:date[]] }}} *where 
>> you read *this is displayed inside the list*
>>
>> I am happy still to help, but you force me to revisit the whole thread 
>> again. I am not sure that when I gave previous answers, you tried to 
>> understand what I shared with you, it seems more like you just tried to 
>> "plugin my answers" to your code without trying to work it out. I may be 
>> wrong but please try a little harder to work through the carefully 
>> considered answers you get.
>>
>> Tones
>>
>> On Sunday, 29 August 2021 at 12:38:56 UTC+10 mohamed...@hotmail.com 
>> wrote:
>>
>>> thanks tones,
>>>
>>> back one step , the original code was ..
>>>
>>>   matchthen[color: 
>>> red;]] }}}><>
>>> 
>>>
>>> 
>>> 
>>> the modified code is as follows 
>>>
>>> >> [all[]prefix[New]!titleget[field]match*{!!field}*then[color:
>>>  
>>> red;]] }}}>* this is displayed inside the list* 
>>>
>>> the instruction is to replace 
>>>  *{{!!field}} *
>>> With *{{{ [all[current]get[field]format:date[]] }}}*
>>>
>>> *(change "field" to your date field)*
>>>
>>> making the code
>>>
>>> >> [all[]prefix[New]!titleget[field]match *{{{ 
>>> [all[current]get[field_example]format:date[]] }}} *then[color: red;]] 
>>> }}}> this is displayed inside the list 
>>>
>>> this does not work, prob because i have misinterpreted your instructions
>>>
>>> also there are several things missed out in the modified code , the 
>>> enlist operator, the   variable, is this intentional?
>>>
>>> if the date field is "field_example"  , can you please tell me what the 
>>> full line of code would be ..  
>>>
>>> thanks again
>>> On Saturday, August 28, 2021 at 1:44:23 AM UTC+2 TW Tones wrote:
>>>
>>>> The information you are after is in my earlier post
>>>> *<> {{!!field}} *is the display replace this with *{{{ 
>>>> [all[current]get[field]format:date[]] }}}*
>>>>
>>>> It is what is inside the span that gets coloured using style attribute, 
>>>> thus what is inside the span is what is displayed,
>>>>
>>>> >>> [all[]prefix[New]!titleget[field]match{!!field}then[color: 
>>>> red;]] }}}>* this is displayed inside the list*
>>>>
>>>> So basically we replace the display of  *{{!!field}} *
>>>> With *{{{ [all[current]get[field]format:date[]] }}}*
>>>> (change "field" to your date field)
>>>>
>>>> So the following will be inside the span because you want the title and 
>>>> its date.
>>>> *<> **{{{ [all[current]get[field]format:date[]] }}}*
>>>>
>>>> The format operator requires tiddlywiki 5.1.23 or greater
>>>>
>>>> Tones
>>>> On Saturday, 28 August 2021 at 02:13:48 UTC+10 mohamed...@hotmail.com 
>>>> wrote:
>>>>
>>>>> Hi tones,
>>>>>
>>>>> have 

Re: [tw5] Re: Collapse and expand headings in a tiddler

2021-08-29 Thread TW Tones
Actually the summary tag can contain wiki text.

I have used it to allow editing {{tiddlername||$:/core/ui/Buttons/edit}}

HelloThere 
{{HelloThere||$:/core/ui/Buttons/edit}}

{{HelloThere}}


I also use filtered transclusion to count something and display that in the 
summary so there is not need to open it if there are no cases (=0)
Or wrap the whole thing to optionally display

<$list filter="display condition" variable=nul emptyMessage="No details 
message">
HelloThere 
{{HelloThere||$:/core/ui/Buttons/edit}}

{{HelloThere}}



Regards
Tones
On Monday, 30 August 2021 at 07:56:32 UTC+10 cj.v...@gmail.com wrote:

> Not only can summary be styled, but details can be styled too, as per this 
> snippet from the tiddlers included in that earlier attachment of mine:
>
> <*details* style="background-color:white;border:1px solid lightgray;">
>   <*summary* style="font-size:1.5em;background-color:white;border:1px 
> solid lightgray;">{{!!title}}<$link>*
>
> <$transclude tiddler=<> mode="block"/>
> 
>
> On Sunday, August 29, 2021 at 6:50:24 PM UTC-3 theok...@gmail.com wrote:
>
>> To add to what @David Gifford said I've been tinkering with the details 
>> html element today. They documentation I was reading said it didn't support 
>> any attributes besides open/close.
>>
>> BUT...  I discovered SUMMARY which is used to change it's name DOES.
>>
>> 
>> > style="background-color:green;color:white;font-weight:bold;width:220px;">TESTING
>>  
>> DETAILS STYLES
>>
>> Testing a bunch of testing text. a bunch and more and more and more.
>> 
>>
>> On Sunday, August 29, 2021 at 11:39:51 AM UTC-4 cj.v...@gmail.com wrote:
>>
>>> Hoo Nelly, I'm not an Emacs Org-Mode guy, so that is all gobbledygook to 
>>> me.
>>>
>>> There is a sweet spot for adequate WikiText:
>>>
>>>- complex WikiText formatting markup is bad
>>>- not enough simple WikiText formatting markup is bad
>>>- too much simple WikiText formatting markup is bad
>>>- not enough depends on the person; too much also depends on the 
>>>person
>>>
>>> That can be a drag when one needs some complicated formatting that isn't 
>>> available in WikiText (or whatever markup).
>>>
>>> But having to fall back on HTML/CSS isn't so bad.  With TiddlyWiki, it 
>>> can be plug and play.  Grab somebody else's HTML/CSS, drop it in some 
>>> tiddlers, and forget about it.
>>>
>>> Ideally, any HTML (well, anything particularly complicated/messy) you do 
>>> need can be put in a template tiddler, and then it is just a matter of 
>>> applying that template anywhere you need via the beauty of transclusion and 
>>> then you never need to put your eyeballs on that HTML again.  Well, maybe 
>>> once in a blue moon when really necessary.
>>>
>>> Yeah, I go bananas for transclusion ...
>>>
>>>
>>>
>>>
>>>
>>> On Sunday, August 29, 2021 at 3:17:09 AM UTC-3 Sandip Deshmukh wrote:
>>>
 @Charlie,

 Thanks a lot. The example you showed nearly does what I wanted.

 But to implement it, I will need to do more than write simple wikitext.

 I was looking to solution like Emacs org-mode Visibility Cycling 
 .


 @David

 Thanks a ton!

 Your code snippet came in handy for something else that was bothering 
 me.  And that is solved now.

 But for collapse/ expand headings, it requires additional markup. That 
 would be too cumbersome to implement.



 On 29/08/21 4:24 am, David Gifford wrote:

 Everyone always forgets the simplest solution to this. The HTML details 
 disclosure element.

 Your section header

 {{Your transcluded tiddler}} 

 

 On Saturday, August 28, 2021 at 1:49:15 PM UTC-5 cj.v...@gmail.com 
 wrote:

> BTW, please remember: anything cosmetically disagreeable can be easily 
> adjusted via some quick CSS adjustments. 
>
> For example: different border setup or no borders, background colors, 
> indent of sections within other sections, etc. etc.
>
> That code demo is very rough around the edges, just to prototype a 
> design possibility.
>
> On Saturday, August 28, 2021 at 3:41:45 PM UTC-3 Charlie Veniot wrote:
>
>> Hello, 
>>
>> Just a code sample in case of any use.  It is just me imagining how 
>> I'd create a basic setup to get started.  A little bit rough around the 
>> edges.
>>
>> Download the attached and drag it into https://tiddlywiki.com/ for 
>> importing and checking out.
>>
>> Screenshot below fyi.
>>
>> Cheers!
>>
>> [image: Screenshot 2021-08-28 3.40.35 PM.png]
>>
>>
>>
>> On Saturday, August 28, 2021 at 12:23:22 AM UTC-3 Sandip Deshmukh 
>> wrote:
>>
>>> ReadThisLongManual tiddler carries this:
>>>
>>> ! Heading1
>>>
>>> {{||PartOne}}
>>>
>>> {{||PartTwo}}
>>>
>>> !! Heading 2
>>>
>>> Some text 

[tw5] Re: Highlighting duplicates in lists

2021-08-29 Thread TW Tones
Mohamad,

Part of the issue here is you have not yet learned the basic syntax of 
tiddlywiki yet, we all start somewhere, my instructions should have being 
self evident if you had just rudimentary tiddlywiki syntax, all of which I 
learned from TiddlyWiki.com 

I did answer this latest question here 
<https://groups.google.com/g/TiddlyWiki/c/ahbcnXqVgl8/m/zoVC1ppaAQAJ> and 
you can put *{{{ [all[current]get[date-field]format:date[]] }}} *where you 
read *this is displayed inside the list*

I am happy still to help, but you force me to revisit the whole thread 
again. I am not sure that when I gave previous answers, you tried to 
understand what I shared with you, it seems more like you just tried to 
"plugin my answers" to your code without trying to work it out. I may be 
wrong but please try a little harder to work through the carefully 
considered answers you get.

Tones

On Sunday, 29 August 2021 at 12:38:56 UTC+10 mohamed...@hotmail.com wrote:

> thanks tones,
>
> back one step , the original code was ..
>
>   matchthen[color: 
> red;]] }}}><>
> 
>
> 
> 
> the modified code is as follows 
>
> get[field]match
> *{!!field}*then[color: red;]] }}}>* this is displayed inside the 
> list* 
>
>
> the instruction is to replace 
>  *{{!!field}} *
> With *{{{ [all[current]get[field]format:date[]] }}}*
>
> *(change "field" to your date field)*
>
> making the code
>
> get[field]match 
> *{{{ 
> [all[current]get[field_example]format:date[]] }}} *then[color: red;]] 
> }}}> this is displayed inside the list 
>
> this does not work, prob because i have misinterpreted your instructions
>
> also there are several things missed out in the modified code , the enlist 
> operator, the   variable, is this intentional?
>
> if the date field is "field_example"  , can you please tell me what the 
> full line of code would be ..  
>
> thanks again
> On Saturday, August 28, 2021 at 1:44:23 AM UTC+2 TW Tones wrote:
>
>> The information you are after is in my earlier post
>> *<> {{!!field}} *is the display replace this with *{{{ 
>> [all[current]get[field]format:date[]] }}}*
>>
>> It is what is inside the span that gets coloured using style attribute, 
>> thus what is inside the span is what is displayed,
>>
>> > [all[]prefix[New]!titleget[field]match{!!field}then[color: 
>> red;]] }}}>* this is displayed inside the list*
>>
>> So basically we replace the display of  *{{!!field}} *
>> With *{{{ [all[current]get[field]format:date[]] }}}*
>> (change "field" to your date field)
>>
>> So the following will be inside the span because you want the title and 
>> its date.
>> *<> **{{{ [all[current]get[field]format:date[]] }}}*
>>
>> The format operator requires tiddlywiki 5.1.23 or greater
>>
>> Tones
>> On Saturday, 28 August 2021 at 02:13:48 UTC+10 mohamed...@hotmail.com 
>> wrote:
>>
>>> Hi tones,
>>>
>>> have you had the chance to look at my last post?
>>>
>>> On Saturday, August 21, 2021 at 5:14:38 AM UTC+2 paulgilbert2000 wrote:
>>>
>>>> Hi Tones,
>>>>
>>>> I am not sure which line of code you are referring too , the line that 
>>>> does the coloring is 
>>>> <$list filter="[all[current]get[field_example]] 
>>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>>> variable=field-value>
>>>> matchthen[color: 
>>>> red;]] }}}><>
>>>>
>>>> It does not have <> {{!!field}} 
>>>>
>>>> instead there is  <>  ,so is this the bit that should be 
>>>> replaced *?*
>>>>
>>>> i tried this  with no luck..
>>>>
>>>>
>>>> *[image: Capture.PNG]*
>>>> On Monday, August 16, 2021 at 6:29:52 AM UTC+2 TW Tones wrote:
>>>>
>>>>> Hio,
>>>>>
>>>>> Back in my code
>>>>> 
>>>>> <$list filter="[all[]prefix[New]has[field]]">
>>>>>>>>> [all[]prefix[New]!titleget[field]match{!!field}then[color:
>>>>>  
>>>>> red;]] }}}>* <> {{!!field}}*
>>>>> 
>>>>> 
>>>>>
>>>>>
>>>>> *<> {{!!field}} *is the display
>>>>> replace this with 
>>>>> *{{{ [all[current]get[field]format:date[]] }}}*
>>>>> Not tested by me on this occasion
>>>>>
>>>>> where

[tw5] Re: Dynamic list with tiddler names containing a space

2021-08-28 Thread TW Tones
Sandip,

Come over and try Discourse and continue the conversation there, you can 
edit posts there.

I understand that tiddlywikis flexibility and some of its quirks seem 
overwhelming in the early days but it is very rewarding in the long run. A 
Good investment in time.

Tones

On Thursday, 26 August 2021 at 00:59:44 UTC+10 Sandip Deshmukh wrote:

> Thanks, Mario.
>
> That was an error. It should have been the same field in both the places.
>
> Frankly, I am kind of overwhelmed with a lot of things in tiddlywiki. And 
> being a newbie, finding it is a bit difficult to cope up.
>
> I am very near to achieving what I wanted to. But because Google Groups 
> does not allow me to change the earlier message, I will post a new 
> conversation.
>
> Please bear with me.
>
>
> On Wednesday, August 25, 2021 at 7:28:17 PM UTC+5:30 PMario wrote:
>
>> On Wednesday, August 25, 2021 at 12:26:56 PM UTC+2 Sandip Deshmukh wrote:
>>
>> But the filter syntax you have provided does not produce any results.
>>>
>>
>> IMO your variables are different. You wrote there is a tag project and 
>> the filter uses it. 
>> Then your wrote 
>>
>> >Another tiddler "D D" has [[A A]] and [[B B]] in participants. 
>>
>> Here you use participants. .. Which is not used in the filter. So it 
>> doesn't do anything. 
>>
>> just a guess
>> -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/5a676286-5dce-47c7-b4c5-40db163b261fn%40googlegroups.com.


Re: [tw5] Re: Tw-Themes: How to keep CSS so users can still (palette) tweak?

2021-08-28 Thread TW Tones
An additional Note see Control Panel > Info > Advanced > StyleSheets

The order they are in determines which styles win. use 
<> and you can drag and drop the order.

Tones

On Saturday, 28 August 2021 at 07:20:26 UTC+10 Álvaro wrote:

> If you change "background" to green the tiddler background take it.
>
> El viernes, 27 de agosto de 2021 a las 20:10:26 UTC+2, flanc...@gmail.com 
> escribió:
>
>> Everything seems to be starting to come together! I noticed in the 
>> Palette that background and page-background are different, what does 
>> background refer to?
>>
>> On Friday, August 27, 2021 at 8:47:31 AM UTC-4 Finn Lancaster wrote:
>>
>>> Thanks @Alvaro, I’ll take a look at those. Already, the TW-primer shows 
>>> up in the themes tab based on my changes on my end, I tend not to push to 
>>> GitHub until the product is able to be used. 
>>>
>>> On Fri, Aug 27, 2021 at 7:00 AM Álvaro  wrote:
>>>
 You can include the paltte in the theme.
 Here you have two examples:
 - Mono theme 
 
 - Notebook theme 
 

 There is another point that you can see, these themes start with 
 *$:/themes/ 
 *instead of  *$:/plugins/ . *They are a kind of plugin but you will 
 see them in ControlPanel > Appearance > Theme 

 El viernes, 27 de agosto de 2021 a las 2:45:01 UTC+2, 
 flanc...@gmail.com escribió:

> Started working on it, and already another question! It seems that I 
> can't include a palette inside the theme, but instead may have to do it 
> differently ???
>
> My palette file looks like this:
>
> description: Sleek dark skin for tw5, based on primer.css!
> name: tw5-primer
> title: $:/palettes/tw5-primer
> tags: $:/tags/Palette
> type: application/x-tiddler-dictionary
>
> And palette code here...
>
> Any ideas for what's going on? I'm thinking maybe the palette may have 
> to be defined inside the css file??
>
> Thanks for your (continued) help!
> On Thursday, August 26, 2021 at 7:45:47 PM UTC-4 Finn Lancaster wrote:
>
>> Thanks, I'll look at doing this, and hopefully not run into any more 
>> issues so that I don't have to bother you anymore :)
>>
>> On Thursday, August 26, 2021 at 7:36:55 PM UTC-4 Álvaro wrote:
>>
>>> A palette is basically a data tiddler, a dictionary that stores N 
>>> key:value, with type application/x-tiddler-dictionary. Then you can use 
>>> it 
>>> with <> where keyName can be page-background or 
>>> others. 
>>>
>>> You don´t need change the type, that is the default type (I think). 
>>> If your file has the correct tag ( $:/tags/Stylesheet ) then it 
>>> works like stylesheet file.
>>>
>>> you can see more of what was discussed here 
>>> 
>>>
>>> Do not be scared of the number of entries in the vanilla palette, 
>>> many keys reuse values, there are palettes with fewer entries. It 
>>> is also something that has already been discussed about how to reduce 
>>> the 
>>> palettes, but it would be part of the hard rework in the styles of 
>>> TiddlyWiki. 
>>> El viernes, 27 de agosto de 2021 a las 0:36:14 UTC+2, 
>>> strikke...@gmail.com escribió:
>>>
 <> gives you the color number from the palette - that 
 will be the colour the user of your theme has chosen as the active 
 palette 
 for their use of Tiddlywiki. 
 Sorry but I do not know much more about the subject.

 On Thursday, August 26, 2021 at 11:54:48 PM UTC+2 
 flanc...@gmail.com wrote:

> that seems to have worked, @strikke..., I'm guessing I have to 
> include it in my theme files now, and that I can change my css to a 
> text/vnd.tiddlywiki file, so that I can call colors such as 
> <> 
> ? Is this correct to assume?
>
> On Thursday, August 26, 2021 at 5:48:02 PM UTC-4 
> strikke...@gmail.com wrote:
>
>>
>>
>> Sorry if I am being stupid, but could it not be done going to 
>> $:/ControlPanel  
>> select tab Appearance and then Palette. Go to the bottom of that and 
>> click 
>> the Show editor button. That will show the selected palette. Select 
>> clone 
>> palette. Then you can edit that. You will see how it is done and can 
>> choose 
>> the colours you prefer. That is at least a start. 
>> On Thursday, August 26, 2021 at 10:27:17 PM UTC+2 
>> flanc...@gmail.com wrote:
>>
>>> 

[tw5] Re: Tiddler Pick List for Creating a Link?

2021-08-28 Thread TW Tones
look at the link icon on the editor tool bar, this does exactly that.

On Saturday, 28 August 2021 at 21:34:49 UTC+10 mikjs...@gmail.com wrote:

>
> Hi
>
> When Im editing a tiddler, is it possible to pick a tiddler from a list 
> and then create a link to it? I want to make sure I get the name right and 
> so pick it from a list of existing tiddlers rather than have to type it in
>
> 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/82b9d3ec-e8a8-46d6-afa7-2b8d455e8386n%40googlegroups.com.


[tw5] Re: Edit Suggestion: Simple ways to write protect tiddlers

2021-08-27 Thread TW Tones
I add the edit icon to other lists so I can edit a tiddler !

{{||$:/core/ui/Buttons/edit}} <$link/>

Tones
On Saturday, 28 August 2021 at 11:51:10 UTC+10 Eric Shulman wrote:

> On Friday, August 27, 2021 at 3:49:41 PM UTC-7 cj.v...@gmail.com wrote:
>
>> Simple ways to write protect tiddlers 
>> 
>>
> To write-protect a tiddler, I'm thinking a good idea to not just prevent 
>> edit of such a tiddler, but also prevent delete of such a tiddler.
>> I've added a little bit to the original sample code in that documentation 
>> tiddler:
>> .tc-tagged-Locked button[title="Edit this tiddler"] {display: none;}
>> .tc-tagged-Locked button[title="Delete this tiddler"] {display: none;}
>>
>
> Question:
> Let's suppose you lock a tiddler by adding the "Locked" tag and then you 
> need to make changes (e.g., fixing a typo).
> How would you unlock the tiddler, since you can't edit it to remove the 
> "Locked" tag?
>
> -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/a711b5e9-c06e-4fe0-ab03-82c67dceff2an%40googlegroups.com.


Re: [tw5] Re: Gitmbed is Public! Make YOUR wiki more accessible!

2021-08-27 Thread TW Tones
That would be great. Do try and write for the Naive reader, at most they 
have some understanding of tiddlywiki.

Perhaps explain why the plugin exists, what it can do for you, avoid jargon 
compare it to existing tools.

Then you can go into technical details and jargon later in the post/email.

Join us in Discourse <http://talk.tiddlywiki.org>

On Saturday, 28 August 2021 at 11:28:03 UTC+10 flanc...@gmail.com wrote:

> Thanks for the great positivity! I’m always trying to make TW better than 
> it already is as well as I can; I’m glad to see people appreciate it! 
>
> I’m thinking about perhaps making a how-to manual for my plugins/software, 
> so that people can better understand how to do/use some of my solutions. 
> Maybe this is yet another thing I can use TW for! 
>
> On Fri, Aug 27, 2021 at 9:21 PM TW Tones  wrote:
>
>> Flanc,
>>
>> Once again you seem to be producing another revolutionary feature to the 
>> TiddlyVerse. Unfortunately I can't keep up just now but I want to thank 
>> you. I would also suggest with 5.2.0 soon and Discourse many may have 
>> difficulty learning about and using your solutions right away, I expect 
>> they will be a "slow burn", so expect a response if not delayed a bit.
>>
>> Thanks for your contributions
>> Tones
>>
>>
>> On Friday, 27 August 2021 at 23:48:31 UTC+10 flanc...@gmail.com wrote:
>>
>>>  Hi everyone,
>>>
>>> A while back, I posted about my new chrome extension: gitmbed, which, 
>>> while not directly tw-related, I believe could be used to improve 
>>> accessibility to tw from INSIDE online social media/GitHub. The extension 
>>> can be found at 
>>> https://chrome.google.com/webstore/detail/gitmbed/cbfjhpckapddemlmidlmgoepochhfpfi,
>>>  
>>> the official gitmbed website is at https://gitmbed.finnsoftware.net, 
>>> and the GitHub is at https://github.com/flancast90/gitmbed.
>>>
>>>
>>> *How can I use gitmbed with tw?*
>>>
>>> Gitmbed makes it easy to embed your tw inside Social Media Website Posts 
>>> (Instagram.com, Facebook, GitHub) which would normally block embeds. You 
>>> can make your first gitmbed by navigating to 
>>> https://gitmbed.finnsoftware.net#setup 
>>> <https://gitmbed.finnsoftware.net/#setup>, which all you will have to 
>>> give is a URL to your tw, the height you want the embed to be, and the 
>>> width. 
>>>
>>>
>>> While instructions for only Instagram.com and GitHub are given there, 
>>> gitmbed, in fact, will work on anything where you can add alt text to an 
>>> image. This means that you can use it for Facebook/anywhere else assuming 
>>> you can add an image and alt text to it.
>>>
>>>
>>> I hope it really is a help for all of you; a demo of an embedded 
>>> tiddlywiki.com can be found at https://gitmbed.finnsoftware.net#demo 
>>> <https://gitmbed.finnsoftware.net/#demo>, and, as usual, feel free to 
>>> drop a star at https://github.com/flancast90/gitmbed.
>>>
>> -- 
>> You received this message because you 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/67203d86-03d7-4401-adf2-010887f408b4n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/67203d86-03d7-4401-adf2-010887f408b4n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

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


[tw5] Re: Gitmbed is Public! Make YOUR wiki more accessible!

2021-08-27 Thread TW Tones
Flanc,

Once again you seem to be producing another revolutionary feature to the 
TiddlyVerse. Unfortunately I can't keep up just now but I want to thank 
you. I would also suggest with 5.2.0 soon and Discourse many may have 
difficulty learning about and using your solutions right away, I expect 
they will be a "slow burn", so expect a response if not delayed a bit.

Thanks for your contributions
Tones


On Friday, 27 August 2021 at 23:48:31 UTC+10 flanc...@gmail.com wrote:

>  Hi everyone,
>
> A while back, I posted about my new chrome extension: gitmbed, which, 
> while not directly tw-related, I believe could be used to improve 
> accessibility to tw from INSIDE online social media/GitHub. The extension 
> can be found at 
> https://chrome.google.com/webstore/detail/gitmbed/cbfjhpckapddemlmidlmgoepochhfpfi,
>  
> the official gitmbed website is at https://gitmbed.finnsoftware.net, and 
> the GitHub is at https://github.com/flancast90/gitmbed.
>
>
> *How can I use gitmbed with tw?*
>
> Gitmbed makes it easy to embed your tw inside Social Media Website Posts 
> (Instagram.com, Facebook, GitHub) which would normally block embeds. You 
> can make your first gitmbed by navigating to 
> https://gitmbed.finnsoftware.net#setup 
> , which all you will have to 
> give is a URL to your tw, the height you want the embed to be, and the 
> width. 
>
>
> While instructions for only Instagram.com and GitHub are given there, 
> gitmbed, in fact, will work on anything where you can add alt text to an 
> image. This means that you can use it for Facebook/anywhere else assuming 
> you can add an image and alt text to it.
>
>
> I hope it really is a help for all of you; a demo of an embedded 
> tiddlywiki.com can be found at https://gitmbed.finnsoftware.net#demo 
> , and, as usual, feel free to 
> drop a star at https://github.com/flancast90/gitmbed.
>

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


[tw5] Re: Highlighting duplicates in lists

2021-08-27 Thread TW Tones
The information you are after is in my earlier post
*<> {{!!field}} *is the display replace this with *{{{ 
[all[current]get[field]format:date[]] }}}*

It is what is inside the span that gets coloured using style attribute, 
thus what is inside the span is what is displayed,

get[field]match{!!field}then[color: 
red;]] }}}>* this is displayed inside the list*

So basically we replace the display of  *{{!!field}} *
With *{{{ [all[current]get[field]format:date[]] }}}*
(change "field" to your date field)

So the following will be inside the span because you want the title and its 
date.
*<> **{{{ [all[current]get[field]format:date[]] }}}*

The format operator requires tiddlywiki 5.1.23 or greater

Tones
On Saturday, 28 August 2021 at 02:13:48 UTC+10 mohamed...@hotmail.com wrote:

> Hi tones,
>
> have you had the chance to look at my last post?
>
> On Saturday, August 21, 2021 at 5:14:38 AM UTC+2 paulgilbert2000 wrote:
>
>> Hi Tones,
>>
>> I am not sure which line of code you are referring too , the line that 
>> does the coloring is 
>> <$list filter="[all[current]get[field_example]] 
>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>> variable=field-value>
>> matchthen[color: 
>> red;]] }}}><>
>>
>> It does not have <> {{!!field}} 
>>
>> instead there is  <>  ,so is this the bit that should be 
>> replaced *?*
>>
>> i tried this  with no luck..
>>
>>
>> *[image: Capture.PNG]*
>> On Monday, August 16, 2021 at 6:29:52 AM UTC+2 TW Tones wrote:
>>
>>> Hio,
>>>
>>> Back in my code
>>> 
>>> <$list filter="[all[]prefix[New]has[field]]">
>>>>> [all[]prefix[New]!titleget[field]match{!!field}then[color: 
>>> red;]] }}}>* <> {{!!field}}*
>>> 
>>> 
>>>
>>>
>>> *<> {{!!field}} *is the display
>>> replace this with 
>>> *{{{ [all[current]get[field]format:date[]] }}}*
>>> Not tested by me on this occasion
>>>
>>> where field is the chosen fieldname.
>>>
>>> Regards
>>> Tones
>>>
>>> On Monday, 16 August 2021 at 12:14:51 UTC+10 mohamed...@hotmail.com 
>>> wrote:
>>>
>>>> Thank you tones
>>>>
>>>> The real life example is to evaluate duplicate dates, so the actual 
>>>> real values populating the fields are not  1 ,2 , etc.. they are actual 
>>>> dates , IE . 2021062506295,   20210811055859000,etc.
>>>> and so what i was trying is to  do is have the highlighted duplicate 
>>>> values converted from the tiddly wiki format they are stored in in their 
>>>> respective fields , to a normal readable format when displayed in the 
>>>> filter
>>>>
>>>> the
>>>> On Monday, August 16, 2021 at 2:34:07 AM UTC+2 TW Tones wrote:
>>>>
>>>>> Mohammad,
>>>>>
>>>>> I am confused, until now the fields  field_example,  field_example1,  
>>>>> field_example2 did not contain dates. 
>>>>>
>>>>>- Are you trying to convert these to dates?
>>>>>- the view widget format=date only works on tiddlywiki full serial 
>>>>>number dates!
>>>>>
>>>>> Perhaps step back and describe what you want to do in the real world, 
>>>>> not with tiddlywiki code that may or may not be correct. 
>>>>>
>>>>> Regards
>>>>> Tones
>>>>>
>>>>> On Monday, 16 August 2021 at 01:46:55 UTC+10 mohamed...@hotmail.com 
>>>>> wrote:
>>>>>
>>>>>> HI tones,
>>>>>>
>>>>>> sorry i guess i asked the wrong question, what i wanted to know is 
>>>>>> where to place the widget  in the code , if i do it that way , it no 
>>>>>> longer 
>>>>>> highlights duplicates
>>>>>>
>>>>>>  <>: |  
>>>>>><$list filter="[all[current]get[field_example]] 
>>>>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>>>>> variable=field-value>
>>>>>> <$view field="field_example "format=date template=""/>
>>>>>> <$view field="field_example1"format=date template=""/>
>>>>>> <$view field="field_example2"format=date template="

[tw5] Re: List filter using the checkbox widget

2021-08-26 Thread TW Tones
Also remember you can make yourself a set of buttons and they can do what 
you want, then double them and conditionally show the appropriate one for 
the current state.

Buttons can replicate checkboxes, radio buttons and much more if you want, 
in fact tabs we use are and can be designed as buttons.

Tones


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

> @Tones
> I did see the select widget but was hoping for a method that takes up less 
> space and has a slightly easier mechanic.  I'll may use it, at least for now
>
> @Stobot
> I hadn't thought of using fields in the temp tiddler.  I think I would 
> need a method of naming and incrementing through the fields as this will 
> change based on the source tiddler's field contents
>
> Thanks to you both for a quick reply
>
> On Thursday, August 26, 2021 at 7:19:10 AM UTC-5 Stobot wrote:
>
>> I might be proven wrong, but my experience is that it's a 1:1 
>> relationship between the checkbox and a storage location, there's not a way 
>> to directly have multiple checkboxes change a list per-se. A couple of 
>> ideas though:
>>
>>- You could use the same temp tiddler and use individual fields for 
>>your possible values, that might make it easier to collect the values for 
>>later processing. 
>>- There are now "checkactions" and "uncheck actions" associated with 
>>the widget. So, if you wanted to, you could force the checkboxes to run a 
>>listops routine to add-subtract values from a list. This would be the 
>>closest to what your expecations are, but it might not actually be the 
>> most 
>>efficient. 
>>
>>
>> On Thursday, August 26, 2021 at 8:07:40 AM UTC-4 TW Tones wrote:
>>
>>> jkm
>>>
>>> Have you looked at the select widget, it also has a multiple option.
>>>
>>> Tones
>>>
>>> On Thursday, 26 August 2021 at 21:26:28 UTC+10 jkm...@gmail.com wrote:
>>>
>>>> I am able to use the radio widget to control my list filter.  Now I 
>>>> would like to use checkboxes in a multi-select manner (e.g., include any 
>>>> checked keywords:  Info, fix, Procedure).  However, I haven't seen an 
>>>> example of this yet.  My attempt
>>>>
>>>> ...
>>>> ''KBA Type:''
>>>>   <$checkbox tiddler="$:/temp/ktype" 
>>>> value="Procedure">Procedure
>>>>   <$checkbox tiddler="$:/temp/ktype" 
>>>> value="Info">Info
>>>>   <$checkbox tiddler="$:/temp/ktype" 
>>>> value="Fix">Fix  
>>>> 
>>>> ...
>>>> <$list filter="[tag[KBA]ktype{$:/temp/ktype}]">
>>>>
>>>> I think I expected all selected items to be handled in the same temp 
>>>> tiddler but maybe I'm overwriting it each time I check/uncheck.  Do I need 
>>>> to create a temp tiddler for each and work out the list filter logic 
>>>> manually in a sequence of separate runs?   
>>>>
>>>> Not sure it's relevant, but I will be wanting to use this to filter on 
>>>> values in a field.  That field may contain a single string or list of 
>>>> strings (examples: *Info *or *Fix Procedure* or *Fix Info*).  
>>>> Ultimately I would like to derive the list of checkboxes from a field 
>>>> within all tiddlers with a specific tag.  Like a "tag" based search engine 
>>>> except they are not TW tags, they are just tags derived from the tiddler 
>>>> field.  But, baby steps (assuming it's possible/practical).
>>>>
>>>

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


[tw5] Re: List filter using the checkbox widget

2021-08-26 Thread TW Tones
jkm

Have you looked at the select widget, it also has a multiple option.

Tones

On Thursday, 26 August 2021 at 21:26:28 UTC+10 jkm...@gmail.com wrote:

> I am able to use the radio widget to control my list filter.  Now I would 
> like to use checkboxes in a multi-select manner (e.g., include any checked 
> keywords:  Info, fix, Procedure).  However, I haven't seen an example of 
> this yet.  My attempt
>
> ...
> ''KBA Type:''
>   <$checkbox tiddler="$:/temp/ktype" 
> value="Procedure">Procedure
>   <$checkbox tiddler="$:/temp/ktype" 
> value="Info">Info
>   <$checkbox tiddler="$:/temp/ktype" 
> value="Fix">Fix  
> 
> ...
> <$list filter="[tag[KBA]ktype{$:/temp/ktype}]">
>
> I think I expected all selected items to be handled in the same temp 
> tiddler but maybe I'm overwriting it each time I check/uncheck.  Do I need 
> to create a temp tiddler for each and work out the list filter logic 
> manually in a sequence of separate runs?   
>
> Not sure it's relevant, but I will be wanting to use this to filter on 
> values in a field.  That field may contain a single string or list of 
> strings (examples: *Info *or *Fix Procedure* or *Fix Info*).  Ultimately 
> I would like to derive the list of checkboxes from a field within all 
> tiddlers with a specific tag.  Like a "tag" based search engine except they 
> are not TW tags, they are just tags derived from the tiddler field.  But, 
> baby steps (assuming it's possible/practical).
>

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


[tw5] Re: Renaming and deleting fields

2021-08-26 Thread TW Tones
Sorry,

I meant to say as long as a field exists somewhere it will be available in 
the new field dropdown. If you need to delete in bulk let us know or use 
Mohammads tools.

Tones

On Thursday, 26 August 2021 at 22:04:56 UTC+10 TW Tones wrote:

> Sandip
>
>
>- In edit mode the fields should appear at the bottom for editing, to 
>the right is a trash can to delete.
>- To rename you need to create the new one (optionally copy the value 
>over) and delete the old one
>- If you are trying to do it programmatically you can use a button 
>and  ActionSetFieldWidget 
><https://tiddlywiki.com/#ActionSetFieldWidget>  ActionDeleteFieldWidget 
><https://tiddlywiki.com/#ActionDeleteFieldWidget> and or  WidgetMessage: 
>tm-remove-field 
><https://tiddlywiki.com/#WidgetMessage%3A%20tm-remove-field>
>
> Regards
> Tones
>
> On Thursday, 26 August 2021 at 20:34:14 UTC+10 Sandip Deshmukh wrote:
>
>> It is easy to rename and delete tags.
>>
>> But how do I do the same with fields?
>>
>> Suppose, fld1 and fld2 are the fields I have created.
>>
>> How can I rename fld1 to field1 and remove (so it does not show up in the 
>> list of fields available when I create a tiddler) fld2?
>>
>

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


[tw5] Re: Renaming and deleting fields

2021-08-26 Thread TW Tones
Sandip


   - In edit mode the fields should appear at the bottom for editing, to 
   the right is a trash can to delete.
   - To rename you need to create the new one (optionally copy the value 
   over) and delete the old one
   - If you are trying to do it programmatically you can use a button and  
   ActionSetFieldWidget   
   ActionDeleteFieldWidget  
and 
   or  WidgetMessage: tm-remove-field 
   

Regards
Tones

On Thursday, 26 August 2021 at 20:34:14 UTC+10 Sandip Deshmukh wrote:

> It is easy to rename and delete tags.
>
> But how do I do the same with fields?
>
> Suppose, fld1 and fld2 are the fields I have created.
>
> How can I rename fld1 to field1 and remove (so it does not show up in the 
> list of fields available when I create a tiddler) fld2?
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3f666842-1e2b-4d05-9efa-1203fcc44876n%40googlegroups.com.


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

2021-08-26 Thread TW Tones
 such an awesome developer!) so far all releases have been 
> pretty self explanatory as far as basic functionality goes anyway 
> especially with his release notes and the help he and everyone here or 
> later there in discourse provides. So until I really need to communicate I 
> will probably just lurk there as I have here and search threads on both to 
> find answers to any questions I may have. Almost always anything I might 
> have a question about has already been asked and answered anyway. You guys 
> are awesome and I want you to know that despite what I can or can not do I 
> am 100% behind all of you! 
>
> Thanks, 
>
> On Wed, Aug 25, 2021 at 7:17 PM TW Tones  wrote:
>
>> Birthe/Strike,
>>
>> I hope Ed did not think "I thought he was complaining". I think my 
>> argument points out the new platform will be valuable to everyone, and is 
>> important, despite the pain of change. In fact it is really important Ed 
>> and Charlie etc.. understand I will help in any way I can.
>>
>> Some of these improvements will help reduce cognitive load once we have 
>> them working, like being able to have a Wiki Post that we can all edit 
>> which ultimately can summarise a thread.
>>
>> Also I would hope the overriding message is "as a community we can work 
>> with our diverse community" to support and enable them which I can really 
>> see is necessary when moving to a fully featured solution. Basically unlike 
>> many other communities members can get personal one on one support. We have 
>> done some in the past, and yes we can do so more, but the community seems 
>> dedicated to do so.
>>
>> Still I welcome your comments.
>>
>> On Tuesday, 24 August 2021 at 13:20:39 UTC+10 strikke...@gmail.com wrote:
>>
>>> Tony,
>>> Ed did not complain. He would not like to miss totally out on the group 
>>> and is afraid that will happen! Explained that his need was to receive 
>>> email summary as that is the only way it would be possible for him to enjoy 
>>> the part possible for him to use. The question was not about the reasoning 
>>> for some to want the move - but: "Will I be able to receive email summary 
>>> from this new group - and if so, can someone help me get it set up?"
>>>
>>> Just as when you asked for a couple of days, why you were not able to 
>>> login and get writing in the new group - and asked repeatedly to get help 
>>> from moderators to be able to write to the group. (Sure easy to sign up - 
>>> you now write). Other people have other problems, and not everyone has all 
>>> of your expertise in using all sorts of groups at a professional level.
>>>
>>> As a promoter for the move and now a leader in the new group prepare for 
>>> questions like this - and be happy when they are asked. This group is large 
>>> and lots of users have used it for years - but have special needs to be 
>>> able to do so.  If questions like this is not met with answers - those 
>>> users will just be sorry and give up without telling you - and have lost 
>>> yet another thing in life. Please remember that someone's gain is often 
>>> happening while others loose out.
>>>
>>> We know that quite some users of this group -found ways to keep using 
>>> Tiddlywiki and this group. And at. some point explained their special needs 
>>> and why they needed a solution. Poor eyesight or blindness has been one of 
>>> them.
>>>
>>> I would think that promoting the discourse group - why not make it clear 
>>> - can you use the group directly from receiving emails - emails summary. 
>>> Can you use the group fully if your only way of being able is using a 
>>> screen reader?
>>>
>>> Others have written earlier about having difficulty with busy screens, 
>>> moving parts - and lot of colour - lots of changing screens with shifting 
>>> layouts - and even more I cannot remember now. Explain how to use it for 
>>> those - if possible.
>>>
>>> If people with special needs are not in the target group for the the new 
>>> group - save time and explain why.
>>>
>>> Please think about it - and ask people to explain their problems - and 
>>> try to find solutions. Use those points in the promotion.  Plenty of 
>>> telling it is beautiful, easy, what some wants etc. I think most have read 
>>> that by now.
>>>
>>> And the questions have to be asked before your wished making this group 
>>> read only - because afterwards - you will n

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

2021-08-25 Thread TW Tones
gt;>> go because he knows when he adds new features he needs to make the 
>>> explanations and use of them as intuitive and user friendly (there's an old 
>>> term!) as possible and most likely with those explanations in mind. 
>>> TiddlyWiki itself is the best example that I can think of due to its 
>>> simplicity in a way. It has amazing capabilities but an ease of use 
>>> unparalleled by programs that have almost none of the customization 
>>> capabilities allowing it to be used as needed. I have seen efforts to write 
>>> books and manuals fail not due to a lack of effort, knowledge, or ability 
>>> but a lack of being able to keep up with the pace TW5 evolves which is an 
>>> amazing example of how much work Jeremy and those who help him have 
>>> put into this over the years! To me this group does represent a record of 
>>> all that effort and progress he might prefer continues here? 
>>>
>>> But not trying to argue for or against with anyone. LOL I know longer 
>>> have those skills either (happily). I am Just trying to keep up, which is 
>>> probably a fool's errand anyway but, also offer a reminder that unless 
>>> there is a fork planned I personally feel no one should just take the 
>>> community he has built here and put it over there without him at least 
>>> being a part of that decision.  
>>>
>>> Thanks!
>>>
>>>
>>> On Mon, Aug 23, 2021 at 10:20 PM strikke...@gmail.com <
>>> strikke...@gmail.com> wrote:
>>>
>>>> Tony,
>>>> Ed did not complain. He would not like to miss totally out on the group 
>>>> and is afraid that will happen! Explained that his need was to receive 
>>>> email summary as that is the only way it would be possible for him to 
>>>> enjoy 
>>>> the part possible for him to use. The question was not about the reasoning 
>>>> for some to want the move - but: "Will I be able to receive email summary 
>>>> from this new group - and if so, can someone help me get it set up?"
>>>>
>>>> Just as when you asked for a couple of days, why you were not able to 
>>>> login and get writing in the new group - and asked repeatedly to get help 
>>>> from moderators to be able to write to the group. (Sure easy to sign up - 
>>>> you now write). Other people have other problems, and not everyone has all 
>>>> of your expertise in using all sorts of groups at a professional level.
>>>>
>>>> As a promoter for the move and now a leader in the new group prepare 
>>>> for questions like this - and be happy when they are asked. This group is 
>>>> large and lots of users have used it for years - but have special needs to 
>>>> be able to do so.  If questions like this is not met with answers - those 
>>>> users will just be sorry and give up without telling you - and have lost 
>>>> yet another thing in life. Please remember that someone's gain is often 
>>>> happening while others loose out.
>>>>
>>>> We know that quite some users of this group -found ways to keep using 
>>>> Tiddlywiki and this group. And at. some point explained their special 
>>>> needs 
>>>> and why they needed a solution. Poor eyesight or blindness has been one of 
>>>> them.
>>>>
>>>> I would think that promoting the discourse group - why not make it 
>>>> clear - can you use the group directly from receiving emails - emails 
>>>> summary. Can you use the group fully if your only way of being able is 
>>>> using a screen reader?
>>>>
>>>> Others have written earlier about having difficulty with busy screens, 
>>>> moving parts - and lot of colour - lots of changing screens with shifting 
>>>> layouts - and even more I cannot remember now. Explain how to use it for 
>>>> those - if possible.
>>>>
>>>> If people with special needs are not in the target group for the the 
>>>> new group - save time and explain why.
>>>>
>>>> Please think about it - and ask people to explain their problems - and 
>>>> try to find solutions. Use those points in the promotion.  Plenty of 
>>>> telling it is beautiful, easy, what some wants etc. I think most have read 
>>>> that by now.
>>>>
>>>> And the questions have to be asked before your wished making this group 
>>>> read only - because afterwards - you will never know.
>>&g

Re: [tw5] Re: Random html tags appear in my wiki

2021-08-25 Thread TW Tones
David,

I am not so sure how to help you but in the past I have seen random 
tiddlers or their content transcluded when a filter is broken and the 
result is some artifact. So if you can find the page template, or something 
tagged $:/tags/BelowStory with a filter in it and fix the filter you may 
stop it.
On Tuesday, 24 August 2021 at 23:12:37 UTC+10 David Shaw wrote:

> I get the same sort of thing with both Tiddloid and Tiddloid Lite. I 
> suspect it is a problem with Tiddloid as I can get the code to disappear if 
> I open it in either Tiddloid version, save and close it then open it in the 
> other Tiddloid and save and close it, but this is only a very temporary 
> solution I'm afraid; the code comes back pretty quickly.
>
> David Shaw
>
> On Tue, 24 Aug 2021, 13:52 PMario,  wrote:
>
>> Hi,
>>
>> Which version of TW do you use?
>> Can you link to the Android app you are using?
>>
>> Did you install any new plugins, before you copied it over to the phone?
>>
>> -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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/797d0403-6673-408f-87af-b093d6365993n%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/7a536d61-993a-4da3-9059-1638e7891d3cn%40googlegroups.com.


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

2021-08-25 Thread TW Tones
Birthe/Strike,

I hope Ed did not think "I thought he was complaining". I think my argument 
points out the new platform will be valuable to everyone, and is important, 
despite the pain of change. In fact it is really important Ed and Charlie 
etc.. understand I will help in any way I can.

Some of these improvements will help reduce cognitive load once we have 
them working, like being able to have a Wiki Post that we can all edit 
which ultimately can summarise a thread.

Also I would hope the overriding message is "as a community we can work 
with our diverse community" to support and enable them which I can really 
see is necessary when moving to a fully featured solution. Basically unlike 
many other communities members can get personal one on one support. We have 
done some in the past, and yes we can do so more, but the community seems 
dedicated to do so.

Still I welcome your comments.

On Tuesday, 24 August 2021 at 13:20:39 UTC+10 strikke...@gmail.com wrote:

> Tony,
> Ed did not complain. He would not like to miss totally out on the group 
> and is afraid that will happen! Explained that his need was to receive 
> email summary as that is the only way it would be possible for him to enjoy 
> the part possible for him to use. The question was not about the reasoning 
> for some to want the move - but: "Will I be able to receive email summary 
> from this new group - and if so, can someone help me get it set up?"
>
> Just as when you asked for a couple of days, why you were not able to 
> login and get writing in the new group - and asked repeatedly to get help 
> from moderators to be able to write to the group. (Sure easy to sign up - 
> you now write). Other people have other problems, and not everyone has all 
> of your expertise in using all sorts of groups at a professional level.
>
> As a promoter for the move and now a leader in the new group prepare for 
> questions like this - and be happy when they are asked. This group is large 
> and lots of users have used it for years - but have special needs to be 
> able to do so.  If questions like this is not met with answers - those 
> users will just be sorry and give up without telling you - and have lost 
> yet another thing in life. Please remember that someone's gain is often 
> happening while others loose out.
>
> We know that quite some users of this group -found ways to keep using 
> Tiddlywiki and this group. And at. some point explained their special needs 
> and why they needed a solution. Poor eyesight or blindness has been one of 
> them.
>
> I would think that promoting the discourse group - why not make it clear - 
> can you use the group directly from receiving emails - emails summary. Can 
> you use the group fully if your only way of being able is using a screen 
> reader?
>
> Others have written earlier about having difficulty with busy screens, 
> moving parts - and lot of colour - lots of changing screens with shifting 
> layouts - and even more I cannot remember now. Explain how to use it for 
> those - if possible.
>
> If people with special needs are not in the target group for the the new 
> group - save time and explain why.
>
> Please think about it - and ask people to explain their problems - and try 
> to find solutions. Use those points in the promotion.  Plenty of telling it 
> is beautiful, easy, what some wants etc. I think most have read that by now.
>
> And the questions have to be asked before your wished making this group 
> read only - because afterwards - you will never know.
>
> Who *IS* in the Target group for the new group? And then list the 
> promoting  points - ALL of them. Show that list clearly in both groups.
>
> Please - I did not in anyway want to offend anyone - but we are not all 
> the same.
>  
> On Tuesday, August 24, 2021 at 1:46:44 AM UTC+2 TW Tones wrote:
>
>> Ed,
>>
>> Many of us who are deeply imbedded and active in Google Groups have good 
>> reasons and arguments to move. Apart from the fact you can't even reply on 
>> a mobile, mark code in a forum post and more Discourse solves a range of 
>> problems and issues that I expect you do not experience every day.
>>
>> We can't rely on Google any more and moving to talk.tiddlywiki.org puts 
>> control into the communities hands. In many ways "a move" if not "this 
>> move" has being on the cards for years, however getting consensus from the 
>> community is like herding cats. To put this decision on Jeremy alone is 
>> also asking too much.
>>
>> I know change can be difficult but as always the community is here to 
>> help, and from what I have seen Discourse offers everything and more than 
>> GG. So I am confident w

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

2021-08-23 Thread TW Tones
Ed,

Many of us who are deeply imbedded and active in Google Groups have good 
reasons and arguments to move. Apart from the fact you can't even reply on 
a mobile, mark code in a forum post and more Discourse solves a range of 
problems and issues that I expect you do not experience every day.

We can't rely on Google any more and moving to talk.tiddlywiki.org puts 
control into the communities hands. In many ways "a move" if not "this 
move" has being on the cards for years, however getting consensus from the 
community is like herding cats. To put this decision on Jeremy alone is 
also asking too much.

I know change can be difficult but as always the community is here to help, 
and from what I have seen Discourse offers everything and more than GG. So 
I am confident we can restore the functionality you want.

Please continue to raise issues but also let the community help you 
transition or solve the problems you experience, or even ultimately change 
our minds because of your experience.

If you did not see yet, signing up at  talk.tiddlywiki.org with your google 
login is possibly the easiest entry to the new system.

Yours sincerely
Tony

On Tuesday, 24 August 2021 at 01:15:03 UTC+10 eddi...@gmail.com wrote:

> Hi All,
>
> Unless Jeremy plans to do the same sorry but no thanks and even then 
> probably not. Other than it being a perhaps more feature rich, and newer 
> platform is there really a burning need to make this switch now? I know its 
> been debated here for a long time and have read the arguments both for and 
> against but this sounds as though it is being forced upon us regardless of 
> Jeremys reluctance to do so for some reason. Maybe google has announced it 
> is killing off groups, Jeremy has decided it is for the best, or something 
> else I am unaware of? (very possible I suffer from brain damage and am no 
> longer really in the know anymore, but do rely on getting these emails to 
> try and stay up on developments with TiddlyWiki and the plugin work being 
> done). I can still use TiddlyWiki to great advantage but no longer have the 
> ability to write plugins or do many things I used to do before. Anything 
> new is pretty much impossible for me to learn. Will discourse offer these 
> email updates like the one I am responding to here and will those of us who 
> choose not to join discourse (my mind is unable to learn new things) be 
> registered to receive those if this is done or will I need to register my 
> email address in their site in order to keep these condensed emails coming 
> to me? I also feel there is a wealth of historical information in this 
> group that would be a shame if not transferred over (perhaps it has?) 
> Anyway, I hope replying to "all" is the proper way to ask. If not I do 
> apologize. Also, I am not being critical of this change just explaining my 
> inability to do this and feel it is pointless unless Jeremy wants to make 
> this change as well. If so I guess this group can still stand as an archive 
> of all the history and work that has been done to get us here and if it 
> offers that condensed email capability then maybe. I DO NOT want an email 
> for every post being made thats is an absolute! 
>
> Thanks, 
> On Sunday, August 22, 2021 at 9:21:36 AM UTC-5 TW Tones wrote:
>
>> JW Are you on the specific instance of discourse? 
>> https://talk.tiddlywiki.org/
>>
>> Regards
>> Tones
>>
>> On Sunday, 22 August 2021 at 20:55:10 UTC+10 JWHoneycutt wrote:
>>
>>> Signed up for Discourse - can't find any hits when searching 
>>> "TiddlyWiki" - did I just lose access to the community?
>>> JWH
>>>
>>> On Saturday, August 21, 2021 at 10:23:29 PM UTC-4 joshua@gmail.com 
>>> wrote:
>>>
>>>> Definitely moving over to the Discourse community. See you all there!
>>>>
>>>> Best,
>>>> Joshua Fontany
>>>> On Saturday, August 21, 2021 at 3:42:18 PM UTC-7 Scott Simmons 
>>>> (Secret-HQ) wrote:
>>>>
>>>>> I've created a profile on Talk.TiddlyWiki.org and am delighted with 
>>>>> the interface there.  I'll try to ask questions and create new threads 
>>>>> there rather than here, though I guess I'll be drawn back to Google 
>>>>> Groups 
>>>>> is that's where the conversation flows.  (For my part, I'm hoping it 
>>>>> moves 
>>>>> to Talk.TW)
>>>>>
>>>>> https://talk.tiddlywiki.org/u/secret-hq/
>>>>>
>>>>

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


[tw5] Re: Uncaught TypeError: title.substr is not a function

2021-08-23 Thread TW Tones
Siniy-kit,

I don't know how to help, but if I were in this situation I would try and 
use the JSON Mangler plugin or XLSX Utilities edition to import the same 
spread sheet. Perhaps one of these will not experience the bug or fail 
gracefully helping you identify the problem.

Do join us in discourse talk.tiddlywiki.org

Tones
On Saturday, 21 August 2021 at 04:24:03 UTC+10 Siniy-Kit wrote:

> the problem was that title could non be a number (only a string), when we 
> create tiddler by 
> *if($tw.browser) {$tw.wiki.addTiddler(new 
> $tw.Tiddler($tw.wiki.getModificationFields(),fields,$tw.wiki.getCreationFields()))};*
> so I make .toString() to all values and now it works
>
> пятница, 20 августа 2021 г. в 16:11:06 UTC+3, Eric Shulman: 
>
>> On Friday, August 20, 2021 at 5:45:47 AM UTC-7 Siniy-Kit wrote:
>>
> Hi. I import data from this googlespreadsheet ... and get error
>>>
>> *Well, this is embarrassing. It is recommended that you restart 
>>> TiddlyWiki by refreshing your browser*
>>> *Uncaught TypeError: title.substr is not a function*
>>>
>>
>> I'm not certain, but I think you need a spreadsheet column with heading 
>> of "title", so the import knows what to name each imported 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/787db633-a143-40b3-b5f0-fbde9e7322a7n%40googlegroups.com.


[tw5] Re: Cannot use a variable from a filter. Can someone help me ?

2021-08-22 Thread TW Tones
I just had a quick look at your code

<$vars todayfilter="[get[task_date]compare:string:eg[]]

Try;
vars todayfilter="[all[current]get[task_date]compare:string:eg]"

Tones
On Monday, 23 August 2021 at 06:24:58 UTC+10 vpl wrote:

> Hi,
>
> I'm trying to run the following code (at the end of the message) which 
> uses a variable called 'target' (that contains the current date) into a 
> filter called todayfilter
>
> When I set the  todayfilter 
> <$vars todayfilter="[get[task_date]compare:string:eg[2021-08-22]]">
> All works fine (I mean the list <$list 
> filter="[regexp[db___]!sort[task_start_time]filter]"> 
>
> When I set the  todayfilter using the  variable (as in the code 
> below) this does not works. I've tested several syntax options without 
> success ...
>
> Any expert to tell me when the syntax is wrong ?
> Many thanks , Regards
> Vpl
>
> \define now_val()
> <$vars now_date=<>>
> <$vars  target={{{ [] }}}>
> <>
>
> <$vars todayfilter="[get[task_date]compare:string:eg[]]">
>
> 
>
> DateProjectTaskStartStop
> 
>   
>   //Number of tiddlers//
>   ''<$count 
> filter="[regexp[db___]filter]"/>''
>  
> <$list filter="[regexp[db___]!sort[task_start_time]filter]">
> 
> <$link><$view field="task_date"/>
> <$view field="tags"/>
> <$view field="task_comment"/>
> <$view field="task_start_time"/>
> <$view field="task_end_time"/>
> 
> 
> 
>
> \end
>
> <>
>

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


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

2021-08-22 Thread TW Tones
JW Are you on the specific instance of 
discourse? https://talk.tiddlywiki.org/

Regards
Tones

On Sunday, 22 August 2021 at 20:55:10 UTC+10 JWHoneycutt wrote:

> Signed up for Discourse - can't find any hits when searching "TiddlyWiki" 
> - did I just lose access to the community?
> JWH
>
> On Saturday, August 21, 2021 at 10:23:29 PM UTC-4 joshua@gmail.com 
> wrote:
>
>> Definitely moving over to the Discourse community. See you all there!
>>
>> Best,
>> Joshua Fontany
>> On Saturday, August 21, 2021 at 3:42:18 PM UTC-7 Scott Simmons 
>> (Secret-HQ) wrote:
>>
>>> I've created a profile on Talk.TiddlyWiki.org and am delighted with the 
>>> interface there.  I'll try to ask questions and create new threads there 
>>> rather than here, though I guess I'll be drawn back to Google Groups is 
>>> that's where the conversation flows.  (For my part, I'm hoping it moves to 
>>> Talk.TW)
>>>
>>> https://talk.tiddlywiki.org/u/secret-hq/
>>>
>>

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


[tw5] Re: Random html tags appear in my wiki

2021-08-21 Thread TW Tones
Try using advanced search to find where this content is found in the wiki, 
look at the tiddlers containing this and see if it has tags it should not.

The tiddler may have a tag such as  SystemTag: $:/tags/BelowStory 
, remove 
this to see if its fixed, if not re tag it and keep looking.

I expect a tiddler is broken or corrupt. 

Regards
Tones
On Saturday, 21 August 2021 at 15:02:59 UTC+10 Sandip Deshmukh wrote:

>
> I have a plain vanilla tiddlywiki with a couple of tiddlers.
>
> I copied this on my Android smartphone. And opened it with tiddloid.
>
> All went well till I was only viewing the tiddlers.
>
> But after I edited/ added new tiddlers, some html markup strings started 
> appearing at the very end. They are not part of any tiddler. And they 
> continue to show even after I close all the tiddlers and hide the sidebar.
>
> I copied the wiki back to my desktop and opened it with TiddlyDesktop. The 
> html markup strings continue to appear and behave the same way. I can 
> select them, copy them but can not delete them.
>
> There seems to be no problem with the wiki otherwise ---  I can open 
> tiddlers, edit tiddlers, etc.
>
> Here is what the text looks like:
>
> $tw.browser && !$tw.node) { $tw.passwordPrompt = new 
> $tw.utils.PasswordPrompt(); } // Preload any encrypted tiddlers 
> $tw.boot.decryptEncryptedTiddlers(function() { // Startup 
> $tw.boot.startup({callback: callback}); }); }; /// 
> Autoboot in the browser if($tw.browser && !$tw.boot.suppressBoot) { 
> $tw.boot.boot(); } return $tw; }); if(typeof(exports) !== "undefined") { 
> exports.TiddlyWiki = _boot; } else { _boot(window.$tw); } { 
> $tw.boot.boot(); } return $tw; }); if(typeof(exports) !== "undefined") { 
> exports.TiddlyWiki = _boot; } else { _boot(window.$tw); }
>
> How do I get rid of this annoyance?
>

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


[tw5] Re: We need more discourse about Discourse ... and not just the positives ...

2021-08-21 Thread TW Tones
Folks,

Personally I have used many kinds of forums and conversational systems and 
the good ones have a number of features that you find are needed and help 
both with communications and adoption. Discourse has many if not all these 
features, and sure they may be implemented differently in different 
solutions, but in the long run all of these are needed. It may take a 
little longer to get used to the way it works, but from my experience it is 
about what we need in the long run not simply what we may want initially.

With my experience I have found Discourse a walk in the park, with the odd 
little exception.  Why, because almost everything Discourse does or 
permits, is in a wide range of similar solutions. What I am trying to say 
is much of it is industry standard and learning Discourse will be reusable 
skills you can use in other places.  This is not just learning about a 
particular product but learning about the state of the art in collaboration 
systems. 

Sure we can criticise any system for sure, nothing is perfect, but if helps 
hearing someone experienced in such things such as myself, it is all going 
to be worth it, its moving forward in a big step and it is largely based on 
standard practices. I urge you to push through the barriers to change or 
the new because we will all be rewarded. 

I would also add, I have tried to get us to move before now and it was like 
herding cats, if we have any momentum at all I think we should move to an 
alternative, especially since Google has let us down big time. Eg No code, 
no mobile, are you kidding Google!

Regards
Tones
On Saturday, 21 August 2021 at 22:49:19 UTC+10 strikke...@gmail.com wrote:

> I signed up a few days ago and have looked around to get to know it - and 
> hopefully find something I liked about it. In between looking around and 
> reading- I started up a few "comfort" tiddlywikis.
>
> It looks rather complicated to me. Time will hopefully help.
> A lot of users over quite some time discussing tiddlywiki, and not forum 
> details will make it more interesting. But I realise that right now - it is 
> necessary to get the forum the way it can be - and users need help. - to 
> later be able to tell everyone else how easy it really is.
>
> Sorry - it might be my age.
>
> @Mohammad,
> The tutorial is nice and start when signing in - I wonder why so many did 
> not find it.
>

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


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

2021-08-20 Thread TW Tones
If node is set to 0.0.0.0 the IP address becomes server on the LAN at the 
current (or all) IP address(s) of the device.

On windows you can actually configure additional IP addresses on your 
desktop, and then rather than use 0.0.0.0 use the specific IP address. I 
have done this on bob but got it mixed up a few occasions. The smart trick 
is to assign an additional IP address outside the dhcp range and host your 
server on that but from your desktop. One day you may move your server and 
the additional IP address to another computer, say onto a NAS, server or 
always on computer - even a raspberry Pi.

Another nice tip is you can use any 127.X.X.X address on the local host as 
well so you keep 127.0.0.1 free for other services.

I can elaborate, I am just hinting here.

Regards
Tones
On Thursday, 19 August 2021 at 02:17:10 UTC+10 Stobot wrote:

> 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/504e001c-4840-447d-b339-ef2d7e5d94b7n%40googlegroups.com.


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

2021-08-20 Thread TW Tones
I will join the "me too" movement (to discourse of course :)

On Friday, 20 August 2021 at 13:24:49 UTC+10 fred@gmail.com wrote:

> moved over also
>
> On Thursday, 19 August 2021 at 14:40:24 UTC-4 PMario wrote:
>
>> On Thursday, August 19, 2021 at 8:11:12 PM UTC+2 R² wrote:
>>
>>> Switched too. Discourse is looking pretty good so far and indeed much 
>>> superior to GG. I did find the base config a bit spammy though, as users 
>>> are automatically registered as tracking a thread (and therefore receive 
>>> email alerts) after only 4 minutes with the thread open.
>>
>>
>> All those settings can be adjusted in your Preferences page. You can also 
>> "mute" a category if you want. So you don't get e-mailed at all. 
>>
>> -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/70dd200c-8f28-4271-892e-0c39e5954b3cn%40googlegroups.com.


Re: [tw5] Talk TiddlyWiki and the "discobot"

2021-08-19 Thread TW Tones
Mario,

For me start tutorial only gave me the same original post. I am not an 
admin!

[image: Snag_24a351e5.png]
I will look for a tutorial though

Thanks
Tones
On Friday, 20 August 2021 at 05:51:28 UTC+10 PMario wrote:

> On Thursday, August 19, 2021 at 9:43:13 PM UTC+2 Folke Hermansson Snickars 
> wrote:
>
>>
>> How can I come back to the discobot  tutorial if I missed it when I 
>> joined?
>>
>
> You should still have the message in your in-box. 
>
> You can restart the "conversation" when you reply with : start tutorial 
>
> [image: discobot-01.gif]
>
> -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/a8408657-6168-44d2-9fa8-0b5f7069d8c3n%40googlegroups.com.


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

2021-08-19 Thread TW Tones
Jamm

You can do a lot with tiddlywiki macros and widgets, perhaps an infinite 
amount without any javascript, but if you choose to build complex solutions 
you are also using html, css and Javascript technologies which are all 
reusable skills and essential knowledge for the internet.  

I would just make sure my data in tiddlywiki was logically arranged and not 
worry about the future its structure, technologies, tools and more all 
allow you to move your tiddlywiki data on to other places without any 
problems. Tiddlywiki is not a proprietary trap.

Tones
On Friday, 20 August 2021 at 07:23:05 UTC+10 jamm...@gmail.com wrote:

> Thanks for clarifying, Tones and Soren. I had the impression that 
> TiddlyWiki was more cookie cutter, or could be if I didn't add or alter 
> code. "A no-code personal wiki system," I heard TW called. But yes, I was 
> seeing this as a future-proofing mechanism where I might want to migrate 
> some- or everything stored in TiddlyWiki to a different platform in the 
> future.
>
> For more context, I was trying to set myself up to be able to transfer my 
> info from a digital garden on a more cookie cutter platform to a later less 
> cookie-cutter one, once I learned to code a bit. Starting 
> "non-technically," in the sense Maggie Appleton's articles  impressed on 
> me. 
>
> https://github.com/MaggieAppleton/digital-gardeners
> https://maggieappleton.com/nontechnical-gardening
>
> It seems I still misunderstand the question of going from a manageable 
> Digital Garden to a more complex one, not having data transfer be an issue.
> On Thursday, August 19, 2021 at 8:36:03 AM UTC-4 Soren Bjornstad wrote:
>
>> As Tones said, I think we need a bit more information about what you're 
>> hoping to accomplish to give a complete answer. Are you seeing this as a 
>> future-proofing mechanism where you *might* want to migrate something 
>> stored in TiddlyWiki to a different platform in the future? Or you want to 
>> use TiddlyWiki as a CMS and then publish using a different tool? Or 
>> something else?
>>
>> On a straightforward level, it's possible to quickly render some or all 
>> tiddlers to HTML, at which point you can post-process them using whatever 
>> tooling you want. I've been using this to crosspost my sabbatical updates 
>> from my Zettelkasten 
>>  to my 
>> Jekyll blog 
>> , 
>> using the following rule in my Makefile:
>>
>> sabbatical_updates := $(wildcard 
>> zettelkasten_dir/tiddlers/SabbaticalUpdate*)
>> sabbatical_files: $(sabbatical_updates)
>> rm -rf /tmp/twout
>> cd $(zettelkasten_dir) && tiddlywiki --output /tmp/twout --render 
>> "[prefix[SabbaticalUpdate/]]" "[is[tiddler]addsuffix[.html]]" "text/html" 
>> '$$:/sib/Templates/Export/SabbaticalUpdateCabCrosspost'
>> python3 automation/crosspost-sabbatical-updates.py 
>> /tmp/twout/SabbaticalUpdate/*
>>
>> The Python script is about 70 lines and primarily sets up a YAML header 
>> with appropriate metadata so Jekyll understands what to do with the post. 
>> This is also the purpose of the 
>> $:/sib/Templates/Export/SabbaticalUpdateCabCrosspost template -- it embeds 
>> certain fields in the HTML where this script can retrieve it. If you 
>> preferred, I think you could use pandoc at this point to convert back to 
>> Markdown or a similar format; since I'm keeping my source of record in 
>> TiddlyWiki, I'm fine just leaving the posts as HTML in Jekyll.
>>
>> Of course, if you take advantage of dynamic features of TiddlyWiki that 
>> can't be represented as HTML with 100% fidelity, e.g. dynamic lists based 
>> on filters or displays of backlinks, you'll end up losing some 
>> functionality when you do this.
>>
>> On Wednesday, August 18, 2021 at 2:31:10 PM UTC-5 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/ccd2aba8-eacb-48e5-9cd8-3b45b0e0409bn%40googlegroups.com.


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

2021-08-19 Thread TW Tones
Folks,

I am on air because of Boris and others help.

On discourse I am very happy, we have regained features lost in GG forums 
updates, dropping tiddlywiki title links on a thread converts it to a 
markup link and a lot more. I believe we have an integration for discourse 
comments on a published tiddlywiki, I will try and locate that. I can 
integrate discourse with WordPress to maybe continue with my idea 
of http://www.colabteam.net/tiddlywiki/

There are ways to apply an overlay to any webpage to refactor it to a more 
compact look, so if none of the themes help I would not give up. Also I 
don't concur with the criticisms when compared with google groups, Sure GG 
makes use the the real-estate a lot more but when deep in a thread there is 
way too much information on the screen you do not need. Whilst there is a 
lot of white space on discourse I would like to reduce, it has all the 
information one may want.

Reintroducing the ability to highlight code, edit after posting, and many 
other new features like private chats make this far superior the GG and in 
my mind a "no brainer" even if we want improvements.

Tones

On Friday, 20 August 2021 at 08:34:43 UTC+10 cj.v...@gmail.com wrote:

> Well, I say that ...
>
> If the theme doesn't make viewing a conversation thread full-screen, I'm 
> not going to enjoy that.
>
> Software that doesn't take advantage of the full desktop display width 
> turns me off.
>
> Is it just me or is discourse designed for mobile devices?
>
> On Thursday, August 19, 2021 at 7:13:51 PM UTC-3 Charlie Veniot wrote:
>
>> If this theme 
>>  
>> can be provided as an option, then I'm good.
>>
>> On Thursday, August 19, 2021 at 6:44:50 PM UTC-3 PMario wrote:
>>
>>> On Thursday, August 19, 2021 at 11:25:13 PM UTC+2 cj.v...@gmail.com 
>>> wrote:
>>>
 Yeah, just looked at it again.  Created an account to see if I can 
 customize the interface to be more GG looking, no dice.

 Love TiddlyWiki, *really* loathe that new forum.  Not convinced I'll 
 have the patience to deal with that interface.   Too many bells and 
 whistles going on.  Bare-bones minimalism is more my cup of tea.

>>>
>>> At the moment there is only 1 theme installed. .. But there seems to be 
>>> a possibility to add more. They should even be selectable by users. ... BUT 
>>> I have to read the docs first ... If I can find it ;)
>>>
>>> There are 16 popular themes that can be reviewed. .. So there are 
>>> probably more .. 
>>>
>>> We will see. 
>>>
>>> -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/a4890e83-41ca-4424-ba62-589010935d2an%40googlegroups.com.


Re: [tw5] Re: [ Streams ] future development plans

2021-08-19 Thread TW Tones
Thanks all Boris helped me out.

On Friday, 20 August 2021 at 00:28:33 UTC+10 Mohammad wrote:

> Tones,
>
>  I think Boris and  Mario are the Admin of Talk Tiddlywiki!
> It is good to ask from them!
>
>
>
>
>
> Best wishes
> Mohammad
>
>
> On Thu, Aug 19, 2021 at 5:29 PM TW Tones  wrote:
>
>> Fair enough, but I can't get access yet, there is a bug?, so it may be 
>> premature to make it a rule.
>>
>> Thanks for the presentation Saq.
>>
>> Tones
>>
>> On Thursday, 19 August 2021 at 19:01:43 UTC+10 Saq Imtiaz wrote:
>>
>>> Hi everyone,
>>>
>>> I've started a thread about future development plans for Streams 
>>> <https://talk.tiddlywiki.org/t/streams-future-development-sept-2021/147>
>>> .
>>>
>>> Please note that I will no longer be monitoring or replying to Streams 
>>> related matters on the Google Group. Please address any questions, comments 
>>> or feedback that you wish for me to see to either the Discourse forum 
>>> <https://talk.tiddlywiki.org/c/plugins/7> or Github 
>>> <https://github.com/saqimtiaz/streams>.
>>> Thank you.
>>>
>>> Regards,
>>> Saq
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/2e592a83-4850-4ded-bbfb-2cfb1d3da552n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/2e592a83-4850-4ded-bbfb-2cfb1d3da552n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

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


[tw5] Re: [ Streams ] future development plans

2021-08-19 Thread TW Tones
Fair enough, but I can't get access yet, there is a bug?, so it may be 
premature to make it a rule.

Thanks for the presentation Saq.

Tones

On Thursday, 19 August 2021 at 19:01:43 UTC+10 Saq Imtiaz wrote:

> Hi everyone,
>
> I've started a thread about future development plans for Streams 
> .
>
> Please note that I will no longer be monitoring or replying to Streams 
> related matters on the Google Group. Please address any questions, comments 
> or feedback that you wish for me to see to either the Discourse forum 
>  or Github 
> .
> Thank you.
>
> Regards,
> Saq
>

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


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

2021-08-19 Thread TW Tones
I am all for it but as posted elsewhere I am not getting the confirmation 
email and can't use my account.

Whos the admin? Help please.

Tones

On Tuesday, 17 August 2021 at 17:52:32 UTC+10 BurningTreeC wrote:

> Hi tiddlywikians,
>
> there's this new TiddlyWiki forum at https://talk.tiddlywiki.org/
>
> Is the google group still a thing for you or are you going to move to the 
> new Forum?
>
> just out of interest :)
>
> Best wishes,
> BTC
>

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


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

2021-08-19 Thread TW Tones
Trimming values, fieldnames and tiddler titles makes sense, there may 
however be a rare occasion where this is needed, however I think the hack 
would be to use a special space character (that is not trimmed) if you 
really needed.

Of course when possible allow the default to be overridden if needed, with 
a conscious action to do so. Just follow the standards eg in HTML input 
fields.

Tones



On Thursday, 19 August 2021 at 17:08:23 UTC+10 PMario wrote:

> On Thursday, August 19, 2021 at 12:33:29 AM UTC+2 Soren Bjornstad wrote:
>
> If I'm misunderstanding, please correct me (and can you link the 
>> discussions on GitHub?).
>>
>
> Sorry, I was talking about field values. 
>
> You are right, we should trim field names. There is some time left to do 
> so. But this question should be raised as a github issue. 
>
> -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/5261a18c-0194-4b35-b5a2-9a3c1b45229en%40googlegroups.com.


Re: [tw5] Seeking common misunderstandings

2021-08-18 Thread TW Tones
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

2021-08-18 Thread TW Tones
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

2021-08-18 Thread TW Tones
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?

2021-08-18 Thread TW Tones
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 

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

2021-08-18 Thread TW Tones
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] Re: Import tiddlers w/ json including custom fields

2021-08-18 Thread TW Tones
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.


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

2021-08-18 Thread TW Tones
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: I Think I Hacked TiddlyWiki

2021-08-18 Thread TW Tones
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 malicious javascript code, hidden 
>> in a data-uri to the server, which will sync it to all connected users is a 
>> concern...
>>
>> Best,
>> Joshua Fontany
>>
>> On Tuesday, August 17, 2021 at 10:12:13 AM UTC-7 TiddlyTweeter wrote:
>>
>>>  Mark S. wrote:
>>>
 That was one of the concerns with TWederation. You could import from 
 someone you trusted who imported from someone they trusted who ... 
 actually 
 couldn't be trusted. It's kind of a hard problem.

>>>
>>> *Right! *It IS an interesting issue. But *maybe as much an 
>>> anthropological issue as a technical one. *
>>> Suddenly tech switches into *"HOW CAN I TRUST?" *mode. 
>>> Despite the fact most everyone, well everyone, here (you, reading this) 
>>> is completely trust-worthy. 
>>> I think its a basic sociological fact that much of the internet is NOW 
>>> premised on the idea you can't trust anyone.
>>> It has led to a kind of "authentication gymnastics" that makes doing 
>>> some things very convoluted.
>>>
>>> Just rambles
>>> TT
>>>

 On Tuesday, August 17, 2021 at 8:13:42 AM UTC-7 saq.i...@gmail.com 
 wrote:

>
>> I'd be more concerned about people being tricked into importing a 
>> tiddler that contained code like this.
>>
>
> From my perspective this is the only practical concern, and once again 
> emphasizes the need to be careful when importing content from others. 
>


-- 
You received this message because you are subscribed to the Google Groups 

[tw5] Re: Scrollable Sidebar Tabs?

2021-08-16 Thread TW Tones
Thanks for Sharing I will test it out!

Tones

On Tuesday, 17 August 2021 at 02:08:37 UTC+10 amreus wrote:

> The attached is a sample of a scrollable More/All tab. Import it to 
> tiddlywiki.com.  I just think it it's a better experience than having the 
> entire sidebar scroll.
>
> I think an issue might be what height do you set the scrollble part to? 
> Could it be calculated from the existing sidebar-segments?
>
> <$scrollable class="tc-scrollable-demo">
> <$list filter={{$:/core/Filters/AllTiddlers!!filter}} 
> template="$:/core/ui/ListItemTemplate"/>
> 
>
> On Monday, August 16, 2021 at 10:43:19 AM UTC-4 amreus wrote:
>
>>
>> Another style question - is there one place where I can make all the 
>> sidebar tabs scrollable, or does each tiddler tagged $:/tags/SideBar 
>> and  $:/tags/MoreSideBar need to wrapped in a scrollable widget?
>>
>> Thanks. 
>>
>> I think all of the sidebar tabs should be scrollable by default so the 
>> entire sidebar does not scroll out of view. Or maybe all of the 
>> SidebarSegments above the tabs should be fixed position.
>>
>>
>>
>>

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


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

2021-08-16 Thread TW Tones
Charlie,

Whatever you wish but I feel I needed to clarify the innerwiki plugin can 
run on single file wikis and generate new single file wiki, like in an 
iframe., from where you can save it as a new single file wiki, if you 
wanted. Perhaps a good place to test.

Its purpose was for documentation snapshots which requires node, other 
applications of it do not need node.

Regards
Tones


On Monday, 16 August 2021 at 23:18:55 UTC+10 cj.v...@gmail.com wrote:

> Well, I'm more assuming than presuming that it is secure.
>
> Yup, template in my quick follow-up after initial post looks much nicer.
>
> Nah, I have not played with the Innerwiki plugin.  I largely prefer 
> single-file TiddlyWiki's, and Innerwiki seems to be for TiddlyWiki on 
> nodejs.  I'll try it sometime for giggles, but my goal here is the ability 
> to quickly add simple javascript needs with simple copy/paste  and without 
> javascript macros.
>
> I'm loving the speculation.  
>
>- In particular:  TiddlyWiki as an editor for creating web pages 
>(HTML, CSS, javascript)
>
>
> Be aware that the TiddlyWiki cannot see what is in the iFrame, and the 
> iFrame cannot see what is in the TiddlyWiki.
>
> *However and hypothetically*: the HTML fed to the iFrame can be dynamic 
> (i.e. the HTML created by TiddlyWiki, thus allowing TiddlyWiki to include 
> TiddlyWiki info in the HTML.  Interesting possibilities ...
>
>
>
>
>
> On Monday, August 16, 2021 at 1:21:58 AM UTC-3 TW Tones wrote:
>
>> Charlie,
>>
>> Thanks for this. 
>>
>>- I presume it is secure because the iframe acts like a sandbox
>>- The result will be what is displayed because there is no permitted 
>>way to impact the wiki
>>
>> I wonder if 
>>
>>- A template can be used rather than the variable? yes the following 
>>worked
>>
>>- Use a TiddlyWiki template for the content of the iframe may need to 
>>wikify first.
>>
>> Have you played with the* innerwiki plugin* it's similar but different? 
>> It can pass a lot more data to the iframe (I think), in fact can build a 
>> whole wiki inside the iframe.
>>
>> Speculation;
>>
>>- Could this be used by students of javascript?
>>- what kind of Javascript code can be implemented this way?
>>- Could it access functions defined in the parent wiki eg raw tags?
>>   - I suppose it could if added to the template.
>>- Could we use iframes in which to publish complete html pages 
>>including javascript as a website development or learning tool.
>>
>> Regards
>> Tones
>>
>> On Monday, 16 August 2021 at 12:39:05 UTC+10 cj.v...@gmail.com wrote:
>>
>>> Better to keep the HTML readable, drag the attached json with two 
>>> tiddlers into some TiddlyWiki:
>>>
>>> On Sunday, August 15, 2021 at 11:27:41 PM UTC-3 Charlie Veniot wrote:
>>>
>>>> I don't know what made me think of this.
>>>>
>>>> In case this has not been brought up in a while (I doubt this is new to 
>>>> seasoned folk) ...
>>>>
>>>> I was thinking: could I use an iFrame to include simple javascript in a 
>>>> tiddler without getting into macros or plugins that enable javascript.
>>>>
>>>> And, if I could, then could I set things up so that the iFrame is 
>>>> showing javascript dynamically created by the tiddler ?
>>>>
>>>> So here is a way to show a digital clock in TiddlyWiki, for 
>>>> non-programmers who just want to copy and paste javascript code from the 
>>>> web without figuring out how the javascript code works :
>>>>
>>>> Put this in a brand new tiddler:
>>>>
>>>> *<$vars* *vSrcDoc*={{{ [[  
>>>>   let clockEl = document.getElementById("clockDiv");function 
>>>> getClockTime() {  let date = new Date();  let hr = 
>>>> date.getHours();  let min = date.getMinutes();  let sec = 
>>>> date.getSeconds();  hr = ("0" + hr).slice(-2);  min = ("0" + 
>>>> min).slice(-2);  sec = ("0" + sec).slice(-2);  clockEl.innerHTML = 
>>>> `${hr}:${min}:${sec}`;}setInterval(getClockTime, 1000);  
>>>> ]] }}}*>*
>>>> *>* style="border:none;width:100%;"
>>>> *>*
>>>> **
>>>>
>>>> Sneaky sneaky, has me wondering what kind of other fun things could be 
>>>> done...
>>>>
>>>

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


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

2021-08-16 Thread TW Tones
Flank,

I can already see you contributing a lot to the community, thanks a lot. As 
Jeremy says you may need to unlearn and relearn a little to get right into 
tiddlywiki. I am myself intentionally a superuser, I do everything in the 
world of wiki text etc... There is very little we can't do without 
javascript except as Jeremy outlined. The key pieces are to me filters, 
wiki text and the widgets (especially the list widget).

You may learn to ask the question "can I do it natively in tiddlywiki?" It 
is mostly when you are brining in functions and API's you may need 
Javascript otherwise not so often.

About learning tiddlywiki, 

   - Ask here in the forum (as you are doing)
   - search tiddlywiki.com
  - Especialy https://tiddlywiki.com/#Community
  - Eg Grok Wiki 
  - Search https://links.tiddlywiki.com/
  - Search 
  https://tiddlywiki.com/#%22TiddlyWiki%20Toolmap%22%20by%20David%20Gifford
  - My Own resource especially 
   https://anthonymuscio.github.io/#Standard%20Nomenclature
   - There is a lot more out there so feel free to ask

Tones

On Tuesday, 17 August 2021 at 06:26:09 UTC+10 flanc...@gmail.com wrote:

> Thanks! I've already had a look around the Developer TW page, but, sadly, 
> it does seem lacking on so-much info. Instead, I've had to refer to various 
> posts/pages written by other community-members, but even those are 
> few-and-far between for some of what I want to know.
>
> On the note of calling the JS function, I would like to call a pre-defined 
> script in the startup folder, with the tiddler text as an argument. The 
> call would look like
> text_to_speech(TIDDLER TEXT HERE)
>
> Is this possible to do, or does it need a line in a .info file, or 
> something so that one can access the functions of the other?
>
> On Monday, August 16, 2021 at 4:17:04 PM UTC-4 jeremy...@gmail.com wrote:
>
>> Hi Finn
>>
>> Thanks Jeremy! I was able to get the button to show-up! I have a few more 
>>> stupid questions, if you have the time, mainly related to styling these 
>>> buttons and to wikitext.
>>>
>>> Firstly, I would like the colour of the button to change onhover. While 
>>> this is simple to do with CSS, I imagine it needs some sort of special 
>>> stylesheet (styles.tid, perhaps), to do this. It would be great if you 
>>> could share the syntax needed for this.
>>>
>>
>> As you inferred, there are two parts: (a) assign a class to the button 
>> and (b) create a stylesheet with a :hover rule. Stylesheets are ordinary 
>> tiddlers with the tag "$:/tags/Stylesheet", and (usually) the type 
>> "text/css".
>>
>> For dynamic effects, one can also use the wikitext type 
>> "text/vnd.tiddlywiki" and use wikitext primitives like <$list> to generate 
>> stylesheet rules dynamically.
>>  
>>
>>> Next and lastly, I am a bit confused as to how to implement this with 
>>> JS. I would like to be able to get the tiddler text, and then call a JS 
>>> function with this JS text as an argument. How could I go about getting the 
>>> tiddler text when the button is clicked, and then have this transfer over 
>>> to JS for the function call?
>>>
>>
>> It sounds like you want to make a view toolbar button that calls a JS 
>> function to do something with the text of a tiddler. There are quite a few 
>> ways to do that, and the precise details will depend on what you're trying 
>> to achieve. What does the JS function do with the text? Does it need to 
>> update the tiddler value in the store?
>>
>> The key types of JS modules in TW5 are as follows:
>>
>> * JS macros for simple deterministic text transformations that don't have 
>> any side effects (eg they cannot modify the tiddler store)
>> * Widgets for dynamic components that reflect values in the tiddler 
>> store, and automatically refresh if the values in the store change
>> * Filter operators for operations on lists of items. Again, they mustn't 
>> have side effects
>> * Savers for saving entire TiddlyWiki HTML files
>> * SyncAdaptors for saving/loading individual tiddlers to remote servers
>>
>> There are some docs at https://tiddlywiki.com/dev, and it's worth 
>> browsing the code over at GitHub:
>>
>> https://github.com/Jermolene/TiddlyWiki5/tree/master/core/modules
>>
>> Sorry if these questions are a bit basic, but I have yet to find a good 
>>> resource for learning WikiText/TW Syntax, so I have to rely on the 
>>> community and you. 
>>>
>>
>> Not at all. It sounds like you've plenty of experience of HTML, CSS and 
>> JS which puts you in a great position. Some of it will be a matter of 
>> unlearning some of the usual ways of doing things. TiddlyWiki is a 
>> different beast: it tries to make it easy to write complex apps 
>> declaratively by composing a small number of higher level primitives. But 
>> it also tries to have it's cake and eat it, in the way that it tries to 
>> expose the underlying flexibility of HTML, CSS and JS.
>>
>> Best wishes
>>
>> Jeremy
>>
>>

-- 
You received this message because you are 

[tw5] Re: how to filter on a field of a specific tiddler ?

2021-08-16 Thread TW Tones
Try this;

\define test_project() $:/temp/project-1
<$list filter="[get[alarms]!match[]]" variable="has_alarms">
   <>


When you go from a text reference transclusion 
"{$:/temp/project-1!!alarms}" to a filter "[get[alarms]" you 
can't just change half the text reference.

Tones

On Monday, 16 August 2021 at 22:48:03 UTC+10 vpl wrote:

> Hi,
>
> I'm blocking a the current issue.
> I want to apply a $listwidget on the value contained into a specific 
> tiddler variable
>
> The following code works fine
>
> \define test_project()$:/temp/project-1
> <$list filter="[{$:/temp/project-1!!alarms}!match[]]" 
> variable="has_alarms">
><>
> 
>
> But when I want to use the test_project macro name (defining the tiddler) 
> this does not works ..
> <$list filter="[{!!alarms}!match[]]" variable="has_alarms">
><>
> 
>
> Any idea that would help me ???
>
> Thanks a lot for your support
>
> 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/ef4a4218-901b-4c6c-96e0-1b155ea0b9a0n%40googlegroups.com.


[tw5] Re: !!! ''foo'' does not appear as bold

2021-08-16 Thread TW Tones
Can you give an example?

This works;

 This is a heading with ''bold'' in it

Tones

On Saturday, 14 August 2021 at 20:03:47 UTC+10 Sapphireslinger wrote:

> The heading wikitext cancels out the bold wikitext.
>
> I went to the control panel and looked through the palette editor but 
> couldn't find anything to edit to keep the H1 and H2  and H3 (etc) buttons 
> from interfering with the bold formatting. 
>
> I am using Vanilla theme.
>
> Thank you for any tips.
>

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


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

2021-08-16 Thread TW Tones
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.
> What a seasoned programmer would conceive and write in half an hour will 
> take hours --if not days-- for me to think about and assemble, and I am 
> overwhelmed with joy if it works, even if the resulting code would be 
> scoffed at by students, let alone their teachers, after a few months in a 
> 101 Programming class.
>
> Being both a perfectionist and a dabbler, one should never been given such 
> good advice as yours! They will  keep what you suggest in mind and want to 
> implement it without ever knowing how to get started! How terrible! ;-)
> My project is certainly not well-thought-out, and if it was, I would 
> probably need more code examples like the solution Eric Shulman kindly 
> provided me with. And TW v. 5.2.0 being in prerelease, I haven't looked 
> into it yet.
>
> I am aware that that TW project of mine is personal and is not designed to 
> be published. Unless I get struck with Alzheimer's disease soon --in which 
> case I won't need that project anymore--, for the moment I should be able 
> to remember its quirks when I use it. And there's room for improvement in 
> several other priority aspects of it. I am already spending way too much 
> time trying to achieve a project that probably wouldn't need all those 
> bells and whistles to work properly, to the detriment of other --as / 
> more-- meaningful projects. 
>
> Best,
>
> Stéphane
>
> Le lundi 16 août 2021 à 02:34:48 UTC+2, joshua@gmail.com a écrit :
>
>> We've found a bug!
>>
>> The wikitext parser object always tries to read Pragmas from the 
>> beginning to parse a text, and this _always_ trims whitespace from the text 
>> (moves the parser position past any leading whitespace).
>>
>> The $:/core/modules/parsers/wikiparser/wikiparser.js module needs to 
>> updated.
>>
>> The Parser's `this.skipWhiteSpace =` method needs to check the 
>> `this.configTrimWhiteSpace` value before moving the parser position, or 
>> reset the parser position if no pragmas are read, etc.
>>
>> This type of change should definitely have Jeremy's eye on it.
>>
>> I am terribly busy at work, so I will come back and file a Bug/Issue on 
>> GitHub if no-one else can.
>>
>> Best,
>> Joshua Fontany
>>
>> On Sunday, August 15, 2021 at 10:34:41 AM UTC-7 Misterel85 wrote:
>>
>>> Yay, it works!!! Thank you very much for your quick reply and your 
>>> simple and straightforward solution, Eric!
>>> After a bit of trial and error, I could adapt it to my TiddlyWiki.
>>> No need for an  anymore indeed.
>>> Thanks again to all of you for your help, solutions, explanations and 
>>> suggestions.
>>>
>>> Best,

[tw5] Re: Task for today on journal tiddler

2021-08-16 Thread TW Tones
Dasvidb

Without giving and testing a solution try a minor edit

schedule[

should read;
schedule
Which possibly means
g[-],[]]]

should read
g[-],[]]


Regards
Tones

On Monday, 16 August 2021 at 21:40:47 UTC+10 davidb...@gmail.com wrote:

> Hi everyone,
> I'm trying to create a template to show all the tasks for today, I use the 
> journal title as -0MM-0DD
> and i would like to filter something like this 
> [sameday:schedule[search-replace:g[-],[]]]
> if I hardcode the title it works [sameday:schedule[20210816]]
>

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


[tw5] Re: Highlighting duplicates in lists

2021-08-15 Thread TW Tones
Hio,

Back in my code

<$list filter="[all[]prefix[New]has[field]]">
   get[field]match{!!field}then[color: 
red;]] }}}>* <> {{!!field}}*




*<> {{!!field}} *is the display
replace this with 
*{{{ [all[current]get[field]format:date[]] }}}*
Not tested by me on this occasion

where field is the chosen fieldname.

Regards
Tones

On Monday, 16 August 2021 at 12:14:51 UTC+10 mohamed...@hotmail.com wrote:

> Thank you tones
>
> The real life example is to evaluate duplicate dates, so the actual real 
> values populating the fields are not  1 ,2 , etc.. they are actual dates , 
> IE . 2021062506295,   20210811055859000,etc.
> and so what i was trying is to  do is have the highlighted duplicate 
> values converted from the tiddly wiki format they are stored in in their 
> respective fields , to a normal readable format when displayed in the filter
>
> the
> On Monday, August 16, 2021 at 2:34:07 AM UTC+2 TW Tones wrote:
>
>> Mohammad,
>>
>> I am confused, until now the fields  field_example,  field_example1,  
>> field_example2 did not contain dates. 
>>
>>- Are you trying to convert these to dates?
>>- the view widget format=date only works on tiddlywiki full serial 
>>number dates!
>>
>> Perhaps step back and describe what you want to do in the real world, not 
>> with tiddlywiki code that may or may not be correct. 
>>
>> Regards
>> Tones
>>
>> On Monday, 16 August 2021 at 01:46:55 UTC+10 mohamed...@hotmail.com 
>> wrote:
>>
>>> HI tones,
>>>
>>> sorry i guess i asked the wrong question, what i wanted to know is where 
>>> to place the widget  in the code , if i do it that way , it no longer 
>>> highlights duplicates
>>>
>>>  <>: |  
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> variable=field-value>
>>> <$view field="field_example "format=date template=""/>
>>> <$view field="field_example1"format=date template=""/>
>>> <$view field="field_example2"format=date template="YYYY"/>
>>>
>>>  matchthen[color: 
>>> red;]] }}}><>
>>>
>>> 
>>>
>>> i also tried  adding format:date[DDD]] , which didn't yield any results 
>>>
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> format:date[DDD]] variable=field-value> 
>>> On Sunday, August 15, 2021 at 10:12:57 AM UTC+2 TW Tones wrote:
>>>
>>>> Look for and use the viewWidget and use the format date with a 
>>>> template, or the format relativedate
>>>>
>>>> Get into the habit also of searching in tiddlywiki.com to learn how to 
>>>> do things.
>>>> [image: Snag_c8a06a9.png]
>>>>
>>>> eg;
>>>>
>>>> <$view field=created format=date template=""/>
>>>>
>>>> <$view field=created format=relativedate/>
>>>>
>>>>  5.1.23 now allows this inside filters. 
>>>> <https://tiddlywiki.com/#format%20Operator%20(Examples)>
>>>>
>>>> Regards
>>>> Tones
>>>>
>>>> On Sunday, 15 August 2021 at 10:26:32 UTC+10 mohamed...@hotmail.com 
>>>> wrote:
>>>>
>>>>> Sorry one more questions
>>>>>
>>>>> if the values are dates, how can they be displayed in normal format 
>>>>> ,and not the tiddly wiki format
>>>>>
>>>>> On Monday, August 9, 2021 at 1:10:18 AM UTC+2 paulgilbert2000 wrote:
>>>>>
>>>>>> Thank you tones
>>>>>>
>>>>>> Will take me a while to understand all that . but it works like a 
>>>>>> charm , and its even more than what i have asked for
>>>>>>
>>>>>> thanks again:)
>>>>>>
>>>>>> On Sunday, August 8, 2021 at 7:31:10 AM UTC+2 TW Tones wrote:
>>>>>>
>>>>>>> Mohamad,
>>>>>>>
>>>>>>> I am happy to look at solving the problem presented but my suspicion 
>>>>>>> remains that there may be a different way to put the question in the 
>>>>>>> first 
>>>>>>> place. 
>>>>>>>
>&

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

2021-08-15 Thread TW Tones
Charlie,

Thanks for this. 

   - I presume it is secure because the iframe acts like a sandbox
   - The result will be what is displayed because there is no permitted way 
   to impact the wiki

I wonder if 

   - A template can be used rather than the variable? yes the following 
   worked
   
   - Use a TiddlyWiki template for the content of the iframe may need to 
   wikify first.

Have you played with the* innerwiki plugin* it's similar but different? It 
can pass a lot more data to the iframe (I think), in fact can build a whole 
wiki inside the iframe.

Speculation;

   - Could this be used by students of javascript?
   - what kind of Javascript code can be implemented this way?
   - Could it access functions defined in the parent wiki eg raw tags?
  - I suppose it could if added to the template.
   - Could we use iframes in which to publish complete html pages including 
   javascript as a website development or learning tool.

Regards
Tones

On Monday, 16 August 2021 at 12:39:05 UTC+10 cj.v...@gmail.com wrote:

> Better to keep the HTML readable, drag the attached json with two tiddlers 
> into some TiddlyWiki:
>
> On Sunday, August 15, 2021 at 11:27:41 PM UTC-3 Charlie Veniot wrote:
>
>> I don't know what made me think of this.
>>
>> In case this has not been brought up in a while (I doubt this is new to 
>> seasoned folk) ...
>>
>> I was thinking: could I use an iFrame to include simple javascript in a 
>> tiddler without getting into macros or plugins that enable javascript.
>>
>> And, if I could, then could I set things up so that the iFrame is showing 
>> javascript dynamically created by the tiddler ?
>>
>> So here is a way to show a digital clock in TiddlyWiki, for 
>> non-programmers who just want to copy and paste javascript code from the 
>> web without figuring out how the javascript code works :
>>
>> Put this in a brand new tiddler:
>>
>> *<$vars* *vSrcDoc*={{{ [[
>> let clockEl = document.getElementById("clockDiv");function 
>> getClockTime() {  let date = new Date();  let hr = 
>> date.getHours();  let min = date.getMinutes();  let sec = 
>> date.getSeconds();  hr = ("0" + hr).slice(-2);  min = ("0" + 
>> min).slice(-2);  sec = ("0" + sec).slice(-2);  clockEl.innerHTML = 
>> `${hr}:${min}:${sec}`;}setInterval(getClockTime, 1000);  
>> ]] }}}*>*
>> *>* style="border:none;width:100%;"
>> *>*
>> **
>>
>> Sneaky sneaky, has me wondering what kind of other fun things could be 
>> done...
>>
>

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


[tw5] Re: Presenting Text-to-Speech v1.0.0: the flip-side of Speech-to-Text!

2021-08-15 Thread TW Tones
Flanc,

Exciting and thanks for this. I am getting my firefox menus with  
Alt+Shift+E

In chrome I heard it momentarily only. I will experiment further.

Regards
Tones

On Monday, 16 August 2021 at 00:00:45 UTC+10 flanc...@gmail.com wrote:

> After seeing some recommendations for a text-to-speech plugin in TW5 while 
> releasing the Speech-to-Text plugin v1.0.5 with BTC, I took it upon myself 
> to make my first solo plugin: text-to-speech!
>
> *How does it work?*
> Text-to-Speech uses the web text-to-speech API, which functions like a 
> screen reader. To apply this to TiddlyWiki, I made a custom function 
> calling this API, which then takes as arguments a selected area of text 
> using cutom code I wrote!
>
> *Get Started!*
> To get started with the plugin, you can install by drag-and-drop from 
> text-to-speech.finnsoftware.net! Then, anywhere in your TiddlyWiki, you 
> can highlight text, and press the hotkey Alt+Shift+E, and listen to the 
> plugin read the text to you!
>
> *What to Expect in the Future?*
>
>- test for foreign language support
>- test support across browsers
>- button in toolbar/editing
>
>

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


[tw5] Re: Highlighting duplicates in lists

2021-08-15 Thread TW Tones
Mohammad,

I am confused, until now the fields  field_example,  field_example1,  
field_example2 did not contain dates. 

   - Are you trying to convert these to dates?
   - the view widget format=date only works on tiddlywiki full serial 
   number dates!

Perhaps step back and describe what you want to do in the real world, not 
with tiddlywiki code that may or may not be correct. 

Regards
Tones

On Monday, 16 August 2021 at 01:46:55 UTC+10 mohamed...@hotmail.com wrote:

> HI tones,
>
> sorry i guess i asked the wrong question, what i wanted to know is where 
> to place the widget  in the code , if i do it that way , it no longer 
> highlights duplicates
>
>  <>: |  
><$list filter="[all[current]get[field_example]] 
> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
> variable=field-value>
> <$view field="field_example "format=date template=""/>
> <$view field="field_example1"format=date template=""/>
> <$view field="field_example2"format=date template=""/>
>
>  matchthen[color: red;]] 
> }}}><>
>
> 
>
> i also tried  adding format:date[DDD]] , which didn't yield any results 
>
><$list filter="[all[current]get[field_example]] 
> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
> format:date[DDD]] variable=field-value> 
> On Sunday, August 15, 2021 at 10:12:57 AM UTC+2 TW Tones wrote:
>
>> Look for and use the viewWidget and use the format date with a template, 
>> or the format relativedate
>>
>> Get into the habit also of searching in tiddlywiki.com to learn how to 
>> do things.
>> [image: Snag_c8a06a9.png]
>>
>> eg;
>>
>> <$view field=created format=date template=""/>
>>
>> <$view field=created format=relativedate/>
>>
>>  5.1.23 now allows this inside filters. 
>> <https://tiddlywiki.com/#format%20Operator%20(Examples)>
>>
>> Regards
>> Tones
>>
>> On Sunday, 15 August 2021 at 10:26:32 UTC+10 mohamed...@hotmail.com 
>> wrote:
>>
>>> Sorry one more questions
>>>
>>> if the values are dates, how can they be displayed in normal format ,and 
>>> not the tiddly wiki format
>>>
>>> On Monday, August 9, 2021 at 1:10:18 AM UTC+2 paulgilbert2000 wrote:
>>>
>>>> Thank you tones
>>>>
>>>> Will take me a while to understand all that . but it works like a charm 
>>>> , and its even more than what i have asked for
>>>>
>>>> thanks again:)
>>>>
>>>> On Sunday, August 8, 2021 at 7:31:10 AM UTC+2 TW Tones wrote:
>>>>
>>>>> Mohamad,
>>>>>
>>>>> I am happy to look at solving the problem presented but my suspicion 
>>>>> remains that there may be a different way to put the question in the 
>>>>> first 
>>>>> place. 
>>>>>
>>>>> Sometimes a question can be rephrased such that the answer is simpler 
>>>>> to find.
>>>>>
>>>>>- In this we have multiple tiddlers, with multiple fields, with 
>>>>>*values* that may be duplicated across these tiddlers/fields.
>>>>>- in effect you want to list all tiddlers using the select fields, 
>>>>>list these for each tiddler then for each found value
>>>>>   -  detect when that value occurs in any other tiddler (not 
>>>>>   self?) or select fields, if it does highlight it.
>>>>>- I am not sure why you want to do this and can think of many ways 
>>>>>to list/interpret the data! 
>>>>>- What about triplicates?
>>>>>- What about duplicates in the same tiddler?
>>>>>
>>>>> I think using your test data this is what you wanted?
>>>>>
>>>>> 
>>>>> <$list filter="[all[]has[field_example]]">
>>>>><$set name=other-values 
>>>>> filter="[all[]!get[field_example]] 
>>>>> [all[]!titleget[field_example2]] 
>>>>> [all[]!titleget[field_example3]] +[sort[]]">
>>>>><>: |  
>>>>><$list filter="[all[current]get[field_example]] 
>>>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>>>> variable=field-value>
>>>>> >>>> [enlistmatchthen[color: red;]] 
>&

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

2021-08-15 Thread TW Tones
Misterel,

I believe I understand what you are trying todo. Yet I would persist in 
suggesting you separate the data from its presentation. 

Of course its is fine to use the pragmatic approach as you wish.

What I would do is build the concatenation process to always include a 
space between elements, no leading or trailing spaces needed, except when 
it starts with period or any other exceptions you identify.

Basically I would get the logic to handle the language concatenation and 
leave such fiddling, outside of the data. Ideally I would even leave 
leading commas out of the data as this is again all about presentation eg 
if I have a list of three items the first is separated from the second by a 
comma the third by "and". and the full stop comes at the very end. ie just 
store the items because you need not know how you will use them in the 
future and when using them format according to the presentation. The recent 
and next version 5.2.0 contains some support for this first, seconds and 
last treatment such as with the counter variable, even css can handle this.

Experience has shown me such an approach is actually much simpler in the 
short term and few exceptions are required, where the approach you are 
taking will ultimately be the opposite, more complex and have more 
exceptions, while also loosing flexibility.

But yes you are an autonomous being :) do what you want.

Tones
On Monday, 16 August 2021 at 03:34:41 UTC+10 Misterel85 wrote:

> Yay, it works!!! Thank you very much for your quick reply and your simple 
> and straightforward solution, Eric!
> After a bit of trial and error, I could adapt it to my TiddlyWiki.
> No need for an  anymore indeed.
> Thanks again to all of you for your help, solutions, explanations and 
> suggestions.
>
> Best,
> -Stéphane
>
> Le dimanche 15 août 2021 à 18:01:55 UTC+2, Eric Shulman a écrit :
>
>> On Sunday, August 15, 2021 at 7:10:39 AM UTC-7 Misterel85 wrote:
>>
>>> I first thought there would have been a more straightforward solution to 
>>> that issue, but actually I come to think that it should be possible to 
>>> inspect the first character in the contents of field 2:
>>> If value of field2 starts with space, then insert `` between the 
>>> transclusions, else just proceed with both transclusions.
>>>
>>
>> Try this:
>> <$transclude field="field1"/><$text text={{{ 
>> [{!!field2}split[]first[]match[ ]] }}}/><$transclude field="field2"/>
>>
>> Notes:
>> * The {{{ [...] }}} is a "filtered transclusion"
>> * The filter starts by getting the value of the desired field, using 
>> {!!field2}
>> * It then splits that value into separate characters, using split[]
>> * Next, it gets just the first character, using first[]
>> * and compares it with a space, using match[ ]
>> * The result of the filter is either nothing, or an actual space 
>> character (not an )
>> * The <$text> widget then converts the output to plain text (instead of 
>> displaying a link to a space!)
>>
>> 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/dc56b6c3-cf1e-4a76-b865-c823bfd8923dn%40googlegroups.com.


[tw5] Re: convert date in a text field to date format

2021-08-15 Thread TW Tones
Format  T.  ?

Surely you mean "0DD. MMM "

In this case you would parse this date to extract the DD, MMM and  as 
separate values, convert from MMM to a month number with a 12 month table, 
then re-assemble them into a tiddlywiki date/time string. I suggest 1200 or 
12 noon as the time, otherwise zero fill seconds and milliseconds.

eg D all before ".", 
Month split[ ]nth[2]
Year split[ ]nth[3] or last[]

Regrds
Tones
On Monday, 16 August 2021 at 09:47:47 UTC+10 Mark S. wrote:

> @ Eric
>
> Just tried 
>
> <>
>
> and got a hard RSOE ("from" not defined). I think the arguments need to be 
> tweaked in the macro.
>
> HTH
> On Friday, August 13, 2021 at 2:53:09 PM UTC-7 Eric Shulman wrote:
>
>> On Friday, August 13, 2021 at 12:36:11 AM UTC-7 S² wrote:
>>
>>> I use a created text field 'published', which will be filled with a date.
>>> (This date can also be in the future)
>>> format is *T.  * - (eg. *7. April 2021* or *13. August 2021*).
>>>
>>> 1. How can this be converted into a date format?
>>>
>>
>> I have just added a new javascript macro to the TiddlyTools timer package.
>>
>> https://tiddlytools.com/timer.html#TiddlyTools%2FTime%2FConvertDate
>>
>>- To convert a date to a different format, use <>from:inputdate to:outputformat>>.
>>- The input date can use any date format recognized by the Javascript 
>>Date.parse() function. Generally this conforms to *ISO 8601 standard 
>>date format*. 
>>- The output format uses TiddlyWiki Date Format codes 
>>, and defaults to 
>>*[UTC]0MM0DD0hh0mm0ss0XXX*.
>>
>> 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/cc381b92-116b-4665-bd16-9ebe4decf23cn%40googlegroups.com.


[tw5] Re: Help please for indicators in SideBar

2021-08-15 Thread TW Tones
Folks,

I said I would share the result back, and it is attached so far. 

It is largely working very nicely, later I will package a range of 
indicators with it as I develop them.

However it still has a problem.

   - The attached JSON has a few tiddlers, which displays indicators 
   (icons/buttons tagged $:/tags/indicator) just above the sideBar tabs
   - It currently only comes with one indicator, an info icon with a 
   tooltip about itself.

Unfortunately there is an artifact, no doubt a clash with the CSS I am 
using.
eg class="tc-btn-invisible" on the button.

Regards
Tones
On Saturday, 14 August 2021 at 18:39:08 UTC+10 TW Tones wrote:

> Télumire,
>
> Hey thanks soo much, that is exactly what I needed.
>
> I have adopted the final css as follows to get smaller icons that the 
> PageControls.
>
> .indicator-container { display:block; margin-top: -15px; margin-bottom: 
> -22px; line-height:unset; } .indicator-item{ height:15px; width:15px; 
> display:inline-block; position:relative; } .indicator-item button, 
> .indicator-item button * { width:100%!important; height:100%!important; 
> padding:unset; margin:unset; display:inline-block; left:0; top:0; }
>
> I will shareback my indicators "bar" macro shortly
>
> Regards
> Tones
>
> On Friday, 13 August 2021 at 04:16:44 UTC+10 Télumire wrote:
>
>> Erratum bis (sorry..) :
>>
>> .indicator-container {
>> display: flex;
>> flex-wrap:wrap;
>> margin-top: -14px;
>> margin-bottom: -26px;
>> --indicator-size:10px;
>> }
>>
>> .indicator-item{
>> height:var(--indicator-size);
>> width:var(--indicator-size);
>> display:inline-block;
>> position:relative;
>> }
>>
>> .indicator-item button, .indicator-item button * {
>> position:absolute;
>> width:100%!important;
>> height:100%!important;
>> padding:unset;
>> margin:unset;
>> left:0;
>> top:0;
>> }
>>
>> Should I send further replies by private message to avoid spam ?
>>
>>
>> Le jeudi 12 août 2021 à 20:02:22 UTC+2, Télumire a écrit :
>>
>>> Erratum : no need for the line-height:unset nor the inline-block for the 
>>> button and its content :
>>
>>
>>>
>>> .indicator-container {
>>> display:block;
>>> margin-top: -14px;
>>> margin-bottom: -26px;
>>> }
>>>
>>> .indicator-item{
>>> height:40px;
>>> width:40px;
>>> display:inline-block;
>>> position:relative;
>>> }
>>>
>>> .indicator-item button, .indicator-item button * {
>>> width:100%!important;
>>> height:100%!important;
>>> padding:unset;
>>> margin:unset;
>>>
>> left:0;
>>> top:0;
>>> }
>>>
>>> Le jeudi 12 août 2021 à 20:00:09 UTC+2, Télumire a écrit :
>>>
>>>> Ok now I understand what you mean … This is because tiddly wiki wrap 
>>>> the content in a  tag, which has a margin of 14px. So to fix that, 
>>>> since 
>>>> we can't style an element based on it's content (at least not until the 
>>>> pseudo-class :has is supported) nor give it a class (as far as I know), we 
>>>> need to wrap the indicators in a container and use it to compensate with 
>>>> negative margin.
>>>>
>>>> The code becomes :
>>>>
>>>> \whitespace trim
>>>> 
>>>> 
>>>> {{$:/core/ui/Buttons/edit}}
>>>>  
>>>> ..etc..
>>>> 
>>>> {{$:/core/ui/Buttons/cancel}}
>>>> 
>>>>  
>>>>
>>>> And the css becomes 
>>>>
>>>> .indicator-container {
>>>> display:block;
>>>> margin-top: -14px;
>>>> margin-bottom: -26px;
>>>> line-height:unset;
>>>> }
>>>>
>>>> .indicator-item{
>>>> height:40px;
>>>> width:40px;
>>>> display:inline-block;
>>>> position:relative;
>>>> }
>>>>
>>>> .indicator-item button, .indicator-item button * {
>>>> width:100%!important;
>>>> height:100%!important;
>>>> padding:unset;
>>>> margin:unset;
>>>> display:inline-block;
>>>> left:0;
>>>> top:0;
>>>> }
>>>> Le jeudi 12 août 2021 à 08:22:19 UTC+2, TW Tones a écrit :
>>>>
>>>>> Télumire
>>>>>
>>>>> I just tried this on tiddlywiki.com;
>>>>>
>>>>> Thanks, we are almost 

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

2021-08-15 Thread TW Tones
I think you can have your cake and eat it, as long as you use the 
tiddlywiki recipe/ingredients.

First lets see if I can explain about order.

If this was my first design (with space between them)
<$transclude field="field1" /> <$transclude field="field2" />

And I decided I wanted;
<$transclude field="field2" /> <$transclude field="field1" />


   - I modify the presentation in the above code, I do not need to modify 
   my data, just its presentation. This may be happening inside a list widget 
   for example.
   - In your case you may need to change both the presentation and the data.


Now, If I understand correctly you want to correctly treat the joining of 
"snipits" found in fields correctly, you would be better served building 
some standards for your data and tools to do the joining. Since there are 
already implied standards for handling those values lets adopt them, then 
if you can identify occasions where appending one snippet to the other by 
separation with a space, is not working, let us detect and alter that case.

In the original post I think you go down the path of altering the way they 
are presented by modifying the data.

*Could you give us some examples where you are finding it hard to join such 
snippets?*

I would suggest {{!!foo}}{{!!bar}} for your first example (As did 
Mario)

Tones

On Sunday, 15 August 2021 at 22:54:39 UTC+10 Misterel85 wrote:

> Thank you for your replies, PMario, Joshua and Tones.
>
> @ Joshua: Thanks a lot for taking the time to write this comprehensive and 
> clear explanation.
>
> I have followed your solution to insert `\whitespace notrim` at the 
> beginning of a tiddler text, but unfortunately, it doesn't work.
>
> I also tried to place it into a macro like this:
>
> ```
> \define mymacro()
> \whitespace notrim
> <$transclude field="field1" /><$transclude field="field2" />
> \end
> ```
>
> but in vain. In the documentation , the 
> default is set to 'notrim', so adding such an instruction in a macro is 
> useless.
>
>
> @ PMario:
>
> I am aware of the solution you provide, but inserting a normal or 
> non-breakable space between the two transclusions is not an option.
>
> A very simplified example of what I would like to do is connecting two 
> parts of something similar to a sentence together, but that sentence may 
> not need a complement in the second part.
> For instance:
> if field1 contains: 'The cat is eating'
> field2 might contain: ' a mouse.' or ' cat food.' (note the space), or '.' 
> (no space required before a full stop / period).
>
> Your solution would always insert a space, even before a punctuation sign 
> such as a period or a comma...
>
>
>
> @ Tones
>
> Your advice is worth following 'for standard use cases'. But what I wish 
> to implement is probably not an ordinary one.
>
> You wrote:
>
>- The spacing you wish is something best done in the display of the 
>data and not in the data, what if they changed order? 
>
>
> I don't understand what you mean by 'what if they changed order?'.
> What would change order? The data? The fields? No, I wouldn't need to 
> change their order. See my example above. Why would I need the 
> 'complementary' part of the data to show before the 'main' part?
>
> As for the spacing, it is an integral part of the data here (as a word 
> separator within a sencence, for instance). Therefore putting it anywhere 
> else in this case wouldn't be a wise choice.
>
>
>- A field containing a list of titles or tiddlers is typically space 
>delimited. So we often need the leading and trailing spaces not to be 
>included.
>
>
> Sure, but that's not my use case. And 'often' is not 'always'! ;-)
>
>
>- You can access fields in a different way if you really need to have 
>leading or training spaces as part of the data
>
>
> Well, that's exactly what I'm after!
>
>
> > '{{{ [all[current]get[afield]] }}}'
>
> > The transcluded filter output demonstrates the field contains a leading 
> space of it has one.
>
> That filter output is interesting. But it doesn't render HTML tags or 
> Wikitext, contrary to $transclude.
> If 'afield' contains: ` This is my //field//. `, 
> then 
> '{{{ [all[current]get[afield]] }}}'
> '<$text text={{{ [all[current]get[afield]] }}} />'
> '<$view field=afield />'
> all render raw text as: 
> ' This is my //field//. '
> whereas
> '<$transclude field=afield/>'
> renders as:
> 'This is *my* *field*.'
>
> Seems that I have to trade in the leading space for formatting and 
> vice-versa. Can't have my cake and eat it.
>
> Regards,
>
> Stéphane
>
>
>

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


[tw5] Re: System and shadow need some love

2021-08-15 Thread TW Tones
Post script,

In line with the OT, I also though we could have a system-caption field 
that is searched Along with standard tiddlers, so system tiddlers would 
have the option of "publishing themselves" in the standard search. eg the 
tag manager, if you search for it in empty you will not find it, as it 
exist in a system tiddler  $:/TagManager if we gave this a system-caption = 
"Tag Manager" then this system tiddler would be found although it is a 
system tiddler.

This is a somewhat simple core change, or hack.

Regards
Tones
On Sunday, 15 August 2021 at 18:25:39 UTC+10 TW Tones wrote:

> I am late to this thread but I have designed a method called advanced 
> search indicators. Below
>
> There is already a feature to support tabs see $:/tags/SearchResults 
> <https://tiddlywiki.com/#SystemTag%3A%20%24%3A%2Ftags%2FSearchResults>
> additional tabs appear in the standard search drop down if you tag some 
> search tabs, *although I am not keen on this method*.
>
> eg make a tiddler tagged $:/tags/SearchResults and the field caption = 
> System and include the below, now search in the sidebar
> \define searchResultList()
>
> //Search System Tiddlers//
> //{{$:/language/Search/Matches/Title}}//
> <$list 
> filter="[is[system]search:title{$(searchTiddler)$}sort[title]limit[250]]" 
> template="$:/PSaT/ExtendedSearch/ListItemCaptionTemplate"/>
>
> //{{$:/language/Search/Matches/All}}//
>
> <$list filter="[is[system]search{$(searchTiddler)$}sort[title]limit[250]]" 
> template="$:/PSaT/ExtendedSearch/ListItemCaptionTemplate"/>
>
> \end
> <>
>
> *Advanced search indicators - design concept*
>
>- What it does is monitor the content if the standard search entry and 
>does much of what you want, ie starts with $ searches for system tiddlers, 
>or allows you to open a tiddler if it exists and a lot, lot more. 
> Basically 
>additional icons appear that if clicked will do something based on the 
>content of the search temp field. eg list all items with the current 
> search 
>string as a prefix...
>
> I will publish this one day, and sooner if someone can sponsor me.
>
> Tones
>
>
>
> On Sunday, 15 August 2021 at 10:23:56 UTC+10 springer wrote:
>
>> David, I'm confused why you see 5 steps to get to advanced search. 
>>
>> Control-Shift-A opens the Advanced Search tiddler and puts your cursor in 
>> the search field... The tab is whatever you last chose, so often there's 
>> only the one quick step. 
>>
>> Your other points are important (and I too use advanced search about as 
>> often as the standard search), but this "5-steps" description misses the 
>> keyboard shortcut...
>>
>> -Springer
>>
>> On Saturday, August 14, 2021 at 10:10:44 AM UTC-4 David Gifford wrote:
>>
>>> I hate the loss of the edit post button on this forum. 
>>>
>>> I forgot a point: the actual steps are four, before you can enter your 
>>> search term in $:/Advanced search:
>>>
>>> 1. Move from what you are doing in the story river, to the sidebar.
>>> 2. Resist the urge to do a regular search, and instead click 
>>> $:/AdvancedSearch button.
>>> 3. Switch your attention back to the story river to view 
>>> $:/AdvancedSearch.
>>> 4. Pick a tab
>>> 5. Then and only then can you enter your search string.
>>>
>>> Instead, what I am proposing is
>>>
>>> 1. Move from what you are doing in the story river, to the sidebar. 
>>> 2. Enter search string in regular search bar **as step two, rather than 
>>> step five**
>>> 3. Pick a tab and see results
>>> 4. Refine search string if needed
>>>
>>> On Saturday, August 14, 2021 at 10:01:54 AM UTC-4 David Gifford wrote:
>>>
>>>> Hi everyone
>>>>
>>>> I am playing with the field-search plugin by PMario, and seeing how 
>>>> search results for a simple search come up in tabs one can pick from.
>>>>
>>>> This made me wonder, why couldn't there be something similar: do a 
>>>> search from the default searchbar, and have standard, system and shadow 
>>>> come up as tabs? 
>>>>
>>>> This seems like it would be much more intuitive for users: search, then 
>>>> filter results. As it stands, $:/AdvancedSearch does the opposite: it 
>>>> makes 
>>>> you pick a type of search (standard, system, shadow, filter) first, and 
>>>> only then can you do the search. The search string you want to enter may 
>>>> or

[tw5] Re: System and shadow need some love

2021-08-15 Thread TW Tones
I am late to this thread but I have designed a method called advanced 
search indicators. Below

There is already a feature to support tabs see $:/tags/SearchResults 

additional tabs appear in the standard search drop down if you tag some 
search tabs, *although I am not keen on this method*.

eg make a tiddler tagged $:/tags/SearchResults and the field caption = 
System and include the below, now search in the sidebar
\define searchResultList()

//Search System Tiddlers//
//{{$:/language/Search/Matches/Title}}//
<$list 
filter="[is[system]search:title{$(searchTiddler)$}sort[title]limit[250]]" 
template="$:/PSaT/ExtendedSearch/ListItemCaptionTemplate"/>

//{{$:/language/Search/Matches/All}}//

<$list filter="[is[system]search{$(searchTiddler)$}sort[title]limit[250]]" 
template="$:/PSaT/ExtendedSearch/ListItemCaptionTemplate"/>

\end
<>

*Advanced search indicators - design concept*

   - What it does is monitor the content if the standard search entry and 
   does much of what you want, ie starts with $ searches for system tiddlers, 
   or allows you to open a tiddler if it exists and a lot, lot more. Basically 
   additional icons appear that if clicked will do something based on the 
   content of the search temp field. eg list all items with the current search 
   string as a prefix...

I will publish this one day, and sooner if someone can sponsor me.

Tones



On Sunday, 15 August 2021 at 10:23:56 UTC+10 springer wrote:

> David, I'm confused why you see 5 steps to get to advanced search. 
>
> Control-Shift-A opens the Advanced Search tiddler and puts your cursor in 
> the search field... The tab is whatever you last chose, so often there's 
> only the one quick step. 
>
> Your other points are important (and I too use advanced search about as 
> often as the standard search), but this "5-steps" description misses the 
> keyboard shortcut...
>
> -Springer
>
> On Saturday, August 14, 2021 at 10:10:44 AM UTC-4 David Gifford wrote:
>
>> I hate the loss of the edit post button on this forum. 
>>
>> I forgot a point: the actual steps are four, before you can enter your 
>> search term in $:/Advanced search:
>>
>> 1. Move from what you are doing in the story river, to the sidebar.
>> 2. Resist the urge to do a regular search, and instead click 
>> $:/AdvancedSearch button.
>> 3. Switch your attention back to the story river to view 
>> $:/AdvancedSearch.
>> 4. Pick a tab
>> 5. Then and only then can you enter your search string.
>>
>> Instead, what I am proposing is
>>
>> 1. Move from what you are doing in the story river, to the sidebar. 
>> 2. Enter search string in regular search bar **as step two, rather than 
>> step five**
>> 3. Pick a tab and see results
>> 4. Refine search string if needed
>>
>> On Saturday, August 14, 2021 at 10:01:54 AM UTC-4 David Gifford wrote:
>>
>>> Hi everyone
>>>
>>> I am playing with the field-search plugin by PMario, and seeing how 
>>> search results for a simple search come up in tabs one can pick from.
>>>
>>> This made me wonder, why couldn't there be something similar: do a 
>>> search from the default searchbar, and have standard, system and shadow 
>>> come up as tabs? 
>>>
>>> This seems like it would be much more intuitive for users: search, then 
>>> filter results. As it stands, $:/AdvancedSearch does the opposite: it makes 
>>> you pick a type of search (standard, system, shadow, filter) first, and 
>>> only then can you do the search. The search string you want to enter may or 
>>> may not stay in your short term memory while you are figuring out which 
>>> type of search you want to do. It seems like it would be a better user 
>>> experience to 'dump' the search term first, then figure out which tab you 
>>> want.
>>>
>>> On the same subject, Why is there no comparable "recent" tab for system 
>>> tiddlers? It seems like developers would benefit greatly having something 
>>> like that open as they work on macros, styling, buttons, etc. 
>>>
>>> I would love to hear your input: 
>>> Do you agree with me? Why or why not? If so, should this be core pull 
>>> request or a plugin? 
>>> What are the reasons $:/AdvancedSearch is set up backwards? Technical 
>>> limitations? Workflow-related?
>>> What are the ways you work around these limitations?
>>>
>>>

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


[tw5] Re: Highlighting duplicates in lists

2021-08-15 Thread TW Tones
Look for and use the viewWidget and use the format date with a template, or 
the format relativedate

Get into the habit also of searching in tiddlywiki.com to learn how to do 
things.
[image: Snag_c8a06a9.png]

eg;

<$view field=created format=date template=""/>

<$view field=created format=relativedate/>

 5.1.23 now allows this inside filters. 
<https://tiddlywiki.com/#format%20Operator%20(Examples)>

Regards
Tones

On Sunday, 15 August 2021 at 10:26:32 UTC+10 mohamed...@hotmail.com wrote:

> Sorry one more questions
>
> if the values are dates, how can they be displayed in normal format ,and 
> not the tiddly wiki format
>
> On Monday, August 9, 2021 at 1:10:18 AM UTC+2 paulgilbert2000 wrote:
>
>> Thank you tones
>>
>> Will take me a while to understand all that . but it works like a charm , 
>> and its even more than what i have asked for
>>
>> thanks again:)
>>
>> On Sunday, August 8, 2021 at 7:31:10 AM UTC+2 TW Tones wrote:
>>
>>> Mohamad,
>>>
>>> I am happy to look at solving the problem presented but my suspicion 
>>> remains that there may be a different way to put the question in the first 
>>> place. 
>>>
>>> Sometimes a question can be rephrased such that the answer is simpler to 
>>> find.
>>>
>>>- In this we have multiple tiddlers, with multiple fields, with 
>>>*values* that may be duplicated across these tiddlers/fields.
>>>- in effect you want to list all tiddlers using the select fields, 
>>>list these for each tiddler then for each found value
>>>   -  detect when that value occurs in any other tiddler (not self?) 
>>>   or select fields, if it does highlight it.
>>>- I am not sure why you want to do this and can think of many ways 
>>>to list/interpret the data! 
>>>- What about triplicates?
>>>- What about duplicates in the same tiddler?
>>>
>>> I think using your test data this is what you wanted?
>>>
>>> 
>>> <$list filter="[all[]has[field_example]]">
>>><$set name=other-values 
>>> filter="[all[]!get[field_example]] 
>>> [all[]!titleget[field_example2]] 
>>> [all[]!titleget[field_example3]] +[sort[]]">
>>><>: |  
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> variable=field-value>
>>> >> [enlistmatchthen[color: red;]] 
>>> }}}><>
>>> 
>>>
>>> 
>>> 
>>>
>>> It will also highlight triplicates...
>>>
>>> A slightly more efficient method is available that could actually could 
>>> the number of repeats and color red if > 1
>>>
>>> <$set name=all-values filter="=[all[]get[field_example]] 
>>> =[all[]get[field_example2]] =[all[]get[field_example3]]">
>>> "<>" {{{ [split[ ]count[]] }}}
>>> 
>>> <$list filter="[all[]has[field_example]]">
>>><>: |  
>>><$list filter="[all[current]get[field_example]] 
>>> [all[current]get[field_example2]] [all[current]get[field_example3]]" 
>>> variable=field-value>
>>> <$set name=value-count filter="[split[ 
>>> ]matchcount[]]">
>>> compare:number:gt[1]then[color: 
>>> Red;]] }}} ><> (<>)
>>>  
>>> 
>>> 
>>> 
>>> 
>>>
>>> Of course in the above you can choose not to show the count of the same 
>>> value delete  "(<>)"
>>>
>>> Regards
>>> Tones
>>>
>>> On Sunday, 8 August 2021 at 02:05:57 UTC+10 mohamed...@hotmail.com 
>>> wrote:
>>>
>>>> Hi Tones,
>>>>
>>>> sorry for the late reply , i wasn't clear at all in my last question 
>>>> actually
>>>>
>>>> So for example ,if  every tiddler has three fields  , field_example , 
>>>> field_example2 and  field_example3 
>>>>
>>>> [image: Capture.PNG]
>>>>
>>>> and they are populated with values as such
>>>>
>>>> *   tiddler 1*has in field_example "3" And in field_example2 
>>>> "2"And in field_example3 "6"
>>>> and
>>>>*tiddler 2 *   has in field_example "4&q

[tw5] Re: Speech-to-Text v1.0.5 is here!

2021-08-15 Thread TW Tones
Thanks BTC, and especially Flanc...

This is seriously cool, I will try and contribute more moving forward.

I can't believe how I could switch to the French language and even my poor 
French was recognised as I spoke it. Wow.  As I said before to practice a 
new language and succeed at having the correct words transcribed is a 
revolutionary tool. No need to always talk to native speakers to practice :)



Some thoughts

   1. I feel perhaps I need to identify easy ways to have tiddlers read 
   back to us as a complement, I am sure there are similar tools for browsers, 
   whether or not they can be built in like this transcription process. There 
   was a plugin that reads text with a progress indication over the text as it 
   reads, I will share when I locate it. 
  1. Windows already has text to voice readers, 
   2. I do look forward, if possible to inserting transcriptions into 
   existing text, which I understand is on the list of features.
   3. The commands seem to be working well. 
   4. I do not follow how to add multiple new keywords, I am just a little 
   confused.
   5. Is it possible to capture the actual audio and save that in a tiddler 
   as well? 
  1. ie using voice not only to transcribe but also to trigger a 
  recording. 
   

Speculation

   - The reason I ask question 5 above, is along with 1. above we could 
   build a wiki for managing reading and playing spoken word as a script or 
   like karaoke. Podcasters, radio producers etc... may find this useful. Then 
   editing content could be as simple as rearranging tiddlers, be it textural 
   and/or audio read what you hear, and see what is up next.
   - If this was running on top of a node server we could imagine the 
   operating system responding when detecting a new tiddler containing 
   instructions.
   - I listen to a lot of spoken work podcasts. Perhaps one day I can just 
   play a favorite quote into my microphone, to capture it in tiddlywiki, a 
   bit like how I can copy and past a types transcript.

Regards
Your excited tiddlywikian
Tones

On Sunday, 15 August 2021 at 17:11:49 UTC+10 BurningTreeC wrote:

> The Link to the GitHub project page 
> https://github.com/flancast90/Speech-To-Text-in-TW5
>
> The Link to the Demo page https://speech-to-text.finnsoftware.net/
>
> TW Tones schrieb am Sonntag, 15. August 2021 um 09:06:51 UTC+2:
>
>>
>> Links etc... here in this thread please
>> On Sunday, 15 August 2021 at 08:55:13 UTC+10 flanc...@gmail.com wrote:
>>
>>> *What's New?*
>>>
>>> New language features:
>>>
>>>- auto switch when TW language switched (opt-in on plugin settings)
>>>- more settings, such as continuous listening option!
>>>- Loads of more languages!
>>>- minor BUG fixes
>>>- and lots more!
>>>
>>>

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


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

2021-08-15 Thread TW Tones
Misterel

Joshua does a great technical explanation here, and Mario gives the 
standard solution.

   - The spacing you wish is something best done in the display of the data 
   and not in the data, what if they changed order? 
   - A field containing a list of titles or tiddlers is typically space 
   delimited. So we often need the leading and trailing spaces not to be 
   included.
   - Create a new tiddler and give it leading and ending spaces and you 
   will see how these end up trimmed and do not become part of the title.
   - You can access fields in a different way if you really need to have 
   leading or training spaces as part of the data
   - Transcluding not only brings the fields value, in but what follows is 
   it is rendered, I believe this is when the spaces are trimmed.

Try
'<$transclude field=afield/>' or '{{!!afield}}'
'{{{ [all[current]get[afield]] }}}'

The transcluded filter output demonstrates the field contains a leading 
space of it has one.

Regards
Tones
On Sunday, 15 August 2021 at 06:28:56 UTC+10 Misterel85 wrote:

> How can I prevent TW from trimming leading space in field transclusion?
>
> When transcludings two fields one after the other, for instance:
>
> `<$transclude field="foo" /><$transclude field="bar" />`
>
> if the value of field "bar" starts with a space, that space is 
> automatically removed in the transclusion.
>
> In this example the successive transclusions of:
>
> "foo"=> "This is foo"
> "bar"=> " and this is bar."
>
> render as:
>
> "This is fooand this is bar."
>
> Inserting a trailing space in "foo" or a `` between the two 
> transclusions is not an option for me.
> Placing a `` at the beginning of the value in the second transcluded 
> field works, but that's a bit of a hassle with multiple transclusions.
>
> Why does TW behave so and what is needed to achieve the result I am 
> looking for (a kind of 'untrim' operator)? 
>
> Sorry if that question seems trivial or was already asked before.
>
> -Stéphane L.
>

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


  1   2   3   4   5   6   7   8   9   10   >