On Nov 12, 2016, at 11:41 AM, Richard Charles wrote:
> The current documentation seems to be well formatted for display on an iPad.
> Does anyone have a programming work flow that uses the documentation
> displayed on an iPad or iOS device?
>
> I suppose if you are commuting to work riding a t
> On 12 Nov 2016, at 18:41, Richard Charles wrote:
>
> The current documentation seems to be well formatted for display on an iPad.
> Does anyone have a programming work flow that uses the documentation
> displayed on an iPad or iOS device?
>
> I suppose if you are commuting to work riding a
> On Nov 12, 2016, at 11:41, Richard Charles wrote:
>
> Why is the documentation team going down this bizarre path? Do they really
> think we will be programming on iPads some day?
I find the overly large format of the Xcode doc viewer to be really hard to
parse at a glance. It's not at all co
The current documentation seems to be well formatted for display on an iPad.
Does anyone have a programming work flow that uses the documentation displayed
on an iPad or iOS device?
I suppose if you are commuting to work riding a train or a bus and want to
review the documentation on your iPad
> On 12 Nov 2016, at 01:34, James Walker wrote:
>
> However, the new cell has failed to copy much of the state of the old one.
> Things like title, font, target, action, bezelStyle... I can manually copy
> anything that I notice is missing, but I'm just wondering why the keyed
> archiver ap
Well, I have two responses.
First let me ask the question a different way: if people use this app, it
is because they want the *watch* to “buzz” them at a certain time. Is there
any foolproof way to make that happen?
Second, I’m not doing anything in the iPhone portion of the app, which it
think
