It is time to consider user friendliness of the solutions too. For those who are used to TW and can find their way around a problem, these solutions will do. However, can you imagine telling someone knew stuff like:
"Oh, and by the way, the only way to save it, is to download a new copy everytime you modify something." "You can totally save it if you are willing to use a slightly outdated firefox version with an addon that is no longer supported." "Would you be willing to modify a batch-script for every TW you use?" "Do you know to run a node js server?" I use Tiddlyserver for my day to day usage. Apart from the noticeable lag times to load a data folder in my android, it works perfectly. MY idea of an ideal solution based on Tiddlyserver would involve the two things below. 1. Consider packing it to deb/exe/whatever-mac-uses formats. The installer should ideally place necessary shortcuts and menu entries in the corresponding folder to each OS. 2. The opening HTML is replaced by a TW itself. It should show links to the various TW as it does now. In addition, that tiddlywiki should also have a control panel, which would allow the user to new TW paths, and modify settings. It won't be hard to cook up a button that will export these settings to json format. On the other end of debate is people who do not have the necessary admin privileges to install node js on their system. -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/802b886a-88ed-4a38-a041-a00ff1cfd87a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
