1,847
edits
Projects: Difference between revisions
→GUI/IDE: Move "GUI Variable Editor and Property Inspector" here from Summer of Code - Getting Started.
(→Numerical: Acknowledge {{patch|8172}}.) |
(→GUI/IDE: Move "GUI Variable Editor and Property Inspector" here from Summer of Code - Getting Started.) |
||
| Line 94: | Line 94: | ||
=GUI/IDE= | =GUI/IDE= | ||
*Søren Hauberg has suggested that we need C++ code that can: | *Søren Hauberg has suggested that we need C++ code that can: | ||
**Determine if a line of code could be fully parsed, i.e. it would return true for "plot (x, y);", but false for "while (true)". | **Determine if a line of code could be fully parsed, i.e. it would return true for "plot (x, y);", but false for "while (true)". | ||
| Line 100: | Line 99: | ||
**Query defined variables, i.e. get a list of currently defined variables. Bonus points if it could tell you if anything had changed since the last time you checked the variables (could also be done with signals). | **Query defined variables, i.e. get a list of currently defined variables. Bonus points if it could tell you if anything had changed since the last time you checked the variables (could also be done with signals). | ||
* Create a better (G)UI for the {{manual|profile|profiler}}. This may be done with Qt, but not necessarily. | * Create a better (G)UI for the {{manual|profile|profiler}}. This may be done with Qt, but not necessarily. | ||
== GUI Variable Editor and Property Inspector == | |||
Octave has a preliminary implementation of a Variable Editor: a spreadsheet-like tool for quickly editing and visualizing variables. The initial phase of the project will be learning how the implementation was done. | |||
With the knowledge gained, the second part of the project will be to implement a Property Inspector. This is a spreadsheet like interface to the many, many graphics properties that exist and are different on a per-object basis. The goal would be not only the concise-display of the existing properties, but a reasonable user interface to change them. As examples, Boolean properties should be able to be toggled with a double-click; Radio properties should have a drop-down list of only the supported options; Other properties that can be modified should have the constraints built-in (for example, Linewidth must be a scalar, while Position must be a 1x4 vector). It would also be important to have easy access to the documentation of a property. | |||
For reference, Matlab has a similar Property Inspector (https://www.mathworks.com/help/matlab/ref/inspect.html). | |||
== Sisotool. Create a graphical design tool for tuning closed loop control system ([[Control package]])== | == Sisotool. Create a graphical design tool for tuning closed loop control system ([[Control package]])== | ||