|
Keith,
Just because XML can be used to express a complete database does not mean that you would have to know all that to edit a simple text file like what TJ is suggesting. As I already pointed out, a text file is something that can also be generated in AFL. It would not take more than TJ or one knowledgeable user to write an AFL #include that could edit or create the file based on the idea of a HideColumn() function that could do that specific function. I dare say a lot easier than all the effort going into the concerns being expressed here.
I am sure if TJ wrote exactly what was requested, someone would complain how come it can't also do X when Y condition happens and expect TJ to rewrite it and re-document it...
Too much emphasis is being placed on ready made narrowly defined high level functions and not enough on low level enabling functionality that gives the ability to produce many more useful functions, and tailor them to specific needs.
The low level AFL control of AB is what I am starving for. Likely 10 times easer for for TJ to code, but 10 times more useful in the long run. They are the seeds that grow the plants. I would rather have 10 tomato plants than 10 tomatoes.
BR,
Dennis
On Jan 20, 2009, at 11:39 AM, Keith McCombs wrote:
Dennis --
TJ in his posting said, "XML is plain text file editable with Notepad or any editor". So, I assume that he expects me as a user to not just copy verbatim a file which he has provided, but to somehow modify it.
I just looked up XML on Wikipedia. The description is extensive. I also looked for XML books on Amazon. The first one in a multi-page list is called "XML for Beginners", and is 1080 pages long.
Also, I can't see how "HideColumn" would clutter up my formulas any more than AddColumn, SetOption, or any other function does now. When the clutter gets to much for me, I can always use #include.
-- Keith
Dennis Brown wrote:
Friends,
I for one do not care if additional flexibility is crated by XML files, plain text files, DLL files, JScript, AFL includes, OLE... blah blah blah.
It does not require learning a new language to use something that was written in a different language.
I do not personally use anything but indicator mode for my systems, so I am not biased for or against this particular item. However, I have a keen interest in similar solutions proposed for other functionality that I do use, and I am all for it.
Give me any "reasonable" way to get additional functionality into AFL. If a reasonable way is available that can be expressed with an include AFL file, it does not matter the details of the language, because all that can be hidden inside a function or include.
For example, If a function required a JScript language to set certain s ettings via ActiveX who cares. Just give me the script and I will use it. I don't have to even know JScript or ActiveX at all to use it. Wrap it in an AFL function and stuff it in an include with a bunch of other nifty functions and I would be quite happy.
Need an XML file to control something, fine! Make an AFL program the takes parameters and generates the XML text file and give it away to everyone, or generate it on the fly with an AFL function that takes all the parameters and stuff it into an include.
We have a wonderful tool with AB and AFL. When TJ offers to expand it to your needs in a way that meets his also... jump at it!!!!
I only wish I had more opportunities to do that with my requests.
BR,
Dennis
On Jan 20, 2009, at 7:48 AM, Tomasz Janeczko wrote:
XML is plain text file editable with Notepad or any editor. It is easy editable, as compared to binary settings files
used for .ABS (AA settings).
As to suggested "HideColumn" AFL function suggested by Herman, that would not be best, IMHO, because it will clutter every formula
(as I guess people would want to hide unneeded columns for every backtest they run) a nd make it slower.
Best regards,
Tomasz Janeczko
amibroker.com
----- Original Message -----
From: Steve Dugas
To: amibroker@xxxxxxxxxps.com
Sent: Monday, January 19, 2009 11:18 PM
Subject: Re: Re[2]: [amibroker] Re: How NOT to show all the built-in metrics in the backtester?
I am glad you liked it. 8 - ) I don't know anything about XML or how that would work, but I would guess that most users would prefer not to write all their own stat functions from scratch, so perhaps your XML idea ( which sounds more flexible ) might be appreciated by more users?
Steve
----- Original Message -----
From:& nbsp;Tomasz Janeczko
To: amibroker@xxxxxxxxxps.com
Sent: Monday, January 19, 2009 3:46 PM
Subject: Re: Re[2]: [amibroker] Re: How NOT to show all the built-in metrics in the backtester?
That's not bad idea :-). Either this or XML config file that you can manually edit would be solution for advanced users.
Best regards,
Tomasz Janeczko
amibroker.com
----- Original Message -----
From: Steve Dugas
To: amibroker@xxxxxxxxxps.com
Sent: Monday, January 19, 2009 8:17 PM
Subject: Re: Re[2]: [amibroker] Re: How NOT to show all the built-in metrics in the backtester?
Perhaps, if TJ doesn't plan on implementing individual column control, a much simpler feature might be just a switch allowing us to turn all columns on or off. Speaking for myself, I have written my own code for many of AB's stats, as well as other stats, originally for use in my charts but now I have added them to the backtest results also via the CBT, so I would be happy to just turn off AB's built-in stats ( would save a lot of scrolling and moving columns around ). Anyway just a thought, I don't know how others feel about it...
Steve
----- Original Message -----
From: Herman
To: Tomasz Janeczko
Sent: Monday, January 19, 2009 4:43 AM
Subject: Re[2]: [amibroker] Re: How NOT to show all the built-in metrics in the backtester?
Column control was suggested long ago and I still think that being able to select, by disabling from afl (of course NOT using check boxes!) would be a good idea. I, without exception after each and every Backtest, have to use the scroll bar to see my columns of interest. I greatly miss being able to add/suppress columns without the use of the CBT.
Since in the back tester column layout is fixed a simple afl function like HideColumns( 3, 2-9, 15 ) would do the job.
A alternate sol ution would be for Tomasz to publish a CBT backtester on the KB that would mimic the standard BT but provided the above option.
... while on the topic of reports ... it would also be nice to have the AddSummaryRows() enabled for portfolio backtests :-)
We have a wonderful product but there are always more wishes ;-))
Best regards,
herman
Sunday, January 18, 2009, 7:34:01 PM, you wrote:
|
>
|
Hello,
"that no columns be displayed by default, and that the all columns and their widths be specified programmatically and/or in a settings page."
Since there are 46 build in stats, implementing your idea means 46 new checkboxes
and 46 edit fields (to define widths)
That's 92 new controls (to be placed on dialogs , docs and so on).
More settings -> more problems for beginners -> Lower sales. Plus more support
(every beginner asking "where is K-ratio", and "why there are no metrics produced?"
and "why there are so few metrics?")
From my perspective it would not be improvement. Just the opposite.
Best regards,
Tomasz Janeczko
amibroker.com
----- Original Message -----
From: Keith McCombs
To: amibroker@xxxxxxxxxps.com
Sent: Saturday, January 17, 2009 10:48 PM
Subject: Re: [amibroker] Re: How NOT to show a ll the built-in metrics in the backtester?
Ozzy --
Yes, at this point it seems to be easier to live with all the extra columns than to learn how OLE works.
I believe, long ago, before the suggestion page was implemented on AB site, that I suggested to TJ that no columns be displayed by default, and that the all columns and their widths be specified programmatically and/or in a settings page. Obviously the suggestion was not implemented. IMHO, it would be a significant improvement over the present system.
I did get your previous response. But I understand your concern. I had to post my request three times before it finally went through. My two others were on 1/14, 1:04am and 1/16, 1:39am. Just recently these were finally delivered. Yahoogroups can be unbelievably slow at times.
-- Keith
ozzyapeman wrote:
Seems my response did not go thru. Reposting:
Keith - did not get around to implementing any OLE. Living with the
extra columns for now. But if I do write any code for it, will post it
here in the future.
--- In amibroker@xxxxxxxxxps.com, Keith McCombs <kmccombs@xxx> wrote:
>
> Ozzy --
> Any chance you have already gone through the pain of implementing the
> appropriate OLE code. If so, would it be possible to share it and some
> brief instructions on how to use it? That would be greatly appreciated.
>
> Thank you.
> -- Keith
>
> ozzyapeman wrote:
> >
> > I asked this Q on the board a few weeks ago, and the consensus was
"no".
> >
> > But you can export the report using OLE and run an exploration showing
> > only the columns you want:
> >
> > < a class="rvts15" href="">"http://finance.groups.yahoo.com/group/amibroker/message/132540" style="font-size: 11pt;color: rgb(0, 0, 255);font-family: tahoma;text-decoration: underline;">http://finance.groups.yahoo.com/group/amibroker/message/132540
> > <http://finance.groups.yahoo.com/group/amibroker/message/132540>
> >
> > --- In amibroker@xxxxxxxxxps.com
<mailto:amibroker%40yahoogroups.com>,
> > "huanyanlu" <huanyan2000@> wrote:
> > >
> > > Hi,
> > >
> > > I just learned to add some custom metrics into backtester. But
then I
> > > find that some of the built-in metrics in the backtester are not
> > > important in my way of analysis. So is there a way to show only
some of
> > > the built-in metrics , together with my added custom metrics ?
> > >
> > > According to the help file, it seems that the backtester object can
> > > allow you either show all the built-in metrics, or not show any of
> > > them .
> > >
> > > Thanks for any help
> > >
> > > Huanyan
> > >
> >
> >
>
|
|