An example of the image at the time of running the software
There are three levels of compression:
Without removing the line feed
Line feeds are not removed from the script (except where they are considered unnecessary, such as blank lines). Only comments and extra white space are removed. This provides good compression and ensures that no code is broken.
Line feeds are omitted wherever possible
In this case, line feeds are removed from the end of statements where it is determined that it is safe to do so, typically resulting in an additional 2-5% compression. For example, lines ending in an operator such as *,,,/+-etc., and those ending in a semi-colon will have all trailing line feeds removed. There are several other conditions that can result in exclusion, which are described below in the Code Description section. Also, steps are taken to prevent deletion in cases such as missing semi-colons so that the code is not broken. However, I may not have caught all of these conditions, so if the code breaks with this state, you can go back to the above state. This mode achieves its best results when you are diligent about placing semicolons after all the expressions you can use to properly mark your endpoints.
Function parameter and variable name compression
This can be combined with one of the first two compression options to further reduce script size. When enabled, function parameters and variable names are renamed and shortened as much as possible. The naming scheme starts with the names a through z, then _a through _z, _aa through _az, _ba through _bz, and so on. With this option enabled, script size can typically be reduced by 10% to 15%. There may be more potential for broken code with this option, so it is not enabled by default. If enabled, it is recommended to fully test all compressed scripts before deployment.
Dear user, you are offered a download