My apologies for the late response, Lyall - I'm still rather busy at the
moment, so I didn't get around to replying...
After a bit of looking, I am unsure as to what is fundamentally
different between your demo and my old plugin
I now realize this isn't obvious at all - mainly due to the fact that
the code has grown far beyond what was originally anticipated...
The basic difference is that my plugin operates directly on individual
tiddlers rather than the document as a whole. If I recall correctly,
your plugin's encryption occurs during serialization, when writing the
document to file. However, this is never triggered when sync'ing changes
to a server (whether manually or via the ServerSideSavingPlugin*).
are you asking for a 'Re-encrypt This' and a 'Re-Encrypt All' button
which does not 'save' but simply operates locally?
I'm not sure whether separate buttons are desirable - it seems like this
should be handled automatically, ensuring that the decrypted text is
never persisted.
This requirement was a bit silly, from my original perspective but
times change
This (even) more tiddler-centric view, with the tiddler (rather than the
document) as the basic unit, was brought about by various explorations
and experiences in recent years, including of course TiddlyWeb. It seems
to be in line with where the web is moving (again); individually
addressable chunks of atomic content.
an interesting coding style with variables being defined as functions
Indeed, it can take some time to get used to functions as first-class
objects - but it's quite a powerful concept...
-- F.
* as used by both TiddlyWeb and ccTiddly:
http://svn.tiddlywiki.org/Trunk/association/plugins/ServerSideSavingPlugin.js
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywikidev?hl=en.
