Hi Benjamin:

Benjamin Lindner wrote:
> Philip Nienhuis wrote:
>>
>> Hopefully the next windows binary has an up-to-date octave-forge. 
>> That's the binary used mainly by folks who don't do svn...
> 
> Do you have a particular package or specific patch in mind?
> I can include a post-release version of an octave-forge
> package in the binary installer.
> I haven't done this as standard, only when the last available
> released package did not build cleanly.

Windows package:
----------------
For the Excel .xls stuff that I plan to upload soon *), an up-to-date
version of the windows package is needed for proper ActiveX /COM
supported Excel I/O.
A while ago I've contributed a small but fairly essential patch for
__com__.cc that Michael Goffioul already applied in svn.

Java package:
-------------
I found that on Mandriva Linux (2009.0), the Java-1.2.5 package will do
for the Java-supported Excel I/O.
But last September Michael Goffioul has sent me an updated Java-1.2.6
package so I *guess* that for Windows/MingW the latest svn patches for 
the Java package are also needed.

So all in all, including updated Windows and Java packages in a new
MingW binary would be great for those people needing Excel .xls file
support in octave.

Will you include those in a next Windows/MingW binary (3.2.4)?
Because, as the Excel stuff is probably only alpha at present, I might 
need some time for bug-fixing & refinement based on more knowledgeable 
users' (than me) comments before it's put into an official Windows/MingW 
binary.


*) Hopefully this weekend I'll be able to master svn sufficiently for
uploading the whole stuff.

As to current Excel .xls r/w development status:

I plan to put all Excel r/w & support scripts + doc (currently 15 files;
sorry) in the I/O package on octave-forge.
I've contacted Alois Schloegl about his (outdated) xlsread.m. IMO it had
better be removed as AFAICS csvread.m & dlmread.m have more flexible
functionality; but I'll simply rename it to xlsread-old.m if you don't mind.
Some functionality of Apache POI doesn't work when invoked from octave, 
notably Excel formula evaluation and OOXML initialization. I don't know 
where the problem lies (octave/java? or Apache POI?). Anyway I've also 
implemented JExcelAPI now and that seems to work OK (but sometimes slow, 
a factor of 5-20 (!) compared to ActiveX/COM/native Excel, largely 
depending on Excel formula complexity).

Thank you,

Philip

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to