New index page for pear.php.net (my 2 cents)

[email protected] (Karsten Dambekalns) Tue, 6 Mar 2001 15:56:31 +0100
Newsgroups php.pear
Organization fishfarm
Message-ID <[email protected]>
Hi!

There is much discussion going on at the moment about phplib  being merged
into PEAR,a bout what database abstraction layer to use for phpwebsite and
about PEAR in general.

One thing that gets mentioned _a lot_ is the the state of the web pages.

I cannot maintain them (and I don't know if any of you guys would let me
that, anyway), but I slapped together a simple index page which make it at
least look as if it was updated.

I just added some word from the codign standards page, added a link to CVS
and linked to two article about PEAR on phpbuilder.com (sadly enough, these
were the only ones I found, not even zend.com had stuff about PEAR).

Look at it, use it, throw it away. At least I tried.

Regards,
Karsten

BTW: I am not subscribed to the php-pear list, so If you want to reach me: I
will be looking at the archives now and then and you can email me directly,
right?
-- 
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:[email protected] w³: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg
index.php (application/x-httpd-php, 2.1 KB)
<?php

pageHeader();

print "<h1>PEAR: PHP Extension and Add-on Repository</h1>\n";

if ($SERVER_NAME != "pear.php.net" || $REMOTE_ADDR == '213.188.9.2') {
    menuLink("Authors", "authors.php");
    menuLink("Packages", "packages.php");
    menuLink("Domains", "domains.php");
}
?>
<h2>What is PEAR?</h2>

<p>PEAR is a code repository for PHP extensions and PHP library code
inspired by TeX&acute;s CTAN and Perl&acute;s CPAN.</p>

<p>The intention behind PEAR is to provide a means for library code
authors to share their code with other developers, to give the PHP
community an infrastructure for using third-party code, to define
standards that help developers write code that runs in different PHP
configurations, and to provide tools for code maintenance and
distribution.</p>

<p>Fortunately, PEAR a general mechanism for reporting errors. An
error is &quot;raised&quot; by creating an error object that may be
used as the return value of a function/method. I say &quot;may be
used&quot; because PEAR errors have several modes of operation: simply
returning an object with more information, printing the error (and
optionally exit), call PHP&acute;s internal error handling functions,
or invoke a callback function.</p>

<p>For more information please see the preliminary documentation at</p>

<?php
menuLink("Documentation", "doc/");
?>

<p>or have a look at CVS at <a
href="http://cvs.php.net/viewcvs.cgi/php4/pear/">http://cvs.php.net/viewcvs.cgi/php4/pear/</a></p>

<h2>Articles &amp; Tutorials</h2>

<p>There are some tutorials about the use of PEAR for database
abstraction and other tasks. Skim through them to get an impression of
how PEAR works and how you might benefit from it.</p>

<ul>
  <li><a
      href="http://www.phpbuilder.com/columns/sean20000712.php3">PHP
      Extension Add-on Repository (PEAR)</a>an article on
      phpbuilder.com</li>
  <li><a
      href="http://www.phpbuilder.com/columns/allan20010115.php3">Best
      Practices: Database Abstraction</a>, an article on phpbuilder.com
      comparing database access using PEAR vs. mysql_*</li>
</ul>

print "<!-- $REMOTE_ADDR -->\n";

?>
signature.asc (application/pgp-signature, 238 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1e-SuSE (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6pPqfzmcQByaBiO8RAqvFAJwNKsuQIDJGF7Ti+dHa84GxTLoIjgCfSByG
54xNmeTR8n+K6GScUZRY0yE=
=Gmrk
-----END PGP SIGNATURE-----