1,847
edits
GUI terminal widget: Difference between revisions
→Open questions: Add section "Alternatives".
m (Add Category:Development) |
(→Open questions: Add section "Alternatives".) |
||
| Line 42: | Line 42: | ||
# The system function may need to be modified so that external programs that expect to be running in a terminal will continue to work properly. On Unixy systems, this job can be done with ptys. I guess Windows systems can use a hidden console? But if these things are required, are we more or less back to were we were before since we used a pty and hidden console to implement the terminal widgets? I believe the Emacs start-process function must do similar things, so we might be able to reuse that code. | # The system function may need to be modified so that external programs that expect to be running in a terminal will continue to work properly. On Unixy systems, this job can be done with ptys. I guess Windows systems can use a hidden console? But if these things are required, are we more or less back to were we were before since we used a pty and hidden console to implement the terminal widgets? I believe the Emacs start-process function must do similar things, so we might be able to reuse that code. | ||
=== Alternatives === | |||
# [https://github.com/jupyter/qtconsole qtconsole] | |||
#* (+) Fancy interactive features including plots | |||
#* (+) Contains history and a pager | |||
#* (-) Written in Python | |||
# [https://github.com/lxqt/qtermwidget qtermwidget] | |||
#* (+) Reusable component (less Octave code) as shared and development library [https://packages.debian.org/stretch/libqtermwidget5-0 Debian], [https://software.opensuse.org/package/libqtermwidget5-0 openSUSE]. | |||
#* (+) Contains history (and a pager?) | |||
#* (+) Written in C++ | |||
[[Category:Development]] | [[Category:Development]] | ||