Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!news.sei.cmu.edu!cis.ohio-state.edu!math.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!sgiblab!cs.uoregon.edu!usenet.ee.pdx.edu!fastrac.llnl.gov!lll-winken.llnl.gov!trib.apple.com!amd!netcomsv!xilinx!bretts
From: bretts@fred.xilinx.com (Brett Stutz)
Subject: VisulWorks Critique (was Re: ObjectWorks/SmallTalk)
Message-ID: <1994Oct11.180648.4219@xilinx.com>
Originator: bretts@xilinx.com
Sender: usenet@xilinx.com
Reply-To: bretts@fred.xilinx.com (Brett Stutz)
Organization: Xilinx Inc.
References: <37bma7$gk7@hermes.uni-konstanz.de> <37br39$ad@panix.com>
Date: Tue, 11 Oct 1994 18:06:48 GMT
Lines: 31


In article <37br39$ad@panix.com>, dsiegel@panix.com (David Siegel) writes:
|> 
|> VisualWorks is a superset of ObjectWorks.  You could ignore
|> all the VisualWorks GUI stuff entirely (there are times when
|> I'm tempted to do so).
|> 

Could you expand on your parenthetical comment? I'm a (fairly new) VW
user.  There are some
things I like and others I don't.  The architecture is a little sloppy
and shows evidence of
several different styles.  This made more sense when I read that the VW
classes were originally
developed by TI for a project they were doing (rather than being
designed from the start by
expert ST/OO designers as a commercial product).

As an example, consider the way controllers are created for widgets.
View has a method
defaultControllerClass, but when UILookPolicy instantiates the widgets,
it uses a hardcoded
Controller class to make controllers for the widgets.

I'm interested in more substantial critique of the product.  How can PP
make VW better?
-- 
Brett C. Stutz
Staff Engineer and Object Wrangler
Xilinx 
Opinions are mine, not those of my employer.
