You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That would make it a drop-in replacement for graph layout algorithms in e.g GraphMakie.jl. The only change that would be needed are:
The solvers inherit from NetworkLayout.AbstractLayout
The solver structs are themselves callable and return vectors of GeometryBasics.Point2
For this, we'd have to add three new fields to the Zarate struct that correspond to the kwargs in the current solve_positions function. But this wouldn't technically be breaking from a user perspective, since that function's kwargs can still override the solver specification if desired.
What do you think @oxinabox? I'm happy to put in a PR if you think this makes sense.
The text was updated successfully, but these errors were encountered:
That would make it a drop-in replacement for graph layout algorithms in e.g GraphMakie.jl. The only change that would be needed are:
NetworkLayout.AbstractLayout
GeometryBasics.Point2
For this, we'd have to add three new fields to the
Zarate
struct that correspond to the kwargs in the current solve_positions function. But this wouldn't technically be breaking from a user perspective, since that function's kwargs can still override the solver specification if desired.What do you think @oxinabox? I'm happy to put in a PR if you think this makes sense.
The text was updated successfully, but these errors were encountered: