TiddlyWiki 2.10.1 and other updates

[Yakov]

Hello everyone,

today I'm happy to announce the release 2.10.1 is out there. Here are the main changes:

• Behavior improvements:
  • Default option values are no longer stored in cookies;
  • Permalink buttons now support context menus (to copy url/open in a new tab/...).
    • ..in fact, for now they only have the correct url when the current address hash a # already (otherwise they have no #, too); the fix will go to the next release
      
• UI updates (see the visual summary):
  • GettingStarted shadow is now clearer and more instructive, has a link to quickly find custom savers;
    
  • Upgrade wizard now looks better (primarily on mobile devices, when using with a proper viewport tag):
    • Symmetrical margin for backstage panels (avoid viewport overflow);
    • Shorter and clearer title and subtitle;
    • The upgrade url is now shown without the https:// bit;
    • Borders of wizard buttons are now symmetric (and look better in the dark mode);
  • Tagging, tags blocks now use thick borders instead of solid background color;
  • Less visible updates are: colors of inputs are now based on ColorPalette (Background, Foreground), thanks to Pengju Yan; prevented multiword tab labels from getting multiline in some cases.
• Fixes: Native backups saving broken in 2.10.0 works again.
• Hackability (see details in the release):
  • defining default option values is available for plugins;
  • some fine-grained updates to saving methods.
    
• Infrastructure:
  • jQuery is now a dependency defined by package.json (forced updating 1.8.3 → 1.9.1; a dedicated upgrading, presumably to 3.x, will be done later);
  • reduced some duplicated autotests.
    
• Lingo updates (for translations) can be found here.
• Some docs updates (see details in the release).

I'd like to thank Pengju Yan and Simon Baird for contributions that made it to this release.

Here's a brief reminder about the upgrading process: since 2.10.0, data safety and instructions clarity are included into TW itself, but when upgrading from below 2.10.0, please refer to HowToUpgrade (create a backup, use the SimplifiedUpgradingPlugin or alternatives).

***

MainTiddlyServer is also updated, see the 1.7.5 release.

The first advantage of async saving is taken in the new native saver: ContinousSavingPlugin (haha, looks like I've copy-pasted the typo in the plugin name everywhere since the beginning, I'll probably fix that, should be "ContinuousSavingPlugin", but that may break some links). This new saver will probably get into TW core at some point.

As always, your feedback is welcome.

Best regards,

Yakov.

[Reto]

Good news!

I am on 2.10.0. Is SimplifiedUpgradingPlugin still needed?

Cheers

Reto

[Yakov]

Hi Reto,

the answer depends on what saver you are using. The general answer is this:

