So, I went to take a screenshot to show what I was seeing before, and it looks like the problem is fixed in the latest version of XCode (or I am crazy and it was never a problem). What I was seeing was that synthesized fields did not show up in the variable window when debugging, and I would constantly have to type "po self.foo" to inspect things.
Anyways, doesn't seem to be a problem now, so I'll scratch this one from the list :). On Wed, Nov 7, 2012 at 9:12 AM, Becky Gibson <[email protected]> wrote: > Ok, this doesn't seem to be a little thing and it concerns me: > > -iOS don't synthesize variables via properties since it causes them to not > show up in the debugger. With ARC, it is now just as convenient to use > fields as it is properties for private members anyways. > > Can you explain this a bit better? Apple recommends using properties why > would be deviate from that? I haven't seen any issues debugging, can you > elaborate? Some example code would help to make sure we are all using the > same terms. > > thanks, > -becky > > > On Tue, Nov 6, 2012 at 11:54 PM, Andrew Grieve <[email protected]> > wrote: > > > Here's my list of things I want to see done / plan on doing: > > > > Bigger things: > > -Make the cordova/scripts sane for iOS and Android (CB-1668) > > -iOS: Work on moving symbols that we don't want to be in our public API > out > > of header files (or into _private.h header files) > > -Android: Work on making symbols private / package-private that we don't > > want to be in our public API. > > -Create a Google cordova plugin to provide OAuth2 for Google APIs via > > gtm-oauth2 on iOS and AccountManager on Android. > > > > Littler things: > > -iOS don't synthesize variables via properties since it causes them to > not > > show up in the debugger. With ARC, it is now just as convenient to use > > fields as it is properties for private members anyways. > > > > -Create a helper function to reduce exec() param checking in the JS. e.g. > > Instead of a bunch of if() blocks with throws / errBack calls, we'd have: > > function(win, fail, num, str, func, opt_numOrString, opt_str) { > > // n = number > > // s = string > > // f = function > > // * = anything goes > > // S = string or null or undefined (likewise, N and F) > > checkedExec('nsf*S', win,fail,'Service', 'action', > > [num,str,func,opt_numOrString, opt_str]); > > } > > > > > > Also note that both of Shaz's items would appear on this list if he > hadn't > > pointed them out already :) > > > > > > > > > > On Tue, Nov 6, 2012 at 3:21 PM, Simon MacDonald > > <[email protected]>wrote: > > > > > Sure, we've only been delaying it for about a year now, what's another > > > month. > > > > > > Passive aggressiveness FTW! > > > > > > Simon Mac Donald > > > http://hi.im/simonmacdonald > > > > > > > > > On Tue, Nov 6, 2012 at 3:17 PM, Shazron <[email protected]> wrote: > > > > > > > I agree it's a mess. Seeing stuff on the iOS 2.3.0 plate perhaps we > can > > > > slate it for 2.4.0 -- but we can plan what needs to be done now I > > > suppose. > > > > > > > > > > > > On Tue, Nov 6, 2012 at 6:42 AM, Simon MacDonald > > > > <[email protected]>wrote: > > > > > > > > > The InAppBrowser would be great to have in 2.3.0. > > > > > > > > > > Can we do a review of the Media API as well? It's a mess. Maybe we > > can > > > > just > > > > > fix the inconsistencies this release and look at a true Audio API > > for a > > > > > future release. > > > > > > > > > > Simon Mac Donald > > > > > http://hi.im/simonmacdonald > > > > > > > > > > > > > > > On Mon, Nov 5, 2012 at 7:16 PM, Shazron <[email protected]> wrote: > > > > > > > > > > > I'd like to implement InAppBrowser in 2.3.0? > > > > > > https://issues.apache.org/jira/browse/CB-1506 > > > > > > > > > > > > Also I'd like to migrate the Cordova.plist to config.xml for iOS: > > > > > > https://issues.apache.org/jira/browse/CB-1108 > > > > > > > > > > > > > > > > > > > > >
