=== Improve interface for communication between GUI and interpreter ===
instead of using an external program, but overall user interaction
could be improved.
=== Generating publication-quality figures ===
* Lack of WYSIWYG
* Duplication of effort with FLTK and Qt widgets. With the rest of
* the GUI using Qt widgets, we should
eliminte the FLTK plotting widget. To do that, we will need to make the Qt plotting widget work when Octave is started with --no-gui and ensure that all features in the FLTK widget are also present in the Qt widget .
=== Improvements to classdef (the Matlab object-oriented programming framework) ===
=== String class ===
Matlab now uses "" to create string objects that behave differently from Octave double-quoted strings.
=== Handle UTF-8 (or whatever) characters properly ===
=== Handle single and integer values for ranges ===
=== Local functions ===
=== Allow large files to be loaded and saved ===
Make the load and save commands compatible with Matlab'sHDF5-based file format. Matlab users expect this and we needsomething like this to support large arrays anyway.
=== Matlab packages (+DIR directories in the loadpath; related to classdef) ===
piece is implementation of the "import" functionality and handling
it efficiently and in a way that is compatible with Matlab.
=== Toolboxes ===
* Better use of C++ features. Especially standard library features as their implementation becomes more widely available. For example, we might be able to simplify some things in Octave by using the C++17 filesystem and special functions libraries, if they provide results that are at least as good what we are using now.
* Eliminate C preprocessor macros where possible
=== GUI code editor ===
Make it possible to use external editors such as Emacs, vim, or
others with the GUI in addition to Octave's built-in code editor
=== Documentation ===