Re: Documentation Workflow

> On Dec 6, 2016, at 3:45 PM, Carl Hoefs wrote: > > Just now I was looking for a list of NSString method signatures to peruse. Open NSString.h? —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do

Re: Documentation Workflow

> On Dec 3, 2016, at 11:52 AM, Richard Charles wrote: > >> On Dec 2, 2016, at 11:34 AM, Slipp Douglas Thompson >> wrote: >> >> Alternatively, there's always archive.org's Wayback Machine. > >> Since developer.apple.com's URL paths have

Re: Documentation Workflow

> On Dec 2, 2016, at 11:34 AM, Slipp Douglas Thompson > wrote: > > Alternatively, there's always archive.org's Wayback Machine. > Since developer.apple.com's URL paths have changed quite a bit with the > recent narrow-body-giant-text-ification, I plugged >

Re: Documentation Workflow

> On Dec 2, 2016, at 11:34 AM, Slipp Douglas Thompson > wrote: > > Alternatively, there's always archive.org's Wayback Machine. Very helpful. I did not know this existed. Thanks so much for the example and instructions. --Richard Charles

Re: Documentation Workflow

I bet the documentation has gotten leaner since Apple's developers have been dog-fooding the Xcode feature, Add Documentation, available under the Editor:Structure men path, and only using what’s in there. Just kidding…but maybe not! -- Gary L. Wade http://www.garywade.com/

Re: Documentation Workflow

Alternatively, there's always archive.org's Wayback Machine. For example, the Core Data Programming Guide from 2014-07-03 is available right here:

Re: Documentation Workflow

> On 2 Dec 2016, at 23:25, Richard Charles wrote: > > Somebody needs to start an online repository of older Apple developer > documentation in pdf format. I did do exactly that for the legacy AppleScript stuff[1] when it started disappearing, but it’d be a bit of a

Re: Documentation Workflow

> On Nov 12, 2016, at 10:41 AM, 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 hate to beat a dead horse here but there really does seem to be an effort underway

Re: Documentation Workflow

> On Nov 17, 2016, at 12:15 PM, Carl Hoefs > wrote: > > Fixing the layout of the documentation doesn't help the core problem, namely, > the way in which it's organized. Each page is so sparse as to be almost > worthless. Well spoken. > You have to drill down

Re: Documentation Workflow

Dash for iOS has just been open sourced. It's a doc viewer for iPad/iPhone... https://github.com/Kapeli/Dash-iOS On 17 November 2016 at 11:23, Laurent Daudelin wrote: > What’s the 2 “gist” files you are mentioning? > > -Laurent. > -- > Laurent Daudelin >

Re: Documentation Workflow

What’s the 2 “gist” files you are mentioning? -Laurent. -- Laurent Daudelin laur...@nemesys-soft.com AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/

Re: Documentation Workflow

Fixing the layout of the documentation doesn't help the core problem, namely, the way in which it's organized. Each page is so sparse as to be almost worthless. You have to drill down 2, 3, 4 or more links to find the information that you want, dragging the reader through page after page...

Re: Documentation Workflow

Adding this CSS alone increases readability dramatically for the docs pages when viewing from a browser. @namespace url(http://www.w3.org/1999/xhtml); *{font-family:"Tahoma", sans-serif !important;} Whatever Apple's using now looks skinny and is is simply unsettling. Now, if we could only get

Re: Documentation Workflow

On Nov 17, 2016, at 9:13 AM, Slipp Douglas Thompson wrote: > No, you don't need to know HTML or CSS to get this to work. > > Here's a basic step-by-step: > > 1. Download & install the Stylish plugin/add-on/extension for your browser of > choice. The official userstyles.org Stylish is

Re: Documentation Workflow

No, you don't need to know HTML or CSS to get this to work. Here's a basic step-by-step: 1. Download & install the Stylish plugin/add-on/extension for your browser of choice. The official userstyles.org Stylish is available for Chrome (

Re: Documentation Workflow

> On Nov 17, 2016, at 6:45 AM, Slipp Douglas Thompson > wrote: [snip] > I got tired of the layout issues and cooked up some quick Stylish CSS to > rectify developer.apple.com/reference/* pages. [snip] > My Stylish CSS (in Mozilla Format) can be found at: >

Re: Documentation Workflow

> On Nov 12, 2016, at 10: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? Submitted bug report.

Re: Documentation Workflow

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

Re: Documentation Workflow

> 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

Re: Documentation Workflow

> 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

Documentation Workflow

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