Re: [tw5] Artwork for v5.2.0

[Mohammad Rahmani]

Springer,

 Many thanks! Your mockup is now great! I appreciate all your efforts both
for this mockup and also for hosting the competition art works!
 Kudos gos to you!


Best wishes
Mohammad


On Sun, Jun 27, 2021 at 9:32 PM springer  wrote:

> I've tweaked a *bit* more, and added Mohammad's submission to our gallery
> at:
>
> https://tw-logo-contest.tiddlyhost.com/
>
> -Springer
>
> On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:
>
>> Hi all, I had an exchange with Mohammad about the actual graphic file, to
>> which he does not have access.
>>
>> But the work was based on his own sketches, and it's not too hard to
>> replicate after discovering that the font is open-source Saira (google
>> font), apart from the curly brackets, whose font isn't yet clear to me. So
>> here's a rough mockup of Mohammad's design, though I admit I haven't
>> obsessed about replicating all the details:
>>
>> [image: Mohammad's JSON logo mockup.png]
>>
>> On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:
>>
>>> Just to have a little fun in this competition!
>>>
>>> These are my designs, but I'm not sure if they are suitable for the new
>>> release logo!
>>>
>>> [image: image.png]
>>>
>>>
>>>
>>> [image: img_342_chrome.png]
>>>
>>>
>>> and also!
>>>
>>> [image: img_341_chrome.png]
>>>
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston 
>>> wrote:
>>>
 This is to announce our regular competition for the artwork for the
 next release of TiddlyWiki 5. The next release is planned to be called
 v5.2.0, which requires a little explanation.

 We've bumped the minor version number because of a single very
 important change: for the first time in a decade, we're changing the format
 used to encode tiddlers into the HTML file.

 The new format is based on JSON, making it much easier to develop tools
 that produce or consume TW5 standalone HTML files. While there is some
 limited backwards compatibility, the developers of many existing tools will
 need to make modifications to keep things working with v5.2.0.

 Hence the version number change: it's intended to make every developer
 ask "Gosh, what could have changed to warrant such a big jump", and helps
 us to make sure that the news of the change is promulgated as widely and
 prominently as possible.

 The change also brings one big improvement for all users: field names
 now have no restrictions on which characters can be used, and are
 case-sensitive so that "MyField" is a valid fieldname, and refers to a
 different field than "myfield" (just like tiddler titles). Finally, we can
 have fields called "⛄️".

 These changes will be merged shortly, but in the meantime can be
 inspected here:

 https://github.com/Jermolene/TiddlyWiki5/pull/5708

 So, with that, back to the artwork competition. The task is to design
 the banner image that is shown on the splash screen and within the opening
 HelloThere tiddler. It is traditional for the artwork to reflect some of
 the changes in the new version.

 The rules for the competition are:

 * The version number (with the correct punctuation) must be clear and
 readable even when the banner is shown at a reduced size
 * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
 * The bottom 46 pixels will be obscured by the banner text “What’s new
 in 5.2.0” when it is displayed within HelloThere
 * Feel free to enter an updated version of artwork that was a runner-up
 in a previous competition
 * Reply to this message with your entry, or any questions

 Here are the posts about previous artwork competitions:

 v5.1.23 -
 https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
 v5.1.22 -
 https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
 v5.1.21 -
 https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ

 If you’ve got a great idea for the banner image, but don’t have the
 skills to produce finished artwork, do feel free to share your ideas in
 case somebody else would like to work on the artwork.

 The competition will be open for a week, at which point if there is
 more than one submission I’ll set up a Google Form for voting.

 Best wishes and many thanks,

 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+...@googlegroups.com.

>>> To view this discussion on the web visit
 https://groups.google.com/d/msgid/tiddlywiki/41EF749B-8AC8-412E-BE59-BBFCE7164340%40gmail.com
 

Re: [tw5] Re: butlast filter operator

[Damon Pritchett]

Thanks Eric,

I appreciate that. I looked at it, but I really don’t know JavaScript.
Makes me want to learn though.



On Sun, Jun 27, 2021 at 12:07 PM Eric Shulman  wrote:

> On Sunday, June 27, 2021 at 11:28:50 AM UTC-7 History Buff wrote:
>
>> I don't understand why a 0 in the butlast operator would yield no results
>>
>
> The butlast[] operator is defined in this shadow tiddler:
> https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Ffilters%2Flistops.js
>
> Here's the javascript code from that tiddler:
> exports.butlast = function(source,operator,options) {
> var count = $tw.utils.getInt(operator.operand,1),
> results = [];
> source(function(tiddler,title) {
> results.push(title);
> });
> return results.slice(0,-count);
> };
>
> The first line gets the operand value, defaulting to 1.
> The next 4 lines copy the entire list of items into a results array
> The last line uses the javascript slice() function to remove items from
> the results array and then return that array
>
> Here's the documentation for the javascript slice() function:
>
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/slice
>
> Note the description of the "end" parameter:
> Zero-based index before which to end extraction. slice extracts up to *but
> not including* end.
>
> Thus, when you used butlast[0], the filter code invokes slice(0,-0),
> i.e., "*starting from the first item up to but not including the first
> item*"
> which results in *no items* being returned.
>
> enjoy,
> -e
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/lROJc--2xFI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/c1f40a73-746d-4c39-89b9-6786c9caee0fn%40googlegroups.com
> 
> .
>

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

[tw5] Re: [recommendation] Installing a splash screen

[Charlie Veniot]

Yikes, did I ever take the scenic route.

+1 from me for sure.  That's a great idea.

More user friendly to "blank out" (opt-out of?) a preexisting splash screen 
if one doesn't want it than it is to set it all up from scratch when one 
wants a splash screen.

And way convenient to personalise a preexisting splash screen.




On Sunday, June 27, 2021 at 6:59:39 PM UTC-3 TW Tones wrote:

> Charlie et al,
>
> Yes, My suggestion is to use the existing splash screen method and put a 
> low fi one into the empty.html so all wikis have a minimalistic one 
> installed. Owners/designers can remove or customise the splash screen as 
> they wish.
>
>
>- The key reason to place it in the standard distribution is because 
>users with lower internet speeds, or as wikis grow larger, it becomes 
>necessary, to avoid people abandoning the link to a tiddlywiki. It is well 
>known that people can give up following a link if they find they are 
>waiting a few seconds. Because this is not already in place in every wiki, 
>I have already abandoned following some tiddlywiki links with my current 
>diminished internet speeds, and I know they have to load before they 
> become 
>interactive, where every day internet users do not. 
>- We do not want published tiddlywikis to look broken as a rule, it 
>will effect its reputation.
>- Empty.html represents a minimum standard for tiddlywiki from which 
>many build a wiki, thus it makes sense if we are trying to set a minimum 
>standard.
>   - The next best would be a core plugin to install a minimal splash 
>   screen.
>
> Regards
> Tones
>
> On Monday, 28 June 2021 at 03:29:41 UTC+10 cj.v...@gmail.com wrote:
>
>> BTW, refresh the page for that link, and you'll notice for a split second 
>> that the red area displays the TiddlyWiki splash screen (the one Eric 
>> points to.)
>>
>> Tones: I figured you already knew about the TiddlyWiki splash screen 
>> approach, and were looking for a little something more ?
>>
>> Or were you just simply suggesting that splash screen be setup in 
>> TiddlyWiki empty.html by default, so that folk just need to customise 
>> something that is already setup, instead of having to set it all up from 
>> scratch?
>>
>> On Sunday, June 27, 2021 at 12:55:34 PM UTC-3 Charlie Veniot wrote:
>>
>>> Oh yeah, "loader" in action:  
>>> https://leptitaurele.neocities.org/TiddlyWiki_Loader.html
>>>
>>> On Sunday, June 27, 2021 at 12:48:56 PM UTC-3 Charlie Veniot wrote:
>>>
 Until a non-technical/friendly solution comes along ...

 Sounds like the quickest thing to do at the moment, I think, is to have 
 a dinky "loader" html page that loads a TiddlyWiki in an iframe, keeping 
 the iframe hidden until TiddlyWiki is fully loaded, and showing splash in 
 the meantime.

 I imagine that needs some javascript, and me not being a fan, Ieave 
 that to somebody else.

 Here's something I cobbled together quickly, just for the giggles, as a 
 starting point  (Largely a copy paste from 
 https://stackoverflow.com/questions/325273/make-iframe-to-fit-100-of-containers-remaining-height
 ):

 
 
  Le P'tit Aurèle, un lexique acadien
  
   body, html {width: 100%; height: 100%; margin: 0; padding: 0}
   .first-row {position: absolute;top: 0; left: 0; right: 0; 
 height: 100px; background-color: lime;}
   .second-row {position: absolute; top: 100px; left: 0; right: 
 0; bottom: 0; background-color: red }
   .second-row iframe {display: block; width: 100%; height: 
 100%; border: none;}
  
 
  
  
   The TiddlyWiki is loading
  
  
   https://leptitaurele.neocities.org/LePtitAurele_PreviousVersion.html
 ">
  
 



 On Saturday, June 26, 2021 at 10:02:42 PM UTC-3 TW Tones wrote:

> Folks,
>
> I have currently got the unhappy situation where my broadband provider 
> has failed to move my broadband to my new address. Broken beaurocracy is 
> on 
> of my biggest frustrations. 
>
> What this means is I am running at less than 1MB internet access, and 
> I thought I would share the fact that many tiddlywikis look like they are 
> broken when no loading splash screen is available.
>
> So I would like to suggest not only Add a splash screen to large 
> wikis, a must, but perhaps even add them to all internet published wikis.
>
> If you agree please thumbs up here 
> https://github.com/Jermolene/TiddlyWiki5/discussions/5827
>
> Tones
>


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

[tw5] Re: [recommendation] Installing a splash screen

[TW Tones]

Charlie et al,

Yes, My suggestion is to use the existing splash screen method and put a 
low fi one into the empty.html so all wikis have a minimalistic one 
installed. Owners/designers can remove or customise the splash screen as 
they wish.


   - The key reason to place it in the standard distribution is because 
   users with lower internet speeds, or as wikis grow larger, it becomes 
   necessary, to avoid people abandoning the link to a tiddlywiki. It is well 
   known that people can give up following a link if they find they are 
   waiting a few seconds. Because this is not already in place in every wiki, 
   I have already abandoned following some tiddlywiki links with my current 
   diminished internet speeds, and I know they have to load before they become 
   interactive, where every day internet users do not. 
   - We do not want published tiddlywikis to look broken as a rule, it will 
   effect its reputation.
   - Empty.html represents a minimum standard for tiddlywiki from which 
   many build a wiki, thus it makes sense if we are trying to set a minimum 
   standard.
  - The next best would be a core plugin to install a minimal splash 
  screen.
   
Regards
Tones

On Monday, 28 June 2021 at 03:29:41 UTC+10 cj.v...@gmail.com wrote:

> BTW, refresh the page for that link, and you'll notice for a split second 
> that the red area displays the TiddlyWiki splash screen (the one Eric 
> points to.)
>
> Tones: I figured you already knew about the TiddlyWiki splash screen 
> approach, and were looking for a little something more ?
>
> Or were you just simply suggesting that splash screen be setup in 
> TiddlyWiki empty.html by default, so that folk just need to customise 
> something that is already setup, instead of having to set it all up from 
> scratch?
>
> On Sunday, June 27, 2021 at 12:55:34 PM UTC-3 Charlie Veniot wrote:
>
>> Oh yeah, "loader" in action:  
>> https://leptitaurele.neocities.org/TiddlyWiki_Loader.html
>>
>> On Sunday, June 27, 2021 at 12:48:56 PM UTC-3 Charlie Veniot wrote:
>>
>>> Until a non-technical/friendly solution comes along ...
>>>
>>> Sounds like the quickest thing to do at the moment, I think, is to have 
>>> a dinky "loader" html page that loads a TiddlyWiki in an iframe, keeping 
>>> the iframe hidden until TiddlyWiki is fully loaded, and showing splash in 
>>> the meantime.
>>>
>>> I imagine that needs some javascript, and me not being a fan, Ieave that 
>>> to somebody else.
>>>
>>> Here's something I cobbled together quickly, just for the giggles, as a 
>>> starting point  (Largely a copy paste from 
>>> https://stackoverflow.com/questions/325273/make-iframe-to-fit-100-of-containers-remaining-height
>>> ):
>>>
>>> 
>>> 
>>>  Le P'tit Aurèle, un lexique acadien
>>>  
>>>   body, html {width: 100%; height: 100%; margin: 0; padding: 0}
>>>   .first-row {position: absolute;top: 0; left: 0; right: 0; 
>>> height: 100px; background-color: lime;}
>>>   .second-row {position: absolute; top: 100px; left: 0; right: 
>>> 0; bottom: 0; background-color: red }
>>>   .second-row iframe {display: block; width: 100%; height: 100%; 
>>> border: none;}
>>>  
>>> 
>>>  
>>>  
>>>   The TiddlyWiki is loading
>>>  
>>>  
>>>   https://leptitaurele.neocities.org/LePtitAurele_PreviousVersion.html
>>> ">
>>>  
>>> 
>>>
>>>
>>>
>>> On Saturday, June 26, 2021 at 10:02:42 PM UTC-3 TW Tones wrote:
>>>
 Folks,

 I have currently got the unhappy situation where my broadband provider 
 has failed to move my broadband to my new address. Broken beaurocracy is 
 on 
 of my biggest frustrations. 

 What this means is I am running at less than 1MB internet access, and I 
 thought I would share the fact that many tiddlywikis look like they are 
 broken when no loading splash screen is available.

 So I would like to suggest not only Add a splash screen to large wikis, 
 a must, but perhaps even add them to all internet published wikis.

 If you agree please thumbs up here 
 https://github.com/Jermolene/TiddlyWiki5/discussions/5827

 Tones

>>>

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

[tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

[Si]

Hi Mario,

I only just noticed your Uni-link Search feature! Very handy -  I have been 
frequently writing things like [[really good idea|Really Good Ideas]], so 
this will save me a lot of time.

I have a question however: Is there any way to customise exactly how the 
search is applied?

Many of my titles are in singular (in English), but I often refer to them 
in the plural. For example I might have a tiddler with text like this: "The 
library contained a lot of [[books|Book]]."

I'm wondering if there is a way to use Uni-link search, but tweak it so it 
will ignore the final "s"? So [[books|??]] would automatically link to 
[[Book]].

Anyway I was very happy to find this plugin, thanks!
On Wednesday, 17 March 2021 at 22:50:11 UTC PMario wrote:

> Hi Folks, 
>
> I just released an updated version of the "uni-link" plugin 
>  V 2.1.0 
>
> *Intro-Video*: Can be seen at the link above
>
> *What's New*
>
> Uni-link Search
>
> [[case insensitive title|??]] will do a literal, case-insensitive title 
> search. It will return the first tiddler it finds. 
>
> Examples:
> [[this is a test|??]]  will link to eg: "This is a Test" ... If the 
> tiddler exists!
>
> Important
>
>- uni-link V2.1.0 does not contain a "relink plugin" addOn!
>- So if you change the tiddler name, those links won't be changed!
>
> relink-support should follow soon.
>
> The original Intro-thread is: [INTRO] uni-link V1.0.0 
>  
>
> have fun!
> mario
>
> *PS - If you like it: Support it  :) *
>

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

[tw5] Re: Refresh tiddler automatically

[Eric Shulman]

On Sunday, June 27, 2021 at 12:55:56 PM UTC-7 Soren Bjornstad wrote:

> OK, I started having a major problem which took me a good hour to 
> debug…but I have a fix. When I tried to use the TiddlyWiki CLI (for 
> instance, with a --savewikifolder), it would hang indefinitely, because it 
> is waiting on the timer to be torn down before terminating. Fortunately, 
> there is a tag $:/tags/StartupAction/Browser 
> 
>  which 
> invokes the timer setup only when viewing the wiki in the browser. So I 
> just removed $:/tags/StartupAction and added that one, and now it's working 
> fine again.
>

Nice catch!  I don't use the CLI much at all, so that issue never came up 
for me.  I've updated 
http://tiddlytools.com/timer.html#TiddlyTools%2FTime%2FTicker to 
use $:/tags/StartupAction/Browser instead of $:/tags/StartupAction so that 
other won't have the same issue when using the default ticker.

Note: I've also done a *feature update* 
to http://tiddlytools.com/timer.html#TiddlyTools%2FTime%2FCalendar so that 
calendar dates now show alarms and timers in addition to events and tiddler 
changes.  If you prefer, you can use the Calendar Settings (gear icon) to 
omit alarms and/or timers from the Calendar display.  You can also change 
the date background color for alarms and/or timers.  By default, dates with 
alarms will use "OrangeRed" and dates with timers will use "LightYellow" .

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/04d17cfd-7fd7-492f-b554-d66cbc3403dbn%40googlegroups.com.

[tw5] Re: Restyling a drop zone

[Soren Bjornstad]

Yes, $:/sib/Templates/Automatic/OpenTopBar 
.
 
I tagged it $:/tags/TopLeftBar, but I think one could instead use the 
PageTemplate or several other tags as well since the location on screen is 
fixed via CSS.

<$list filter=<> variable=_>

<>



(ff  
is a *feature flag *conditional, which makes it possible to show and hide 
it on the fly, and separately for the public and private editions. I don't 
have it on in public, but if you search for FeatureFlags and turn the "Open 
top bar" checkbox on, you can see this in action.)

On Sunday, June 27, 2021 at 12:06:14 PM UTC-5 iamdar...@gmail.com wrote:

> Hello Soren!
>
> As always awesome solution/work!
>
> I just had a quick question; is it safe to assume that you need a tiddler, 
> with the following code, open in the storylist for your code to work? Or 
> did you add it to a template?
>
> 
> <>
> 
>
> Thanks!
>
> On Sunday, June 27, 2021 at 12:41:25 PM UTC-4 Soren Bjornstad wrote:
>
>> Maki, yeah, I had previously tried inline-block along with a bunch of 
>> other things in that rule. It didn't help because I hadn't targeted the 
>> item underneath it as well.
>>
>> Saq, thanks, that was *very* helpful. (For anyone else who comes along, 
>> that should be "tc-dragover", with a dash, not a dot.)
>>
>> The selector I had missed targeting was *.tc-droppable.tc-dragover > 
>> .tc-droppable-placeholder*. (Both the droppable divs and the placeholder 
>> divs beneath them need to be inline-block.) I also needed this goofy rule:
>>
>> div.sib-quick-tiddler-jump ul > div.tc-droppable 
>> div.tc-droppable-placeholder svg {
>> height: 0;
>> width: 1rem;
>> }
>>
>> Yes, that's an *svg*, because TiddlyWiki uses a blank image within a 
>> *div* for the placeholder after the last *li* in list-links-draggable. I 
>> assume there is a good reason for this. :-)
>>
>> Final version for anyone interested:
>>
>> div.sib-quick-tiddler-jump {
>> background-color: <>;
>> position: fixed;
>> z-index: 850;
>> display: inline-block;
>> top: 0;
>> right: 0;
>> left: 0;
>> text-align: center;
>> height: 30px;
>> overflow: auto;
>> border-bottom: 1px solid <>;
>> padding-bottom: 3px;
>> padding-top: 3px;
>> font-size: 12px;
>> }
>>
>> div.sib-quick-tiddler-jump a {
>> color: <>;
>> }
>>
>> div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
>> font-weight: normal;
>> }
>>
>> div.sib-quick-tiddler-jump ul {
>> list-style-type: none;
>> margin: 0;
>> padding: 0;
>> }
>>
>> /* Droppable placeholders take up no space until we drag something there. 
>> */
>> div.sib-quick-tiddler-jump ul li.tc-droppable 
>> div.tc-droppable-placeholder {
>> height: 0;
>> }
>>
>> /* TW inserts this as a placeholder after the last item. We have to 
>> resize it to match the rest. */
>> div.sib-quick-tiddler-jump ul > div.tc-droppable 
>> div.tc-droppable-placeholder svg {
>> height: 0;
>> width: 1rem;
>> }
>>
>> div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
>> display: inline-block;
>> }
>>
>> div.sib-quick-tiddler-jump ul > li.tc-droppable div,
>> div.sib-quick-tiddler-jump ul > div.tc-droppable div {
>> display: inline-block;
>> }
>>
>> div.sib-quick-tiddler-jump .tc-droppable.tc-dragover > 
>> .tc-droppable-placeholder {
>> display: inline-block;
>> background-color: green;
>> border: 0px;
>> width: 1rem;
>> height: 1rem;
>> margin-bottom: 0;
>> margin-top: 0;
>> padding-bottom: 0;
>> padding-top: 0;
>> }
>>
>> div.sib-quick-tiddler-jump ul li, div.sib-quick-tiddler-jump ul > 
>> div.tc-droppable {
>> display: inline-block;
>> }
>>
>> .sib-quick-tiddler-jump ul li div:nth-child(2):after {
>> padding-left: 5px;
>> content: "·";
>> padding-right: 5px;
>> }
>>
>> /* not last-child because there's a dropzone after it */
>> .sib-quick-tiddler-jump ul li:nth-last-child(2) div:after {
>> content: "";
>> }
>>
>>
>> On Sunday, June 27, 2021 at 4:11:05 AM UTC-5 saq.i...@gmail.com wrote:
>>
>>> Inspect the dropzone DOM node with the browser dev tools and add the 
>>> class "tc.dragover". This will allow you see what CSS is active during the 
>>> drag over and make it easier to arrive at a solution.
>>>
>>> On Sunday, June 27, 2021 at 1:18:07 AM UTC+2 Soren Bjornstad wrote:
>>>
 I'm creating a horizontal list of my open tiddlers that runs across the 
 top of the wiki, like this:

 [image: Screenshot from 2021-06-26 18-13-01.png]

 It's based on *list-links-draggable* and works great except for when I 
 try to drag something to a different position. When I try, the bar scrolls 
 to fit the dropzone on a separate line, so that I can no longer see where 
 I'm moving the tiddler to:

 [image: 2.png]

 I tried poking through the theme CSS for a bit, but wasn't able to find 
 anything that worked. It doesn't help that it's impossible to carefully 
 inspect the DOM with the browser devtools 

