Bakir Hassani | 1 Jan 11:02 2008

Re: Problem creating an acount to submit a proposal

Hello,

"Mark Wiesemann wrote

> Please read the whole page. On top you can find this sentence:
> | You have chosen to request an account for proposing a new (and 
> *complete*)
> | package for inclusion in PEAR.
>
> Do you notice a difference between the text behind the checkbox and this
> sentence? ;-)

I can blame my poor English here ;-)

> The second error message is related to the "Solve the problem:" field.

Maybe I should reconsider my priorities and develop my basic mathematics 
skill before developing code for Pear ;-)

Well, I do not think that form will get good scores at usability tests, btw 
it could benefit from javascript functions to validate form fields client 
side.

Thank you

Bakir Hassani 

--

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

Bakir Hassani | 1 Jan 11:16 2008

Re: Re: Problem creating an acount to submit a proposal

Hello,

David Coallier wrote
>
> Few points you have to fix.
>
> 1. Make that php5

OOP_Template performs better with php5 due to better object handling as I 
noticed in some benchmarks I did, but what about

support for php4?

> 2. Use proper naming (Prefix with PEAR_ your class name)
> 3. Read the coding standards

In fact that online files are the pre-draft of the package and links to them 
showed by mistake on my first message

> 4. Add more benchmark, from looking at that code it doesn't seem
> faster than what's out there. Do we really need another templating
> engine ? Have you looked at Sigma, Flexy, PHPLIB, Xipe ? Can you put
> benchmark up there

I did some benchmark and it is about three times faster than Template_IT in 
reading and initializing blocks tree ...

benchmarks will be published when proposing package
OOP_Template has a different approach to templates, it somehow treats 
template like a DOM, and it is extensible, indeed I have
(Continue reading)

Bakir Hassani | 1 Jan 11:16 2008

Re: Re: Problem creating an acount to submit a proposal

Hello,

David Coallier wrote
>
> Few points you have to fix.
>
> 1. Make that php5

OOP_Template performs better with php5 due to better object handling as I 
noticed in some benchmarks I did, but what about

support for php4?

> 2. Use proper naming (Prefix with PEAR_ your class name)
> 3. Read the coding standards

In fact that online files are the pre-draft of the package and links to them 
showed by mistake on my first message

> 4. Add more benchmark, from looking at that code it doesn't seem
> faster than what's out there. Do we really need another templating
> engine ? Have you looked at Sigma, Flexy, PHPLIB, Xipe ? Can you put
> benchmark up there

I did some benchmark and it is about three times faster than Template_IT in 
reading and initializing blocks tree ...

benchmarks will be published when proposing package
OOP_Template has a different approach to templates, it somehow treats 
template like a DOM, and it is extensible, indeed I have
(Continue reading)

Bakir Hassani | 1 Jan 11:16 2008

Re: Re: Problem creating an acount to submit a proposal

Hello,

David Coallier wrote
>
> Few points you have to fix.
>
> 1. Make that php5

OOP_Template performs better with php5 due to better object handling as I
noticed in some benchmarks I did, but what about

support for php4?

> 2. Use proper naming (Prefix with PEAR_ your class name)
> 3. Read the coding standards

In fact that online files are the pre-draft of the package and links to them
showed by mistake on my first message

> 4. Add more benchmark, from looking at that code it doesn't seem
> faster than what's out there. Do we really need another templating
> engine ? Have you looked at Sigma, Flexy, PHPLIB, Xipe ? Can you put
> benchmark up there

I did some benchmark and it is about three times faster than Template_IT in
reading and initializing blocks tree ...

benchmarks will be published when proposing package
OOP_Template has a different approach to templates, it somehow treats
template like a DOM, and it is extensible, indeed I have
(Continue reading)

Loïc Vernet | 1 Jan 17:20 2008
Picon

Invisible bug ?

I am receiving this alert.

But, when this bug does not appear in the bug list of my package (PHP_Debug)

What's wrong ?

see u. COil

