Dayless Day

PHP test coverage exceeded 55%

nospam@example.com (Antony Dovgal) — 2008-05-21T09:17:02Z

According to GCOV reports, PHP test coverage has recently exceeded 55%, which is really good number, but still not enough. It took us about 2 years to get the last 5% and I believe most of the kudos should go to IBM people, who continue to contribute lots of new tests.
I hope that the Testfest will help us to speed up this process.

libHaru.org - the new home of free & open source PDF generation lib

nospam@example.com (Antony Dovgal) — 2008-02-28T09:26:10Z

It took quite some time for me to think it over and prepare new libHaru site - libHaru.org.
Nevertheless, it's finally online and I'm going to continue maintaining the library, new bugfix release is on its way.

Though I don't think I can do all the maintenance job on my own - some help is required with Windows builds and other things like the documentation, which needs some cleanup (even though it's in a good shape at the moment), so volunteers are very welcome.

Anyway, if you need to produce PDF files, libHaru is the answer.
If it doesn't satisfy your needs or even lacks something crucial - let me know, I'll see what I can do.

Gpasman for Maemo

nospam@example.com (Antony Dovgal) — 2008-02-27T09:38:51Z

I've been using Gpasman to store my numerous passwords for about 5 years now, so no wonder my first thought when I bought my Nokia N800 was to port it to Maemo. And that's what I did =)

Gpasman is now available in Maemo Garage and Maemo Downloads.
You can see a couple of screenshots here.

If you have more than two passwords and are afraid to forget them one day - give it a try, it's really handy.
I also have Gpasman RPMs for SuSE.

We're open, don't try to change us

nospam@example.com (Antony Dovgal) — 2008-02-01T23:27:47Z

Just so that you know what I think about that CLA thing:

Make It Open Or Go Away

We don't need no new PDO

nospam@example.com (Antony Dovgal) — 2008-01-24T21:25:59Z

PDOv1 was initially a small project created and maintained mostly by 1-2 persons.
Even though it was quite small, it turned out to be a kind of monster which nobody really likes or understands.
Oh.. and did I mention that it never actually worked?

And now we're being forced to have PDOv2, which is of course very much different from PDOv1: it's being developed by a secret group of people (which includes some mysterious "vendors") aand.. it requires signing a legal paper it you want to participate or even read its spec.

PDO does not need a CLA, PDO needs *CARE*.

Doesn't matter how much "vendors" participate in PDO, it's going to be a total failure as long as nobody cares about it.
That was the biggest flaw of PDOv1 and CLA won't magically fix it.

Happy holydays, everybody!

nospam@example.com (Antony Dovgal) — 2007-12-23T17:57:14Z

PhD docu builds are online!

nospam@example.com (Antony Dovgal) — 2007-11-26T19:10:27Z

The docs generated by the brand new docu build system PhD ([CVS], [releases]) written by Hanness Magnusson, after several months of development are finally online!

Feel the difference:
With the old OpenJade/DocBook it took 40-60 minutes to build 'many htmls' version of the manual.
With PhD it takes less than 2 minutes to build all three formats (`phpweb`, `one big html` and `many htmls`).

Kudos to Bjori!

More template benchmarks

nospam@example.com (Antony Dovgal) — 2007-11-15T11:28:19Z

As you know, there are lies, damned lies and ~~statistics~~ benchmarks.
So here are some more template benchmarks: http://template-bench.iliakantor.ru/, prepared by Ilia Kantor.
Curiously enough, Smarty is on the 5th place, right after the stuff written in C, so think twice before saying it's slow.

PHP Seven Commandments

nospam@example.com (Antony Dovgal) — 2007-11-12T16:27:33Z

IMO it's time to make the development process more organized.
This is my version of what I would like to see as an official set of rules for PHP community.

PHP Seven Commandments

1. Thou shalt obey the Release Master.

2. Thou shalt not commit any patches except for bugfixes after RC stage has started.
Even bugfixes must be discussed with the release master before committing.

3. Remember the coding standards and keep them holy.

4. Thou shalt not forget to add comments to thy code, especially if the code is tricky.

5. Thou shalt not fix a bug only in one of the branches unless it did not exist in the others.
The rule of thumb is to fix it in HEAD first and then backport it.
Forwardporting is not appreciated unless it happens in a matter of hours.

6. Major development goes in HEAD, other branches are created for bugfixes and minor improvements.

7. Thou shalt discuss all new features in internals@.
If nobody pays attention to your proposal, it makes little sense to implement it.

blitz templates 0.5.7

nospam@example.com (Antony Dovgal) — 2007-11-07T09:37:28Z

Alexey Rybak has recently rolled out new bugfix release of his template PHP extension - Blitz 0.5.7.
This release fixes a number of minor problems including memory leaks and possible invalid reads and does not affect functionality or speed in any way, so the extension is still blazing fast, but even more stable now.
See more about Blitz here (benchmarks included).