does not work on linux @edvin

@ron I keep forgetting. I can give you a linux script that works though.

its ordered

looks like d3.js generates SVG?

may be relevant: https://docs.oracle.com/javase/8/javafx/api/javafx/scene/shape/SVGPath.html

running d3.js inside nashorn with some tweaks to make jfx render the svg data would be neat

alternatively use batik to render the svg to an image

@mikehearn That would be cool, but then we would miss out on the interactive features. I guess that might be fine for many situations, and it would probably behave much better with regards to memory usage and resources.

true. i don't know how interactive d3.js gets or how much of the web DOM it needs

I think this has great potential, but it requires some work. I just don't have time right now I'm afraid.

@edvin @mikehearn I'm going to play with this some more today and tomorrow, and I'll share my findings. It's Independence Day here in the U.S., but I might slip in some computer time. I do wonder how much "interactivity" there will be, but we'll see how far we can push it.

I think Mike's idea would yield the best result if possible. Interactivity isn't always so important, and we might possibly support two rendering modes down the line perhaps?

note that d3.js has a canvas mode

canvas does not support DOM event dispatch. so if d3 can do interactivity with canvas mode, it must do its own hit testing and animation

mapping web canvas to javafx canvas should be easy, right? they're pretty similar APIs iirc

If that's possible I think we have a winner!

A tornadofx SVG builder could also be an idea. SVG seems to map perfectly to a declarative builder and a kotlin dsl could reduce a lot of the pains in building svg's. Advanced functionality could then be provided by wrapping some of d3's modules or replicating them in some way or form.

@edvin, I hate to dig up my problem from Friday last week. But here is a small, self-contained project with the compilation problem.

If you try importing it into Intellij, it complains about a 1.6 compatibility issue.

@thomasnield I'll have a look right now 🙂

@thomasnield Do you open each of the projects separately, and is that how you want it to be?

@teedee That's a very nice idea indeed. It wouldn't be so hard to create, actually I think we have most of the building blocks already.

@thomasnield I did two things. 1. Add the Kotlin Facet to each project (F4 on the project, Facets, +). 2. Go into Settings -> Compiler -> Kotlin Compiler and select Target JVM Version 1.8 instead of the default 1.8. I think both of these issues are due to some issue with the latest IDEA. It should have picked up those settings from the pom. Also, the project language level was 1.3 by default, which I see in IDEA when importing new projects all the time.

@edvin are you using the maven source/target set to 1.8 and still getting the 1.3 from intellij?

@carlw Actually, that was a dead end. When I open app2, IDEA also shows app1 in the workspace, and since there is no parent pom, it just leaves it at the default 1.3. It is not a problem at all though, each project has the correct language level.

@thomasnield I deleted everything and tried again, the only setting I need to change is the Kotlin Compiler JVM Target setting, which is not being picked up automatically.

@edvin each module has the correct language level, just not the parent?