> JBT built-in web-server is great, but we wanted to add more features and we > build an enhanced JBT web interface. > > XML-RPC integration only covers real-time performance monitoring. It grabs > current performance of a strategy through its PerformanceManager class, and > expose it on an internal XML-RPC server (this is a kind of lightweight > web-service). > > Basically the enhanced web interface does: > > - Shows real time performance along with contract's real-time chart > (polling XML-RPC JBT server) > - Shows daily historical data from the trade database for each > strategy, so you can check at a glance which strategies are performing > well > on concrete time intervals. > - Shows strategy day details, where shows up all trades in a chart > (similar to JBT backtest chart) and a table with trade info (similar to > trade report). The graph doesn't contain indicators info yet > > >
Ok, I understand now, thanks. My take on this has always been that any kind of analysis should take place after the trading day. After all, the JBT startegies are meant to be fully automated, and this is how I ran JBT. There is no advantage of analyzing historical performance during the day if it can be done after hours, unless of course, you are using the real time performance to intervene manually. I do like your idea of showing strategy performance on different time periods (such as "last week", "last 3 months", and "last year"). -- 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.