Re: [tw5] NoteTaking in Streams

[Si Si]

Whoops, sent the previous message before finishing it:


> That is definitely a nice idea. I wonder if we might take it a step
> further and just drop the last word (which may be incomplete). This is
> untested:

 <$text text={{{
> [length[]compare:number:lt[40]then]
> ~[split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]]
> }}}/>
> What do you think?


I did consider this, but I'm actually not sure which way looks better. I
don't think that cutting off an incomplete word half way through looks bad,
and I might even prefer it, though I couldn't say why. Possibly just
because that's what windows explorer does so I'm just used to it.

On Sun, 27 Jun 2021 at 20:59, Si Si  wrote:

> Saq,
>
> I've also been considering asking for volunteers for a small group of
>> regular users of Streams for testing new features..
>
>
> I'm happy to test stuff out as required.
>
>
>> from my perspective however how, much effort I put into adding new
>> features to Streams is highly dependent on how many people regularly use it
>> and find that it imparts value. Call it a personal quirk but wanting to
>> impart the most value possible is something that often drives my decision
>> making in terms of what I dedicate my time to.
>
>
> It says a lot of positive things about your character if that is what
> motivates you!
>
> That is definitely a nice idea. I wonder if we might take it a step
>> further and just drop the last word (which may be incomplete). This is
>> untested:
>
>  <$text text={{{
>> [length[]compare:number:lt[40]then]
>> ~[split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]]
>> }}}/>
>> What do you think?
>
>
> On Sat, 26 Jun 2021 at 14:21, Saq Imtiaz  wrote:
>
>> @Walt hopefully you are getting some helpful feedback here. Apologies for
>> the slight digression caused by my replying to Streams specific comments
>> and feedback.
>>
>> @fred you can also export using a filter from the Filter tab in Advanced
>> Search
>>
>> @Si,
>>
>>
>>> On the topic of how many people use it, maybe you could consider
>>> creating a Google Form and linking to it from the download page, asking
>>> users if they would take a second to answer some brief questions?
>>>
>>
>> I've been considering it for some time actually. Apart from feedback on
>> workflow, just knowing whether the number of people regularly using Streams
>> is < 10, 10-20, or 20+ would be very helpful.
>>
>>
>>> I was also wondering if you had considered setting up a way for users to
>>> donate? Not necessarily to fund development, just to show appreciation for
>>> great free software! I am not currently in a position to contribute much,
>>> but in the future I would certainly be happy to subscribe to a patreon or
>>> whatever.
>>>
>>
>> I think the most value for myself would be in just getting regular,
>> precise and on-topic feedback. Implementing new features in the absence of
>> user feedback is just driving blind from my perspective. I also find it
>> very frustrating and motivation sapping when I post ideas or demos and at
>> times get feedback that is far off topic or just so poorly written that it
>> is more frustrating than helpful.  Mind you, I try to be very understanding
>> of users for whom English is not their first language. It is actually very
>> pleasing how constructive and helpful this thread has been thus far in
>> comparison.
>>
>> I've also been considering asking for volunteers for a small group of
>> regular users of Streams for testing new features.. from my perspective
>> however how, much effort I put into adding new features to Streams is
>> highly dependent on how many people regularly use it and find that it
>> imparts value. Call it a personal quirk but wanting to impart the most
>> value possible is something that often drives my decision making in terms
>> of what I dedicate my time to. Otherwise the motivation for work on Streams
>> is just whatever seems interesting for me personally from a technical
>> perspective.
>>
>>
>>> I would add that like Mario I am very happy with the current features of
>>> streams, though I have made the following tweak to the text display for the
>>> breadcrumbs. It's a very minor thing, but in my opinion looks nicer than
>>> just cutting off the title mid-word:
>>>
>>> <$text text={{{
>>> [length[]compare:number:lt[40]then]
>>> ~[split[]first[40]join[]trim[]addsuffix[...]] }}}/>
>>>
>>
>> That is definitely a nice idea. I wonder if we might take it a step
>> further and just drop the last word (which may be incomplete). This is
>> untested:
>>
>>  <$text text={{{
>> [length[]compare:number:lt[40]then]
>> ~[split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]]
>> }}}/>
>>
>> What do you think?
>> Cheers,
>> Saq
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
>> To 

