Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    innerop
    @innerop
    I mean even if you have it outside of render in the initial GraphViz setup
    It should be called each time before render, no?
    Magnus Jacobsson
    @magjac
    å is pronounced as the a in walk if you're an Englishman. If you're American... ¯_(ツ)_/¯
    True. I'll update the example. Thanks!
    innerop
    @innerop
    There was a Swedish pub in NYC that I used to hang out at and it was where I discovered Hoegaarden. I recall it being said the same way Americans say ”John” it’s not JOHN but more like JAHN, but it’s written with an O. I’m ethnically Turkish and Persian, but been in US since 87... so the accent grew on me (grew up with British English)
    All the Os are elongated in America
    Homotopically equivalent after all (A and O) ... k, back to work, sorry for the noise
    Magnus Jacobsson
    @magjac
    @innerop https://www.npmjs.com/package/d3-graphviz/v/3.0.0-alpha.3 even though I don't thinks there's any differences that matter to you
    innerop
    @innerop
    great @magjac will check it out... I think from a UX perspective, network topology changes (or any graph change in a realtime monitoring scenario) should be played out one change at a time, as it would be confusing to make sense of multiple simultaneous changes in an animated scenario.. in a static scenario, one may be able to keep track of 6-7 changes at once but the human mind cannot track too many simultaneous changes ...
    Magnus Jacobsson
    @magjac
    @innerop Thanks. Not sure if I understand what you mean by that.
    I also updated the README: https://github.com/magjac/d3-graphviz/blob/wip-port-to-hpcc-js-wasm4/README.md and I plan to write a few lines about the differences vs. 2.x in the release notes.
    innerop
    @innerop
    I mean that the performance from 2.x should be fine since the changes between states of the graph will be serial and relayed at 1 second interval, so no more than one change per second and each change will involve only a few nodes and edges. But the client may also want to go with just static snapshots using graphviz WASM or the WASM version of networkx... still unsure ... depends on their UX designers and what they decide
    Magnus Jacobsson
    @magjac
    OK, what is it they want to show? Or are you not allowed to tell?
    innerop
    @innerop
    I think it’s public knowledge that there are network monitoring that display alarms and other events like topology changes, and there are products already that offer visualization of both. What they want to do is a niche application of this same UX to a particular kind of network so I thought I’d introduce them to animated graphs and see if that makes sense vs static snapshots.
    Magnus Jacobsson
    @magjac
    OK. Thanks.
    Magnus Jacobsson
    @magjac
    @innerop I've added https://github.com/magjac/d3-graphviz/blob/wip-port-to-hpcc-js-wasm4/CHANGELOG.md
    I will make the official release as soon as I get your feedback.
    @GordonSmith Thanks for the v0.3.6 release with the image support btw. Greatly appreciate it :pray:
    innerop
    @innerop
    @magjac my interpretation of this "However, there are two d3-graphviz functions, drawNode and drawEdge that calls the layout functions directly and if they are going to be used, the script type must be "application/javascript" or "text/javascript"."
    is that if we need to use drawNode or drawEdge then we can't use GraphViz in a Web Worker?
    N/m, I get what you mean now
    innerop
    @innerop
    I wonder why you can't call drawNode and drawEdge via postMessage (I've not used workers in a while but I recall that JS types serialize automatically via HTML5 structured cloning, done by the browser)
    at least in recent browsers...
    innerop
    @innerop
    @magjac only feedback so far is you need to mention how to include the script for d3-graphviz itself, e.g. <script src="https://unpkg.com/d3-graphviz@3.0.0-alpha.3/build/d3-graphviz.js"></script>
    everything seems to be working, at least in my demo
    i can't tell if it's snappier or not as I have a very small graph
    but so glad it's using the latest GraphViz and assuming @GordonSmith continues to keep up with GraphViz upstream or documents best practices (or tips) for building the WASM with Emscripten, we should be all good ...
    Magnus Jacobsson
    @magjac
    Thanks. Well, it's not using the latest Graphviz which is 2.42.3 which even that has a bug that is fixed in HEAD but not released. See our discussion above.
    Gordon Smith
    @GordonSmith
    FWIW graphviz/graphviz#1665 (I currently would need an official TAG to build from).
    Magnus Jacobsson
    @magjac
    d3-graphviz v3.0.0 has left the building! :tada:
    Thank you so much for your encouragement and support @GordonSmith @innerop
    Gordon Smith
    @GordonSmith
    Congrats and your welcome!
    (I guess I can bump mine to version 1 in the near future...)
    Magnus Jacobsson
    @magjac
    Hopefully you can include an upgrade to Graphviz 2.42.4 to get rid of graphviz/graphviz#1605
    Gordon Smith
    @GordonSmith
    Once its released let me know!
    innerop
    @innerop
    Your idea behind d3-graphviz is very unique. I've seen "graph stories" where they fade out one frame and fade in another (Dagre-D3 has such an example) but nothing like what you've done which involves node and edde tweening. The idea itself is very powerful. If combined with some markup for math equations it can be very useful for students of algebraic topology where animations would follow the flow of equations. It has many other use cases...
    Magnus Jacobsson
    @magjac
    @GordonSmith Will do!
    @innerop Thanks :slight_smile: that makes me glad to here. I'm always interested to see if someone has use for it.
    I think scientists of all kinds who deal with graphs and topologies will find animation to be useful in illustrating concepts
    that's besides IP network topology monitoring, which is what I'm working on at the moment ...
    Magnus Jacobsson
    @magjac
    Gordon Smith
    @GordonSmith
    Hmmm - looks like I have gone out of my way to not include it...
    Rebuilding with now...
    innerop
    @innerop
    That’s interesting. In my demo I use the < <font ... > ... </font> > markup and that works ok (I think) but that may be unrelated
    Gordon Smith
    @GordonSmith
    That might get passed straight through? I did have it enabled in previous projects, just need to cmake FindEXPAT secret sauce...
    innerop
    @innerop
    Cool thanks! I didn’t even know that we can embed HTML structure inside nodes. I mean if the node border can be 0 and we embed a div then we can use CSS to create any custom shape. But I am not sure that GraphViz parses the CSS or if it does I’m not sure what subset of CSS it supports. But I can try and see ... interesting.
    Magnus Jacobsson
    @magjac
    @GordonSmith Thanks.
    Can you also comment on this issue: https://github.com/magjac/d3-graphviz/issues/127#issuecomment-594720193
    @innerop It's not actually HTML. It's HTML-like: https://www.graphviz.org/doc/info/shapes.html#html
    innerop
    @innerop
    Oh I see. Would have been great if it was HTML+CSS but I understand that the routing and layout algorithms would have to understand CSS and HTML too in that case in order to route/layout correctly ...
    innerop
    @innerop
    FWIW, people complaining about offline use cases should be more than ok running a Python or Node web server. It’s habit to kick off a web server process in each folder. D3 itself will have issues if there is no web server (when it needs to load data via .json and anything that employs XHR)
    Or they can do this: If using Chrome, the command line switch is --allow-file-access-from-files
    Not sure the flag would work in case of WASM but the underlying issue is XHR which is used to load WASM
    So it should work ...