TCF files (class files) can be a great way to go. Making a class file with 6 different methods or 6 different class files if you like would do just what you're looking for, giving you distinct files or methods to call when needed, also simplifying the task of updating and loading less 'stuff' at once.
This is a pretty gross over-simplification, but it's something worth exploring. There have been more than a few posts about this in the past, so your handy list archive is a good place to start. I'm sure others will chime in as well...
Jason
On Tuesday, February 25, 2003, at 03:04 PM, ServerSmiths Tango Development wrote:
I have a large monolithic app that I have planned to make modular for speed
and ease of updating.
A post on the list last week made a parenthetical comment about there being
better ways to do things than branching.
Isn't creating 6 modules out of 1 large app and then branching back and forth the best way to go?
What would be the alternatives?
Maybe I misinterpreted the comment but I certainly need to know if the branch to another .taf concept is outdated already.
Thanks,
Michael Heth Web Information Architect
__________________S E R V E R S M I T H S__________________
http://www.serversmiths.com/
Technology Infrastructure Provider
I N T E R N E T P R E S E N C E S O L U T I O N S
| EWordSmith | LightningSite | Enigma.Engine |
________M A R I N C O U N T Y C A L I F O R N I A________
_______________________________________________________________________ _
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
-- ____________________________________________________________________
Jason Pamental, President [EMAIL PROTECTED]
Bathysphere Digital Media Services, Inc. http://bathyspheredms.com
____________________________________________________________________
Tel: 401.490.6830 Fax: 401.490.6831 ________________________________________
A North American Distributor for Witango (http://www.witango.us)
Rapid Web Application Development - XML Execution Engine
________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
