open source or not is not what I was talking about. Nevermind, just keep up the good work, I only wanted to remind you to settle the grounds first. Licensing on top of a closed product as Elite is a bit tricky..
About being open for others I was meaning, any other development on top of yours requires a license from your project and this is a big "against" for people that would love to give their job for free.
Anyway, I'm following up this project closely, I might be interested as well!
Oh, I see. Sorry.
Yes. Licensing from FD is a bridge I haven't crossed yet. I'll just have to see how that goes. That will definitely be squared away before the product goes on sale.
Development with my app would require, out of necessity (you would need the assemblies to reference for a start), a purchase of the app. And, of course, it would require that the end user has a licensed copy of the app in order to use your module.
I will ensure that 3rd party (4th party?) development is covered by royalty-free licence if that is required. I'll discuss that with my lawyer when I get him to produce the licence stuff for me. The only instance where restrictions would be needed would be if FD specifically requires them or if a developer writes something that goes beyond that "grey area" and puts the future of my app at risk.
Thanks for your comments.