Beta

Slashdot: News for Nerds

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Apple Launches Reference Library

pudge posted more than 10 years ago | from the woo-hoo dept.

OS X 46

andy55 writes "If you thought Apple's online dev resources were already the best out there, they just got better. Apple has announced the launch of their new ADC Reference Library. Named features are: powerful search options, added navigation, 'Getting Started; docs on key technologies, and a more consistent organization. Impressively, the first search I ran in their search engine on a painful Mach-O dev issue I've been fighting for the last week turned up the key obscure tech info I needed!" Meanwhile, skrysakj writes "Apple has launched a new Reference Library. I always thought their help/references for Developers was spotty (either non-existent or dead on) so this should be a welcome change."

cancel ×

46 comments

STRIKE A POSE, BITCHES (-1, Offtopic)

Anonymous Coward | more than 10 years ago | (#8620984)

Yeah! Who's yo mamma!

Oh yeah, FP! - take that thymecop!!!!!!!111

Gay information? (-1, Troll)

Anonymous Coward | more than 10 years ago | (#8621070)

Does the library contain information on how to be a good gay Mac user?

Re:Gay information? (-1, Troll)

Anonymous Coward | more than 10 years ago | (#8621185)

Just ask your dad.

Great stuff (5, Informative)

tiktokfx (699424) | more than 10 years ago | (#8621142)

However, in reference to the "spotty references" on developing... there's plenty of reference material for those who look... nice heavy folder full of documentation in the developer tools installation.

Riiiiight! (-1, Troll)

Anonymous Coward | more than 10 years ago | (#8621182)

Apple's dev resources are the best? Nothing, and I mean *nothing* beats MSDN [microsoft.com] . Not gay Apple's docs [ngltf.org] and definitely not socialist GNU/Linux's docs [cpusa.org] . Microsoft takes care of its developers.

Paranoid (5, Interesting)

Anonymous Coward | more than 10 years ago | (#8621196)

Even though I have no prior reason for distrusting Apple, I get the feeling that eventually this information will be accessible to developers paying a premium rather than those of us who signed up for the free account.

Anyone know if the ADC is going to replace the current /Developer/Documentation that comes with OSX? 6 years ago I used to sit and while away the hours reading man pages and HOWTOs in Linux, and since I bought a PowerBook I find I'm doing the same kind of thing with their docs which I have locally installed. The ADC (that's Apple Developer Connection, not the monitor connector ;) looks awesome, but a local, offline copy would be even better.

I guess I could always buy a printer...

Re:Paranoid (3, Interesting)

Anonymous Coward | more than 10 years ago | (#8621244)

after looking at the way the directory is set up, maybe you could try wget

Re:Paranoid (5, Informative)

the_proton (257557) | more than 10 years ago | (#8621368)

The local offline copy should be part of the next Xcode release. The documentation that comes with Xcode is just a snapshot of what was on the various areas of the ADC site as the software was released.

- proton

Re:Paranoid (5, Insightful)

jwthompson2 (749521) | more than 10 years ago | (#8621369)

I think your paranoia is somewhat interesting but the current model that Apple has with distributing XCode and other development resources freely with their operating system is the most valuable model. Heck, MS is talking about have command line development tools available in the default install of Longhorn. The concept of 'every user a developer' is something Apple is and will continue to benefit from if they maintain their current stance.

Re:Paranoid (1, Funny)

Anonymous Coward | more than 10 years ago | (#8621390)

Heck, MS is talking about have command line development tools available in the default install of Longhorn.

debug has been a part of the default Windows install for years ;)

Re:Paranoid (1)

Tumbleweed (3706) | more than 10 years ago | (#8621489)

fdisk, too. :)

Re:Paranoid (0, Flamebait)

rixstep (611236) | more than 10 years ago | (#8623707)

every user a developer

Oh please. Who exactly will benefit, and how?

It is sad that programming is becoming yet another wannabe art and is rather ceasing to be an art altogether.
- MN Karthik


The day this began was the first day of the end of the world.

Re:Paranoid (5, Insightful)

Etcetera (14711) | more than 10 years ago | (#8623976)

every user a developer

Oh please. Who exactly will benefit, and how?


Go read up on the history of HyperCard, yo. Plenty of people benefited from the use of it, and many are still benefiting today.

Re:Paranoid (5, Insightful)

Jeff Kelly (309129) | more than 10 years ago | (#8628205)

"Oh please. Who exactly will benefit, and how?"

Every user which develops applications is a good thing. Talent is only 20% of art. The other 80% come from experience and practice. Nobody is a born coder. Some of the greatest developers in the industry started their career with such development tools. And it took them years of coding to get them where they are today.

Every new application is an argument for using that particular platform even if it is only a mediocre program.

A Linus Torvalds had 12 years working on the linux kernel-code to take him from an apprentice student programmer to the wizkid he is today.

Without gcc and similar free development tools we would never have had something like the current BSDs, Linux, Apache, Gnome, KDE you name it.

Even Microsoft releases the basic development tools for free. (Platform SDK)

This benefits everybody. Without free development tools we would have to pay premium for even the simplest programs and would be very limited in choice because only those who could afford the $1500 Visual Studio or the $3000 IBM Tools could develop applications.

"It is sad that programming is becoming yet another wannabe art and is rather ceasing to be an art altogether."

Elitist bullshit. Even Dali or Picasso had to do mundane tasks to earn their living and it took them decades to perfect their art.

Art lies in the eye of the beholder. The more people are practicing it the more will come out of it. The beginners can learn from the professionals (reading code for example) and the professionals have enough competition so that they are not likely to grow content with what they have accomplished already.

This is what is driving on every art form. Those who would like to limit it are the ones who fear to lose their renown, fame or status.

p.s. i apologise in advance for the spelling and grammar mistakes i am not a native speaker.

Re:Paranoid (-1, Offtopic)

Anonymous Coward | more than 10 years ago | (#8631907)

Let's face it: some mods are just out-and-out assholes.

Re:Paranoid (5, Insightful)

jamesbrown1000 (39200) | more than 10 years ago | (#8627925)

I agree wholeheartedly.

I started a new job in January and my supervisor is a big AppleScript guy. From that, I've started learning AppleScript Studio in Xcode. There isn't much I can't do with AppleScript and shell scripts, and that's led me to write my own little apps in the past month or so.

Every user has the power to make his own software. How cool is that?

Re:Paranoid (3, Insightful)

Unregistered (584479) | more than 10 years ago | (#8621404)

I doubt it. The main thing that hurts Apple is the lact of apps available. I doubt they would do anything that would scare off potential developers.

Re:Paranoid (5, Insightful)

Graff (532189) | more than 10 years ago | (#8625721)

Even though I have no prior reason for distrusting Apple, I get the feeling that eventually this information will be accessible to developers paying a premium rather than those of us who signed up for the free account.

Actually, if anything Apple has gotten more free with its documentation. It used to be that Apple sold huge tomes called "Inside Macintosh" which described the inner workings and APIs of the Mac. There were at least 2 dozen of these books which covered every inch of programming on a Mac, gathered by topic. Each of these books would run $35 or so. You didn't need every one of them but it really helped to have about a half dozen of the key ones, so figure about $35 * 6 = around $200.

As Apple entered its current Mac OS X stage it began to take on more and more of a open-source flavor. Documentation was being distributed along with free programming tools, prices were dropping to become a registered developer, a free type of registered developer appeared, code was being released back to the community with minimal licenses, etc.

Right now it is the best time to be an Apple developer. It literally costs you nothing to become an official registered developer. If you do pay for one of the higher levels of being a registered developer you get significant price breaks and free stuff which pays many timed over for the price of registering. Students can pay a pittance of $100 and they get way over $500 in benefits. Apple staff is very responsive on their mailing lists and there are a ton of new developers out there who share your enthusiasm and who are willing to help.

As a worst case, even if Apple does change its policy (not likely because they WANT people to program for the Mac) and starts charging for programming documentation it is unlikely that the free programming information out there will disappear. That's because EVERY version of Mac OS sold in the last few years includes this free documentation. There's no way that Apple will change its APIs fast enough to make that documentation obsolete for at least a decade. Yeah a command here or there might get depreciated but Apple takes their time in truly tossing anything out. You will be fairly safe using old, free documentation that you can get freely off a Mac OS X cd from a few years past.

Re:Paranoid (3, Insightful)

bar-agent (698856) | more than 10 years ago | (#8626443)

The Inside Macintosh volumes were incredibly useful. The thoroughly covered all aspects of a topic, and had a really good cross-reference.

But then they stopped putting out Inside Macintosh. Everything started being documented in technotes and hard-to-find articles.

But it looks like Apple's definitely got their act together as far as content goes. Now all they need is a better look-up system in their mailing list archives.

Re:Paranoid (2, Insightful)

pudge (3605) | more than 10 years ago | (#8634849)

Apple has put all its developer docs online, for free, since 1996 or earlier (when I started downloading all the Inside Mac volumes in PDF). I see no reason to suspect they will start charging money any time soon.

Re:Paranoid (1)

jcr (53032) | more than 10 years ago | (#8639177)

I don't know why you'd get that feeling. It is in Apple's interest to make the docs available as widely as possible. As for developer docs on your local drive, they're included with every release of the developer tools.

-jcr

MSDN (0, Troll)

skinfitz (564041) | more than 10 years ago | (#8621562)

It looks just like msdn.microsoft.com [microsoft.com] but for OSX.

Great!

Re:MSDN (0)

Anonymous Coward | more than 10 years ago | (#8622184)

Yeah... and not a pain in the ass to browse, either. :-)

Re:MSDN (4, Funny)

rixstep (611236) | more than 10 years ago | (#8623693)

It's great because it looks like the Microsoft Developer Network?

Someone toss me a flight bag quick.

Re:MSDN (0)

Anonymous Coward | more than 10 years ago | (#8635539)

http://developer.apple.com/referencelibrary/index. html
looks nothing like
http://msdn.microsoft.com/library/default.as p

Definitely a step in the right direction... (5, Informative)

Chief Typist (110285) | more than 10 years ago | (#8621679)

The newly release Reference Library is very well organized and makes finding things much easier. Good job, Apple! It's been a long time coming!

There's still a problem, though. Much of the "state of the art" documentation is actually happening on the Mac OS X and Cocoa mailing lists. It's good to have reference materials, but if you're looking for information on the latest & greatest addition to the OS, go search the archives [mamasam.com] .

You'll find that you can get answers directly from the developers before the reference materials are formalized and made public. As an example, in the months following last year's WWDC, there was a ton of information on the lists about the new Cocoa Bindings. As a developer who wants to stay on the leading edge of Mac OS X product development, this is invaluable.

Also, the guy that is running the mailing list archive, is looking for donations. If you are a developer who uses these archives, PLEASE DONATE.

-ch

Re:Definitely a step in the right direction... (1)

rixstep (611236) | more than 10 years ago | (#8623730)

mamasam.com

Mamasan is good, but it's not formalised. And a lot of time is wasted by newbies who are too lazy to RTFM.

Vervante has a nice selection of books. They're pricey (~$300 for the lot) but they're good.

Re:Definitely a step in the right direction... (1)

logicat2001 (706979) | more than 10 years ago | (#8631635)

FYI: Vervante [vervante.com] apparently no longer offers the bound Cocoa API set. A search for 'cocoa' on their site yields nothing, and a browse through their Apple section [vervante.com] shows an MacOS X Server manual and some Final Cut Pro documentation.

Re:Definitely a step in the right direction... (5, Informative)

bar-agent (698856) | more than 10 years ago | (#8626434)

Another good source of information is the cocoadev.com wiki. Documentation gaps are filled pretty quickly -- I should know, I'm a regular contributor.

good for beginners (4, Interesting)

bodrell (665409) | more than 10 years ago | (#8621686)

Apple has done everything in their power to make developing software for OS X as easy as possible. There's the tutorial for the "Currency Exchanger" program, to get started with Project Builder, and there is always to option to throw together a shell script if the whole build process is too scary.

I don't know shit about programming, but I'm learning. And having a bash shell, with actually useful commands, is really helpful to that goal. So many people don't understand the appeal of a command line, or think that you have to pick a nice GUI or a nice CLI, but that's bullshit. Someone actually asked why I would care about the GUI if I spend so much time with the command line. It seems obvious to me--I can carry on everyday operations with apps familiar to me, but can craft more and more complex helper apps/scripts in my free time. Much simpler than rebooting into Linux when I feel like experimenting, then getting frustrated that I can't burn a CD because the procedure is too complex and having to reboot into a more idiot-proof OS. I welcome any enhancement that makes development easier for the ignorant (like me), and avoids rebooting.

Oh, and I don't want to hear anyone try to compare Windows' cmd.exe with a bash shell. I do use the Windows command line, but it's a total cripple compared to any UNIX shell. Sure there's Cygwin and Mingwin (or something like that), but they aren't very integrated.

Re:good for beginners (5, Informative)

Anonymous Coward | more than 10 years ago | (#8622091)

Oh, and I don't want to hear anyone try to compare Windows' cmd.exe with a bash shell.

Too bad :P I like cmd.exe and use it every day. Some features it has that give it some respectability:

  • Redirection operators < > |
  • Logical operators && ||
  • Macros somewhat similar to bash's. Try doskey macro_name=command_line
  • Ability to redirect stderr to stdout Try 2>1 or 1<&2
  • User-defined file descriptors (or in Windows-speak, handles). >&3 >&4 and so on up to 9
  • improved looping. for /l %a in (start,step,end) do for_body for iterative loops.
  • better text file parsing. Try for /f. You can read in a text file, break it up into tokens and pass the tokens to a command. You can also do that with command output or strings.
  • Tab completion
  • /dev/null workalike. Redirect to NUL instead.
  • directory stacks. pushd and popd
  • Ability to read in input and store it into a variable. set /p variable=promptString
  • Advanced arithmetic. set /a can do modulus, bitshifts, bit flipping, compound assignment, xor, bitwise or, bitwise and
  • improved decision selection. if string operator string body The operator can be equ for equal, gtr for greater than, and so on.
  • grep replacement, findstr. Has the ability to use regular expressions.
Anyway, cmd.exe is not as crippled as command.com. It is much more capable and useful. It can even somewhat hold its own against Unix shells.

Re:good for beginners (4, Funny)

quecojones (108609) | more than 10 years ago | (#8622408)

So, basically, you're saying cmd.exe has all the stuff bash and, I assume, most of the other UNIX shells have had for ages?

About time. 8)

Re:good for beginners (1, Insightful)

Anonymous Coward | more than 10 years ago | (#8632646)

without screen it's pretty useless.

Add the fact that there isn't a decent editor like vim or emacs. I just double-checked Windows 2003 Server command line, and the about box says "MS-Dos Editor Version 2.0.026 (C) 1995". They haven't updated the QBasic pad, in an operating system that's supposedly cutting-edge.
It can even somewhat hold its own against Unix shells.

No, I'm sorry. It cannot.

cmd.exe or bash? Hrm. 3+3 = 2+4 (2, Interesting)

mactari (220786) | more than 10 years ago | (#8646761)

Boy, if this isn't a case of, "I know what I know," I'm not sure what is. But then I just said that. ;^)

Folks, it's all zeroes and ones. All we're really talking about here is running & interacting with programs from standard input and reading from standard output. I imagine you could gentoo together a nice, bare version of Linux that had as few (or many, as your half-filled glass may appear to you today) applications available as there are by default in Win2k.

Personally I quite enjoy cmd.exe and use it as much as I do the Terminal (or iTerm or X11 with xterm (with an "&" no less)) in OS X. You can get vim [vim.org] running from cmd.exe very easily with syntax highlighting and full integration with the Windows clipboard.

To sum quickly, I can... change active directories, view directory contents, copy, delete, & move files, edit text, create scripts, call any app I want, interact with anything that has a standard in/out interface, print, schedule repeated/timed tasks, reboot other machines on your network, find & replace strings in files, and install any app I dang well please from either cmd.exe or bash or tcsh or whatever you prefer.

And hey, in any event, it's a far cry better than the command line in Mac OS 9-. (Which, for those who didn't know, you could get in the Mac Programmers' Workshop (MPW), but sure wasn't installed by default.)

Re:good for beginners (-1, Offtopic)

Anonymous Coward | more than 10 years ago | (#8623754)

  • I don't know shit about programming, but I'm learning

Uhoh...

Who's the ass who submitted this story? (-1, Troll)

Anonymous Coward | more than 10 years ago | (#8623218)

Apple have already sent out newsletters about this twice now; who else is going to be interested that has not already been informed?

You guys are incredible jackasses.

Things I miss. (4, Interesting)

BibelBiber (557179) | more than 10 years ago | (#8623234)

Some of the things I miss from ADC is that documentation updates that seem to be on a regular basis are not downloadable. I don't have access to the net all the time I develop so it would be nice to have it completely offline. As well a search function would be nice. I have it aliased in my apache so a simple php search would be convenient.

AppKiDo (4, Informative)

rixstep (611236) | more than 10 years ago | (#8623741)

Don't want to tout someone's product, but seriously: if you're a pro here, you can't make it fast or far without Andy Lee's AppKiDo. It's easy to Google to, and it's free.

What Andy does is parse the actual documentation you already have on disk, but he does a much better job of it than Apple. Searches are better, faster, more flexible, and so are the renderings.

It's one of the truly indispensable programs out there.

Re:AppKiDo (2, Informative)

Juanvaldes (544895) | more than 10 years ago | (#8626241)

I can not AOL this enough. AppKiDo is a Cocoa developoers best friend.

Re:AppKiDo (2, Informative)

XxtraLarGe (551297) | more than 10 years ago | (#8629647)

Absolutely. AppKiDo is in my dock right next to Project Builder. A must have for any serious OS X developer.

Re:AppKiDo (3, Informative)

MasonMcD (104041) | more than 10 years ago | (#8636472)

The search function on the ADC reference library is now powered by Google, so you should get much better hits now, and moreso as more people use it.

It didn't USED to be spotty... (3, Insightful)

dpbsmith (263124) | more than 10 years ago | (#8636689)

...this is a another sad case of Apple regressing to the mean.

From 1984 through, say, 1998, Apple documentation was some of the best documentation I've ever used. (And I've used the VAX/VMS documentation that came in thirty-or-so China-red binders). Apple documentation accurate, well-written, well-organized, thorough, complete, and written in a down-to-earth developer-to-developer tone of voice.

Meanwhile, my colleagues developing for Windows were struggling with DDK components that were "documented" only with sample code, getting hints and tips from magazine articles, or reading "official" MS material that mixed an enormous amount of propaganda with the technical information.

Unfortunately, one of the things that appears to have come in with the NeXT subculture is a more casual attitude toward documentation. Perhaps they were too much in a hurry to release OS X (did I actually say perhaps?) Perhaps it's a not-so-benign influence of open-source development. I still find all too often that the header files are as good or better documentation than the documents.

OS X documentation is much, much better than it was, say, a year-and-a-half ago, so hopefully this is being addressed. But it really is a pity to journey from superb documentation to inadequate documentation, then climb slowly up to sorta-OK documentation.

The release of the hardbound Inside Mac volumes 1-3 had a tremendous impact within a certain now-defunct Fortune 500 minicomputer company. One director was running around slamming it down on peoples' desks and saying "Look at this! What does it say about Apple? They expect their software to be around forever!"

Re:It didn't USED to be spotty... (2, Informative)

Anonymous Coward | more than 10 years ago | (#8639278)

Unfortunately, one of the things that appears to have come in with the NeXT subculture is a more casual attitude toward documentation.

Not hardly. NeXT was noted for excellent documentation, particularly the NeXTSTEP concepts doc.

The long and short of it is, Apple simply has a lot more to document than they ever did before, and they're doing the best they can to get it out the door ASAP.

If you have specific (keyword SPECIFIC) issues with any of apple's docs, file a report at bugreporter.apple.com. Just parroting the old "apple's docs suck" isn't a bug report, it's just an unfounded gripe.

Re:It didn't USED to be spotty... (3, Funny)

Cmdr TECO (579177) | more than 10 years ago | (#8644698)

"... a certain now-defunct Fortune 500 minicomputer company."

A now-defunct minicomputer company? Yup, that sure narrows it down.

Is Anything Really *New*? (1)

Beeman (31488) | more than 10 years ago | (#8648094)

To the best that I can tell, none of the documentation is actually new, they just put a nice index page up which makes it possible to find things that you are looking for. All of the documentation was available previously, if you could find it.

One thing that's missing (1, Interesting)

Anonymous Coward | more than 10 years ago | (#8650482)

Apple documentation does not specify what goes with which version of what operating system, nor does it mention what other dependencies use might entail. Microsoft documentation always states clearly which function calls require what - and what OS. Developers can adjust their code accordingly and at least leave the user with 'graceful failure', ie 'Sorry, this application requires Microsoft Windows blah-blah and Internet Explorer 14.0.'

The Apple stuff does none of the kind. Oh it's there all right - it's just not exported/documented properly. There are so many quirks in this development environment that what usually happens is that users see a bouncing icon and then it disappears. They have no inkling of what went wrong - and the developers don't either. All anyone knows is 'this doesn't seem to work with OS X version blah blah', and that's not good enough.

It's a mess, because adding instance variables to a class in either the Foundation Kit or the AppKit is going to screw up the offsets to the class methods, and if the client (application) is prebound then you can get lots of nice stuff like crashes and that.

So what do you have, for all the ease of use of Cocoa? You get forced to provide different builds for different versions of OS X, are never sure exactly why the one works and not the other, nothing is properly documented - you're walking on ice all the time.

And identical code built with identical compilers on different boxes with different resident versions of the operating system produce different application behavior despite their executables being identical - figure that one out. But it's happening all the time.

Apple need to explain what is going on. They can and must do better.

Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Create a Slashdot Account

Loading...