Organize/unify the drawing module

[nwlandry]

At this point, we have lots of great functionality for drawing. The draw.py file is now ~1.5k lines! I'm wondering if we should

1. Organize the functions (some are drawing utilities, some only draw nodes/edges, some draw the entire hypergraph)
2. Unify the functions in some way (the most extreme example being that you have a single draw method with kwargs to change the style). I don't feel strongly about this, I just think it might be time to streamline this module.

[leotrs]

1.5k lines is too much for me to wrap my head around and I'm scared.

One thing to keep in mind is how to handle kwargs. All of these methods that just pass kwargs to some other call down the line tend to be very verbose and repetitive and bug-prone when doing things like if some_kwargs in kwargs: ....

[iaciac]

networkx has also 1.5k lines, just saying

[maximelucas]

Partially solved by #435

[maximelucas]

Since opening this issue, a lot changed in the drawing module:

• many smaller functions have been moved to a draw_utils.py file.
• many larger functions have been rewritten to use the same building block functions.

In particular right now we have:

• draw_nodes, draw_hyperedges to do the heavy lifting (the latter includes the hull drawing as an option)
• draw_node_labels, draw_hyperedge_labels for the labels
• draw combines all the above
• draw_multilayer which has code similar to do what's in draw_nodes and draw_hyperedges but cannot use those due to the 3d nature of the plot: scatter and other functions take additional arguments in 3d.
• draw_dihypergraph that uses draw_nodes and has its own code to draw the arrows.

My feeling is that none of those can be easily merged or use each other more. If that's the case, should we close this issue? Or @nwlandry did you have more ideas to unify?

[nwlandry]

I think that we can close now. Thanks for taking care of all these issues!