Nabble - Pear - Dev

bugtrackers, was Re: [PHP-DEV] Towards 5.3.2

2009-12-10T07:33:23Z

Hi,

This is just a spin-off from an internals discussion. I moved this
pear-dev, to avoid noise on internals.

On Tue, Dec 8, 2009 at 3:30 PM, Tjerk Anne Meesters <datibbaw@...> wrote:
> Just out of curiosity, is there any open source bug tracker out there
> that would lend itself well to these needs? Currently the bug tracker
> is highly customized so when thinking about adding those new features,
> it may also be a good time to look around ;-)

Greg Beaver and I have been experimenting with a potential bugtracker
for use with PEAR2 and any other PEAR channel.

The project in pear2/BugManager has support for roadmaps, multiple
assignees, remote context validation, hard or soft linking between
bugs in different projects (PEAR bug depends on PHP bug) and some
other 'nice to haves.' This is a different approach than 'one
bugtracker to rule them all' — the goal of this is a per-project
bugtracker with the capability of linking bugs between different
instances.

Right now the UI still needs to be completed, adding some web
services, and authentication. Assistance would be appreciated.

I'm sure there are others out there, this is just the one we're
experimenting with.

--
Brett Bieber

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Deploying scheduled jobs with PEAR

2009-12-10T07:30:53Z

Hi,

Consider the situation where you have one or more applications installed using
PEAR, and each of them need to set up some scheduled jobs ("cron jobs").

Does anyone have a good existing solution for this using PEAR?

The logical way I can come up with doing it so far is this:

- create a new file role called "scheduledjob" or something, which
installs into a special directory

- define (by convention) that files installed using that role are in a
specific format (say, for example, the typical crontab format like
"*/5 * * * * php /path/to/script.php"). Naturally, these would almost
certainly need to be pre-processed with tasks:replace etc. to fill in the
file paths, php bin location etc.

- use a custom task to, on installation of a file with role "scheduledjob",
parse it and set up cron (or the equivalent on other platforms, e.g.
Windows Scheduled Tasks).

Is there any existing package to do the work within that latter point to set
up the job? I was looking for something like System_Cron or
System_ScheduledTask but didn't find anything. (If not, then it could
potentially be a new PEAR lib, for example System_ScheduledTask, with drivers
like System_ScheduledTask_Cron [possibly with several variants for the various
crons out there], System_ScheduledTask_Windows etc. I already have some sample
code for this for Linux crons.)

But does anyone have any other well-established solution to this? Even pearweb
just has the scripts in a directory called "cron", marked with role "www". As
far as I can tell, these have to be installed manually; there doesn't seem to
be anything in the post-installation tasks to do it.

N.B. I'm quite keen on using "standard" system schedulers rather than
solutions like "every X hits to my website, trigger some task" on the basis
that they are proven and don't rely on some external mechanism.

Thanks,

Tim

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PEPr] Changes in proposal for Web Services::Services_Digg2

2009-12-07T13:01:47Z

Bill Shupp (http://pear.php.net/user/shupp) has edited the proposal for Web Services::Services_Digg2.

Change comment:

* Moved from Validate to filter_var (thanks bbieber!)

* Cleaned up some dependency info

Please review the proposal:
http://pear.php.net/pepr/pepr-proposal-show.php?id=622

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PEPr] Proposal for Web Services::Services_Digg2

2009-12-07T10:34:17Z

