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

[Hubert]

@Mark, it's version 5.2.1 but as per donmor's response, TW version is 
irrelevant because the issue is related to Android 11's SAF implementation.

I've switched to using a mobile browser for saving until the Android 11+ / 
Tiddloid combination works reliably again.

On Saturday, 11 December 2021 at 18:09:22 UTC Mark S. wrote:

> What version of TiddlyWiki ?
>
> On Saturday, December 11, 2021 at 9:23:20 AM UTC-8 Hubert wrote:
>
>> I've found the same issue today (both Tiddloid and Tiddloid Lite, latest 
>> versions), Android 11 (not an issue on Android 8).
>>
>> The code appears to belong to the boot.js core tiddler and  I suspect 
>> it's related to the encryption mechanism (though I'm not sure).
>>
>> Steps to reproduce:
>>
>> 1. Open an (encrypted) TiddlyWiki in Tiddloid or Tiddloid Lite (on 
>> Android 11)
>> 2. Save the wiki
>> 3. Reopen the wiki
>>
>> The code appears "underneath" tiddler frame after the wiki is saved by 
>> Tiddloid/Tiddloid Lite and then reopened. Once it's saved like this, the 
>> code will show on any mobile or desktop browser, it appears "burned in" but 
>> how much of the code is revealed depends on the height of the tiddler.
>>
>> Has anyone found a fix?
>>
>> I've opened an issue 
>> <https://github.com/donmor/Tiddloid/issues/25#issue-1077594218>on the 
>> Tiddloid github page.
>>
>> Thanks,
>>
>>
>> [image: tiddloid_code_issue1.png][image: tiddloid_code_issue2.png]
>> On Thursday, 26 August 2021 at 06:06:24 UTC+1 Sandip Deshmukh wrote:
>>
>>> My experience is also very similar to what David has described. Either 
>>> TiddlyDesktop or Tiddloid could be causing the problem.
>>>
>>> But nothing seems to be broken. The wiki works perfectly otherwise.
>>>
>>> On Thursday, August 26, 2021 at 5:55:52 AM UTC+5:30 TW Tones wrote:
>>>
>>>> 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
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/tiddlywiki/797d0403-6673-408f-87af-b093d6365993n%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/d20ee8e6-d562-45ee-87ed-c0d767600559n%40googlegroups.com.

[tw5] Re: Coding fun: Pie Chart with Google Charts, via some trickery

[Hubert]

This is great! It could replace my own custom SVG charting solution that is 
way too heavy. Thank you Charlie.

On Thursday, 4 November 2021 at 18:11:41 UTC cj.v...@gmail.com wrote:

> The screenshot in my first post gave a chart of tiddler types in 
> tiddlywiki.com.
>
> There are so many test/vnd.tiddlywiki tiddlers in tiddlywiki.com, that it 
> makes most of the pie slices ridiculously small.
>
> Here's the same tiddlers, but in a smaller TiddlyWiki just to make for 
> reasonable pie slice sizes.
>
> [image: Screenshot 2021-11-04 3.07.39 PM.png]
>
> On Wednesday, November 3, 2021 at 11:42:42 PM UTC-3 Charlie Veniot wrote:
>
>> Download the attached json, and drag into some TiddlyWiki 
>> (TiddlyWiki.com!) to import three tiddlers:
>>
>>- Pie Chart HTML
>>   - Code sample from Google 
>>   
>> , 
>>   with some modifications
>>  - Some javascript added to handle regenerating a chart when the 
>>  container is resized
>>  - Some placeholders (?), for later search-replace by custom 
>>  chart title and custom data
>>   - The Pie Chart Data
>>   - The Google Pie Chart code needs a table of data to display; this 
>>   tiddler is to build that table of data that will replace the relevant 
>>   placeholder in the HTML
>>- Sample Pie Chart Viewer
>>   - This is the tiddler with all the trickery
>>   - an iframe to display HTML+CSS+javascript dynamically created and 
>>   via the iframe "srcdoc" attribute
>>   - the html fed to the iframe is a neat little filter that grabs 
>>   the content of "Pie Chart HTML" and replaces the "Title" and "Data" 
>>   placeholders with
>>  - I got lazy: just the hard-coded title slapped right there in 
>>  the filter
>>  - The contents of a variable that wikifies the content of "The 
>>  Pie Chart Data" tiddler"
>>  - Notice that the iframe has a very faint grab handle on the 
>>  bottom right-hand corner.  Resizing the iframe causes the chart to 
>> be 
>>  resized too.  Likely not a big deal for folk who really know their 
>> stuff, 
>>  but I'm patting myself on the back for that one.
>>  - Hover over the chart itself to see details for each pie.
>>   
>> Using Google Charts in TiddlyWiki is very convenient, and really easy 
>> (I'm thinking or putting an interface together for what I've done so far, 
>> to make it even easier.
>>
>> And it sure helps keep a TiddlyWiki instance really light by using an 
>> external charting service.
>>
>> Not so great when off-line.  But when I'm offline, I don't have much use 
>> for any computer anyway ...
>>
>> Cheers !
>>
>>
>>
>> [image: Screenshot 2021-11-03 11.18.54 PM - Display 1.png]
>
>

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

Re: [tw5] Re: Tiddloid or TiddloidLite instalation

[Hubert]

Hi Tony/Tones,

I'm not sure if you still need help with Tiddloid.

Tiddloid Lite is better suited for the latest Android versions (8+). You 
can download the apk file directly from its github repository, no need to 
compile anything:

https://github.com/donmor/TiddloidLite/releases/tag/1.1.4

Click on Assets and download the apk to your phone.

Open the apk with a file manager. Android will prompt you to enable 
installation from unknown sources (unless you've previously enabled that).

That's it.

Donmor was adding some upgrades to the app recently but the latest version 
available on github is still from late 2019.

That said, it works perfectly fine and I'm using it all the time — my most 
used Android app actually ;)

Hope this helps.

Thanks,
Hubert


On Saturday, 8 May 2021 at 06:39:18 UTC+1 TiddlyTweeter wrote:

> Mark S. wrote:
>
>> Also quinoid, with similar installation issues:
>>
>> https://github.com/Marxsal/Quinoid01
>>
>> There isn't a lot of "reward" in Android development. You do a lot of 
>> work, and then only a handful of people seem to use it. Google keeps 
>> changing their API
>>
>
> FYI, I'm still using Quinoid. I think it is very good. No issues so far. 
>
> The mechanism to be able to have a JSON file of sites is actually a real 
> benefit for my use cases.
>
> I often want to ask you to think about a method that could allow me to add 
> that file, re-.defined by me, so that I could provide an apk address to my 
> users knowing they will get an app that works well on Anroid and with the 
> sites available easily they are needing.
>
> Why did I *not* ask? For all the reasons you list. I can clearly seen 
> that programming for Android is something of a PITA. And asking for more 
> seems like just too much.
>
> Just a comment
> TT
>

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

[tw5] Re: The case against in TW?

[Hubert]

Hi Saq,

Thanks for sharing your take on this, I appreciate it.

The inputActions parameter sounds interesting. Sounds like it will save me 
a button click in certain scenarios :) Thanks for bringing this up.

Regards,
-Hubert

On Tuesday, 13 April 2021 at 14:57:20 UTC+1 saq.i...@gmail.com wrote:

> Note that the <$edit-text> widget can be used in this form: 
>
> <$edit-text tag="input" type="date" tiddler="test">
>
> The user interface however is widely inconsistent across browsers. Also, 
> if you want to save dates in the same format that TW uses for the modified 
> and created field, you will run into shortcomings for converting the TW 
> format date string into something the browser can understand as a date. 
> Using a button to display the date in an <$edit-text> widget after applying 
> a filter is a potential workaround. Saving it back in the correct format is 
> easily resolved with the inputActions parameter to <$edit-text>. 
>
> I am all for minimal solutions but I cannot recommend this approach due 
> the poor cross browser user experience.
>
>
>
>
>

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

[tw5] Re: The case against in TW?

[Hubert]

Hi Mario, Joshua

@Mario, thanks for your detailed response.

I'm in any way trying to challenge the fact that TiddlyWiki has no built-in 
datepicker functionality. I understand why it doesn't and it makes perfect 
sense. It would be a complex undertaking that is unlikely to meet all 
needs. In fact, I think that TW is actually better off without a built-in 
datepicker widget (less likelihood of bloat, increased bite-size as you 
mentioned due to various locale settings etc. and also no maintainability 
requirements). But the building blocks are there, so individual solutions 
can be built on top of the pure HTML functionality that is inherent to TW.

I was more trying to understand whether relying on the pure HTML 
implementation can cause problems in itself, other than 
consistency/compatibility. These problems could be, for instance, that in 
one browser/OS combination the output of  would be 
-MM-DD and in another browser/OS combination it could be /MM/DD 
etc., which would create problems in that the output would need to be 
parsed (by filters for instance) differently depending on those 
combinations so that the output is made consistent with the TW format of 
0MM0DD0hh0mm0ssXXX before being usable. So, it might need to be more 
"hacky" than it should. 

BTW, the browser/OS combination is something I haven't tested yet but 
assume that the output of  could indeed have 
inconsistent formatting depending on browser/OS combination. This would 
then create problems even for personal wikis if used on different devices.

@Joshua, thanks for responding from a technical perspective.

I wasn't aware that the  HTML entity can be removed from the DOM on 
refresh but widgets can actually withstand refreshes. I guess that we could 
work around that to some extent but again I'm not sure if it's worthwile. 
Anyway, thank you for linking to the additional resources, I'll have a read.

Regards,
-Hubert


On Tuesday, 13 April 2021 at 00:42:54 UTC+1 joshua@gmail.com wrote:

