I identify as lurker, from a couple years back, but thought I'd stop by and let people know of a small idea that's kept me busy for the past fifteen years since leaving college (just shy of a Bachelor's degree, to my shame).
You can find it at https://my.graphplot.app/. I am currently building a version I can host on heroku and mongodb, and would love your feedback. I mean, be brutal, what would you improve about this program? Some of the technical stuff will sound obvious to me, as I've been working on it incrementally since 2007, trying to build my own version and package in a small web componenet library to make dynamic (in the sense that one deosn't have to know the graph up front, rather than the sense that it employs dynamic programming, which is an implication of the 2007 Veldhuizen paper) graph visualizations more universally accessible.
Over the years, and in between jobs, I have tinkered with a narrow (single level) dynamic graph visualization, played around with web components, tinkered around with WebAssembly, and am finally tying some of the previous versions into an MVP before I start over from scratch and tie everything together into THE PERFECT LIBRARY.
I'll rest easy once that's done, settle into a job and all that, but in the meantime, I'd love to hear everyone's feedback, on the preview (the interface is a little clunky, but to show that it can work, you create nodes by label, and type the labels again to connect them to an edge (label1>label2). Don't type @s for now, that's a different tangent I've been working on.
1 comment
[ 2.1 ms ] story [ 15.6 ms ] threadI identify as lurker, from a couple years back, but thought I'd stop by and let people know of a small idea that's kept me busy for the past fifteen years since leaving college (just shy of a Bachelor's degree, to my shame).
You can find it at https://my.graphplot.app/. I am currently building a version I can host on heroku and mongodb, and would love your feedback. I mean, be brutal, what would you improve about this program? Some of the technical stuff will sound obvious to me, as I've been working on it incrementally since 2007, trying to build my own version and package in a small web componenet library to make dynamic (in the sense that one deosn't have to know the graph up front, rather than the sense that it employs dynamic programming, which is an implication of the 2007 Veldhuizen paper) graph visualizations more universally accessible.
Over the years, and in between jobs, I have tinkered with a narrow (single level) dynamic graph visualization, played around with web components, tinkered around with WebAssembly, and am finally tying some of the previous versions into an MVP before I start over from scratch and tie everything together into THE PERFECT LIBRARY.
I'll rest easy once that's done, settle into a job and all that, but in the meantime, I'd love to hear everyone's feedback, on the preview (the interface is a little clunky, but to show that it can work, you create nodes by label, and type the labels again to connect them to an edge (label1>label2). Don't type @s for now, that's a different tangent I've been working on.