octave-maintainers
[Top][All Lists]
Advanced

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

Re: Release Ideas


From: Philip Nienhuis
Subject: Re: Release Ideas
Date: Tue, 27 Jan 2015 15:26:06 -0800 (PST)

John W. Eaton wrote
> It's been a long time since 3.8.0.
> 
> What's required for the gui-release branch to be released?  My list 
> really only has
> 
>    Use Qt widgets for plotting with the GUI
> 
> I've been working a little bit on adding buttons and making zooming work 
> with the mouse wheel.  I hope to push some changes for those things 
> later this week.

I haven't used the qt toolkit a lot as a number of things do not work yet;
panning is one of them.
But qt seems to work a lot faster and smoother than fltk.


> Beyond that, I think the GUI is in pretty good shape.  Sure, a lot of 
> issues have been reported, but I think it is more than usable at this
> point.

It absolutely is.


> I'd like to follow that release relatively soon with a release from what 
> is now the default branch because it has a lot more bug fixes that 
> should probably be in a released version of Octave.
> 
> What show-stopping bugs need to be fixed on either branch before we make 
> a release?

A serious issue for me is the OpenGL single precision. I often work with
time series from the late 19th century to date (datenum order ~ 733000) and
those time series get severely distorted due to insufficient precision.  See
bugs #40246, #33748 and #32980.

Default: as long as classdef is still experimental, not much.
Support for I/O of classdef objects in .mat files would be wonderful when
classdef gets more mature. But of course that's the wish list, not a
showstopper bug.

A while ago you mentioned you'd liked to have xlsread & xlswrite in core
Octave. I'm almost ready to amend the io package to make that happen, but I
could use some guidance; I've made some remarks and asked some questions in
the thread in question
(http://octave.1599824.n4.nabble.com/Spreadsheet-support-in-core-Octave-instead-of-io-package-tt4666947.html#a4666962).
One is what parts can go to core Octave first, what parts can follow later
and what parts should rather stay in the io package. 
Plus of course, from the POV of a package maintainer, how to manage io
package support for the then newest and older versions of Octave.

Philip




--
View this message in context: 
http://octave.1599824.n4.nabble.com/Release-Ideas-tp4668294p4668295.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.



reply via email to

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