PEAR: RFC Proposed for Rules/Guidelines

Grok Headline matches for PEAR: RFC Proposed for Rules/Guidelines

Tobias Schlitt's Blog: PEAR::Image_3D
Proposed

Tobias Schlitt's Blog: PEAR::Image_3D
Proposed 06/17/2005 03:32 PM
Tobias Schlitt has a new post with a proposal for inclusion into the PEAR libraries - PEAR::Image_3D.

Image_3D enables you to render 3D images using PHP. As I mentioned in my last post on that topic, the usage of PHP to render 3 dimensional images seems a bit ridiculous, but it definitly has a sense: Imagine the rendering of 3D charts from database data (we plan to implement a driver for PEAR::Image_Graph) or rendering of simple 3D images from user data. Of course one should not render those images on the fly, but cache them. Exciting is the fact, that rendering even complex 3D images (about 16.000 polygones) takes an acceptable amount of time. Try it yourself! :)

He also shares a few resources on the subject, including: the proposal, the package itself, as well as an example of it in use...

User Agent Accessibility Guidelines
Become a W3C Proposed Recommendation

User Agent Accessibility Guidelines
Become a W3C Proposed Recommendation 10/17/2002 02:08 PM
17 October 2002: W3C is pleased to announce the advancement of User Agent Accessibility Guidelines 1.0 to Proposed Recommendation. Comments are welcome through 14 November. Written for developers of user agents, the guidelines lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). The companion Techniques Working Draft is updated. Read about the Web Accessibility Initiative. (News archive)

Proposed Federal Rules On E-Document
Destruction

Proposed Federal Rules On E-Document
Destruction 04/04/2005 08:35 AM

U.S. House rejects proposed new overtime
pay rules

U.S. House rejects proposed new overtime
pay rules 09/10/2004 08:18 PM
In a surprise move against the White House administration's effort to overhaul the rules that govern who is and is not eligible for overtime pay, the U.S. House of Representatives voted Thursday 223-193 to circumvent the rules, which took effect last month. These rules are particularly germane to IT-related employees, well known for working long hours, often deep into the night and weekends.

White House Downplayed the Risks of
Mercury in Proposed Rules, Scientists
Say

White House Downplayed the Risks of
Mercury in Proposed Rules, Scientists
Say 04/09/2004 03:55 PM
White House staff members deleted or modified information on the toxic effects of mercury when writing regulations for coal-fired power plants, documents and e-mail messages show.

oai-pear

oai-pear 04/26/2004 07:40 AM
PEAR::OAI 0.4.1 Released

Court Rules Evel Knievel Is A Pimp;
Knievel Rules Judges Are Bimbos

Court Rules Evel Knievel Is A Pimp;
Knievel Rules Judges Are Bimbos 01/04/2005 08:20 PM
Really not quite sure what to make of this one, but it's too amusing to pass up. Apparently, a few years ago, ESPN posted a picture of famed daredevil Evel Knievel with his arms around two women (one of whom was his wife) with the caption: "You're never too old to be a pimp." Knievel, not realizing this was a (weak) attempt at complimenting him, sued ESPN for defamation. A lower court tossed out the ruling, and he appealed. Now the Appeals Court has ruled against him as well, noting that, based on the context no one is actually going to think Knievel is a "pimp," and, in fact that the statement was supposed to be a positive one, as the slang of the day suggests. Knievel, apparently lacking a sense of irony over this particular case, has responded by calling the judges "bimbos." The full quote is: "They ruled against the law. What good is law in the United States of America if five or six goddamn bimbos are going to rule against it?" You think he intended that as a compliment? Anyway, in the meantime, feel free to go on captioning photos on the web while calling people pimps.

PEAR Out of Beta!

PEAR Out of Beta! 01/11/2003 09:10 AM
The PEAR development team is proud to announce that PEAR is finally out of its long beta period. As of PHP 4.3, the PEAR installer is installed by default. Unix support is considered stable, while Windows and Darwin are still of beta-quality.

PHP's PEAR on Mac OS X

PHP's PEAR on Mac OS X 01/21/2003 10:06 PM
The PHP Extension and Application Repository (PEAR) is an online repository of high-quality, peer-reviewed PHP classes that conform to a rigorous coding standard. In this article, Jason Perry shows you how to install, configure and use the PEAR Package Manager on Mac OS X 10.2

PEAR grows up: MDB

