[TW5] Announcing the release of TiddlyWiki v5.1.15

[Jeremy Ruston]

I’m delighted to announce the belated release of TiddlyWiki version 5.1.15:

https://tiddlywiki.com/

Remember to keep careful backups before upgrading existing 5.x.x wikis at:

https://tiddlywiki.com/upgrade.html

There are quite a few improvements and new features in this version. Highlights include:

* A new plugin for use with TiddlyDesktop that allows you to import files as external attachments: rather than importing the entire file, a tiddler is created with a _canonical_uri field that points to the file. There is flexible control over whether absolute or relative links are created. Hopefully this is the start of features that take advantage of capabilities of TiddlyDesktop that we could never have implemented with TiddlyFox

* Updated support for Beaker browser. This is a good time to check it out again now that there is a Windows package available. Right now, it seems to be the closest thing to the Firefox+TiddlyFox user experience

* For Node.js, the addition of new “render” and “save” commands that combine the functionality of rendertiddler/rendertiddlers and savetiddler/savetiddlers respectively with more flexible handling of filenames

* Many bug fixes, including the notorious problem with the “new journal” button

* Many minor tweaks and improvements

Full details of all the changes can be found in the release note:

http://tiddlywiki.com/#Releases

My sincere thanks to the many people who have contributed to this substantial release.

As usual, feedback and questions are welcome,

Best wishes

Jeremy

[Tristan Kohl]

Thank you Jeremy for your continued and awesome work.
Kudos to all contributors :)

[PMario]

On Wednesday, November 15, 2017 at 4:40:41 PM UTC+1, Jeremy Ruston wrote:

* Updated support for Beaker browser. This is a good time to check it out again now that there is a Windows package available. Right now, it seems to be the closest thing to the Firefox+TiddlyFox user experience

The beaker browser is a very fast moving target. ... I really like the concept of the distributed data storage. See: https://datproject.org/

Beaker browser 0.7.x is nice and it allows the TW beakerSaver to directly create a new file on the host filesystem. ... This area is called "staging area" .... BUT ....

Version 0.8.x will completely remove this feature without a replacement... yet!  So the existing saver will only create a TW file in a "hidden" DAT filesystem.

The advantage still is the distributed behaviour of the filesystem, .. but it will considerably slow down our file:///local userexperience. At the moment we won't win much, in terms of complexity.

I think the concept is still great, to experiment with, but beaker is still a --web first-- experience. Even if some stuff is stored in a locally hidden filesystem. ... End of rumbling ;)

have fun!

mario

[Mark S.]

Once it's forked from Chrome, can you trust it for daily browsing?  i.e. Will it no longer have the security patches that Chrome has? A browser that is good for TW but isn't safe for daily use is no different from using TW with an older obsolete browser ... which we can already do.

Just wondering --

Mark

[Jeremy Ruston]

Hi Mark

Once it's forked from Chrome, can you trust it for daily browsing?  i.e. Will it no longer have the security patches that Chrome has? A browser that is good for TW but isn't safe for daily use is no different from using TW with an older obsolete browser ... which we can already do.

Beaker isn't forked from Chrome; it embeds the same underlying browser engine that is also used by Google Chrome. It's called Blink, and it's open source; it's also embedded by TiddlyDesktop via nwjs.

As I noted in the "Firefox Apocalypse” tiddler, this is how browser innovation happens now that browser extensions are curtailed: open source application projects embedding and customising open source browser engines.

As Mario notes, Beaker itself is changing rapidly, and some of those changes may require changes to the TiddlyWiki saver for Beaker. I'd be pretty confident that we can track those changes; from the perspective of the Beaker project, TiddlyWiki isn't so very different from other CMS-like systems on their platform.

Best wishes

Jeremy.

Just wondering --

Mark

On Wednesday, November 15, 2017 at 9:29:40 AM UTC-8, PMario wrote:

On Wednesday, November 15, 2017 at 4:40:41 PM UTC+1, Jeremy Ruston wrote:

* Updated support for Beaker browser. This is a good time to check it out again now that there is a Windows package available. Right now, it seems to be the closest thing to the Firefox+TiddlyFox user experience

The beaker browser is a very fast moving target. ... I really like the concept of the distributed data storage. See: https://datproject.org/

Beaker browser 0.7.x is nice and it allows the TW beakerSaver to directly create a new file on the host filesystem. ... This area is called "staging area" .... BUT ....

Version 0.8.x will completely remove this feature without a replacement... yet!  So the existing saver will only create a TW file in a "hidden" DAT filesystem.

The advantage still is the distributed behaviour of the filesystem, .. but it will considerably slow down our file:///local userexperience. At the moment we won't win much, in terms of complexity.

I think the concept is still great, to experiment with, but beaker is still a --web first-- experience. Even if some stuff is stored in a locally hidden filesystem. ... End of rumbling ;)

have fun!

mario

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/bb0f1441-6efa-4f21-b2bc-959987f3ad71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Eneko Gotzon]

On Wed, Nov 15, 2017 at 6:29 PM, Tristan Kohl <kohlt...@gmail.com> wrote:

Thank you Jeremy…

​

Kudos to all contributors :)

​+ 1 :)​

--

Eneko Gotzon Ares

Izan, egon, egin

Donostia – EH, Baskonia, NA Oso

Tf 

(+34) 943 273 431 - (+34) 639 626 858

——————————————————

Mezu hau eta berari atxikitako agiri oro isilpeko dira eta soilik hartzaileari zuzentzen zaizkie. Mezu hau hutsegitez jasoz gero berau ezabatzea eskatzen da eta igorleari horren berri ematea eskertuko litzake. Baimen agerikorik gabe debekatuta dago mezu honen edota bere edukinen edozein erabilera edo hedatzea, bai osoki zein zatiz. 

Mezu elektronikoak andea daitezke; mezu hau andeaturik, aldaturik edota aizun balego Eneko Gotzon Aresek edota bere ordezkariek uko egiten diote edonolako ardurei.