----- Message transféré ----
De : PEAR QA <pear-qa <at> lists.php.net>
À : Loïc Vernet <qrf_coil <at> yahoo.fr>
Envoyé le : Mardi, 1 Janvier 2008, 10h42mn 03s
Objet : [PEAR-BUG][Reminder] Reminder about open bugs in PHP_Debug

 PEAR Bug Database summary for PHP_Debug - http://pear.php.net/bugs

  ID  Status     Summary

11196 Assigned  Adding of a "DebugLine::TYPE_WARNING". 

  Further comments can be seen at http://pear.php.net/bugs/11196
  Edit this bug report at
 http://pear.php.net/bugs/bug.php?id=11196&edit=1

      _____________________________________________________________________________ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr
Mark Wiesemann | 1 Jan 17:45 2008
Picon
Picon

Re: Invisible bug ?

Loïc Vernet wrote:
> I am receiving this alert.
> 
> But, when this bug does not appear in the bug list of
> my package (PHP_Debug)
> 
> What's wrong ?

The bug tracker currently shows only bugs from registered users. With
the new release of pearweb (scheduled for tomorrow) this will be fixed
for people with pear.dev karma, i.e. the list will then also contain the
"invisible" bug.

That the attached patch has a valid account name assigned, while the bug
itself hasn't, seems to be bug. I haven't checked whether this behaviour
was already fixed.

BTW, using "Won't fix" status without a single comment is maybe a little
bit "rude"?

Regards,
Mark

-- 
http://www.markwiesemann.eu

--

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

(Continue reading)

Loïc Vernet | 1 Jan 19:16 2008
Picon

Re : Invisible bug ?

Indeed, i think i was upset by this bug. I have added some comments. 

Thanks Mark.

----- Message d'origine ----
De : Mark Wiesemann <wiesemann <at> php.net>
À : Loïc Vernet <qrf_coil <at> yahoo.fr>
Cc : pear-dev <at> lists.php.net
Envoyé le : Mardi, 1 Janvier 2008, 17h45mn 51s
Objet : Re: Invisible bug ?

Loïc Vernet wrote:
> I am receiving this alert.
>
> But, when this bug does not appear in the bug list of
> my package (PHP_Debug)
>
> What's wrong ?

The bug tracker currently shows only bugs from registered users. With
the new release of pearweb (scheduled for tomorrow) this will be fixed
for people with pear.dev karma, i.e. the list will then also contain
 the
"invisible" bug.

That the attached patch has a valid account name assigned, while the
 bug
itself hasn't, seems to be bug. I haven't checked whether this
 behaviour
was already fixed.
(Continue reading)

Levi Stanley | 1 Jan 19:24 2008

[PEPr] Proposal for Encryption::HCE_SHA


Levi Stanley (http://pear.php.net/user/niterain) proposes Encryption::HCE_SHA.

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

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

--

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

Philippe Jausions | 1 Jan 20:18 2008

[PEPr] Comment on Encryption::HCE_SHA


Philippe Jausions (http://pear.php.net/user/jausions) has commented on the proposal for Encryption::HCE_SHA.

Comment:

1. Please provide direct access to the source, besides the packaged
version.

2. Don't use TAB but spaces to indent code

3. Class should at least be named "Crypt_HCE_SHA"

4. Is sha1 the only hash function supported? The thinking behind the
question, is whether SHA should even be in the class name.

5. Put spaces around = signs, after commas, and before { in for loops

6. What is the purpose of the empty __destruct() method?

7. Public methods should follow camelCase i.e. blockEncrypt() instead of
hce_block_encrypt()

8. Clean up formatting of doc blocks to match PEAR's coding standard

9. Missing doc block for private members $secret_key and $random_key)

10. I don't have much suggestions for better method names, but
hce_block_encode_mime() and hce_block_decode_mime() but "mime" doesn't
necessarily implies "base64", and "encode" vs "encrypt" is not very
consistent.
(Continue reading)

Christian Schmidt | 3 Jan 18:59 2008
Picon

Re: Re: [PEPr] Comment on File System::S3

till wrote:
> Since many people expressed interest in it, we'll work on something
> new, clean and (probably) re-propose later on.

Are you still expecting to re-propose it? If so, what is your timeframe? 
I am also very interested.

Thanks,

Christian

--

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


Gmane