Re: Spreadsheet::WriteExcel port to PEAR

Hi all, > Hi, I sent you this mail to jonny@1409.org, but had no reply, so I'm sending > it here now: Sorry, I didn't have much time yesterday, but I really intended to reply the next days :-). Anyway now as there is a thread with some more people participating I'll answer to them all. And I also send this to the PEAR mailing list as I guess there is some public interest in it. > Your class seems to be complete and stable, so making a duplicate of it > would probably be a waste of time, but I still think there should be a PEAR > class for generating Excel files. Do you have any interest in making your > class compliant to the PEAR standards? If so, it would be great! Of course I try to make my code PEAR conformant. Whenever I clean up files, I'm also correcting the code to follow the PEAR coding standards. > If you don't have interest in the project, I would like to take advantage of > your work and make it PEAR compliant. I think some of the code I've done so > far can be used, although it's still not PEAR compliant itself, and far from > complete. If you want to take a look at it, it's in: > http://www.dcc.uchile.cl/~xnoguer/Spreadsheet_Excel/ > (It has some "issues" with Excel, I've done most of my testing with > StarOffice). I don't know if your files fit into the php_writeexcel structure. If they do and they are more PEAR compliant than my files, I'll put them in. Changing idents and other white space stuff is probably something I must do myself. Context diffs won't work here, so you can't do it while I'm working on other things. If you want to help out regarding PEAR compliance, the best job you can do is pointing out what must be changed for it apart from the coding standards. Somebody asked if rewriting the Excel classes from scratch wouldn't be the better solution as porting it from Perl means leaving a lot of perlism in it. I don't think so. The OOP specific stuff (if you really want to call Perl's bless mess OOP!) has already been rewritten - it wouldn't work with PHP otherwise... And regarding the call_user_method_array() stupidities: I think we *can* fix it. So what other perlisms will be there at the end? What I'm currently working on is the OLE stuff. The current version of php_writeexcel has OLE support of course. However this is the same highly simplified OLE stuff as found in SpreadSheet::WriteExcel which limits the maximum file size to about 7 MB. I have nearly completed a port of the OLE::Storage_Lite package to PHP. And if we want to compete with CPAN there should be two PEAR packages: ole and writeexcel. And as the ole stuff will also have read support, somebody should work on readexcel. :-) Btw, I have asked for including php_jh_pdf in PEAR some time ago, and some people agreed that this was an good idea telling me that I should get a PEAR CVS account. So could anybody tell be how I can actually get one? :-) Cheers, Jonny <jonny@1409.org>