skie1997 commented on issue #29886: URL: https://github.com/apache/superset/issues/29886#issuecomment-2316821651
> Hi! Thank you for the proposal! VisActor is very slick looking. I suppose I have a few initial questions to ask: > > 1. Are you proposing this as a _replacement_ for ECharts, or to _augment_ existing ECharts plugins? > 2. Are you proposing putting these in core Superset, or do you want to make an external ([third party](https://github.com/apache/superset/wiki/Superset-Third%E2%80%90Party-Plugins-Directory)) set of plugins people can add to their Superset instances? > 3. Do you intend to contribute this code, or is this a request for engineering support from the Superset community? > 4. Is there any sort of document comparing/contrasting VisActor with ECharts? That might be helpful to assess the situation > > It's also worth saying that there are perpetual discussions around how to make the process of developing visualization plugins simpler. I don't think that will happen immediately, but it is discussed from time to time. Only mentioning it since when the day comes, existing plugins might need additional rework to accommodate a (hopefully simpler) API. 1. Compared to ECharts, as previously mentioned, our VisActor product not only includes the standalone [VChart](https://www.visactor.io/vchart/example) chart library but also includes the [VTable](https://www.visactor.io/vtable/example) table library, [VMind](https://www.visactor.io/vmind) intelligent components, and VStory narrative components. These visualizations encompass a complete ecosystem of visualization rendering, so we expect to develop three visualization plugins on par with ECharts based on VisActor, rather than as a supplement to ECharts. 2. We hope to include high-frequency chart types or our unique capabilities into the core of Superset, such as [chart annotations](https://www.visactor.io/vchart/demo/marker/mark-line-total-diff). Low-frequency chart types or component types can be placed into third-party plugins. Of course, this depends on your product definition of Superset. 3. Our team has a complete set of visualization engineers, and we are confident in participating in and contributing to Superset. During this period, we hope to have good communication with the Superset team and to listen to your development suggestions. 4. We have an internal comparison document with ECharts, which involves descriptions of chart types, feature capabilities, cross-platform compatibility, performance, package size, and other aspects. We will synchronize it with you after sorting it out later. Please review and let me know if you need any adjustments or additional translations! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
