Re: Interface naming standards?
| From: | Daniel Convissor | Date: | Wed, 07 Jun 2006 13:55:35 +0000 |
| Subject: | Re: Interface naming standards? | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42818@lists.php.net to get a copy of this message | ||
Hi Christian:
On Fri, Jun 02, 2006 at 07:06:53PM +0200, Christian Weiske wrote:
> By the way, I don't even know if different driver classes for formats,
> workbooks and so are needed. If they represent an abstract object that
> holds some data only, output transformation could be put into a
> different file, so that only one Format and one Workbook class is needed.
...
> S_W_Driver_Excel
...
> S_W_Format
> S_W_Workbook
Won't fly. They don't just hold data, they hold methods and properties
specific to the given spreadsheet format.
Perhaps an argument can be made to put the sub classes into the main
class, but it'd be awkward. A spreadsheet can have multiple Format
objects instantiated (to be clear, all instantiations are from the same
class). Each Format object contains the native data related to that one
format. For example:
$this->_formats[0] contains arial, 10pt, white
$this->_formats[1] contains arial, 10pt, red, bold, thin border
So, having Format as a separate class is pretty helpful. Along the same
lines, there are also Worksheet objects, etc.
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409