|
Octave GTK+ must allow the user to:
|
|
> Use 'octave' to program in GTK+. |
-
Where by we visualise the concept of bringing the scientific
computing closer to users, with the help of GUI interface to
computing code.
-
This will also provide hassle free method of making the GUI's
and also ease writing computationally intensive code.
-
User can get parameters from the GTK+ GUI, and the matrix
intensive calculations can be performed with Octaves BLAS tools,
which will ease writing computationally intensive programs with
a GUI.
|
|
> Write a front end to Octave with GTK+.
|
-
;-)
Thats the next step. We must write a GTK+ IDE for octave,
that can indent/edit/highlight code, and provide all the
features of the GUI can with some eye-candy.
|
|
> Interface GLADE to Octave.
|
-
By making GLADE design the GUI, and we convert the ".glade"
files to octave-gtk binding API, we will be able to use this
code generation facility to make a dynamic GUI code, for the
user. After this the user need only create the callback code,
and write his/her functional code.This could accelerate
octave-gtk+ utility to end users.
-
|
|
> SWIG-Octave
|
-
;-)
Swig Octave will allow the deveopers to automatically
use swig [http://swig.sourceforge.net], and port their program
with wrappers to be available from Octave. We are working on it.
|
|
> Hand'e'l Graphics
|
-
Handle graphics will be a compatibility layer, and [Xp] cross platform
layer for our work on making GUI's scripting with Octave. Also we would like
to implement a platform independent layer within the octave kernel itself,
with extensions/run-time selection of widget-set/toolkit for using within
Octave GUI. A Power idea.
|
a GTK+ binding for GNU/Octave.