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

Re: Omega or Traderware???



PureBytes Links

Trading Reference Links

For the record, Traderware was programmed exclusively in Microsoft Visual
C++. The only Visual Basic aspect of the program was the ability to write
systems/indicators etc., in a VBScript type language and this capability was
an add-in package.

Actually, TraderWare probably could have benefited from using VB for the GUI
and VC++ for the data-intensive stuff. If you were familar with TW's GUI you
would understand what I mean. However, the crux of TW's performance problems
do not stem from the data crunching, but rather from extremely ineffecient
screen drawing.

Patrick White
----- Original Message -----
From: "David Rosenthal" <davidrnews@xxxxxxxxxxxxx>
To: <I4Lothian@xxxxxxx>
Cc: "Omega-List@xxxxxxx Com" <omega-list@xxxxxxxxxx>
Sent: Sunday, March 25, 2001 6:05 PM
Subject: RE: Omega or Traderware???


John,

Just one comment - from what I can tell from this thread, Traderware was
built (at
least primarily?) with Visual Basic.  VB is a decent way to build a database
front-end, but it is simply not an appropriate tool to create a real-time
trading
platform.  The comments on this thread re performance and bug problems are
consistent with VB's performance and memory-management problems.  To the
degree that
the Traderware code base is Visual Basic, the chances of evolving it into a
truly
useable piece of software are greatly diminished - and this really raises a
red flag
about the judgment of the original developers.

If the developers had wanted to avoid C++, they would have been much better
off
using Delphi (which apparently is what Ensign is programmed in) or perhaps
PowerBasic (although I haven't used that tool and cannot really comment on
its
capabilities).