On Thu, Mar 24, 2022 at 11:04 PM TW Tones <[email protected]> wrote: [...]
> I believe I can add a lot here but there remains a slight technical > barrier for me. > > What I want to see is to minimize user interaction including between > reloads, and when forced interaction is necessary, improve and guide the > user for minimum complexity. Here are a few techniques that may help > overcome the barriers. > > - *Copy path to clipboard*: If we want to save a tiddlywiki to an > existing location, as may be forced when reloading the wiki or browser, we > already have the full path and filename available in the browser, it just > needs to be available to the save as dialogue. > > Does this one have any technical barrier for you? Sounds like you have it figured out. Sounds like a useful approach as long as the tiddlywiki is loaded from a file url. [...] > > - *Custom Target/tab:* If we want to protect against opening the same > wiki in a tab, one trick is after the first save (knowing the full path and > filename) we can construct a html link with an appropriate target > attribute, then navigate to that (if possible closing the original tab), > thus the wiki is now running in a tab with a named target. > > What needs to know the full path and filename here? The user will know and the browser will know, but the functionality running in the web page (i.e. the tiddlywiki instance) will not know. It only has access to the filename minus the directory location. The directory location is hidden from it. The user has the information required to construct the html link you mention, but the tiddlywiki page does not. [...] > > - > - This should help given the global file:// issues > > I'm not sure what you mean here. > > - *Bookmarklet*: Perhaps extending the value of Custom Target/tab and > because there is value using it, we can consider the use of a bookmarklet > both with a target and a payload if necessary. > > What do you mean by "payload"? Could you give an example? > > - An example may be so if the user returned to the source site, > published on the internet the bookmarklette can recall you already have a > local copy and with a click. When saving from the source URL for the first > time we could prompt the user to use their saved bookmark if they want to > access their local copy, to not create a new one, or override and existing > one. > > I'm not sure how the bookmarklet would know you already have a local copy [...] -- 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/CAO5X8CzTsJzpJBRtmjR9oh8p1kTHTsXSD1nWd%3Dd%2BMbPGZcOgng%40mail.gmail.com.
