@holgerbrandl okay awesome, I was just browsing Vegas the other day. I'll think about this carefully and start putting together a list under my GitHub name. I'll share it once it's up.

@holgerbrandl also possibly of interest: https://github.com/stefaneidelloth/javafx-d3 . he embedded d3.js into a webview (instead of vega) to get jvm plots

i was actually planning to switch koma to spitting out vega-lite so i could dump it into a webview. looks like i might be able to use kravis instead of having to do all the jfx wrangling myself

if only javafx supported webgl, then cesium could come along for the ride...

@thomasnield i'd recommend jackson for your list. data in/out is the most annoying part to figure out when using a new platform

i haven't found a good user friendly binding for hdf5 unfortunately

@kyonifer I've seen it but it looked a bit inactive to me. And also Vega-lite is much closer to common scientific vis types than D3 which is much more generic.

agreed, I like vega lite better when its applicable

I wonder if anyone here has plans regarding 3d plotting from kotlin? there's a few JVM options I've seen but they are all limited

getting out to a browser with 3d support requires some awkwardness, such as jcef or swt

@kyonifer @holgerbrandl we haven't even thrown Kotlin Native into the mix yet. I think that's going to catch on quickly once it hits 1.0, and if we are lucky many robust libraries will pop up within a few years.

I may casually start exploring UI's with native which already has been discussed in #tornadofx. I'm not sure how hard it will be though. https://github.com/vurtun/nuklear

@thomasnield I did write some toy gtk apps with native. seemed to work reasonably

since koma runs on native and js I'm planning to make a multiplatform plotting piece that targets whatever is on those platforms, so its definitely on my mind as well

js is naturally going to be the easiest piece there

@kyonifer I was trying to remember if you made it native compatible, that's awesome. I got to get on the multiplatform wagon soon. FOMO and all that.

@kyonifer not sure if native can compete so easily with javascript-powered datavis. Like with all the current momentum in d3, vega, etc it seems more efficient to me to rather provide some easy to use kotlin bindings for these frameworks. Also native (if I understood it corretly) is an all-in game: So you either go “just” native and loose all the cool jvm libs, or you stick to jvm and integrate datavis as good as possible. Lazy and old as I’m, I’m more in favor of the latter.

from java that's maybe jfx or swt etc. from native that might look like a qtwebview. from js back end... well you just straight plot

plotting and doing other computation from native is something that would definitely make my life easier, since I can't always have a JVM around for my work (e.g. embedded robotics)

it'd be cool if I could prototype in JVM and then deploy with native. and have a vis pipeline that worked on both sides

which is also why I think something like vega lite is the right solution. the data side can just generate json to be consumed by whatever js engine is available, even if that's a remote browser over a web socket

with that architecture it wouldn't matter a huge deal if you were on native or JVM kotlin, as long as you can stream json to a web view or browser

I was planning to tinker with writing a multiplatform plotting api with back ends on each platform, trying to find the easiest path to a js engine to parse the vega/d3/etc generated by the common module

it looks like kravis might be an easy path for the jvm side, if it supported the plot types

there was someone else on this channel looking at doing some kotlin vis awhile ago on the kotlin-js side and was talking about supporting vega, but I forget who it was

maybe @thomasnield remembers that convo

I miss channel history

@kyonifer still working on it 🙂. https://github.com/data2viz/data2viz

There is a lot of work to do and we also have been working on an editor.

ah even better.. sorry I'm terrible with names :)