Empty configuration over full configuration

[pmairoldi]

So I've finally integrated some charts into my project using this but I am finding that out of the box charts are configured too much. There is a chart description, a legend, and a bunch of other stuff that the simple use case would not need. I think it might be a good idea to rethink of what "needs" to be included in a base chart.

This would reduce the need for turning everything off that I don't need and just turn on things I want. I think that everything off be default would be way better and reduce the amount of code someone would have to write to get something they want on screen.

What's everyone's thoughts on this?

[danielgindi]

@PhilJay

[liuxuan30]

Turning legends, desciption off by default is fine, but sometimes, when I see additional stuff I don't expected, I would take a look and learn something new. It's always good to find out some small features in the chart :)

[alinoz77]

Maybe make sense to have a turn all off/on method.

[pmairoldi]

@liuxuan30 if you are learning new things about the library by mistake wouldn't that mean that the documentation is lacking?

[liuxuan30]

@petester42 I read the document from android WIKI, but I now get used to read code directly... Thanks to Swift, it's easy to read. enhancing WIKI is also a good choice.

[pmairoldi]

closing due to inactivity.