AutoIt Script Cleaner

[grzesiek]

I would like to share with you a program which does similar tasks to Obfuscator, but not in the same way and has some other features. Here is the description of the program:

The program can be used to clean, optimize and obfuscate an AutoIt script before using it, before compilation. A file with the whole program script is created, with added functions from UDFs. Changes in the script should be made in the original script.

Only functions and global variables used in the script are added from UDFs, instead of adding whole files. When adding a global variable, if possible, the variable name withing the script is replaced with the value assigned to the variable during declaration, instead of declaring the variable. Unneeded data are removed from the script. The names of functions and variables are shortened. Recycling of variables is performed - no longer used variables are reused instead of creating new variables. This way the script will work efficiently, use less computer resources, less space. The program also replaces in the script @ScriptLineNumber with the line number, this way also after compilation the line number is returned.

It is likely that your script will not immediately work with this program, the script has to be compatible with the program. Please read the informations in the program before starting to clean the script.

The program does a lot of operations and is written in AutoIt, so it slows down the processing of the script.

You do not have to pay to use the program, but if you want you can make a donation.

Here is the link to download the program: https://sites.google.com/site/programs1131/programs/autoitscriptcleaner/AutoIt%20Script%20Cleaner.zip

Edited July 1, 2012 by grzesiek

[Skitty]

Sound's a little like the obfuscator used with the "/so" parameter, can you explain what you mean by this statement "names of used variables are replaced with values or declarations of those variables are added", I'm having a little trouble understanding it.

Edited April 11, 2012 by ApudAngelorum

[grzesiek]

When using a constant variable declared in a library, the program can replace the variable name within the script with the value assigned to the variable, instead of adding a declaration, thus highly reduce the number of declared variables.

[BrewManNH]

That's a bad idea, what if, down the line those constant values change? Now you're stuck with a wrong value assigned to where a variable was before.

[FaridAgl]

When using a constant variable declared in a library, the program can replace the variable name within the script with the value assigned to the variable, instead of adding a declaration, thus highly reduce the number of declared variables.

Why we even use constants?

[ProgAndy]

It is an interesting project, somewhat an obfuscator which does not hide the values of the variables.

Recycling of variables is performed - no longer used variables are re-used instead of creating new variables.

How do you determine whether a variable can be reused?

That's a bad idea, what if, down the line those constant values change? Now you're stuck with a wrong value assigned to where a variable was before.

Constants cannot change. Edited April 11, 2012 by ProgAndy

[BrewManNH]

The values that the constants refer to in the xxConstants.au3 files can change, and if you've run this program on your script, and it's converted the old values to "magic numbers" instead of leaving the variables where they were, you now have values that don't work.

[ProgAndy]

The values that the constants refer to in the xxConstants.au3 files can change, and if you've run this program on your script, and it's converted the old values to "magic numbers" instead of leaving the variables where they were, you now have values that don't work.

I cannot agree with that. Once you have converted your script you do not access the includes anymore. The "magic numbers" are perfectly fine for the version of the UDFs integrated in your script. If you want to make changes use the original script, and when you are finished perform the merge again. Then you get the correct new constants for the changed functions.

[guinness]

I suppose it's on the same lines as using Macros e.g. #define, #ifdef etc..

[BrewManNH]

I cannot agree with that. Once you have converted your script you do not access the includes anymore. The "magic numbers" are perfectly fine for the version of the UDFs integrated in your script. If you want to make changes use the original script, and when you are finished perform the merge again. Then you get the correct new constants for the changed functions.

We agree to disagree, I will never think this is a good idea.

[guinness]

$GUI_EVENT_CLOSE is constantly -3 and never changes (unless done so by the user) so I can't see a problem changing this Global variable to it's subsequent value of -3. Or did I miss the point?

Edited April 11, 2012 by guinness

[Skitty]

Or did I miss the point?

Doesn't seem like it, but the problem is that the OP explains this in a cryptic tongue, confusing me and the majority of everyone else here, you have a gift, obviously you can translate very well for these kinds of people.

Edited April 11, 2012 by ApudAngelorum

[UEZ]

I tried your program with AutoIt Windows Screenshooter v1.43 Build 2012-02-16 Final but the result is not working. A lot of errors (already declared/assigned) when trying to start the optimized script.

Beside that it took a long time to optimize the script.

Br,

UEZ

Edited April 11, 2012 by UEZ

[guinness]

I tried to tackle this program a second time without any result I'm afraid. I'm just curious as to why this can't be standalone? In that I run it, select the AutoIt file and voila it outputs a new AutoIt script.

[Skitty]

I just tried the program and was surprised that it added itself to the right click context menu.

Actually, I was more surprised that the context menu entry did not appear so that I could begin to optimize various scripts..

Also, I noticed that you didn't actually just delete autoit's default icon, you replaced it with the shell32 default application icon... if you just delete the icon, windows will automatically assign your binary that specific icon you included, there's no need to include it with your application.

[BrewManNH]

Seems like the download has been taken down, page not found error on the download page. Both the english and polish versions have been taken down.

[Skitty]

And no response from the op about this?

[grzesiek]

Thank you for testing. I disabled the download right now, I will have to fix some mistake.

I will response to questions later when I have a time.

[grzesiek]

The program is again available. I improved the program, added more description, also the cleaning process takes now a bit less time. It took me a while but it was a lot of work. I think the program works good right now, but there still may be some problems which I did not spot. I updated the first post.

Also, I noticed that you didn't actually just delete autoit's default icon, you replaced it with the shell32 default application icon... if you just delete the icon, windows will automatically assign your binary that specific icon you included, there's no need to include it with your application.

The system icon is used only when I remove all icons, so I would now be able to use any icons.

How do you determine whether a variable can be reused?

The program checks the positions of variables, the type of the variable, and by this knows if the variable can be reused.

Sorry for late reply.