Bill Shupp (http://pear.php.net/user/shupp) proposes Web Services::Services_Digg2.

You can find more detailed information here:
http://pear.php.net/pepr/pepr-proposal-show.php?id=622

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Pyrus bug during installation of Spreadsheet_Excel_Writer 0.9.2

2009-12-05T07:46:59Z

On Sat, Nov 28, 2009 at 2:08 AM, Christian Weiske <cweiske@...> wrote:

> I'm getting an error when trying to install the dev test version of
> SpreadSheet_Excel_Writer 0.9.2 - it seems to simply hang after that,
> with 100% CPU utilization and eating memory.
>
> cweiske:~/tmp>
> php-5.3.1 ../Dev/cvs/pear/pear2/Pyrus/trunk/PEAR2_Pyrus-2.0.0a1.phar
> install ../Spreadsheet_Excel_Writer-0.9.2.tgz Pyrus version 2.0.0a1
> SHA-1: 43AA5C4003AAE68426323C00225A9EDAB0E774FB Using PEAR installation
> found at /home/cweiske/Dev/cvs/pear/instpear2
>
> Warning: call_user_func_array() expects parameter 1 to be a valid
> callback, class 'pear2\Pyrus\PackageFile\v2' does not have a method
> 'resetConcreteVersion' in
> phar:///home/cweiske/Dev/cvs/pear/pear2/Pyrus/trunk/PEAR2_Pyrus-2.0.0a1.phar/PEAR2_Pyrus-2.0.0a1/php/pear2/Pyrus/Package/Base.php
> on line 208

Looks like there are two issues here. We should only call
resetConcreteVersion(); if the package is remote.

I believe the infinite loop is caused by no compatible versions
matching the preferred_state being available for a dependency. An
exception should be thrown somewhere which states this... before the
infinite loop of course.

As a workaround you can use:
php pyrus.phar set preferred_state alpha
php pyrus.phar install ../Spreadsheet_Excel_Writer-0.9.2.tgz

--
Brett Bieber

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Pyrus bug: info is too short

2009-12-05T06:44:57Z

On Sat, Nov 28, 2009 at 2:04 AM, Christian Weiske <cweiske@...> wrote:
> Hi,
>
>
> Since we have no bug tracker yet for pyrus:
> The description is too short when using "info", it tells me to use info.

Fixed in SVN. Thanks for the note Christian.

--
Brett Bieber

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PEAR-QA] Re: Mail_MIME

2009-12-03T14:44:52Z

Hey Alec,
You're ticking all of the boxes to get a +1 from me.

Re #12411 and it being a bulk patch, it might be worth splitting up
back into specific fixes - ie; it's hard for me as a QA person to
assertain exactly what kind of regression hell might be unleashed by
solving 5 bugs at once, and it's unclear if there's specific
individual test coverage (though my review was cursory).

Unfortunately with Mail_MIME, since it's not unmaintained, all PEAR QA
can really do is hassle out the authors on your behalf.

*NUDGE*
walter/cipri
*/NUDGE*

What will probably happen next - walter / cipri give you a +1 as well,
add you as a developer, and ask you to apply for an SVN account -
http://www.php.net/svn.php

Someone in PEAR group will then grant you karma for the specific package.

This might all take a while (the wheels can turn a little slowly), so
hang in there!

On Fri, Dec 4, 2009 at 12:09 AM, A.L.E.C <alec@...> wrote:
> A.L.E.C wrote:
>>
>> I don't use main Mail package.
>
> Sorry, of course I do use it in LMS, but now it's not priority for me. Maybe
> later.
>

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PEPr] Proposal for Web Services::Services_Memotoo

2009-12-03T10:23:22Z

Pequet Thomas (http://pear.php.net/user/memotoo) proposes Web Services::Services_Memotoo.

You can find more detailed information here:
http://pear.php.net/pepr/pepr-proposal-show.php?id=620

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Status of Spreadsheet_Excel_Writer: Very bad

2009-12-03T04:03:53Z

Hello!

I just wanted to give a feedback on Spreadsheet_Excel_Writer.

We have now released a new version of Spreadsheet_Excel_Writer which
makes it at least usable for most simple tasks with BIFF8.

However when trying to fix a couple more bugs I realized the following
facts:

Spreadsheet_Excel_Writer is hopelessly outdated. At the time it was
created very little was known about the Excel format and so the whole
structure of the package does reflect that. Fixing the most simple
things, like formulas etc. or this one:
http://pear.php.net/bugs/bug.php?id=2146 would need a complete rewrite
of the internal procedures since the current package does not really
know how an Excel file is structured. Something I would not be able to
do (because it would cost _alot_ of time) and considering the fact that
there is a pretty decent PHP Excel package out there (PHPExcel), it is
very unlikely that anyone will do it.

When I took over the package I was hoping that only applying patches by
the users and a couple intensive debugs would fix the problems - only
after alot of insight into the package I found out the things above.

Under these circumstances I would recommend to put this package out of
its misery and mark it as deprecated.

If you have any questions or comments please let me know.

Best regards

Carsten Schmitz

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PEPr] Comment on Math::Math_Assoc

2009-12-02T11:49:20Z

Some comments:

- For finding roots and evaluating equations, Math_Numerical_RootFinding
already provides much of this functionality.

- For number conversion, Number_Roman already provides this.

- Math_Fraction already provides lcd / gcm

- Math_Polynomial already provides some of the other features.