PEAR grows up: MDB 01/12/2003 01:36 PM
We met with the author of Metabase at the International PHP Conference 2001 and we talked about the benefits of having something like Metabase as part of the PEAR project. Shortly afterwards a discussion began once more in the PEAR mailing list about the potential benefits of a merge of PEAR DB and Metabase. After much discussion at my company we decided to take up this task. After several months of hard work we now have the first stable release of MDB. - Lukas Smith Lukas Smith has done a fine job with MDB and finally PEAR has a decent db abstraction library. Congrats! "zeldman.bardot2"

Comprehensive PHP PEAR::DB

Comprehensive PHP PEAR::DB 02/10/2004 02:46 AM
Overall, this is maybe a good and very helpful book if you are using, or plan to use, the PEAR::DB package. Although it does not cover the features that the PEAR::MDB package adds over PEAR::DB, the book may also be helpful if you are interested in PEAR::MDB as this package provides a compatible superset of the PEAR::DB features.

PEAR::PHPUnit 2-2.0.3

PEAR::PHPUnit 2-2.0.3 09/27/2004 03:25 AM
A regression testing framework for PHP 5.

Without a pear, I improvise.

Without a pear, I improvise. 10/28/2003 11:06 PM
Many application developers shy away from database abstraction tools, in part because of the overhead and new APIs they have to learn, but also because it's difficult for those tools to port complex instructions and queries to each different RDBMS....

PEAR::PHPUnit 2-2.0.0

PEAR::PHPUnit 2-2.0.0 07/14/2004 01:51 AM
A regression testing framework for PHP 5.

PEAR::PHPUnit 1.0.2 (PHP 4)

PEAR::PHPUnit 1.0.2 (PHP 4) 09/21/2004 09:06 AM
A regression testing framework for PHP 5.

Introduction to PEAR

Introduction to PEAR 10/29/2003 02:21 AM
An introduction to PEAR with examples of using the Benchmark package.

How to use the PEAR ITX templating
system

How to use the PEAR ITX templating
system 01/09/2003 10:39 PM
Fortunately for me, something kept pushing me on to investigate, and in the end it turned out that ITX is exactly the thing I was looking for. It had support for blocks and variables, some primitive support for calling PHP functions directly from the template (if you ever find yourself in need of that) and a very easy template syntax for my users. I found this last feature more important than anything else that other templating systems could offer!

Compared to Smarty, ITX is definitely smaller and lighter. Many things are missing, and yet I'd say that the thing most of the folks will find missing is caching. If you need caching you can still implement it with finer cache expiry methods than those of Smarty. I suppose there will also be a tutorial about ITX caching and cache control at some point in time. -- Ivan Stojic

"zeldman.mrsp"

PHPBuilder: Your First Bite of PEAR

PHPBuilder: Your First Bite of PEAR 12/27/2002 08:16 AM

PEAR::PHPUnit PHPUnit2-2.0.2

PEAR::PHPUnit PHPUnit2-2.0.2 09/04/2004 05:11 AM
A regression testing framework for PHP 5.

The PEAR::SOAP Implementation

The PEAR::SOAP Implementation 12/24/2002 07:14 AM
This article will step you through one of the leading SOAP implementations – PEAR::SOAP, its installation, and then detail an example ‘Hello World’ SOAP application using PEAR::SOAP. PEAR::SOAP is an implementation that is based on SOAPx4 and offers a basic, yet very useful way of developing SOAP clients and servers with PHP.

PEAR::PHPUnit 1.0.0-alpha3

PEAR::PHPUnit 1.0.0-alpha3 01/18/2004 09:20 AM
A regression testing framework for PHP 5.

Instant XML with PHP and
PEAR::XML_Serializer

Instant XML with PHP and
PEAR::XML_Serializer 05/17/2004 04:46 AM
WebmasterBase May 17 2004 7:20AM GMT

PHP Magazine: Comprehensive PHP PEAR::DB

PHP Magazine: Comprehensive PHP PEAR::DB 08/27/2004 01:35 PM
Over on PHP Magazine's website today, there's a new review of a book that all PEAR users (and even those looking to get into it) will find quite helpful.

Pear Versus ADOdb

Pear Versus ADOdb 11/25/2002 09:58 AM
Comparing Pear and ADOdb is one of those PHP things that we're all curious about. I haven't used it but I'd also look at Metabase (sorry for no link) since someone I respect technically really likes it. [ Go ]

