>> ...
>> this structure also sheds light on tiddlywiki not responding naturaly to
>> multi user updates, though fine with multiuser read only.
>
> That's not 100% true. ... It only doesn't react on multi user changes,
> because there is no code at the moment, that triggers the "change" event.
On Sunday, March 11, 2018 at 4:52:38 AM UTC+1, TonyM wrote:
...
> this structure also sheds light on tiddlywiki not responding naturaly to
> multi user updates, though fine with multiuser read only.
>
That's not 100% true. ... It only doesn't react on multi user changes,
because there is no
Joe,
Here is something I posted previously, that may help Old Dogs grasp
TiddlyWiki. I came from a procedural language background and I was beating
my head against the wall a few times grasping how tiddlywiki works.
A conceptual outline. What follows is part of draft work in progress
If you
On Monday, March 5, 2018 at 9:05:37 PM UTC+1, joearms wrote:
>
> As you say there are actually two tidders
> XXX and Draft of 'XXX' (and two files on disk)
>
Yes. ... Jeremy wanted to save the "Draft" state. So even nodejs server
version saves those changes immediately. .. This is ok for a
On Monday, 5 March 2018 11:26:53 UTC+1, PMario wrote:
>
> Hi Joe,
>
> That's intentional. The "Draft of" tiddler is a "clone" of the tiddler you
> want to edit.
> Using the draf to edit a tiddler is the only way to implement a "canceling
> system", which reverts back to the original.
>
>
Hi Joe,
That's intentional. The "Draft of" tiddler is a "clone" of the tiddler you
want to edit.
Using the draf to edit a tiddler is the only way to implement a "canceling
system", which reverts back to the original.
If you use the toolbar: "cancel-button", the draft will be deleted, without
