Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42718 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33159 invoked from network); 19 Jan 2009 23:57:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jan 2009 23:57:16 -0000 X-Host-Fingerprint: 82.41.135.70 82-41-135-70.cable.ubr02.grth.blueyonder.co.uk Received: from [82.41.135.70] ([82.41.135.70:26484] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 06/AD-04172-C5315794 for ; Mon, 19 Jan 2009 18:57:16 -0500 Message-ID: <06.AD.04172.C5315794@pb1.pair.com> To: internals@lists.php.net Date: Mon, 19 Jan 2009 23:57:03 +0000 User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 82.41.135.70 Subject: maybe we could all? From: nrixham@gmail.com (Nathan Rixham) Project: PHP Common Objects and Datatypes method: for everybody who wishes to contribute, and for everybody to review, discuss and work on the same classes. what are they: classes we can all use, that have been discussed, reviewed and agreed between many great developers around the world. the classes: all the common ones we can re-use from "User" to "Address" "Email" "Article" and beyond, also perhaps wrappers for primatives / scalars. expanding: extra abstract classes we can also use, common interfaces for the above; eventually maybe utility classes as well. the idea wouldn't be a framework or another php classes, more of a repo full of common classes to save us all some time, and as a nice project anybody can contribute to and which we can all discuss and debate the finer grained details. additional: these would maybe be best to stick to common usage, so if we have say a "User" class in our own project with specific needs, we can simply extend the base user class and add our own functionality. thinking of putting this distraction and debate time to good use that we can all benefit from. would also propose sticking to php 5.X [we could decide a version] and obviously OO; but then if the procedural guys wanted they could as well. maybe it's just me, no commitment, no solid work, just bits of contrib and discussion / feedback. follow? thoughts? comments? interest? [everybody, even tony, would need max input and discussion to get the best solutions for us all, and class at a time should mean we get a steady stream of classes to the repo.. think about 6 months down the line]