Path: utzoo!utgpu!attcan!uunet!husc6!tut.cis.ohio-state.edu!diplodocus.cis.ohio-state.edu!jgreely
From: jgreely@diplodocus.cis.ohio-state.edu (J Greely)
Newsgroups: comp.sys.next
Subject: Re: Next and the competition
Message-ID: <29994@tut.cis.ohio-state.edu>
Date: 23 Dec 88 05:32:35 GMT
References: <29866@tut.cis.ohio-state.edu> <5567@cbmvax.UUCP>
Sender: news@tut.cis.ohio-state.edu
Organization: THE Ohio State University, CIS Dept.
Lines: 28

In article <5567@cbmvax.UUCP> daveh@cbmvax.UUCP (Dave Haynie) writes:
>in article <29866@tut.cis.ohio-state.edu>, J Greely says:
>> ... when an application doesn't know how to handle refreshes
>> properly.
>
>Aargh!! No, no!  Please don't say that this system doesn't support "SMART" 
>refresh windows!
 
This (an application that didn't update itself properly) has
happened to me twice, under odd conditions.  My suspicion is that
it is an alpha-bug, and will be history by 0.9.  Most of the real
clumsy things are listed as "fixed by 0.9", and the
evolving-interface class is on the list (basically, it looks like
the user-interface guidelines aren't set in stone yet, so there are
mostly-minor differences between applications).

I think the whole point of building an application with the
object-oriented approach is that a window class (proper Objective C
wording?  Haven't gotten any docs on it yet to find out) will handle
the refresh message itself (ouch, he says, as he opens himself to
charges of pure ignorance).

  Oh well, time to hit the bookstore for a good book on Objective C.
Suggestions, anyone?
-=-
J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)
"Give him some orange juice and a sugar cookie, ...
 maybe a tetanus shot.  He'll be fine."