Re: Re[4]: [PEAR-DEV] previos message

From: Date: Sat, 15 Sep 2001 22:29:46 +0000
Subject: Re: Re[4]: [PEAR-DEV] previos message
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-1938@lists.php.net to get a copy of this message
On Sun, 16 Sep 2001 02:12:21 +0400, Denis Peplin wrote: >MJ> On Sun, 16 Sep 2001 01:11:45 +0400, Denis Peplin wrote: > >>>Saturday, September 15, 2001, 12:45:00 PM, you wrote: >>> >>>MJ> On Thu, 13 Sep 2001 22:54:30 +0400, Denis Peplin wrote: >>> >>>MJ> It was about the Image class, right? >>>Yes, right. >>> >>>MJ> I think the code looks promising >>>MJ> and it might be interesting for lots of users, but you should make it >>>MJ> pass all your test before committing it into PEAR. >>>Ok, I will do it in one day. >>>But I have two questions: what name and what file name will be best >>>for this class? > >MJ> Image_Common is OK. The place for it in PEAR >MJ> should be /pear/Image_Common/Common.php then. > >Why not /pear/Image/Common.php? Ahh, I should really commit the 'documentation' stuff ;-). PEAR has to scale in terms of the number of developers, so for practical reasons we organize the "pear" CVS module into sub-projects (packages). Each package has its own development team, release cycle and also its own directory under "pear". To take your example, a "Image" package would probably become very big and hard to maintain. So if nobody has enough interest in everything image-related to maintain a single package for "Image", smaller packages such as Image_Foo and Image_Bar start showing up. According to this rule I don't know anymore if Image_Common is an appropriate name for it. Perhaps Image_GDConvert would be better since converting images (that's the purpose of your class, isn't it?) isn't what I would call common image operations. - Martin

« previous php.pear.dev (#1938) next »