There should be a *defined and user friendly* way to export and import coded strategies (and even building block strategies).
I do some coding work for other people. They should be able to send me their scripts,
and to read the scripts I send them by mail.
I know it is possible to copy these scripts to/from the strategy folder but I consider this hard to do for Mr. Average User.
I do some coding work for other people. They should be able to send me their scripts,
and to read the scripts I send them by mail.
I know it is possible to copy these scripts to/from the strategy folder but I consider this hard to do for Mr. Average User.
Rename
Agree, let's get this one upvoted so we can see it implemented quickly!
In WL6, strategies were saved in XML format to clearly separate their parts. Why wasn't that done in WL7?
Really, if there were an import/export (de)serializer class that separated the WL7 strategy parts automatically, then you wouldn't need the XML format. But without such a class, you do. But employing XML for strategies as WL6 did isn't a bad option. The .NET framework already has an XML serializer/deserializer to separate everything.
My only gripe with XML files is that they are verbose. But Windows has built-in utilities that can compress/decompress these into binaries transparently.
Really, if there were an import/export (de)serializer class that separated the WL7 strategy parts automatically, then you wouldn't need the XML format. But without such a class, you do. But employing XML for strategies as WL6 did isn't a bad option. The .NET framework already has an XML serializer/deserializer to separate everything.
My only gripe with XML files is that they are verbose. But Windows has built-in utilities that can compress/decompress these into binaries transparently.
Because I needed to make significantly changes in many areas to distinguish the product from Fidelity-owned WL6.
XML is in the "public domain" such that Fidelity cannot claim ownership to it. I know; I'm a computer engineer dealing with "open standards" (like XML) all the time.
As long as you're using open standards, there shouldn't be a problem. You can rearrange the XML dataset some just to make the WL6 XML files organized differently (incompatible) from the WL7 XML files. But Fidelity cannot exclude you from using open standards of any type.
If your copyright attorney told you couldn't use open computer standards, you need to find a new attorney.
As long as you're using open standards, there shouldn't be a problem. You can rearrange the XML dataset some just to make the WL6 XML files organized differently (incompatible) from the WL7 XML files. But Fidelity cannot exclude you from using open standards of any type.
If your copyright attorney told you couldn't use open computer standards, you need to find a new attorney.
I know. It was just an area I decided to do differently this time around. Maybe a bad decision but nobody's perfect \o/
QUOTE:You can still correct this, and I would.
I know.
But change the XML dataset organization (arrangement) just enough to make the WL7 XML incompatible with WL6 XML if you're concerned. There are some things I don't like about the WL6 XML format (which needs changing), but that can be discussed in another topic.
Here's an idea which might be the simplest way to solve Mr. Average User's problem:
An Import/Export button would open the Strategies folder and show the tree in Explorer where the user would either copy or paste the .TXT file, and in the latter case WL7 would rebuild the tree on success.
An Import/Export button would open the Strategies folder and show the tree in Explorer where the user would either copy or paste the .TXT file, and in the latter case WL7 would rebuild the tree on success.
With the rapid completion of the feature request related to controlling the chart and pane properties from a strategy, I'm activating this request for development for Build 14!
Your Response
Post
Edit Post
Login is required