ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Duffy <char...@dyfis.net>
Subject Proposal: Make Xooki spoof TiddlyWiki to use TiddlyFox plugin?
Date Mon, 20 Jan 2014 16:23:34 GMT
Howdy, all --

The release process for Ivy includes using Xooki to edit the documentation
before publication.

Unfortunately, the code Xooki uses for saving updated files, borrowed from
an early TiddlyWiki release, is no longer supported on modern FireFox or
Chrome -- and while HTML5 has its own filesystem API, that refers to a
sandbox cut off from the "real" visible filesystem, so HTML5 apps can't
edit files on the filesystem directly.

Older versions of TiddlyWiki use a Java plugin for filesystem access;
however, this isn't actively maintained, and when testing code that uses it
for saving from Xooki, I get a notice that future security changes are
going to cause breakage.

The way modern versions of TiddlyWiki are able to edit filesystem contents
consists of using the TiddlyFox plugin. The mechanism used by this plugin
to detect when it's being used to edit a TiddlyWiki document is
straightforward to duplicate -- basically, one need only identify oneself
as a TiddlyWiki in a tag in the header, and the user will be prompted to
allow write access should the plugin be correctly installed.

Any yeas/nays/alternative approaches? In preparing the Ivy 2.4.0-rc1
branch, I ended up editing HTML by hand -- but if we're going to be doing
that on an ongoing basis, we should update the process documentation to no
longer point at tools which aren't still supported.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message