Wanted to come on here and paste a copy of an email I sent to Mary a while ago in the hopes that I can rally enough community support to make it happen:
We’ve been thinking a lot here about version control and team development. We could create a Git repository containing our Opto strategies, but it wouldn’t do us much good because Git doesn’t understand Opto’s files. However, I wonder if it would be possible for Opto to write some XML files when it saves charts/subroutines/strategies. So, for each subroutine with a .isb file, also write a .xml file. I’ve attached a sample XML file from the FetchFloat subroutine I wrote…
Here are some of the reasons:
- It would allow customers to use version control software because the version control software could "understand" the XML files.
- It would allow customers to do custom documentation/etc. using XSL and the XML files. For example, if we did something like auto uploading those XML files to a web server, we could parse and display that information in a variety of ways. Then, if somebody else needed to see something about the strategy I'm working on, he could go look at the web server, which would theoretically update every time I saved a chart/strategy/subroutine.
- I would allow me to provide documentation to non-developers (maintenance guys, etc.).
- It would provide much greater searchability than is built into Opto. I could search the XML files for any place across multiple strategies where a given subroutine is used, for example. Where all am I using any communication handle? Where all am I using a given command?
I’m really hoping we can make this happen. My job would be so much easier if we were able to develop better documentation for our Opto code, and I can’t be the only one who would seriously benefit from this. As a side benefit, I think it could lead to more open source Opto code and a more vibrant community of Opto developers.
Can we please make this happen?
Example XML file: https://www.dropbox.com/s/tg4fiimnospi6oo/FetchFloat.xml?dl=0