- flip_sign, is_positive, is_negative, is_null all seem pretty useless;
what's wrong with if ($num < 0)?

- {...} syntax for square root seems a bit odd.

--
http://pear.php.net/pepr/pepr-proposal-show.php?id=619

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PEPr] Comment on Math::Math_Assoc

2009-12-02T11:24:45Z

On Wed, Dec 2, 2009 at 8:17 PM, Philippe Jausions <pear@...> wrote:
> (...)
> - Use func_get_args() to eliminate duplicate functions gcm(), gcm_mult()
> and so forth

Or __call().

(Make sure to use the phpdoc for magic methods to document all.)

Till

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PEPr] Comment on Math::Math_Assoc

2009-12-02T10:17:44Z

Couple of comments.

- Avoid using the PHP license. MIT, LGPL, New BSD etc are preferred ones

- The existing Number_Roman package already handles the Roman to Arabic
conversion

- Package should be PHP 5+

- Put the code of your package directly viewable online

- Use func_get_args() to eliminate duplicate functions gcm(), gcm_mult()
and so forth

- function names should be camelCase isPositive() vs is_positive()

I don't know what your date and conversion functions do, but they
shouldn't be in the same package as an equation-related one.

--
http://pear.php.net/pepr/pepr-proposal-show.php?id=619

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PEPr] Proposal for Math::Math_Assoc

2009-12-02T09:07:31Z

Bogomil Gospodinov (http://pear.php.net/user/azerot) proposes Math::Math_Assoc.

You can find more detailed information here:
http://pear.php.net/pepr/pepr-proposal-show.php?id=619

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PEPr] Comment on HTML::MetaTags

2009-12-01T06:23:16Z

This is a handy package. I've got some feedback:

1.) consisify between camelCase and under_scores. The camelCase style is
preferred.

2.) Document the available options in the class constructor in the method
docblock.

3.) documentation should use the 3rd person declarative rather than the
2nd person imperative in documentation. "Sets the foo" rather than "Set
foo". See http://pear.php.net/manual/en/standards.sample.php

4.) consistify between single quoted strings and double quoted.
Single-quoted is preferred.

5.) The regular expression has the punctuation characters hard-coded when
it appears you can specify them in the constructor.

6.) Lines should be at most 85 characters long.

7.) consider only using mb_strlen(), mb_strtolower(), etc if the functions
are avialable That way installations that don't have mb_string can still
use the package.

8.) stripText() could be simplified by using a regular expression.

9.) Package doesn't generate any HTML. I recommend renaming to
Text_Metadata or Text_MetaTags

10.) The use of the PHP license is discouraged. Consider BSD, Apache2 or
MIT instead.

11.) try running the code through phpcs (PHP_CodeSniffer)

12.) Min PHP version in package.xml is too low. At least PHP 5 is
required.

13.) This package is a great cantidate for unit testing. Consider adding
some tests to the proposal.

--
http://pear.php.net/pepr/pepr-proposal-show.php?id=618

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: QR_Img (barcodes) - proposal

2009-11-29T04:52:15Z

Hi Ken, David,

Great - thanks for both of your replies re the package, and apologies for
the delay in replying :-)

David - I'll get to work on restructuring both the package layout and the
code itself. Could you possibly let me know what you'd recommend in terms
of the PHP4-PHP5 changes? I'll switch to the array of options in the
constructor or similar as well.

Thanks again :-)

Rich

On Thu, Nov 26, 2009 at 8:53 AM, Ken Guest <ken@...> wrote:

> On Wed, Nov 25, 2009 at 8:10 PM, Rich Sage <rich.sage@...> wrote:
> > Hi all,
> >
> > I'd like to propose a package for inclusion in PEAR - the package is
> > currently titled "QR_Img" and is for generation of QR (2-dimensional)
> > barcode images. The original code was by Y.Swetake, and he's happy for
> it
> > to be packaged up and made available to more developers; I've just
> > restructured it into a class and with adherence to the coding standards
> etc.
> >
> > I understand it's best to mention the proposal on pear-dev before
> submitting
> > an "official" proposal (I wasn't able to do that anyway, the PEAR site
> > informed me I had insufficient privileges on my account for this!) -
> would
> > this package be of interest? I'd envisage it sitting within the Images
> > category, although if another one is more suitable please let me know!
> >
>
>
> Hi Rich,
> one of my compatriots on the PEAR Group has given you pepr access -
> this means you are
> now enabled for making a package proposal.
>
> k.
> --
> http://blogs.linux.ie/kenguest/
>