Re: [tw5] NoteTaking in Streams

[Si Si]

Saq,

I've also been considering asking for volunteers for a small group of
> regular users of Streams for testing new features..


I'm happy to test stuff out as required.


> from my perspective however how, much effort I put into adding new
> features to Streams is highly dependent on how many people regularly use it
> and find that it imparts value. Call it a personal quirk but wanting to
> impart the most value possible is something that often drives my decision
> making in terms of what I dedicate my time to.


It says a lot of positive things about your character if that is what
motivates you!

That is definitely a nice idea. I wonder if we might take it a step further
> and just drop the last word (which may be incomplete). This is untested:

 <$text text={{{
> [length[]compare:number:lt[40]then]
> ~[split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]]
> }}}/>
> What do you think?


On Sat, 26 Jun 2021 at 14:21, Saq Imtiaz  wrote:

> @Walt hopefully you are getting some helpful feedback here. Apologies for
> the slight digression caused by my replying to Streams specific comments
> and feedback.
>
> @fred you can also export using a filter from the Filter tab in Advanced
> Search
>
> @Si,
>
>
>> On the topic of how many people use it, maybe you could consider creating
>> a Google Form and linking to it from the download page, asking users if
>> they would take a second to answer some brief questions?
>>
>
> I've been considering it for some time actually. Apart from feedback on
> workflow, just knowing whether the number of people regularly using Streams
> is < 10, 10-20, or 20+ would be very helpful.
>
>
>> I was also wondering if you had considered setting up a way for users to
>> donate? Not necessarily to fund development, just to show appreciation for
>> great free software! I am not currently in a position to contribute much,
>> but in the future I would certainly be happy to subscribe to a patreon or
>> whatever.
>>
>
> I think the most value for myself would be in just getting regular,
> precise and on-topic feedback. Implementing new features in the absence of
> user feedback is just driving blind from my perspective. I also find it
> very frustrating and motivation sapping when I post ideas or demos and at
> times get feedback that is far off topic or just so poorly written that it
> is more frustrating than helpful.  Mind you, I try to be very understanding
> of users for whom English is not their first language. It is actually very
> pleasing how constructive and helpful this thread has been thus far in
> comparison.
>
> I've also been considering asking for volunteers for a small group of
> regular users of Streams for testing new features.. from my perspective
> however how, much effort I put into adding new features to Streams is
> highly dependent on how many people regularly use it and find that it
> imparts value. Call it a personal quirk but wanting to impart the most
> value possible is something that often drives my decision making in terms
> of what I dedicate my time to. Otherwise the motivation for work on Streams
> is just whatever seems interesting for me personally from a technical
> perspective.
>
>
>> I would add that like Mario I am very happy with the current features of
>> streams, though I have made the following tweak to the text display for the
>> breadcrumbs. It's a very minor thing, but in my opinion looks nicer than
>> just cutting off the title mid-word:
>>
>> <$text text={{{
>> [length[]compare:number:lt[40]then]
>> ~[split[]first[40]join[]trim[]addsuffix[...]] }}}/>
>>
>
> That is definitely a nice idea. I wonder if we might take it a step
> further and just drop the last word (which may be incomplete). This is
> untested:
>
>  <$text text={{{
> [length[]compare:number:lt[40]then]
> ~[split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]]
> }}}/>
>
> What do you think?
> Cheers,
> Saq
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/0b65a408-28d6-4709-8e16-feb01355858en%40googlegroups.com
> 
> .
>

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

[tw5] Re: Refresh tiddler automatically

[Soren Bjornstad]

OK, I started having a major problem which took me a good hour to debug…but 
I have a fix. When I tried to use the TiddlyWiki CLI (for instance, with a 
--savewikifolder), it would hang indefinitely, because it is waiting on the 
timer to be torn down before terminating. Fortunately, there is a tag 
$:/tags/StartupAction/Browser 

 which 
invokes the timer setup only when viewing the wiki in the browser. So I 
just removed $:/tags/StartupAction and added that one, and now it's working 
fine again.

On Sunday, June 27, 2021 at 10:45:26 AM UTC-5 Soren Bjornstad wrote:

