> To implement the proposed interface, one cannot solely use bindings to
> accomplish this w/o modeling the intermediary join table. The relationship
> management is instead accomplished via code (through NSSets and so on as per
> mmalc's example).
Correct; not with a straight tableview. You can
[mailto:cocoa-dev-
> bounces+jmunson=his@lists.apple.com] On Behalf Of Jon C. Munson II
> Sent: Thursday, March 26, 2009 9:36 AM
> To: 'Melissa J. Turner'
> Cc: 'Cocoa Developers'
> Subject: RE: Implementing a many-to-many ("reflexive") relationshi
[Jon C. Munson II] OK. Benjamin Stiglitz responded suggesting I take a
look at the ToManyCheckbox example on mmalc's page, so I'll do that and see
if that clarifies things. Also, I noticed in the iClass example that code
is used to support the relationship and so on. Is that the recommended
"t
On Mar 25, 2009, at 13:44, Jon C. Munson II wrote:
[Jon C. Munson II] OK. Benjamin Stiglitz responded suggesting I
take a
look at the ToManyCheckbox example on mmalc's page, so I'll do that
and see
if that clarifies things. Also, I noticed in the iClass example
that code
is used to sup
On Mar 25, 2009, at 2:44 PM, Jon C. Munson II wrote:
Do you mean here that you will "pop up" a window that contains an
NSTableView that will be used to select rows of Entity B? Correct
language is critical. I think most Cocoa developers would assume that
"popup" means NSpopupButton.
[Jon C. M
>
> On Mar 25, 2009, at 7:47 AM, Jon C. Munson II wrote:
>
> > Two entities, one named A, the other named B. A and B have a
> > reflexive
> > relationship with each other (that would be a many-to-many type). The
> > backend is a SQLite store (not that it should matter).
>
> To be clear, a refl
>
> For the sake of this discussion, here's a sample entity layout:
>
> Two entities, one named A, the other named B. A and B have a reflexive
> relationship with each other (that would be a many-to-many type). The
> backend is a SQLite store (not that it should matter).
>
> I'd like my interf
On Mar 25, 2009, at 7:47 AM, Jon C. Munson II wrote:
Two entities, one named A, the other named B. A and B have a
reflexive
relationship with each other (that would be a many-to-many type). The
backend is a SQLite store (not that it should matter).
To be clear, a reflexive relationship is
Namaste!
For the sake of this discussion, here's a sample entity layout:
Two entities, one named A, the other named B. A and B have a reflexive
relationship with each other (that would be a many-to-many type). The
backend is a SQLite store (not that it should matter).
I'd like my interface to
