- ago
Not sure if this is an ask for a feature or for the best practices recommendation, but sometimes I wish I had a better way to track changes on a strategy.

Right now I tend to create a new copy of strategy whenever I do major changes, but having a version control (either internally or through integration with external tools) could be quite helpful.

If there is enough interest, It seems that Git has some documentation on how to implement Git integration from within an application -
https://git-scm.com/book/en/v2/Appendix-B%3A-Embedding-Git-in-your-Applications-Command-line-Git
https://github.com/libgit2/libgit2sharp/
8
959
6 Replies

Reply

Bookmark

Sort
Glitch8
 ( 7.81% )
- ago
#1
Hmm that is indeed interesting, maybe we can eventually integrate with GitHub for some version control right in WL7.

There's a C# library we could use too ...

https://github.com/libgit2/libgit2sharp
1
- ago
#2
Would it be possible to add this to the Wishlist? I did not set the proper tag initially since I wasn't sure if there already a way to use version control
0
- ago
#3
You can already do it if developing compiled strategies in Visual Studio (Code)
https://code.visualstudio.com/Docs/editor/versioncontrol
https://www.wealth-lab.com/Support/ExtensionApi/StrategyLibrary

If you prefer to stick to Wealth-Lab's Editor or other strategy types, you can leverage Dropbox file versions by pointing it to the WealthLab7\Strategies folder. And if you want to get serious you can do the same with a version control system like Subversion or Git client installed on your PC.
1
Glitch8
 ( 7.81% )
- ago
#4
I tagged this as a FeatureRequest for proper tracking.
1
mjj38
- ago
#5
The ideal solution would allow you to create, modify and check-in(versioning) strategies without having to compile a dll and restart WL7.

Perhaps you could replace the built in code editor control with Microsoft Code or Visual Studio Community. Or approach it like NinjaTrader where you have the option to use Visual Studio as your editor (which lets you check the code into a code repository for versioning) but WL7 would still compile the strategy (which avoids the need to compile and restart WL7). I believe though you save the strategies as text or xml which would make that more difficult.

Currently I use the built in editor while developing a strategy and move it to a Strategy Library when completed or going live.
0
Glitch8
 ( 7.81% )
- ago
#6
Interesting, the Strategy could contain a link to the source code file name rather than the actual source code.
1

Reply

Bookmark

Sort