>
> From a technical standpoint, that HTML entity may be removed from the DOM 
> at any time (during the TW refresh cycle, if it is inside a block that gets 
> refreshed to no longer include it, i.e. a user closes the Tiddler in the 
> river, or "hides" it by a "slider"/$reveal. Any code references to that 
> specific HTML entity in the DOM are now broken.
>
> TW uses Widgets (which survive the refresh process, handles all code 
> references i.e. persisting variables or data, and then build HTML to insert 
> into the DOM if the widget is actively displayed).
>
> I would read the Dev Wiki on tiddlywiki.com to get a sense of how the 
> update/refresh procces works, and then the $edit-textwidget docs, and then 
> the CODE inside the "simple engine" that the $edit-text widget spawns for 
> simple 1 line textboxes:
>
>
> https://tiddlywiki.com/dev/#WikiText:WikiText%20Widgets%20Introduction%20HelloThere
>
> https://tiddlywiki.com/#EditTextWidget
>
>
> https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Feditor%2Fengines%2Fsimple.js
>
>
> There is also this similar plugin: http://kixam.github.io/TW5-datePicker/
>
> Best,
> Joshua Fontany
>
> On Monday, April 12, 2021 at 5:56:59 AM UTC-7 PMario wrote:
>
>> Hi Hubert,
>>
>> I think it's mainly because of UI consistency. We need browser and OS 
>> consistency. So it's much easier to create your own UI and be consistent, 
>> instead of documenting a 100 different OS and browser combinations. 
>>
>>- Date and Time pickers imo are always used in a very specific 
>>context. ... You mentioned Projectify, which is a task-management context
>>- On a holiday-booking size you may need a "from - to" context and 
>>you probably need 2 pickers in 1 "popup". 
>>- In a calendar context you will probably need additional fields for 
>>"week" and "time" ... 
>>- ... .and so on ... 
>>
>> All of this makes it "easier" to make it on your own!
>>
>> *On the other hand* date-calculations are extremely complex, since they 
>> have to deal with country and / or region specific differences. ... That's 
>> the reason, why many 3rd party libraries are huge in terms of byte-size. 
>>
>> So TW only provides the most basic possibilities. ... Even if they would 
>> profit hugely from some "love", since the browsers have made a lot of 
>> progress since TW5 and the date-functions have been created. 
>>
>> Just my thoughts!
>> mario
>>
>>

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

[tw5] The case against in TW?

[Hubert]

Hello,

What is the case *against *using the html input tag with the "date" type in 
TiddlyWiki other than compatibility across browsers?

We've seen some great efforts to create datepickers for TiddlyWiki, either 
standalone or as part of other solutions (such as the brilliant Projectify 
<https://projectify.wiki/demo.html>).

Except for browser compatibility, is there any particular reason why the 
use of the "pure" html implementation of a datepicker is generally 
discouraged?

Thanks
-Hubert

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

Re: [tw5] Order of template tiddlers tagged with $:/tags/ViewTemplate

[Hubert]

Thank you Mohammad! It worked.

I've reordered the templates by clicking on the tag pill. I see the new 
order is now reflected in the list field of the tiddler $:/tags/ViewTemplate

However, I need to do some more "testing" and re-reading of the 
documentation <https://tiddlywiki.com/#Order%20of%20Tagged%20Tiddlers> to 
understand list-before and list-after better.

Regards,
-Hubert

On Friday, 2 April 2021 at 11:57:47 UTC+1 Mohammad wrote:

> The simplest is to click on the tag pill for $:/tags/ViewTemplate and 
> reorder the templates
> The best practice is to use list-after / list-before  in your user 
> template!
>
> Best wishes
> Mohammad
>
>
> On Fri, Apr 2, 2021 at 2:27 PM Hubert  wrote:
>
>> Hi,
>>
>> Minimum use case:
>>
>> Let's say I have a tiddler named "apple" with some *lorem ipsum *fluff 
>> in its text field and with the tag "fruit".
>>
>> I also have a tiddler 
>> <https://tiddlywiki.com/static/TemplateTiddlers.html>, let's name it, 
>> "viewer" tagged with $:/tags/ViewTemplate and the following content:
>>
>> <$list filter="[all[current]tag[fruit]]">
>> This is a fruit
>> 
>>
>> When I open the tiddler named "apple" I will see:
>>
>> Lorem ipsum
>>
>> This is a fruit
>>
>> My question is -- how can I decide what should come first: the text field 
>> of the "apple" tiddler (as defined by the core viewtemplates) or the text 
>> in my own viewtemplate ("viewer")? What determines the order? If I decided 
>> I want to see "This is a fruit" before or after "Lorem ipsum" how could I 
>> achieve this?
>>
>> Apologies if this is not clear and thanks in advance for suggestions.
>>
>> Regards,
>> -Hubert
>>
>> -- 
>> You received this message because you 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/174f27ad-69b9-4d41-bcdd-4226bc8361ccn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/174f27ad-69b9-4d41-bcdd-4226bc8361ccn%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/f455a26f-fc2d-4553-8b11-1af5860bbc44n%40googlegroups.com.

[tw5] Re: Making zoomin story view scroll to the top of the tiddler

[Hubert]

Interesting observation, I'd like to know this too.

On Wednesday, 24 March 2021 at 11:37:05 UTC Soren Bjornstad wrote:

> So when I took a look at $:/core/modules/storyviews/zoomin.js, I found 
> that seemingly the necessary code was already there, just commented out:
>
> // Scroll the target into view
> // $tw.pageScroller.scrollIntoView(targetElement);
>
> I checked the blame view 
> 
>  and 
> it appears this has been commented out since it was first introduced in 
> 2013. Is this intentional? Not a big deal either way, just curious.
>
> On Saturday, March 20, 2021 at 12:31:36 PM UTC-5 Soren Bjornstad wrote:
>
>> Hi all,
>>
>> I've been considering using the zoomin story view for *Grok TiddlyWiki *to 
>> make life easier for people who aren't used to scrolling through a bunch of 
>> different tiddlers, but have noticed that when I click on a link within a 
>> tiddler, the browser doesn't scroll to the top of the newly opened tiddler. 
>> Given that sections consist of a number of tiddlers transcluded together, 
>> they are often larger than the screen, so I suspect this is enough to 
>> cancel out any benefit in behavior standardization.
>>
>> Is there an easy way to adjust the scroll when using *zoomin*? I'm not 
>> in the mood to dive into rendering JavaScript today, but perhaps someone 
>> else has done this before.
>>
>

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

[tw5] Order of template tiddlers tagged with $:/tags/ViewTemplate

[Hubert]

Hi,

Minimum use case:

Let's say I have a tiddler named "apple" with some *lorem ipsum *fluff in 
its text field and with the tag "fruit".

I also have a tiddler <https://tiddlywiki.com/static/TemplateTiddlers.html>, 
let's name it, "viewer" tagged with $:/tags/ViewTemplate and the following 
content:

<$list filter="[all[current]tag[fruit]]">
This is a fruit


When I open the tiddler named "apple" I will see:

Lorem ipsum

This is a fruit

My question is -- how can I decide what should come first: the text field 
of the "apple" tiddler (as defined by the core viewtemplates) or the text 
in my own viewtemplate ("viewer")? What determines the order? If I decided 
I want to see "This is a fruit" before or after "Lorem ipsum" how could I 
achieve this?

Apologies if this is not clear and thanks in advance for suggestions.

Regards,
-Hubert

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

[tw5] Re: Lag in edit-text widget

[Hubert]

Hi Clutterstack,

Try addding this field to your state tiddler: *throttle.refresh*

I'm using TW quite heavily on mobile (in addition to desktop) and after 
raising issues regarding typing performance on mobile 
<https://groups.google.com/g/tiddlywiki/c/IqdgBUkrgbA/m/4RNWLf7GCgAJ> Jeremy 
was kind to add a throttle.refresh 
<https://tiddlywiki.com/static/RefreshThrottling.html> setting (code 
<https://github.com/Jermolene/TiddlyWiki5/commit/6089c4de2921df0f76f605f1830fb2c04548f73c>),
 
starting with TiddlyWiki version 5.1.22 (if I remember correctly).

The way it works for me (as in, issue solved permanently) is that my 
edit-text widgets use "$:/typing" as the target tiddler to type into. That 
tiddler has the field "throttle.refresh" with the value "$:/typing". 
Performance is comparable to the one you get when typing in edit mode.

One thing to remember is that although you can now experience lag-free 
typing, your changes won't be committed until the wiki can actually 
refresh. So, I'm wrapping my edit-text widgets in a keyboard widget that 
listens for the enter key. When I'm done typing and hit enter, then an 
action widget populates the value taken from the "$:/typing" tiddler into a 
tiddler of choice and the $:/typing tiddler itself is cleared.

It's smooth and easy but you lose the possibility of searching with live 
updating. It all depends on what is more important to you. I personally aim 
for peak performance, whether desktop or mobile and this solution provides 
that.

Hope this helps. Please let me know if you need any help with this or any 
example code, etc.

Cheers,
-Hubert


On Friday, 2 April 2021 at 03:16:20 UTC+1 clutterstack wrote:

>
> Thanks, Mark. No, I used a separate state tiddler. It works fine, it's 
> just a bit hard to type. I've typed a huge amount into laggy widgets over 
> the past year; I just thought it was my fault and that I'd fix my plugins 
> eventually. Now I'm not sure I can fix them without getting "closer to the 
> metal."
> On Thursday, April 1, 2021 at 9:54:17 PM UTC-4 Mark S. wrote:
>
>> Are you trying to edit text or fields in the SAME tiddler that your edit 
>> widget is in? Because that will cause problems. You have to edit the 
>> contents of some other tiddler.
>>
>> On Thursday, April 1, 2021 at 5:53:32 PM UTC-7 clutterstack wrote:
>>
>>> Hi all,
>>>
>>> I've been trying all sorts of things to make typing in my personal 
>>> plugins less laggy, and I've realised that all I have to do to make typing 
>>> laggy is to do it within an edit-text widget in view mode, no plugin 
>>> required. I can get down to 5fps typing in an edit-text widget in a new 
>>> tiddler on tiddlywiki.com (it's almost 10x as fast in the normal 
>>> tiddler editor).
>>>
>>> Has anyone else noticed this? Is this a well-known thing? I haven't 
>>> found a lot of clues but my google-fu may be weak today.
>>>
>>> Thanks,
>>> Chris
>>>
>>

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

[tw5] Re: Embedding sound files

[Hubert]

Can confirm. Chrome on Android works fine, so does Chrome and FF desktop 
(Windows).

It must be something to do with Tiddloid Lite, I might contact donmor on 
Github.

Thanks again Saq for all your help today.

On Wednesday, 20 January 2021 at 15:49:16 UTC saq.i...@gmail.com wrote:

> Odd. In Chrome on mobile (Android 10) and desktop (Win 10), autoplay works 
> for me.
>
> On Wednesday, January 20, 2021 at 4:22:44 PM UTC+1 Hubert wrote:
>
>> Thanks.
>>
>> Since I last responded, I checked this on mobile using Tiddloid Lite.
>>
>> The sound did not autoplay on mobile (whether it's audio/mpeg or 
>> video/mp4)
>>
>> It did play on mobile when play was explicitly pressed on the mp3 
>> tiddler, it's just that autoplay does not work for some reason.
>>
>> Regards,
>> Hubert
>>
>>
>> On Wednesday, 20 January 2021 at 15:05:29 UTC saq.i...@gmail.com wrote:
>>
>>> I was copying from what I posted for someone else since I'm on my phone 
>>> and it's hard to type wiki syntax.
>>> Surprised that worked, I would have used audio/mpeg
>>>
>>> As for other types you will just need to try, I have never looked into 
>>> this much.
>>>
>>> On Wednesday, January 20, 2021 at 1:41:08 PM UTC+1 Saq Imtiaz wrote:
>>>
>>>> Again untested code but try this:
>>>>
>>>> >>> autoplay />
>>>>
>>>> On Wednesday, January 20, 2021 at 1:29:57 PM UTC+1 Hubert wrote:
>>>>
>>>>> Thank you Sylvain.
>>>>>
>>>>> I was able to embed the mp3 file and play it with a press of a button. 
>>>>> Unfortunately, unlike in the case of "referenced" (external) files, 
>>>>> autoplay doesn't seem to work for *embedded *files (I've checked that 
>>>>> on TiddlyWiki.com as well).
>>>>>
>>>>> When I put this into a tiddler and then open that tiddler, the sound 
>>>>> does not play:
>>>>>
>>>>> 
>>>>>   
>>>>>  
>>>>>
>>>>> Is there anything else I'd need to do for autoplay to work for *embedded 
>>>>> *files?
>>>>>
>>>>> Thanks again,
>>>>> Hubert
>>>>>
>>>>> On Wednesday, 20 January 2021 at 12:04:19 UTC sil...@gmail.com wrote:
>>>>>
>>>>>> Le mercredi 20 janvier 2021 à 11:35:41 UTC+1, Hubert a écrit :
>>>>>>
>>>>>>>
>>>>>>> I would like to embed the mp3 (or ogg or any other compressed sound) 
>>>>>>> file within TiddlyWiki instead of keeping it as an external source file.
>>>>>>>
>>>>>>
>>>>>>
>>>>>> Hello Hubert,
>>>>>>
>>>>>> Did you see this : https://tiddlywiki.com/#Audio
>>>>>>
>>>>>> Tiddler TiddlyWiki.mp3 is set to audio/mp3 content type.
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>> Sylvain
>>>>>>
>>>>>

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

[tw5] Re: Embedding sound files

[Hubert]

Thanks.

Since I last responded, I checked this on mobile using Tiddloid Lite.

The sound did not autoplay on mobile (whether it's audio/mpeg or video/mp4)

It did play on mobile when play was explicitly pressed on the mp3 tiddler, 
it's just that autoplay does not work for some reason.

Regards,
Hubert


On Wednesday, 20 January 2021 at 15:05:29 UTC saq.i...@gmail.com wrote:

> I was copying from what I posted for someone else since I'm on my phone 
> and it's hard to type wiki syntax.
> Surprised that worked, I would have used audio/mpeg
>
> As for other types you will just need to try, I have never looked into 
> this much.
>
> On Wednesday, January 20, 2021 at 1:41:08 PM UTC+1 Saq Imtiaz wrote:
>
>> Again untested code but try this:
>>
>> > autoplay />
>>
>> On Wednesday, January 20, 2021 at 1:29:57 PM UTC+1 Hubert wrote:
>>
>>> Thank you Sylvain.
>>>
>>> I was able to embed the mp3 file and play it with a press of a button. 
>>> Unfortunately, unlike in the case of "referenced" (external) files, 
>>> autoplay doesn't seem to work for *embedded *files (I've checked that 
>>> on TiddlyWiki.com as well).
>>>
>>> When I put this into a tiddler and then open that tiddler, the sound 
>>> does not play:
>>>
>>> 
>>>   
>>>  
>>>
>>> Is there anything else I'd need to do for autoplay to work for *embedded 
>>> *files?
>>>
>>> Thanks again,
>>> Hubert
>>>
>>> On Wednesday, 20 January 2021 at 12:04:19 UTC sil...@gmail.com wrote:
>>>
>>>> Le mercredi 20 janvier 2021 à 11:35:41 UTC+1, Hubert a écrit :
>>>>
>>>>>
>>>>> I would like to embed the mp3 (or ogg or any other compressed sound) 
>>>>> file within TiddlyWiki instead of keeping it as an external source file.
>>>>>
>>>>
>>>>
>>>> Hello Hubert,
>>>>
>>>> Did you see this : https://tiddlywiki.com/#Audio
>>>>
>>>> Tiddler TiddlyWiki.mp3 is set to audio/mp3 content type.
>>>>
>>>>
>>>> Cheers,
>>>> Sylvain
>>>>
>>>

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

[tw5] Re: Using tm-scroll to scroll to a section of a long tiddler (5.1.23)

[Hubert]

Again, thank you!

This now works, albeit only on "vanilla" tiddlers, not on tiddlers affected 
by my view templates. I'll need to investigate further to see if it's my 
CSS that could be affecting the scrolling (margins, transforms etc.) or if 
it's the view template "mechanism" itself that could be invalidating the 
scrolling mechanism (well, I hope it's not the latter).

Regards,
Hubert

On Wednesday, 20 January 2021 at 12:50:59 UTC saq.i...@gmail.com wrote:

> try selector=".bottom" and not $selector.
>
> On Wednesday, January 20, 2021 at 12:39:55 PM UTC+1 Hubert wrote:
>
>> Hi,
>>
>> Since 5.1.23, we've had the ability to scroll onto a section within a 
>> long tiddler using the extended tm-scroll widget message 
>> <https://tiddlywiki.com/#WidgetMessage%3A%20tm-scroll> by specifying the 
>> scroll target as a CSS class of the target element.
>>
>> I've tried this both within the <$scrollable/> widget and without using 
>> it but couldn't get it to work in either case. I keep getting the red JS 
>> error message ("element undefined").
>>
>> Here's my code:
>>
>> <$button actions="""<$action-sendmessage $message="tm-scroll" 
>> $selector=".bottom"/>""">
>> Scroll
>> 
>>
>> Then there's several paragraphs of the lorem ipsum text with the bottom 
>> part wrapped in a div with the class "bottom", i.e.:
>>
>> {{Lorem Ipsum}}
>> 
>> {{Lorem Ipsum}}
>> 
>>
>> When clicking the above button to scroll, I always get the same JS error 
>> message. What have I missed?
>>
>> Thanks for your help.
>> Hubert
>>
>> [image: js_error.png]
>>
>

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

[tw5] Re: Embedding sound files

[Hubert]

It worked! Thank you Saq.

Quick follow-up question: I've tested that on an mp3 file and it worked, 
even though you used "video/mp4" as data type. Is this data type universal 
for mpeg "specification" of files (mp3, mp4 etc, no matter if it's audio or 
video) or is this just a meaningless placeholder that will also accept 
non-mpeg filetypes, like ogg etc?

Regards,
Hubert
On Wednesday, 20 January 2021 at 12:41:08 UTC saq.i...@gmail.com wrote:

> Again untested code but try this:
>
>  autoplay />
>
> On Wednesday, January 20, 2021 at 1:29:57 PM UTC+1 Hubert wrote:
>
>> Thank you Sylvain.
>>
>> I was able to embed the mp3 file and play it with a press of a button. 
>> Unfortunately, unlike in the case of "referenced" (external) files, 
>> autoplay doesn't seem to work for *embedded *files (I've checked that on 
>> TiddlyWiki.com as well).
>>
>> When I put this into a tiddler and then open that tiddler, the sound does 
>> not play:
>>
>> 
>>   
>>  
>>
>> Is there anything else I'd need to do for autoplay to work for *embedded 
>> *files?
>>
>> Thanks again,
>> Hubert
>>
>> On Wednesday, 20 January 2021 at 12:04:19 UTC sil...@gmail.com wrote:
>>
>>> Le mercredi 20 janvier 2021 à 11:35:41 UTC+1, Hubert a écrit :
>>>
>>>>
>>>> I would like to embed the mp3 (or ogg or any other compressed sound) 
>>>> file within TiddlyWiki instead of keeping it as an external source file.
>>>>
>>>
>>>
>>> Hello Hubert,
>>>
>>> Did you see this : https://tiddlywiki.com/#Audio
>>>
>>> Tiddler TiddlyWiki.mp3 is set to audio/mp3 content type.
>>>
>>>
>>> Cheers,
>>> Sylvain
>>>
>>

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

[tw5] Re: Reveal a element only when dragging (not necesarily hovering)

[Hubert]

OK, perfect. I'll give the dragstart actions a try, it sounds promising.

Thanks,
Hubert

On Wednesday, 20 January 2021 at 12:43:22 UTC Hubert wrote:

> Thank you Saq.
>
> The droppable element is now showing when I'm dragging an element over it. 
> However, I'd like it to show *the very moment I start dragging*, so even 
> *before* I've hovered it over the area of the droppable .
>
> Is that possible?
>
> Thanks again,
> Hubert
>
> On Wednesday, 20 January 2021 at 11:52:27 UTC saq.i...@gmail.com wrote:
>
>> If the element isn't visible or doesn't have dimensions, it wont receive 
>> the dragover 
>>
>> Try something like this: (untested code)
>>
>> \define OnDrop()
>> <$some-actions-here/>
>> \end
>>
>> <$list filter="[list[!!list]]" variable="list_item">
>> <$draggable tiddler=<>>
>> <>
>> 
>> 
>>
>> 
>> <$droppable actions=<>>Drop here
>> 
>> 
>>
>> and
>>
>> .show-on-dragover-only > .tc-droppable > span {
>> visibility: hidden;
>> }
>>
>> .show-on-dragover-only > .tc-droppable.tc-dragover > span{
>>visibility: visible;
>> }
>>
>>
>> On Wednesday, January 20, 2021 at 12:17:20 PM UTC+1 Hubert wrote:
>>
>>>
>>> Hi,
>>>
>>> I'm trying to make a  only show when a draggable element is being 
>>> dragged.
>>>
>>> I have some list items and a div with the class "show-on-dragover-only" 
>>> below. That div should stay invisible (either through CSS or the <$reveal/> 
>>> mechanism) until the moment I started dragging any of the list items (the 
>>> sole action of *dragging *should be the trigger, not hovering over the 
>>> droppable element -- hovering is trivial with CSS pseudoclasses and that's 
>>> not what I'm looking for). I assume I have to somehow target the 
>>> .tc-dragover class but I could not make it work.
>>>
>>> Here's my minimal use case:
>>>
>>> \define OnDrop()
>>> <$some-actions-here/>
>>> \end
>>>
>>> <$list filter="[list[!!list]]" variable="list_item">
>>> <$draggable tiddler=<>>
>>> <>
>>> 
>>> 
>>>
>>> 
>>> <$droppable actions=<>>
>>> Drop here
>>> 
>>> 
>>>
>>> And the CSS (which does not work):
>>>
>>> .show-on-dragover-only {
>>> display: none;
>>> }
>>>
>>> .show-on-dragover-only > .tc-droppable.tc-dragover div {
>>> display: block;
>>> }
>>>
>>> Thank you in advance for your hints.
>>>
>>> Regards,
>>> Hubert
>>>
>>

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

[tw5] Re: Reveal a element only when dragging (not necesarily hovering)

[Hubert]

Thank you Saq.

The droppable element is now showing when I'm dragging an element over it. 
However, I'd like it to show *the very moment I start dragging*, so even 
*before* I've hovered it over the area of the droppable .

Is that possible?

Thanks again,
Hubert

On Wednesday, 20 January 2021 at 11:52:27 UTC saq.i...@gmail.com wrote:

> If the element isn't visible or doesn't have dimensions, it wont receive 
> the dragover 
>
> Try something like this: (untested code)
>
> \define OnDrop()
> <$some-actions-here/>
> \end
>
> <$list filter="[list[!!list]]" variable="list_item">
> <$draggable tiddler=<>>
> <>
> 
> 
>
> 
> <$droppable actions=<>>Drop here
> 
> 
>
> and
>
> .show-on-dragover-only > .tc-droppable > span {
> visibility: hidden;
> }
>
> .show-on-dragover-only > .tc-droppable.tc-dragover > span{
>visibility: visible;
> }
>
>
> On Wednesday, January 20, 2021 at 12:17:20 PM UTC+1 Hubert wrote:
>
>>
>> Hi,
>>
>> I'm trying to make a  only show when a draggable element is being 
>> dragged.
>>
>> I have some list items and a div with the class "show-on-dragover-only" 
>> below. That div should stay invisible (either through CSS or the <$reveal/> 
>> mechanism) until the moment I started dragging any of the list items (the 
>> sole action of *dragging *should be the trigger, not hovering over the 
>> droppable element -- hovering is trivial with CSS pseudoclasses and that's 
>> not what I'm looking for). I assume I have to somehow target the 
>> .tc-dragover class but I could not make it work.
>>
>> Here's my minimal use case:
>>
>> \define OnDrop()
>> <$some-actions-here/>
>> \end
>>
>> <$list filter="[list[!!list]]" variable="list_item">
>> <$draggable tiddler=<>>
>> <>
>> 
>> 
>>
>> 
>> <$droppable actions=<>>
>> Drop here
>> 
>> 
>>
>> And the CSS (which does not work):
>>
>> .show-on-dragover-only {
>> display: none;
>> }
>>
>> .show-on-dragover-only > .tc-droppable.tc-dragover div {
>> display: block;
>> }
>>
>> Thank you in advance for your hints.
>>
>> Regards,
>> Hubert
>>
>

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

[tw5] Re: Embedding sound files

[Hubert]

Thank you Sylvain.

I was able to embed the mp3 file and play it with a press of a button. 
Unfortunately, unlike in the case of "referenced" (external) files, 
autoplay doesn't seem to work for *embedded *files (I've checked that on 
TiddlyWiki.com as well).

When I put this into a tiddler and then open that tiddler, the sound does 
not play:


  
 

Is there anything else I'd need to do for autoplay to work for *embedded *
files?

Thanks again,
Hubert

On Wednesday, 20 January 2021 at 12:04:19 UTC sil...@gmail.com wrote:

> Le mercredi 20 janvier 2021 à 11:35:41 UTC+1, Hubert a écrit :
>
>>
>> I would like to embed the mp3 (or ogg or any other compressed sound) file 
>> within TiddlyWiki instead of keeping it as an external source file.
>>
>
>
> Hello Hubert,
>
> Did you see this : https://tiddlywiki.com/#Audio
>
> Tiddler TiddlyWiki.mp3 is set to audio/mp3 content type.
>
>
> Cheers,
> Sylvain
>

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

[tw5] Using tm-scroll to scroll to a section of a long tiddler (5.1.23)

[Hubert]

Hi,

Since 5.1.23, we've had the ability to scroll onto a section within a long 
tiddler using the extended tm-scroll widget message 
<https://tiddlywiki.com/#WidgetMessage%3A%20tm-scroll> by specifying the 
scroll target as a CSS class of the target element.

I've tried this both within the <$scrollable/> widget and without using it 
but couldn't get it to work in either case. I keep getting the red JS error 
message ("element undefined").

Here's my code:

<$button actions="""<$action-sendmessage $message="tm-scroll" 
$selector=".bottom"/>""">
Scroll


Then there's several paragraphs of the lorem ipsum text with the bottom 
part wrapped in a div with the class "bottom", i.e.:

{{Lorem Ipsum}}

{{Lorem Ipsum}}


When clicking the above button to scroll, I always get the same JS error 
message. What have I missed?

Thanks for your help.
Hubert

[image: js_error.png]

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

[tw5] Reveal a element only when dragging (not necesarily hovering)

[Hubert]

Hi,

I'm trying to make a  only show when a draggable element is being 
dragged.

I have some list items and a div with the class "show-on-dragover-only" 
below. That div should stay invisible (either through CSS or the <$reveal/> 
mechanism) until the moment I started dragging any of the list items (the 
sole action of *dragging *should be the trigger, not hovering over the 
droppable element -- hovering is trivial with CSS pseudoclasses and that's 
not what I'm looking for). I assume I have to somehow target the 
.tc-dragover class but I could not make it work.

Here's my minimal use case:

\define OnDrop()
<$some-actions-here/>
\end

<$list filter="[list[!!list]]" variable="list_item">
<$draggable tiddler=<>>
<>




<$droppable actions=<>>
Drop here



And the CSS (which does not work):

.show-on-dragover-only {
display: none;
}

.show-on-dragover-only > .tc-droppable.tc-dragover div {
display: block;
}

Thank you in advance for your hints.

Regards,
Hubert

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

[tw5] Embedding sound files

[Hubert]

Hi,

In this GG post 
<https://groups.google.com/g/tiddlywiki/c/6yf3tOA6RH8/m/L1849adtAwAJ>, Eric 
presented a minimal use case for TW to play a sound on clicking a checkbox.

I would like to embed the mp3 (or ogg or any other compressed sound) file 
within TiddlyWiki instead of keeping it as an external source file.

We don't have any relevant tiddler content types for sound at the moment. 
Was anyone able to come up with a solution that works? Perhaps using binary 
data tiddlers?

Thanks in advance for sharing your ideas.

-Hubert

PS. Here's Eric's post for reference.

Try this:

1) Create a tiddler "DoneSound", containing:

  


2) In your <$checkbox> widget, add a "checkactions" parameter, like this:
<$checkbox ... checkactions="""<$action-sendmessage $message="tm-notify" 
$param="DoneSound" />""">
   checkbox text goes here



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

[tw5] Re: [5.1.23] Text alignment issue in More Actions menu

[Hubert]

Apologies, it looks like the screenshots did not load. Trying again:

[image: test.png]

On Friday, 25 December 2020 at 20:21:17 UTC Hubert wrote:

> Hi All,
>
> I've noticed that the word "Delete" looks as if it had a negative 
> "margin-left" value or there was some other alignment issue (screenshot 
> below).
>
> Before altering a shadow tiddler in my own wiki, I've decided to report it 
> to the Group because the issue can be replicated on TiddlyWiki.com using 
> 5.1.23 (the alignment was correct in 5.1.22), so it appears it's not just 
> me :)
>
>
> My own wiki:
>
>

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

