It is possible to waste years debating Java vs. Microsoft or VB vs.
C++ etc., and the debate doesn't get you anywhere. I view this forum
as a way to share code, learn from what others are doing and perhaps
use as a lobbying jumping off point to get the IB developers to
prioritize important API improvements / bug fixes. I don't want to
cooperatively work on a project to develop a killer app, and I'd
rather the list didn't get hung up in that either. I have my own app
and have no interest in being a cog in the next open source project.
I develop my trading software to fill a need in my trading. I'm sure
there are many others who do the same thing. Programming isn't my
primary focus, trading is. To the extent that I can improve my
trading by programming the IB TWS API, I will do it. To the extent
that I can offer code and help to others traveling the same path as
me, I will do it. To the extent that I can get help from professional
programmers to meet this end I am appreciative.
--- In twsapi@y..., "dtkamp" <dkamp@e...> wrote:
Thanks Scott for getting responses.
Seems like way to go in a cooperative project is to get
participants
to use .NET framework, where language choice is least likely to
cause
problems, and C/C++ can be used to generate/process any necessary
unmanaged (= not under control of .NET runtime) or legacy code. I
think that will get us the most bang for the buck with repect to
our
individual uses of the code (but perhaps not the most bang if
someone
wanted to sell and distribute a cross-platform app - not a high
priority for me - but makes sense for IB's use of Java in TWS).
So what do the other 180 people up here think of what I just wrote
with respect to development platform selection for such a
cooperative
effort? (We can do a separte survey to figure out who's actually
interested in such a project. Am just fishing for .NET objections
to
start with.) Thanks!
