phpbt-dev

[phpBT-dev] Time to update Pear:Spreadsheet:Excel?

[Ulf E. <ulf...@fa...>]

Benjamin,

Will you please take a look at updating the spreadsheet component? I 
have never used it.. (anyway, it looks to me as if you never used a 
PEAR_PATH for it. why?) Now, there is a report that says that you need 
an OLE component as well for newer versions (and you probably need a 
newer version for php5):
	http://sourceforge.net/forum/message.php?msg_id=2989428

Re: [phpBT-dev] Time to update Pear:Spreadsheet:Excel?

[Benjamin C. <php...@be...>]

You know, maybe we should just ditch the included PEAR code and depend
on it being available on the system.  It would make life easier for us,
at the expense of some users who don't have PEAR and can't easily
install it.

Ulf Erikson wrote:
> Benjamin,
> 
> Will you please take a look at updating the spreadsheet component? I
> have never used it.. (anyway, it looks to me as if you never used a
> PEAR_PATH for it. why?) Now, there is a report that says that you need
> an OLE component as well for newer versions (and you probably need a
> newer version for php5):
>     http://sourceforge.net/forum/message.php?msg_id=2989428
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev

Re: [phpBT-dev] Time to update Pear:Spreadsheet:Excel?

[Benjamin C. <php...@be...>]

Yeah, I can take a look at it.  To be perfectly honest, though, my
installation has been running just fine with PHP 5.0.3 and MySQL 4.1
with the antiquated PEAR code. :)  So, I won't see any change, even with
an upgrade to the PEAR stuff.

Ulf Erikson wrote:
> Benjamin,
> 
> Will you please take a look at updating the spreadsheet component? I
> have never used it.. (anyway, it looks to me as if you never used a
> PEAR_PATH for it. why?) Now, there is a report that says that you need
> an OLE component as well for newer versions (and you probably need a
> newer version for php5):
>     http://sourceforge.net/forum/message.php?msg_id=2989428
> 

Re: [phpBT-dev] Time to update Pear:Spreadsheet:Excel?

[Ulf E. <ulf...@fa...>]

* Benjamin Curtis [2005-05-31 02:12]:
> Yeah, I can take a look at it.  To be perfectly honest, though, my
> installation has been running just fine with PHP 5.0.3 and MySQL 4.1
> with the antiquated PEAR code. :)  So, I won't see any change, even with
> an upgrade to the PEAR stuff.

Hey! Since when are you running php5 and mysql 4.1? And how come you 
didn't tell me that things already worked before I start to hunt for 
possible problems ;-)

Anyway, I think you are using your system wide Pear install since there 
doesn't seem to be any PEAR_PATH in use for the Spreadsheet.

* Benjamin Curtis [2005-05-31 02:13]:
> You know, maybe we should just ditch the included PEAR code and depend
> on it being available on the system.  It would make life easier for us,
> at the expense of some users who don't have PEAR and can't easily
> install it.

That's perfectly okay with me. With instructions on where to download it 
and how to install it localy (by repeating the PEAR_PATH trick for 
people who cannot install it globaly) that wouldn't a problem.

Now, with php5 and mysql 4.1 working, (untested) updates for postgres 
and oracle in cvs, and logging of the install and update progress in 
cvs; How about bundling a new cvs "snapshot" and ask people to test 
things? I doubt a lot of people pull code from cvs to test..

Do you have ToDo list for the release? I'll see how much of my feature 
patches I can include (priorities in a table, (re)editable queries, 
bookmarks, and so on), but maybe you prefer help in some other area 
first? I see that the documentation is a bit behind, for instance.

Re: [phpBT-dev] Time to update Pear:Spreadsheet:Excel?

[Ben C. <php...@be...>]

A new release, RC6, has been made at the sourceforge site.  I haven't 
announced it via sourceforge to give the list members a chance to bang 
on it first. :)

As far as a TODO is concerned, all I care about before releasing 1.0 
final is getting everyone agreed that it runs on PHP5.  It would also be 
nice to update the docs and close some bugs, but that shouldn't hold us 
up.  I'd like to release 1.0 by July 4th.

Ulf Erikson wrote:
> * Benjamin Curtis [2005-05-31 02:12]:
> 
>> Yeah, I can take a look at it.  To be perfectly honest, though, my
>> installation has been running just fine with PHP 5.0.3 and MySQL 4.1
>> with the antiquated PEAR code. :)  So, I won't see any change, even with
>> an upgrade to the PEAR stuff.
> 
> 
> Hey! Since when are you running php5 and mysql 4.1? And how come you 
> didn't tell me that things already worked before I start to hunt for 
> possible problems ;-)
> 
> Anyway, I think you are using your system wide Pear install since there 
> doesn't seem to be any PEAR_PATH in use for the Spreadsheet.
> 
> * Benjamin Curtis [2005-05-31 02:13]:
> 
>> You know, maybe we should just ditch the included PEAR code and depend
>> on it being available on the system.  It would make life easier for us,
>> at the expense of some users who don't have PEAR and can't easily
>> install it.
> 
> 
> That's perfectly okay with me. With instructions on where to download it 
> and how to install it localy (by repeating the PEAR_PATH trick for 
> people who cannot install it globaly) that wouldn't a problem.
> 
> Now, with php5 and mysql 4.1 working, (untested) updates for postgres 
> and oracle in cvs, and logging of the install and update progress in 
> cvs; How about bundling a new cvs "snapshot" and ask people to test 
> things? I doubt a lot of people pull code from cvs to test..
> 
> Do you have ToDo list for the release? I'll see how much of my feature 
> patches I can include (priorities in a table, (re)editable queries, 
> bookmarks, and so on), but maybe you prefer help in some other area 
> first? I see that the documentation is a bit behind, for instance.
> 
ev