Re: [PEPr] Proposal for Yawp::Yawp
| From: | Paul M Jones | Date: | Mon, 22 Mar 2004 21:49:27 +0000 |
| Subject: | Re: [PEPr] Proposal for Yawp::Yawp | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-26637@lists.php.net to get a copy of this message | ||
On Mar 22, 2004, at 3:26 PM, Martin Jansen wrote:
On Mon Mar 22, 2004 at 08:0937PM -0000, PEPr wrote:Fair enough; I needed to call it //something// for the proposal. :-) The name's not important.Paul Jones (http://pear.php.net/user/pmjones) proposes the new package Yawp::Yawp.Uhm, that name absolutely does not fit into PEAR's naming scheme.
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. ;-) 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). 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. 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. ;-) -- Paul M. Jones Savant: the simple alternative to Smarty. http://phpsavant.com/