• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: an interesting delegate design issue raised by IB...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: an interesting delegate design issue raised by IB...


  • Subject: Re: an interesting delegate design issue raised by IB...
  • From: "Michael B. Johnson" <email@hidden>
  • Date: Wed, 12 Sep 2001 14:45:47 -0700
  • Organization: Pixar Animation Studios

Ondra Cada wrote:
>
> Michael,
>
> >>>>>> Michael B. Johnson (MBJ) wrote at Wed, 12 Sep 2001 10:57:57 -0700:
> MBJ> >Of course, you can send those notifications using NSPostWhenIdle, which
> MBJ> >would easily solve this problem (but not some more elaborated ones).
> MBJ>
> MBJ> like what? I'm interested - I wouldn't do it this way, but I'm
> MBJ> interested in what problems might arise from doing it this way.
>
> Like if I (as a programmer) _for any reason_ don't _want to_ redisplay the
> change immediately.
>
> Frankly, I can't imagine none such reason just now. My programming
> experience just kind of hints that *if* the API would not make that possible,
> then some such reason would occur one day ;)
>

*Then* I change the API, not before. I try to design things simply, so that they can used
immediately, and then progressively expose more as needed. If someone can't come up with a
compelling real case of why they need something in an API, it shouldn't be in there. Otherwise,
it's not clear what is "best practice".

Just my opinion, of course.


> MBJ> Ooh, I really don't like that. It would be too easy to have things get
> MBJ> out of sync.
>
> As you perhaps noticed, with API I am for flexibility, even if it happens to
> be dangerous when not used properly. That's just my opinion, of course (but
> I guess Brad Cox had the very same idea when designed ObjC!).

fair enough. I'm a tool designer for artists first, and my programming skills (such as they are
:-)) have to be led by that. If things can get out of sync, they will. For me, that means wasted
time, and potential creativity that gets nipped in the bud because users become more cautious about
how flexible their workflow can be, which is always bad.

This is obviously more of a discussion of philosophy now, so perhaps we can just agree to disagree.



--> Michael B. Johnson, Ph.D. -- email@hidden
--> Studio Tools, Pixar Animation Studios
--> http://xenia.media.mit.edu/~wave


  • Follow-Ups:
    • Re: an interesting delegate design issue raised by IB...
      • From: Ondra Cada <email@hidden>
References: 
 >Re: an interesting delegate design issue raised by IB... (From: "Michael B. Johnson" <email@hidden>)
 >Re: an interesting delegate design issue raised by IB... (From: Ondra Cada <email@hidden>)
 >Re: an interesting delegate design issue raised by IB... (From: "Michael B. Johnson" <email@hidden>)
 >Re: an interesting delegate design issue raised by IB... (From: Ondra Cada <email@hidden>)

  • Prev by Date: Applications folder path
  • Next by Date: Re: Can I use more than one controller in same application
  • Previous by thread: Re: an interesting delegate design issue raised by IB...
  • Next by thread: Re: an interesting delegate design issue raised by IB...
  • Index(es):
    • Date
    • Thread