Hello all.
Uglify is back, and now it can not only uglify your code, it can prune it down and get rid of features you don’t want.
…or it can JUST prune away features if you don’t care about uglifying. The idea behind this is you can create “production” wikis, which are customer facing, or in some way “final”. You might not want to confuse your customers with things like editing or theme choices. Or maybe you just want to remove features that would otherwise bloat your site.
Currently, there are three major features you can trim away with uglify.
- Editing. You can make your wiki genuinely read-only and cut away hundreds of shadow tiddlers associated with editing. It’ll be as though the editing, create-new, and delete buttons never existed at all. You’re not just hiding the editing tools.
- Server-only content. Did you know that every tiddlywiki, including single-file ones, contain a whole slew of modules and documentation necessary to run features on a Node.JS server? How useless is that? Now you can scrap it.
- Unused palettes and themes. You’ve finalized the palette and theme you want for your site. And pushed it to your website. There’s no need for all those other color sets you don’t need anymore. Get rid of them.
As usual, I’ve tried pretty hard to make sure this doesn’t break stuff, so it’s somewhat conservative in what it cuts. For instance, layout configuration and theme tweaks are still in there, and “Read-only” doesn’t cut importing, and maybe it should?
I’d love to hear feedback. I hope this solves problems for some people.
(Check out the pruning tab in the demo. It show what tiddlers you can cut, and lets you cut features right out of the demo site itself.)
-Flibbles