> Eric,
>
> This worked perfectly! Thanks for the widget and the instructions.
>
> On Saturday, June 26, 2021 at 11:57:27 PM UTC-5 Eric Shulman wrote:
>
>> On Saturday, June 26, 2021 at 8:05:15 PM UTC-7 Soren Bjornstad wrote:
>>
>>> Has anyone found a way to make TiddlyWiki re-render a part of the page 
>>> template periodically?
>>
>> I'd like to have a section in my page template that does a calculation 
>>> based on the current time, and would love if I didn't have to click a 
>>> button all the time to update it. 
>>
>> Maybe some kind of event that's scheduled in JavaScript and fires every 
>>> minute?
>>
>>
>> My TiddlyTools Timer functions can do this.
>>
>> 1) Copy the $action-timeout widget from 
>>   
>>  http://tiddlytools.com/timer.html#TiddlyTools%2FTime%2Faction-timeout.js 
>> 
>>
>> 2) Create a "MinuteTickerStartup" tiddler, tagged with 
>> *$:/tags/StartupAction*, containing:
>> \define minute_ticker() <$action-setfield 
>> $tiddler="$:/temp/time/minuteticker" text=<> />
>> <$action-timeout interval=6 actions=<> />
>>
>> 3) In a tiddler tagged with *$:/tags/PageTemplate*, put the content you 
>> want to automatically re-render each minute, like this:
>> <$vars ticker={{$:/temp/time/minuteticker}}>
>>*** content you want to re-render ***
>> 
>>
>> Notes:
>> 1) MinuteTickerStartup is invoked *once* when you load your TiddlyWiki 
>> and sets up an javascript "interval" timer that is triggered every minute 
>> (6 milliseconds)
>> 2) The ticker action updates the contents of *$:/temp/time/minuteticker* to 
>> contain the current time (0hh0mm0ss)
>> 3) The $vars "wrapper" in the page template tiddler creates a refresh 
>> dependency associated with the current value in 
>> *$:/temp/time/minuteticker*
>>
>> The result is that whatever content is in your page template will be 
>> re-rendered once per minute.  Q.E.D.
>>
>> 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/b880880e-77f1-460a-b604-93f833cff211n%40googlegroups.com.

Re: [tw5] Artwork for v5.2.0

[James Anderson]

one more using emojis, though someone would probably need to redo the new 
and fish tiddlers as i doubt emoji are free to use whereever we like.

[image: tiddler.png]



>Télumire
>>but the way you represent it with different colours led me to think that 
this is about colors, maybe printing ? 

Not wanting to spell it out, but light can be considered part of a field 
too :) that was the angle i was going for. 

>Mohammed
I like your design! :)

Thanks,
James



On Sunday, 27 June 2021 at 18:05:08 UTC+1 saq.i...@gmail.com wrote:

> It is probably worth mentioning that the logo does not *have* to do with 
> any new features being introduced. So if anyone has other ideas, go for it.
>
> On Sunday, June 27, 2021 at 7:02:55 PM UTC+2 springer wrote:
>
>> I've tweaked a *bit* more, and added Mohammad's submission to our gallery 
>> at:
>>
>> https://tw-logo-contest.tiddlyhost.com/
>>
>> -Springer
>>
>> On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:
>>
>>> Hi all, I had an exchange with Mohammad about the actual graphic file, 
>>> to which he does not have access.
>>>
>>> But the work was based on his own sketches, and it's not too hard to 
>>> replicate after discovering that the font is open-source Saira (google 
>>> font), apart from the curly brackets, whose font isn't yet clear to me. So 
>>> here's a rough mockup of Mohammad's design, though I admit I haven't 
>>> obsessed about replicating all the details:
>>>
>>> [image: Mohammad's JSON logo mockup.png]
>>>
>>> On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:
>>>
 Just to have a little fun in this competition!

 These are my designs, but I'm not sure if they are suitable for the new 
 release logo! 

 [image: image.png]



 [image: img_342_chrome.png]


 and also!

 [image: img_341_chrome.png]




 Best wishes
 Mohammad


 On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  
 wrote:

> This is to announce our regular competition for the artwork for the 
> next release of TiddlyWiki 5. The next release is planned to be called 
> v5.2.0, which requires a little explanation.
>
> We've bumped the minor version number because of a single very 
> important change: for the first time in a decade, we're changing the 
> format 
> used to encode tiddlers into the HTML file.
>
> The new format is based on JSON, making it much easier to develop 
> tools that produce or consume TW5 standalone HTML files. While there is 
> some limited backwards compatibility, the developers of many existing 
> tools 
> will need to make modifications to keep things working with v5.2.0.
>
> Hence the version number change: it's intended to make every developer 
> ask "Gosh, what could have changed to warrant such a big jump", and helps 
> us to make sure that the news of the change is promulgated as widely and 
> prominently as possible.
>
> The change also brings one big improvement for all users: field names 
> now have no restrictions on which characters can be used, and are 
> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
> different field than "myfield" (just like tiddler titles). Finally, we 
> can 
> have fields called "⛄️".
>
> These changes will be merged shortly, but in the meantime can be 
> inspected here:
>
> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>
> So, with that, back to the artwork competition. The task is to design 
> the banner image that is shown on the splash screen and within the 
> opening 
> HelloThere tiddler. It is traditional for the artwork to reflect some of 
> the changes in the new version.
>
> The rules for the competition are:
>
> * The version number (with the correct punctuation) must be clear and 
> readable even when the banner is shown at a reduced size
> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
> * The bottom 46 pixels will be obscured by the banner text “What’s new 
> in 5.2.0” when it is displayed within HelloThere
> * Feel free to enter an updated version of artwork that was a 
> runner-up in a previous competition
> * Reply to this message with your entry, or any questions
>
> Here are the posts about previous artwork competitions:
>
> v5.1.23 - 
> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
> v5.1.22 - 
> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
> v5.1.21 - 
> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>
> If you’ve got a great idea for the banner image, but don’t have the 
> skills to produce finished artwork, do feel free to share your ideas in 
> case somebody else would like to work on the artwork.
>
> The competition will be 

[tw5] Re: butlast filter operator

[Eric Shulman]

On Sunday, June 27, 2021 at 11:28:50 AM UTC-7 History Buff wrote:

> I don't understand why a 0 in the butlast operator would yield no results
>

The butlast[] operator is defined in this shadow tiddler:
https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Ffilters%2Flistops.js

Here's the javascript code from that tiddler:
exports.butlast = function(source,operator,options) {
var count = $tw.utils.getInt(operator.operand,1),
results = [];
source(function(tiddler,title) {
results.push(title);
});
return results.slice(0,-count);
};

The first line gets the operand value, defaulting to 1.
The next 4 lines copy the entire list of items into a results array
The last line uses the javascript slice() function to remove items from the 
results array and then return that array

Here's the documentation for the javascript slice() function:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/slice

Note the description of the "end" parameter:
Zero-based index before which to end extraction. slice extracts up to *but 
not including* end.

Thus, when you used butlast[0], the filter code invokes slice(0,-0),
i.e., "*starting from the first item up to but not including the first item*
"
which results in *no items* being returned.

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/c1f40a73-746d-4c39-89b9-6786c9caee0fn%40googlegroups.com.

[tw5] butlast filter operator

[History Buff]

All,

I have a general question about the butlast filter operator. I had a filter 
where I had the butlast operator as the last item with a variable for the 
parameter. All worked fine until the variable was 0.  I expected that it 
wouldn't remove any of the last items, but what I got was no results at 
all. I fixed it be making sure that the variable was never 0, but I don't 
understand why a 0 in the butlast operator would yield no results. Can 
anyone explain that to me? 

Thanks so much!

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

[tw5] Re: [recommendation] Installing a splash screen

[Charlie Veniot]

BTW, refresh the page for that link, and you'll notice for a split second 
that the red area displays the TiddlyWiki splash screen (the one Eric 
points to.)

Tones: I figured you already knew about the TiddlyWiki splash screen 
approach, and were looking for a little something more ?

Or were you just simply suggesting that splash screen be setup in 
TiddlyWiki empty.html by default, so that folk just need to customise 
something that is already setup, instead of having to set it all up from 
scratch?

On Sunday, June 27, 2021 at 12:55:34 PM UTC-3 Charlie Veniot wrote:

> Oh yeah, "loader" in action:  
> https://leptitaurele.neocities.org/TiddlyWiki_Loader.html
>
> On Sunday, June 27, 2021 at 12:48:56 PM UTC-3 Charlie Veniot wrote:
>
>> Until a non-technical/friendly solution comes along ...
>>
>> Sounds like the quickest thing to do at the moment, I think, is to have a 
>> dinky "loader" html page that loads a TiddlyWiki in an iframe, keeping the 
>> iframe hidden until TiddlyWiki is fully loaded, and showing splash in the 
>> meantime.
>>
>> I imagine that needs some javascript, and me not being a fan, Ieave that 
>> to somebody else.
>>
>> Here's something I cobbled together quickly, just for the giggles, as a 
>> starting point  (Largely a copy paste from 
>> https://stackoverflow.com/questions/325273/make-iframe-to-fit-100-of-containers-remaining-height
>> ):
>>
>> 
>> 
>>  Le P'tit Aurèle, un lexique acadien
>>  
>>   body, html {width: 100%; height: 100%; margin: 0; padding: 0}
>>   .first-row {position: absolute;top: 0; left: 0; right: 0; 
>> height: 100px; background-color: lime;}
>>   .second-row {position: absolute; top: 100px; left: 0; right: 0; 
>> bottom: 0; background-color: red }
>>   .second-row iframe {display: block; width: 100%; height: 100%; 
>> border: none;}
>>  
>> 
>>  
>>  
>>   The TiddlyWiki is loading
>>  
>>  
>>   https://leptitaurele.neocities.org/LePtitAurele_PreviousVersion.html
>> ">
>>  
>> 
>>
>>
>>
>> On Saturday, June 26, 2021 at 10:02:42 PM UTC-3 TW Tones wrote:
>>
>>> Folks,
>>>
>>> I have currently got the unhappy situation where my broadband provider 
>>> has failed to move my broadband to my new address. Broken beaurocracy is on 
>>> of my biggest frustrations. 
>>>
>>> What this means is I am running at less than 1MB internet access, and I 
>>> thought I would share the fact that many tiddlywikis look like they are 
>>> broken when no loading splash screen is available.
>>>
>>> So I would like to suggest not only Add a splash screen to large wikis, 
>>> a must, but perhaps even add them to all internet published wikis.
>>>
>>> If you agree please thumbs up here 
>>> https://github.com/Jermolene/TiddlyWiki5/discussions/5827
>>>
>>> Tones
>>>
>>

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

[tw5] Re: Restyling a drop zone

[Darth Mole]

Hello Soren!

As always awesome solution/work!

I just had a quick question; is it safe to assume that you need a tiddler, 
with the following code, open in the storylist for your code to work? Or 
did you add it to a template?


<>


Thanks!

On Sunday, June 27, 2021 at 12:41:25 PM UTC-4 Soren Bjornstad wrote:

> Maki, yeah, I had previously tried inline-block along with a bunch of 
> other things in that rule. It didn't help because I hadn't targeted the 
> item underneath it as well.
>
> Saq, thanks, that was *very* helpful. (For anyone else who comes along, 
> that should be "tc-dragover", with a dash, not a dot.)
>
> The selector I had missed targeting was *.tc-droppable.tc-dragover > 
> .tc-droppable-placeholder*. (Both the droppable divs and the placeholder 
> divs beneath them need to be inline-block.) I also needed this goofy rule:
>
> div.sib-quick-tiddler-jump ul > div.tc-droppable 
> div.tc-droppable-placeholder svg {
> height: 0;
> width: 1rem;
> }
>
> Yes, that's an *svg*, because TiddlyWiki uses a blank image within a *div* 
> for 
> the placeholder after the last *li* in list-links-draggable. I assume 
> there is a good reason for this. :-)
>
> Final version for anyone interested:
>
> div.sib-quick-tiddler-jump {
> background-color: <>;
> position: fixed;
> z-index: 850;
> display: inline-block;
> top: 0;
> right: 0;
> left: 0;
> text-align: center;
> height: 30px;
> overflow: auto;
> border-bottom: 1px solid <>;
> padding-bottom: 3px;
> padding-top: 3px;
> font-size: 12px;
> }
>
> div.sib-quick-tiddler-jump a {
> color: <>;
> }
>
> div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
> font-weight: normal;
> }
>
> div.sib-quick-tiddler-jump ul {
> list-style-type: none;
> margin: 0;
> padding: 0;
> }
>
> /* Droppable placeholders take up no space until we drag something there. 
> */
> div.sib-quick-tiddler-jump ul li.tc-droppable div.tc-droppable-placeholder 
> {
> height: 0;
> }
>
> /* TW inserts this as a placeholder after the last item. We have to resize 
> it to match the rest. */
> div.sib-quick-tiddler-jump ul > div.tc-droppable 
> div.tc-droppable-placeholder svg {
> height: 0;
> width: 1rem;
> }
>
> div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
> display: inline-block;
> }
>
> div.sib-quick-tiddler-jump ul > li.tc-droppable div,
> div.sib-quick-tiddler-jump ul > div.tc-droppable div {
> display: inline-block;
> }
>
> div.sib-quick-tiddler-jump .tc-droppable.tc-dragover > 
> .tc-droppable-placeholder {
> display: inline-block;
> background-color: green;
> border: 0px;
> width: 1rem;
> height: 1rem;
> margin-bottom: 0;
> margin-top: 0;
> padding-bottom: 0;
> padding-top: 0;
> }
>
> div.sib-quick-tiddler-jump ul li, div.sib-quick-tiddler-jump ul > 
> div.tc-droppable {
> display: inline-block;
> }
>
> .sib-quick-tiddler-jump ul li div:nth-child(2):after {
> padding-left: 5px;
> content: "·";
> padding-right: 5px;
> }
>
> /* not last-child because there's a dropzone after it */
> .sib-quick-tiddler-jump ul li:nth-last-child(2) div:after {
> content: "";
> }
>
>
> On Sunday, June 27, 2021 at 4:11:05 AM UTC-5 saq.i...@gmail.com wrote:
>
>> Inspect the dropzone DOM node with the browser dev tools and add the 
>> class "tc.dragover". This will allow you see what CSS is active during the 
>> drag over and make it easier to arrive at a solution.
>>
>> On Sunday, June 27, 2021 at 1:18:07 AM UTC+2 Soren Bjornstad wrote:
>>
>>> I'm creating a horizontal list of my open tiddlers that runs across the 
>>> top of the wiki, like this:
>>>
>>> [image: Screenshot from 2021-06-26 18-13-01.png]
>>>
>>> It's based on *list-links-draggable* and works great except for when I 
>>> try to drag something to a different position. When I try, the bar scrolls 
>>> to fit the dropzone on a separate line, so that I can no longer see where 
>>> I'm moving the tiddler to:
>>>
>>> [image: 2.png]
>>>
>>> I tried poking through the theme CSS for a bit, but wasn't able to find 
>>> anything that worked. It doesn't help that it's impossible to carefully 
>>> inspect the DOM with the browser devtools since the mouse is tied up with 
>>> the drag. Can someone point me to how I'd make the dropzone end up 
>>> horizontally inline with the items, instead of above/below them?
>>>
>>> Here's the code of the tiddler/CSS that I currently have:
>>>
>>> 
>>> <>
>>> 
>>>
>>> 
>>> div.sib-quick-tiddler-jump {
>>> background-color: <>;
>>> position: fixed;
>>> z-index: 850;
>>> display: inline-block;
>>> top: 0;
>>> right: 0;
>>> left: 0;
>>> text-align: center;
>>> height: 25px;
>>> overflow: auto;
>>> border-bottom: 1px solid <>;
>>> padding-bottom: 3px;
>>> padding-top: 3px;
>>> font-size: 12px;
>>> }
>>>
>>> div.sib-quick-tiddler-jump a {
>>> color: <>;
>>> }
>>>
>>> div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
>>> font-weight: normal;
>>> }
>>>
>>> div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
>>> display: block;
>>> 