PEAR::PHPUnit 2.0.0-beta2

PEAR::PHPUnit 2.0.0-beta2 05/26/2004 07:39 AM
A regression testing framework for PHP 5.

phpPatterns: More PEAR Productivity?

phpPatterns: More PEAR Productivity? 12/02/2003 01:36 AM
I seems as though Harry Fuecks has stumbled upon something very interesting in the PEAR site and project - a process to make the voting and inclusion of new libraries in PEAR a much simpler process.

The Fruity Taste of PEAR

The Fruity Taste of PEAR 05/31/2004 12:40 PM
You cannot help but like someone like Greg who is honest and humble:

"I am one of the core developers of the PEAR package who has joined the game relatively late... The base PEAR class is one monstrous mistake, and PEAR_Error is pretty close. Everyone knows this. I designed an error class that is much, much more flexible and it is part of PEAR 1.3.1 (PEAR_ErrorStack) - check it out. "

Sadly it's just not true that everyone knows that PEAR class is big mistake (Jeff Moore has more on why PEAR.php is awful). Given that PEAR is both an important framework and a worthless class, the confusion in names will definitely cause the value of the PEAR class to be overestimated. Just read any article on PEAR and you can see what nice words they have to say about the base classes :-(

I once said once that too many PEAR developers were journeymen. This might have offended some people, but I was trying hard to be diplomatic. I must say that today the PEAR group is definitely more mature, and they have learnt a lot about library design. What would really make my eyes light up would be an PEAR2 initiative that kept the existing classes, but dropped the bad seeds such as PEAR.php (e.g. the PEAR and PEAR_Error classes).

And in case you were wondering, I do think there's great value in the PEAR DB API. API's are important for interoperatability. For example, ADOdb has a PEAR DB compatibility mode. I would certainly be flattered if PEAR DB had an ADOdb compat mode too :-)

The PEAR ITX Templating System

The PEAR ITX Templating System 01/31/2003 08:03 PM
An analysis of the ITX templating system included with PEAR.

Building PHP Web services with PEAR

Building PHP Web services with PEAR 02/16/2004 11:54 AM
PHP -- short for PHP Hypertext Preprocessor -- was, along with Perl, one of the frontrunners in server-side programming long before any JSP/Servlet or ASP technology came to be. It is often the language of choice for those using Apache's Web server, which runs almost 70% of sites on the Web. Due to its pervasiveness, it seems obvious that it should support the most recent standards, such as SOAP, which are also adopted by major technology vendors. In this article, we will describe how Web services can be implemented in PHP.

A Turning point for PEAR?

A Turning point for PEAR? 11/10/2003 10:52 PM
A posting in the php.pear.dev newsgroup by one of PEAR's leading developers. I think this is a very honest assessment, and I'm hopeful about this.

