My head's been out of TW for several months so all this Bob stuff is new to me. Well done Jed and and everyone involved!
But I have a question about a statement on the Multi-User TW5 plugin github site where you say "*a git plugin is currently being developed*”. I see this as critical to multi-use TW on the open web and very keen to hear about its status. I should explain why. 20 years ago I spent a lot of time on the original c2 wiki. I ran one of its sister sites, GreenCheese, edited about 2000 pages of the original WardsWiki, and built the first open source clone of it, “CvWiki". So I saw most of the heat-death of c2 up close and personal. I was one of the dozen folk Ward picked as stewards to try to defend it form the trolls … unsuccessfully … Right now I'm running the “free and open source agile” community at http://xscalealliance.org . We have a TW at http://xscale.wiki but most of our communications are going via slack. I see slack as very inferior to the wiki way and I’m keen to open up xscale.wiki to multiple users. But given the broad potential community I think I need git integration to do it. I had been thinking that we’d just let practitioners use TW's single user node.js server to edit, and then submit pull requests in the usual git way. I probably don’t need to tell you that’s clunky … What I’m hoping for is a multi-user mode where users are able to make a number of local edits on their local copy of the wiki, then when they press "save" we would have a pull-request generated automagically along with a little form for them to fill in the purpose of their edits. After that, normal github-flow should be sufficient for the community to police its own development. Though I think we might also want the “Recents” tab to be improved to change the river to reflect the recently changed tiddlers. RecentChanges was the beating pulse of c2 … to the point that back in the day many of us made it our browser’s homepage. We called ourselves "RecentChangesJunkies" ... No worries if you meant something completely different by this but I thought it might save us a lot of duplicated effort if you’re going down this path and I'm enormously impressed with the progress you've made on Bob to date! Cheers, Pete On Tuesday, 16 October 2018 03:03:32 UTC+11, Jed Carty wrote: > > I ended up doing some things on the back-end of Bob that would break > backwards compatibility if anyone modified the server components of Bob. I > am not aware of anyone who has but this gets a minor version bump anyway. I > never got through testing version 1.0.7 before getting distracted so those > changes got rolled into this. > > This is a prerelease for now because there have been a lot of changes and > while I am not aware of any new bugs from them, there may be some I have > missed. As always, back up your wikis!! The easiest way is to just make an > archive of your Wikis folder and the IndexWiki. > > The big changes from the perspective of using Bob are: > - you can now build html wikis that take tiddlers from any of the wikis > served by Bob instead of just building an html version of an existing wiki. > - You can select which plugins from the server should be used in the > current wiki > - Custom tiddler paths using $:/config/FileSystemPaths should work now > > The plugin version of Bob is on GitHub here: > https://github.com/OokTech/TW5-Bob > The newest version of BobEXE is available here: > https://github.com/OokTech/TW5-BobEXE/releases > > If you want to support the development OokTech has a patreon page here > https://www.patreon.com/OokTech > or if you prefer there is a link for PayPal here > > https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZG94CTLHTKYRE > > > Here is the current changelog for version 1.1.0 > > !! Version 1.1.0 (ongoing) > > - Add `savePluginFolder` web socket message to save packaged plugins as > folders on a server. These plugins can then be available to other served > wikis and in the plugin library, if it is enabled. > - Add the `import` browser message handler to make fetching nicer > - Add options for how to handle conflicts for `internalFetch` > - `internalFetch` now displays a list of imported tiddlers > - Added a way to change which plugins a wiki uses from inside the wiki > - In the Bob Settings tab there is a Manage Plugins tab > - Added an interface to save plugins to the server and to select which > plugins from the server should be used in the current wiki > - Change the internals to make one $tw.Wiki object for each wiki instead > of having them all in $tw.wiki > - There are lots of internal changes to make this work > - $tw.boot.files still uses the prefixed name > - Streamlined and simplified the file system monitor > - It should now watch new subfolders inside the tiddlers folder > - Environment variables are now set from the plugin, themes, and languages > paths given in the settings. > - This is needed by the core to properly list available plugins > - This means that you can set the location of one folder listing > plugins, themes and languages in the settings instead of using > environment variables. At the moment this is limited to one folder. > - The `unloadWiki` message now ensures that the connection to any browsers > with that wiki open are closed correctly. > - Updates to the `buildHTMLWiki` message > - You can now pull tiddlers in from any served wiki while making an > html file. This means you can combine wikis in the output. > - There is a default filter for excluding plugins like Bob and > components that are only useful on a server > - You can add an additional filter to exclude tiddlers from the > exported html wiki > - You can disable the default exclude list for more control > - The `$:/config/FileSystemPaths` settings should work now > > -- 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 post to this group, send email to [email protected]. 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/1cf875b1-6304-4b0a-acec-c658e82b877f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
