Re: Documentation Workflow

2016-11-12 Thread Alex Zavatone

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 train or a bus and want to 
> review the documentation on your iPad this might work well. This might also 
> work if the documentation was sitting at your side on an iPad like a book or 
> if you wanted to read the documentation like you would read a bound book. 
> However I would be surprised if many programmers have a programming work flow 
> like this. It is simply too restrictive, slow, and cumbersome when actually 
> coding.
> 
> My current workflow has a local copy of OS X 10.9 documentation displayed in 
> Safari, often using multiple tabs, on a second display. I find this 
> documentation setup to be very helpful, searchable, inclusive, and productive.
> 
> Why is the documentation team going down this bizarre path? Do they really 
> think we will be programming on iPads some day?
> 
> --Richard Charles

The important thing is that we are not now.

Apparently, the fonts are STILL too visible.  The text in the documentation 
needs to be even skinnier so there is no possible chance that we can read it.  
And it's really good that there are no PDF documents for us to keep as 
reference for anything that we searched for.

Whomever is making these decisions at Apple should be checked in to a place 
where they are not allowed to declare policy to anyone again, ever.



___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Documentation Workflow

2016-11-12 Thread Pascal Bourguignon

> 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 train or a bus and want to 
> review the documentation on your iPad this might work well. This might also 
> work if the documentation was sitting at your side on an iPad like a book or 
> if you wanted to read the documentation like you would read a bound book. 
> However I would be surprised if many programmers have a programming work flow 
> like this. It is simply too restrictive, slow, and cumbersome when actually 
> coding.
> 
> My current workflow has a local copy of OS X 10.9 documentation displayed in 
> Safari, often using multiple tabs, on a second display. I find this 
> documentation setup to be very helpful, searchable, inclusive, and productive.
> 
> Why is the documentation team going down this bizarre path? Do they really 
> think we will be programming on iPads some day?

Indeed, the main problem with the documentation on iPad, is that it’s harder to 
copy-and-paste from it to Xcode source windows. 
But I hear that in macOS Sierra and iOS 10, it’s possible to copy-and-paste 
from an iPad to the Mac?


-- 
__Pascal J. Bourguignon__



___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Documentation Workflow

2016-11-12 Thread Steve Mills
> 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 conducive to developer needs.

Steve via iPad


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Documentation Workflow

2016-11-12 Thread Richard Charles
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 this might work well. This might also 
work if the documentation was sitting at your side on an iPad like a book or if 
you wanted to read the documentation like you would read a bound book. However 
I would be surprised if many programmers have a programming work flow like 
this. It is simply too restrictive, slow, and cumbersome when actually coding.

My current workflow has a local copy of OS X 10.9 documentation displayed in 
Safari, often using multiple tabs, on a second display. I find this 
documentation setup to be very helpful, searchable, inclusive, and productive.

Why is the documentation team going down this bizarre path? Do they really 
think we will be programming on iPads some day?

--Richard Charles


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Substituting instance of cell subclass for instance of superclass

2016-11-12 Thread Jonathan Mitchell

> 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 approach here doesn't work.

It might be that NSButton archives the missing properties and applies them to 
the unarchived cell during initialisation.


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Make WatchKit app show local notification

2016-11-12 Thread Charles Jenkins
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 should mean if the watch won’t show the notification, the phone
should by default. I’ll work on it today to see if that’s the case, and if
not I’ll try adding notification handling to the phone.


On Fri, Nov 11, 2016 at 9:49 AM, Jeff Kelley  wrote:

> The recommended approach here (I think) is to show the notification on
> whichever device the user is using. Are you implementing any of the
> UserNotification framework pieces on the phone? Would it work for your
> purposes if the alert sometimes appeared there?
>
>
> Jeff Kelley
>
> slauncha...@gmail.com | @SlaunchaMan  |
> jeffkelley.org
>
> On Nov 11, 2016, at 7:13 AM, Charles Jenkins  wrote:
>
> Thanks, Jeff! Lordy be, the only thing I want is a sound and prominent
> haptic when the countdown reaches zero. Is there no foolproof way to
> achieve that? Everything I’ve tried seems to only work in certain cases.
>
>


-- 

Charles
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com