octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Joining Octave Development


From: Rik
Subject: Re: Joining Octave Development
Date: Wed, 27 Aug 2014 09:23:59 -0700

On 08/27/2014 09:00 AM, address@hidden wrote:


> ​Hi everyone,
>
> I am Yves Matanga ,a graduate student who is currently doing his Master
studies in Electronic Engineering (Specialization : Control & Image
Processing).
>
> I am very much in favor of the Octave project and would like to
contribute in its development as I believe that It has a very helpful to
support many development and research work especially when
> it is hard to procure one self with commercial similar ones.
>
> ​Are they any specific procedure to get involved in this project?​

Not really.  The first step for everyone wanting to contribute is to make
sure that you can get a development version of the code through Mercurial
and successfully compile it on your local machine.  Instructions for
contributing are in Appendix D of the manual, but also available here
(https://www.gnu.org/software/octave/doc/interpreter/Contributing-Guidelines.html#Contributing-Guidelines.

Once you have cloned the Mercurial repository to your local machine
./bootstrap
./configure
make

to build a local copy.

>
> ​ I am much more concern into :
>
> - i​​mproving the f​igure window features (figure copy .GUI,....)

That's great, we want to improve the GUI too.  The code you will want to
examine is in libgui/.  The best way to start is to look on the Octave bug
tracker (https://savannah.gnu.org/bugs/?group=octave) and change the
display criteria to display bugs marked with category "GUI".  Try picking a
bug and see if you can code a solution.

--Rik

> - working torward the creation of Simulink or Scicos Like toolbox for GUI
assisted design,
> -....
>
>
> My current expertise are in C/C++ /Java  (to name the relevant
programming languages,..)
>
> Thanks.​
>
>
> --
> Yves Matanga



reply via email to

[Prev in Thread] Current Thread [Next in Thread]