[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: About the editor in Octave GUI
|
From: |
John W. Eaton |
|
Subject: |
Re: About the editor in Octave GUI |
|
Date: |
Sat, 14 Dec 2013 08:48:10 -0600 |
|
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:10.0.11) Gecko/20121123 Icedove/10.0.11 |
On 12/14/2013 08:01 AM, Pascal Dupuis wrote:
In order to be able to choose other editors, the actual code should be
rebuilt following a two-tier approach:
1) a direct interface for octave which is editor-agnostic
2) glue code in order to interface with specific editor, i.e.
translating the upper layer calls to according to the editor API.
This way, the interface for each specific editor would become a plugin.
Right, this is what I would like to do (because I would personally
like to be able to use Emacs as the GUI editor), but it won't happen
for the 3.8 release. Perhaps for 4.0.
Writing this plugin architecture is time and ressources consuming.
You are also correct that it will take time. Given that we already
have an editor that works, it is also a low priority item.
jwe