1. using SimplifiedUpgradingPlugin won't hurt anyway
   • on Tiddlyhost, upgrading there doesn't seem to work even with SUP 0.7.0 (haven't investigated the reasons yet), so seemingly the only way is to download, upgrade, and upload back (I've provided a plugin for downloading/uploading here + a patch for Firefox);
2. if you try upgrading without it, the core upgrading will either succeed or (avoid data loss and) will suggest alternatives (basically, will point to HowToUpgrade). (internally, it works this way: TW checks if it can load the backup that was supposedly saved during the previous upgrading step, and proceeds if it can, because that guarantees the success; if it can't, it shows the fallback instructions)
   

For example, SUP is still needed for:

• Timimi (will be needed until the core handles its "optimistic reporting before saving is finished" behavior, I've already prepared a proof-of-concept code for that, but it's not finished yet),
• MTS (it won't at some point),
• resumably, for mobile apps like Tiddloid and for "bare extensions" like savetiddlers or file-backups;

and not needed for

• TiddlyFox (in FF, security.fileuri.strict_origin_policy: false setting may be needed),
• I think it's also not needed for IE saving , Jon's tiddly-node-saver, and for nw.js savers (TiddlyDesktop, Okido's nwTWcSaver).

but I can be wrong about the last bullet in each list.

Best regards,

Yakov.

среда, 7 февраля 2024 г. в 14:44:32 UTC+3, Reto:

[Reto]

Ok, then I leave SUP installed - I am using FF with Timimi.

Thanks

Reto

[Jeremy Ruston]

Hi Yakov,

I'd like to offer my congratulations to you and the other contributors on another milestone release. You have accomplished a lot, keeping TiddlyWiki Classic thriving with meaningful enhancements and fixes.

Although my attention is now much more on TiddlyWiki 5, it gives me great personal satisfaction that TiddlyWiki Classic is continuing, and that others are prepared to give their time and attention to it. I can't think of a better tribute to all the people who enthusiastically adopted TiddlyWiki in its first wave of GTD-driven popularity in 2005/6.

Your hard work is also deeply significant in that it fulfils TiddlyWiki's promise of practicality for perpetuity. People today choosing any variety of TiddlyWiki can see for themselves the evidence that it is a tool that will grow and improve over their lifetime.

I hope you're able to continue, and I will be looking forward to see what 2.20 brings.

Best wishes

Jeremy

[Jeremy Ruston]

I made a brief post on talk.tiddlywiki.org about this latest TiddlyWiki Classic update:

https://talk.tiddlywiki.org/t/congratulations-on-another-tiddlywiki-classic-release/9087

[Reto]

I just tried to upgrade and got this message:

Nevertheless I can find the backup *.pre.core.upgrade.*.

I am using Firefox and Timimi. SimplifiedUpgradingPlugin is installed and activated.

Do I need to upgrade by import?

Cheers

Reto

[Yakov]

Hi Jeremy, thanks for the support! I'll probably join the thread you've started later; thanks also for the fix of TW5 for building TWC.

Speaking of the building process, I've noticed that TW5 doesn't set the markup blocks (so currently it requires an additional edit) as well as the title, do you think it is reasonable to try to implement it, too, or the only reasonable way to fix the workflow is to use Puppeteer with headless browser or something alike? May be we can continue this discussion here. At some point, I'll probably also suggest changes to sort fields in a standard way to avoid unwanted diffs.

Reto, do you have SUP 0.7.0? Have you tried increasing the "wait saving" interval? The fact that you can see the *.pre.core.upgrade.* file but also get the error means that the backup is saved after the load check is done (such thing happens on attempt to upgrade with Timimi and without SUP, which resulted in an empty TW, that's why I've introduced the safety check), so increasing the interval should help for bigger TWs. At least I've just tried upgrading one of my TWs from 2.10.0 to 2.10.1 with Timimi and SUP, and it went fine.

Best regards,

Yakov.

пятница, 9 февраля 2024 г. в 13:04:55 UTC+3, Reto:

[Reto]

Actually, I still used SUP 0.5.0 ... was not aware that there is a new version. After upgrading to 0.7.0 it worked like a charm. Thanks!

One issue noticed:

The title background goes "through" the tag block. This was also like this before, but I did not notice because the tag block had a darker background than the title.

Cheers

Reto

[Yakov]

Yeah, I've noticed that, too, will fix in the next version; as a quick workaround, you can add this to your StyleSheet:

.tagging, .tagged { background: [[ColorPalette::Background]]; }

> I still used SUP 0.5.0 ... was not aware that there is a new version

By the way, do you have EEP (without chkSkipExtensionsUpdatesCheckOnStartup enabled)? Did it fail to find the update?

суббота, 10 февраля 2024 г. в 14:34:39 UTC+3, Reto:

[Jeremy Ruston]

Thank you @Yakov

I do think that using Puppeteer or Playwright is likely to be the easiest way to fix the markup blocks and title. You may have seen that TW5 is now using Playwright within GitHub Actions to run tests. You may be able to adapt the code at https://github.com/Jermolene/TiddlyWiki5/blob/master/.github/workflows/ci.yml

I've also used Playwright in another project for reading EPUBs. We load the HTML from the EPUB into a Playwright instance, and then extract the text. See https://github.com/TWPUB/TWPUB-Tools/blob/main/epub2twpub/text-extractor.js 

[Reto]

By the way, do you have EEP (without chkSkipExtensionsUpdatesCheckOnStartup enabled)? Did it fail to find the update?

Yes, EEP is installed and active. chkSkipExtensionsUpdatesCheckOnStartup is not set. I clicked on the "Check" button behind SUP but it did not find the new version.

The source URL of 0.5.0 pointed to here > http://yakovlitvin.pro/TW/pre-releases/SimplifiedUpgradingPlugin.txt

[Yakov]

Ah, I see, this may be at least due to EEP doesn't handle redirects for now, and at some point I've restored https on my site (with a http → https redirect). I'm still a little surprised, though, because that happened much later than I've updated the pre-release version of SUP to 0.5.2 with a new Source pointing to Github. I think I'll add the support of redirects at some point, but probably not very soon, so if you have any pre-release versions of my plugins, you may want to check if they were updated, too.

воскресенье, 11 февраля 2024 г. в 16:07:00 UTC+3, Reto: