As discussed https://github.com/data2viz/data2viz/issues/239, this adds Viz.toSVG() support.

Support is almost finished, almost everything works. What still needs to be done:

• Gradients need more tests (especially radial)
• More tests in general
• Text is a bit misaligned (too far downwards)
• Chart<*>.toSVG()

If there are any suggestions for tests or text alignment, let me know!

This is a potential solution for #29.

I updated the Travis config to use a build matrix in order to be able to run the default build and android build in parallel. You can view the build here, which has one regular Java job and one Android job.

The main Java job runs exactly the same as before. The android job disables the "-js" sub-projects to avoid duplicate work. I tried also disabling "-jfx" projects as these seemed unnecessary, but I discovered that some of the "-jvm" projects depend on "-jfx" ones. I added the toggle for js and jfx using boolean properties in gradle.properties files, which can be overridden using project properties, for example: ./gradlew -Dinclude_js=false check. Some checks were added in settings.gradle for these properties.

I had to update the android sdk to version 28 in the root project, as examples/app and viz/rendering-app both were already on 28 and it's way easier to have everything on the same version for Travis.

I also removed local.properties from git and added an exclusion to .gitignore.

Let me know if you have any feedback!

I would like to be able to update visualizations without entirely recreating them, and possibly do that for real-time (rapidly updating) data.

As far as I can tell, this is not very feasible with the current API - on Android (which is the platform I am working with) it seems that to update a visualization, you have to remove the old View and replace it with a new one, which is a pretty wasteful way of updating graphs.

Have I missed something here? If not, is there a chance that this will be implemented at some point, or should I turn to specialized real-time libraries for that?

Travis CI fails on android configuration:

* What went wrong:
A problem occurred evaluating project ':app'.
> The SDK directory '/Users/gaetan/Library/Android/sdk' does not exist.

See https://stackoverflow.com/questions/27644586/how-to-set-up-travis-ci-with-multiple-languages and https://docs.travis-ci.com/user/languages/android/

Why of all the class and singleton names these particular ones should start with a lowercase letter?

scales.continuous.linear { }

instead of

Scales.Continuous.linear { }

This strikes me as a very odd and arbitrary decision.

Hi I tried to rewrite a simple d3js network graph http://bl.ocks.org/jose187/4733747 to data2viz. I'm using the ex-force example as reference.

But i'm stuck. Since i'm still unfamiliar with the DSL & the API. Could you give me some pointer or the classes to use to rewrite this. Thanks.

Due to the differences in arc API on each platform, all cases should be tested on all platforms with a comparison of the rendered images.

start; end; counterclocwise; 0; 0.25PI; false 0; 0.25PI; true 0; 2.0PI; true 0; 2.0PI; false .25PI; 2.25PI; true .25PI; 2.25PI; false ...

I got a graph to work in Chrome, Firefox, Edge, but not in Iexplorer. I can see the online JS examples are also not working in IExplorer.

I think it may be because IExplorer does not accept the append method on dom elements, these calls could be probably replaced with "appendChild".

The README of your repository contains two links to examples: http://data2viz.io/dist/chart.html http://data2viz.io/dist/svgperfs.html both are not working for me neither in Firefox nor in Chrome.

was searching for a while but never found any helpful topic on how to express continuous and streamed data in moving graph to generalize assume

var x = 0
while(true){
   x++
   // displaying x in continuous manner
}

tried approach that behaves almost exactly like the code below

val p = Pane()
                            var x = 1.0
                            val viz = p.newVizContainer().apply {
                                size = Size(width, height)
                            }
                            while(true) {
                                x++
                                values[1] = x

                                print(values)



                                //  while(true) {
                                viz.chart(values) {
                                    val values = quantitative({ domain })

                                    plot(values, values)
                                }
                                //  }

                                val scene = Scene(p, width, height)
                                jfxpanel.scene = scene
              }

but never succeed

Bumps fstream from 1.0.11 to 1.0.12.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Data2viz currently supports only two types of transformation: Translation and Rotation but not Scaling. Could support for a scaling transformation be added? See details on the scaling transformation for the HTML Canvas here: https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/scale

Hey there,

does this library also support force directed graphs for multiplatform targets, specifically jetbrains compose multiplatform? i've seen this demo but it looks like its only for kotlin/js

Currently, the Android implementation of D2V doesn't handle the size of the viz particularly well.

• the VizContainerView has a default size of 100x100, which gets replaced by the size given by the system in onSizeChanged(). If container.newViz() gets called before the size has been updated, the viz will only receive the default square size to work with.
• when the size of the container gets updated, it also updates the size of the viz but doesn't call viz.resize(), which means that the viz can't respond to the update.
• there is no way for the viz to modify the container size. On Android, a view can actually have a width/height of wrap_content, which means that the viz can choose itself what size it wants to have. However, this was not something I was able to make use of with the current API.

I'm currently using this workaround to make sure the viz always receives the correct container size (using Compose, but the idea should be independent of it):

AndroidView(
        factory = { context ->
            val container = VizContainerView(context)

            val viz = container.newViz {}

            // Draw viz when the size given by the outside changes
            container.addResizeListener {
                viz.clear()
                viz.apply { ... }
                // Start the animations, D2V doesn't launch them by itself.
                viz.startAnimations()
            }

            return@AndroidView container
        },
        // Modifiers determining the size of the view
    )

I'm not sure what changes exactly would need to be made, but as it is, I found it a frustrating experience to simply figure out how to draw my viz with the correct measurements.

To use renders and plots in papers it would be very useful to be able to export them to a vector format like SVG. As indicated by the developers, there already exists a small conversion to SVG for geoms: https://github.com/data2viz/data2viz/blob/33d381fb6349877c9cafe084cb69c3a6f8a86349/core/src/commonMain/kotlin/io/data2viz/geom/PathGeom.kt#L138 but this isn't the case yet for everything that can be rendered. I don't how much work it would be or how easy it would be per-platform.

If I'm correct, we would need new renderers like for Jfx (https://github.com/data2viz/data2viz/tree/master/viz/src/jfxMain/kotlin/io/data2viz/viz) but then to create an SVG string right?