Folks, Here is a short specification that may lead to an answer,
alternatives, help and criticism welcome.
1. On opening a WIki check to see if they can see a restricted file, if
not remain in a read-only mode.
2. If the restricted file is visible user has update rights, check to
see of a lock/Checkout file exists,
1. if so advise user and email address of person who checked it out,
idealy monitor provide reload button to see if checkout status changed
2. If checked out by me allow me to edit and save
1. Save Wiki, Then use a system similar to 2.3.x to allow to end
check out
3. If not checked out to anyone provide option to check out HTML
1. Include a Tiddler containing a standalone HTML and/or using PHP that
can be presented in an iframe
2. Open the Tiddler in an Iframe. Display when checkout is needed
3. Allow User and email address to be provided and request
checkout
4. Write the lock/checkout file with my details, cause wiki reload
(or suggest), Ie return to 1
Of note is the active html/php can be made available only to those who have
authenticated and have file the right to request check in check out and
save. This will be using the hosts authentication process, other wise
anonymous can be given read only, or no access.
Regards
Tony
On Wednesday, January 23, 2019 at 11:50:01 AM UTC+11, TonyM wrote:
>
> Folks,
>
> I have raised this a number of times in a number of contexts but *NOW I'm
> Serious - We need Check in and Check Out*
>
> TWC had a method to allow serial editors and a lock file (that all can
> see). We need this as an option to TW5 as well.
>
> Why?
>
> 1. TiddlyWikis can be used as smart documents served from a file or
> network location without fear of contention and overwrite (Single File or
> Network served)
> 2. Its a "poor mans" multi-user wiki - Serial multi-user update access
> NOT Multi-user multi-access
> 3. TW-Receiver could provide read/update access to any number of users
> knowing simultaneously is not available.
> 4. The lack of such a facility is driving some of the complexity we
> face trying to simplify the saving process, if we could check in out
> documents reliably we secure the the wiki from corruption/overwrite.
> 5. It could help users protect them from themselves opening the same
> wiki from more than one tab/or browser without needing a server solution.
> 6. Perhaps TiddlyDesktop and the other servers could also honour this
> allowing free transfer between platforms.
>
> How
>
> I am confident we have the technology and avenues by which to achieve
> this, I do not believe their is a technical barrier any more. An example in
> point is some of the local save tools, we know they are writing information
> such as backups, so we have the ability to read and write a switch/lock and
> we can include an informational user name in that switch.
>
> We could provide a checked out to current user with a save and check in
> button. We could provide a NO check out user with a reload and check in
> button (if not locked)
>
> I can provide more technical possibilities if requested, but some of you I
> expect already know how to do this.
>
> Feedback please!
>
> Thanks tony
>
--
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/d1a77727-6340-4918-97d0-f53f3de23f1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
