[phplib] EZ-phplib From: giancarlo pinerolo (giancarlo <email protected>)
Date: 07/15/01

Hi all

I tried to sensibilize the phplib developers, and you all, about these
items, but had a scarce response.

So I'll try to start a project on it, and maybe go on alone.

I have put down a paper, which is incomplete as the project didn't start
yet.
Would be on sourceforge ofcourse.

What do you think?

Giancarlo

EZ-phplib project init
----------------------

PREAMBLE

There are quite a few packages based on phplib, but each one supposes
you are installing
phplib for the first time.
Installing a phplib-based package for the first time is relatively easy
(relatively...), as
is installing phplib by itself for your own, in-house development.
 
Things become more complicate when you want to install a package based
on phplib onto a
preexisting phpilib site.

Most people think that having phplib already configured and running
would make it easier for
them to add an extra package based on it.

The reality, at the moment, is exactly the contrary, and he'd be better
off if he didn't have
it already.

This is because phplib has been designed so flexible and configurable,
that hardly any
supposition can be made on an existing installation, and package
developers themselves prefer
to deliver their application accompained with a predefined,
preconfigured phplib kit.

And this leads to the surmentîoned problem: phplib-based packages hardly
comvive with each
other or whith preexisting phplib-based sites.
And integrating these, requires far more acquaintance with the inner
phplib workings than
what is needed in a first-time installation.

TARGET:

this project is targeted both at web developers and at package
developers, acquainted in the
use and configuration of phplib

It is not meant for solving installatîon problems, but to develop
flexible ways to solve
them.

Nor it is aimed at helping people in their first-time impact with
phplib: the phplib mailing
list and site are the best places for that.

The final tools and code will hopefully help them.

GOAL:

what is meant to start here is not a fork of phplib, but a separate
project to provide a
smooth, flexible way of configuring it.

Then, hopefully, the code can be adopted by the core phplib project, and
package developers
can assume and rely on this setup tools.

This will end in a phplib that configures more easily and is more
'third-party package
friendly'.

CONSTRAINTS:

Phplib offers many ways to tailor its functionalities, by offering the
possibilty to extend
its base classes in a great number of ways.

By no means this project intends to be a fork of the 'core' phplib
development, nor it will
attempt to rewrite core phplib functionalities, or anything that will
not work with 'any'
base phplib distribution.

Rather, it will attempt to provide an uniform, easily configurable way
to (pardon the
sync...) configure the extension of phplib's base classes.

So, as a rigid constraint, it will only limit its action on the
'local.inc' and
'prepend.php3' files.

PATH:

the first step is opening up a discussion on these issues, trying to
explain our common
problems and needs.

So you are invited to join the discussion at the project, which is
hosted at......... 

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>