Re: [tw5] Artwork for v5.2.0

[Saq Imtiaz]

It is probably worth mentioning that the logo does not *have* to do with 
any new features being introduced. So if anyone has other ideas, go for it.

On Sunday, June 27, 2021 at 7:02:55 PM UTC+2 springer wrote:

> I've tweaked a *bit* more, and added Mohammad's submission to our gallery 
> at:
>
> https://tw-logo-contest.tiddlyhost.com/
>
> -Springer
>
> On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:
>
>> Hi all, I had an exchange with Mohammad about the actual graphic file, to 
>> which he does not have access.
>>
>> But the work was based on his own sketches, and it's not too hard to 
>> replicate after discovering that the font is open-source Saira (google 
>> font), apart from the curly brackets, whose font isn't yet clear to me. So 
>> here's a rough mockup of Mohammad's design, though I admit I haven't 
>> obsessed about replicating all the details:
>>
>> [image: Mohammad's JSON logo mockup.png]
>>
>> On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:
>>
>>> Just to have a little fun in this competition!
>>>
>>> These are my designs, but I'm not sure if they are suitable for the new 
>>> release logo! 
>>>
>>> [image: image.png]
>>>
>>>
>>>
>>> [image: img_342_chrome.png]
>>>
>>>
>>> and also!
>>>
>>> [image: img_341_chrome.png]
>>>
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  
>>> wrote:
>>>
 This is to announce our regular competition for the artwork for the 
 next release of TiddlyWiki 5. The next release is planned to be called 
 v5.2.0, which requires a little explanation.

 We've bumped the minor version number because of a single very 
 important change: for the first time in a decade, we're changing the 
 format 
 used to encode tiddlers into the HTML file.

 The new format is based on JSON, making it much easier to develop tools 
 that produce or consume TW5 standalone HTML files. While there is some 
 limited backwards compatibility, the developers of many existing tools 
 will 
 need to make modifications to keep things working with v5.2.0.

 Hence the version number change: it's intended to make every developer 
 ask "Gosh, what could have changed to warrant such a big jump", and helps 
 us to make sure that the news of the change is promulgated as widely and 
 prominently as possible.

 The change also brings one big improvement for all users: field names 
 now have no restrictions on which characters can be used, and are 
 case-sensitive so that "MyField" is a valid fieldname, and refers to a 
 different field than "myfield" (just like tiddler titles). Finally, we can 
 have fields called "⛄️".

 These changes will be merged shortly, but in the meantime can be 
 inspected here:

 https://github.com/Jermolene/TiddlyWiki5/pull/5708

 So, with that, back to the artwork competition. The task is to design 
 the banner image that is shown on the splash screen and within the opening 
 HelloThere tiddler. It is traditional for the artwork to reflect some of 
 the changes in the new version.

 The rules for the competition are:

 * The version number (with the correct punctuation) must be clear and 
 readable even when the banner is shown at a reduced size
 * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
 * The bottom 46 pixels will be obscured by the banner text “What’s new 
 in 5.2.0” when it is displayed within HelloThere
 * Feel free to enter an updated version of artwork that was a runner-up 
 in a previous competition
 * Reply to this message with your entry, or any questions

 Here are the posts about previous artwork competitions:

 v5.1.23 - 
 https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
 v5.1.22 - 
 https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
 v5.1.21 - 
 https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ

 If you’ve got a great idea for the banner image, but don’t have the 
 skills to produce finished artwork, do feel free to share your ideas in 
 case somebody else would like to work on the artwork.

 The competition will be open for a week, at which point if there is 
 more than one submission I’ll set up a Google Form for voting.

 Best wishes and many thanks,

 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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/41EF749B-8AC8-412E-BE59-BBFCE7164340%40gmail.com
  
 

[tw5] Re: Restyling a drop zone

[Saq Imtiaz]

 

> Saq, thanks, that was *very* helpful. (For anyone else who comes along, 
> that should be "tc-dragover", with a dash, not a dot.)
>
 
 Happy it helped and apologies for the typo.

Another neat trick when trying to inspect tricky CSS that involves 
transient states is to trigger the debugger after a time out by executing 
this in the console:

setTimeout(function() { debugger; }, 2000);

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

Re: [tw5] Artwork for v5.2.0

[springer]

I've tweaked a *bit* more, and added Mohammad's submission to our gallery 
at:

https://tw-logo-contest.tiddlyhost.com/

-Springer

On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:

> Hi all, I had an exchange with Mohammad about the actual graphic file, to 
> which he does not have access.
>
> But the work was based on his own sketches, and it's not too hard to 
> replicate after discovering that the font is open-source Saira (google 
> font), apart from the curly brackets, whose font isn't yet clear to me. So 
> here's a rough mockup of Mohammad's design, though I admit I haven't 
> obsessed about replicating all the details:
>
> [image: Mohammad's JSON logo mockup.png]
>
> On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:
>
>> Just to have a little fun in this competition!
>>
>> These are my designs, but I'm not sure if they are suitable for the new 
>> release logo! 
>>
>> [image: image.png]
>>
>>
>>
>> [image: img_342_chrome.png]
>>
>>
>> and also!
>>
>> [image: img_341_chrome.png]
>>
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  
>> wrote:
>>
>>> This is to announce our regular competition for the artwork for the next 
>>> release of TiddlyWiki 5. The next release is planned to be called v5.2.0, 
>>> which requires a little explanation.
>>>
>>> We've bumped the minor version number because of a single very important 
>>> change: for the first time in a decade, we're changing the format used to 
>>> encode tiddlers into the HTML file.
>>>
>>> The new format is based on JSON, making it much easier to develop tools 
>>> that produce or consume TW5 standalone HTML files. While there is some 
>>> limited backwards compatibility, the developers of many existing tools will 
>>> need to make modifications to keep things working with v5.2.0.
>>>
>>> Hence the version number change: it's intended to make every developer 
>>> ask "Gosh, what could have changed to warrant such a big jump", and helps 
>>> us to make sure that the news of the change is promulgated as widely and 
>>> prominently as possible.
>>>
>>> The change also brings one big improvement for all users: field names 
>>> now have no restrictions on which characters can be used, and are 
>>> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
>>> different field than "myfield" (just like tiddler titles). Finally, we can 
>>> have fields called "⛄️".
>>>
>>> These changes will be merged shortly, but in the meantime can be 
>>> inspected here:
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>>>
>>> So, with that, back to the artwork competition. The task is to design 
>>> the banner image that is shown on the splash screen and within the opening 
>>> HelloThere tiddler. It is traditional for the artwork to reflect some of 
>>> the changes in the new version.
>>>
>>> The rules for the competition are:
>>>
>>> * The version number (with the correct punctuation) must be clear and 
>>> readable even when the banner is shown at a reduced size
>>> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
>>> * The bottom 46 pixels will be obscured by the banner text “What’s new 
>>> in 5.2.0” when it is displayed within HelloThere
>>> * Feel free to enter an updated version of artwork that was a runner-up 
>>> in a previous competition
>>> * Reply to this message with your entry, or any questions
>>>
>>> Here are the posts about previous artwork competitions:
>>>
>>> v5.1.23 - 
>>> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>>> v5.1.22 - 
>>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>>> v5.1.21 - 
>>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>>
>>> If you’ve got a great idea for the banner image, but don’t have the 
>>> skills to produce finished artwork, do feel free to share your ideas in 
>>> case somebody else would like to work on the artwork.
>>>
>>> The competition will be open for a week, at which point if there is more 
>>> than one submission I’ll set up a Google Form for voting.
>>>
>>> Best wishes and many thanks,
>>>
>>> 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/41EF749B-8AC8-412E-BE59-BBFCE7164340%40gmail.com
>>>  
>>> 
>>> .
>>>
>>

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

Re: [tw5] Artwork for v5.2.0

[springer]

Hi all, I had an exchange with Mohammad about the actual graphic file, to 
which he does not have access.

But the work was based on his own sketches, and it's not too hard to 
replicate after discovering that the font is open-source Saira (google 
font), apart from the curly brackets, whose font isn't yet clear to me. So 
here's a rough mockup of Mohammad's design, though I admit I haven't 
obsessed about replicating all the details:

[image: Mohammad's JSON logo mockup.png]

On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:

> Just to have a little fun in this competition!
>
> These are my designs, but I'm not sure if they are suitable for the new 
> release logo! 
>
> [image: image.png]
>
>
>
> [image: img_342_chrome.png]
>
>
> and also!
>
> [image: img_341_chrome.png]
>
>
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  wrote:
>
>> This is to announce our regular competition for the artwork for the next 
>> release of TiddlyWiki 5. The next release is planned to be called v5.2.0, 
>> which requires a little explanation.
>>
>> We've bumped the minor version number because of a single very important 
>> change: for the first time in a decade, we're changing the format used to 
>> encode tiddlers into the HTML file.
>>
>> The new format is based on JSON, making it much easier to develop tools 
>> that produce or consume TW5 standalone HTML files. While there is some 
>> limited backwards compatibility, the developers of many existing tools will 
>> need to make modifications to keep things working with v5.2.0.
>>
>> Hence the version number change: it's intended to make every developer 
>> ask "Gosh, what could have changed to warrant such a big jump", and helps 
>> us to make sure that the news of the change is promulgated as widely and 
>> prominently as possible.
>>
>> The change also brings one big improvement for all users: field names now 
>> have no restrictions on which characters can be used, and are 
>> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
>> different field than "myfield" (just like tiddler titles). Finally, we can 
>> have fields called "⛄️".
>>
>> These changes will be merged shortly, but in the meantime can be 
>> inspected here:
>>
>> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>>
>> So, with that, back to the artwork competition. The task is to design the 
>> banner image that is shown on the splash screen and within the opening 
>> HelloThere tiddler. It is traditional for the artwork to reflect some of 
>> the changes in the new version.
>>
>> The rules for the competition are:
>>
>> * The version number (with the correct punctuation) must be clear and 
>> readable even when the banner is shown at a reduced size
>> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
>> * The bottom 46 pixels will be obscured by the banner text “What’s new in 
>> 5.2.0” when it is displayed within HelloThere
>> * Feel free to enter an updated version of artwork that was a runner-up 
>> in a previous competition
>> * Reply to this message with your entry, or any questions
>>
>> Here are the posts about previous artwork competitions:
>>
>> v5.1.23 - 
>> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>> v5.1.22 - 
>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>> v5.1.21 - 
>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>
>> If you’ve got a great idea for the banner image, but don’t have the 
>> skills to produce finished artwork, do feel free to share your ideas in 
>> case somebody else would like to work on the artwork.
>>
>> The competition will be open for a week, at which point if there is more 
>> than one submission I’ll set up a Google Form for voting.
>>
>> Best wishes and many thanks,
>>
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/41EF749B-8AC8-412E-BE59-BBFCE7164340%40gmail.com
>>  
>> 
>> .
>>
>

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

[tw5] Re: Restyling a drop zone

[Soren Bjornstad]

Maki, yeah, I had previously tried inline-block along with a bunch of other 
things in that rule. It didn't help because I hadn't targeted the item 
underneath it as well.

Saq, thanks, that was *very* helpful. (For anyone else who comes along, 
that should be "tc-dragover", with a dash, not a dot.)

The selector I had missed targeting was *.tc-droppable.tc-dragover > 
.tc-droppable-placeholder*. (Both the droppable divs and the placeholder 
divs beneath them need to be inline-block.) I also needed this goofy rule:

div.sib-quick-tiddler-jump ul > div.tc-droppable 
div.tc-droppable-placeholder svg {
height: 0;
width: 1rem;
}

Yes, that's an *svg*, because TiddlyWiki uses a blank image within a *div* for 
the placeholder after the last *li* in list-links-draggable. I assume there 
is a good reason for this. :-)

Final version for anyone interested:

div.sib-quick-tiddler-jump {
background-color: <>;
position: fixed;
z-index: 850;
display: inline-block;
top: 0;
right: 0;
left: 0;
text-align: center;
height: 30px;
overflow: auto;
border-bottom: 1px solid <>;
padding-bottom: 3px;
padding-top: 3px;
font-size: 12px;
}

div.sib-quick-tiddler-jump a {
color: <>;
}

div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
font-weight: normal;
}

div.sib-quick-tiddler-jump ul {
list-style-type: none;
margin: 0;
padding: 0;
}

/* Droppable placeholders take up no space until we drag something there. */
div.sib-quick-tiddler-jump ul li.tc-droppable div.tc-droppable-placeholder {
height: 0;
}

/* TW inserts this as a placeholder after the last item. We have to resize 
it to match the rest. */
div.sib-quick-tiddler-jump ul > div.tc-droppable 
div.tc-droppable-placeholder svg {
height: 0;
width: 1rem;
}

div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
display: inline-block;
}

