• 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: Multiple NSTableView question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multiple NSTableView question


  • Subject: Re: Multiple NSTableView question
  • From: Phillip Mills <email@hidden>
  • Date: Thu, 21 Jun 2001 13:38:33 -0400

On 6/21/01 12:17 PM, "Greg Titus" <email@hidden> wrote:

> What you are driving at is a different question: What if I have two
> table views with some of the data manipulation code in common and other
> parts that are unique?

Yes. Thanks for the example...I *really* like it.

I have a good (I believe) background in OOP, but not in MVC. It may take
awhile for me to internalize the idea that one of the things I think of as
an object might be better represented as two or three program-domain
objects.

> That having been said, making something more object oriented is supposed
> to help you as a programmer get more done faster in a more maintainable
> way. But it's a technique among many other techniques, not a religion.

Understood, but a major problem that the tool is excellent at overcoming is
cascading dispatch cases...prime spaghetti territory. Although the original
example in this thread was simple and clear, it got me thinking of what it
would look like in a more elaborate example.

Thanks again.


References: 
 >Re: Multiple NSTableView question (From: Greg Titus <email@hidden>)

  • Prev by Date: Re: WWDC Dev Tools / Software update
  • Next by Date: RE: Cocoa/EOF for non-enterprise apps
  • Previous by thread: Re: Multiple NSTableView question
  • Next by thread: Re: Multiple NSTableView question
  • Index(es):
    • Date
    • Thread