--
Rich Sage
Oxford, UK
rich.sage@...

Re: PHPTAL package name

2009-11-29T03:39:47Z

Kornel Lesiński wrote:

> On 28.11.2009, at 11:17, till wrote:
>>
>> Afaik, no. But feel free to go on IRC to ask.
>>
>> IMHO, the change is not so huge:
>>
>> require_once 'HTML/Template/PHPTAL.php';
>> $phptal = new HTML_Template_PHPTAL('my_template_file.xhtml');
>
>
> It also affects base classes for pre/post filters, translation service, custom attributes, and probably prefix of functions for custom expression modifiers. In latest version I've exposed PHPTAL's DOM with dozen of PHPTAL_Dom_* classes.
>
> I'm not keen on having 3 times longer prefix.
>
> Can PEAR2 packages be published yet?

Yes. You should expect them to be alpha stability at least until pyrus
is officially released (still need some bodies to work on the bug tracker)

Greg

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: PHPTAL package name

2009-11-28T08:07:18Z

2009/11/28 Kornel Lesiński <kornel@...>:

Yeah, I think especially Brett would be happy to help you. ;)

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PEAR-QA] about a new Archive_Tar release

2009-11-28T07:23:39Z

On Wed, Nov 25, 2009 at 1:34 PM, Michiel Rook <michiel.rook@...>wrote:

> Hi all,
>
> I've been able to close a few bugs since taking over maintenance of
> Archive_Tar, preparing a new release is something that has slipped through
> the cracks unfortunately (sorry about that!)
>
> Now that I have some time to spend on that, I'm thinking about marking the
> next release 'beta'. Even though I'm pretty confident about my fixes,
> Archive_Tar is an essential package.
>
> Any thoughts?
>
> regards,
>
> Michiel
>

Hey Michiel,

Releasing an alpha or beta is certainly an option that's up to you, as the
maintainer. If you've made any changes that aren't *strictly* bug fixes,
then an X.Y release number bump, and an alpha or beta stability, are
certainly the way to go. Whenever I do an X.Y bump for a stable package, I
typically do release at least one alpha and one RC beta before a final
stable.

It's not *customary* to mark an X.Y.Z bump as beta if it's part of an
already stable X.Y, but I don't think there are any *guidelines* against
it. I think you'll be fine to do so.
--
CRB

about a new Archive_Tar release

2009-11-28T06:43:56Z

Hi all,

I've been able to close a few bugs since taking over maintenance of
Archive_Tar, preparing a new release is something that has slipped
through the cracks unfortunately (sorry about that!)

Now that I have some time to spend on that, I'm thinking about marking
the next release 'beta'. Even though I'm pretty confident about my
fixes, Archive_Tar is an essential package.

Any thoughts?

regards,

Michiel

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: PHPTAL package name

2009-11-28T06:31:58Z

On 28.11.2009, at 11:17, till wrote:
>
> Afaik, no. But feel free to go on IRC to ask.
>
> IMHO, the change is not so huge:
>
> require_once 'HTML/Template/PHPTAL.php';
> $phptal = new HTML_Template_PHPTAL('my_template_file.xhtml');

It also affects base classes for pre/post filters, translation service, custom attributes, and probably prefix of functions for custom expression modifiers. In latest version I've exposed PHPTAL's DOM with dozen of PHPTAL_Dom_* classes.

I'm not keen on having 3 times longer prefix.

Can PEAR2 packages be published yet?

--
regards, Kornel

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Re: New release of Spreadsheet_Excel_Writer?

2009-11-28T04:59:27Z

Hi Christian,

Thank you for your comments.

>> Fixed a huge number of wrong MIME types.
> which applied only to the SVN settings; it is irrelevant to the users.

Ok, will take that one out.

>> --Fixed bug #2405: Text concat operator & truncate ..
>> +-Fixed bug #2405: Text concat operator and truncate ..
> Using & is possible - since it's xml, escape the & as "&".

Thank you ;)
>
>> dev Added missing file to package.xml
>> + <file name="OLEwriter.php" role="php" />
> Strangely, this file has been around for nearly 7 years but was not in
> the last version of SEW. There is also an own OLE package in PEAR as I
> see, but without that file. Is it in use at all?

I guess not. Will take it out after I can confirm it.

> There is at least one log entry that is not in the changelog:
>> Fix Bug #14587: tmpfile() used despite setTempDir() [sberg]

