I'm not sure how familiar you are with Node/Socket.io, so if this is a bit confusing for you, just ask me for clarification. I am also always willing to collaborate on great ideas, if you would like to build something like this and need help, I'd be happy to help via GitHub Collaboration!
On Tuesday, August 17, 2021 at 2:47:15 PM UTC-4 Finn Lancaster wrote: > Charlie, > > One way to do this (since you are using node), is to implement Socket.io > into the Wiki. Each time the edit button is pressed, tell Socket.io via > socket.emit to in turn socket.emit to each client (the first socket.emit > would contain JSON containing the name of the editor and the tiddler). With > socket.io, too, on each client instance, just add a listener for a > specific event using socket.on... , and have it display a simple message > such as "name is editing tiddler such-and-such" > > On Tuesday, August 17, 2021 at 2:18:27 PM UTC-4 [email protected] wrote: > >> Say I have a TiddlyWiki running on node.js, and two people currently >> viewing the same TiddlyWiki in their browsers. >> >> Say User 1 is editing a tiddler. I'm thinking it would be cool if User >> 2 could know that User 1 is editing the tiddler (or that anybody is editing >> the tiddler.) >> >> And/or, it would be cool if User 2 can get a notification that a >> particular tiddler has changed (because of User 1's editing), and that User >> 2 should refresh the browser to get that change if he/she wants it. >> >> Something like that. >> >> I'm not convinced it is something I can do, but I'm kind of interested in >> trying IF it isn't something that's already been done. >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki/e3f597d0-5513-47ad-af32-8ffcbcb64687n%40googlegroups.com.
