[TW5] testing Bob and BobEXE version 1.0.7 prerelease

158 views
Skip to first unread message

Jed Carty

unread,
Oct 5, 2018, 2:34:28 PM10/5/18
to TiddlyWiki
This update is focused on improving the fetching interface and the plugin server functionality.

You can now add plugins to the plugin library from inside the wiki and you can use any plugins that are available in the plugin library in any of the served wikis. You can drag and drop a plugin into a wiki and then use the interface in the control panel to save the plugin on the server. Then in the control panel you can select which plugins you want to include in the wiki.

Both features work but I haven't had a chance to thoroughly test them or to figure out what would be a good interface. Which is why we have the prerelease version here.

I am sure that as soon as anyone else touches it there will be many bugs that need to be fixed so have at it.

Some more documentation about the plugin library features is here:
https://github.com/OokTech/TW5-Bob/blob/master/Documentation/Plugin%20Library.tid

Documentation about the individual components is in the documentation included with Bob.

The plugin version is available here: https://github.com/OokTech/TW5-Bob
The BobEXE version is available here: https://github.com/OokTech/TW5-BobEXE/releases/tag/1.0.7

!! Version 1.0.7 (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` borwser 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
- Added an interface to save plugins to the server and to select which plugins
from the server should be used in the current wiki

TonyM

unread,
Oct 5, 2018, 8:01:14 PM10/5/18
to TiddlyWiki
Jed,

It is great to see your continuose innovation of Bob, thanks so much.

Centralised management of plugins is very helpful, and I will implement this once past prerelease. It will however be a rework of my current wiki network and will require a time commitment.

You are running at the leading edge and may only get responces from early adopters but be assured your solutions will in time be adopted by many more people since they offer systematic improvements.

Tony

@TiddlyTweeter

unread,
Oct 6, 2018, 4:22:48 AM10/6/18
to tiddl...@googlegroups.com
Ciao Jed & Bob

The revised "internalFetch" is excellent allowing comparison of "original" and "imported" versions before you make a choice. It worked faultlessly for me. (Bob single executable, Win7, Firefox52, all 64-bit)

Small cosmetic glitch after replacing. After having displayed the Import version, the pointer to the (no longer existing) state Tiddler is not expunged ... for instance this is left on-screen after a successful fetch with overwrite.

Best wishes
Josiah

@TiddlyTweeter

unread,
Oct 6, 2018, 7:55:32 AM10/6/18
to tiddl...@googlegroups.com
Ciao Jed & Bob

I just started looking at the new plugin gizmo.

Immediately I want to suggest that the Plugin List generated in $:/plugins/OokTech/Bob/SelectPlugins present so that the Bob plugins have their own group at the top (because of their importance). In other words, the list start like this ...

Bob Plugins
 
[ ] OokTech/Bob
 
[ ] OokTech/TWederBob

Wiki Plugins
 
[ ] tiddlywiki/async
 
[ ] tiddlywiki/aws
 etc
...

Best wishes
Josiah

Matthew Lauber

unread,
Oct 12, 2018, 8:32:06 AM10/12/18
to TiddlyWiki
In the version of BoxLinux I downloaded (1.0.7), I ran into what I think is a typo.  In the file $:/plugins/OokTech/Bob/SelectPlugins the following code appears to have the katex plugin hardcoded.  

<$button>
  Save Plugin As Folder
  <$action-websocketmessage
    $type='savePluginFolder'
    plugin='$:/plugins/tiddlywiki/katex'
  />
</$button>

Jed Carty

unread,
Oct 12, 2018, 8:36:45 AM10/12/18
to TiddlyWiki
Oh, yes. It looks like I left in my testing code. I will hopefully have time to fix it when I get home tonight. Thank you for pointing that out.

Matthew Lauber

unread,
Oct 12, 2018, 10:14:49 AM10/12/18
to TiddlyWiki
When I replaced that code with what I think should be there (the name of the plugin tiddler starting with $:/) I was able to write the files to the FS, but they're still not showing up in the available plugin list.  I'm not sure exactly why not, I need to download the source version of Bob so I can debug that side of it.  

Jed Carty

unread,
Oct 12, 2018, 11:51:10 AM10/12/18
to TiddlyWiki
To try and cover the simplest problem right away, you have to refresh the list by clicking the 'Update Plugin List' before the new plugin will show up. If that isn't the problem than the next thing to check is to make sure that there is a plugin.info file in the saved folder. I don't know why there wouldn't be but that is the first thing I can think of to check.

Matthew Lauber

unread,
Oct 12, 2018, 2:41:18 PM10/12/18
to TiddlyWiki
Figured out my issue.  It's not actually a bug in your code, per se.  This line in boot.js only executes if the TIDDLYWIKI_PLUGIN_PATH env var is defined.  Once I defined that to point to the same folder I defined in the settings, my plugins started to show up correctly.  That looks to me like a bug, but I'm really not that well versed in the boot.js plugin loading code.

Jed Carty

unread,
Oct 12, 2018, 2:46:02 PM10/12/18
to TiddlyWiki
I hadn't noticed that because all of my tests use scripts that set the environment variable. I set that inside the code for the online version so I may be able to make that happen in the Bob plugin as well.

I am always surprised by how many edge cases pop up as soon as multiple people use the same software.
Reply all
Reply to author
Forward
0 new messages