Tony, The purpose of Bob is that you download BobEXE and run it and it works without any configuration. Adding required configuration is not something I am going to do. I am also not going to create multiple versions that behave differently and add that confusion on top of everything else.
Having someone use Bob and not explaining that it is running a server on their computer with all of the associated warnings about what that means when Bob opens the first time is exactly the opposite of what I want to do. While proper informed consent isn't always possible or practical because many/most people don't have the background to understand what any of it means or don't care about the risks that has to be something that they decide. They are taking a risk of some sort, if they want to move forward with that even if they don't understand the details that is their decision, but having Bob start up without explicitly informing them that there can be some element of risk is not something I am willing to do. As it is I need to add more explanation of the saver server to the default Bob edition. The single file saver part of Bob is very simple, if you want it wouldn't be difficult or take much time to re-implement it I c++ with QT5 or something similar to make properly compiled native binaries for different systems and give it a taskbar icon and all that fancy stuff. I am working on adding a wrapper on BobEXE to make it a proper app bundle in OS X and looking at different options for it in Linux. In my experience windows doesn't play well with others so something for windows may have to come from someone else. -- 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/0631309b-bfac-4ab7-9ca8-8bc915ad0714%40googlegroups.com.
