Better yet would be to keep all columns in the output code, but run the results through a user-defined XSLT to eliminate the ones they don't want.
On Tue, Sep 1, 2009 at 1:35 PM, nonlinear5 <[email protected]> wrote: > > > Im looking forward too see next release.... Maybe you should think of > > the way of alowing easy configuration of columns in the actual report > > as well.... Say I don't want to see Max dd, but I want to see some of > > my custom performance measures. I would be wery keen to be able to do > > that. > > > > This is very straightforward, just add two lines of code in > StrategyReportManager.java, one to add a header, and one to add > content. It's certainly possible to build a "Report Column Chooser > GUI" in JBT, and in that case no code modifications would be required. > However, I think that would be an overkill. I am not trying to build a > highly customizable product which targets hundreds of thousands users, > such as TWS. One of my fundamental design principles with JBT has > always been a light-weight, well defined, and narrowly focused > framework. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en -~----------~----~----~----~------~----~------~--~---
