Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Half Streaming window for Strategy output #34

Open
setkeh opened this issue May 10, 2013 · 4 comments
Open

Half Streaming window for Strategy output #34

setkeh opened this issue May 10, 2013 · 4 comments

Comments

@setkeh
Copy link

setkeh commented May 10, 2013

Hey
i just got a strategy running and its doing well i love this tool and how simple it makes life :D

Though it would be beneficial to cut the streaming window (the one Down the bottom) in half and use the second half for the output of strategy and client messages instead of having them jumbled in the stream to make reading a lot easier :D

http://screenshots.setkeh.com/goxtool.png << for example :D

@setkeh
Copy link
Author

setkeh commented May 10, 2013

Sorry I dident realise there was another already like this :P you can close this one sorry

@v3nz3n
Copy link

v3nz3n commented Jul 12, 2013

This is probably the first thing that sprang to mind when I started using goxtool. I think a lot of people want this functionality. However, splitting the console window into smaller parts is trivial, but getting strategy messages in there is not! After 2 months of customising and coding my strategies, I finally got round to outputting my strategy messages to the curses GUI instead of watching my logs for alerts and status info :)

The mechanism I implemented is outlined here: #25 (comment)

It uses ZeroMQ and this works very well for me, but there may be other solutions which I'd be interested to hear about - not because ZMQ is not brilliant for this exact usecase but because I am interested to learn any and all ways of doing things with Python.

@prof7bit
Copy link
Owner

The reason why it never came to my mind to implement this is that from
the very beginning when I started developing this I always had a
separate terminal window open with a

tail -f goxtool.log | grep Strategy

so I never really had the need to implement the second scrolling
window. Also my terminal width on my old laptop is very limited and I
had no idea where to place this second scrolling window (there is not
enough room at the right side).

Maybe I could implement a keyboard shortcut to toggle between general
log and strategy log or between general log and a custom filter. Since
the debug signal also transmits a reference to the sender of the debug
message (from the instance one can derive the class name and the
module name) it should be possible to filter for individual
strategies.

@v3nz3n
Copy link

v3nz3n commented Jul 13, 2013

Filtering on the signal_debug() transmitted reference is a simple and effective way of getting Strategy messages into an additional curses window created in goxtool.py or, as you suggest, just toggling its output to the existing Console window. Not quite sure what the transmitted reference content is, so please elaborate on that.

btw, I fixed the link in my comment above to point at the correct issue and comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants