Object framework, collaborative projects, management, future vision

At 13:51 09/11/01 -0500, you wrote:

2. new classes aren't getting distributed w/ PHP, and PEAR installer stuff seems far from being usable by everyday PHP users (please correct me if i'm wrong here. status on the state of the installer and a brief explanation of how it works would be awesome, if anyone involved has the time).

I don't understand the logic behind this. PEAR is meant to be a single set of basic libraries delivered in the standard PHP branch. This is the power of Linux, which gives access to all required libraries at onece. I don't see the meaning of splitting your work. This is pure destruction!!!

As I said multiple times: I'm open to changes. I would be very happy, if you could set up sth. like an RfC describing a less strict coding standard that you think is good for PEAR, since I currently don't have the time to sit down and write something down in a proper way.

RFC should describe 'spaces' or whatever but also: - project vision and future, - object framework project. What do you intend to build with PEAR?

Uh, sorry, no. There is released code that's using PEAR already. There was when someone broke DB's backwards compatibility for a month with the whole quote() vs. quoteString() mess, and that was a problem, too.

No, we are in a free world. PEAR should include syntax checking, release management and dependency checking. If you can't build an installer tool, use RPM which exists on all platforms, including $Win. This can be worked out in a standard PHP interface. Why try to build something different from RPM ??? THIS IS PURE WASTE OF TIME.

decentralization and federation is where it is at, not centralization.

Decentralization does not mean PEAR should not be organized. I am new to PEAR. Who are the project leader? Whom can I submit ideas of porting Swing? Again, what is your vision? Who is responsible for writing documentation? I think that if PEAR==Java then PEAR=object framework (like Swing). Why stick to this old-fashion idea of search/replace templates? We need templates, OK, but also more... The question is "How to build database list/page views without templates?". "How to split a page into panes?". "How to define objects within panes?". "How to define data layers (XML, SQL)?". "How to manage user access and security?" etc... etc... Can anyone give me precise answers? I am not trying to criticize PEAR, I am only looking for a 'home' for collaborative projects including frameworks (not template search/replace tools, I can find good ones elsewhere). What do think of BinaryCloud? Do you think it has good chances to be included as a standard in Php? Best regards, Jean-Michel