I'm not sure how you're "servering versions" or even what that means, but I assume it's about generating standalone tiddlywiki files from a NodeJS tiddlywiki. If that's the case, then a publish-filter already exists. It's part of the "rendertiddler" command. You can see the uglify tiddlywiki.info file for an example of how to generate a tiddlywiki file without certain plugins or files. In Uglify's case, it creates one without the jasmine plugin, or any tiddlers with the "Test/' prefix.
-Flibbles On Saturday, June 19, 2021 at 6:21:39 AM UTC-4 Jan wrote: > Hi Flibbles, > I think a publish filter is a good idea, I wanted to do that for years > with Mat's publish-plugin but lost it out of sight. What is the best tool > to do this right now? > It would be interesting to combine this with your plugin to have the > maximum reduction. > > Best wishes Jan > > Am Sa., 19. Juni 2021 um 01:21 Uhr schrieb Flibbles < > [email protected]>: > >> Hey Jan, >> >> I'm glad Uglify works well for you. To answer your questions >> >> >> 1. Removing overridden core Tiddlers could reduce the code size >> somewhat, but I'm not sure how often that use case would come up. Even in >> my beastly TiddlyWiki projects, my overridden tiddlers don't make up very >> much space, particularly since I (and most people I'd think) only >> override >> smallish tiddlers. If it's something larger, a monkey-patch injection is >> used more often. Meanwhile, removing those overridden shadows could lead >> to >> a whole slew of nasty bugs if someone A) Removed the override down the >> line, or B) Tried to export their project into any form other than >> exactly >> what it is. >> 2. Temporarily removing deactivated plugins seems out of scope for a >> content compression plugin (But just by a little. It compresses plugins. >> Removing them is a different job), and it's probably best done by the >> user. >> If they are serving versions of a tiddler where they want certain plugins >> excluded, they'd could use the publishFilter. A slightly elaborate >> tiddly-filter could exclude all deactivated plugins. >> >> >> Hope this helps! >> -Flibbles >> >> On Friday, June 18, 2021 at 6:45:03 PM UTC-4 Jan wrote: >> >>> Hi Flibbles, >>> great idea! My wikis tended to grow recently this seems to be a great >>> remedy. >>> Some Questions: Could it also remove >>> - overridden core Tiddlers >>> - temporarily deactivated plugins and inactive themes >>> from the version which is served? >>> >>> Best wishes Jan >>> >>> Am Di., 19. Jan. 2021 um 21:26 Uhr schrieb Flibbles < >>> [email protected]>: >>> >>>> Some people want a minified version of the TW5 core, but it'd be too >>>> much work to maintain. >>>> Some people think it should remain uncompressed for the sake of >>>> editors, but TW5 continues to grow by the day. >>>> Some developers compress their plugins, making efficient code, but it's >>>> a pain for anyone debugging it. >>>> Some developers leave their plugins uncompressed, but that means it's >>>> larger than necessary for 90% of all end-users. >>>> >>>> Now there's a solution for everybody: TW5-uglify. >>>> >>>> This is a plugin primarily designed to be used by a Node.JS server. >>>> Your server has access to all your uncompressed and unpacked plugins, >>>> which >>>> is fine, since servers have the speed and memory for it. But what it sends >>>> to browsers are fully compressed plugins. Your little smart phones and >>>> tablets get the efficient TW5 they deserve. >>>> >>>> Or maybe you're a plugin developer who wants to minify their code. Now >>>> you no longer have to resort to using npm-gulp like some kind of chump. >>>> Your build process can remain an entirely TiddlyWiki process. >>>> >>>> Or maybe you want to miniify your standalone TiddlyWiki file. You can, >>>> but... think hard about this before you do it. Because unlike with >>>> TW5-Uglified server, compressing your standalone files is a one-way >>>> process. You'll forever have compressed code unless you download a new >>>> Tiddlywiki, redownload all your plugins, and transfer all your tiddlers >>>> from your old file. But hey! Maybe you're running TiddlyWiki on your 2000 >>>> era Nokia phone in an wifi wasteland. Then go ahead. >>>> >>>> Check it out. >>>> Here's the demo site. <https://flibbles.github.io/tw5-uglify/> >>>> And here's the github page <https://github.com/flibbles/tw5-uglify>. >>>> >>>> Let me know what you all think. >>>> >>>> -- >>>> 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/2ce6fad2-8600-4c73-940c-515548e49c1en%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/tiddlywiki/2ce6fad2-8600-4c73-940c-515548e49c1en%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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/f7283bcf-1f16-426e-bfd7-402dfe712a45n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/f7283bcf-1f16-426e-bfd7-402dfe712a45n%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/14dbaa8f-04f2-4235-854c-5022c687d095n%40googlegroups.com.
