I'm more in support of close sourcing the ide, watermarking the exports,
I don't think there should be "pro" closed sourced plugins. A stable more powerful construct could beceome saturated with amazing plugins if all other plugins are opensource as a form advanced documentation. Add-on development should be absolutely embraced and encouraged, with the same liscense as c1, where community made plugins can be distributed freely, or commercially without interference from scirra.
Also, programs that charge for advanced features always feel like ripoffs. Opening up a watermarked c2 as a new user, and being overwhelmed by all the available fx, behaviors, and objects is what'd make me reach for the wallet. Not struggling to extract fun out of a crippled version while staring longingly at screenshots.
About the exporter thing though, it should be navigated with care. The liscense should prohibit the creation of exporters to platforms already done by scirra, but I wouldn't underestimate the eagerness or ability of c2's future community to create exporters. It could be a huge draw. People would kill for the ability to export to android and iphone from a program as easy as construct. There will be many who want to create such things. Holding back the community from creating exporters could close off a huge potential userbase. I think there should be at least one opensource exporter to learn from, the freedom to create exporters free or with a charge, but also a a clear path to partnership. Meaning I go to download the exporter sdk, and on that same page I learn that there are profit sharing opportunities for exporters to the major platforms.
That way, when I consider making a free android exporter, I will consider the possibility of profit and
Instead of my own selling ability offsite, my android exporters could be sold in the construct store, scirra gets a share, but now instead of lucid's random android exporter, its owned and maintained by scirra, and can be included in deals like the c2 super mobile exporter pack
The very worst that can happen, is that scirra becomes the amazing tool notorious for having several free exporters to many different platforms, which means more copies of the main program sold.
.as. far as compiling parts of the source code as a form of piracy, I think there are much easier ways to steal software