Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
StockSharp has taken a back seat for the time being while I complete my switch from NT to MultiCharts (lots of indicators and strategies to recode). S# is still my ultimate goal for my primary platform.
Can you help answer these questions from other members on NexusFi?
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
Ok, after spending hours digging through code, I have learned that the WPF learning curve is STEEP! In trying to figure out how some components work, I get lost when I'm 7+ classes deep.
Anyone know of a breadcrumb style debug viewer for XAML/WPF?
I think it is a wrong way. Just use S#.API as a user. When you completely understand all common use cases (send transaction and receive market data) you can try to change something in core. For now change XAML components (for what, btw?) is wasting time. Most of all trading robot - one window with several buttons. Pretty easy for GUI develop.
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
I am actually in the process of just rolling my own instead of trying to mold hydra or studio into what I want. A responsive and robust version of studio would be great but it's so complex that I think it will be easier and faster to make my own from the API.
I will continue to post here with relevant S# information.
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
Still working on getting connectors working but here is a test on a real time charting built using SciChart with a random walk generator for data. I tested up to 1,000,000 bars and it chugged right through with virtually no slow down or lag. This is a 5,000 bar test
Runtime is already localized and all errors/warning/messages are on english now. But comments (in tooltips) still on russian only.
To use S# you should to good knowledge of C#. Trust be - it is at the first. Many guys that use S# now tell me that they almost never use doc because API structure is well formed and logically. Just as example. 2 month ago I was working with chinese trading gateway. There was almost on hieroglyphs. Nothing was helped me (even google translate). Thanks God there was good developed library with a samples. As a programmer I will understand logic very quickly, without any doc.
C# is also has a docs and books. But it so intuitive you do not need any documentation.
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
I have reached out to several futures.io (formerly BMT)'ers and a few have expressed interest in contributing to this project (a big thanks to those people). My goal is to make an application which a multitude of trading styles could take advantage of while remaining open source. Just with the initial small group, there is already a wide array of feature interests. My thinking is that the more people contribute and/or extend this platform to what's important to them, the more everyone benefits and the more feature-rich it becomes. If anyone else is interested in contributing, please PM me. The only caveat is that since this is very much still in development stage, you'll need to be somewhat proficient and comfortable in the dev environment. I'm no salesman so that's my best pitch....sales tie is coming off and pocket protector going back on
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
I've been having trouble getting the connectors to work with anything other than simple example programs. I managed to recursively get all of the connector assemblies and instantiate them programatically. This will allow new connectors to be created, compiled, then just dropped in a folder with no changes to the program's code. The new "Connector" tab is not the final UI implementation but it'll due for now.
Real time data should be working soon
@mattz I wanted to say thanks for helping with multiple connector test credentials. That allowed me to test more than just IQFeed to ensure as much compatibility as possible from the beginning.