• 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: UI for nonuniform Core Data object hierarchy
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UI for nonuniform Core Data object hierarchy


  • Subject: Re: UI for nonuniform Core Data object hierarchy
  • From: Wain <email@hidden>
  • Date: Tue, 24 Jan 2006 18:01:58 +0000

Yep,

The easiest way is probably to store the window in it's own nib file
and then whenever something gets double clicked you can load a new copy.
You will also be able to setup a controller in the nib file which will link to the owner
you specify when calling 'instantiateNibWithOwner:topLevelObjects' in your
double click action.


Hope that makes sense :)

Wain


On 24 Jan 2006, at 00:19, Michael Gardner wrote:

Thanks for the tip. Will this method still work if I want to create a
new window for each unique object that gets double-clicked, rather
than replacing the contents of a single inspector-style window?

Mike

On 1/23/06, Wain wrote:
Hi,

Setup the first table view with a controller to display it's contents
as normal.
Use '- (void)setDoubleAction:(SEL)aSelector' to set the operation to
be called when the table view is double clicked (probably on your
delegate).
In this operation you can load your other window and setup a
controller to supply it with data.

No sample code but this is generally along the lines of a master
detail interface, your case is a little more complex as you want your
second table view in a separate window (so probably a separate nib)
but your child info is basically the details about the selected parent.


If you haven't used a master detail interface before it might be a
good idea to implement both sides in the same window to begin with.

Wain

On 20 Jan 2006, at 21:18, Michael Gardner wrote:

I'm using Core Data to manage a nonuniform hierarchy of objects (i.e.
the children of a given node do not have the same class as the node
itself).


My problem is in creating the UI: a tree seems inappropriate, since
the different types of objects might have very different attributes;
instead I want an NSTableView where double-clicking on an object pops
up a new window like the first, with an NSTableView showing the
children of the object in question.


How might I do this? Apologies if this question is too noobish, but I
can't find docs or sample code to lead me in the right direction.


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






___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
_______________________________________________
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: 
 >UI for nonuniform Core Data object hierarchy (From: Michael Gardner <email@hidden>)
 >Re: UI for nonuniform Core Data object hierarchy (From: Wain <email@hidden>)

  • Prev by Date: Re: Database frameworks for Cocoa
  • Next by Date: Re: Big/Arbitrary integers
  • Previous by thread: Re: UI for nonuniform Core Data object hierarchy
  • Next by thread: NSTableView cells with custom views: tab order
  • Index(es):
    • Date
    • Thread