Well, Jed's adapter and everyone's thoughts so far inspired me to do a little exploring and I managed to put this little proof of concept together. It turned out I did not need to touch the client at all and only modify four routes on the server. What's nice is that the index is still generated as usual so you can turn off the plugin and make changes to the initial HTML document if you want, then turn it back on and all your database tiddlers come back again. Almost like a template. The plugin is inside the data folder for now, but the npm install needs to be done in the tiddlywiki root folder (the folder containing tiddlywiki.js). The readme has rather simple instructions and the npm install command that needs to be run.
On Mon, Dec 2, 2019 at 10:38 AM Arlen Beiler <arlen...@gmail.com> wrote: > I think in this case I'm rather aiming to build something new on top of > TiddlyWiki5. I may revisit the rest of the TiddlyWeb protocol at a later > time and take some ideas from it. However, I think that to build something > new it would need to be built using TiddlyWiki5 from the ground up, whereas > tiddlyspot was built for TWC. That's just how I work best. For someone else > to take a different approach would not bother me at all. > > On Mon, Dec 2, 2019 at 5:30 AM mauloop <maul...@gmail.com> wrote: > >> Why not to reuse Tiddlyweb/Tiddlyspace work? >> >> - It has MySQL backend >> - It is multiuser and allows concurrent editing >> - It has public and private spaces >> - It uses the standard Node.js sync-adaptor >> - It works with TWC as well >> >> IMO it is a great piece of software. Not easy to set up. I did it on a >> local VM just to give it a try and Chris kindly helped me to solve some >> problems I fell into. I always feel bad when I see that good software falls >> into oblivion. Maybe it is not to be taken as is, but it could be a good >> starting point. Just to not reinvent the wheel. >> >> Another thought is... this is an old paradigm. PMario's suggestion (DAT >> protocol) goes one step beyond, moving towards the p2p paradigm. I use >> Syncthing to keep my devices synced. Both (DAT and Syncthing, which, I >> think, uses QUIC behind the scenes) provides versioning, encryption and, >> last but not least, ... privacy! >> >> TWedereation goes this direction too, isn't it? >> >> I have no much developing skills to contribute, but I would be happy to >> help testing if needed. >> >> )+( >> >> -- >> 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 tiddlywiki+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/cb3cdfd0-e05a-417a-a329-1281e2064ecb%40googlegroups.com >> <https://groups.google.com/d/msgid/tiddlywiki/cb3cdfd0-e05a-417a-a329-1281e2064ecb%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSe4-y4wR%3D6o_ihBmYe8E_bUqAgqT0tpb7LwaSpv7K9Uw%40mail.gmail.com.