> From: Xavier Noguer [mailto:xnoguer#xavier-noguer.com]
> Sent: Saturday, November 08, 2003 3:41 PM
 
> Martin Jansen <mj#php.net> escribió
> 
> > (http://pear.php.net/manual/en/developers.contributing.php)
> >
> > It is pretty funny to see how much developers have actually read
the
> > "Developers Guide" ...
> 
>  I've read that guide. I just don't seem to be able to take it
seriously
> when
> it lists requirements that have never, as far as I know, been voted
by the
> pear group or the developer community at large, such as regressions
tests
>
(http://cvs.php.net/diff.php/peardoc/en/guide/developers/contributing.
xml?
> r1=1.8&r2=1.9&ty=h)
I agree here.
While previous mistakes don't make a wrong a right, I think our whole
manual
lacks any consistent concept of what we really feel needs to happen
when and
where.
Anyways we have a bunch of messes that are a result of the long
period of
limited peer review, followed by a period of package inflation,
followed by
the today ruling confusion.
I think its time we fix our standards by starting from a clean
slate with a
PEAR2. There we can think about how to best deal with our developer
and
users base and how to great the best possible code in a PHP version
which
actually supports our needs for OOP.
PEAR1 should of course be maintained as we all have an interest to
keep that
code running and to use PEAR1 as a momentum towards a PEAR2 which
build on
the past experience.
<rant>
PEAR1 is now suffering from the fact that it focused from a long
period of
building technical foundations without planning the community growth
at the
same time. This has lead to numerous problems and is making us very
inefficient. Of course PEAR1 has a lot to offer, but I don't think we
are
scaling well and past mistakes seem to haunt us more and more, which
we
don't seem to be able to fix. So I think we need to recognize our past
which
we of course need to maintain to remain credible, but at the same time
we
should work to build a more scalable PEAR2 in which we can address our
issues on a clean slate.
</rant>
>  Would you be so kind to point me to the pear group document or
public
> discussion in which this requirement was approved?
There is no such decision I can remember.
As George pointed out we discussed this point in Amsterdam, however I
don't
remember that anyone decided on requiring documentation at first
commit.
However our decisions there were mostly only concepts and not
complete.
Anyways maybe someone should check when this was commited anyways.
Regards,
Lukas Smith

Builder.com: Pinging with PHP and PEAR

Builder.com: Pinging with PHP and PEAR 07/01/2004 08:47 AM
On Builder.com today, there's a new article about creating a script to ping a remote host with PHP.

PHP & PEAR at FOSDEM 2005

PHP & PEAR at FOSDEM 2005 03/14/2005 04:43 PM
This year PHP & PEAR have a devroom at FOSDEM 2005 held in Brussels. On Sunday, 27th of February, several developers will talk about PHP & PEAR. Topics include Xdebug, eZ publish, SimpleTest, Horde and PEAR. A full schedule can be found on the FOSDEM's site. Along with giving the scheduled talks, the developers will be available during the course of the day to chat with. The devroom is also open to all who want a place to code and/or relax. We hope to see you there !

Comparing PEAR DB to ADOdb

Comparing PEAR DB to ADOdb 11/17/2002 10:47 PM

PEAR DB is the default database abstraction library for PEAR. ADOdb is a high end database abstraction library modelled on Microsoft's ADO that is also very popular.

1. Feature Comparison
Where we try to put you to sleep by showing you the similarities between PEAR DB and ADOdb 2. Features Missing from PEAR DB
Now we try to wake you up with some teasers 3. Criticisms of ADOdb
Read what other people are moaning and complaining about

"zeldman.57"

Database Abstraction with PEAR

Database Abstraction with PEAR 08/05/2002 10:44 PM
So you've written a great application with PHP and it is up and running smooth. Then, your boss calls and tells you that your company won't be using MySQL anymore. You're moving to Oracle. Your application is dead in the water. You should have used database abstraction. It's a grim tale that happens all too often. Don't think it can't happen to you. It will. When you least expect it. But don't worry, there are ways to plan for situations like this. Wouldn't you love to just smile at your boss and tell him it won't be a problem? Well, today you will learn just how to do that. Database Abstraction is a method of coding that allows you to concentrate on coding rather than the syntax for a particular database API. You use generic methods to access the database, any database. Obviously, you need additional code or libraries to do database abstraction. That is where PEAR comes in. PEAR includes a database abstraction class that you can use in your scripts. There are other abstraction classes out there, but for the purpose of this tutorial we will focus on the one provided with PEAR. -- Matt Wade "zeldman.naft"

Caching with PEAR::Cache

Caching with PEAR::Cache 04/09/2004 04:02 PM
So, your web site is starting to get popular? With popularity comes more page request, and with more page requests comes higher server load. Don't get in a situation where you can't serve up the pages. Build your application to handle the load. That's where PEAR::Cache comes in. In this tutorial, Timothy will show you how to use it.

Generating Spreadsheets with PHP and
PEAR

Generating Spreadsheets with PHP and
PEAR 04/15/2004 09:08 PM
WebmasterBase Apr 16 2004 1:49AM GMT

PEAR Weekly News

PEAR Weekly News 07/08/2002 02:38 AM
Welcome to the first edition of the PEAR weekly news, hopefully the first of many!. The idea is to keep up to date with new pear packages, and developments on the PEAR mailing lists. -- Alan Knowles

PEAR is the official framework and distribution system for reusable PHP components.

Prickly Pear May Be Hangover
Preventative

Prickly Pear May Be Hangover
Preventative 06/30/2004 01:18 AM

PHPEverywhere: The Fruity Taste of PEAR

PHPEverywhere: The Fruity Taste of PEAR 06/01/2004 09:17 AM
On PHPEverywhere, there is a new posting that some of the core PEAR developers out there might not want to see.
Grok Description matches for PEAR: RFC Proposed for Rules/Guidelines
GrokA matches for PEAR: RFC Proposed for Rules/Guidelines

PEAR: RFC Proposed for Rules/Guidelines

The following phrases have been identified by the grok system as matching this entry: