Isn't the NDOC good enouph for documentation ? It's also open source - unfortunately not supported any more but still doing its job just fine. IMHO not less usable then javadocs.
Actually, everyone will have full source code to everything except the engine itself. The engine only does the CPU intensive and very complex job of managing all the model callouts, data bar building, multithreading, multiprocessor, etc. The goal of that is to hide all the complexity from custom built trading rules. That way it's just as easy as AmiBroker or even easier to whip up a trading idea for a strategy or indicator and try it out. So all the base classes for Models, performance stats, etc are all open source. I want the project to be "community driven" where I don't have veto power. We can gradually add a team power users/developers who can vote on improvements. I'll certainly work on them as the project moved forward. But others are able to contribute something they think it needs. Only the engine itself will be protected. That's where all the intellectual property lies. It's a > 2 Megabyte DLL assembly with tons of high performance optimizations for speed and also facilitate faster/easier debugging of trading rules. Wayne
Actually, I really like C#. It's a little weak on the automated tools front but a nice and fast language. I found more uses for the pointer ability. The most powerful documentation in C# is the tellisense (I think it's called) which pops up tips on classes and methods with documentation while coding. That's awesome, it save time from looking up stuff or searching the internet, wiki, etc. I plan to focus on that primarily. And the rest will just be coding examples on the wiki. It's always nice to be able to copy and paste some code that does close to what you want and the tweak it for a trading rule. Wayne
My real emphasis was on test suite - not the engine code, although I understand it's interconnected. I would better not open the pandora box about keeping proprietary code in open source project.
Yeah, I'm thinking about opening the test suite code also. That would be a win/win to reduce work for everyone. But probably not the unit test code for the internals of the engine. It seems that strong copy protection and license keys tracked to the individual for the free version of the engine will make it possible to keep the free version for individuals free forever. That means code obfuscation and serious anti-cracking measures, asymetric license keys. Sincerely, Wayne
If anyone is curious, here's the requirements use for selected and building the copy protection (almost finished). 1. Must allow users to install the engine on any machine they own or lease without the hassle of a new license key. 2. Must NOT have any hardware protection (like dongles)!!! 3. Must allow enforcement against piracy to keep the free version always free. To protect everyone from the cost of piracy, we have the following requirements: 1. There will be an anonymous FREE download but very limited. Users can request the freeware version (for FREE) by requesting it through the mail. 2. The mailed version will be electronically watermarked along with a product key recorded and trackable to each user. This makes enforcement easy. 3. The system will use asymmetric license keys so it's impossible to create key generators. 4. It must have advanced anti-crack measures that are home grown, secret, and take crackers a very long time to crack. Again, there will be NO paid version available. This will be free and support will be free. Sincerely, Wayne
FYI, if I understood you correctly. The author of the code can legally license their code in any combination of proprietary or open source. The restrictions on open source like GPLv3 come from those who use open source authored by someone else. In that case, they must open their source for anything they build based on it. This is confirmed through an attorney. Also, I have conferred with the FSF. Sincerely, Wayne
Anyway, let's close this thread, because we're getting off topic. The original thread was about releasing in C++ and that's history now. So I'll request it to be closed. Wayne
This is slightly OT, but how do you do this? I've never had to do it until now, and in reading up I see several ways of doing it. It seems the Java Native Interface might be the way to go but I thought I'd ask you in case you've used one method or another. - Andrew.