[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Quant Studio



PureBytes Links

Trading Reference Links

Mark ,

Thanks for the message
































I program to 7.2 via COM now. I can write C++ and I also interoperate with 
TS and c#/.net via my own mechanisms.
































TS is however still not a real API- you can only use script to invoke the 
COM code. There is no access to the BULK of the API- you cannot fetch data- 
create windows, automate much of anything- except by using global memory and 
other things like that to 'share' data. There is no access to a library 
style API with most of TS. No matter how you cut it- TS API is NOT much 
exposure into TS. There is NO way to have true source control. There is a 
WEAK debugger (I am used to Visual Studio style debigging (or borland's, 
etc).
































It is not a programmers programming environment. It is a script environment 
with some add-ons that allow you minimal access to small portions of the 
entire hidden TS API's.
































You can do lots with TS- but I am sure that you are all aware of the 
limitations.
































-Chris
































































From: "Mark Simms" <mar.ko@xxxxxxxxxxx>
Reply-To: <mar.ko@xxxxxxxxxxx>
To: "chris donnan" <chrisdonnan@xxxxxxxxxxx>
Subject: RE: Quant Studio
Date: Sun, 29 Feb 2004 20:48:02 -0500

Chris  - someone told me that TS 7.2 has a good break-point debugger
now.....
and they have really cleaned-up the DLL API and made it totally COM-based.
Which version were you making a reference to ?

> -----Original Message-----
> From: chris donnan [mailto:chrisdonnan@xxxxxxxxxxx]
> Sent: Sunday, February 29, 2004 12:24 PM
> To: omega-list@xxxxxxxxxx
> Subject: Re:Quant Studio
>
>
> No offense Max- but spoken like someone who has never had to
> REALLY program
> something non-trivial. Having a robust debug process and tools cannot be
> ignored. When you are dealing with a non-trivail applicaiton - with out
> logging and debugging (yes- with step-throughs) is NECESSARY. I again 
can
> say this as I manage several enterprise class develpers and am myself a
> software developer for some time in large enterprise environments
> where the
> work is non-trivial.
>
> TradeStation simply is not a robust development tool- that is a
> fact. It is
> not debatable that TS is NOT a real development environment. You have no
> access to a compiler- you have no REAL api access (TS's api that
> is) - the
> debugger is POOR. There is really no advanced IDE like feature in
> TS at all.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> I just wanted to make it clear - TS is a great TOOL - but it is
> far far far
> from an enterprise programming environment.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> -CD
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> PS- Again I say - No offense intended.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> >From: Max Pierson <maxpi_44@xxxxxxxxx>
> >To: Omega List <omega-list@xxxxxxxxxx>
> >Subject: Re:Quant Studio
> >Date: Sat, 28 Feb 2004 19:05:40 -0800 (PST)
> >
> >It never fails to amaze me that people would want
> >to single step their code when they have the
> >visual debugging tool of all debugging tools, the
> >chart!! Write your code as an indicator and step
> >through bar by bar and check that it is working!!
> >Use the Data Window!! Much, much better than
> >single stepping through code and making
> >assumptions about what is going on (and blaming
> >Tradestation when it hiccups)
> >
> >Max
> >
> >================================================
> >....couldn't disagree more. When I have program
> >in
> >C, I can at least single
> >step through the code to see how and where bugs
> >are occuring. Try that with
> >TS. It is amazing to me that people can even talk
> >
> >about a programming
> >environment without having a debugger to "single
> >step" through the code. I
> >can give you five different situations where TS
> >is simply doing buggy things
> >(as of TS2000i.)
> >
> >
> >=====
> >"The race may not always go to the swift nor the battle to the
> strong, but
> >it is the way to bet"
> >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>