RE: [GT] BuySellArrow misnomer

["Weigert, Thomas" <weigert AT mst.edu>]

Please see below....

> -----Original Message-----
> From: Robert A. Schmied [mailto:ras
AT
acm.org]
> Sent: Wednesday, June 11, 2008 1:43 AM
> To: devel
AT
geniustrader.org
> Subject: Re: [GT] BuySellArrow misnomer
> 
> 
> maybe a corrective action is called for (one or more of)

The most important thing is that users don't get confused between the
"Buy/Sell" that, say, backtest.pl, would propose, vs. the "Buy/Sell" in
graphics.pl. These arrows are still very useful.

Personally, what I would have done is give BuySellArrow two signals as
arguments, rather than a SY. That way, it is clear that it just pictures
the output of these signals. The SY just is a holder for these two
signals and serves not much further purpose.

The other option would be to change terminology and not call the
SystemManager object a SY. 

> a) more clearly explain it in the graphic.pl pod
> b) change directive to LongShortArrows (but still accept BuySellArrows
>    but depreciate it by removing the pod references)
>    naturally that implies a name change to
> GT/Graphics/Object/BuySellArrows
>    too.
> c) correct BuySellArrows by requiring a system description that
> includes a close strategy (will that work now if the argument is
such?)

I think this will involve much more evaluation, in a sense, one has to
run the core of backtest.pl then.

> d) other to be determined
> 
> humm -- does VotingLine work similarly?

Yes, same issue for voting line.

> 
> ras
>