Make an identical tiddlywiki code compression wizard according to the official website

[XYZ]

This is what the official website looks like

There are two more plug-ins than my tiddlywiki

so I installed them in my tiddlywiki and saved it, opened it and found that the default open icon is not the download icon of the official website, although directly dragging and dropping the html to be compressed by code can also do the next thing normally

Any reply would be greatly appreciated

[pmario]

@XYZ

[…] so I installed them in my tiddlywiki and saved it, opened it and found that the default open icon is not the download icon of the official website

Uglify is an action, that usually only needs to be done once. If it’s done you do not need the plugin anymore. So from my point of view it does not make sense to permanently install it to your wiki.

That’s the reason, why there is an uglify-wizard page. So you can update your wiki and then you are done.

See:

Uglify is even uglier. New features. Sourcemapping extravaganza

Uglify is back. Very ugly, but reliable. Dependable. Supportive. There for you. First: Sourcemapping Before, Source mapping was something that only worked for basic server setups. Now it can work for everything. I’m talking single standalone html files. It can generate a source map directory to sit beside it. I’m talking offline-external-js html files. The tiddlywikicore.js file can be versioned, so you can multiple versions of uglified, sourcemapped core code on your WebDAV server or whatev…

[XYZ]

In my testing of it, when you download the plugin to tiddlywiki, the code compression effect is obvious the first time you use it, and when you add or modify your tiddlers to use it again there are three cases, nothing has changed, the file is 1kb larger and the file is 5kb smaller

[Flibbles]

Like @pmario was saying, you shouldn’t be installing Uglify into your standalone tiddlywiki file. The only time it makes sense to install Uglify is if you’re using Node.JS, and it doesn’t look like you’re doing that.

Also, the Uglify-Wizard should never be installed. That’s intended to be interacted with only through the github page through drag-and-drop. The reason it’s a plugin is just to sandbox all its tiddlers together, which makes it easy to remove itself when the wizard passes back your compressed tiddler.

Also, so we’re clear, Uglify will not uglify the tiddlers you’re working on. It only affects plugins and boot files, so the idea of editing some tiddlers and then saving again won’t actually result in any changes. The only reason to ever bother uglifying a second time is if you’ve installed some new (and large) plugins.

Hope this helps clear things up!

-Flibbles

[Flibbles]

…But I guess if you’re trying to duplicate the compression wizard itself, then yeah, you’d download both of those plugins, and that should be all you need to do. Would this be for offline mode, or for a legacy version?

Edit: Actually, it’s be easier just to save the uglify wizard using the “save” button. It’ll compress its own compression plugins, but it’d still work.

[XYZ]

You’re right. It does download the code compression wizard directly and it works, and the ui ICONS are displayed, just like the original photos

@XYZ

This is what the official website looks like

I tried to add this download guide to my main tiddlywiki repository (because my Internet is often unstable, and I have a deep obsession with downloadable tiddlywiki utilities in case I never find them again). Or the website crashed when I needed it so I wanted to download it to have a sense of security) (I can download the wizard from the official website to the local, but my local files are too many, it’s easy to forget it, So I want to tie it to my tiddlywiki), unfortunately it doesn’t become a web tiddlers directly in tiddlywiki like a normal web page, but is resolved as a select import tiddlers