home.social

#higraph — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #higraph, aggregated by home.social.

fetched live
  1. Release 0.3.2 of #Higraph is out.
    Edge names can be placed anywhere along the edge, and will maintain their position. And a handful of bugs/ rough edges rubbed off.

    I am singularly pleased with the edge name code - it uses the spline parameter t, and a perpendicular distance d, to convert between the (x,y) screen coords and (t,d), which are "natural" coords for a spline.

    Find it here:

    github.com/ghillebrand/Higraph

    #GraphTheory #Python #indieDev

  2. Release 0.3.2 of #Higraph is out.
    Edge names can be placed anywhere along the edge, and will maintain their position. And a handful of bugs/ rough edges rubbed off.

    I am singularly pleased with the edge name code - it uses the spline parameter t, and a perpendicular distance d, to convert between the (x,y) screen coords and (t,d), which are "natural" coords for a spline.

    Find it here:

    github.com/ghillebrand/Higraph

    #GraphTheory #Python #indieDev

  3. Updated release of #Higraph - this is bug squishing, and a number of UI tweaks to make modelling flow more easily.

    github.com/ghillebrand/Higraph

    #Python #Pyside6 #IndieDev

  4. Updated release of #Higraph - this is bug squishing, and a number of UI tweaks to make modelling flow more easily.

    github.com/ghillebrand/Higraph

    #Python #Pyside6 #IndieDev

  5. And it's up! The first public release of #Higraph is now available!
    There is only a Windows installer at present. But it only has 1 dependency (#PySide6), and there are (hopefully clear!) build instructions on the home page of the repo!

    github.com/ghillebrand/Higraph

    #Python #IndieDev

  6. And it's up! The first public release of #Higraph is now available!
    There is only a Windows installer at present. But it only has 1 dependency (#PySide6), and there are (hopefully clear!) build instructions on the home page of the repo!

    github.com/ghillebrand/Higraph

    #Python #IndieDev

  7. #Higraph progress! The text names of items now open in an in-picture editor as you create the item, and for nodes and blobs, can be moved! This is the last major thing before MVP!

    #Python #Pyside6 #GraphTheory #indieDev

  8. #Higraph progress! The text names of items now open in an in-picture editor as you create the item, and for nodes and blobs, can be moved! This is the last major thing before MVP!

    #Python #Pyside6 #GraphTheory #indieDev

  9. #Higraph #Python #GraphTheory

    One more small feature, and some housekeeping, and I will have a "minimum viable product" of a higraph editor!

    (This picture was directly copied and pasted from the tool - not a screenshot 🤓)

  10. #Higraph #Python #GraphTheory

    One more small feature, and some housekeeping, and I will have a "minimum viable product" of a higraph editor!

    (This picture was directly copied and pasted from the tool - not a screenshot 🤓)

  11. #Higraph update:
    #Hyperedges can now be straight lines or hermite splines.

    Heading towards "minimum viable product" quite quickly now!

    #Python #Qt #PySide6

  12. #Higraph update:
    #Hyperedges can now be straight lines or hermite splines.

    Heading towards "minimum viable product" quite quickly now!

    #Python #Qt #PySide6

  13. #Higraph progress!

    Still got lots to do, but hyperEdges can now be saved & loaded in modified #graphml files. The "model tree" on the left highlights items in the graph on the right.
    I can see "minimum viable product"!

    The #hyperedge structure is both graphically and algebraically accessible. I'm not aware of anything else that does this, pretty certainly not in #Python
    #graphTheory #VisualFormalism

  14. #Higraph progress!

    Still got lots to do, but hyperEdges can now be saved & loaded in modified #graphml files. The "model tree" on the left highlights items in the graph on the right.
    I can see "minimum viable product"!

    The #hyperedge structure is both graphically and algebraically accessible. I'm not aware of anything else that does this, pretty certainly not in #Python
    #graphTheory #VisualFormalism

  15. #Higraph update.
    My wife has been squashing bugs and added an awesome hierarchical view of the blobs (sets).
    #Hyperedges still need work, but this is getting tantalisingly close to a usable tool!

    #Python #pyside6

  16. #Higraph update.
    My wife has been squashing bugs and added an awesome hierarchical view of the blobs (sets).
    #Hyperedges still need work, but this is getting tantalisingly close to a usable tool!

    #Python #pyside6

  17. You asked, and here it is: #hyperedges are basically working. 1200 lines of code & changes in 2 weeks - about 50 odd hours of coding. This was not trivial, but hyperedges are a thing.

    There are still some features to add (deletion, XML serialisation), and bugs to squash, but the hard work is done.
    😁

    #Python #Higraph #GraphTheory #PYside6

  18. You asked, and here it is: #hyperedges are basically working. 1200 lines of code & changes in 2 weeks - about 50 odd hours of coding. This was not trivial, but hyperedges are a thing.

    There are still some features to add (deletion, XML serialisation), and bugs to squash, but the hard work is done.
    😁

    #Python #Higraph #GraphTheory #PYside6

  19. This image is of a simulation of a simple directed #hypergraph , but using an n-ary line rather than a set for the #hyperedge

    I have written a working #graphTheory editor for binary edges, where nodes are extended to sets (a #Higraph) , and am contemplating the complexity of n-ary edges with increasing apprehension. It requires refactoring just about the entire edge drawing codebase - 100's of changes across ~2000 lines of #Python.
    Is it worth it? Please comment/ vote in the poll below

  20. This image is of a simulation of a simple directed #hypergraph , but using an n-ary line rather than a set for the #hyperedge

    I have written a working #graphTheory editor for binary edges, where nodes are extended to sets (a #Higraph) , and am contemplating the complexity of n-ary edges with increasing apprehension. It requires refactoring just about the entire edge drawing codebase - 100's of changes across ~2000 lines of #Python.
    Is it worth it? Please comment/ vote in the poll below

  21. A #Higraph milestone: Blobs (nodes as sets) now work! Grab a 'parent' blob, and all the children move. Edges connect anywhere on the blob, and default to be orthogonal to the point of contact. graphML read and write working.

    Now on to proper hyperedges!

    #Python #Pyside6 #Qt #GraphTheory

  22. A #Higraph milestone: Blobs (nodes as sets) now work! Grab a 'parent' blob, and all the children move. Edges connect anywhere on the blob, and default to be orthogonal to the point of contact. graphML read and write working.

    Now on to proper hyperedges!

    #Python #Pyside6 #Qt #GraphTheory

  23. Hi #Mathstodon - a #GraphTheory question:
    Given the following visual set containment, I can obtain the total containment of every item as a list (text on the left). This intuitively seems sufficient information to derive the containment graph (almost a tree - n7 breaks that).
    Are there any 'standard' techniques to apply to this?

    Boosts, partial ideas, discussion all welcome.
    #Higraph

  24. Hi #Mathstodon - a #GraphTheory question:
    Given the following visual set containment, I can obtain the total containment of every item as a list (text on the left). This intuitively seems sufficient information to derive the containment graph (almost a tree - n7 breaks that).
    Are there any 'standard' techniques to apply to this?

    Boosts, partial ideas, discussion all welcome.
    #Higraph

  25. @MrBerard #Higraph editor question:
    So far, it has been possible to round trip models from my tool into yEd and back. I'm now developing more higraph specific functionality that they don't explicitly support. But the graphML spec has a very _similar_ idea (nested graphs). Is it worth the effort to save higraphs in an "approximately round-trippable" format, or just leave yEd behind?
    Thoughts welcome!

  26. @MrBerard #Higraph editor question:
    So far, it has been possible to round trip models from my tool into yEd and back. I'm now developing more higraph specific functionality that they don't explicitly support. But the graphML spec has a very _similar_ idea (nested graphs). Is it worth the effort to save higraphs in an "approximately round-trippable" format, or just leave yEd behind?
    Thoughts welcome!

  27. If I did everything right, I have a public alpha release of my graph (nodes and edges) editor
    With source and windows binary !
    (I hope)
    It's a rolling chassis, to explore the design patterns for the ultimate goal of a #higraph editor.

    #Python #PySide6 #graphTheory

    github.com/ghillebrand/qtPyGra

  28. If I did everything right, I have a public alpha release of my graph (nodes and edges) editor
    With source and windows binary !
    (I hope)
    It's a rolling chassis, to explore the design patterns for the ultimate goal of a #higraph editor.

    #Python #PySide6 #graphTheory

    github.com/ghillebrand/qtPyGra

  29. I was looking for an icon for the Version 00 release of my #Higraph tool, and remembered that my 1999 version had one.
    I had to fire up a #WIndows98 VM, and access the files via IE5 and XAMPP on my PC, but here it is. Zipfile with full system is there for your download pleasure!

    #retrocomputing

    isijingi.co.za/wp/2025/07/14/a

  30. I was looking for an icon for the Version 00 release of my #Higraph tool, and remembered that my 1999 version had one.
    I had to fire up a #WIndows98 VM, and access the files via IE5 and XAMPP on my PC, but here it is. Zipfile with full system is there for your download pleasure!

    #retrocomputing

    isijingi.co.za/wp/2025/07/14/a