I have to find a good way for tiddlywiki to determine if Bob is currently running or not and have it use this saver if Bob is running and to fallback to the manual download saver if not.
I will put that in the next release
I imaging preparing a website on the internet and the plugin to use local host with an unusual port e.g. 8087 with be the most effective way to stay local only and not clash with an existing port.
Then all they do is install bob on any platform, reload the wiki and its done.
With careful use of the local storage plugin we can retain any history or changes made when online and save them via the plugin and turn off local storage.
This is getting very close to perfect, as the first step.
A little more guidance and they will be using bob as a local platform, server, new wikis etc... With no additional installation.
Good stuff
Tony
I finally got around to adding a way for Bob to let you work with single file wikis.The way it works is that you have Bob running, you have a plugin installed in your single file wiki and then you proceed normally.
Just a dumb question. I use (in this scenario) a single TW-file with the bob plugin. To use it I have to start the bob server. How do I start the bob server? This information is missing. As a noob I don't know how I should use the bob plugin. The simple sentence "start bob" is not very useful for me.
The browser shouldn't matter at all to the plugin unless there is some browser that doesn't allow javascript to send http requests.
... I wasn't able to get IE to work with Bob, but don't think that it was a Bob problem. It might be that my IE
was too out of date, ...
That needs to be an option not the standard behaviour as having the saver hidden pending loading finding a bob server can simplify workflow
Tony
I will provide one or more methods to add bob.exe to load on startup on windows. You can choose what suits you.
Regards
Tony
Adding that check should be easy enough, but I agree with Tony that it has to be optional behaviour.
If this continues to work well and people like it than I will get it added to the core as one of the savers and if that were the default behaviour every wiki would complain if it couldn't find Bob.
Tony,
Thank you, I have no idea how windows handles things these days.
Stefan,yes, you can suppress the browser opening. I will add a checkbox in the control panel for this in the next version, but for now you need to edit the manual settings.
Dim WinScriptHost
Set WinScriptHost = CreateObject("WScript.Shell")
WinScriptHost.Run Chr(34) & "C:\Scheduled Jobs\mybat.bat" & Chr(34), 0
Set WinScriptHost = Nothing
Stephan,See my previous post for another approach. The shortcut is set to open minimised.
Stephan,As Mark states and Jed Elsewhere people using a server program installed on their computer need to be aware of it, they need to give consent to possible security issues and exposure, they need to see the IP Address(s) to find there wiki etc... so I do not see this being hidden by default.
I finally got around to adding a way for Bob to let you work with single file wikis.The way it works is that you have Bob running, you have a plugin installed in your single file wiki and then you proceed normally.You don't have to do anything special when opening the html file and there aren't restrictions on where it can be saved on your computer. Just double click on the file and edit.Of course this is the first version and there is one big annoyance, I have to find a good way for tiddlywiki to determine if Bob is currently running or not and have it use this saver if Bob is running and to fallback to the manual download saver if not.So far the way that tiddlywiki determines which savers are available doesn't support this situation because the saver availability can change even without reloading the wiki.I am working on it.To install the plugin and for more information you can drag and drop it from here:https://ooktech-public.gitlab.io/bobsaver/
So the switches to the download saver are probably from some problem that doesn't always let the browser ping Bob.
I don't know what would cause it.
In another thread I was asking if the various savers could indicate they have saved when they do so at least we could see that they did in retrospect. With a few filesvers now working on file:// it is getting harder to tell which saver was used.
It would be simple as a save time stamp and saver name. Which we could test or to look at to see which saver was successful.
Regards
Tony
Thanks!