Thanks for your suggestions! I will pass them on to the developers.
However, the short answer to most of your requests is: we don't want to create another scripting language. Instead, we'd like to make iMacros as good as possible in what it is designed for: automating/extracting web sites. Leaving everything else to the scripting/programming language of your choice.
But here's more detail:
tata668 wrote:{{!LAST_EXTRACT}} would be a good idea though...
Using iimGetLastExtract() you can address the separate extractions, cf.
http://wiki.imacros.net/iimGetLastExtract
- more (unlimited?) custom variables settable inside the macro itself, not just VAR1, VAR2, VAR3
We recommend leaving the variable handling to the script. That way you can use as much as you like, with whatever name you want, and with all the methods working on it that your scripting language provides.
- simple "if" inside the macro itself (I know you can do this in a script):
And this is exactly where it should be placed. Just as all the kinds of loops (for/while/until/...).
- We should be able to set a key for each value inside !EXTRACT. This way it would be easier in a script to know which extract is which.
As said above, iimGetLastExtract() allows for accessing each of the extracted items independently. Save it to a variable and you have a unique, speaking name for it.
- A way to set our own custom error code when exiting a macro maybe?
There's a difference between macro errors (TAG not found, Syntax error, User exit) and handling the extractions. The latter surely belongs to the scripting part.