For me, I think editing the strategy on the fly is trival. I find a more important and easier thing to implement. After optimization, we have to copy the parameters into our codes and recomplie. I propose to seperate the parameters from the source codes, but read it from the saved optimization file. This will save us a lot of time. After optimization, what we need to do it clik the optimal parameter set, and the JBT will use new selected parameters.
On Sep 9, 7:19 pm, nonlinear5 <[EMAIL PROTECTED]> wrote: > OK, I understand this better now. While I see the potential benefit of > saving a few clicks and of easier JBT set up and deployment, it seems > to me that the actual savings in time would be negligible, considering > that they would be offset by presumably less productive Java > development in some sort of a custom editor where it would be much > more error prone. Granted, Java would still report syntax errors, even > if compiling is done by reflection, and you could correct the errors, > but this entire concepts sounds a little strange to me. It's almost > like reinventing an IDE. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
