home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.oop.macapp3
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!spool.mu.edu!agate!apple!mumbo.apple.com!gallant.apple.com!wintermute.apple.com!user
- From: ksand@apple.com (Kent Sandvik )
- Subject: Re: TEditText P.S.
- Sender: news@gallant.apple.com
- Message-ID: <ksand-271292160755@wintermute.apple.com>
- Date: Mon, 28 Dec 1992 00:10:19 GMT
- References: <725492220.0782951@AppleLink.Apple.COM>
- Organization: (Evil Eye Creature from Mars, Inc.)
- Followup-To: comp.sys.mac.oop.macapp3
- Lines: 24
-
- In article <725492220.0782951@AppleLink.Apple.COM>, RSD@AppleLink.Apple.COM
- (Research SW Design, D Goldman,PRT) wrote:
- > By the way, despite the occasional inquiry here, I've never seen an explanation
- > of the point of all this floating TEView business in the first place (as
- > opposed to having TEditText simply be a subclass of TTEView). The memory
- > savings per instantiation are small, but the increased code complexity is VERY
- > high.
-
- > [Since Apple actively supports MacApp 3.0, I look forward to any *current*
- > Apple MacApp engineer answering this question.]
-
- Is an answer from a MacApp support engineer OK? Based on my recollection
- talking with the originators of the floating view, there were talks about
- deleting the floating TEView construct from MacApp 3.0, but due to time
- limits the operation was never done. I agree, the complexity behind
- the floating view is a support/port/maintenance nightmare, a good example
- when a splendid idea does not automatically imply a splendid end result.
-
- Cheers,
- Kent
- -------------------
- Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
- DISCLAIMER: Private activities on the Net.
- "Don't just do something! Stand there!" -- Mystery Science Theater 3000
-