@ Jed Thank you for building this incredible toolset. It's badass. Among the many things it does (and you obviously know more than I do about what it can and will be used for), your tool makes Tiddlywiki a realtime GUI terminal for me, and it makes scripting outside of javascript for my wiki more worthwhile too. I suggest you have defeated some difficult race conditions.
> I just realised that I haven't released a lot of what I made after I got frustrated with some things so I haven't released my tools yet. But I have made things for Bob that take a single file wiki and split it up into .tid files and multiple methods for compiling a single file wiki from Bob. But compiling .tids into a single file should be a single button click. The two main methods I have right now are a download button that gives you the current wiki as a single html file without the Bob plugin or any of the server plugins (so like the download empty button on tiddlywiki.com, but it downloads the current wiki) and one that can take tiddlers from any of the wikis served by Bob and complies them into a single html file. I will gladly click. I'll likely be running a bare minimum OS and browser with automated clicking inside a virtual machine to do it though. I just saw you had a release today. I'm excited to use it. > So using Bob to edit and have it give you a single file wiki is possible, I just never got around to publishing it. I am grateful to be able to see your previously unpublished work. Even the sketch of how you think it should be done is valuable to me. > I don't know what you use for signing but that doesn't sound like a bad idea for distributing wikis that aren't meant to be edited. I use PyNaLC (https://github.com/pyca/pynacl). I sign the wiki every minute. Currently, the signature file is separate, but I'm going to be saving the signature inside the wiki instead soon enough (when I get to it). The script will remove the old signature, generate the new signature, and place it in. I use a script to verify (which comes with the wiki too). I can't say I'm good at this part either, but I very much want my wiki to be self-contained. > I am dyslexic and can barely read anything on your site so I have no idea what your process is there, so I don't think I can help much with that part. I'm sorry. Perhaps I should offer an easy way to change the font to something more palatable (though, I daresay legibility improvements might not improve its readability). You have already helped with the process I have in mind! I'm re-engineering the backend of my process in virtue of Bob. @ TonyM Thank you very much. I actually did some testing in light of what you said and developed a response (it's sitting on my wiki), but now I can see that what I had to say is irrelevant with Jed's new release of Bob today. The export is clean and fast. Yay! On Wednesday, December 5, 2018 at 5:58:17 AM UTC-5, TonyM wrote: > > H0p3, > > As much as we seperate save and export, I understand they are effectively > the same thing. During the save process a filter is used To choose the > tiddlers which ultimately saves the whole wiki. So you could build a wiki > with authorship tools that generates a published wiki without those tools > through the use of a custom export filter. Perhaps a username could be one > of the filters or export everything except a subset. > > I can think of another possible mechanisium I will share soon. > > Tony > > -- 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/72f3a897-5476-45e2-aefe-e399ea8f3e65%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