[tw5] [5.1.23] Text alignment issue in More Actions menu

[Hubert]

Hi All,

I've noticed that the word "Delete" looks as if it had a negative 
"margin-left" value or there was some other alignment issue (screenshot 
below).

Before altering a shadow tiddler in my own wiki, I've decided to report it 
to the Group because the issue can be replicated on TiddlyWiki.com using 
5.1.23 (the alignment was correct in 5.1.22), so it appears it's not just 
me :)


My own wiki:

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

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

[Hubert]

Thank you Jeremy and everyone involved in bringing this fantastic release 
to life!

I wish you all Happy Holidays and a healthy 2021!

Best regards,
Hubert

On Friday, 25 December 2020 at 11:32:55 UTC Ton Gerner wrote:

> Hi all,
>
> Thank you very much Jeremy et al.
> Many things to be explored.
>
> Merry Christmas and a healthy new year.
>
> Ton
>
>

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

[tw5] Re: unwanted space in, macro result

[Hubert]

Hi,

I haven't studied your code in its entirety (I'm currently on mobile) but 
maybe try adding \whitespace trim in the line immediately following your 
macro definition.

Good luck!
Hubert


On Thursday, 24 September 2020 at 19:14:03 UTC+1 jn.pierr...@gmail.com 
wrote:

> I have spaces surrounding the result of my macro call, even though the 
> result is spaceless. Yet again somethink that I must have overlooked...
>
> Here is the macros code:
>
> \define getWcagDir() <$transclude tiddler="$:/user/dict/wcag/ref/cat" 
> index="$(codeFamily)$"/>
> \define wcagTechDict(ref)
> <$set name="codeFamily" filter="[[$ref$]splitregexp[\d+]join[]]">
> <$macrocall $name="getWcagDir"/>
> 
> \end
> \define wcagUrl(ref)
> <$set name="base" value="https://www.w3.org/WAI/WCAG21/Techniques/;>
> <><>/$ref$ />
> 
> \end
>
> Here is the dictionnary $:/user/dict/wcag/ref/cat
>
> ARIA:aria
> C:css
> F:failures
> G:general
> H:html
> SCR:client-side-script
> SM:smil
> SVR:server-side-script
>
> Here is the user code with call to the wcagUrl macro
>
> SM8 in <> to <>
>
> Here is the result:
>
> SM8 in smil to https://www.w3.org/WAI/WCAG21/Techniques/ smil /SM8
>
> (with a link only from https: up to Techniques/ which is also a problem).
>
> I tried a trim[] after the join[] in the filter. It was redundant, it had 
> no effect.
>
> I tried an other definition for this macro:
>
> \define wcagUrl(ref)
> <$set name="base" value="https://www.w3.org/WAI/WCAG21/Techniques/;>
> <$set name="url" filter="[[] [] [/$ref$] 
> +[join[]]]">
> <>
> 
> 
> \end
>
> but the result is beyond me:
>
> SM8 in smil to <$set name="url" filter="] [] 
> [/SM8] +[join[]"> 
>
> (with a link from  up to +[join[ in the bargain).
>
> Any idea you gurus? (as an ancient Amiga owner, I respect much gurus!)
>
>
>
>

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

[tw5] Re: Advice for new TW5 user regarding line breaks

[Hubert]

Hi BhKh,

Welcome back to the world of TiddlyWiki! :) 

> I wonder if you could just try to pick one? :-) Lets say I'm going to 
paste twenty lines of text into a tiddler from a word document. Each line 
is (as is standard) on it's own line. How can I make them appear on their 
own lines 

A simple and quick way that I use when I need to paste something from 
anywhere else and preserve the original line breaks is wrap my content in 
three double quotes, like here:

"""
This is my content. This is the first line.
This is the second line.

This is the fourth line (note the third line is blank)
"""

When you save your tiddler you will see that the rendered tiddler looks 
exactly like your input (the draft), except the quotes.

As Tony said, there are many ways to implement this, many of which may be 
programmatic etc. By contrast, the above way is just a quick and simple 
solution that you can use right away.

Hope this helps.

Enjoy!
Hubert

On Saturday, 5 September 2020 at 06:07:30 UTC+1 BhKh wrote:

> Dear Tony,
>
> I have noticed your involvement in several related threads and I 
> appreciate the work you and others are doing on this.
>
> > Quite a few existing solutions can help (many exist so I am not sure 
> where to start for you) 
>
> I wonder if you could just try to pick one? :-) Lets say I'm going to 
> paste twenty lines of text into a tiddler from a word document. Each line 
> is (as is standard) on it's own line. How can I make them appear on their 
> own lines
>
>1. in the editor
>2. in the preview
>3. in the final tiddler
>4. and when I copy from the tiddler into another document
>
> without
>
>- having to put double enters at the end of every line
>- code the whole thing in html
>- have other markup be broken
>
> Is that possible?
>
> Right now using the custom class for text tiddlers seems to meet this 
> except for #2 and #4.
>
> I really wanted to get back into using TiddlyWiki, but this issue seems 
> almost absurd. I could appreciate this if we were talking about making a 
> website (which I guess in the the end is what TW is, which may be the 
> issue). But even then, in WordPress I am easily able to copy and paste text 
> both in and out of a web page without thinking twice.
>
> I found this post and am wondering if it provides a solution. I tried to 
> implement it, but I just don't know enough yet about how TW works to get it 
> working.
> https://github.com/Jermolene/TiddlyWiki5/issues/443#issuecomment-368355140
>
> Alternatively, I wonder if I should be using the wysiwyg editor here: 
> http://bjtools.tiddlyspot.com/#VisualEditor. I've tried getting that 
> setup but have so far been unsuccessful.
>
> Am I to assume correctly that I don't want to be tagging tiddlers as 
> text/x-tiddlywiki? This seems to fix it, but there must be some problem 
> with it since a big warning box is displayed.
>
> Any help you can give is most appreciated.
>
> On Saturday, September 5, 2020 at 9:58:27 AM UTC+5:30 TW Tones wrote:
>
>> BhKh,
>>
>> This is a common issue for new users, and as annoying as it is there are 
>> good reasons for it. However it has long being a "bug bear" of myself and 
>> many others.
>>
>> The good news is;
>>
>>- You tend to get used to it
>>- Quite a few existing solutions can help (many exist so I am not 
>>sure where to start for you)
>>- Some of us are currently working on a solution which introduces a 
>>much more powerful set of choices that will all but eliminate the issue.
>>- A lot of copy and pastes work out of the box with tiddlywiki 
>>already so this is not a problem in many cases
>>- If you wish you can copy as html and paste html into a tiddler and 
>>reasonable well rendered.
>>- You can also past anything into one "data tiddler" and create 
>>another tiddler that extracts content from the data tiddler, according to 
>>your desired rules and presents it correctly. Eg each line as a paragraph.
>>   - This is a powerful solution because you could past updated 
>>   content in the data tiddler and the same "re-parse" rules will be 
>> applied.
>>   - This allows one effort to parse the input that can be reused 
>>   again on other data with a click.
>>   - Note: This is a design possibility I have noted as an advanced 
>>   solution one-day
>>
>> Some even find it difficult to enter two new lines to separate each line 
>> and paragraph and stop this concatenation occurring when rendered.
>>
>>- As you seem to have noticed if you use a Heading

[tw5] Re: issue with the "Saved wiki" yellow notification

[Hubert]

No problem Jero, you're very welcome! :)

BTW, the release notes for the current version are listed here 
<https://tiddlywiki.com/static/Releases.html>. A few versions ago, 
TiddlyWiki got math operators in the core and some significant speed 
improvements. To get the details of what's changed in every version since 
5.1.17 you might need to have a look at the github repo here 
<https://github.com/Jermolene/TiddlyWiki5/releases>.

Enjoy!
Hubert

On Tuesday, 4 August 2020 23:23:27 UTC+1, Jero wrote:
>
>
>
> On Tuesday, August 4, 2020 at 10:51:23 PM UTC+9, Hubert wrote:
>>
>> PS. I've noticed that you're using an old TW version:
>>
>> Tiddlywiki 5.1.17 , Firefox 78.0.2 64 bit, Windows 10
>>>
>>
>> The current official TW version is 5.1.22. Each version brings 
>> significant usability improvements. You can upgrade your old wiki to 
>> version 5.1.22 using the upgrader tool 
>> <https://tiddlywiki.com/upgrade.html>. 
>>
>> Remember to *backup* before upgrading!
>>
>>
> Thanks a lot! I was not aware of there being an "upgrade tool". The idea 
> of messing up the wikis by trying to upgrade was more scary than having an 
> old, suboptimal version. But now I will give it a try! 
>

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

[tw5] Re: issue with the "Saved wiki" yellow notification

[Hubert]

PS. I've noticed that you're using an old TW version:

Tiddlywiki 5.1.17 , Firefox 78.0.2 64 bit, Windows 10
>

The current official TW version is 5.1.22. Each version brings significant 
usability improvements. You can upgrade your old wiki to version 5.1.22 
using the upgrader tool <https://tiddlywiki.com/upgrade.html>. 

Remember to *backup* before upgrading!

Best regards,
Hubert


On Tuesday, 4 August 2020 11:54:33 UTC+1, Jero wrote:
>
> Hi everyone.
>
> Tiddlywiki 5.1.17 , Firefox 78.0.2 64 bit, Windows 10
>
> Issue: 
> The "Saved wiki" yellow notification covers the "hide/show sidebar" toggle 
> icon.
> It can take several seconds until the notification disappears, forcing me 
> to wait before I can access the toggle iconn -which, by frequent saving, 
> noticeably disrupts my workflow.
>
> Two solutions come to my mind: 
> 1. Being able to set the max. showing time of the "Saved wiki" 
> notification (I would go for something like 300ms).
> 2. Being able to change the showing place (or size) of the "Saved wiki" 
> notification, so it doesn't cover the "hide/show sidebar" toggle icon.
>
> But I have no idea how to do any of these.
>
> Any help very welcome.
> Jero
>

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

[tw5] Re: issue with the "Saved wiki" yellow notification

[Hubert]

Hi Jero,

If you want to reposition the notification, you can do it like this:

1. Create a new tiddler (any title)
2. Tag it with *$:/tags/Stylesheet*
3. Paste the below code to its body

.tc-notification {
position: fixed !important;
right: 200px;
}

4. Save

Now your notifications will be moved 200 pixels to the left, relative to 
the right edge of the viewport.

You can play with it further using CSS to fit your needs, reposition, 
change colours, styling etc. and delete the above tiddler altogether to 
move back to the core version.

Just an idea, hope this helps.

Have fun!
Hubert


On Tuesday, 4 August 2020 11:54:33 UTC+1, Jero wrote:
>
> Hi everyone.
>
> Tiddlywiki 5.1.17 , Firefox 78.0.2 64 bit, Windows 10
>
> Issue: 
> The "Saved wiki" yellow notification covers the "hide/show sidebar" toggle 
> icon.
> It can take several seconds until the notification disappears, forcing me 
> to wait before I can access the toggle iconn -which, by frequent saving, 
> noticeably disrupts my workflow.
>
> Two solutions come to my mind: 
> 1. Being able to set the max. showing time of the "Saved wiki" 
> notification (I would go for something like 300ms).
> 2. Being able to change the showing place (or size) of the "Saved wiki" 
> notification, so it doesn't cover the "hide/show sidebar" toggle icon.
>
> But I have no idea how to do any of these.
>
> Any help very welcome.
> Jero
>

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

[tw5] Re: Do you guys want another Tiddly app for Android?

[Hubert]

Hi,

Apologies for not responding to the most recent post, just something to 
note:

One additional note: by default, mobile Chrome doesn't support use of 
> drag-and-drop handling (but it does include "pinch zoom" behavior).  
> Fortunately, there is a plugin in the TiddlyWiki Official Plugin Library 
> that adds standard drag-and-drop handling capability even when using mobile 
> Chrome.  Search the plugin library for "mobile" and you will find 
> $:/plugins/tiddlywiki/mobiledragdrop.
>
Drag and drop *DOES *actually work out of the box on mobile, at least on 
Chrome/Chromium (so Tiddloid Lite as well), but not in Firefox. I was quite 
amazed when I've first seen that, it may have been a change to Webview or 
something that made it possible. 

Upon seeing this, I've immediately retired all my list sort buttons and now 
I solely rely on drag and drop for this, whether on mobile or desktop. See 
my original post here 
<https://groups.google.com/forum/#!msg/tiddlywiki/Jh3oH7gApJw/ONhHcS3OBAAJ>.

Thanks,
Hubert

On Thursday, 2 July 2020 20:10:51 UTC+1, Eric Shulman wrote:

> On Thursday, July 2, 2020 at 11:41:00 AM UTC-7, Eric Shulman wrote:
>>
>> Adobe PhoneGap (https://phonegap.com/) is a developer utility that can 
>> produce apps for Android or iPhone, built from HTML/CSS/Javascript source 
>> files (along with any image resources they use).  This is ideal for taking 
>> a single-file TiddlyWiki and wrapping it up to be a "native" app for your 
>> mobile platform.
>>
>
> For Android using Chrome browser (and possibly others), you can just open 
> any single-file TiddlyWiki HTML file, and it will run in the mobile Chrome 
> browser, just like any other web page.
>
> If you then use the "save to desktop" menu item in Android Chrome, it will 
> create an "app" icon directly on your tablet/phone home screen.  When you 
> launch from this icon, Chrome opens the HTML in a bare-bones wrapper that 
> doesn't include the usual tabs, bookmarks, and URL input controls.  The 
> effect is that, except for the standard Android status bar at the top, the 
> entire screen shows the TiddlyWiki content... and, if you use the "toggle 
> full screen" button from the TW sidebar (see "Tools" tab) then even the 
> Android status line disappears and you get *all* of the screen for 
> TiddlyWiki display, with *no* extra stuff at all.
>
> One additional note: by default, mobile Chrome doesn't support use of 
> drag-and-drop handling (but it does include "pinch zoom" behavior).  
> Fortunately, there is a plugin in the TiddlyWiki Official Plugin Library 
> that adds standard drag-and-drop handling capability even when using mobile 
> Chrome.  Search the plugin library for "mobile" and you will find 
> $:/plugins/tiddlywiki/mobiledragdrop.
>
> -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/20e17b0b-9b76-45fe-8c2b-f2015a0f9e70o%40googlegroups.com.

[tw5] Re: [META/OT] Google Groups has a new look

[Hubert]

Definitely, it's not ready for prime time. In addition to that, many 
features have been removed or have been broken, which I've already reported 
to Google:

   - Code formatting is gone 
   - Posts cannot be edited
   - The number of views is not displayed
   - Images cannot be dragged and dropped to display inline
   - Unnecessary scroll bars are showing in the top section on the first 
   page 
   - The overall UI is generally too busy; Google says the new Groups is 
   supposed to be consistent with their other products, but there's no display 
   density setting (Default/Comfortable/Compact) like in Gmail
   
There are many other issues. Usability definitely took a hit. 

Like Tony, I would like the GG dev team to iterate quickly and fix all of 
the points above, but I'm doubtful to be honest.

Just my two cents.

Thanks,
Hubert

On Wednesday, 10 June 2020 at 03:25:47 UTC+1 TonyM wrote:

> Folks,
>
> I reviewed this myself, and it is still under development. There are 
> sufficient gaps that it will handicap the current flexibility while in my 
> view offering little in return.
>
> Lets hope it matures quickly and adds more.
>
> Tony
>
>
> On Tuesday, June 9, 2020 at 11:32:35 PM UTC+10, Hubert wrote:
>>
>> Hi,
>>
>> When I opened up GG this morning (while logged in) I saw this:
>>
>> [image: gg.png]
>>
>> I think it's being rolled out on a phased basis, as has been the case 
>> with most Google redesigns over the years.
>>
>> It looks fresher but not necessarily better in terms of UX/functionality 
>> in my opinion.
>>
>> Thanks,
>> Hubert
>>
>> On Tuesday, 9 June 2020 at 14:11:53 UTC+1 PMario wrote:
>>
>>> Hi, 
>>> How did you activate this view?
>>> -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/4c318f78-c204-4ae8-bcf4-a6f55e849ec5n%40googlegroups.com.

[tw5] Re: [META/OT] Google Groups has a new look

[Hubert]

Hi,

When I opened up GG this morning (while logged in) I saw this:

[image: gg.png]

I think it's being rolled out on a phased basis, as has been the case with 
most Google redesigns over the years.

It looks fresher but not necessarily better in terms of UX/functionality in 
my opinion.

Thanks,
Hubert

On Tuesday, 9 June 2020 at 14:11:53 UTC+1 PMario wrote:

> Hi, 
> How did you activate this view?
> -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/096ecce2-2793-40da-98c3-7c7ae0083be4n%40googlegroups.com.

[tw5] Re: [META/OT] Google Groups has a new look

[Hubert]

[image: gg.png]

On Tuesday, 9 June 2020 at 11:51:02 UTC+1 Hubert wrote:

> Hello,
>
> GG is being redesigned:
>
>
> It might not yet be available to everyone.
>
> For one, this could mean that GG is not going to be axed by Google for 
> some time.
>
> More here:
> https://support.google.com/groups/answer/9718200
>
> Regards,
> Hubert
>
>
>
>

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

[tw5] [META/OT] Google Groups has a new look

[Hubert]

Hello,

GG is being redesigned:


It might not yet be available to everyone.

For one, this could mean that GG is not going to be axed by Google for some 
time.

More here:
https://support.google.com/groups/answer/9718200

Regards,
Hubert



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

[tw5] Re: ISO date query

[Hubert]

Hi Jon,

You can use this ugly macro below to "convert" any string like this: 
"20/06/07" into this: "2020/06/07", assuming that the earliest year in your 
range is the year 2000.

Paste this macro definition in a new tiddler:

\define UpdateDate(date)
<$vars
   y={{{ [<__date__>split[/]nth[1]add[2000]] }}}
   m={{{ [<__date__>split[/]nth[2]] }}}
   d={{{ [<__date__>split[/]nth[3]] }}}>
<>/<>/<>

\end

And then below that, put your input dates in the macro like this:

<>

When you save the tiddler the output will be rendered to this: 2020/06/07

You can wrap this macro in a filter to change all dates in one go and then 
simply copy/paste the output.

The whole operation would probably be quicker and simpler using a text 
editor as these are just strings, not to mention that the above macro can 
probably be simplified to a one-liner. Anyway, just something quick.

Regards,
Hubert

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

[tw5] Re: TiddlyWiki github repo has 4913 stars but it should show 5000+ stars!!

[Hubert]

Done :) Now only 55 stars left.

On Monday, 8 June 2020 14:19:41 UTC+1, Lin Onetwo wrote:
>
> I'm doing my part and sharing this news in some tiddlywiki related wechat 
> and QQ group!
>
> LinOnetwo
>
>

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

[tw5] Mobile drag and drop out of the box

[Hubert]

Hello,

I've just realised that drag and drop works out of the box on mobile IF the 
browser is Chrome/Chromium based (tested on Android). The widgets in 
question are $draggable and $droppable.

Tiddloid Lite is based on Chromium, so it works. It also works in Chrome 
mobile, obviously. It does NOT work in Firefox.

