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
{{ message }}
This repository was archived by the owner on Sep 1, 2022. It is now read-only.
In addition to the notebook interface, we need to implement a web-based version of the console interface. Here are some of the tasks that will get us there:
Create a ConsolePanel as a container that holds a ConsoleWidget, similar to the way the notebook works.
Create a ConsoleModel that is similar to a NotebookModel but does not have a notion of arbitrary cell insertion.
The first child of the ConsoleWidget needs to be a RawCellWidget to hold a banner and the second needs to be a CodeCellWidget to hold the prompt.
The ConsoleWidget needs a set of keyboard bindings to emulate the Qt Console application.
The execution of the code cell needs to be separated from the notebook because it is common functionality.
After every prompt execution, a new CodeCell needs to be generated to become the new prompt.
The UI needs to be styled to look like the Qt Console application.
The history functionality of the Qt Console needs to be implemented (i.e. navigating through past commands via arrow keys).
The contextual tooltip feature of the Qt Console needs to be implemented.
The pager functionality of leaving the prompt and residing within a different interactive context (i.e., entering the interactive help) needs to be implemented.
The completion functionality (i.e., tab completion) of the Qt Console needs to be implemented. This should be done in a way that allows the notebook, or other widgets potentially, to use it as well.