Thank you, Ville, for your valuable feedback and the resources you provided—they are indeed helpful! I look forward to having a more in-depth discussion on these topics once I delve into them further. At the moment, I am focusing on the jittering and break axis features.
If you’re interested, your contributions to any of the features would be greatly appreciated. However, please don’t feel pressured; any form of assistance, including discussions like this via email, is welcome. Wishing you a wonderful day! Thanks *Ovilia* On Thu, May 30, 2024 at 10:06 AM Ville Brofeldt <ville.v.brofe...@gmail.com> wrote: > Hi all, > > This is truly exciting! A few thoughts from me: > - Jittering for categorical data ( > https://github.com/apache/echarts/pull/19941) is IMO really useful, and > would be a neat addition! > - I've always had a thing for Violin plots, and I'm super stoked to see it > on the backlog. I've seen a few good implementations of them previously, > namely ggplot2 and Seaborn, so it's probably a good idea to try to get > feature parity on those. > - Aligning axis labels with actual data ( > https://github.com/apache/echarts/issues/19605) is something I've heard > many people request over the years, and I've seen many workarounds to > implement this, with varying success. So having this functionality natively > would be very beneficial. > - I think adding support for KMB style formatters ( > https://github.com/apache/echarts/issues/19565) is a really common need, > and one that would be really neat to support natively. I think Grafana > probably has the most comprehensive set of these types of formats, so > they're probably a good benchmark to go by: > https://community.grafana.com/t/grafana-unit-for-mb-gb-etc/68495/2 . > While on this topic, being able to customize tick intervals, where they're > are not based on base 10, (1000 = 1k, 2000 = 2k etc), but where the ticks > would be based on something else, like kilobytes (1024 bits = 1 kilobyte, > 2048 = 2 kilobytes etc) or minutes (60 sec = 1 min, 120 sec = 2 min, 3600 > sec = 1 hour, 7200 sec = 2 hours etc) is also something that would make > these types of charts more intuitive. IIRC, d3 has functionality for this, > so there may be good examples there to go by. > > Anyway, this is really cool, and I hope I'll be able to be able to > contribute to this release. > > Ville > > > > On May 20, 2024, at 10:56 PM, Ovilia <oviliazh...@gmail.com> wrote: > > > > Apache ECharts 5.0 was released in December 2020, and now it's time for > the > > next major version: 6.0! > > > > We are excited to announce that we plan to release Apache ECharts 6.0 in > > the first quarter of 2025. We have put together a list of features [1] > that > > we intend to include in this upcoming release. > > > > We would love to hear from you about which features you are most excited > > about and looking forward to using. Please share your thoughts and let us > > know what you think! > > > > It's important to keep in mind that most of our contributors work on > > ECharts in their free time, so some features may take longer to implement > > than others. If you are passionate about a particular feature and would > > like to help us bring it to life, we warmly welcome you to join our > > community and contribute to the development of ECharts 6.0! > > > > [1] https://github.com/orgs/apache/projects/327/views/2 > > > > Thanks > > > > *Ovilia* > >
