publish(self, data, metadata=None, source=None, *, transient=None, update=False, **kwargs) -> None
See the display_data
message in the messaging documentation for more details about this message type.
The following MIME types are currently implemented:
text/plain
text/html
text/markdown
text/latex
application/json
application/javascript
image/png
image/jpeg
image/svg+xml
A dictionary having keys that are valid MIME types (like 'text/plain' or 'image/svg+xml') and values that are the data for that MIME type. The data itself must be a JSON'able data structure. Minimally all data should have the 'text/plain' data, which can be displayed by all frontends. If more than the plain text is given, it is up to the frontend to decide which representation to use.
A dictionary for metadata related to the data. This can contain arbitrary key, value pairs that frontends can use to interpret the data. Metadata specific to each mime-type can be specified in the metadata dict with the same mime-type keys as the data itself.
Unused.
A dictionary for transient data. Data in this dictionary should not be persisted as part of saving this output. Examples include 'display_id'.
If True, only update existing outputs with the same display_id, rather than creating a new output.
Publish data and metadata to all frontends.
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them