CoreDate (was: [Biococoa-dev] WWDC2005)

Charles PARNOT charles.parnot at stanford.edu
Thu Feb 17 14:19:14 EST 2005


>And the KVC, KVO protocols are first of all easy to implement, second it gives you bindings for (almost) free and IMHO all classes we produce should be compatible (even if you make the 10.2 compatible), key value coding (using accessors) is something we do already anyway. It's not difficult and not that much of work actually.

I do agree with Alex that KVC should be fairly easy to add. I also do like John's idea of sticking to 10.2 as much as possible, which should be possible with KVC. I also know that there are some differences which could get quite annoying, and that the 10.2 KVC is not as consistent and usable as the KVC in 10.3... but that may be fixable with some NSObject category. Anyway, after all these however/but, the bottom line is: my opinion is we should try to implement KVC asap and at the same time, stick to the 10.2 APIs as long as possible.

Regarding other 10.3-sepcific APIs, here are the questions we should answer (in particular Alex):
* Alex, what APIs other than binding are you refering to? Can we narrow down to just bindings the question of '10.2 vs 10.3'? Are there any other critical super-useful 1.3-specifc APIs that we are going to use? (e.g. NSIndexSet --> possible work-arounds)
* Then, about bindings: are there really any use of bindings at the framework level? The bindings would be in the app, right? We would just have to be KVC-compliant in the framework. Do the bindings use 10.2 deprecated methods when forced to?


>Remember, right now 10% is on 10.2, once Tiger will be out that will drop to even less (I know people who will skip 10.3 but will go for 10.4), and our framework isn't even out yet (add a few months) and the first app will come even later right (add even a few more months), who will still use 10.2 by then?

Probably true, future will tell. My prediction: there will be 5% people stuck at 10.2 for a long long time!

charles

NB: and yes, Koen, we should just be coding instead of chatting, for God's sake!

-- 
Help science go fast forward:
http://cmgm.stanford.edu/~cparnot/xgrid-stanford/

Charles Parnot
charles.parnot at stanford.edu

Room  B157 in Beckman Center
279, Campus Drive
Stanford University
Stanford, CA 94305 (USA)

Tel +1 650 725 7754
Fax +1 650 725 8021



More information about the Biococoa-dev mailing list