div.sib-quick-tiddler-jump ul > li.tc-droppable div,
div.sib-quick-tiddler-jump ul > div.tc-droppable div {
display: inline-block;
}

div.sib-quick-tiddler-jump .tc-droppable.tc-dragover > 
.tc-droppable-placeholder {
display: inline-block;
background-color: green;
border: 0px;
width: 1rem;
height: 1rem;
margin-bottom: 0;
margin-top: 0;
padding-bottom: 0;
padding-top: 0;
}

div.sib-quick-tiddler-jump ul li, div.sib-quick-tiddler-jump ul > 
div.tc-droppable {
display: inline-block;
}

.sib-quick-tiddler-jump ul li div:nth-child(2):after {
padding-left: 5px;
content: "·";
padding-right: 5px;
}

/* not last-child because there's a dropzone after it */
.sib-quick-tiddler-jump ul li:nth-last-child(2) div:after {
content: "";
}


On Sunday, June 27, 2021 at 4:11:05 AM UTC-5 saq.i...@gmail.com wrote:

> Inspect the dropzone DOM node with the browser dev tools and add the class 
> "tc.dragover". This will allow you see what CSS is active during the drag 
> over and make it easier to arrive at a solution.
>
> On Sunday, June 27, 2021 at 1:18:07 AM UTC+2 Soren Bjornstad wrote:
>
>> I'm creating a horizontal list of my open tiddlers that runs across the 
>> top of the wiki, like this:
>>
>> [image: Screenshot from 2021-06-26 18-13-01.png]
>>
>> It's based on *list-links-draggable* and works great except for when I 
>> try to drag something to a different position. When I try, the bar scrolls 
>> to fit the dropzone on a separate line, so that I can no longer see where 
>> I'm moving the tiddler to:
>>
>> [image: 2.png]
>>
>> I tried poking through the theme CSS for a bit, but wasn't able to find 
>> anything that worked. It doesn't help that it's impossible to carefully 
>> inspect the DOM with the browser devtools since the mouse is tied up with 
>> the drag. Can someone point me to how I'd make the dropzone end up 
>> horizontally inline with the items, instead of above/below them?
>>
>> Here's the code of the tiddler/CSS that I currently have:
>>
>> 
>> <>
>> 
>>
>> 
>> div.sib-quick-tiddler-jump {
>> background-color: <>;
>> position: fixed;
>> z-index: 850;
>> display: inline-block;
>> top: 0;
>> right: 0;
>> left: 0;
>> text-align: center;
>> height: 25px;
>> overflow: auto;
>> border-bottom: 1px solid <>;
>> padding-bottom: 3px;
>> padding-top: 3px;
>> font-size: 12px;
>> }
>>
>> div.sib-quick-tiddler-jump a {
>> color: <>;
>> }
>>
>> div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
>> font-weight: normal;
>> }
>>
>> div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
>> display: block;
>> position: relative;
>> top: 0;
>> left: 0;
>> right: 0;
>> }
>>
>> div.sib-quick-tiddler-jump ul {
>> list-style-type: none;
>> margin: 0;
>> padding: 0;
>> }
>>
>> div.sib-quick-tiddler-jump ul li {
>> display: inline-block;
>> }
>>
>> .sib-quick-tiddler-jump ul li div:after {
>> padding-left: 5px;
>> content: "·";
>> padding-right: 5px;
>> }
>>
>> /* not last-child because there's a dropzone after it */
>> .sib-quick-tiddler-jump ul li:nth-last-child(2) div:after {
>> content: "";
>> }
>> 
>>
>

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

