Thanks Jeff :) > I like your d3 idea, my friends advise that projects that are based on d3 > like bokeh go a long way and then get bogged down in details, so heads up, > but it's too cool to not try.
Hehe. Yes. I have spent a lot of time doing things in SVG that would have been much easier using HTML, e.g. I built an SVG textbox widget because I didn't want to use foreignObject :) Now I just finished a serializer to allow me to save the GUI state, which isn't completely trivial for Javascript modules. This will allow me to do things like undo/redo and I can imagine sharing the GUI display across multiple clients for training and/or streaming, e.g, market data. > Unfortunately, incorporating Julia via node-julia will not work when using > Nashorn and Avatar.js as they are projects to replace node and v8 not work > with them. Nor will node-webkit or atom-shell if you are wanting to go > browser-as-desktop-app route, but d3 in a browser still will of course. That does not sound encouraging :) I am probably confused, but in the link, they are talking about running Node in Nashorn and it even points to a list of Node modules they are currently able to run. https://avatar-js.java.net I was hoping node-julia could be added to the list. I guess not? By the way, as I was reading up on Nashorn, I learned that it is intended to be more general than just "Javascript in Java". It is supposed to be an architecture for scripting languages in general to run on JVM, i.e. an "LLVM for JVM", which begs the question if it now starts to make sense thinking about compiling Julia directly to bytecode for JVM? The Javascript performance seems pretty good. I think that would be a big boost to Julia if you're able to get Java developers on board.
