octave-maintainers
[Top][All Lists]
Advanced

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

Re: GUI design


From: Daniel J Sebald
Subject: Re: GUI design
Date: Thu, 29 Mar 2012 00:35:28 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

On 03/27/2012 02:59 PM, John W. Eaton wrote:

   * When there is an error running an Octave script, an editor should
     pop up and place the cursor at the line of the error.

The line number and file is displayed on the screen. Having the IDE capture that info is the issue. What is the preferred means for that?


   * You should be able to interact with the debugger through the
     editor.

Same thing here. There needs to be a way for the IDE to capture things appearing in the command line window such as

keyboard: stopped in /home/sebald/matlab/debug/test.m at line 3


   * It is absolutely essential that the choice of editor is
     configurable.  It must be possible to use Emacs for this purpose.

That makes the debugging feature a bit tricky. If an outside editor is used, the debugger window should probably be disabled from modifying code, simply reload the file and show stepping information every time the code is re-run.

Or are you saying that Emacs is a good candidate for interacting with a debugger because there is some way to direct escape commands to it?


The Octave IDE will be used by novices.  It is NOT the place for UI
innovation.  We should use GUI/IDE features that are proven, familiar,
and easy to work with.

Good GUI/IDE design should be comprehendible no matter the complexity. Also, I would assume some level of computer experience from new users of Octave. If the group in question is students, they will have used all sorts of programs in different courses by the time of being introduced to Octave.

Dan


reply via email to

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