• 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: How to implement an Xcode-style hierarchical file browser
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to implement an Xcode-style hierarchical file browser


  • Subject: Re: How to implement an Xcode-style hierarchical file browser
  • From: "I. Savant" <email@hidden>
  • Date: Tue, 26 Sep 2006 13:36:44 -0400

I guess I should add that the other reason I asked the original question is that the documentation for NSOutlineView is eerily silent regarding the use of NSTreeController and bindings. I've implemented a few outline views already using bindings, but had to work that out pretty much on my own as there's not much in the way of documentation or examples (or wasn't when I last did this and it still seems to be the case). Is it the case that outlines are still better implemented using data sources and delegates, as opposed to bindings? I know that support for binding an ouline view lagged behind similar support for tables, but this has been added quite a while ago.

NSTreeController is tricky and the documentation is currently insufficient (given the mass confusion evident by many related threads on this list :-)). You're not alone there.

Regarding the 'data source or bindings' argument, either way is just as effective in the general sense. Sure, if you know how to use it, NSTreeController makes it far easier to work with Core Data, but you most certainly can use data source methods in combination with Core Data. The two are not mutually exclusive. I have a project which uses Core Data for its store but uses almost no bindings.

Stick with what you're most comfortable with for now and you should be fine. At the very least, learn how to use NSOutlineView on its own (data source methods) before throwing Bindings and Core Data into the mix.


Also I am guessing that if the model represented in the outline view is based on a Core Data representation then there may be special concerns or opportunities to use bindings but I might be wrong.

Special concerns? Not really - just understand KVC / KVO, Cocoa Bindings, and Core Data. Opportunities? I'm discovering new ones every day. :-) Again, NSTreeController *is* a bit confusing, but it's more so if you don't understand outline views in general.


--
I.S.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >How to implement an Xcode-style hierarchical file browser (From: Rick Hoge <email@hidden>)
 >Re: How to implement an Xcode-style hierarchical file browser (From: Murat Konar <email@hidden>)
 >Re: How to implement an Xcode-style hierarchical file browser (From: Rick Hoge <email@hidden>)
 >Re: How to implement an Xcode-style hierarchical file browser (From: "I. Savant" <email@hidden>)
 >Re: How to implement an Xcode-style hierarchical file browser (From: Rick Hoge <email@hidden>)

  • Prev by Date: Re: Getting an NSManagedObject just added through an NSArrayController
  • Next by Date: Re: Problem with relationships in Core Data
  • Previous by thread: Re: How to implement an Xcode-style hierarchical file browser
  • Next by thread: Re: How to implement an Xcode-style hierarchical file browser
  • Index(es):
    • Date
    • Thread