A simple 2D plotting library that outputs graphs to SVG that can be styled using CSS.

Hey, I am learning poloto API, and the Double iterator concept feels like it's not necessary?

Feels like the following might be enough?

    pub fn line_fill<N, I>(&mut self, name: N, plots: I) -> &mut Self
    where
        N: Display + 'a,
        I: IntoIterator<Item = [f64; 2]>,
        I::IntoIter: Clone,

Hi! Since updating from 6.1 to 7.1, the background colour of the SVG disappeared (outside the viewBox). In Firefox, I see the background-color property was removed from the root element. It seems like it's been replaced by a very large circle. Why is this?

To display additional information next to the name of the data, I've added an empty scatter. That however still results in a coloured bar above the text.

Is there potential for an option of removing the bar and or a separate method for showing info there?

Great project!

When adding data, long names are truncated in the SVG. This is due to the dimensions, I believe.

I'd be very grateful if the text would wrap or if it just wouldn't clip.

Great project!

I think this is a big trap that users can easily fall into.

Doing data.line("") seems innocent, but if data is a big Vec, then this line will clone a std::vec::IntoIter, causing the entire Vec to be duplicated in memory. The user should instead do (&data).line(""). However that very sneaky and easy to overlook. I'm thinking the safest thing to do is just forbid IntoIterator and require only Iterator to force the user to write data.iter().line("") as its more clear that the entire Vec will not be duplicated.

Right now, all the iterators are collected into a vec of vecs of floats of array size 2. Then they are also inserted into the document. So if the user is iterating through their own data structure, the same data can be in memory 3 times, which is wasteful.

Originally the iterators passed in were clonable and they were used twice. Once to find the bounds and once to normalize them. This reduces memory, but the user has be to aware to not do expensive calculations in their iterator because it will happen twice. To avoid user error, I opted to instead use the iterator once but collect the results. This uses more memory but the api can't be misused.

I think ideally, you'd run the iterators once and save them to a file while also finding the bounds. Then you would read the file again and normalize each float as you see them and write to svg.

I think the svg crate keeps the whole svg in memory. Another improvement wooluld be if the svg was written to file as you built it keep in memory only what you need to complete in finished tags.

I think this isn't that big of a deal though because ideally the user is not plotting a ton of data. This crate is meant to be used just to see broad trends

If you have just one giant point, for example, the intervals all print the same value (in scientific notation).

For example, do a scatter plot of just the point 30000000.0,30000000.0

It gives this error message:

the method `chain` exists for struct `poloto::build::SinglePlot<std::iter::FilterMap<std::iter::Map<std::ops::Range<{integer}>, [closure@src/bin/main.rs:500:30: 500:99]>, [closure@src/bin/main.rs:504:38: 514:26]>, std::string::String>`, but its trait bounds were not satisfied

only if the trait PlotIteratorExt isn't imported. This should be done in the macro.

When supplying an empty string to the functions here, no text is added to the legend. This isn't documented. I suggest making name an Option, which implicitly tells your users the name is optional.

Thanks for the nice and easy to use crate! I could not really find that out, but is it (already) possible to format the tick values? E.g., I have a graph that has the time that it already ran as number of seconds as x-axis and want to provide some function to a Formatter, that formats it as Xh Ymin Zsec.

Would it be possible to allow String input values on the x-axis, i. e.:

    let data = [
        ("Jan 2020", 3144),
        ("Feb 2020", 3518),
        ("Mar 2020", 3835),
    ];

Something like this:

use poloto::build;
// PIPE me to a file!
fn main() {
    let data = vec![[0, 0], [1, 2], [2, 3]];

    let a = build::plot("label").line(data);

    poloto::data(a)
        .build_and_label(("hello world", "x", "y"))
        .annotate(|w|{
            let point=w.convert_point([1,2]);
            
            let circle=hypermelon::build::elem("circle").with(attrs!(("x",point.x),("y",point.y)))

            let text_pos=w.request_text_position();

            let text=hypermelon::build::elem("text").with(attrs!(("x",text_pos.x),("y",text_pos.y)))

            circle.append(text)
        })
        .append_to(poloto::header().light_theme())
        .render_stdout();
}

In conjunction with defs and use tags so as to not repeat the r attribute. Need to wait for svg 2 spec if want to keep allowing user to change radius with css