Jed, I did ask "what you think" so thanks for replying, I had no intention of making any work for you. I hoped I was providing you with an observation that this may act as a barrier to providing a simple tiddlywiki adoption path. You are right its beautiful that BobEXE installs with no configuration. I am actually trying to reduce confusion for the new user as well.
Please let me try and explain what I see as the user experience more precisely. For a user installing BobEXE to make the the New Bob File Saver plugin work (Which is a brilliant piece of work on its own port etc...) the naive users will get the bob master wiki open up, before they try and download the online wiki (COntaining the Bob Filesaver plugin) that promoted the install of BobEXE. I fear many may go off on a tangent and not download/open the file of there downloaded wiki. This is likely to occur on every Operating system. I would in no way expect you to compromise your standards and the informed consent etc.. Perhaps this informed consent could even be added to the Bob Filesaver plugin?. My Intention was to then provide (in the downloaded file based wiki) the steps for the user to open Bob Master and why and how to use it. Kind of an easter egg, when they suddenly discover the value of Bob in their use of Tiddlywiki. I thought this may turbo charge the adoption of Bob. Once installing BobEXE to enable the Bob File Saver Plugin they could just work on their saved site, but here we can point to if they want to make it available on the local network, multi-user etc... how to migrate the single file wiki into Bob. I simply raise these for you to consider, if there were a way to do this while meeting your architecture and design principals. Perhaps you can solve this perceived issue another way? In the meantime I will see how we can get help from a windows developer/install script writer. Regards Tony On Thursday, November 28, 2019 at 9:02:04 PM UTC+11, Jed Carty wrote: > > 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/c0a8023a-222e-4e18-9ec0-e7bb0deaef6f%40googlegroups.com.
