Hola > Hello Felix, > > How do you force the save of the wiki? I wait till the dialog closes and issue a save wiki event right after that.
> Are all the users forced to use tiddlyfox? Yes, good spot. This was the deal at the office to ensure it is always saved into the file without having to ask the users. > How do you notify users that has the wiki opened already that a new user is > editing? I do not! When a user X is in read mode, he/she does not receive any updates or doesn't know that another user Y started to edit the wiki. But when X clicks the "switch to edit mode" button (I created for this mechanism), the wiki reloads and the user sees that Y is already editing. > You have to reload the file to notice any change. Correct > Do you have any function (SetTimeout) scheduled for this? No. in our case, the information does not need to be highly up to date, but when the user hits the refresh button, he/she can load the new state manually. > How do you manage the different user names? Do you change the tiddler that > determines the user or do you have your own mechanism? The user that "logs in" will be set as the current user ($:/status/UserName). A list of existing users is maintained (tiddlers tagged with "user") and are displayed during login. --- When it all works fine (which it seems to do), I'll report back. -Felix -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/BLU437-SMTP72E0E6D82C83AFA6A3F350CECA0%40phx.gbl. For more options, visit https://groups.google.com/d/optout.
