Re: Documentation Workflow

[Jens Alfke]

> 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 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

[Carl Hoefs]

> 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 changed quite a bit with the 
>> recent narrow-body-giant-text-ification, I plugged 
>> https://developer.apple.com/library/ios/navigation/ into the Wayback Machine 
>> ( https://developer.apple.com/library/mac/navigation/ also works), chose a 
>> capture date a couple years ago, and then used the “Documents [ 
>> ] 4293 of 4293” search input to find the doc I was looking for.
> 
> It appears that October 21, 2014 was the last archive date for old style iOS 
> documentation and content.
> 
> It appears that November 5, 2015 was the last archive date for old style mac 
> documentation and content.
> 
> This would be a good starting point if you are looking for something older 
> that is now gone.
> 

Just now I was looking for a list of NSString method signatures to peruse. Is 
that now impossible? It seems all methods are shoveled onto a single mega-page 
called "Methods to Override", with full descriptions, but no there's no 
overview method list any more, as there is no disclosure triangle on the 
"Methods to Override" element in the left column. 

-Carl


___

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

[Richard Charles]

> 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 
> https://developer.apple.com/library/ios/navigation/ into the Wayback Machine 
> ( https://developer.apple.com/library/mac/navigation/ also works), chose a 
> capture date a couple years ago, and then used the “Documents [ ] 
> 4293 of 4293” search input to find the doc I was looking for.

It appears that October 21, 2014 was the last archive date for old style iOS 
documentation and content.

It appears that November 5, 2015 was the last archive date for old style mac 
documentation and content.

This would be a good starting point if you are looking for something older that 
is now gone.

--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: Documentation Workflow

[Richard Charles]

> 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


___

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

[Gary L. Wade]

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/ 
___

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

[Slipp Douglas Thompson]

Alternatively, there's always archive.org's Wayback Machine.

For example, the Core Data Programming Guide from 2014-07-03 is available right 
here: 
https://web.archive.org/web/20140703032131/https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/CoreData/cdProgrammingGuide.html#//apple_ref/doc/uid/TP40001075
 .  Both the HTML & PDFs are archived, so the PDF is downloadable from the 
“PDF” link (which gives you 
https://web.archive.org/web/20140702154734/https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/CoreData/CoreData.pdf
 ).

Since developer.apple.com's URL paths have changed quite a bit with the recent 
narrow-body-giant-text-ification, I plugged 
https://developer.apple.com/library/ios/navigation/ into the Wayback Machine ( 
https://developer.apple.com/library/mac/navigation/ also works), chose a 
capture date a couple years ago, and then used the “Documents [ ] 
4293 of 4293” search input to find the doc I was looking for.

— Slipp


> On Dec 2, 2016, at 10:36 AM, 2551phil <2551p...@gmail.com> wrote:
> 
> 
>> 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 mammoth task to do the same for the 
> whole of the Cocoa APIs. The best alternative I found once Apple removed the 
> PDFs was to use Dash[2]. 
> 
> [1]. https://applescriptlibrary.wordpress.com
> [2]. https://kapeli.com/dash
> 
> 
> 
> Best
> 
> 
> Phil
> ___
> 
> 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/apple%2Bcocoa-dev%40slippyd.com
> 
> This email sent to apple+cocoa-...@slippyd.com


___

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

[2551phil]

> 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 mammoth task to do the same for the whole 
of the Cocoa APIs. The best alternative I found once Apple removed the PDFs was 
to use Dash[2]. 

[1]. https://applescriptlibrary.wordpress.com
[2]. https://kapeli.com/dash



Best


Phil
___

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

[Richard Charles]

> 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 to dumb down the developer documentation.

Here is a fustrating example I just encountered.

The current online documentation for NSManagedObject refers three times to a 
"Managed Object Accessor Methods" section in the Core Data Programming Guide. 
However it appears this section has now been entirely removed from the guide. 
Reaching this conclusion is a difficult task because there is no longer a pdf 
of the guide to search through. Apple only provides searching through all 
guides or manually drilling and dragging through a single guide searching for 
the revelant information.

So I guess the lesson here is if you have pdfs of the documentation you may 
want to consider saving it rather than tossing it. Somebody needs to start an 
online repository of older Apple developer documentation in pdf format. Now 
that would be helpful.

--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: Documentation Workflow

[Richard Charles]

> 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 2, 3, 4 or more links to find the information that you 
> want, dragging the reader through page after page…

Exactly. Drilling and dragging through the documentation is unproductive.

> Why not simply have all the relevant information on the page, where it 
> belongs?

Seems logical.

Why not have the web server detect if you are on a mobile device or on a PC. If 
you are on a mobile device (iPad or iPhone) then drilling and dragging may be 
acceptable. If you are on a PC (Mac) then please give the developer a more 
productive layout and organization of the documentation.

--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: Documentation Workflow

[David Brittain]

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
> laur...@nemesys-soft.com 
> AIM/iChat/Skype:LaurentDaudelin
> http://www.nemesys-soft.com/ 
> Logiciels Nemesys Software
>
> > On Nov 17, 2016, at 10:13, Slipp Douglas Thompson <
> apple+cocoa-...@slippyd.com> 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 available for
> Chrome ( https://chrome.google.com/webstore/detail/stylish/
> fjnbnpbmkenffdnngjfgmeleoegfcffe?hl=en ) and Firefox (
> https://addons.mozilla.org/en-us/firefox/addon/stylish/ ), though it
> looks like someone else made a Safari version ( http://sobolev.us/stylish/
> ).
> > 2. Download the 2 files from that gist.
> > 3. Open up the Stylish plugin/add-on/extension's UI and click the import
> button, choose one file, then click import and choose the other file.
> > 4. Enjoy better layout/styling whenever you visit a URL matching
> `http[s]://developer.apple.com/reference/*`.  ;-)
> > 5 (optional). Stylish for Chrome allows you to toggle styles on & off
> for the current page by clicking the toolbar icon for the extension (to the
> right of the address bar; the Stylish extension's icon is an “S” in a
> 4-colored square), so you can decide on-the-fly if you really want to use
> these changes or not.  I'd imagine Stylish for other browsers works
> similarly.
> > 6 (optional). Modify the CSS to your liking.  The most obvious point of
> customization would be the `font-size: 10pt !important;` line— you can
> change the `10pt` to `12pt` or `24pt` or `6pt` or whatever other numerical
> font size you please.
> >
> > 
> >
> > Also, I'm not sure if those images went through, so here they are again,
> hosted externally:
> >
> > Turns this: https://cl.ly/0m1c462d1z40
> > Into this: https://cl.ly/2b03340B3F2y
> >
> > — Slipp
> >
> >
> >> On Nov 17, 2016, at 8:55 AM, Richard Charles 
> wrote:
> >>
> >>
> >>> On Nov 17, 2016, at 6:45 AM, Slipp Douglas Thompson <
> apple+cocoa-...@slippyd.com> 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:
> https://gist.github.com/capnslipp/208d50e8a6c630d053b4f22e704f28a5
> >>>
> >>> — Slipp
> >>
> >> How about some simple instructions for those of us who don’t know html
> and are not web developers on how to get this to work? Do you do something
> like this?
> >>
> >> http://stackoverflow.com/questions/7173096/how-to-
> apply-default-css-styling-to-all-html-pages
> >>
> >> --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/
> laurent%40nemesys-soft.com
> >
> > This email sent to laur...@nemesys-soft.com
>
> ___
>
> 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/websites%40paperetto.com
>
> This email sent to websi...@paperetto.com
>



-- 
David Brittain
da...@paperetto.com
___

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

[Laurent Daudelin]

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/ 
Logiciels Nemesys Software

> On Nov 17, 2016, at 10:13, 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 available for Chrome ( 
> https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe?hl=en
>  ) and Firefox ( https://addons.mozilla.org/en-us/firefox/addon/stylish/ ), 
> though it looks like someone else made a Safari version ( 
> http://sobolev.us/stylish/ ).
> 2. Download the 2 files from that gist.
> 3. Open up the Stylish plugin/add-on/extension's UI and click the import 
> button, choose one file, then click import and choose the other file.
> 4. Enjoy better layout/styling whenever you visit a URL matching 
> `http[s]://developer.apple.com/reference/*`.  ;-)
> 5 (optional). Stylish for Chrome allows you to toggle styles on & off for the 
> current page by clicking the toolbar icon for the extension (to the right of 
> the address bar; the Stylish extension's icon is an “S” in a 4-colored 
> square), so you can decide on-the-fly if you really want to use these changes 
> or not.  I'd imagine Stylish for other browsers works similarly.
> 6 (optional). Modify the CSS to your liking.  The most obvious point of 
> customization would be the `font-size: 10pt !important;` line— you can change 
> the `10pt` to `12pt` or `24pt` or `6pt` or whatever other numerical font size 
> you please.
> 
> 
> 
> Also, I'm not sure if those images went through, so here they are again, 
> hosted externally:
> 
> Turns this: https://cl.ly/0m1c462d1z40
> Into this: https://cl.ly/2b03340B3F2y
> 
> — Slipp
> 
> 
>> On Nov 17, 2016, at 8:55 AM, Richard Charles  wrote:
>> 
>> 
>>> 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: 
>>> https://gist.github.com/capnslipp/208d50e8a6c630d053b4f22e704f28a5
>>> 
>>> — Slipp
>> 
>> How about some simple instructions for those of us who don’t know html and 
>> are not web developers on how to get this to work? Do you do something like 
>> this?
>> 
>> http://stackoverflow.com/questions/7173096/how-to-apply-default-css-styling-to-all-html-pages
>> 
>> --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/laurent%40nemesys-soft.com
> 
> This email sent to laur...@nemesys-soft.com

___

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

[Carl Hoefs]

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...

Why not simply have all the relevant information on the page, where it belongs?

-Carl


> On Nov 17, 2016, at 8:38 AM, Alex Zavatone  wrote:
> 
> 
> 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 available for Chrome ( 
>> https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe?hl=en
>>  ) and Firefox ( https://addons.mozilla.org/en-us/firefox/addon/stylish/ ), 
>> though it looks like someone else made a Safari version ( 
>> http://sobolev.us/stylish/ ).
>> 2. Download the 2 files from that gist.
>> 3. Open up the Stylish plugin/add-on/extension's UI and click the import 
>> button, choose one file, then click import and choose the other file.
>> 4. Enjoy better layout/styling whenever you visit a URL matching 
>> `http[s]://developer.apple.com/reference/*`.  ;-)
>> 5 (optional). Stylish for Chrome allows you to toggle styles on & off for 
>> the current page by clicking the toolbar icon for the extension (to the 
>> right of the address bar; the Stylish extension's icon is an “S” in a 
>> 4-colored square), so you can decide on-the-fly if you really want to use 
>> these changes or not.  I'd imagine Stylish for other browsers works 
>> similarly.
>> 6 (optional). Modify the CSS to your liking.  The most obvious point of 
>> customization would be the `font-size: 10pt !important;` line— you can 
>> change the `10pt` to `12pt` or `24pt` or `6pt` or whatever other numerical 
>> font size you please.
>> 
> 
> Oh, man.  What a godsend.  No more UI that looks like it was a graphic design 
> major's "testing limits" project.
> 
> 
> 
> ___
> 
> 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/newslists%40autonomy.caltech.edu
> 
> This email sent to newsli...@autonomy.caltech.edu

___

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

[Alex Zavatone]

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 rid of all that useless and excessive white space on 
the pages, you might not need a whole monitor to use for docs display.

Honestly, on the Objective-C page, there's 1/2 an inch of empty space between 
the the summary text, the horizontal gray line and then another 1/2 inch 
between the horizontal gray line and the word, "Overview".

That's a wasted inch.  And on the page I just opened, 

https://developer.apple.com/reference/objectivec?language=objc

…there is PRECISELY 3 inches of empty white space to the left of all the text 
and on the right of all text.

Whichever art school student Apple hired to set the UI standards for "UX 
Experience" is simply an idiot.

Sadly, I am so old that I remember when Apple was known for its GOOD UI design 
and user experience, not this minimalist "let's use up all the user's browser 
real estate with glaring white space.  

This is not a fine art museum where every painting needs to be framed by 5 feet 
of white space.  These are dev docs that have to present the content in an easy 
to read manner and be RESPECTFUL of the screen real estate.  It's also NICE not 
to use full white as the background for presentation, because it's glaring and 
there are still people spending all day sitting under flouresent lights in 
offices staring at their screens.  This UI is PAINFUL and causes eye fatigue.  


On Nov 17, 2016, at 10:38 AM, Alex Zavatone wrote:

> 
> 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 available for Chrome ( 
>> https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe?hl=en
>>  ) and Firefox ( https://addons.mozilla.org/en-us/firefox/addon/stylish/ ), 
>> though it looks like someone else made a Safari version ( 
>> http://sobolev.us/stylish/ ).
>> 2. Download the 2 files from that gist.
>> 3. Open up the Stylish plugin/add-on/extension's UI and click the import 
>> button, choose one file, then click import and choose the other file.
>> 4. Enjoy better layout/styling whenever you visit a URL matching 
>> `http[s]://developer.apple.com/reference/*`.  ;-)
>> 5 (optional). Stylish for Chrome allows you to toggle styles on & off for 
>> the current page by clicking the toolbar icon for the extension (to the 
>> right of the address bar; the Stylish extension's icon is an “S” in a 
>> 4-colored square), so you can decide on-the-fly if you really want to use 
>> these changes or not.  I'd imagine Stylish for other browsers works 
>> similarly.
>> 6 (optional). Modify the CSS to your liking.  The most obvious point of 
>> customization would be the `font-size: 10pt !important;` line— you can 
>> change the `10pt` to `12pt` or `24pt` or `6pt` or whatever other numerical 
>> font size you please.
>> 
> 
> Oh, man.  What a godsend.  No more UI that looks like it was a graphic design 
> major's "testing limits" project.
> 
> 
> 
> ___
> 
> 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/zav%40mac.com
> 
> This email sent to z...@mac.com

___

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

[Alex Zavatone]

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 available for Chrome ( 
> https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe?hl=en
>  ) and Firefox ( https://addons.mozilla.org/en-us/firefox/addon/stylish/ ), 
> though it looks like someone else made a Safari version ( 
> http://sobolev.us/stylish/ ).
> 2. Download the 2 files from that gist.
> 3. Open up the Stylish plugin/add-on/extension's UI and click the import 
> button, choose one file, then click import and choose the other file.
> 4. Enjoy better layout/styling whenever you visit a URL matching 
> `http[s]://developer.apple.com/reference/*`.  ;-)
> 5 (optional). Stylish for Chrome allows you to toggle styles on & off for the 
> current page by clicking the toolbar icon for the extension (to the right of 
> the address bar; the Stylish extension's icon is an “S” in a 4-colored 
> square), so you can decide on-the-fly if you really want to use these changes 
> or not.  I'd imagine Stylish for other browsers works similarly.
> 6 (optional). Modify the CSS to your liking.  The most obvious point of 
> customization would be the `font-size: 10pt !important;` line— you can change 
> the `10pt` to `12pt` or `24pt` or `6pt` or whatever other numerical font size 
> you please.
> 

Oh, man.  What a godsend.  No more UI that looks like it was a graphic design 
major's "testing limits" project.



___

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

[Slipp Douglas Thompson]

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 ( 
https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe?hl=en
 ) and Firefox ( https://addons.mozilla.org/en-us/firefox/addon/stylish/ ), 
though it looks like someone else made a Safari version ( 
http://sobolev.us/stylish/ ).
2. Download the 2 files from that gist.
3. Open up the Stylish plugin/add-on/extension's UI and click the import 
button, choose one file, then click import and choose the other file.
4. Enjoy better layout/styling whenever you visit a URL matching 
`http[s]://developer.apple.com/reference/*`.  ;-)
5 (optional). Stylish for Chrome allows you to toggle styles on & off for the 
current page by clicking the toolbar icon for the extension (to the right of 
the address bar; the Stylish extension's icon is an “S” in a 4-colored square), 
so you can decide on-the-fly if you really want to use these changes or not.  
I'd imagine Stylish for other browsers works similarly.
6 (optional). Modify the CSS to your liking.  The most obvious point of 
customization would be the `font-size: 10pt !important;` line— you can change 
the `10pt` to `12pt` or `24pt` or `6pt` or whatever other numerical font size 
you please.



Also, I'm not sure if those images went through, so here they are again, hosted 
externally:

Turns this: https://cl.ly/0m1c462d1z40
Into this: https://cl.ly/2b03340B3F2y

— Slipp


> On Nov 17, 2016, at 8:55 AM, Richard Charles  wrote:
> 
> 
>> 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: 
>> https://gist.github.com/capnslipp/208d50e8a6c630d053b4f22e704f28a5
>> 
>> — Slipp
> 
> How about some simple instructions for those of us who don’t know html and 
> are not web developers on how to get this to work? Do you do something like 
> this?
> 
> http://stackoverflow.com/questions/7173096/how-to-apply-default-css-styling-to-all-html-pages
> 
> --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: Documentation Workflow

[Richard Charles]

> 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: 
> https://gist.github.com/capnslipp/208d50e8a6c630d053b4f22e704f28a5
> 
> — Slipp

How about some simple instructions for those of us who don’t know html and are 
not web developers on how to get this to work? Do you do something like this?

http://stackoverflow.com/questions/7173096/how-to-apply-default-css-styling-to-all-html-pages

--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: Documentation Workflow

[Richard Charles]

> 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.

Problem ID: 29248282

--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: Documentation Workflow

[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

[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

[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

[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