Custom Displays

[Baidicoot]

I was wondering if there was any play to update the 'active display' logic to support custom display types (i.e. not one of "full", "plain", "rich", "conversation" or "none"). The functionality for this seems quite easy to implement, so some fork could presumably do it pretty easily. Mostly I see three ways you might go about this:

• Keep the current setup where you have globals for _display_type etc, and update the display initialization functions to read from some registry of displays.
• Pass in the display to the evaluation as an argument.
• Otherwise modify the output logic to stream information to a generalized "Output" class, which then decides what to do with it. Display would then subclass this.

Thanks

[jjallaire-aisi]

Indeed, it wouldn't be hard to make this externally loadable (although honestly the display API wasn't designed for public consumption so might need some revision / clean up). I'm curious though what the scenario for a custom display is (as perhaps it's something we should support internally anyway)