Folks,
I am working on a solution that tests a wiki opened in a browser, which browser is in use, basically I will compare the info tiddler $:/info/browser/name with a configuration tiddler $:/config/browser/home
The reason for this is if you open the same single file tiddlywiki in a different browser you may overwrite changes in a different browser.
- I have a range of methods to avoid this issue within a browser, but not across browsers.
By being able to set a “Home browser” I can test if the wiki is in the home browser just proceed, if it is not, I can warn the user and disable saving. But perhaps you have other actions you would like?
It seems to me this illustrates a code pattern we may want to use for more than one reason, so it occurs to me a generic solution allowing this would make sense. As a result I have started this discussion to seek your views and ideas.
- Test the username for read or edit settings
- Test if the document is available for checkout and editing
- Make a mobile device view read only, or for reference and lookup?
Some Questions to consider
- What is the best way to communicate when the requirement is not met
- Alert Message, popup, modal etc…
- What alternatives are available to us over setting the wiki to read only?
- Local storage can save changes, but not save to file so how could this be used to avoid loss?