Only reuse objects that make sense to reuse from site to site.  It certainly
doesn't make sense to reuse all your business logic from one site to the
next, but It would make sense to reuse common elements.  For example, have
you ever written a routine to build a drop down box for the user to choose
their State or Country?  That's the type code you really want to reuse.
Plus remember that code reuse doesn't always mean "copying the object to
another site and using it again" If you create a TCF with a method and use
that method in more than one place, you've just "reused" that code.  Sure,
you could have done it with a branch instead of a TCF method, but It's a
little easier to understand/maintain in a TCF.

/John

----- Original Message -----
From: "Jose Kuhn" <[EMAIL PROTECTED]>
To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 12:21 PM
Subject: Witango-Talk: TCF Resuability


> I am going to go hip deep in using TCF.
>
> The point of having objects is reusability. However, if you put a search
in
> a method, doesn't that break the reusability aspects of a TCF since the
> Search is DB specific?
>
> In other words If I want to use the TCF using a different database, my
table
> names and fieldnames have to be identical to the initial DB in order to
> enjoy any type of reusability.
>
> Is this correct?
>
> Jose
> --
> Webologies
> 150 Robinette Drive
> Waynesville, NC 28786
> 828.627.1994
>
> http://www.webologies.com
>
> --------------------------------------------------------------------------
--
> "You can't make an omelet without breaking eggs"  Boris Badenov
> --------------------------------------------------------------------------
--
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>                 with unsubscribe witango-talk in the message body

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

Reply via email to