java is dying

[@atomi]

This https://www.chromium.org/developers/npapi-deprecation/ appears to kill the java plugin to run tiddlywiki in browser.

For now you can re-enable it in about://flags but that options seems to be going away in September as well.

[Eric Shulman]

On Tuesday, April 14, 2015 at 4:15:33 PM UTC-7, @atomi wrote:

This https://www.chromium.org/developers/npapi-deprecation/ appears to kill the java plugin to run tiddlywiki in browser.

For now you can re-enable it in about://flags but that options seems to be going away in September as well.

Just to be clear... neither TiddlyWiki nor TiddlyWiki Classic relies upon *java* to run in the browser.  All TiddlyWiki code is written in *javascript*, which is natively supported by nearly all browsers, without any plugins needed.

The only impact of this phase-out of NPAPI support will be for people using TiddlyWiki Classic with the mostly-obsolete TiddlySaver.jar applet to enable local file I/O. However, without TiddlySaver.jar, TiddlyWiki Classic (v2.8.1+) will still be able to save locally, using the fallback "download saver" functionality.

-e

 

[@atomi]

Yeah, as far as I know there is no other way to enable saving tiddlys in browser (and without having to download the whole file) without TiddlySaver.jar

[Eric Shulman]

On Tuesday, April 14, 2015 at 8:17:13 PM UTC-7, @atomi wrote:

Yeah, as far as I know there is no other way to enable saving tiddlys in browser (and without having to download the whole file) without TiddlySaver.jar

* "modern" TiddlyWiki (v5.0.0+) does NOT use Java in any way, so there is simply no impact on current usage.

* TiddlyWiki Classic (v2.8.1+) does not *need* TiddlySaver.jar to save your changes locally since it also can use the fallback "download saver" that works without any Java applet support.  Regardless of how the local file is saved (TiddlySaver.jar or the fallback "download saver"), there is really no difference in the end result... TiddlyWiki Classic always saves the *whole file* each time.

What I'm trying to make clear is that the demise of *Java* plugin support in the Chromium browser will have virtually no impact whatsoever on TiddlyWiki users.

-e

[@atomi]

I use TiddlyWiki classic with the TiddlySaver.jar daily, because I can save without having to deal with additional dialogues.

This post was just a heads up for those people that do use TiddlySaver.jar. If you don't use it don't worry about it.

[Danielo Rodríguez]

This question is probably stupid but, does TWC don't work with tiddlyfox?

[Eric Shulman]

On Wednesday, April 15, 2015 at 10:25:26 AM UTC-7, Danielo Rodríguez wrote:

This question is probably stupid but, does TWC don't work with tiddlyfox?

TiddlyWiki Classic works quite well in FireFox with TiddlyFox.

However, the OP was about the end of Java support in Chromium-based browsers, so the discussion has been focused on the impact that Java's demise would have on those users.

-e

[James Perrett]

I am using Tiddlysaver.jar on a standalone pc with an old chrome and an old Date/Time on the bios.

This is annoying as the date on tiddlers is incorrect. This is a stop gap measure until some-one resigns the tiddlysaver.jar. This is a waste of a pc but at least works well with 2.8.1 will re-evaluate this when 2.9 is out. Are you still working on 2.9? 

cheers 

[Jed Carty]

Since tiddlywiki 5 was released I doubt that there will be any significant development on the old version. I don't think there are any plans to update tiddlysaver or find ways around the problems with it because it isn't relevant in tiddlywiki 5.