In Relation to the checkout Process I wonder if there is a way to obtain a unique session id for a browser session within tiddlywiki, the reason is I would like to be able to tell if a user opens the same single file wiki or hosted server wiki in another browser or tab, simply to refuse saving, ie disallow the dirty flag, for the same user in a different session to that checked out. It can I check out using a given user name and session ID, such should the same user try and checkout in another reason, it will find it is checked out to that user, but not give the new session save rights that could overwrite changes.
Perhaps Tiddlywiki can generate this session ID and save it in the browser, subsequent generation would be different. And not allow save of the apparently checked out document. Serial Editing tools for single file wikis are my dream to support collaboration. Security is not so important when the possible users are friends and colleagues, but a layer could be added later Regards Tony. On Monday, June 22, 2020 at 11:57:43 AM UTC+10, TonyM wrote: > > Saq, > > That is exactly what I want and is "almost" perfect. Whilst it would be > nice that it were possible to set internally/programaticaly in the wiki, > such as when relying on local storage, as a bookmarklet it is of great > value to the designer. > > Unfortunately I do not know how to create the bookmarklet but have tried.. > > If someone can create a simple widget or I expect, action/action message, > to *set OR clear* the dirty status as desired It could be used > programaticaly according to different conditions. > > I May use it in a check in and out process I am building. eg; If not > checked out, change save filter (to nothing) and clear dirty status, so no > save will take place (but local storage will). If someone is checking in > with no changes I can change the save filter (already would be) and force a > save to leave the tab. > > Regards > Tony > > > On Monday, June 22, 2020 at 6:24:46 AM UTC+10, Saq Imtiaz wrote: >> >> Not sure I fully understand the problem despite re-reading the OP a few >> times, but I don't think you can reset the dirty status from wikitext. >> >> The following run from the dev console or via a bookmarklet will reset >> the dirty status: >> >> $tw.saverHandler.numChanges = 0; >> $tw.saverHandler.updateDirtyStatus(); >> >> >> >> On Saturday, June 20, 2020 at 5:24:00 AM UTC+2, TonyM wrote: >>> >>> Bump, >>> >>> This still needs A resolution please. >>> >>> Tony >>> >>> On Friday, June 19, 2020 at 1:55:48 PM UTC+10, TonyM wrote: >>>> >>>> Mario, >>>> >>>> Good tip if I know I can ignore all changes in the window, but I would >>>> like it to ignore the changes in wikis I set to do so. I want the >>>> protection but I want to choose when I don't, on a per wiki basis. >>>> Consciously selected exceptions hence the OT >>>> >>>> Regards >>>> Tony >>>> >>>> On Thursday, June 18, 2020 at 4:51:39 PM UTC+10, PMario wrote: >>>>> >>>>> Hi, >>>>> >>>>> If this happens to me, I just click the close browser button a second >>>>> time. It ignores the dialogs and closes the window. >>>>> I'm using FF >>>>> >>>>> -mario >>>>> >>>> -- 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/ede402f6-93e2-42ff-8230-763559b082f3o%40googlegroups.com.
