Overhead? I think it's comparable to other solutions.
You unzip to a directory. You configure a simple ini. You run a batch file. The setup by INI file is easier than the JSON configuration used in tiddlyserver or Bob. The latest versions of both of these products increased in complexity for some reason, adding levels of indenture that seem unnecessary from a user point of view. Not sure if that reflects some underlying node.js change. In one of the upcoming editions, we hope to add a listing of monitored directories. All the *.htm, *.html, and *.tw files in those directories will be automatically "restored". The problem this solves -- If you're perfectly happy with solutions that only work in Firefox and possibly Chrome, require an (usually unsigned) executable, that may break the next time FF changes its rules AGAIN, or that only work with sub-directories of the download directory, then it may not solve any problem for you. But if you want to see other browsers, not use extensions, and not use (or can't use) executables, then Polly might be a good solution for you. If you want to save copies of your changes in more than one place at once, then Polly might be a good solution for you. If you want a solution that might (some future edition) allow you to run an executable and send a copy of your TW off to a server, then Polly might be a good solution for you. More to the point, if you want a solution where the code is simple enough for you to add on your own processes, then Polly might be a good solution for you. For me, I think the Extension Apocalypse from a couple months ago rekindled my interest in this project. I had no idea that FF was re-evaluating my extensions every single day. There was total lack of transparency in the process. So one morning we get up, and all the extensions we've been depending on are gone. They never explained exactly how they could allow this to happen. The incredible amount of carelessness involved in this fiasco got me rethinking about FF. At this point, most of the native features I really care about in FF are gone -- RSS feed, extensions, tab groups. Despite the "improvements", FF continues to be a memory hog, gradually sucking up 60% of available memory. Over the past year, FF's share has dropped 1.3% and continues downhill. There are other browsers out there -- Brave, Vivaldi, Edge (two versions), IE, Palemoon, Waterfox -- so having more options is a good thing, right? Also, Powershell is allegedly coming to the Linux and Mac platforms, meaning that Polly (or some variant) might become a universal platform solution as well as universal browser solution. HTH! On Tuesday, July 23, 2019 at 6:07:46 AM UTC-7, @TiddlyTweeter wrote: > > Mat asked: >> >> ... must I manually "add" each TW that it is supposed to work for? >> > > Good query! > > *I do think the overhead of setup could be an issue.* > > On the other hand, the fact you can configure (once you "get" what it can > do) in many ways for different purposes is useful. > > If I can figure it out I'll write a settings tool to ease the process. > > TT > > > -- 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/07c1f483-2e83-4a99-ada5-3c1f8ad89566%40googlegroups.com.
