263
edits
JWE Project Ideas: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=== Improve interface for communication between GUI and interpreter === | |||
Currently, communication between the GUI and the interpreter | Currently, communication between the GUI and the interpreter | ||
| Line 8: | Line 8: | ||
would be more flexible and reliable. | would be more flexible and reliable. | ||
=== GUI command window === | |||
The implementation of the GUI command window for Unix-like systems | The implementation of the GUI command window for Unix-like systems | ||
| Line 18: | Line 18: | ||
could be improved. | could be improved. | ||
=== Interrupt handling in the GUI === | |||
This issue is related to the GUI command window. Interrupt | This issue is related to the GUI command window. Interrupt | ||
| Line 27: | Line 27: | ||
find a way to reliably interrupt the interpreter. | find a way to reliably interrupt the interpreter. | ||
=== Generating publication-quality figures === | |||
Generating EPS or PDF versions of figures needs improvement. | Generating EPS or PDF versions of figures needs improvement. | ||
=== OpenGL graphics system issues === | |||
* Improvements to classdef (the Matlab object-oriented | * Scaling plot data values/ranges to fit in single-precision OpenGL values | ||
* Performance issues | |||
* 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) === | |||
* Resolve remaining Matlab compatibility issues. | |||
* Make it possible to load and save classdef objects. | |||
* Improve and simplify the implementation. Although the basic | |||
features that are implemented now appear to mostly work, the | features that are implemented now appear to mostly work, the | ||
implementation seems overly complicated, making it difficult to | implementation seems overly complicated, making it difficult to | ||
| Line 50: | Line 52: | ||
improvement here. | improvement here. | ||
=== String class === | |||
* Matlab now uses "" to create string objects that behave | |||
differently from Octave double-quoted strings. | differently from Octave double-quoted strings. | ||
=== Handle UTF-8 (or whatever) characters properly === | |||
* Try to do this in a Matlab-compatible way. | |||
=== Handle single and integer values for ranges === | |||
=== Local functions === | |||
The semantics for local functions in scripts is different from the | The semantics for local functions in scripts is different from the | ||
| Line 67: | Line 69: | ||
files. | files. | ||
=== Allow large files to be loaded and saved === | |||
Make the load and save commands compatible with Matlab's | Make the load and save commands compatible with Matlab's | ||
| Line 73: | Line 75: | ||
something like this to support large arrays anyway. | something like this to support large arrays anyway. | ||
=== Matlab packages (+DIR directories in the loadpath; related to classdef) === | |||
Octave already searches for files in package directories and | Octave already searches for files in package directories and | ||
| Line 80: | Line 82: | ||
it efficiently and in a way that is compatible with Matlab. | it efficiently and in a way that is compatible with Matlab. | ||
=== Toolboxes === | |||
Move some core toolboxes (communications, control systems, image | Move some core toolboxes (communications, control systems, image | ||
| Line 90: | Line 92: | ||
equations package have already been moved to Octave. | equations package have already been moved to Octave. | ||
=== General code quality improvements === | |||
* Use C++11 features where possible. | |||
* Better and more complete use of C++ namespaces. | |||
as their implementation becomes more widely available. For | * Better use of C++ features. Especially standard library features | ||
example, we might be able to simplify some things in Octave by | as their implementation becomes more widely available. For | ||
using the C++17 filesystem and special functions libraries, if | example, we might be able to simplify some things in Octave by | ||
they provide results that are at least as good what we are using | using the C++17 filesystem and special functions libraries, if | ||
now. | 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 | 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 | others with the GUI in addition to Octave's built-in code editor | ||
=== Documentation === | |||
make it easier for new contributors to understand the Octave code | * Continue to improve Doxygen documentation for Octave internals to | ||
base. | make it easier for new contributors to understand the Octave code | ||
base. | |||
=== JIT compiler === | |||
A proof-of-concept implementation was done several years ago by a | A proof-of-concept implementation was done several years ago by a | ||
| Line 124: | Line 128: | ||
and Octave internals. | and Octave internals. | ||
=== Windows distribution === | |||
Eliminate the following msys packages. Some might be removed | Eliminate the following msys packages. Some might be removed | ||