Re: Basics of Cocoa Bindings

On Sep 12, 2015, at 06:55 , Alex Hall wrote: > > if you need to display an array or dictionary in a table, when that data > source could be updated at a random time or asynchronously, how might you do > it without bindings? Ah, but what do you mean by “without”? There are

Re: Basics of Cocoa Bindings

> On Sep 12, 2015, at 08:59, dangerwillrobinsondan...@gmail.com wrote: > > You would implement the NSTableView data source and delegate methods in a > class. In a simple case in the app delegate to try them out and get used to > them. That's how my project started out, using a data source

Re: Basics of Cocoa Bindings

IT! WORKS! Thanks so much for your help. Now I'll advance this project, to test more aspects of this binding, and hopefully grasp things more completely with practical examples I make. Out of curiosity, you said you never use table view bindings anymore. If you had to display the contents of

Re: Basics of Cocoa Bindings

You would implement the NSTableView data source and delegate methods in a class. In a simple case in the app delegate to try them out and get used to them. Sent from my iPhone > On Sep 12, 2015, at 9:28 PM, Alex Hall wrote: > > IT! WORKS! Thanks so much for your help.

Re: Basics of Cocoa Bindings

(ugh, reposted due to size moderation, again) On Sep 11, 2015, at 13:40 , Alex Hall wrote: > What I've done so far is set things up, but not gotten the app to run. At > first, I was getting some odd errors, but I eventually realized that > populating my tweetsArray object

Re: Basics of Cocoa Bindings

On Sep 11, 2015, at 21:05 , Quincey Morris wrote: > > There’s a sub-hierarchy of 3 other things, called “Table Cell View” […], > "Table View Cell” […] and “Table View Cell” […]. On reflection, I feel obliged to emphasize — for anyone who enjoys the

Re: Basics of Cocoa Bindings

On Sep 11, 2015, at 15:49 , Alex Hall wrote: > > I followed all of that, and I see what you're saying. The binding to an array > is, to it, no different than binding to a boolean or a string, it's just a > single object. But how does a binding know what it's accessing? I

Re: Basics of Cocoa Bindings

(continued from part 1) On Sep 11, 2015, at 15:49 , Alex Hall > wrote: > > Out of curiosity, why do I not need these but I *do* need insert and remove > methods for the property? All standard UI elements use KVC to retrieve their values, or use

Re: Basics of Cocoa Bindings

> On Sep 11, 2015, at 21:04, Quincey Morris > wrote: > > On Sep 11, 2015, at 15:49 , Alex Hall > wrote: >> >> I followed all of that, and I see what you're saying. The binding to an >> array is, to it, no

Re: Basics of Cocoa Bindings

Minor update: in the zip file, in ViewController.swift, I hadn't changed the variable name in the for loop. It should be "tweets", not "tweetsArray". The project builds, and the error appears, either way. Actually, that it builds with a mistake like that seems a bit odd. Anyway, just something

Re: Basics of Cocoa Bindings

On Sep 11, 2015, at 20:20 , Alex Hall wrote: > > Okay, the error I'm seeing (about [ViewController count]) is the table asking > for how big it should be. Actually, that’s not it, though you can be excused for thinking so. What’s wrong is that you tried to add way too many

Re: Basics of Cocoa Bindings

(reposted to the list in 2 parts because the whole thing was 1 byte over the stupid limit) On Sep 8, 2015, at 21:04 , Alex Hall > wrote: > > and too little comprehension of how bindings work I think it’s both easier than you think, and harder.

Re: Basics of Cocoa Bindings

(continued from part 1) The clever thing about array controllers is that to metal pieces they look like plastic, and to plastic pieces they look like metal. Hence the name “mediating”. As in legal arbitration, the mediator looks to each side like the opposing side’s advocate. Their other

Re: Basics of Cocoa Bindings

On Sep 8, 2015, at 11:04 PM, Alex Hall wrote: > I've created a new thread, because I obviously don't understand nearly as > much about Cocoa Bindings as I thought I did. Bindings is a complex and advanced topic. It's built on top of other technologies, which you need to

Basics of Cocoa Bindings

I've created a new thread, because I obviously don't understand nearly as much about Cocoa Bindings as I thought I did. Adding it to my existing project is just not working out at all, and I think it's because I'm starting with too complex a model and too little comprehension of how bindings

Re: Basics of Cocoa Bindings

> On 2015 Sep 08, at 21:04, Alex Hall wrote: > > why are keyPathsForValuesAffecting needed? Is this method taking the > place of something I might do in IB, or is this something different? Of course, they are not required, as many successful apps were written before we