1,852
edits
GUI terminal widget: Difference between revisions
Jump to navigation
Jump to search
m
→Background: Pointer to latest thread https://lists.gnu.org/archive/html/octave-maintainers/2019-05/msg00115.html.
(→Open questions: Categories.) |
m (→Background: Pointer to latest thread https://lists.gnu.org/archive/html/octave-maintainers/2019-05/msg00115.html.) |
||
| Line 2: | Line 2: | ||
Way back in January 2012, jwe [https://lists.gnu.org/archive/html/octave-maintainers/2012-01/msg00416.html posted the following message] about changing the terminal widget in the GUI to handle input differently. | Way back in January 2012, jwe [https://lists.gnu.org/archive/html/octave-maintainers/2012-01/msg00416.html posted the following message] about changing the terminal widget in the GUI to handle input differently. | ||
This question was [https://lists.gnu.org/archive/html/octave-maintainers/2019-05/msg00115.html addressed again in May 2019]. | |||
Jwe included a simple example written with gtkmm to illustrate the idea of having the terminal widget in the GUI be in control of input and output and feed lines of text to the interpreter. | Jwe included a simple example written with gtkmm to illustrate the idea of having the terminal widget in the GUI be in control of input and output and feed lines of text to the interpreter. | ||
| Line 12: | Line 13: | ||
See the [https://hg.octave.org/jwe-qt-gui-with-push-parser/file/tip/NOTES NOTES file] for build instructions. | See the [https://hg.octave.org/jwe-qt-gui-with-push-parser/file/tip/NOTES NOTES file] for build instructions. | ||
That file also contains the following list of open questions that will need to be resolved if we are going to attempt a switch. | That file also contains the following list of open questions that will need to be resolved if we are going to attempt a switch. | ||
== Open questions == | == Open questions == | ||