Folks, I may have discovered a path to a universal install.
I am discovering a lot of power with links to files, and executables and batches. With some recently developed methods to customize and export scripts to the local computer. Further a custom protocol as an alternative to file:// can actually pass parameters to the Operating system. In time I hope to pass larger payloads at a click of a button or link. The annoying thing is this only works on top of TiddlyDesktop with its local rights as a fully fledged application. Installing and managing solutions that Mark has developed would be so easy, but users will have had to of installed tiddlydesktop first which misses the point. However this has made me realise what if we provided a custom browser, you install (Like TiddlyDesktop) but one designed to open .tw files (TiddlyWiki.html in disguise) (Even a specific tiddlywiki) and this browser can install on any OS, people could get a "management wiki" with a single install script for each alternative build or solution. In some ways this solves the platform issues, if at that point we present ways to obtain all the other possible methods with install scripts it would open it up to multiple setups. So to use tiddlwiki on any computer install the "tiddlywiki manager" app. A Custom browser that loads a helper wiki. This can be used to open tiddlywikis, will automatically open .tw files but also has oneclick installs of The powershell script, TiddlyDesktop, TiddlySever, Node, Bob, Timimi and even support installing tw-receiver to a local server (WebDav, AMPPS/Apache etc...). Why so powerful?, because we are working behind the "firewall" called a browser. Perhaps just building this resource into a build of TiddlyDesktop and its backstage, would be a quick remedy. Even if users do not continue to use tiddleyDesktop, it will manage the other options. Regards Tony On Monday, May 20, 2019 at 11:05:35 PM UTC+10, @TiddlyTweeter wrote: > > At the moment, on modern browsers, saving TW without any custom saver, > means the save ends up in "Downloads". > > We have no tool to "auto resurrect" and copy back that save for those > kinds of saves. Copying back has to be manual and can get complicated in a > forest of downloads. > > The more I think about this the more odd it seems. > > I mean, with an "AUTO-RESTORE" from saves in Download to a wiki directory > ANY browser could be used and with ANY version of TW. We would not be > dependent on specific solutions. > > Any thoughts on how to do this? And its probable value? > > I know Mark S. has thought about it. > > Best wishes > Josiah > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0a4e5286-a33b-4183-bceb-a1ccb08299f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