Yes, I left it out because it relates to a new feature, so it is a fix
for something that did not exist in the last version anyway and
therefore imho obsolete (doesn't mean I appreciate the effort ;)

>
> Please fill in the release notes of 0.9.1's changelog entry. They are
> missing now.

Will do.

> The package.xml is valid, even after Pyrus standards, which is great.
>
>
> Btw, it was a very good idea to ask for comments before the release.
> Other people do not do that and release the same version 6 times.

Thank you again!

Best regards
Carsten

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: PHPTAL package name

2009-11-28T03:17:29Z

On Fri, Nov 27, 2009 at 11:01 AM, Kornel Lesinski
<kornel@...> wrote:

> On 26 Nov 2009, at 18:23, till wrote:
>
>> you are correct, changing the packagre name requires changing the
>> class names and possibly the file structure in your VCS
>> (HTML/Template/PHPTAL.php, etc.).
>>
>> I don't know about the upgrade procedure for your existing users, but
>> my guess is that if they use a pear-install already, the "new" package
>> name would hint at a totally new package for the user. E.g. if they
>> did pear install PHPTAL before, they now need to do pear install
>> HTML_Template_PHPTAL.
>
> That's not good. That means not only reinstall, but also changes in users'
> code.
>
>> Let me know if this answers your question.
>
>
> I'd like to know if "PHPTAL" is acceptable as package name?
>

Afaik, no. But feel free to go on IRC to ask.

IMHO, the change is not so huge:

require_once 'HTML/Template/PHPTAL.php';
$phptal = new HTML_Template_PHPTAL('my_template_file.xhtml');

Till

Till

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Re: New release of Spreadsheet_Excel_Writer?

2009-11-28T00:09:08Z

Hello Carsten,

> I have fixed a last bug, update the package.xml and now packaged a
> new version of which is downloadable at
> http://www.limesurvey.org/Spreadsheet_Excel_Writer-0.9.2.tgz to be
> checked out.
Great to hear from you, and even greater that Spreadsheet_Excel_Writer
will get a new release!
You do have a release note
> Fixed a huge number of wrong MIME types.
which applied only to the SVN settings; it is irrelevant to the users.

> --Fixed bug #2405: Text concat operator & truncate ..
> +-Fixed bug #2405: Text concat operator and truncate ..
Using & is possible - since it's xml, escape the & as "&".

> dev Added missing file to package.xml
> + <file name="OLEwriter.php" role="php" />
Strangely, this file has been around for nearly 7 years but was not in
the last version of SEW. There is also an own OLE package in PEAR as I
see, but without that file. Is it in use at all?

There is at least one log entry that is not in the changelog:
> Fix Bug #14587: tmpfile() used despite setTempDir() [sberg]

Please fill in the release notes of 0.9.1's changelog entry. They are
missing now.

The package.xml is valid, even after Pyrus standards, which is great.

Btw, it was a very good idea to ask for comments before the release.
Other people do not do that and release the same version 6 times.

--
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

signature.asc (205 bytes) Download Attachment

Pyrus bug during installation of Spreadsheet_Excel_Writer 0.9.2

2009-11-28T00:08:39Z

Hi,

I'm getting an error when trying to install the dev test version of
SpreadSheet_Excel_Writer 0.9.2 - it seems to simply hang after that,
with 100% CPU utilization and eating memory.

cweiske:~/tmp>
php-5.3.1 ../Dev/cvs/pear/pear2/Pyrus/trunk/PEAR2_Pyrus-2.0.0a1.phar
install ../Spreadsheet_Excel_Writer-0.9.2.tgz Pyrus version 2.0.0a1
SHA-1: 43AA5C4003AAE68426323C00225A9EDAB0E774FB Using PEAR installation
found at /home/cweiske/Dev/cvs/pear/instpear2

Warning: call_user_func_array() expects parameter 1 to be a valid
callback, class 'pear2\Pyrus\PackageFile\v2' does not have a method
'resetConcreteVersion' in
phar:///home/cweiske/Dev/cvs/pear/pear2/Pyrus/trunk/PEAR2_Pyrus-2.0.0a1.phar/PEAR2_Pyrus-2.0.0a1/php/pear2/Pyrus/Package/Base.php
on line 208

--
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

signature.asc (205 bytes) Download Attachment

Pyrus bug: info is too short

2009-11-28T00:04:46Z

Hi,

Since we have no bug tracker yet for pyrus:
The description is too short when using "info", it tells me to use info.

cweiske:~/tmp>
php-5.3.1 ../Dev/cvs/pear/pear2/Pyrus/trunk/PEAR2_Pyrus-2.0.0a1.phar
info ../Spreadsheet_Excel_Writer-0.9.2.tgz Pyrus version 2.0.0a1 SHA-1:
43AA5C4003AAE68426323C00225A9EDAB0E774FB Using PEAR installation found
at /home/cweiske/Dev/cvs/pear/instpear2 Spreadsheet_Excel_Writer
(pear.php.net Channel)
--------------------------------------------------------------------------------
Package type: PHP package Version: 0.9.2 (API 0.9.1),
Stability: beta (API beta) Release Date: 2009-11-28 01:28:34 Package
Summary: Package for generating Excel spreadsheets Package Description
Excerpt: Spreadsheet_Excel_Writer was born as a porting of the
Spreadsheet::WriteExcel Perl module to PHP.
It allows writing of Excel spreadsheets without the need for COM
object... (info ../Spreadsheet_Excel_Writer-0.9.2.tgz description for
full description) Release Notes Excerpt:

+Added feature: setTmpDir property for people that have
openbase_dir. (dufuz) -Fixed bug #14932: The name of the Workbook
stream MUST be "Workbook", not "Book" (progi1984...
(info ../Spreadsheet_Excel_Writer-0.9.2.tgz notes for full release
notes)

--
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

signature.asc (205 bytes) Download Attachment

Re: Re: New release of Spreadsheet_Excel_Writer?

2009-11-27T16:36:13Z

Hi everyone,

I have fixed a last bug, update the package.xml and now packaged a new
version of which is downloadable at
http://www.limesurvey.org/Spreadsheet_Excel_Writer-0.9.2.tgz to be
checked out.

I tested various configurations (that's how I found the last minute
open_base_dir problem) with the installed package. I also checked the
documentation and found it still to be correct and working in this
latest version of the package.
To not delay a release any further I have passed the option to include
sample code in the package this time. I agree that for future release
this would be great and we will be doing this for sure.

Please check out the package. Thank you!

Best regards

Carsten Schmitz

Christian Weiske schrieb:

> Hello Franck,
>
>
>>> I think it would be great if you could push out a new release of
>>> Spreadsheet_Excel_Writer - you fixed some
>>> bugs, and some others have been fixed in the last years, too [1].
>> Why not ? But just a beta ? What is the procedure for releasing .
>
> Up to now, SEW is beta software - and keeping that would be fine and
> I'd do the same.
> The procedure for releasing:
> - Update package.xml with the latest release notes. I already started
> that when I submitted your patches. Use the Closed-since-last-release
> link in the bugtracker to complete the task. Updating version number
> is already done
> - Copy release notes to changelog in package.xml, add yourself as lead.
> - package the package: $ pear package
> - Try to install it via pear (pear install packagename.tgz)
> - Run some scripts using the package from your home dir or any other
> dir except the svn src dir so in every case you get the installed
> version of the SEW files.
> - See that everything is fine
> - Upload the package to some temporary location where I and other devs
> can check it and try it out
> - Once we give green light, go to pear.php.net -> developers -> upload
> release and release the package
>
> I suggest you add some examples to the package. Look at
> Text_Figlet to see how to add them to your package (directory-wise in
> svn: docs/examples and in package.xml).
>
> Those examples should be available and runnable when you installed the
> package. (pear list-files Spreadsheet_Excel_Writer)
>
>
>> An another point :
>> I am in holidays the next week for four weeks (and nearly not access
>> to web) or the next week after the next week for three weeks (I don't
>> remember). What is the procedure in this case ?
> Send an e-mail to QA that you're away for some weeks and all is fine.
>
>
> [1]
> http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Spreadsheet_Excel_Writer&status=CRSLR
>

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: PHPTAL package name

2009-11-27T02:01:18Z

On 26 Nov 2009, at 18:23, till wrote:

> you are correct, changing the packagre name requires changing the
> class names and possibly the file structure in your VCS
> (HTML/Template/PHPTAL.php, etc.).
>
> I don't know about the upgrade procedure for your existing users, but
> my guess is that if they use a pear-install already, the "new" package
> name would hint at a totally new package for the user. E.g. if they
> did pear install PHPTAL before, they now need to do pear install
> HTML_Template_PHPTAL.

That's not good. That means not only reinstall, but also changes in
users' code.

> Let me know if this answers your question.

I'd like to know if "PHPTAL" is acceptable as package name?

--
regards, Kornel

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: PHPTAL package name

2009-11-26T10:23:56Z

Hey Kornel,

you are correct, changing the packagre name requires changing the
class names and possibly the file structure in your VCS
(HTML/Template/PHPTAL.php, etc.).

I don't know about the upgrade procedure for your existing users, but
my guess is that if they use a pear-install already, the "new" package
name would hint at a totally new package for the user. E.g. if they
did pear install PHPTAL before, they now need to do pear install
HTML_Template_PHPTAL.

Let me know if this answers your question.

Till

On Thu, Nov 26, 2009 at 5:41 PM, Kornel Lesinski
<kornel@...> wrote:

> Hello, any advice on this?
>
> On 10 Nov 2009, at 23:41, Kornel Lesiński wrote:
>
>> I've been informed on #pear that PHPTAL package should be renamed to
>> HTML_Template_PHPTAL. That category definitely suits the project, but as far
>> as I'm aware, this also requires change of package name and class names.
>>
>> Just change of package name doesn't sound very bad, it'll only require
>> existing pear users to uninstall old package first (right?), but change of
>> class name prefix seems very disruptive to me. It would require changes not
>> only all over PHPTAL codebase, but also in all existing PHPTAL-based
>> projects/framework adapters and some 3rd party extensions.
>>
>> I could provide wrappers or dummy classes that inherit new ones under old
>> names, but that would be messy and nearly double number of files that have
>> to be loaded (startup performance is PHPTAL's weak point already, and I
>> don't want PHPTAL to be perceived as bloated and high overhead).
>>
>> Also, without real namespaces class names that are already overly long
>> (e.g. PHPTAL_Php_Attribute_TAL_Condition) would get even longer. Some of
>> those classes are visible to users.
>>
>>
>> I wouldn't mind renaming classes when migrating to PEAR2. With real
>> namespaces these problems are minuscule.
>>
>>
>> So my questions are:
>>
>> Is it possible to have "PHPTAL" package in HTML/Template category? or
>> HTML_Template_PHPTAL package that uses only PHPTAL as class name prefix?
>> Can renaming be deferred until PEAR2?
>
> --
> regards, Kornel
>
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

PHPTAL package name

2009-11-26T08:41:36Z

Hello, any advice on this?

On 10 Nov 2009, at 23:41, Kornel Lesiński wrote:

> I've been informed on #pear that PHPTAL package should be renamed to
> HTML_Template_PHPTAL. That category definitely suits the project,
> but as far as I'm aware, this also requires change of package name
> and class names.
>
> Just change of package name doesn't sound very bad, it'll only
> require existing pear users to uninstall old package first (right?),
> but change of class name prefix seems very disruptive to me. It
> would require changes not only all over PHPTAL codebase, but also in
> all existing PHPTAL-based projects/framework adapters and some 3rd
> party extensions.
>
> I could provide wrappers or dummy classes that inherit new ones
> under old names, but that would be messy and nearly double number of
> files that have to be loaded (startup performance is PHPTAL's weak
> point already, and I don't want PHPTAL to be perceived as bloated
> and high overhead).
>
> Also, without real namespaces class names that are already overly
> long (e.g. PHPTAL_Php_Attribute_TAL_Condition) would get even
> longer. Some of those classes are visible to users.
>
>
> I wouldn't mind renaming classes when migrating to PEAR2. With real
> namespaces these problems are minuscule.
>
>
> So my questions are:
>
> Is it possible to have "PHPTAL" package in HTML/Template category?
> or HTML_Template_PHPTAL package that uses only PHPTAL as class name
> prefix?
> Can renaming be deferred until PEAR2?

--
regards, Kornel

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: QR_Img (barcodes) - proposal

2009-11-26T00:53:16Z

On Wed, Nov 25, 2009 at 8:10 PM, Rich Sage <rich.sage@...> wrote:

> Hi all,
>
> I'd like to propose a package for inclusion in PEAR - the package is
> currently titled "QR_Img" and is for generation of QR (2-dimensional)
> barcode images. The original code was by Y.Swetake, and he's happy for it
> to be packaged up and made available to more developers; I've just
> restructured it into a class and with adherence to the coding standards etc.
>
> I understand it's best to mention the proposal on pear-dev before submitting
> an "official" proposal (I wasn't able to do that anyway, the PEAR site
> informed me I had insufficient privileges on my account for this!) - would
> this package be of interest? I'd envisage it sitting within the Images
> category, although if another one is more suitable please let me know!
>

Hi Rich,
one of my compatriots on the PEAR Group has given you pepr access -
this means you are
now enabled for making a package proposal.

k.
--
http://blogs.linux.ie/kenguest/

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: QR_Img (barcodes) - proposal

2009-11-26T00:46:32Z

Hi Rich

Yeah it would be great to have this package in PEAR, we'll give you
karma to make the proposal ASAP.
> I've made my code available at http://code.google.com/p/pearqrcode/ if
> that's of use for information etc. Any pointers welcome! :-)
>
>

I've briefly looked at the code, some notes:

1. the package should be called Image_QRCode I think, or maybe it could
be a driver of Image_Barcode (this package is not maintained and php4
though, so it's not a good idea...)
2. your package layout should look like this:

Image_QRCode
|-- Image
| |-- QRCode
| | `-- Exception.php
| `-- QRCode.php
|-- doc
|-- package.xml
`-- tests

3. we only accept php5 code, the code is still php4-ish

4. the makecode() method is *huge*. Definitively, it should be splitted
in several methods to make the code more maintainable.

5. I think the public API could be better (I don't like the set*()
methods, I'd prefer to pass an array of options in the constructor or
the makecode() method)

6. there's no tests, no doc, no examples, no package.xml

That's all for now ;)

--
David Jean Louis <izimobil@...>

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

QR_Img (barcodes) - proposal

2009-11-25T12:10:52Z

Hi all,

I'd like to propose a package for inclusion in PEAR - the package is
currently titled "QR_Img" and is for generation of QR (2-dimensional)
barcode images. The original code was by Y.Swetake, and he's happy for it
to be packaged up and made available to more developers; I've just
restructured it into a class and with adherence to the coding standards etc.

I understand it's best to mention the proposal on pear-dev before submitting
an "official" proposal (I wasn't able to do that anyway, the PEAR site
informed me I had insufficient privileges on my account for this!) - would
this package be of interest? I'd envisage it sitting within the Images
category, although if another one is more suitable please let me know!

I've made my code available at http://code.google.com/p/pearqrcode/ if
that's of use for information etc. Any pointers welcome! :-)

Thanks in advance,

Rich.

--
Rich Sage
Oxford, UK
rich.sage@...

Re: Class multiCurl

2009-11-22T16:41:50Z

Here's what I don't understand: if PHP5 already has a "MULTI CURL"
API, why is a wrapper needed? If "MULTI CURL"'s built-in interface
needs to have a wrapper what about this MultiCurl class library? Is
PEAR going to start including wrappers for wrappers in it as well?
Where do you draw the line?

If this wrapper offered some sort of compatibility layer (ie. a
fallback pure-PHP option for those who don't have the MULTI CURL
extension installed) or if it offered some sort of non-trivial new
functionality, that'd be one thing, but near as I can tell, this
doesn't do any of that.

On Sun, Nov 22, 2009 at 2:55 PM, Dexter Wayne <randotom@...> wrote:
> I developed MultiCurl class library is a PHP5 solution for work with MULTI
> CURL extension and would like to include in the PEAR.
> See attachment.
>
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: QuickForm2 - ho

2009-11-22T13:05:50Z

Hi Alain,

On Fri, 20 Nov 2009 12:55:29 +0000, Alain Williams <addw@...>
wrote:
> I have found that this does not do what I want:
> $tue->setAttribute('checked');

When you add an element to the form or add a datasource to the form with
element added, element will update its value from this datasource
overwriting whatever you set it to previosly.

> I would like to add them all at once:
> $form->addElement('radio', 'Weekdays', array('value' => $d),
> array('label' => "Day $day", 'content' => "content: $d",
> 'options' => $Wdays));
> .... later on specify default:
> $form->addDataSource(new
> HTML_QuickForm2_DataSource_Array('Weekdays' => 'Tue'));
>
> Can I already do something like that ?

You'll have to use a loop to add radios, but addDataSource() call should
work as expected.

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Class multiCurl

2009-11-22T12:55:22Z

I developed MultiCurl class library is a PHP5 solution for work with MULTI CURL extension and would like to include in the PEAR.

See attachment.

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

multiCurl.tgz (5K) Download Attachment