I did these tests on Android. I'm not sure if the situation is the same in 
iOS. 

I thought it would be of interest as I'm quite sure that the only way to 
make drag and drop work on mobile was using the shim plugin 
<https://tiddlywiki.com/prerelease/static/Mobile%2520Drag%2520And%2520Drop%2520Shim%2520Plugin.html>
.

Regards,
Hubert

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

[tw5] Re: Obsidian - Roam competitor

[Hubert]

I'm not sure if it's fair to compare TW with all these tools. What exactly 
is lost if TW does not immediately appeal to a broad audience?

TiddlyWiki is like a programming language, so some learning curve is part 
of the experience.

We can do amazing things with TW, both functionally and aesthetically, but 
only after investing in "cognitive load": learning and practicing the 
language. Much of the flexibility could be lost if more "features" were 
forced upon the uninitiated "out of the box".

An audience unwilling to learn is perhaps not TiddlyWiki's target "market"? 
Maybe it's apples to oranges in the first place?

Just some thoughts.

On Thursday, 28 May 2020 12:39:43 UTC+1, Reet Pandher wrote:
>
> Is felix hiyashi in this group?
>
> On Thursday, May 28, 2020 at 5:07:18 PM UTC+5:30, Tony K wrote:
>>
>> I do use Obsidian and it is great
>>
>> however give me a faster version of TiddlyMap and I wld be happy, vis.js 
>> is very slow
>>
>>
>>
>> On Wednesday, May 27, 2020 at 6:48:34 PM UTC+3, Diego Mesa wrote:
>>>
>>> Yet another Roam competitor, Obsidian: "Obsidian is a powerful knowledge 
>>> base that works on top of a local folder of plain text Markdown files." 
>>>
>>> Link:
>>> https://obsidian.md/
>>>
>>> HN Comments:
>>> https://news.ycombinator.com/item?id=23324598
>>>
>>> Note the creator of obsidian is in the comments as well.
>>>
>>

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

[tw5] Re: Personal News

[Hubert]

Jeremy,

I hope it's manageable. I wish you a quick recovery!
Keep strong and get well soon!

Best regards,
Hubert

On Monday, 18 May 2020 09:59:36 UTC+1, Jeremy Ruston wrote:
>
> I should let you all know that I have somehow contracted Covid-19, despite 
> being in careful lockdown for two months. I haven't been tested (this is 
> the UK), but the symptoms have gradually become unmistakeable over the last 
> week and a half. It's all tolerable at the moment, and I remain hopeful 
> that this is a mild dose of the disease. My doctor says that I can be 
> cautiously optimistic that I've had symptoms for so long without developing 
> the really dangerous ones. I've been told unequivocally to rest, and so 
> I'll likely be out of action for at least a few days. 
>
> I'm very happy there's so much activity on the group just now, but 
> naturally frustrated not to be able to keep up. Hopefully I'll be back 
> soon, and in the meantime please take care of yourselves and each other, 
>
> Best wishes 
>
> Jeremy 
>
> -- 
> Jeremy Ruston 
> jer...@jermolene.com  
> https://jermolene.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/ffdb081e-0849-4226-a0e5-97b1da3620a4%40googlegroups.com.

Re: [tw5] Show element when in viewport (on scroll)?

[Hubert]

Hi Jeremy,

Thank you for the instructions add the additional information!

Best regards,
Hubert

On Saturday, 16 May 2020 15:02:26 UTC+1, Jeremy Ruston wrote:
>
> Hi Hubert
>
> I’m afraid the dynaview plugin examples were out of date which made things 
> difficult. It’s fixed now, and you can try it out on the prerelease:
>
> https://tiddlywiki.com/prerelease/#%24%3A%2Fplugins%2Ftiddlywiki%2Fdynaview 
> <https://tiddlywiki.com/prerelease/#$:/plugins/tiddlywiki/dynaview>
>
> Here’s a minimal example of making a DIV invisible until it is scrolled 
> into view:
>
>  data-dynaview-track-tiddler="$:/state/lorem-visibility">
> <$reveal state="$:/state/lorem-visibility" type="nomatch" text="0" 
> tag="div">
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod 
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim 
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea 
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate 
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat 
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id 
> est laborum.
> 
> 
>
> The dynaview plugin checks the DOM at frequent intervals for DOM nodes 
> with the class tc-dynaview-track-tiddler-when-visible and the attribute 
> data-dynaview-track-tiddler. For any that it finds, it updates the 
> specified tiddler with the visibility state of the DIV (blank = not 
> scrolled into view, 0 = scrolled into view but subsequently scrolled out 
> again, 1 = nearly in view and 2 = fully or partially in view).
>
> As usual with TiddlyWiki, the current visibility state is kept in a 
> tiddler. If you have many DIVs to handle then you’ll need to adopt an 
> approach for generating unique state tiddler titles.
>
> Best wishes
>
> Jeremy.
>
>
> On 13 May 2020, at 13:11, Hubert > wrote:
>
> Hello,
>
> I know that we have the Dynalist plugin but from what I've gathered it's 
> currently at the proof of concept stage of development. From studying its 
> documentation and code I can also see that it's very ambitious and that it 
> may take some time/effort to make it truly "deployable".
>
> What I'm looking for is a fairly simple functionality whereby an element 
> (a div or even a portion of text within a tiddler, definitely not the 
> entire tiddler) could be hidden and only appear when scrolled into view 
> (through JS and CSS display:none > display:initial or something else).
>
> Could this be accomplished by wrapping the content in a widget, either a 
> new standalone widget or perhaps an upgraded $reveal widget, that would 
> detect the vertical scroll position/viewport etc. and only reveal content 
> when it's visible?
>
> I've already had a look at a similar solution here 
> <https://stackoverflow.com/questions/49916259/show-element-when-in-viewport-on-scroll>
>  
> but could not get it to work as a TW JavaScript widget yet.
>
> I'm using the poor man's single tiddler view ;) (zoomin) with animation 
> set to 0 and have no interest in the other storyviews, though I understand 
> that there might be an issue getting this solution to work consistently 
> across all the storyviews.
>
> I was wondering if anyone built something similar and would be willing to 
> share their approach?
>
> Thank you,
> Hubert
>
>
> even through CSS ("display: none") based on it's class
>
>
>
> Show element when in viewport on scroll 
> <https://stackoverflow.com/questions/49916259/show-element-when-in-viewport-on-scroll>
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddl...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/7ae015fc-0679-460b-b3a3-584906aff425%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywiki/7ae015fc-0679-460b-b3a3-584906aff425%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/a17284f7-7282-4ee2-bffa-9fff3065639b%40googlegroups.com.

[tw5] Re: Question for long time TiddlyWiki users

[Hubert]

Hi Reet,

I've been using TW encryption for years and it's been very reliable. I use 
a single-file TW for everything (currently 5.2 MB) with approx. 2k 
tiddlers. I'm not sure how encryption works when you use one of the other 
access methods (bob/node.js etc.)

I reckon it will add some overhead on startup: once you've provided your 
password and hit enter you'll wait longer until your TW is decrypted and 
loaded the larger it is and the slower your device. But for me encryption 
has been a critical feature since I use the single file for everything and 
this additional wait time is well worth it.

You may read about the encryption 
<https://tiddlywiki.com/static/Encryption.html> standard used by TiddlyWiki 
in the documentation. The library used by the core is called Stanford 
JavaScript Crypto Library 
<https://tiddlywiki.com/static/Stanford%2520JavaScript%2520Crypto%2520Library.html>
.

You might also be interested in this discussion on this group:
https://groups.google.com/forum/#!topic/tiddlywiki/VRGzXzxSYEA

If you're concerned about data corruption, probably the single best measure 
against data loss is to make frequent backups. But again, I would never 
expect it to happen because of encryption.

BTW, there's also a plugin allowing you to encrypt single tiddlers only, 
though I don't personally use that.

I hope this helps.

Enjoy!
Hubert

 

On Monday, 18 May 2020 03:09:26 UTC+1, Reet Pandher wrote:
>
> Have you tried the encryption feature of the tiddlywiki?
> If yes then has it been reliable for you? Reliable as in Has it caused any 
> sort of corruption or loss of data even when you know your password? Does 
> it work properly even when you have large amounts of data stored in it? 
>
> 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/d1e04dd1-f59a-480c-a857-8e20e1b08bae%40googlegroups.com.

[tw5] Re: Show element when in viewport (on scroll)?

[Hubert]

Hello again,

Thanks everyone for your input.

I don't know if "display:none" means it never had to be loaded to begin 
> with before though?
>

Mat, I'm not sure about this either. I've found this in reveal.js which may 
suggests that the DOM needs to be involved directly in order to prevent 
rendering of the hidden content:

if(!this.isOpen) {
domNode.setAttribute("hidden","true");
}

But again, I'm no JS expert to draw any such conclusions.

But if you "reverse" the matter it is easier; i.e if you click-to-scroll 
> rather than scroll-to-activate. There's for example this CSS solution. 
> Maybe something here.
>

I agree :)

The dynalist plugin is fully functional,  and it essentially works by 
> creating state tiddlers for reveal widgets that should be rendered only 
> when visible in the viewport. If you study the templates used, you should 
> be able to use the same logic to trigger different reveal widgets inside of 
> one tiddler as well.
>

Thank you Saq for explaining the mechanism on the top level. It will be 
some time before I get the level of understanding that's required here.

Also the load or first render time is more likely the most impact on the 
> experience of the user
>

Tony, that's right and this impact is exactly what I'm trying to attenuate 
by delaying rendering until the moment the content is visible.

It is also my view that javascript solutions should be last on the list of 
> solutions where possible, and if resorted to they should be generic in 
> nature, better native features than plugins. I think a search for html/css 
> solutions would be the best, but then javascript is not my hammer, ie when 
> you have a hammer everything looks like a nail.
>

I 100% agree with you Tony. I'm a core purist/minimalist in the sense that 
I give precedence to the tools already available in the core. I'm actually 
in the process of replacing all my $formula macros with the core 
math/compare operators. But again, in this particular scenario it looks 
like a step up to JS would be needed.

Regards,
Hubert

On Wednesday, 13 May 2020 21:54:24 UTC+1, TonyM wrote:
>
> Hubert,
>
> Keep in mind what the bottleneck on a phone is, for many it is processing, 
> to my understanding using javascript is more processor intensive than CSS 
> or html render to my knowledge. Also the load or first render time is more 
> likely the most impact on the experience of the user, just like the splash 
> screen feature makes a big difference for wiki load because people know 
> something is happening. 
>
> It is also my view that javascript solutions should be last on the list of 
> solutions where possible, and if resorted to they should be generic in 
> nature, better native features than plugins. I think a search for html/css 
> solutions would be the best, but then javascript is not my hammer, ie when 
> you have a hammer everything looks like a nail.
>
> I have made some large tables on a desktop and adding a reveal feature, 
> like hiding columns or rows at initial load the user then exposes more with 
> a click is one approach.
>
> Regards
> Tony
>
> On Thursday, May 14, 2020 at 2:36:00 AM UTC+10, Hubert wrote:
>>
>> Hi Tony,
>>
>> A possible line of enquiry may be html css overflow parameters which 
>>> allow scrollable content, but you may need to set a height.
>>>
>>
>> Thanks for your suggestion. I was actually looking at CSS @media queries 
>> and overflow-block 
>> <https://developer.mozilla.org/en-US/docs/Web/CSS/@media/overflow-block> 
>> sounds familiar but I suspect that we do need a JS element for this 
>> approach. I might be wrong though.
>>
>> Thank you!
>> Hubert
>>
>> On Wednesday, 13 May 2020 13:56:32 UTC+1, TonyM wrote:
>>>
>>> Hubert
>>>
>>> A possible line of enquiry may be html css overflow parameters which 
>>> allow scrollable content, but you may need to set a height.
>>>
>>> I may be missing your requirement but I hope it helps.
>>>
>>> Regards
>>> Tony
>>>
>>>

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

[tw5] Re: Show element when in viewport (on scroll)?

[Hubert]

Hi Tony,

A possible line of enquiry may be html css overflow parameters which allow 
> scrollable content, but you may need to set a height.
>

Thanks for your suggestion. I was actually looking at CSS @media queries 
and overflow-block 
<https://developer.mozilla.org/en-US/docs/Web/CSS/@media/overflow-block> 
sounds familiar but I suspect that we do need a JS element for this 
approach. I might be wrong though.

Thank you!
Hubert

On Wednesday, 13 May 2020 13:56:32 UTC+1, TonyM wrote:
>
> Hubert
>
> A possible line of enquiry may be html css overflow parameters which allow 
> scrollable content, but you may need to set a height.
>
> I may be missing your requirement but I hope it helps.
>
> Regards
> Tony
>
>

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

[tw5] Re: Show element when in viewport (on scroll)?

[Hubert]

Hi Mat,

Doesn't that hold for exactly everything?
>

Yes, it does :) But only visually. I should have mentioned that I would 
want to prevent *rendering *of anything so encapsulated until it becomes 
visible. My goal is to save processing cycles on mobile. 

Probably the best analogy is the $reveal widget -- whatever is within the 
$reveal widget becomes re-rendered every time the widget is revealed (on 
click). However in what I'm trying to achieve the trigger would not be a 
click but a scroll into view.

Could you perhaps link to some site that features this so it is more clear 
> what you mean.
>

The link I've included in my original post (sorry, it was somewhat hidden) 
shows what I mean, please see here:
https://stackoverflow.com/questions/49916259/show-element-when-in-viewport-on-scroll

Thanks again!
Hubert


On Wednesday, 13 May 2020 16:22:38 UTC+1, Mat wrote:
>
> Hubert wrote:
>>
>> [...] hidden and only appear when scrolled into view
>>
>
> Doesn't that hold for exactly everything? Could you perhaps link to some 
> site that features this so it is more clear what you mean.
>
> <:-)
>
>>

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

[tw5] Show element when in viewport (on scroll)?

[Hubert]

Hello,

I know that we have the Dynalist plugin but from what I've gathered it's 
currently at the proof of concept stage of development. From studying its 
documentation and code I can also see that it's very ambitious and that it 
may take some time/effort to make it truly "deployable".

What I'm looking for is a fairly simple functionality whereby an element (a 
div or even a portion of text within a tiddler, definitely not the entire 
tiddler) could be hidden and only appear when scrolled into view (through 
JS and CSS display:none > display:initial or something else).

Could this be accomplished by wrapping the content in a widget, either a 
new standalone widget or perhaps an upgraded $reveal widget, that would 
detect the vertical scroll position/viewport etc. and only reveal content 
when it's visible?

I've already had a look at a similar solution here 
<https://stackoverflow.com/questions/49916259/show-element-when-in-viewport-on-scroll>
 
but could not get it to work as a TW JavaScript widget yet.

I'm using the poor man's single tiddler view ;) (zoomin) with animation set 
to 0 and have no interest in the other storyviews, though I understand that 
there might be an issue getting this solution to work consistently across 
all the storyviews.

I was wondering if anyone built something similar and would be willing to 
share their approach?

Thank you,
Hubert


even through CSS ("display: none") based on it's class



Show element when in viewport on scroll 
<https://stackoverflow.com/questions/49916259/show-element-when-in-viewport-on-scroll>

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

[tw5] Re: JS sleep/timeout function (custom widget)?

[Hubert]

Tony,

Here's one totally non-representative example:

   1. When I log a new running/cycling workout, I select some options and 
   then click a "Log" button.
   2. This button initiates a sequence of actions (a stack of action 
   widgets), the last of which is a fancy animated notification.
   3. However, when I'm on mobile, my fancy animated notification "Workout 
   logged" is not animated, because my phone is still overwhelmed after 
   running all the previous actions.
   4. So what I've done now using Jed's plugin is wrap my notify action 
   widget like below. Now the notification still shows nicely on mobile, with 
   animation and all, because the 2 second delay was more than enough for the 
   processing power to "recover" and for my phone to render the video (CSS) 
   effect properly:

<$action-one/>
<$action-two/>
<$action-delay delay="2">
<$action-sendmessage $message="tm-notify" $param="_notify_logged"/> // 
Delayed action

 
There are many other examples where you can spread out actions over time, 
we're no longer confined to firing everything this instant. One (probably 
not a useful one) example could be to show an alert and then close it 5 
seconds later.

But again, it all depends on the problem you're trying to solve.

Hope this helps.

Regards,
Hubert

On Thursday, 7 May 2020 14:06:59 UTC+1, TonyM wrote:
>
> Could those in the thread explain to a broader audience what such a 
> function would do for us and or a use case?
>
> thanks
> Tony
>

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

[tw5] Re: [New Plugin] Delay Actions, defer the execution of action widgets for a set amount of time

[Hubert]

Thank you for sharing Jed, amazing work and extremely useful.

Regards,
Hubert

On Thursday, 7 May 2020 12:42:53 UTC+1, Jed Carty wrote:
>
> I needed a break from my other work, so I made an action widget that can 
> add a delay to the execution of other action widgets.
>
> Enjoy.
>
> https://ooktech-tw.gitlab.io/plugins/delayactions/
>

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

[tw5] Re: JS sleep/timeout function (custom widget)?

[Hubert]

Jed, may I suggest that you announce this plugin to the wider group. I 
think it's brilliant and maybe more people will find it useful as well.

I think that also Saq and Jeremy hinted at selectively delaying actions 
during their hangout that was recently published 
<https://groups.google.com/forum/?utm_medium=email_source=footer#!searchin/tiddlywiki/hangout$20104%7Csort:date/tiddlywiki/pT_Fr2pFsDU/coZ7JeUAAQAJ>
 
here. I think what was said was that sometimes some changes are not 
captured by the subsequent action widgets because they fired before TW was 
able to render changes made by the previous action widgets. So, I feel like 
there could be a wider need for your widget :)

Thanks again,
Hubert

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

[tw5] Re: JS sleep/timeout function (custom widget)?

[Hubert]

Jed, thank you!!! This is fantastic. It works as advertised, great work!

Many thanks,
Hubert

On Thursday, 7 May 2020 12:41:26 UTC+1, Jed Carty wrote:
>
> I got bored and needed a break from my other work, so I made the widget I 
> described: https://ooktech-tw.gitlab.io/plugins/delayactions/
>

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

[tw5] Re: JS sleep/timeout function (custom widget)?

[Hubert]

That sounds great, thanks Jed. I'm only just beginning to learn JavaScript 
but this is some important info.

I'm sure I'll come up with some solutions eventually and find new problems 
as I go :)

Thanks,
Hubert

