Apple broke a lot of its developer reference urls... again.
renesd.blogspot.com
Apple broke a lot of its developer reference urls... again.
1–10 of 24 posts
Re: Apple broke a lot of its developer reference urls... again.
#2Yeah, I've seen this several times. I don't know how they put the site together, but it doesn't sound like it would be a hard problem to solve.
As weird as it is on the web, it's even weirder in their developer tools. I kid you not, there are HTML files in "/Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.CoreReference.docset/Contents/Resources/Documents/documentation/Cocoa/Reference/ApplicationKit/Classes/NSApplication_Class". Whereas, if they'd hired me to do it, I would have probably called it "/Developer/Documentation/Cocoa".
Re: Apple broke a lot of its developer reference urls... again.
#3Yeah, I've seen this several times. I don't know how they put the site together, but it doesn't sound like it would be a hard problem to solve. As weird as it is on the web, it's even weirder in their developer tools. I kid you not, there are HTML files in "/Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.CoreReference.docset/Contents/Resources/Documents/documentation/Cocoa/Reference/ApplicationKit/Cl…
Indeed. They need someone to go through and give nice urls to all of their documents. Also be good for someone at 1 infinite loop to get a list of all the old urls, and map them to the new urls.
Probably not a hard task for their web team.
Re: Apple broke a lot of its developer reference urls... again.
#4In my more paranoid moments I think Apple is actively trying to make it difficult to develop for their products. I know how crazy it sounds but it's not entirely irrational.
I mean, how can a company that puts so much effort into perfectionism do something like this by mistake?
Re: Apple broke a lot of its developer reference urls... again.
#5Yeah, I've seen this several times. I don't know how they put the site together, but it doesn't sound like it would be a hard problem to solve. As weird as it is on the web, it's even weirder in their developer tools. I kid you not, there are HTML files in "/Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.CoreReference.docset/Contents/Resources/Documents/documentation/Cocoa/Reference/ApplicationKit/Cl…
While absurdly long, that path actually does (mostly) make sense. If you were to do it, it would be an organizational mess when looking for something.
/Developer is the standard install path. Documentation/ for docs, DocSets for the actual docs (as opposed to sample code), com.apple.ADC_Reference_library to say its an ADC reference library (as opposed to installing your own docsets, which some libraries have), CoreReference.docset to say which docset it is exactly (leopard vs snow leopard, for example), Contents/ is pretty standard for OS X bundles, Resources/ since docs are technically resources, Documents/ (again, there are other files here: sample code, tech notes, etc), documentation/ for the documents themselves, Cocoa/ for which framework you're looking at (It could also be Carbon, Webkit's CSS, Darwin, Java, etc), and, well, thats the end of the chain on my system. But to continue it based on a guess, Reference/, possibly redundant, but its nice for organizational purposes, ApplicationKit/ - you are looking up something in AppKit, but there are other *Kit's that can be used as well, Classes/ instead of headers, maybe, and then NSApplication_Class for the class that you want.
Re: Apple broke a lot of its developer reference urls... again.
#6It’s not like this is even exclusive to the documentation—every new release of OS X takes over /macosx (or whatever it is).
It seems like somebody involved feels that there’s no use for the past.
Re: Apple broke a lot of its developer reference urls... again.
#7Yeah, I've seen this several times. I don't know how they put the site together, but it doesn't sound like it would be a hard problem to solve. As weird as it is on the web, it's even weirder in their developer tools. I kid you not, there are HTML files in "/Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.CoreReference.docset/Contents/Resources/Documents/documentation/Cocoa/Reference/ApplicationKit/Cl…
While absurdly long, that path actually does (mostly) make sense. If you were to do it, it would be an organizational mess when looking for something. /Developer is the standard install path. Documentation/ for docs, DocSets for the actual docs (as opposed to sample code), com.apple.ADC_Reference_library to say its an ADC reference library (as opposed to installing your own docsets, which some libraries have), CoreRe…
The structure is consistent with other bundles. But the question is, are bundles really the logical way to handle documentation? I don't think so.
If you look in places like "/Library/Application Support", everything is basically broken down by product or vendor. It is hard to imagine having so much documentation installed that similar naming wouldn't suffice for DocSets.
Apple has also used saner documentation layouts elsewhere (and oddly, in places that are probably not meant to be "public" documentation). For instance, there's a /Library/Documentation, and its layout is very easy to follow.
Re: Apple broke a lot of its developer reference urls... again.
#8In my more paranoid moments I think Apple is actively trying to make it difficult to develop for their products. I know how crazy it sounds but it's not entirely irrational. I mean, how can a company that puts so much effort into perfectionism do something like this by mistake?
messy kitchen, exemplary dish
Re: Apple broke a lot of its developer reference urls... again.
#9I notice Microsoft regularly breaks its own developer URLs as well... even the links from within Visual Studio's help system to their online content. It's sad that the most reliable way to find documentation is through Google.
Re: Apple broke a lot of its developer reference urls... again.
#10You can Search for anything in the Developer Documentation (installed with XCode).