[tw5] Re: [recommendation] Installing a splash screen

[Eric Shulman]

On Sunday, June 27, 2021 at 8:48:56 AM UTC-7 cj.v...@gmail.com wrote:

> Until a non-technical/friendly solution comes along ...


TiddlyWiki already has support for using a "splash screen" while loading

See https://tiddlywiki.com/#Creating%20a%20splash%20screen

-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/7637e9ef-57a0-4a33-933d-95a7b8717e38n%40googlegroups.com.

[tw5] Re: [recommendation] Installing a splash screen

[Charlie Veniot]

Oh yeah, "loader" in action:  
https://leptitaurele.neocities.org/TiddlyWiki_Loader.html

On Sunday, June 27, 2021 at 12:48:56 PM UTC-3 Charlie Veniot wrote:

> Until a non-technical/friendly solution comes along ...
>
> Sounds like the quickest thing to do at the moment, I think, is to have a 
> dinky "loader" html page that loads a TiddlyWiki in an iframe, keeping the 
> iframe hidden until TiddlyWiki is fully loaded, and showing splash in the 
> meantime.
>
> I imagine that needs some javascript, and me not being a fan, Ieave that 
> to somebody else.
>
> Here's something I cobbled together quickly, just for the giggles, as a 
> starting point  (Largely a copy paste from 
> https://stackoverflow.com/questions/325273/make-iframe-to-fit-100-of-containers-remaining-height
> ):
>
> 
> 
>  Le P'tit Aurèle, un lexique acadien
>  
>   body, html {width: 100%; height: 100%; margin: 0; padding: 0}
>   .first-row {position: absolute;top: 0; left: 0; right: 0; 
> height: 100px; background-color: lime;}
>   .second-row {position: absolute; top: 100px; left: 0; right: 0; 
> bottom: 0; background-color: red }
>   .second-row iframe {display: block; width: 100%; height: 100%; 
> border: none;}
>  
> 
>  
>  
>   The TiddlyWiki is loading
>  
>  
>   https://leptitaurele.neocities.org/LePtitAurele_PreviousVersion.html
> ">
>  
> 
>
>
>
> On Saturday, June 26, 2021 at 10:02:42 PM UTC-3 TW Tones wrote:
>
>> Folks,
>>
>> I have currently got the unhappy situation where my broadband provider 
>> has failed to move my broadband to my new address. Broken beaurocracy is on 
>> of my biggest frustrations. 
>>
>> What this means is I am running at less than 1MB internet access, and I 
>> thought I would share the fact that many tiddlywikis look like they are 
>> broken when no loading splash screen is available.
>>
>> So I would like to suggest not only Add a splash screen to large wikis, a 
>> must, but perhaps even add them to all internet published wikis.
>>
>> If you agree please thumbs up here 
>> https://github.com/Jermolene/TiddlyWiki5/discussions/5827
>>
>> Tones
>>
>

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

[tw5] Re: [recommendation] Installing a splash screen

[Charlie Veniot]

Until a non-technical/friendly solution comes along ...

Sounds like the quickest thing to do at the moment, I think, is to have a 
dinky "loader" html page that loads a TiddlyWiki in an iframe, keeping the 
iframe hidden until TiddlyWiki is fully loaded, and showing splash in the 
meantime.

I imagine that needs some javascript, and me not being a fan, Ieave that to 
somebody else.

Here's something I cobbled together quickly, just for the giggles, as a 
starting point  (Largely a copy paste from 
https://stackoverflow.com/questions/325273/make-iframe-to-fit-100-of-containers-remaining-height):



 Le P'tit Aurèle, un lexique acadien
 
  body, html {width: 100%; height: 100%; margin: 0; padding: 0}
  .first-row {position: absolute;top: 0; left: 0; right: 0; height: 
100px; background-color: lime;}
  .second-row {position: absolute; top: 100px; left: 0; right: 0; 
bottom: 0; background-color: red }
  .second-row iframe {display: block; width: 100%; height: 100%; 
border: none;}
 

 
 
  The TiddlyWiki is loading
 
 
  https://leptitaurele.neocities.org/LePtitAurele_PreviousVersion.html;>
 




On Saturday, June 26, 2021 at 10:02:42 PM UTC-3 TW Tones wrote:

> Folks,
>
> I have currently got the unhappy situation where my broadband provider has 
> failed to move my broadband to my new address. Broken beaurocracy is on of 
> my biggest frustrations. 
>
> What this means is I am running at less than 1MB internet access, and I 
> thought I would share the fact that many tiddlywikis look like they are 
> broken when no loading splash screen is available.
>
> So I would like to suggest not only Add a splash screen to large wikis, a 
> must, but perhaps even add them to all internet published wikis.
>
> If you agree please thumbs up here 
> https://github.com/Jermolene/TiddlyWiki5/discussions/5827
>
> Tones
>

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

[tw5] Re: Refresh tiddler automatically

[Soren Bjornstad]

Eric,

This worked perfectly! Thanks for the widget and the instructions.

On Saturday, June 26, 2021 at 11:57:27 PM UTC-5 Eric Shulman wrote:

> On Saturday, June 26, 2021 at 8:05:15 PM UTC-7 Soren Bjornstad wrote:
>
>> Has anyone found a way to make TiddlyWiki re-render a part of the page 
>> template periodically?
>
> I'd like to have a section in my page template that does a calculation 
>> based on the current time, and would love if I didn't have to click a 
>> button all the time to update it. 
>
> Maybe some kind of event that's scheduled in JavaScript and fires every 
>> minute?
>
>
> My TiddlyTools Timer functions can do this.
>
> 1) Copy the $action-timeout widget from 
>   
>  http://tiddlytools.com/timer.html#TiddlyTools%2FTime%2Faction-timeout.js 
> 
>
> 2) Create a "MinuteTickerStartup" tiddler, tagged with 
> *$:/tags/StartupAction*, containing:
> \define minute_ticker() <$action-setfield 
> $tiddler="$:/temp/time/minuteticker" text=<> />
> <$action-timeout interval=6 actions=<> />
>
> 3) In a tiddler tagged with *$:/tags/PageTemplate*, put the content you 
> want to automatically re-render each minute, like this:
> <$vars ticker={{$:/temp/time/minuteticker}}>
>*** content you want to re-render ***
> 
>
> Notes:
> 1) MinuteTickerStartup is invoked *once* when you load your TiddlyWiki 
> and sets up an javascript "interval" timer that is triggered every minute 
> (6 milliseconds)
> 2) The ticker action updates the contents of *$:/temp/time/minuteticker* to 
> contain the current time (0hh0mm0ss)
> 3) The $vars "wrapper" in the page template tiddler creates a refresh 
> dependency associated with the current value in 
> *$:/temp/time/minuteticker*
>
> The result is that whatever content is in your page template will be 
> re-rendered once per minute.  Q.E.D.
>
> 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/5d586d13-48f6-4e44-b06c-be92e55b8461n%40googlegroups.com.

[tw5] Re: Linking to Field Values

[Merry Machiavelli]

@Eric Shulman Great, that works, thanks! Really minor follow-up question. 
What do I have to put before [field:father-id{!!id}] to get it to actually 
show up on the page as text and a link? 

Currently, I can do this: <> (which is 
the inverse, for finding fathers as opposed to finding sons) but that 
produces a list e.g.

   - Robert Smith

I just want it to show

Robert Smith

Because people only have one biological father! I think the <> 
bit is a 'macro'? I've tried:

<[field:id{!!father}]>
<<[field:id{!!father}]>>
<<$link [field:id{!!father}]>>
<$link to=[field:id{!!father}]>[field:id{!!father}]

All with no luck.

Slightly more general question, I've found myself a bit baffled by 
macros/whatever they are. TiddlyWiki as loads of examples of operators, but 
unless you know what you need to put before them, they aren't actually 
usable! For example, I know the subtract operator looks like this: 

[[23]subtract[19]]

But obviously, just putting that in a tiddler doesn't produce the value 
"4", you have to put something before it. I've got no clue what that should 
be, and the code actually used in the wiki: 

<<.operator-example 1 "[[23]subtract[19]]">>
Does not work. 

Sorry to dump loads of questions! I just get the impression that TiddlyWiki 
is incredibly powerful and perfect for my use-case, but there is a lot of 
basic syntax stuff that I just don't get. 
On Sunday, June 27, 2021 at 1:13:52 PM UTC+1 Eric Shulman wrote:

