I entirely agree with you there, Nick.
We are not planning to open source Intype at all. What we're going for is to add extensibility on three levels:
- Basic: Extending Intype with simple bundles like snippets, grammars and themes.
- Scripting: Allowing users to write advanced automation features using JavaScript API.
- Native: A classic C++ based plugin API to be able to add some more system-resource demanding features.
With this scheme community will be able to actually extend Intype in anyway without actually working with the core. The core will stay "our" domain. As usual, we're opened for any feature requests for all of the APIs in these 3 steps and the plan is to make Intype awesome with the community, not just by ourselves.
Currently, the 0.9.4 release is to polish the Bundle Editor which currently works, but is not error safe as we would like it to be. When the BE is production-ready, we will push the manuals to help people creating their own bundles.
After 0.9.4, we're going to move to the second step: JavaScript. There is actually a lot of work done. This will allow people to do awesome automation stuff not only with editor, but also with the project and other "submodules" in Intype.