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

1.0 #3

Open
3 of 17 tasks
milliams opened this issue Mar 13, 2018 · 4 comments
Open
3 of 17 tasks

1.0 #3

milliams opened this issue Mar 13, 2018 · 4 comments
Assignees
Milestone

Comments

@milliams
Copy link
Owner

milliams commented Mar 13, 2018

This is an overview issue to track all the feature we want before 1.0:

  • lots of plot types
  • legends
  • output plots in may formats
    • SVG
    • ASCII
    • PNG
    • 3D format
  • different projections
    • normal 2D plot
    • 3D plot on a 2D page
    • map projections
  • dual y-axes
  • combined (e.g. scatter plus histogram) plots
  • easy to get own data into plots
  • extensible with new output formats and projects
  • custom axis formatting
  • custom styling
@milliams milliams added this to the 1.0 milestone Mar 13, 2018
@milliams milliams self-assigned this Mar 13, 2018
@ManifoldFR
Copy link
Contributor

What about adding PNG to the list of output formats ? I actually don't know how some of the PNG crates work

@faulesocke
Copy link

What do you think about adding the image crate and extending the View trait with some "to_image" method?

@faulesocke
Copy link

Also annotations (text with pointers towards data points) would be a really nice feature!

@Proksima
Copy link

I might be tempted to contribute in the future to add candle bar plotting available, but I notice the axis is defined with floats while plotting of time series requires some notion of time and duration.

3 questions:

  • Is time series support something you plan to add soon? (so I do not start working on it to see it committed before I'm done...)

  • Between introducing a Coordinate (and maybe an Interval too) trait and having multiple types (integer types, f32, f64, potentially chrono::NaiveTime, chrono::NaiveDate and chrono::NaiveDateTime (behind a feature gate) implement them to potentially get to an abstract Axis<Coordinate> or just using a UNIX timestamp turned into an f64 to represent time-series' coordinates, what would you prefer?

  • Would it be risky for me to start working on those in a few weeks? (e.g. is there any big refactoring planned?)

Otherwise, I am really happy to see a decent-looking crate for plotting appearing. I was actually thinking of making my own soon (I am studying algorithmic trading) and I feel this will save me a lot of time.

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

No branches or pull requests

4 participants