> On Sunday, June 27, 2021 at 4:04:14 AM UTC-7 merry.ma...@gmail.com wrote:
>
>> Now doing this <>
>> Works to retrieve the children of Robert Smith. However, that involves 
>> manually typing in Robert Smith's id. Instead I want something like 
>> this: <>
>> But that doesn't work...
>>
>
> When specifying the parameter value for a filter operator, *the type of 
> brackets indicate the kind of parameter value* you are using:
>
> square brackets are for *literal* values,  e.g. 
> [field:father-id[634750-LiR]]
> angle brackets are for *variable* values, e.g., 
> [field:father-id] 
> curly braces are for *field references*, e.g.,  [field:father-id{!!id}] 
>
> Also note that within filter syntax, use *single* brackets/braces, rather 
> than the *doubled* brackets/braces that are used within regular wiki text 
> syntax;
> i.e., [634750-LiR] instead of [[634750-LiR]],  instead of 
> <>, and {!!id}} instead of {{!!id}}
>
> 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/a7683e9a-7bb6-48d4-8d67-054bc776fd6bn%40googlegroups.com.

[tw5] Re: Soren Bjornstad’s reading list tutorial

[Soren Bjornstad]

And you're very welcome for the tutorial!

On Sunday, June 27, 2021 at 8:28:04 AM UTC-5 Soren Bjornstad wrote:

> Rehali,
>
> I see two problems here:
>
> 1. You have a typo in your transclusion syntax – it should be *{!!title}*, 
> not *{!title}*.
> 2. If the author field contains a link in [[double square brackets]] or is 
> a list of several authors, like I did in the video, then you need to use 
> *contains:*, not *field: *– *field: *does an exact match on the text 
> contents of the field, and this won't be an exact match because the field 
> contains extra square brackets. (Alternatively, if you only ever want to 
> have one author, you could just remove the brackets and not treat it as a 
> list.)
>
> On Saturday, June 26, 2021 at 11:21:13 PM UTC-5 Rehali wrote:
>
>> Before the question, first of all if you read this Soren then many thanks 
>> for your excellent tutorial on YouTube - it’s what got me started with 
>> tiddlywiki.
>>
>> Now the question. If you’ve seen the tutorial, what I would like to do is 
>> to display a list of the books on the tiddly belonging to their author. The 
>> author field for each book is a link, as in [[Charles Dickens]]
>>
>> I was hoping to use a filter on each Author tiddler like:
>>
>> [tag[Source]field:author{!title}]
>>
>> but I can’t get anything to work.
>>
>> Any help would be much appreciated.
>>
>

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

[tw5] Re: Soren Bjornstad’s reading list tutorial

[Soren Bjornstad]

Rehali,

I see two problems here:

1. You have a typo in your transclusion syntax – it should be *{!!title}*, 
not *{!title}*.
2. If the author field contains a link in [[double square brackets]] or is 
a list of several authors, like I did in the video, then you need to use 
*contains:*, not *field: *– *field: *does an exact match on the text 
contents of the field, and this won't be an exact match because the field 
contains extra square brackets. (Alternatively, if you only ever want to 
have one author, you could just remove the brackets and not treat it as a 
list.)

On Saturday, June 26, 2021 at 11:21:13 PM UTC-5 Rehali wrote:

> Before the question, first of all if you read this Soren then many thanks 
> for your excellent tutorial on YouTube - it’s what got me started with 
> tiddlywiki.
>
> Now the question. If you’ve seen the tutorial, what I would like to do is 
> to display a list of the books on the tiddly belonging to their author. The 
> author field for each book is a link, as in [[Charles Dickens]]
>
> I was hoping to use a filter on each Author tiddler like:
>
> [tag[Source]field:author{!title}]
>
> but I can’t get anything to work.
>
> Any help would be much appreciated.
>

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

[tw5] Re: Linking to Field Values

[Eric Shulman]

On Sunday, June 27, 2021 at 4:04:14 AM UTC-7 merry.ma...@gmail.com wrote:

> Now doing this <>
> Works to retrieve the children of Robert Smith. However, that involves 
> manually typing in Robert Smith's id. Instead I want something like 
> this: <>
> But that doesn't work...
>

When specifying the parameter value for a filter operator, *the type of 
brackets indicate the kind of parameter value* you are using:

square brackets are for *literal* values,  e.g. 
[field:father-id[634750-LiR]]
angle brackets are for *variable* values, e.g., 
[field:father-id] 
curly braces are for *field references*, e.g.,  [field:father-id{!!id}] 

Also note that within filter syntax, use *single* brackets/braces, rather 
than the *doubled* brackets/braces that are used within regular wiki text 
syntax;
i.e., [634750-LiR] instead of [[634750-LiR]],  instead of 
<>, and {!!id}} instead of {{!!id}}

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/182c6d0b-163e-475d-a373-28d681115a22n%40googlegroups.com.

[tw5] Re: Linking to Field Values

[Merry Machiavelli]

Sorry, supplemental question involving using fields¬

Another thing I want to do is use id and father-id / mother-id fields to 
automatically list the children of an individual. Ids are preferable to 
just names/titles, because of the chance of duplicate names.

How it might work is this. Say Robert Smith has two sons, John Smith and 
Peter Smith. That could be represented in fields like this:

(John Smith fields)

id: 365974-LlO
father-id: 634750-LiR

(Peter Smith fields)

id:  571157-OnU
father-id: 634750-LiR

(Robert Smith fields)

id:  634750-LiR
father-id: 612745-GbF

Now doing this <>

Works to retrieve the children of Robert Smith. However, that involves 
manually typing in Robert Smith's id. Instead I want something like 
this: <>

But that doesn't work...


On Sunday, June 27, 2021 at 10:07:48 AM UTC+1 Merry Machiavelli wrote:

> Thank you so much @Soren Bjornstad, that works perfectly! I think I tried 
> something close to that at one point, I just messed up the syntax!
>
> @iamdar my use case is that I want to be able to mass-produce 
> wikipedia-style bios for individuals, where the the same basic info comes 
> up in multiple parts of the 'article'/tiddler. 
>
> For example, in the opening line, it might say "John Smith was born in 
> MadeupLand", the side bar might also mention he was born in MadeupLand. If 
> I link both references to MadeupLand through a field i.e. using <$link 
> to={{!!birthcountry}} /> then I only have to specify the country John Smith 
> was born in once, in the field. If I iterate this process 100 times (using 
> the same code for most of the body of the article, just customising it with 
> novel information) it saves a lot of typing.
>
> Another advantage is that it makes it easier to call groups of people who 
> share a particle bit of vital information, without necessary creating a tag 
> for, say, "born in 1872" (which, I could do...it just seemed clunky?). The 
> main example that comes to mind is using surnames as a way to list every 
> individual from a particular patrilineal lineage (assuming it's an unusual 
> surname that unrelated individuals are unlikely to share within my 
> group...I could also have a specific familyID field). 
>
>
>

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

[tw5] Re: Restyling a drop zone

[Saq Imtiaz]

Inspect the dropzone DOM node with the browser dev tools and add the class 
"tc.dragover". This will allow you see what CSS is active during the drag 
over and make it easier to arrive at a solution.

On Sunday, June 27, 2021 at 1:18:07 AM UTC+2 Soren Bjornstad wrote:

> I'm creating a horizontal list of my open tiddlers that runs across the 
> top of the wiki, like this:
>
> [image: Screenshot from 2021-06-26 18-13-01.png]
>
> It's based on *list-links-draggable* and works great except for when I 
> try to drag something to a different position. When I try, the bar scrolls 
> to fit the dropzone on a separate line, so that I can no longer see where 
> I'm moving the tiddler to:
>
> [image: 2.png]
>
> I tried poking through the theme CSS for a bit, but wasn't able to find 
> anything that worked. It doesn't help that it's impossible to carefully 
> inspect the DOM with the browser devtools since the mouse is tied up with 
> the drag. Can someone point me to how I'd make the dropzone end up 
> horizontally inline with the items, instead of above/below them?
>
> Here's the code of the tiddler/CSS that I currently have:
>
> 
> <>
> 
>
> 
> div.sib-quick-tiddler-jump {
> background-color: <>;
> position: fixed;
> z-index: 850;
> display: inline-block;
> top: 0;
> right: 0;
> left: 0;
> text-align: center;
> height: 25px;
> overflow: auto;
> border-bottom: 1px solid <>;
> padding-bottom: 3px;
> padding-top: 3px;
> font-size: 12px;
> }
>
> div.sib-quick-tiddler-jump a {
> color: <>;
> }
>
> div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
> font-weight: normal;
> }
>
> div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
> display: block;
> position: relative;
> top: 0;
> left: 0;
> right: 0;
> }
>
> div.sib-quick-tiddler-jump ul {
> list-style-type: none;
> margin: 0;
> padding: 0;
> }
>
> div.sib-quick-tiddler-jump ul li {
> display: inline-block;
> }
>
> .sib-quick-tiddler-jump ul li div:after {
> padding-left: 5px;
> content: "·";
> padding-right: 5px;
> }
>
> /* not last-child because there's a dropzone after it */
> .sib-quick-tiddler-jump ul li:nth-last-child(2) div:after {
> content: "";
> }
> 
>

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

[tw5] Re: Linking to Field Values

[Merry Machiavelli]

Thank you so much @Soren Bjornstad, that works perfectly! I think I tried 
something close to that at one point, I just messed up the syntax!

@iamdar my use case is that I want to be able to mass-produce 
wikipedia-style bios for individuals, where the the same basic info comes 
up in multiple parts of the 'article'/tiddler. 

For example, in the opening line, it might say "John Smith was born in 
MadeupLand", the side bar might also mention he was born in MadeupLand. If 
I link both references to MadeupLand through a field i.e. using <$link 
to={{!!birthcountry}} /> then I only have to specify the country John Smith 
was born in once, in the field. If I iterate this process 100 times (using 
the same code for most of the body of the article, just customising it with 
novel information) it saves a lot of typing.

Another advantage is that it makes it easier to call groups of people who 
share a particle bit of vital information, without necessary creating a tag 
for, say, "born in 1872" (which, I could do...it just seemed clunky?). The 
main example that comes to mind is using surnames as a way to list every 
individual from a particular patrilineal lineage (assuming it's an unusual 
surname that unrelated individuals are unlikely to share within my 
group...I could also have a specific familyID field). 


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