[tw] Re: [TW5] A working prototype multi-user wiki

Tony, That wouldn't really be part of the gatekeeper part. All the gatekeeper part does is act like the file system adaptors that tiddlywiki normally uses, it just works faster and lets you have multiple connected instances of the same wiki. You can define a set of tiddlers that are not

[tw] Re: [TW5] A working prototype multi-user wiki

.Jed, I have not yet experimented with this, even advanced applications of node JS wikis, there is not enough in a lifetime to do everything that's possible with TiddlyWiki. This solution however is very promising. I will get into it further. I think all the activity around saving has

[tw] Re: [TW5] A working prototype multi-user wiki

WOO!! It works. So try it out if you know how to install npm modules. Follow the instructions in the readme in the repo here https://github.com/OokTech/TW5-Gatekeeper and

[tw] Re: [TW5] A working prototype multi-user wiki

Well, I never figured out how to make a proper sync adapter, but there are almost enough hooks to just use those to trigger sending the web socket messages without using a normal sync adapter. It works but I had to make some pretty hacky things to make everything fit the way it should and I had

[tw] Re: [TW5] A working prototype multi-user wiki

Ok, I am going to try this again. As I said before, I have this working, the only component that I am having trouble with is the sync adapter. Is there someone who has time to help and isn't just going to describe the structure of the tiddlywiki for 5 posts before concluding that I may need to

[tw] Re: [TW5] A working prototype multi-user wiki

Yes, a new sync adapter is exactly what I am trying to make. That is why when I said I was having trouble I said I was having trouble getting a new sync adapter to work. Because everything else works. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki"

Re: [tw] Re: [TW5] A working prototype multi-user wiki

> > the part that I am lacking right now is whatever gets the save hook from > the wiki so that I can make it send the message to save the files on the > file system. Listen for the change event on the client is what I think you want. In the gatekeeper, why don't you just save the updated

[tw] Re: [TW5] A working prototype multi-user wiki

Yes, I understand the structure of the program. I have it working and I can do what you are describing without trouble. That isn't the problem. I will try and figure this out since I am apparently not describing it well. -- You received this message because you are subscribed to the Google

Re: [tw] Re: [TW5] A working prototype multi-user wiki

I guess you understand that the client and server are two separate instances of TiddlyWiki? When the client clicks save changes, the tiddler is saved to the wiki store on the client and a change event is queued. The sync adapter gets called with the changes allowing it to save them to where it

[tw] Re: [TW5] A working prototype multi-user wiki

Watching for changes is relatively simple and I have that working, I have just been watching the file system for changes. I need to set everything up to have it watch all the appropriate folders and let you modify that while the wiki is running, but that shouldn't be difficult. The only part

[tw] Re: [TW5] A working prototype multi-user wiki

I have the message handlers and the connection, the part that I am lacking right now is whatever gets the save hook from the wiki so that I can make it send the message to save the files on the file system. I can manually send things to be saved on the file system and when I do that it changes

Re: [tw] Re: [TW5] A working prototype multi-user wiki

I do, but I don't feel like replying. :) Because I can see how big of a project it will be. The server command is given a wiki object as an option. That wiki object should have somewhere you can listen for changes. I forget where but I know its there. From there it should be quite simple. Set up

[tw] Re: [TW5] A working prototype multi-user wiki

Well, I was trying globally (with -g install npm option) without success. Just retry locally on a home folder on my Fedora, and it's seems to work well. It take about 20 seconds to see push change if I edit remotely on my phone a tiddler. Hope you will be able to work on it to reduce this time

[tw] Re: [TW5] A working prototype multi-user wiki

I have been having trouble making the new syncadapter using websockets, so if there is anyone who can help with that I would appreciate it. Sylvain, Most of the problems I have run into setting it up have been caused by not installing the npm modules correctly. If you have any specific

[tw] Re: [TW5] A working prototype multi-user wiki

Bonjour Jed, That's sound promising ! I've try it today but not succeed at the moment. I'll try later and have a closer look at your howto. (in fact I'm not a node.js version export, just beginner). Sylvain -- You received this message because you are subscribed to the Google Groups

[tw] Re: [TW5] A working prototype multi-user wiki

This is only for node. the closest equivalent for a single file wiki is twederation which can be used to make multi-user wikis but doesn't have the live updates that this does. You can have the websockets plugin in a single file wiki but you will still need a server to connect it to so it

[tw] Re: [TW5] A working prototype multi-user wiki

This is interesting. I don't run node. Any chance of this making it into the Webdav saver? I doubt it since TW uses a single file with DAV. On Wednesday, November 1, 2017 at 9:41:40 AM UTC-4, Jed Carty wrote: > > BIG SCARY DISCLAIMER: I am the only one who has tested this so far, and > only on

[tw] Re: [TW5] A working prototype multi-user wiki

Wow!! This is great! Thanks for setting this up and I look forward to seeing it develop! On Wednesday, November 1, 2017 at 8:41:40 AM UTC-5, Jed Carty wrote: > > BIG SCARY DISCLAIMER: I am the only one who has tested this so far, and > only on linux mint. This may be full of bugs and could