Suggestion for 2.0

Make Construct 2.0 based on a integrated script-code, like ConScript.

The drag'n'drop and the python editors will remain, but everything you create with those editors is ConScript, just displayed visually.

For example, any currently created cap with drag'n'drop will have ConScript, and drag'n'drop would be there just to make the program more user friendly.

ConScript, obviously, would be manually editable, for faster creation and easier problem-solving.

I don't think this is practical.

Parsers for scripting languages (and optimizing their execution) are an extremely specialist and time consuming area. I don't know much about it. Also given that the selection routines for conditions are very complex, I think the auto-generated code would be extremely ugly and difficult to work with, which would defeat the point. It'd probably be slower, too - we'd never have time to write an optimizing compiler-to-assembly, so it could never compete with the compiled code in the runtime at the moment.

Integrated Python snippets (when it works), on the other hand, are already fast, flexible, and can perform the algorithmic things that events aren't so suitable for.

In short, I think this is one of those "wouldn't it be amazing if..." ideas, which in reality, would be cumbersome, not as useful as people imagine, and a huge drain on developer's time.

Ah, thanks for the clarification. So 2.0 will use the same drag'n'drop system as 1.0?

Yes :--).