Hi Tony, This is a great vision. Here is purely philosophical reason behind hesitation. My vision for timimi is that once installed, user should not have to install anything further. If I am doing my job right, user should almost forget that timimi exists. This I believe, is the greatest success of a piece of software. To ensure this, timimi should depend only on things that are part of core tiddlywiki.
So there are 2 ways ahead here. First is to create a entirely different browser plugin for this. Such a scenario will have atleast 3 moving parts - 1. Browser plugin 2. Native host/backend 3. Additional tiddlywiki plugin/saver to generate a new version of save object that corresponds to these browser plugin. Now as I said, this is rather unpleasant because user will have to install the plugin to each and every wiki he uses. Sure, an argument can be made here that user need to install it only if they require the particular feature. Still, unpleasant. Second is my favorite. Mostly because I have a few more ideas regarding this direction Jeremy has hinted an update to attributes generated by tiddlyfox.js <https://github.com/Jermolene/TiddlyWiki5/pull/4526#issuecomment-606562156>. If we are adding attributes anyway - why not add a couple more. Currently save object sends just the data and path to tiddlyfox. Imagine if there are the following attributes too. 1. backup-path 2. lock-status 3. unique-id for the session Now let me expand my thinking here. 1. You have a TW5 file open. You have button that generates a "lock" 2. The "lock" button creates a unique ID for the session which gets associated with the the path of the file. 3. Now when save is triggered, this unique ID and lock command is send along with other data points in save object 4. From then onward, whatever-does-the-actual-saving, will *save to that particular path ONLY if save command is accompanied by the particular unique id*. 5. Finally user can send an unlock command to remove this restriction. 6. If user opens it another browser - user could be notified saying that this file is locked and asking him for explicit permission to unlock it. Such a mechanism could be utilised by any savers - tiddlydesktop, timimi - even Bob I guess. Oh, and the backup-path attribute so that you can have individualised backup paths for each tiddlywiki file. The backup path you set in timimi settings will be default, but if a tiddlywiki file has a backup-path specified, it will override the dafault and save it that location. by the way I love the doco at https://ibnishak.github.io/Timimi/ > Thank you!! You should look at it from a mobile phone. That is my idea of a mobile theme for TW5. It has a lot of moving parts right now. So not recommended for public use. Sincerely, Riz -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/73eb1acf-e587-40f1-b441-2eb1869f3b4a%40googlegroups.com.
