octave-maintainers
[Top][All Lists]
Advanced

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

Re: looking ahead to 3.6


From: Ryan Rusaw
Subject: Re: looking ahead to 3.6
Date: Tue, 15 Feb 2011 21:58:38 -0600

On Mon, Feb 14, 2011 at 12:51 PM, Przemek Klosowski
<address@hidden> wrote:
> On 02/14/2011 01:01 PM, Ryan Rusaw wrote:
>>
>> I'm the primary developer for Octclipse, I'm more than willing to work
>> with anyone interested in helping. The lack of activity springs
>> primarily from my lack of need, ie. I don't use Octave. I wrote it to
>> learn some things with Eclipse itself. Most of the development it sees
>> lately is when I periodically update the C++ interfaces to support
>> whatever changes in API octave has undergone since my last update.
>
> Aha, but you do follow the octave-maintainers' list :).
>
> What do you think are the advantages and disadvantages of your
> Octave/Eclipse GUI vs. other octave-specific projects like QtOctave and
> OctaveDE? Do you think there are any fundamental reasons one might be better
> than another--i.e. that you can't do certain things in X because of Y? On
> one hand, Eclipse has a lot of 'batteries included' modules, on the other
> hand custom GUI might have an easier time accessing large internal data
> structures, just because Eclipse is not designed to deal with such and may
> not have good facilities for them.
>

Advantages:

1. You get access to other plugins from the Ecliple ecosystem ie.
integrated version control, bugtracking, etc.

2. It integrates into a developers workflow easier if they already
using Eclipse for some other purpose already.

Disadvantages:

1. Licensing incompatability ensures the only way to integrate the two
will be at arms length through some form of IPC mechanism.

Ryan


reply via email to

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