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
To support rendering classes that you don't own in addition to a more OO approach there should be 2 ways to write render functions: via implementing an interface or registering a function (likely a lambda).
A render function takes an object of the type it can render and returns DisplayData.
A renderable object must serialize itself as DisplayData similar to toString() but richer instead.
Any objects that are not renderable are rendered as their string form.
The text was updated successfully, but these errors were encountered:
- Parse MIME types
- Register render functions for MIME types
- Displayable interface for owned classes
- Render with parameters and request rendering as certain types
- Always ask for a text representation to support overriding one during
rendering.
- Supply meaningful defaults for DisplayDataRenderable implementations
for supported and preferred types.
- Allow renderable types to declare they support any or an entire group
of mime types.
To support rendering classes that you don't own in addition to a more OO approach there should be 2 ways to write render functions: via implementing an interface or registering a function (likely a lambda).
A render function takes an object of the type it can render and returns
DisplayData
.A renderable object must serialize itself as
DisplayData
similar totoString()
but richer instead.Any objects that are not renderable are rendered as their string form.
The text was updated successfully, but these errors were encountered: