NYCPHP Meetup

[Michael]

A real selling point for me for using object oriented design for a website
is the ability to easily embed one pages functionality inside of another.
For example you can have a login page and include it as a login box in
other pages without recoding much of anything. The data all goes through
the same checks, is handled in exactly the sameway, etc. It seems a small
thing but as you get into complicated modules it can be a major benefit.
You can achieve some major code resue even between multiple sites.


Don't dream it. Be it.

;):):-):):-):):-)8')
Michael McGlothlin <mogmios at mlug.missouri.edu>
http://kavlon.org/projects/

On Wed, 31 Jul 2002, Benjamin Stiglitz wrote:

> On Wednesday, July 31, 2002, at 09:50  AM, Mike West wrote:
> > This is quite right and accurate im my experience. Building objects
> > has, in my experience, been even more helpful than a single entry point.
>
> I definitely agree. This is what we tried to achieve here at Tanjero
> with Jawa. The beauty of using objects in the concept of inheritance.
> Normal page functionality is inherited from base classes. As long as the
> public interface doesn't change, it doesn't matter how we implement any
> one feature; if we want our pages to be output in WML instead of HTML,
> we only have to change it in one place. Authenticated pages are a just a
> subclass, etc...
>
> Of course, objects aren't very useful without planning. The first thing
> we did was create a class map, which has now become a terrifying graph
> of objects will all sorts of lines connecting objects. Easy it wasn't;
> however, it's paid off quite a bit.
>
> Thank you,
> Benjamin Stiglitz
> Tanjero
> ben at tanjero.com
>
>