I had an idea concerning editing strategies. I am referring entirely to strategy logic not parameter choices. Currently, it is a bit of a tedious process. You have to close JBT, edit the strategy source file, recompile, start JBT then backtest and see how your changes fared.
What I propose is to allow strategy editing on the fly. Add in a basic text editor, perhaps some syntax highlighting... so far easy. Next step would be when you got o backtest, optimize, run the strategy whatever is required the strategy is simply compiled on the fly. This is actually not hard to implement. The challenging part comes in the fact that its a fairly substational overhall to the core interface of JBT. No longer will it know what strategies you have when the app starts. Instead It would have to read a specified directory for files. Then add those strategies to the strategy list... Then when a strategy is ran/bactested/optimized it would read in the file coresponding to that strategy name in the directory and compile it.. Thoughts? I think this would make strategy development a bit more rapid and easier to manage.. As now you are using everything from a centralized interface.. make a strategy change run it and see what happens.... Granted it will take a bit of overhall in the loading/ running of strategies as well as listing available strategies. Another benefit could be to allow users to just download the compiled JBT and design and run there strategies without needing to compile the whole project... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
