Hey @TiddlyTweeter I checked out innerwiki.js. It's less about it being recursive, and more about innerwiki using async functions which are >=ECMA 6 features, and aren't supported by UglifyJS. No worries. It just means that single file wasn't compressed.
The freezing on modification is one issue I'm not sure what to do with. Apparently TW5 *completely rerenders itself* after every change, and without modifying the core, I don't think there's a way for Uglify to recognize the difference between a rendering from a change, and rendering because TW is saving to disk. Fortunately this problem only happens once per browser session, since results are cached, and it doesn't occur with NodeJS implementations. Otherwise, glad you like it! -Flibbles On Wednesday, January 20, 2021 at 8:48:28 AM UTC-5 TiddlyTweeter wrote: > *Side thoughts on text/wikitext uglification :-)* > > Flibbles wrote: > >> I'd love to have wikitext compression too; there are some things I can >> do. But it's super tricky. >> > > Right. > > Maybe that would a *later thought* for *other situations* than we > normally face? > I'm thinking particularly of *e-pubs *where you can have huge texts (e.g. > novels) with vast excess space use. But I have NO idea how you could get a > minify of that working in a TW. > > Best wishes > TT > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b6208e38-1995-441b-a659-96313aaf468cn%40googlegroups.com.
