Dear Jeremy and Jed and Bob :-) Anything that eases plugin install is good! Bob's various mechanisms for fetch, plugin install (local) etc are really superb.
Its also worth mentioning Quinoid, Mark S's baby on Android, has an excellent fetch, customisable, mechanism to install remote TW onto your phone. My wondering, somewhat left-field, is not so much about the mechanisms as what proportion of plugins are on github? Dave's Toolmap thing has, I think, improved the situation with findability enormously. But I still struggle to locate what I need. Not quite sure exactly what I am saying .... I guess its there is an *informational* dimension that is not entirely orthogonal to the tech side. If these initiatives can improve findability (and by implication, "indexing") I think it would be excellent and definitely enhance usage. But what about stuff that isn't on Github? Just thoughts Best wishes Josiah I'm wondering On Wednesday, 3 April 2019 11:01:59 UTC+2, Jeremy Ruston wrote: > > Hi Jed > > I’ve been meaning to experiment along similar lines. I had my eye on > unpkg.com, an independent project that provides a gateway to files stored > in npm. It’s intended so that scripts can reference things like: > > https://unpkg.com/[email protected]/boot/boot.js > > The really interesting thing is that the files are served with > access-control-allow-origin: * > > So, we could fairly easily take the repository > https://github.com/jermolene/jermolene.github.io that contains the raw > files for tiddlywiki.com and publish it to npm. Then one would be able to > do things like: > > > https://unpkg.com/[email protected]/library/v5.1.19/recipes/library/tiddlers/%24%3A%2Fplugins%2Ftiddlywiki%2Frailroad.json > > <https://unpkg.com/[email protected]/library/v5.1.19/recipes/library/tiddlers/$:/plugins/tiddlywiki/railroad.json> > > Best wishes > > Jeremy > > On 3 Apr 2019, at 09:34, Jed Carty <[email protected] <javascript:>> > wrote: > > I think I sort of buried the lede in the last release post for Bob, but > one of the new features is that it can now get plugins directly from GitHub > repos. You can just give it the URL and it will fetch the plugin and save > it to your library of plugins so it is available to all of your wikis. > > I have tried to make a version for single file wikis, and it works, aside > from my nemesis, CORS headers. From a browser you can't download the zip > files from GitHub because they don't have CORS set up to let you do that. > You may be able to down load specific files, but from what I have been able > to find you can only do that if you know the names of the individual files. > So the only realistic way I have been able to come up with for a single > file wiki to get and build plugins directly from GitHub requires some sort > of relay server. Bob could act as this server, but if you have Bob running > it would be easier to just get the plugins with Bob and then either make > your wiki in Bob and save it as a single file wiki, or use TWederBob to > fetch the plugin from Bob. > > So, for anyone who was able to follow my rambling, is it worth setting up > Bob as a relay like this? A publicly accessible Bob server like on > ooktech.xyz could also act as a relay which may make the relay idea much > more useful. But so far I don't think anyone is really using the plugin > library there so I have no idea if anyone would care. > > > > The next part is about Bob itself. Currently Bob is quite large, about > 750kb, which is around half the size of an empty wiki. On slow connections > or older hardware this could add a significant amount of time to loading a > wiki. > I can modify how Bob sends wikis to the browser so that it only sends the > required parts to the browser, which come out to around 250kb. The biggest > problem I see with this is that you would not be able to install Bob by > dragging and dropping the plugin into a node wiki. > My hope is that BobEXE means that isn't really necessary anymore, but I > wanted to see how people feel about it. > Another potential concern is that you no longer get to see all of the code > for what Bob is doing in your wiki. I don't think that this is a concern > for most people, and the code for Bob is up on GitHub, but one part of > tiddlywiki that I like is that you can see all of the code that is running > right there in your browser. > > -- > 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] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > 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/6fe8da01-dbeb-4158-9637-7b301e1c5398%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/6fe8da01-dbeb-4158-9637-7b301e1c5398%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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/a1189a69-7ded-4a7e-9c14-6fbe8984dd7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
