Re: [PHP] Re: Suggestions for class design

2005-09-22 Thread Manuel Lemos
Hello, on 09/20/2005 01:51 PM Murray @ PlanetThoughtful said the following: I do not understand why this could bother you or anybody else. If you have a better solution, nothing stops you to make your recommendations. Hi Manuel, I did make my recommendation. To you. It went something like

Re: [PHP] Re: Suggestions for class design

2005-09-21 Thread Manuel Lemos
Hello, on 09/20/2005 10:04 AM Michael Sims said the following: This is not to trivialize your Metastorage project (or, to be more accurate, I know nothing about it, so it's not my place to trivialize it or otherwise), but to point out that 'out-of-the-box' solutions to fundamental coding

RE: [PHP] Re: Suggestions for class design

2005-09-20 Thread Murray @ PlanetThoughtful
on 09/19/2005 02:33 PM Chris W. Parker said the following: Let's take for example a class called 'Customer' that (obviously) manipulates customers in the database. Here is a very basic Customer class. (Data validation and the like are left out for brevity.) This is a basic object

RE: [PHP] Re: Suggestions for class design

2005-09-20 Thread Michael Sims
Murray @ PlanetThoughtful wrote: Once he understands how to solve class abstraction problems such as the one he is asking about, he will be better equipped to deal with a wider range of application development tasks. I agree with this. This is not to trivialize your Metastorage project (or,

Re: [PHP] Re: Suggestions for class design

2005-09-20 Thread Jochem Maas
Michael Sims wrote: Murray @ PlanetThoughtful wrote: Once he understands how to solve class abstraction problems such as the one he is asking about, he will be better equipped to deal with a wider range of application development tasks. I agree with this. This is not to trivialize your

Re: [PHP] Re: Suggestions for class design

2005-09-20 Thread Manuel Lemos
Hello, on 09/20/2005 04:59 AM Murray @ PlanetThoughtful said the following: Let's take for example a class called 'Customer' that (obviously) manipulates customers in the database. Here is a very basic Customer class. (Data validation and the like are left out for brevity.) This is a basic

RE: [PHP] Re: Suggestions for class design

2005-09-20 Thread Murray @ PlanetThoughtful
[snippage] I do not understand why this could bother you or anybody else. If you have a better solution, nothing stops you to make your recommendations. Hi Manuel, I did make my recommendation. To you. It went something like (and I'm paraphrasing), Your proposed solution doesn't solve the

RE: [PHP] Re: Suggestions for class design

2005-09-20 Thread Murray @ PlanetThoughtful
This is not to trivialize your Metastorage project (or, to be more accurate, I know nothing about it, so it's not my place to trivialize it or otherwise), but to point out that 'out-of-the-box' solutions to fundamental coding development problems probably ultimately makes for a poorer

RE: [PHP] Re: Suggestions for class design

2005-09-20 Thread Michael Sims
Murray @ PlanetThoughtful wrote: My post was not aimed at saying 'using packaged approaches to solve coding problems is bad', but to say 'the original poster is asking a fundamental learning question, so a packaged approach will possibly, maybe even probably, hamper his development as a

RE: [PHP] Re: Suggestions for class design

2005-09-20 Thread Chris W. Parker
Murray @ PlanetThoughtful mailto:[EMAIL PROTECTED] on Tuesday, September 20, 2005 8:15 AM said: And it's also worth mentioning at this point that it might present more of a challenge to the original poster to implement and make use of a complex data abstraction package [1] than to learn a

[PHP] Re: Suggestions for class design

2005-09-19 Thread Manuel Lemos
Hello, on 09/19/2005 02:33 PM Chris W. Parker said the following: Let's take for example a class called 'Customer' that (obviously) manipulates customers in the database. Here is a very basic Customer class. (Data validation and the like are left out for brevity.) This is a basic object