On Wednesday, 6 May 2020 20:02:04 UTC+1, Jed Carty wrote:
>
> In the same way that a button widget can have child widgets whose 
> behaviour is affected by the button widget, you could make a widget that 
> calls other widgets, or affects widgets contained inside it.
>
> You could make an action widget that takes a string of action widgets as a 
> parameter and a delay and then runs the widgets after the delay.
>
> The layout would be like this:
>
> <$button>
> WHEE!!!
> <$magic-delay-widget
> actions="""Some list of action widgets here""
> delay="1 million years"
> />
> 
>
> the fastest way to do this would be to modify the button widget to take a 
> delay input and then put the setTimeout around everything inside the click 
> handler.
> There are probably nicer ways to do it, but that would work and should be 
> relatively straight forward.
>
> then it would be a normal button with an extra parameter like this, the 
> actions passed as the actions attribute or listed inside the button tags 
> shouldn't make any difference doing it that way:
>
> <$magicbutton
> delay='10 microseconds'
> actions='lots of action widgets in this list!'
> >
> MAGIC!
> !
>

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

[tw5] Re: JS sleep/timeout function (custom widget)?

[Hubert]

Thanks Jed.

I've actually made some tests with setTimeout in a custom JavaScript widget 
and have realised that setTimeout only delays a function that it is calling.

What this means is that the setTimeout method will have no effect on any 
subsequent actions that may be defined in any* separate* action widgets 
that are stacked below it, because any functions defined there will simply 
be out of scope for the function defined in our current timeout widget.

Please correct me if I'm wrong, but from what I've understood, all action 
widgets are self contained/sandboxed in this respect by design (due to 
security?) or maybe it's just due to JS multi-threading, I have no idea. 
Either way, it appears that setTimeout will not just magically delay JS 
operations globally, not least in any subsequent action widgets.

Thanks,
Hubert

On Wednesday, 6 May 2020 11:41:22 UTC+1, Jed Carty wrote:
>
> Somewhere I have some experiments with something like this. A much safer 
> alternative is to have a background daemon running that emits some event 
> every so often and use that as a clock, then your widget counts pulses (or 
> waits until after a specific time) and then acts.
>
> So you could have the background daemon emit a pulse event every second, 
> then you have an action widget that will count a certain number of pulses 
> before before running the action widgets that it contains.
>
> I hope that makes sense. I have run into a few cases where this would be 
> useful for me in the last few days, but I am not sure how long it will be 
> before I will have the time to make it.
>
> Alternately you could go the easier route and just use a setTimeout in the 
> widget that waits however long you want before running the code. That is 
> how the background daemon would work anyway, the only reason to not use 
> that is that the time would only be accessible inside the widget instead of 
> a globally available clock.
>

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

[tw5] JS sleep/timeout function (custom widget)?

[Hubert]

Hello,

Similar to what was discussed here 
<https://groups.google.com/forum/#!searchin/tiddlywiki/%3C$24action-scrolltotop$2F%3E%7Csort:date/tiddlywiki/oGnX67mw_Nw/e9-ja4o7BgAJ>,
 
is there a JavaScript custom widget with a single timeout function that 
would make it possible to run a sleep/timeout/delay for a number of 
miliseconds as provided through its parameter?

My use case would be to only have the single timeout function in the 
widget, so the widget would only make sense if it was placed before another 
action widget whose actions are to be delayed. It would not do anything 
meaningful on its own, other than freezing the browser a few seconds 
(which, I know, sounds risky in itself).

There's some discussion on StackOverflow and elsewhere advising against 
such solutions, unless in very specific use cases. Freezing anything on 
purpose does not sound as the safest thing to do. I was wondering if 
someone knowledgeable in JS could share their thoughts on the best approach 
to achieve this with little to no risk.

Many thanks,
Hubert

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

[tw5] Re: Demo: Proposal for slight visual changes to getting started tiddler

[Hubert]

Hi Mark,

I wonder, is it possible to detect the OS during boot-up and set the 
> default buttons accordingly?
>

Yes, it's possible. I use TW on Android, Windows and ChromeOS and have the 
following rudimentary solution that works well, no plugins required.

Data is read from $:/info/url/full on startup and searched for the 
following keywords that always occur in the full URL depending on the OS:

Android = emulated
ChromeOS = chronos
Windows = ///

Steps to recreate:

1. Create a tiddler tagged $:/tags/StartupAction and paste this into its 
text field:

<$list filter="[{$:/info/url/full}search:title[///]limit[1]]">
<$action-setfield $tiddler="current_OS" $field="text" $value="Windows"/>


<$list filter="[{$:/info/url/full}search:title[chronos]limit[1]]">
<$action-setfield $tiddler="current_OS" $field="text" $value="ChromeOS"/>


<$list filter="[{$:/info/url/full}search:title[emulated]limit[1]]">
<$action-setfield $tiddler="current_OS" $field="text" $value="Android"/>


2. Customise your TW depending on the OS using $reveal widgets or anything 
else you seem fit based on the name of the OS stored in the tiddler 
current_OS.

I'm not sure whether a consistent URL keyword can be found on Apple devices 
as well, I assume there could be.

Just my two cents, maybe someone will find this solution useful.

Thanks,
Hubert

On Tuesday, 5 May 2020 23:52:46 UTC+1, Mark S. wrote:
>
> That looks nice!
>
> I wonder, is it possible to detect the OS during boot-up and set the 
> default buttons accordingly?
>
> The reason I ask is that most software that I download does exactly this: 
> It presents a menu that attempts to steer me towards whatever platform that 
> I'm currently on.
>
> Based on questions in the forums, it appears that users easily ignore the 
> warning triangle about not saving with the file save menu. I'm thinking 
> that a screen shot of the file save menu with a slash and circle over it 
> might convey the message more readily. In fact, it might make sense to have 
> it at the top of the "Getting Started" tiddler to make the saving "problem" 
> clearer, before explaining the solutions. The whole idea of needing a 
> special approach to saving is going to be new to most people.
>
> On Tuesday, May 5, 2020 at 3:05:43 PM UTC-7, Riz wrote:
>>
>>
>> https://ibnishak.github.io/Tesseract/demo/docs.html
>>
>> I am talking about the visual changes to the "GettingStarted" tiddler 
>> only. Not the other slight modifications made.
>>
>> I was thinking if it would be appropriate to make a PR for this. It is 
>> responsive - so mobile users won't have any issues. But it is some amount 
>> of work. So instead of doing the whole thing and later understanding that 
>> why such a change cannot be merged, I thought I will create a minimum 
>> viable demo and see if it could be integrated.
>>
>> The check-boxes on the side  -  for selecting OS and Browser - works like 
>> normal check-boxes. Which means multiple selection is possible.  So new 
>> users can see if there are save methods that works in all the major 
>> platforms they work in. The cards will rearrange based on the combined 
>> selection. ie - If you check windows, Linux, mac and Firefox - it will show 
>> you methods that is common to these platforms.
>>
>> Other major change is the big green button is now an electric blue. Since 
>> TW5 follows a blue theme - it makes more sense the download button is a 
>> variation of blue. There is enough panache in that button to attract 
>> attention to it I guess.
>>
>> Also we can set the Community Resources for follow the same card pattern. 
>>
>> Sincerely,
>> Riz
>>
>>
>>

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

[tw5] Re: Demo: Proposal for slight visual changes to getting started tiddler

[Hubert]

Hi Riz,

Thanks for sharing. I like your demo, it looks fresher.

I agree it would be great if Mohammad's alerts and tips made it to the 
core, they would bring a more attractive, modern look.

Thanks,
Hubert

On Wednesday, 6 May 2020 00:04:40 UTC+1, Riz wrote:
>
>
> I wonder, is it possible to detect the OS during boot-up and set the 
>> default buttons accordingly?
>>
>> The reason I ask is that most software that I download does exactly this: 
>> It presents a menu that attempts to steer me towards whatever platform that 
>> I'm currently on.
>>
>> This is possible. Create an startup-action tiddler that sets os and 
> browser using information from info tiddlers
>
>  
>
>> Based on questions in the forums, it appears that users easily ignore the 
>> warning triangle about not saving with the file save menu. I'm thinking 
>> that a screen shot of the file save menu with a slash and circle over it 
>> might convey the message more readily. In fact, it might make sense to have 
>> it at the top of the "Getting Started" tiddler to make the saving "problem" 
>> clearer, before explaining the solutions. The whole idea of needing a 
>> special approach to saving is going to be new to most people.
>>
>>
>  My plan is to ask Mohammad to make a PR for the alerts in his shiraz 
> plugin to style the alerts and tips. It catches attention more effectively 
> - being a colored block
>

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

[tw5] Re: TiddlyWiki Hangout #104 with Saq Imtiaz

[Hubert]

Thanks for sharing, Jeremy, and thanks to Saq for showcasing your 
solutions, this was very interesting and inspiring to watch.

Best regards,
Hubert

On Monday, 4 May 2020 17:48:33 UTC+1, Jeremy Ruston wrote:
>
> TiddlyWiki Hangout #104 is now available to watch on YouTube, with my 
> guest Saq Imtiaz demonstrating the heavily customised TiddlyWiki that he 
> uses for personal notes.
>
> https://www.youtube.com/watch?v=lvnqgfvohfM
>
> Many thanks to Saq for his time — and for encouraging me to start things 
> up again.
>
> Questions and feedback welcome,
>
> Best wishes
>
> Jeremy
>
>

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

[tw5] Re: How to display an alert at a predetermined time?

[Hubert]

Hi again Thomas,

Thank you very much for taking the time to share your mechanism in such 
detail!

I was able to reproduce your approach, which opens so many new 
possibilities :)

Thank you again, I really appreciate your help with this.

Best regards,
Hubert

On Sunday, 3 May 2020 10:32:45 UTC+1, Thomas Elmiger wrote:
>
> Hi Hubert,
>
> Thanks for your kind words and sorry for the delayed response.
>
> I'm not interested in timers or anything processing-heavy. Your solution 
>> that triggers the alert when the user is interacting with TW is perfectly 
>> suitable for me (I assume that the alert is triggered when the refresh 
>> mechanism fires, which again is triggered by user interaction).
>>
> Good to see you have the same preferences as me.
>
> I've had a look at the tiddler $:/plugins/telmiger/reminders/messages 
>> which is where, I believe, most of the logic happens. You've built it 
>> beautifully, but unfortunately it's not immediately obvious to me what 
>> "holds off" the alert from being displayed until, say, the double down 
>> arrow on the task in the Do section is pressed.
>>
> I had to take a look again myself ... this is where the messages are 
> generated according to user settings: either a reminder (don’ forget to 
> ...) or an alert (did you really forget to ...?!) with slightly different 
> styling to convey more or less urgency.
>  
>
>> As you've noted, an alert can be triggered just by interacting with the 
>> TW (as long as the deadline is passed), which must imply that the alert is 
>> not triggered by an action in the button but that some re-evaluation of 
>> conditions must happen on a refresh cycle.
>>
> *This is my magic trick: *$:/plugins/telmiger/reminders/display is tagged 
> $:/tags/TopRightBar 
> and thus injected and always present in the top right bar. You are not 
> able to see it, as it is hidden via CSS, but it is re-evaluated as you say 
> with every refresh cycle. No need to set a tag here :)
>
> After evaluating if alerting is active and setting the necessary 
> variables, it creates a list for all tiddlers that have a deadline-field. 
> The list item  will be empty as long as no message should be shown. 
> When a deadline is near or a task is overdue, the result of the 
> reminderCheck macro will be a reminder or an alert. The message will be 
> visible until either the duedate is changed OR the task gets the tag 
> ToDoNow:
>
> 
> 
> <$list filter="""[hastag!tag[ToDoNow]!sort]""" 
> variable="tiddler">
> <$macrocall $name="reminderCheck" 
> reminder-field=<> tiddler=<> reminderspan=<>/>
> 
> 
>
> The sorting should make sure the list is sorted according to urgency so a 
> user can push the first task into the ToDoNow section and postpone the rest.
>
> So far I see that it's impossible to both have a tiddler tagged 
>> $:/tags/Alert and not see it displayed as an alert immediately upon 
>> creation, because once so tagged, such a tiddler *becomes* an alert and 
>> so it *must *fire.
>>
> Tagging requires pushing a button as far as I am aware, so i did not use 
> that.
>
> I have automated alerts that show on startup (if conditions are met) but 
>> this uses actions such as <$action-createtiddler/> (creating alerts on the 
>> fly) embedded in $reveal widgets that narrow down the conditions for 
>> displaying such alerts. But I can't fire such actions by merely interacting 
>> with the TW itself, so I can't create alerts on demand in this way without 
>> running <$action-createtiddler/> somewhere.
>>
> Ïf this was a question, I hope it is answered now ;–)
>
> All the best,
> Thomas
>

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

Re: [tw5] [doc] The BIG PICTURE of TiddlyWiki - an overview

[Hubert]

That was a great read, skillfully written. Thank you Mat!

Regards,
Hubert

On Thursday, 30 April 2020 17:51:31 UTC+1, Julio Peña wrote:
>
> Ah, thank you for clarifying...understood!
>
> On Thursday, April 30, 2020 at 12:24:07 PM UTC-4, Jeremy Ruston wrote:
>>
>> Bitmap images can be converted to png's which would be easier to 
>> maintain...no?
>>
>>
>> The issue is that the images are pictures of TiddlyWiki itself, and so 
>> will need to be kept up to date if the appearance of TiddlyWiki changes. 
>> The innerwiki plugin is designed for that situation, but we don’t currently 
>> have it integrated into the build process.
>>
>> Best wishes
>>
>> Jeremy 
>>
>

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

[tw5] Re: Plugin "tw5-keyboard-navigation"

[Hubert]

Thanks for sharing your plugin Max. It looks like a great addition to the core 
functionality 

.

Good question! For example, I'm using JS in order to determine which 
> tiddler is the current one (because more than one can be in the viewport). 
> I don't think that there is a core feature for doing that.


I think that the storyTiddler 
 variable 
might be just that, though I could be wrong:)


On Thursday, 30 April 2020 18:28:24 UTC+1, Mikesch wrote:
>
> Just great! Thank you! I discovered ESC to cancel editing as well. I do 
> not understand why this isn't in the global shortcuts already included. 
> Perfect! :)
>
> Am Donnerstag, 30. April 2020 16:10:36 UTC+2 schrieb MaxGyver:
>>
>> Hi all,
>>
>> some time ago I created a TiddlyWiki plugin for easier navigation without 
>> using a mouse. It adds some useful key mappings:
>>
>>- j / k: Scroll down/up to the next/previous 
>>tiddler in the story river (instead of scrolling page-wise).
>>- e: Edit the currently "selected" tiddler.
>>- c: Close the selected tiddler.
>>- Esc: Unfocus the search box (when active) in order to 
>>cancel a search and go on navigating with your keyboard.
>>
>> Today, I added new features:
>>
>>- When you search something, you can open the first match with 
>>Return. Without this plugin you have to press Tab, 
>>Tab, Tab, Tab,Return.
>>- When you search something and you want to tab through the results, 
>>a single Tab brings you directly to the first match (so you 
>> save 
>>three Tabs).
>>- When you scroll to the next or previous tiddler via j 
>>/ k, the scrolling is smooth. When you press these keys 
>>repeatedly (delta < 800 ms), you jump instantly to the next (or previous) 
>>tiddler.
>>
>> Check this demo page 
>>  
>> or the plugin source code at GitHub 
>> . I hope this is 
>> useful for somebody.
>>
>> Best regards,
>> Max
>>
>

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

[tw5] Re: Open Tiddler in Edit Mode

[Hubert]

Hi David,

Here's one way:

<$vars title="New Tiddler">
<$button actions="""<$action-sendmessage $message="tm-edit-tiddler" $param=<
>/>""" class="tc-btn-invisible" tooltip="Click to edit">
<>



Just replace the title variable "New Tiddler" with the tiddler you wish to 
open in edit mode.

Your link will now be an invisible button pretending to be a title of your 
tiddler. Click on it and you'll open the tiddler in edit mode.

You might wish to change your CSS classes to make the look of the button 
consistent with other internal links in your wiki (the class tc-tiddlylink 
is one example).

Enjoy!
Hubert






On Thursday, 30 April 2020 18:47:18 UTC+1, David wrote:
>
> I'm always clicking the link to a tiddler and then having to switch it to 
> edit mode.
>
> Possible to do that in one shot?
>

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

[tw5] Re: How to display an alert at a predetermined time?

[Hubert]

Mat,

Thank you for your suggestions. If I remember correctly, "tickler" was part 
of the PM solution named "Cardo". Unfortunately, "Cardo" appears to be 
offline at the moment, so I can't see how it was done.

Thank you,
Huberrt

On Wednesday, 29 April 2020 23:23:17 UTC+1, Mat wrote:
>
> I'm too tired to think clearly so I don't quite understand your request 
> but I come to think of the following and just maybe something is relevant:
>
>- Maybe you can change the "environment" for a your think by means of 
>the TiddlerWidget, making it think it is another time.
>- I have seen some kind of alert system created in TW and it was 
>called "tickler" or similar
>- With 5.1.22, I think comparison ops were just added that should make 
>it possible to compare dates
>- Master *tiddleur *Mark made some macro that calculates the time 
>distance between two dates/times.
>
> If this was all totally irrelevant... then good night. Well good night 
> anyway.
>
> <:-)
>

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

[tw5] Re: How to display an alert at a predetermined time?

[Hubert]

Thomas,

Thank you for your detailed response. I've come across your plugin in the 
past and I'm impressed. Great work indeed!

I'm not interested in timers or anything processing-heavy. Your solution 
that triggers the alert when the user is interacting with TW is perfectly 
suitable for me (I assume that the alert is triggered when the refresh 
mechanism fires, which again is triggered by user interaction).

I've had a look at the tiddler $:/plugins/telmiger/reminders/messages which 
is where, I believe, most of the logic happens. You've built it 
beautifully, but unfortunately it's not immediately obvious to me what 
"holds off" the alert from being displayed until, say, the double down 
arrow on the task in the Do section is pressed.

As you've noted, an alert can be triggered just by interacting with the TW 
(as long as the deadline is passed), which must imply that the alert is not 
triggered by an action in the button but that some re-evaluation of 
conditions must happen on a refresh cycle.

So far I see that it's impossible to both have a tiddler tagged 
$:/tags/Alert and not see it displayed as an alert immediately upon 
creation, because once so tagged, such a tiddler *becomes* an alert and so 
it *must *fire.

I have automated alerts that show on startup (if conditions are met) but 
this uses actions such as <$action-createtiddler/> (creating alerts on the 
fly) embedded in $reveal widgets that narrow down the conditions for 
displaying such alerts. But I can't fire such actions by merely interacting 
with the TW itself, so I can't create alerts on demand in this way without 
running <$action-createtiddler/> somewhere.

Apologies if this is too long winded & thanks for your time!

Regards,
Hubert

On Wednesday, 29 April 2020 20:25:31 UTC+1, Thomas Elmiger wrote:
>
> Hi Hubert and Peter,
>
> @Peter: I have no other solution for recurring reminders than setting the 
> new date manually when you are done.
>
> @Hubert
>
> At the time when I developed ToDoNow I had to build my own alert sytem 
> that probably comes close to what you are looking for. See 
> https://tid.li/tw5/tdn.html and click the double down arrow on the task 
> in the Do section. 
>
> An alert should appear to tell you that this task is late. Click the stop 
> watch to change the deadline and see what happens. My sytem assumes that 
> you are working on the task in the Do section, so tasks placed there will 
> not bother you with alerts.
>
> I think someone else built a *timer* later on to trigger (other) alerts 
> every few seconds or minutes, but my solution does not have that. I did not 
> want to waste processing time while not looking at the screen. So my alerts 
> are triggered by *activity* in the wiki only. A simple click anywhere 
> should be enough in most cases.
>
> The second weakness of my solution ist that time differences are rather 
> guesstimated than calculated. Rather precise for deadlines close to now but 
> probably wrong for deadlines far away from now. And maybe a bit wrong 
> around midnight but we shouldn’t be working then anyway.
>
> My solution was meant to be modular and reusable, so if you can borrow 
> something from there you are very welcome (see the plugins): 
>
> * moments.js by Kixam
> * datepicker plugin by Kixam
>
> These are used to set the deadline in a field* todo-deadline*.
>
> *Reminders for ToDoNow *is my plugin, stuff like the name of the field to 
> watch is configurable.
> For calculations my *rpn* plugin is necessary – this is from a time when 
> TW filters were not able to calculate anything. 
>
> That’s all for now, might be others have better solutions. 
>
> Cheers,
> Thomas
>
>

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

[tw5] Re: Search operator: search for whole words only

[Hubert]

For the record, \b appears limited to ASCII characters. It will not match 
non-English diacritics correctly, as explained in this post 
<https://stackoverflow.com/questions/5311618/javascript-regular-expression-problem-with-b-and-international-characters/5311760>
.

Regards,
Hubert

On Wednesday, 29 April 2020 16:25:10 UTC+1, Hubert wrote:
>
> OK, I had to resort to the $wikify widget but now it works:
>
> <$wikify name="searchterm" text="""\b{{$:/note!!note}}\b""">
> <$list filter="""[tag[note]search:title:regexp]""">
> <>
> 
> 
>
> Thanks again Mark for pointing me in the right direction!
>
> Regards,
> Hubert
>
> On Wednesday, 29 April 2020 15:52:26 UTC+1, Hubert wrote:
>>
>> Thanks Mark. 
>>
>> I still can't get it to work. Here's my entire filter expression. I know 
>> it's clearly incorrect but I can't find any other way to reconcile the 
>> different types of brackets with the title flag, the regex expression and 
>> the in-filter transclusion.
>>
>> My search string to be matched is in the note field of the $:/note 
>> tiddler:
>>
>> <$list filter="""[tag[note]regexp:title[\b{$:/note!!note}\b]]""">
>>
>> 
>>
>> Thanks!
>> Hubert
>>
>> On Wednesday, 29 April 2020 15:32:31 UTC+1, Mark S. wrote:
>>>
>>> Something like:
>>>
>>> [regexp:text[\bTW\b]]
>>>
>>>
>>>
>>> On Wednesday, April 29, 2020 at 7:09:02 AM UTC-7, Hubert wrote:
>>>>
>>>> Hi,
>>>>
>>>> I want to only find whole words when using the search Operator 
>>>> <https://tiddlywiki.com/static/search%2520Operator.html>.
>>>>
>>>> I've tried the options listed here 
>>>> <https://tiddlywiki.com/static/search%2520Operator.html> but cannot 
>>>> make my filter expression match whole words only, even when using the 
>>>> *literal* flag for search strings.
>>>>
>>>> For example, when the search string is TW I only want to find this:
>>>>
>>>>- *TW info*
>>>>- *Hints for tw linking*
>>>>
>>>>
>>>> and NOT this:
>>>>
>>>>- 
>>>> *Two little monkeys *
>>>>
>>>> I suspect that the whole word search can be achieved with regex, would 
>>>> anyone have any idea how?
>>>>
>>>> Many thanks!
>>>> Hubert
>>>>
>>>

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

[tw5] Re: Search operator: search for whole words only

[Hubert]

OK, I had to resort to the $wikify widget but now it works:

<$wikify name="searchterm" text="""\b{{$:/note!!note}}\b""">
<$list filter="""[tag[note]search:title:regexp]""">
<>



Thanks again Mark for pointing me in the right direction!

Regards,
Hubert

On Wednesday, 29 April 2020 15:52:26 UTC+1, Hubert wrote:
>
> Thanks Mark. 
>
> I still can't get it to work. Here's my entire filter expression. I know 
> it's clearly incorrect but I can't find any other way to reconcile the 
> different types of brackets with the title flag, the regex expression and 
> the in-filter transclusion.
>
> My search string to be matched is in the note field of the $:/note tiddler:
>
> <$list filter="""[tag[note]regexp:title[\b{$:/note!!note}\b]]""">
>
> 
>
> Thanks!
> Hubert
>
> On Wednesday, 29 April 2020 15:32:31 UTC+1, Mark S. wrote:
>>
>> Something like:
>>
>> [regexp:text[\bTW\b]]
>>
>>
>>
>> On Wednesday, April 29, 2020 at 7:09:02 AM UTC-7, Hubert wrote:
>>>
>>> Hi,
>>>
>>> I want to only find whole words when using the search Operator 
>>> <https://tiddlywiki.com/static/search%2520Operator.html>.
>>>
>>> I've tried the options listed here 
>>> <https://tiddlywiki.com/static/search%2520Operator.html> but cannot 
>>> make my filter expression match whole words only, even when using the 
>>> *literal* flag for search strings.
>>>
>>> For example, when the search string is TW I only want to find this:
>>>
>>>- *TW info*
>>>- *Hints for tw linking*
>>>
>>>
>>> and NOT this:
>>>
>>>- 
>>> *Two little monkeys *
>>>
>>> I suspect that the whole word search can be achieved with regex, would 
>>> anyone have any idea how?
>>>
>>> Many thanks!
>>> Hubert
>>>
>>

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

[tw5] Re: Search operator: search for whole words only

[Hubert]

Thanks Mark. 

I still can't get it to work. Here's my entire filter expression. I know 
it's clearly incorrect but I can't find any other way to reconcile the 
different types of brackets with the title flag, the regex expression and 
the in-filter transclusion.

My search string to be matched is in the note field of the $:/note tiddler:

<$list filter="""[tag[note]regexp:title[\b{$:/note!!note}\b]]""">



Thanks!
Hubert

On Wednesday, 29 April 2020 15:32:31 UTC+1, Mark S. wrote:
>
> Something like:
>
> [regexp:text[\bTW\b]]
>
>
>
> On Wednesday, April 29, 2020 at 7:09:02 AM UTC-7, Hubert wrote:
>>
>> Hi,
>>
>> I want to only find whole words when using the search Operator 
>> <https://tiddlywiki.com/static/search%2520Operator.html>.
>>
>> I've tried the options listed here 
>> <https://tiddlywiki.com/static/search%2520Operator.html> but cannot make 
>> my filter expression match whole words only, even when using the 
>> *literal* flag for search strings.
>>
>> For example, when the search string is TW I only want to find this:
>>
>>- *TW info*
>>- *Hints for tw linking*
>>
>>
>> and NOT this:
>>
>>- 
>> *Two little monkeys *
>>
>> I suspect that the whole word search can be achieved with regex, would 
>> anyone have any idea how?
>>
>> Many thanks!
>> Hubert
>>
>

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

[tw5] Search operator: search for whole words only

[Hubert]

Hi,

I want to only find whole words when using the search Operator 
<https://tiddlywiki.com/static/search%2520Operator.html>.

I've tried the options listed here 
<https://tiddlywiki.com/static/search%2520Operator.html> but cannot make my 
filter expression match whole words only, even when using the *literal* 
flag for search strings.

For example, when the search string is TW I only want to find this:

   - *TW info*
   - *Hints for tw linking*


and NOT this:

   - 
*Two little monkeys *

I suspect that the whole word search can be achieved with regex, would 
anyone have any idea how?

Many thanks!
Hubert

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

[tw5] How to display an alert at a predetermined time?

[Hubert]

Hi,

I'm trying to display alerts at predetermined times. I know that the alert 
mechanism <https://tiddlywiki.com/#AlertMechanism> will display alerts as 
long as they're tagged:

$:/tags/Alert

I'm also aware that the modified field of the alert tiddler is only used to 
order alerts on the screen. I've tested this by manually creating a tiddler 
and setting its modified date a few minutes into the future (doable by 
using $action-createtiddler with $timestamp="no" and 
modified="FutureUTCTimestamp"). However, the alert mechanism still 
displayed this future alert in the "present" while showing its modified 
"future" date.

Is there any way to make the alert mechanism delay displaying an alert if 
its field (the modified field or any other custom field, if possible) has a 
UTC timestamp set to the future?

Thanks for your help.

Regards,
Hubert

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

Re: [tw5] Re: Is there a solution for triggering scrolling to to Top ( when you are not using the storyriver. )

[Hubert]

Hello,

For anyone who wants to use it, you can find it here: 
> https://szenio.de/Grid/#Scrolltotop 
> <https://www.google.com/url?q=https%3A%2F%2Fszenio.de%2FGrid%2F%23Scrolltotop=D=1=AFQjCNGdYuAiu5417ZRxpoxSFoH8Fnevgw>
>

It works great, thanks for sharing Jan!

It would be nice to have this action implemented on opening a tiddler in 
the zoomin story view and as part of any other single tiddler mode(s) that 
could be introduced in the future. But that's a discussion for a different 
thread.

Thanks again!
Hubert

On Monday, 27 April 2020 11:09:55 UTC+1, Jan wrote:

> Hallo Saq, 
> heureka, it works. 
> For anyone who wants to use it, you can find it here: 
> https://szenio.de/Grid/#Scrolltotop 
>
> Thanks a lot Saq! 
>
> PS.: 
> Encouraged by this success it would be great generalize the function 
> enabeling the widget to scroll to an id that is given as a param. 
> Perhaps we manage that also. 
>
>
>
> Am 27.04.2020 um 00:19 schrieb Saq Imtiaz: 
> > Open the browser developer tools and the console. Do you see any error 
> messages when loading your wiki? I would expect you to. 
> > 
> > Your refresh method is not valid JavaScript. You can actually just 
> remove it entirely. Remove the refresh method. It will inherit from the 
> widget base class and that will be enough in this case. Make sure the 
> tiddler has the correct type for JavaScript and module-type widget. 
> > 
> > If it still doesn't work post your new code and the code for the button 
> being used to trigger this. I'm currently not at a computer so that's the 
> best I can do for now, hope that helps. 
> > 
>
>

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

Re: [tw5] Random operator?

[Hubert]

Thank you Jeremy for pointing this out. I understand the implications and 
dangers, especially when random is part of a filter run.

My use case is very simple, I only intend to generate an integer, which 
should be its final output (so, actually a string) and not an argument in 
any subsequent macro or filter operation.

The reason I originally asked for a random filter operator was based on the 
assumption that filters are central to so many things within TiddlyWiki, 
including maths.

I wasn't aware of the proposed shuffle operator. I will follow the 
developments.

Regards,
Hubert

On Thursday, 23 April 2020 15:37:26 UTC+1, Jeremy Ruston wrote:
>
> There’d been some discussions about this before. A straightforward macro 
> like this can cause problems if not used carefully.
>
> There are some subtle assumptions that filter execution is deterministic 
> (ie, a given filter string will evaluate to the same list every time it is 
> executed in the context of the same tiddler store values). For example, the 
> list widget re-evaluates the filter each time it is refreshed, and detects 
> changes to the list. If there were a randomising filter operator then the 
> filter would be deemed to have changed every time, leading to continuous 
> repeated refreshing of the list widget content.
>
> Matt Lauber has contributed a shuffle operator that should be more robust, 
> but has yet to be finished off:
>
> https://github.com/Jermolene/TiddlyWiki5/pull/3712
>
> Best wishes
>
> Jeremy
>
>
>
> On 23 Apr 2020, at 15:07, TonyM > wrote:
>
> Hubert,
>
> Thanks for sharing !
>
> Tony
>
> On Thursday, 23 April 2020 22:24:22 UTC+10, Hubert wrote:
>>
>> OK, I've written this quick and dirty one-liner JavaScript macro that 
>> takes two arguments: min and max (ideally integers; any floats are floored 
>> down on output). Input arguments (min and max) are included in the random 
>> output.
>>
>> Shorthand syntax below. In this example the macro will output an integer 
>> between 10 and 30 (inclusive).
>>
>> <>
>>
>> File attached if anyone finds it useful.
>>
>> Regards,
>> Hubert
>>
>> On Thursday, 23 April 2020 13:11:18 UTC+1, Hubert wrote:
>>>
>>> Hi Tony,
>>>
>>> Also using now to return the milliseconds may be quite helpful
>>>>
>>>> <>
>>>>
>>>
>>> Wow, that's very creative! Thank you. Through some further tweaking of 
>>> that we might even be able to define the min and max integers for the 
>>> random range as well.
>>>
>>> That could be useful - however I thing some of the maths plugins include 
>>>> this eg evans formula plugin.
>>>>
>>>
>>> Yes, Evan's formula has been my go-to maths plugin for years, also for 
>>> random.
>>>
>>> Thanks again,
>>> Hubert
>>>
>>>
>>> On Thursday, 23 April 2020 13:06:16 UTC+1, TonyM wrote:
>>>>
>>>> Hubert,
>>>>
>>>> That could be useful - however I thing some of the maths plugins 
>>>> include this eg evans formula plugin.
>>>>
>>>> Also using now to return the milliseconds may be quite helpful
>>>>
>>>> <>
>>>>
>>>> However just for one shot, not in a list.
>>>>
>>>> Regards
>>>> Tony
>>>>
>>>> On Thursday, April 23, 2020 at 9:52:20 PM UTC+10, Hubert wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> It appears that Mathematics Operators 
>>>>> <https://tiddlywiki.com/prerelease/static/Mathematics%2520Operators.html>
>>>>>  don't currently include a random operator.
>>>>>
>>>>> I know this feature can be easily written as a macro with just a few 
>>>>> lines of js or, otherwise, the fomula plugin already ships with random
>>>>>  out of the box.
>>>>>
>>>>> However, I think it would be a great to have the random operator in 
>>>>> the core, just like the range 
>>>>> <https://tiddlywiki.com/#range%20Operator> operator was added not so 
>>>>> long ago.
>>>>>
>>>>> Just some thoughts.
>>>>>
>>>>> Regards,
>>>>> Hubert
>>>>>
>>>>>
>>>>>
>>>>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddl...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/006916c1-7873-4933-b8ae-715f6259e8a0%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywiki/006916c1-7873-4933-b8ae-715f6259e8a0%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/649711e4-8fd5-4e16-bb86-ee827328bdb5%40googlegroups.com.

[tw5] Re: Random operator?

[Hubert]

Hi Tony,

Also using now to return the milliseconds may be quite helpful
>
> <>
>

Wow, that's very creative! Thank you. Through some further tweaking of that 
we might even be able to define the min and max integers for the random 
range as well.

That could be useful - however I thing some of the maths plugins include 
> this eg evans formula plugin.
>

Yes, Evan's formula has been my go-to maths plugin for years, also for 
random.

Thanks again,
Hubert


On Thursday, 23 April 2020 13:06:16 UTC+1, TonyM wrote:
>
> Hubert,
>
> That could be useful - however I thing some of the maths plugins include 
> this eg evans formula plugin.
>
> Also using now to return the milliseconds may be quite helpful
>
> <>
>
> However just for one shot, not in a list.
>
> Regards
> Tony
>
> On Thursday, April 23, 2020 at 9:52:20 PM UTC+10, Hubert wrote:
>>
>> Hello,
>>
>> It appears that Mathematics Operators 
>> <https://tiddlywiki.com/prerelease/static/Mathematics%2520Operators.html> 
>> don't currently include a random operator.
>>
>> I know this feature can be easily written as a macro with just a few 
>> lines of js or, otherwise, the fomula plugin already ships with random 
>> out of the box.
>>
>> However, I think it would be a great to have the random operator in the 
>> core, just like the range <https://tiddlywiki.com/#range%20Operator> 
>> operator was added not so long ago.
>>
>> Just some thoughts.
>>
>> Regards,
>> Hubert
>>
>>
>>
>>

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

[tw5] Random operator?

[Hubert]

Hello,

It appears that Mathematics Operators 
<https://tiddlywiki.com/prerelease/static/Mathematics%2520Operators.html> 
don't currently include a random operator.

I know this feature can be easily written as a macro with just a few lines 
of js or, otherwise, the fomula plugin already ships with random out of the 
box.

However, I think it would be a great to have the random operator in the 
core, just like the range <https://tiddlywiki.com/#range%20Operator> 
operator was added not so long ago.

Just some thoughts.

Regards,
Hubert



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

[tw5] Re: Modifying the "More actions" menu

[Hubert]

Thanks Tony.

For the record, I've decided to take the following route:

   1. Open the shadow tiddler *$:/core/ui/Buttons/more-tiddler-actions*
   2. Modify the list filter inside of this shadow tiddler so that it 
   excludes the list items I don't want to see

I've also made a copy of the modified shadow tiddler's text field in a 
separate tiddler in case I ever need to bring back my changes.

If I ever need to bring back the "factory" version, all I need to do is 
delete the modified (overwritten) shadow tiddler. That's the beauty of 
shadow tiddlers in general.

Now I only have the stuff that I need:

[image: modified.png]


Thanks everyone for your help. Issue solved.

By the way, the built in class *.tc-drop-down* causes the More tiddler 
actions dropdown to overflow viewport on mobile, because its max-width is 
set to 380px for some reason. Most mobile browsers in mobile view have a 
viewport width of 360px today, so I've targeted that with a media query in 
my own stylesheet like below, but that's an unrelated note to anyone 
interested:

@media (max-width: 650px) {
.tc-drop-down {
min-width: 360px;
}
}

Regards,
Hubert






On Sunday, 19 April 2020 00:24:44 UTC+1, TonyM wrote:
>
> Hubert,
>
> A good design approach is to rule something into existence rather than 
> hacking the default behavior to rule something out. Its a bit more long 
> winded but would be a more versatile option.
>
>- Create a new More Drop down menu and add only the buttons you want 
>in the new more dropdown
>- Hide the standard more drop down button from display on the view 
>toolbar.
>- With a little reference to the current methods you could have 
>another "more toolbar" settings like the current.
>
> I have actually done this before.
>
> Regards
> Tony
>
> On Sunday, April 19, 2020 at 8:30:36 AM UTC+10, Hubert wrote:
>>
>> Thank you all.
>>
>> I should have stressed that I'm only interested in what's shown when 
>> clicking on the "More actions" button. I'm not trying to hide this button 
>> itself or any other button on the same level for that matter. I am trying 
>> to hide what's *revealed* by the "More actions" button (stuff "beneath" 
>> it).
>>
>> Birthe, you've actually pointed me in the right direction -- I do need to 
>> edit the filter in the shadow tiddler 
>> *$:/core/ui/Buttons/more-tiddler-actions* by manually removing 
>> references to anything I don't need. I'll do that tomorrow and think this 
>> should do the trick. Thank you!
>>
>> PS. Mat, although that's not exactly what I needed, it's great that 
>> you've spotted the UI inconsistency there by the way.
>>
>> Thanks again to everyone for your involvement :)
>>
>> Regards,
>> Hubert
>>
>> On Saturday, 18 April 2020 22:48:13 UTC+1, Mat wrote:
>>>
>>> Hubert, as the others correctly point out, you set it where they state. 
>>> What is not clear, however, is that unchecked items *means* that it 
>>> goes into the more dropdown. IMO this UI is not clear. I'll post an issue 
>>> on 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/bf9f361e-50aa-49cb-8d8c-f9e7be216b04%40googlegroups.com.

[tw5] Re: Modifying the "More actions" menu

[Hubert]

Thank you all.

I should have stressed that I'm only interested in what's shown when 
clicking on the "More actions" button. I'm not trying to hide this button 
itself or any other button on the same level for that matter. I am trying 
to hide what's *revealed* by the "More actions" button (stuff "beneath" it).

Birthe, you've actually pointed me in the right direction -- I do need to 
edit the filter in the shadow tiddler 
*$:/core/ui/Buttons/more-tiddler-actions* by manually removing references 
to anything I don't need. I'll do that tomorrow and think this should do 
the trick. Thank you!

PS. Mat, although that's not exactly what I needed, it's great that you've 
spotted the UI inconsistency there by the way.

Thanks again to everyone for your involvement :)

Regards,
Hubert

On Saturday, 18 April 2020 22:48:13 UTC+1, Mat wrote:
>
> Hubert, as the others correctly point out, you set it where they state. 
> What is not clear, however, is that unchecked items *means* that it goes 
> into the more dropdown. IMO this UI is not clear. I'll post an issue on 
> 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/afece12e-0ac5-4cda-bbb6-1e8a18e2b2ef%40googlegroups.com.

[tw5] Modifying the "More actions" menu

[Hubert]

Hello,

I'd like to hide some options shown in the "More actions" list of a tiddler:

[image: more_actions.png]


I don't remember there being an option to toggle any of these items in the 
Control Panel.

I did find a couple of shadow tiddlers that I could modify (some of which 
are already set to "hide" for some reason) or remove their relevant tag(s) 
but thought I would ask here first in case there was a cleaner (and a 
reversible) solution.

Thank you!
Hubert


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

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

[Hubert]

Thank you Jeremy and everyone involved for this exciting new release!

I feel like a kid on Christmas morning ;)

Best,
Hubert

On Wednesday, 15 April 2020 17:00:14 UTC+1, Jeremy Ruston wrote:
>
> I’m delighted to announce the release of TiddlyWiki v5.1.22.
>
> https://tiddlywiki.com/
>
> This is major release, with many new features, improvements and bug fixes 
> including:
>
> * Plugins that do not contain JS modules can now be loaded dynamically, 
> without needing to save and reload the wiki
> * The plugin chooser (ie the modal for adding new plugins) now features an 
> “updates” tab bringing together all the updates from that plugin library, 
> and allowing them all to be updated with a single click
> * The optional sub-plugins for the CodeMirror plugin are organised under 
> the main plugin in the plugin chooser
> * Plugin dependencies are now installed automatically
> * Improvements to the client-server configuration under Node.js, including 
> better resilience to connection errors and a new dropdown for 
> server-related features
> * New “compare” filter operator for comparing numbers, strings, dates and 
> version numbers
> * New menubar plugin for adding a responsive top menu
> * New freelinks plugin for automatically creating links out of tiddler 
> titles
> * Improved Markdown plugin
>
> …and many more, all listed on the release note:
>
> https://tiddlywiki.com/#Release%205.1.22
>
> You can upgrade your existing single file wikis at: 
> https://tiddlywiki.com/upgrade.html
>
> As usual, please exercise caution when upgrading: take care to take good 
> backups and test that everything is still working as it should
>
> Comments and questions welcome.
>
> I’d like to offer my sincere thanks to the many people who contributed to 
> this release. There are 23 people listed on the release note as having 
> contributed via GitHub but of course many others have helped shape this 
> release through the discussions here. Thanks to everyone.
>
> Best wishes
>
> Jeremy
>

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

[tw5] Re: Woff2 Web fonts and Tiddlywiki 5.1.22p

[Hubert]

Mohammad, thank you for taking the time to explain this in detail. 

Great work indeed!

Best regards,
Hubert

On Thursday, 9 April 2020 16:04:47 UTC+1, Mohammad wrote:
>
> Hi Hubert,
>  It uses the official highlight.js plugin!  see its link here: 
> https://tiddlywiki.com/prerelease/#Highlight%20Plugin 
> The demo wiki only uses Incosolata font (a little bold face).
>
> So to reproduce in your own wiki
>
>1. Install the Highlight.js
>2. Import Incosolata fonts and its stylesheet e.g
>   1. http://kookma.webfonts.tiddlyspot.com/#css-Inconsolata-font
>   2. 
>   http://kookma.webfonts.tiddlyspot.com/#inconsolata-v18-latin-700.woff2
>   3. 
>   
> http://kookma.webfonts.tiddlyspot.com/#inconsolata-v18-latin-regular.woff2
>   3. Set the codeblock fonts as below (see: 
>http://kookma.webfonts.tiddlyspot.com/#Set%20Font)
>
> code, pre {
> font-family: Inconsolata;
> font-size:110%;
> font-weight:500;
> }
>
> put the above CSS in a tiddler tagged with $:/tags/Stylesheet
>
> Cheers
> Mohammad
>

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

[tw5] Re: Woff2 Web fonts and Tiddlywiki 5.1.22p

[Hubert]

Hi Mohammad,

Thank you for this demo. It's very useful and looks great too. Great work! 

A side question, I've noticed that you use a cool feature to display code 
(fortran and css in your examples). Is this something that you've built and 
could share as a plugin or is it rather another feature of the upcoming TW 
version 5.1.22?

Many thanks,
Hubert

On Wednesday, 8 April 2020 20:53:22 UTC+1, Mohammad wrote:
>
> Hi Thomas!
>
> On Wednesday, April 8, 2020 at 11:59:49 PM UTC+4:30, Thomas Elmiger wrote:
>>
>> Thank you, Mohammad
>>
>> Looking forward to this! 
>>
>> I spotted a typo in your documentation: In the how to, step 2.2. Tag it 
>> with $:/tags/Stylesheey
>> should be ... sheet with a t at the end.
>>
>
> Noted and corrected! 
>
>>
>> --Thomas
>>
>
> Cheers
> Mohammad 
>

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

[tw5] Re: CSS styling of radio buttons

[Hubert]

Thank you Mat, that's very neat!

Shortly before you've posted I've completed my own solution:

input[type=radio] {
display: none;
}

.tc-radio {
margin-left: 35px;
position: relative;
}

input[type=radio] + span {
margin-left: -10px;
}

input[type=radio]:not(:checked) + span:before {
content: "-";
color: transparent;
position: absolute;
left: -35px;
height: 12px;
width: 12px;
border: 4px solid #ddd;
background: #ddd;
border-radius: 50%;
transition-duration: 0.2s;
}

input[type=radio]:not(:checked):hover + span:before {
background: #ccc;
transition-duration: 0.2s;
}

input[type=radio]:checked + span:before {
content: "-";
color: transparent;
position: absolute;
left: -35px;
height: 12px;
width: 12px;
border: 4px solid #ddd;
background: #333;
border-radius: 50%;
}

I will look into yours more tomorrow and learn something new.

Thanks again!

Regards,
Hubert


On Thursday, 2 April 2020 20:41:52 UTC+1, Mat wrote:
>
> Presenting: http://radiobuttons.tiddlyspot.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/20f113b4-f5dc-471a-8d43-a591079bdf4a%40googlegroups.com.

[tw5] CSS styling of radio buttons

[Hubert]

Hello,

I'd like to make radio buttons look the same across browsers and I've been 
trying to replace browser defaults by my own styling.

I've used a lot of online resources but adapting them to TW and the 
<$radio/> widget has gotten me nowhere, so far. I'm still learning CSS and 
got stuck here.

Would anyone be willing to share their own CSS for custom radio buttons or 
a bare-bones "wireframe" type CSS code that I could build upon?

Any help would be appreciated.

Thank you,
Hubert

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

[tw5] Re: Voting for v5.1.22 banner

[Hubert]

Hi Jeremy,

Great news, I'm looking forward to the official release of 5.1.22!

PS. I've just voted.

Best regards,
Hubert

On Monday, 30 March 2020 16:13:20 UTC+1, Jeremy Ruston wrote:
>
> Thank you to everyone who entered the competition (see 
> https://groups.google.com/d/topic/tiddlywiki/rYrja18_SfQ/discussion). I’m 
> now making preparations for the release of v5.1.22 so it's time for 
> everyone to vote for their favourite design. Please follow the instructions 
> here:
>
>
> https://docs.google.com/forms/d/e/1FAIpQLSdgS8bum8yoTTw-2n6s9-BxEmcaJAs5Mks7OR7os8JcxRa4Fg/viewform
>
> I’ll leave voting open for at least 3 days from now,
>
> Many thanks,
>
> Jeremy
>
>

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

[tw5] Re: general substring possible?

[Hubert]

I'm not quite sure what you're trying to accomplish.

To split your input (2020-03-12) you can use the split[] operator and to 
replace the dash (-) with a point (.) you can also use join, like for 
instance:

<$list filter="[[2020-03-12]split[-]join[.]]">



Thanks,
Hubert

On Friday, 27 March 2020 13:19:12 UTC, Gerald Weis wrote:

> Hello Hubert
>
> i don't anderstand the solution from jed
>
> My Problem is the best to see in a date
>
> this is an example-title of a tiddler
> Titel Titel Titel 2020-03-12 
>
>
> now to example i want to have. 
> Mister XY was writing on: 12.03.2020 or.
> Mister XY was writing on: 12.03.
> Mister XY was writing on: 12.
>
>
> this date should will use in a textfield of a tiddler
>
>
> Am Freitag, 27. März 2020 13:23:37 UTC+1 schrieb Hubert:
>>
>> Hi Gerald,
>>
>> Please also see Jed's solution here:
>>
>> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/tiddlywiki/MBBVVsTb23M/CNhyN8RCAQAJ
>>
>> Best regards,
>> Hubert
>>
>> On Friday, 27 March 2020 11:51:43 UTC, Gerald Weis wrote:
>>>
>>> Hi Tony
>>>
>>> example-String
>>>
>>> That is a new testversion
>>>
>>> now i want it mak to a new (shorter )string
>>>
>>> <>
>>> < Member for this <>> "19">>
>>>
>>> should given "a Member for this test"
>>>
>>> the number of characters could be mutable
>>>
>>> Am Freitag, 27. März 2020 12:15:42 UTC+1 schrieb TonyM:
>>>>
>>>> Gerald,
>>>>
>>>> It would be good if you gave a sample string and the result.
>>>>
>>>> See here, https://tiddlywiki.com/prerelease/#Filter%20Operators
>>>>
>>>> Any filter can be used to do this, but the triple braces are quick and 
>>>> easy
>>>>
>>>> \define source-field() title
>>>> <$set name=string value={{{ [all[current]get] }}}>
>>>>
>>>>
>>>> ;Is one or some of these what you want?
>>>> :First Character = {{{ [split[]first[]] }}}
>>>> :Last Character = {{{ [split[]last[]] }}}
>>>> :Count = {{{ [split[]count[]] }}}
>>>> :Length = {{{ [length[]] }}}
>>>>
>>>>
>>>> ;This is what split does, notice it removes the spaces (but not with 
>>>> count)
>>>> {{{ [split[]] }}}
>>>>
>>>> 
>>>>
>>>>
>>>> Regards
>>>> Tony
>>>>
>>>> On Friday, March 27, 2020 at 5:34:17 PM UTC+11, Gerald Weis wrote:
>>>>>
>>>>> hi all
>>>>>
>>>>> I have an new projekt where i need an general substringfunktion
>>>>>
>>>>> the makro should work at the pattern "fieldname"  "starting 
>>>>> characternumer which should be extracted" "last charcternumber wich 
>>>>> should 
>>>>> extracted"
>>>>>
>>>>> the most used field is the field "title" of the current Tiddler.
>>>>> but other fields of current tiddlers should be possible to for use.
>>>>>
>>>>> this substring must be printet in an other field as string.
>>>>>
>>>>> my skill ist not so good.
>>>>>
>>>>>
>>>>> thanks for ideas
>>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/087f1a1b-0ad0-4a0a-895f-57937402fff8%40googlegroups.com.

[tw5] Re: general substring possible?

[Hubert]

Hi Gerald,

Please also see Jed's solution here:
https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/tiddlywiki/MBBVVsTb23M/CNhyN8RCAQAJ

Best regards,
Hubert

On Friday, 27 March 2020 11:51:43 UTC, Gerald Weis wrote:
>
> Hi Tony
>
> example-String
>
> That is a new testversion
>
> now i want it mak to a new (shorter )string
>
> <>
> < Member for this < "19">>
>
> should given "a Member for this test"
>
> the number of characters could be mutable
>
> Am Freitag, 27. März 2020 12:15:42 UTC+1 schrieb TonyM:
>>
>> Gerald,
>>
>> It would be good if you gave a sample string and the result.
>>
>> See here, https://tiddlywiki.com/prerelease/#Filter%20Operators
>>
>> Any filter can be used to do this, but the triple braces are quick and 
>> easy
>>
>> \define source-field() title
>> <$set name=string value={{{ [all[current]get] }}}>
>>
>>
>> ;Is one or some of these what you want?
>> :First Character = {{{ [split[]first[]] }}}
>> :Last Character = {{{ [split[]last[]] }}}
>> :Count = {{{ [split[]count[]] }}}
>> :Length = {{{ [length[]] }}}
>>
>>
>> ;This is what split does, notice it removes the spaces (but not with 
>> count)
>> {{{ [split[]] }}}
>>
>> 
>>
>>
>> Regards
>> Tony
>>
>> On Friday, March 27, 2020 at 5:34:17 PM UTC+11, Gerald Weis wrote:
>>>
>>> hi all
>>>
>>> I have an new projekt where i need an general substringfunktion
>>>
>>> the makro should work at the pattern "fieldname"  "starting 
>>> characternumer which should be extracted" "last charcternumber wich should 
>>> extracted"
>>>
>>> the most used field is the field "title" of the current Tiddler.
>>> but other fields of current tiddlers should be possible to for use.
>>>
>>> this substring must be printet in an other field as string.
>>>
>>> my skill ist not so good.
>>>
>>>
>>> thanks for ideas
>>>
>>

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

[tw5] Re: Dictionary to JSON

[Hubert]

It works perfectly, thank you Mohammad!

Regards,
Hubert

On Tuesday, 10 March 2020 15:28:05 UTC, Mohammad wrote:
>
> Try the attached code in tiddlywiki.com
>
>
> --Mohammad
>
>
> On Tuesday, March 10, 2020 at 6:26:39 PM UTC+3:30, Hubert wrote:
>>
>> Hello,
>>
>> Is there a quick and easy way to convert a dictionary-type tiddler to a 
>> json tiddler using existing tools or plugins?
>>
>> It's not about changing the type itself (there's a dropdown for that), 
>> but about parsing and rewriting my key:value pairs to be compliant with the 
>> json data structure.
>>
>> Many thanks,
>> Hubert
>>
>>

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

[tw5] Dictionary to JSON

[Hubert]

Hello,

Is there a quick and easy way to convert a dictionary-type tiddler to a 
json tiddler using existing tools or plugins?

It's not about changing the type itself (there's a dropdown for that), but 
about parsing and rewriting my key:value pairs to be compliant with the 
json data structure.

Many thanks,
Hubert

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

[tw5] Re: [Help] performance of plugin, filters

[Hubert]

Yes, I understand your objectives, but I cannot answer in code if I don't 
have your building blocks.

Anyway, to answer your question on a high level, if your reveal widget 
evaluates to False, then anything it embeds (filters included) is simply 
not run, which does save time.

If it evaluates to True, well, then I guess your best bet would be to run 
performance instrumentation to see how it performs, as Mario suggested 
above. The same applies to your filter run, as long as you can embed the 
functionality of a reveal widget in your filter syntax. By running 
performance instrumentation you can test different solutions and boost 
processing time by a few hundred ms in the best of cases.

Apologies if this appears vague, I just don't want to speculate.

Many thanks,
Hubert

On Tuesday, 10 March 2020 11:20:13 UTC, HC Haase wrote:
>
>
>
> tirsdag den 10. marts 2020 kl. 12.11.34 UTC+1 skrev Hubert:
>>
>> I'm not quite sure what you're trying to accomplish in question #1. 
>> Please post your code and someone may come up with a solution :) (I'll try 
>> my best too).
>>
>> I am thinking if there would be a benefit to combine reveal and the 
> filter, so instead of first a reveal and then a filter I could evaluate, in 
> the same filter, a value in e.g. a state tiddler and then a specific tag.
>  
>
>> As goes for question #2, it's good practice to start building your 
>> filters by defining the fundamental category as explained here 
>> <https://tiddlywiki.com/static/all%2520Operator.html>. There might be 
>> performance benefits too, but I'm not qualified to answer this part of your 
>> question.
>>
>>
> thanks you for your help
>
>
>>

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

[tw5] Re: [Help] performance of plugin, filters

[Hubert]

I'm not quite sure what you're trying to accomplish in question #1. Please 
post your code and someone may come up with a solution :) (I'll try me best 
too).

As goes for question #2, it's good practice to start building your filters 
by defining the fundamental category as explained here 
<https://tiddlywiki.com/static/all%2520Operator.html>. There might be 
performance benefits too, but I'm not qualified to answer this part of your 
question.

Thanks,
Hubert

On Tuesday, 10 March 2020 11:04:19 UTC, HC Haase wrote:
>
> thank very much  you for your answer. This was what I suspected.
>
>
> new questions.
>
> 1
> is it possible to combine reveal and a filter? and will this be faster?
>
> something like:
>
> <$list filter="[speceficTiddler!!field[yes]has[field]]">
>
> and 2
> is there an advantage in 
> [all[tiddlers]tag[something]has[field]]
>
> vs 
> [tag[something]has[field]]
>
> is it an index thing?
>
>
>
>
>
>

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

[tw5] Re: [Help] performance of plugin, filters

[Hubert]

Hi HC,

1. question
> if I hide something (a filter) with the *reveal widget*, will it be 
> bypassed or will it still run the filter but not show it? or is there a 
> better  way (for speed) to toggle between things?
>

It will be bypassed (not executed). Any code/content enclosed in a reveal 
widget that evaluates to False is not run and saves precious processor 
cycles, especially precious on mobile :)

2.question
> is there any advantage in combining filters vs. nesting them?
>
 
Combining all your operators in one filter run is generally better than 
having multiple nested filters, but this depends on how you've designed 
your filters, i.e. how general or how specific they are. If you have two 
nested filters, where the outer one produces an output of 100 items and 
then you re-evaluate that output with your inner (embedded) filter you're 
essentially running it twice, which is inefficient.

For example, this is less efficient:

<$list filter="[all[tiddlers]tag[something]]">
<$list filter="[has[field]]">




than this:

<$list filter="[all[tiddlers]tag[something]has[field]]">




Please correct me if I'm wrong.

Thanks,
Hubert


On Tuesday, 10 March 2020 10:03:39 UTC, HC Haase wrote:
>
> When I am building my new plugin, at some point things get really slow. 
>
> Can you help me understand where I Can optimize please? I am lacking some 
> basic understanding.
>
> 1. question
> if I hide something (a filter) with the *reveal widget*, will it be 
> bypassed or will it still run the filter but not show it? or is there a 
> better  way (for speed) to toggle between things?
>
> 2.question
> is there any advantage in combining filters vs. nesting them?
>
> example:
>
> reveal if field[x]
>   list filter tag[y] limit[1]
>stuff to show
>
>   /list filter
> /reveal
>
> vs
>
> list filter field[x]tag[y] limit[1]
>   stuff to show
> /list
>
>
> 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/f0aa988a-dd99-4ac8-9a86-58b75f35618c%40googlegroups.com.

[tw5] Re: Filter comparison operators

[Hubert]

Hi David,

<$list filter="[tag[blah]has[year](somehow)year<19]">
>
> 
>

I know you're looking specifically for a filter operator. But for the time 
being, is there any reason why you wouldn't settle for the reveal widget? 
This should work based on your code above. You can use that for multiple 
outcomes, use dynamically generated 'variables' and even nest your 
conditions, if needed:

<$list filter="[tag[blah]has[year]]">
<$vars year={{!!year}}>
<$reveal default=<> type="lt" text="19">

content/actions if field "year" has a value that is less than 19





One thing to note is that I'd use a 4-digit year to avoid problems with no 
leading zeroes in single digit years, the reveal widget may sometimes 
return unexpected results in these cases. Once that's taken care of, the 
reveal widget is probably the best 'scenario routing'/comparison mechanism 
that we have in TW at the moment, short of js of course.

More here. <https://tiddlywiki.com/static/RevealWidget.html>

Thanks,
Hubert








On Tuesday, 3 March 2020 12:51:47 UTC, David Allen wrote:
>
> Looking for a filter operator that will let me compare numbers in fields.
>
> <$list filter="[tag[blah]has[year](somehow)year<19]">
>
> 
>
> Just kind of as an example
>

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

[tw5] Re: Question: how to produce a list of unique list items from a filter search?

[Hubert]

Thanks Mat!

After experimenting some more with filters / reading the documentation, I 
was able to come up with a one-line filter expression that works:

<$list 
filter="[all[tiddlers]prefix[TiddlerTest]has[list]each:list-item[list]]">



I guess the missing bit here was each:list-item 
<https://tiddlywiki.com/static/each%2520Operator.html>, somewhat mysterious 
;) but -- it works!

Thanks again,
-Hubert 


On Thursday, 5 March 2020 19:35:56 UTC, Mat wrote:
>
> Here's a... um... really awkward way that at least seems to work. I really 
> hope this is not the best solution:
>
> <$set name=foo filter="[all[tiddlers]prefix[New]get[list]]">
> <$wikify name=bar text={{{ [] }}}>
> <$list filter=<>>
>
> 
> 
> 
>
> @Mark? @Eric? This feels like your hood.
>
> <:-)
>

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

[tw5] Re: Question: how to produce a list of unique list items from a filter search?

[Hubert]

Mat, thanks simplifying the code.

Unfortunately, the output I get still contains duplicates.

I've tried "each" in the meantime as well, but still no luck.

Many thanks,
Hubert


On Thursday, 5 March 2020 18:39:33 UTC, Mat wrote:
>
> <$list filter="[all[tiddlers]prefix[TiddlerTest]get[list]]">
>
> 
>
> I think this should be enough.
>
> <:-)
>
>

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

[tw5] Question: how to produce a list of unique list items from a filter search?

[Hubert]

Hello,

Apologies for awkward phrasing in the title :) Here's what I mean, in code:

TiddlerTest1!!list = banana apple
TiddlerTest2!!list = banana

<$list filter="[all[tiddlers]search:title[TiddlerTest]has[list]]">
<$list filter="[list[!!list]]">

output: *banana apple banana*




The output I get is*: banana apple banana*
What I'm trying to get is: *banana apple* -- so, basically a list of *unique 
*list items. 

I know that the problem here is that I have a "for loop" within a "for 
loop" (in Python speak) and no way of eliminating thus produced duplicates.

Could anyone suggest a fix to my lists that would produce a list of unique 
items?

Thank you in advance.

Regards,
Hubert

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

Re: [tw5] Does ActionListopsWidget not support the $timestamp attribute?

[Hubert]

Ah, I see that now. Thank you for the clarification, Jeremy!

Best regards,
Hubert

On Saturday, 29 February 2020 11:52:34 UTC, Jeremy Ruston wrote:
>
> Hi Hubert
>
> The tiddler $:/config/TimestampDisable is not a shadow tiddler from the 
> core plugin (see below), instead it is created when either of the 
> associated UI buttons are clicked.
>
> We use the term “hidden settings” for configuration options that don’t 
> provide a user interface; in this case there is a user interface in the 
> shape of the sidebar buttons.
>
> Best wishes
>
> Jeremy
>
>
>
> On 29 Feb 2020, at 11:20, Hubert > wrote:
>
> Thank you both.
>
> Temporarily setting $:/config/TimestampDisable to "yes" (and then 
> deleting the tiddler) is the cleanest solution for my use case. Thank you 
> for that, Eric.
>
> As a side note, I could not locate $:/config/TimestampDisable in shadows 
> (Advanced Search only shows this as part of the core) and on editing this 
> tiddler, TW did produce the shadow tiddler warning. I could not find 
> anything else in the TW documentation either. What's the "status" of 
> $:/config/TimestampDisable? Is it yet another hidden setting?
>
> Thank you again!
>
> Regards,
> Hubert
>
>
> On Saturday, 29 February 2020 00:20:06 UTC, Eric Shulman wrote:
>>
>> On Thursday, February 27, 2020 at 6:33:17 AM UTC-8, Hubert wrote:
>>>
>>> The documentation <https://tiddlywiki.com/#ActionListopsWidget> does 
>>> not explicitly state that setting the timestamp attribute with 
>>> $action-listops is supported, so I'm assuming it's not.
>>> Would it then be possible to extend the *ActionListopsWidget *to also 
>>> take the timestamp attribute, in a similar fashion as it's possible in the 
>>> ActionSetFieldWidget and ActionCreateTiddlerWidget?
>>>
>>
>> While it might not be as succinct as having a timestamp attribute 
>> directly in the $action-listops widget, you can currently disable and then 
>> re-enable the $:/config/TimestampDisable value, like this:
>>
>> <$button> Populate 'myfield'
>> <$action-setfield $tiddler="$:/config/TimestampDisable" $value="yes"/>
>> <$action-listops $field="myfield" $subfilter="efg hlm pqr"/>
>> <$action-setfield $tiddler="$:/config/TimestampDisable" $value="no"/>
>> 
>>
>> The result is that the action-listops widget is invoked without changing 
>> the timestamp of the tiddler being modified.
>>
>> 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 tiddl...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/0ae9ef70-c45f-4d98-b850-83f9dee4dbf6%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywiki/0ae9ef70-c45f-4d98-b850-83f9dee4dbf6%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/1dfa3f94-525c-47ac-beb0-8400040c5531%40googlegroups.com.

[tw5] Re: Does ActionListopsWidget not support the $timestamp attribute?

[Hubert]

Thank you both.

Temporarily setting $:/config/TimestampDisable to "yes" (and then deleting 
the tiddler) is the cleanest solution for my use case. Thank you for that, 
Eric.

As a side note, I could not locate $:/config/TimestampDisable in shadows 
(Advanced Search only shows this as part of the core) and on editing this 
tiddler, TW did produce the shadow tiddler warning. I could not find 
anything else in the TW documentation either. What's the "status" of 
$:/config/TimestampDisable? Is it yet another hidden setting?

Thank you again!

Regards,
Hubert


On Saturday, 29 February 2020 00:20:06 UTC, Eric Shulman wrote:
>
> On Thursday, February 27, 2020 at 6:33:17 AM UTC-8, Hubert wrote:
>>
>> The documentation <https://tiddlywiki.com/#ActionListopsWidget> does not 
>> explicitly state that setting the timestamp attribute with 
>> $action-listops is supported, so I'm assuming it's not.
>> Would it then be possible to extend the *ActionListopsWidget *to also 
>> take the timestamp attribute, in a similar fashion as it's possible in the 
>> ActionSetFieldWidget and ActionCreateTiddlerWidget?
>>
>
> While it might not be as succinct as having a timestamp attribute directly 
> in the $action-listops widget, you can currently disable and then re-enable 
> the $:/config/TimestampDisable value, like this:
>
> <$button> Populate 'myfield'
> <$action-setfield $tiddler="$:/config/TimestampDisable" $value="yes"/>
> <$action-listops $field="myfield" $subfilter="efg hlm pqr"/>
> <$action-setfield $tiddler="$:/config/TimestampDisable" $value="no"/>
> 
>
> The result is that the action-listops widget is invoked without changing 
> the timestamp of the tiddler being modified.
>
> 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/0ae9ef70-c45f-4d98-b850-83f9dee4dbf6%40googlegroups.com.

[tw5] Does ActionListopsWidget not support the $timestamp attribute?

[Hubert]

Hi All,

The documentation <https://tiddlywiki.com/#ActionListopsWidget> does not 
explicitly state that setting the timestamp attribute with $action-listops is 
supported, so I'm assuming it's not.

Would it then be possible to extend the *ActionListopsWidget *to also take 
the timestamp attribute, in a similar fashion as it's possible in the 
ActionSetFieldWidget and ActionCreateTiddlerWidget?

Thank you,
Hubert

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

[tw5] Re: tag dropdown slowdown - solution/discussion

[Hubert]

Hello,

Ad 2  see 
> https://tiddlywiki.com/#Hidden%20Setting%3A%20Tags%20Minimum%20Length 
> <https://www.google.com/url?q=https%3A%2F%2Ftiddlywiki.com%2F%23Hidden%2520Setting%253A%2520Tags%2520Minimum%2520Length=D=1=AFQjCNHytCbVtMv_dqQjfaKGbQQgvrmhIg>
>  
> so you can experiment with it already
>

Thank you for that Ton! A nice optimisation feature that I didn't know I 
needed.

It looks like yet another example of a useful feature that is missing in 
the documentation.

Regards,
Hubert

On Friday, 7 February 2020 13:11:54 UTC, Ton Gerner wrote:
>
> Hi,
>
> Ad 2  see 
> https://tiddlywiki.com/#Hidden%20Setting%3A%20Tags%20Minimum%20Length so 
> you can experiment with it already
>
> Cheers,
>
> Ton
>

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

[tw5] Re: [data tiddlers] dealing with ":" (from <>)

[Hubert]

Hi HC,
 

> "data tiddlers won't be worked on" does that mean that dictionary tiddlers 
> should be avoided??


Regarding long-term support for data tiddlers (of which there are two main 
types: dictionary and json), you might be interested in this thread 
<https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/tiddlywiki/n_4IWZqHIEs/nbRAykfMAgAJ>
.

As it stands, they are candidates for deprecation. I still use them a lot 
though, especially for thousands of small data points.

Just a slightly OT note.

Regards,
Hubert

On Wednesday, 5 February 2020 10:05:54 UTC, HC Haase wrote:
>
>
>
> onsdag den 5. februar 2020 kl. 03.28.43 UTC+1 skrev A Gloom:
>>
>> This doesn't help with writing titles to a data tiddler-- I don't know if 
>> urlencode with encode : but you must make those extra :'s into  for 
>> the data tiddler ignore them-- its only needed in title section before the 
>> data tiddler : seperator-- in the value section after the seperator it's 
>> not an issue
>>
>
>  I don't understand what you are saying here.. are you saying, that you 
> could change the colon to url ?  "the value section after the 
> separator it's not an issue"- that part I understand. Good to know. 
>
>
>> Mohammad is correct-- json is better especially since data tiddlers won't 
>> be worked on (but still supported) in the core any longer iirc
>>
>> Look at this at TWScripts-- I went by this when converting to data 
>> tiddlers to json
>>
>> https://kookma.github.io/TW-Scripts/#A%20Dictionary%20Project
>>
>
> For my problem I followd Mohammads advice and just used a json tiddler. 
> workd perfectly. 
>
> "data tiddlers won't be worked on" does that mean that dictionary tiddlers 
> should be avoided?? as I understand it,  the json can do the same as the 
> dictionary and more, so I don't see the need for the dictionary type. But 
> then again I dont know much about the 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/d2866120-231a-4406-a226-0f50732db331%40googlegroups.com.

[tw5] Image in a modal (CSS question)

[Hubert]

OK, I've solved it with:

.tc-modal img {
width: 100%;
object-fit: contain;
}

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

[tw5] Image in a modal (CSS question)

[Hubert]

Hello,

When I'm displaying images in a modal I see scroll bars: a large image is not 
resized to fit the modal window.

I've tried object-fit: contain; and max-width with vw values hoping that the 
image would be resized to fit modal window, but I've had no luck so far.

Just to note, I'm not using absolute positioning or absolute values (like px) 
anywhere.

Is there anything specific in regards to how tc.modal and its children handle 
images? I'm on mobile so can't check that conveniently at the moment. Still, I 
would appreciate advice if anyone is aware of any styling constraints that 
stand out.

Many thanks in advance.

Regards,
Hubert

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

[tw5] Re: TiddlyWiki support multi-user privilege

[Hubert]

Hi Peter,

Here's a quick and dirty solution for you. Attached are two json files:

   - Hide controls
   - Show controls

Drag *hide controls* onto your wiki (import the file). This will remove all 
tiddler control buttons and will essentially make your wiki read only.

To bring back controls, drag the *show controls* file onto your wiki. This 
restores your buttons and enables edits.

In the same way, you can remove/show individual buttons 'non-destructively' 
through CSS, if that's the route you wish to take.

There are many other ways to control access levels but this is probably the 
simplest (and one that does not require building a toggle/UI from scratch).

Regards,
Hubert

On Thursday, 30 January 2020 08:11:27 UTC, PeterTheDog wrote:
>
> I'm talking about read only.
> I'd like to share tiddlywiki on a network folder and only 1 user need to 
> be able to edit the wiki and other user only to read.
>
> thanks in advance.
>
>
>
> Il giorno giovedì 30 gennaio 2020 00:44:30 UTC+1, TonyM ha scritto:
>>
>> I think you may need to explain more what you are after. The only 
>> similtaniouse user solution is a server solution on bob or bobexe however 
>> the privilege side is I believe simple.
>>
>> Are you talking read only or also multiuser edits, do you want such edits 
>> only for each user or does everyone need to see the edits of others
>>
>> There are multiple ways to handle this, my preferred way still under 
>> design is serial editors. One at a time. You can force this on SharePoint.
>>
>> the ability to access the wiki in the first place can depend on your 
>> hosts authentication.
>>
>> Regards
>> Tony 
>>
>>

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


Hide controls.json
Description: application/json


Show controls.json
Description: application/json

[tw5] Re: How to hide creation date/time shown on page?

[Hubert]

Hi Jon,

Modify $:/core/ui/ViewTemplate/subtitle
>

Alternatively, paste this into a new tiddler and tag it with 
$:/tags/Stylesheet:

.tc-subtitle {
opacity: 0;
}

You can also remove the subtitle altogether by using *display: none;* but 
this probably will affect your layout, because the whole corresponding div 
will then be removed from view.

Hope this helps.

Regards,
Hubert

On Wednesday, 29 January 2020 07:21:40 UTC, Jon wrote:
>
> Hi,
>
> I have wiki with the creation date & time, normally shown at the top of 
> the tiddler, hidden and I'd like to reproduce that in another wiki - but I 
> didn't take a note of how its done.
>
> Any ideas?
>
> Regards
> Jon
>

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

Re: [tw5] Default tiddlers do not reload. Bug?

[Hubert]

Thank you Jeremy! Fixed for me too.

Best regards,
Hubert

On Monday, 27 January 2020 18:30:39 UTC, Jeremy Ruston wrote:
>
> Hi Mohammad, Hubert,
>
> I believe that this is now fixed:
>
>
> https://github.com/Jermolene/TiddlyWiki5/commit/29461403ed5868500ac8e9917e1428a5809ed0d3
>
> Please give the prerelease a try,
>
> Best wishes
>
> Jeremy
>
> On 27 Jan 2020, at 10:30, Mohammad > 
> wrote:
>
> Hi Jeremy,
>  This issue also occurred with fresh empty.html
>
> Please also see
> https://groups.google.com/d/msg/tiddlywiki/C1-ag-4m_-s/PA5wdQ8AAgAJ
>
> --Mohammad
>
> On Thursday, September 5, 2019 at 5:01:01 PM UTC+4:30, Jeremy Ruston wrote:
>>
>> Hi Hubert
>>
>> Thanks for the report. Do you have any plugins or customisations in your 
>> wiki? Are you able to duplicate it at https://tiddlywiki.com? 
>> <https://tiddlywiki.com/?> What operating system are you using?
>>
>> Best wishes
>>
>> Jeremy.
>>
>> On 5 Sep 2019, at 11:13, Hubert  wrote:
>>
>> Hello,
>>
>> This may be a possible bug.
>>
>> I have a single tiddler titled Startpage that displays at startup as the 
>> default tiddler (defined in 
>> $:/DefaultTiddlers). Sometimes the TW home button does not bring me back 
>> to the Startpage tiddler but displays an empty story river.
>>
>> My current setup:
>>
>>1. 5.1.20 (single file)
>>2. Firefox
>>3. Storyview: Zoomin
>>
>>
>> Steps to reproduce:
>>
>>1. Go to default tiddlers by clicking on the Home button
>>2. Close all (default) tiddlers (make the story river empty)
>>3. Again, go to default tiddlers by clicking on the Home button
>>4. Story river is empty (default tiddlers did not load this time 
>>around)
>>
>> I was originally transcluding my default tiddler (called Startpage) in 
>> $:/config/EmptyStoryMessage so that I could always see the Startpage 
>> tiddler, even if I've closed all tiddlers, by having 
>> {{Startpage||$:/core/ui/ViewTemplate}} in the above tiddler's text field. 
>> But since 5.1.20, blank story river started showing after the above 
>> sequence of clicks, whether EmptyStoryMessage was defined or not (I've 
>> tested both scenarios, even with a very simple Startpage that only had 
>> 'test' in the tiddler text and having deleted the system tiddler 
>> EmptyStoryMessage, removed all styling, macro definitions, any references 
>> whatsoever etc.).  
>>
>> If anyone was able to reproduce the same behaviour please let me know as 
>> this could then be a possible bug. Please note that I had not observed this 
>> behaviour prior to 5.1.20.
>>
>> Many thanks,
>> Hubert
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddl...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/8ba42bd8-cb12-4580-b16c-73f0fd5d5570%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/8ba42bd8-cb12-4580-b16c-73f0fd5d5570%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 tiddl...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/6370497a-73d9-407e-b859-a3f1c5e8e038%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywiki/6370497a-73d9-407e-b859-a3f1c5e8e038%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/345eb1dd-cfcb-44e9-ab56-29e4cb0f30c0%40googlegroups.com.

[tw5] Re: zoomin story view: is this a bug? or this is the normal behaviour

[Hubert]

Fantastic! Thank you Jeremy for implementing the fix.

Best regards,
Hubert

On Monday, 27 January 2020 18:40:56 UTC, Mohammad wrote:
>
> Hi Jeremy,
>
> I tested the new update at https://tiddlywiki.com/prerelease/
> I confirm the issue has gone! Tested on FF, Edge Chromium.
>
> Many thanks for your prompt action.
>
> --Mohammad
>
> On Monday, January 27, 2020 at 10:00:50 PM UTC+3:30, Jeremy Ruston wrote:
>>
>> I think this is fixed here:
>>
>>
>> https://github.com/Jermolene/TiddlyWiki5/commit/29461403ed5868500ac8e9917e1428a5809ed0d3
>>
>> Please give the prerelease a try,
>>
>> Best wishes
>>
>> Jeremy
>>
>> On Monday, January 27, 2020 at 6:15:43 AM UTC, Mohammad wrote:
>>>
>>>
>>>1. open https://tiddlywiki.com/prerelease/
>>>2. set story view to zoomin
>>>3. from sidebar tools, close all tiddlers
>>>4. click on Home
>>>
>>> Nothing appeasers!
>>>
>>> Do this in an empty.html
>>>
>>> Is this the normal behavior, Home button is not working for story view?
>>>
>>>
>>> --Mohammad
>>>
>>

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