Jeremy,

To make the browser to pick up changes from the server then you can trigger 
> polling with the tm-server-refresh message. In my own experiments I often 
> just change the default polling interval from 60s down to 3-5s 
> (via $:/config/SyncPollingInterval).
>
 
I'm afraid something is wrong: I created a new wiki ("tiddlywiki --init 
server"), made a tiddler, changed the text on the file system and issued 
the $tw.rootWidget.dispatchEvent({type: "tm-server-refresh"}) command in 
the browser console, but the tiddler has not been updated.

I also set the configuration value as you wrote it, restarted the Node 
server, and saw in the console that it searches for changes at specified 
intervals ("syncer-browser-tiddlyweb: retrieving skinny tiddler list"), but 
the tiddler did not take over the file system changes made.

Called $tw.syncer.syncFromServer() directly, same results.

The only solution that really updated it is the 
$tw.syncer.enqueueSyncTask({type: 
"load", title: "New Tiddler"}) command issued in the browser.

$ tiddlywiki --version
5.1.20
$ node --version
v8.10.0

Is it possible that Node 10 is needed for proper operation?

You may also be interested in this pending PR which attempts to address 
> some of these issues by introducing a new framework for invoking external 
> tasks on the server:
>
> https://github.com/Jermolene/TiddlyWiki5/pull/3461
>

It looks promising, but I'm not digging into it yet if I'm so close to the 
goal. In fact, maybe this may be closer to my needs if I really understand 
what it is: https://github.com/Jermolene/TiddlyWiki5/pull/4123 

PS.: $:/config/SyncPollingInterval could be documented at 
https://tiddlywiki.com/#Hidden%20Settings if you agree.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/0cd9d225-d507-4b24-abdd-98db0c0e9e4c%40googlegroups.com.

Reply via email to