> But the lack of an .exe exporter means it's a no for me.
>
I don't think you should put a vote against the licensing model because you don't like the features - they're different things. If we did an EXE exporter, that would not change the proposed licensing model! So the question is, is it a good licensing model?
We've been over the EXE exporter in other threads - we knew we'd disappoint many people with HTML5, but we took a risk and did it anyway, and we still want to eventually produce an EXE runtime. So hopefully everyone is happy in the end!
But you can't seperate the license from its product. That's like saying "I can't really say what exactly I will sell you, but I want to charge 200 ? for it. Is it ok?"
We can only say if a licensing model is a good idea for the specific product it is offered for. And without a guarantee for an .exe exporter, a robust editor, and at least the feature set of Construct 0.x, well, without all this that model is a bad idea.
I don't mind that those features will take time until integrated, but it needs to be definitely in. And as soon as it is so, then that license model is a good idea.
Because, apart from real Scirra fans, people will only buy a feature rich, complete (for its tasks) product.