Re: [PEPr] Proposal for Yawp::Yawp

Paul M Jones wrote:

Apart from that I'm a little bit concerned about the package, because it adds something, of which I have been hoping that it will never find it's way to PEAR: Collections of packages. If we now start adding a first collection, people will come up with all sorts of collections, and they (and rightly so) will claim that the package should be added, because we already have another collection package in PEAR.

If the "you should add my X-function package because there's already an X-function package in PEAR" is a valid argument, then I would like to propose the Savant template system for PEAR right now. ;-)

template systems is where we made mistakes .. no need to repeat them.

Yawp (or whatever name we choose) uses packages in "aggregation" (if you will) and is certainly extensible enough that it can accommodate new packages into its aggregate, thus obviating the need for another collection package. E.g., if PEAR thought it would be good, in general, to have an instance of HTML_Template_Xipe in the Yawp object, it would be easy to add code to Yawp to read the Yawp.conf.php file for a [HTML_Template_Xipe] group and instantiate one based on that configuration. Thus, no need for new collection packages; they could all fit into the Yawp (or whatever) aggregate. (The Xipe instance is just an example; the point of Yawp is to aggregate and encapsulate the classes used in all or nearly-all web-based apps where only usually only one instance is needed: authentication, database, cache, timer, var-dump, etc).

I see what you mean. However the problem is that I think we will end up in exactly the same situation or worse as with the template engines. In the end I feel that collections better fit outsides of PEAR. However PEAR based frameworks or collections should be encouraged. This is what we want to see happening! But putting them in PEAR will only lead to confusion as there are simply so many possible approaches and permutations of combinations that an inflation will undoubtly happen.

Anyway, it's just an idea. As with most of the packages I propose, I already use it myself and thought others might find it useful.

I am sure that other users will agree and will be greatful for this work. As such I propose that we more actively advertise frameworks and collections that are based around PEAR packages. If you want you might want to spear-head such a page in pearweb.

You'll note I did not put together as detailed a proposal this time; I think I'm in the running for "lowest proposal-to-acceptance ratio" on PEAR-DEV. ;-)

You do have a tendency to walk on the edges of PEAR :-) But someone has to walk them I guess to help us more clearly define them :-) regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07