will see if I can make it work...

It seems the code is very well organized, and porting should be easy!

hello. I see there are touch event related code, is it exposed as part of the Viz DSL?

hey, I want to extend the data2viz dsl but that's not possible due to hardcoded renderable types https://github.com/data2viz/data2viz/blob/aad3ce13c12d472d208ad5261d367a390b5d4076/viz/src/jfxMain/kotlin/io/data2viz/viz/JfxGroupRenderer.kt#L51

if (node.visible)
			when (node) {
				is CircleNode       -> node.render(gc)
				is RectNode         -> node.render(gc)
				is GroupNode        -> node.render(gc)
				is PathNode     	-> node.render(gc)
				is TextNode         -> node.render(gc)
				is LineNode         -> node.render(gc)
				else            -> error("Unknow type ${node::class}")
			}

what do you think about making a

Renderable

interface which every node type would implement?

class RectNode(rect: Rect = RectGeom()) : Node(),
        Rect by rect,
        HasFill,
        HasStroke,
        Renderable {
    override fun render(gc: GraphicsContext) {...}
}

or alternatively make a

RectRenderable

interface

I'd be glad to make such contribution, it's just I don't want to work on something that will be then rejected

so my question is: if I were to implement it would you accept the PR?

Hello @Bruno_ Thank you for your interest and your proposal. The idea of the basic visual elements (rectangle, circle, line, path) is that they have no binding to any rendering context. It is then the responsibility of a specific platform renderer to transform this “in memory” element into graphics. Can you explain in what way you would like to extend the DSL, what do you need that is not currently possible?

I wanted to make a

Candle

(pic rel) extension, what I want to do is technically possible by composing two rectangles (or rectangle + path) and I thought that it would be nicer to create a CandleNode etc

This is typically something you can do by adding an extension to Group for example.

fun Group.candle(width: Double, height …) {

line{...}

rect {...}

}

It will then be usable out of the box on Kotlin/JS JFx, Android.

hi, is jetbrains compose for desktop a target ? #compose-desktop

What is the status of charts-kt? It looks like it’s somewhat ready to be used but I don’t see any info about how to use it?

We’d be interested in using it in our react browser application.

Hello Jon, We have been working a lot these last months on Charts-kt and the current version (0.8.4) provides a nice DSL to make the chart creation a breeze. You can see some online samples here: • Basic Scatter Plot • Basic Line chart • Basic Column chart • Basic Bar chart • Stacked Column chart • Multi-series scatter plot We are currently working on the first version of the documentation. We also deployed the API reference documentation (Dokka). We’re planning to publish the v1.0 on the first quarter of 2021. Regarding the platforms, Charts-kt is currently working on JavaFX and inside the browser. It should be quite easy to make the first Android version. Other platforms will depend on our work on the base data2viz project. We would be very much interested in knowing your use case, type of application, platform, ...

Hi 👋 Is it possible to build a Tree representation with data2viz? Looking at the source, it looks like

TreeLayout

is what I want to use to position my nodes. I guess I'll have to do the drawing myself? Is there anything in the library to draw connectors ?

Hello Martin, that's right, you should use TreeLayout to build your tree, then iterate over your nodes to draw basic shapes. If you want some Bézier curves, the LinkBuilder in the io.data2viz.shape module is what you're looking for.

Check this sketch for example : https://play.data2viz.io/sketches/wJwZBY/view/

Hi I'm trying to get a student license to use charts.kt, anyone know who I should talk to about that?

Hi @Bryson Prince, please create an account on our forum https://forum.data2viz.io/ an ping me, we'll send you all the requirements,n and thanks for your interest in charts.kt ! 🙂

HI folks, there is any plan to make a version of data2viz in Compose?

Is there a way to use charts.kt in an opensource project?

Happy New Year everyone! I realized that https://www.data2viz.io/ is down, and there have been no updates in here for a long time. Is this project dead?

Hello @Sebastian Schuberth, Thanks for the alert. The project is not dead and Charts.kt (based on the data2viz library) is used in production. We’ll update our roadmap in the future weeks.

@Sebastian Schuberth The correct URL is https://data2viz.io/. From where did you get the WWW.data2viz.io url? I need to add a redirect.

Hello again, are there any plans to bring data2viz / charts-kt to compose (for desktop)?

Hello @Sebastian Schuberth Yes, it’s in the plans. @louiscad is going to work on it. What is your use case?

Hi, we are interested in using data2viz for a commercial project to generate some nice looking graphs 😉 I would have following questions: • do you have more information about the OEM licensing model (we have more than one developer, but we would generate the graphs on our backends not in apps) • would it be possible to get some test licenses so we could evaluate if the integration for backend generated charts would work for us Thanks

Hi folks! Trying out charts.kt for the first time. Is there any way to customize the order of the series in a stack? I'm using an area chart with standard stacking, but no matter how I define the series, I don't manage to put the one I want below the other.

Hi @Joffrey the order of the series is simply the order of the given items in your list, check this very simple example: https://play.data2viz.io/sketches/XYNkyJ/edit/, if you change the way

SplitProfit

are mapped, then the series will be drawn in a different order.

If you have any trouble, just paste your charts code here and I'll have a look.

Since you seem open to feedback, there is something else I'd like to share. I noticed I could use parts of the charts DSL in nested places that don't make much sense. For instance, I can write the following nonsense and the compiler is happy:

chart(data = props.simulation.monthlyPayments.seriesBreakdown()) {
    title = "Monthly payments (${props.simulation.name})"

    config {
        config {
            config {
                val time = discrete({ domain.month }) { name = "Time" }
                val value = quantitative({ domain.amount }) { name = "Amount" }
                area(time, value)
            }
        }
        events {
            config {
                selection {
                    series = discrete({ domain.type })
                    zoom {
                        selectionMode = SelectionMode.Disabled
                    }
                }
                zoomMode = ZoomMode.X
            }
        }
    }
}

This could be prevented by creating an annotation to mark the charts DSL using `@DslMarker`: https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-dsl-marker/