Talk:Cocoa (API)

message: I un-did some of Tenbaset's edits. Here's why.
*Tenbaset said, "It contains functionality with which programs can create and interact with graphical user interfaces." I changed this back to "code," because "code" is literally correct while "functionality" is not. Libraries contain code, in the form of compiled functions, with which programs can do things. "Functionality," being an abstract sort of idea, isn't something that something can "contain." Plus, "functionality" is a weasel word. If we want to change this to "functions," I'm amenable, but there's an argument to be made that these libraries contain more than just functions. So I used the generic term "code."
*Tenbaset said, "... classes for common tasks such as string and value manipulation, containers and iteration, distributed computing, event handling, networking, and other functions that are not directly tied to the graphical user interface." I changed it back to "things like." String and value manipulation is a task. The other things aren't. Containers are things. Iteration is a process performed with a container. And so on.
*I changed "stems from Coca's NeXTSTEP/OpenStep heritage" back to "reveals Cocoa's..." because the "NS" prefix isn't a new thing. It's a leftover thing that was present in NeXTSTEP. So I don't think it can properly be said to "stem from" anything. Also, fixed the spelling of Cocoa, and eliminated a sentence fragment.
I also changed a couple of other little things to better reflect the document's structure, and I got rid of the phrase "among Windows users" because there were just too many commas in that sentence, and that phrase didn't really add anything useful anyway. (Even though I wrote it. I know, I'm heartless.)
Jharrell 00:15 12 Jul 2003 (UTC)
: Perhaps not "contain" but the libraries "have" functionality.  ("Functions" wouldn't be wise, because these libraries almost certainly have "Methods", and in some languages there is a clear difference, depending on POV.)  "Code" (as a word) just seemed clunky to me.
: "Things like"   I think that phrase doesn't suit the formal tone of an encyclopaedia, which is why I changed that.  "Reveals" has a connotation that you're accusing Apple of doing a cover-up, which is why I changed that.  
: As for DSO/DLL, what is the word that MacOS developers use? (Or do they indeed use multiple terms?) (What extension do these files have?) Tenbaset 10:55 12 Jul 2003 (UTC)
:: I dig it. I still prefer the less stilted "things like," but that's just me. I think formal makes sense up to a point, beyond which it's just puttin' on airs, you know? After all, "Never use a long word when a diminutive one will do." Which is why "functionality" is on my list. ;-)
:: On DSO/DLL... classic Mac programmers never really embraced the concept. The old ASLM (Apple Shared Library Manager) went ignored by practically everybody. (Open Transport used it, as I recall.) Some folks used CFM (Code Fragment Manager) instead, but not too many. More often, code resources were loaded with the Resource Manager for things like Photoshop plug-ins. Shared code wasn't a big part of Mac programming in the pre-Mac OS X period. Microsoft created a COM implementation for the Mac and used it in Office. A few other products also used it, like later versions of PageMaker. But that was about the extent of it. For the most part, Mac programs were just statically linked.
:: Jharrell 15:24 12 Jul 2003 (UTC)
JavaMac 18:54, 17 September 2006 (UTC)
replies: text: OpenStep may have been the first to use the prefix "NS", but it's pretty clear the prefix itself stems from the NeXTSTEP heritage. – Mipadi 21:22, 17 September 2006 (UTC)
replies: text:  I don't think that's clear. It seems logical that it's NeXT-Sun. 128.158.145.51 20:54, 31 May 2007 (UTC)
replies: text:  It's likely from NeXTSTEP, as most sources credit the naming scheme. – Mipadi 17:41, 1 June 2007 (UTC)
thread_title:  Reverted edits 

message: Why was the name of this article changed, apparently without consultation (if there was consultation, where did it take place? - I have most Apple-related articles on my watchlist and didn't get a chance to see anything about this). API stands for APPLICATION programming Interfaces. Cocoa is NOT an API, it's vitually a whole operating system, you can write anything from command-line tools to drivers to system services to plug-ins to preference panels to screensavers and yes, even applications. The previous title seems fine to me, though if this is related to the other discussion about naming conventions for Mac-related articles, then Cocoa (Macintosh) would be more appropriate.Graham 23:30, 27 Apr 2005 (UTC)
thread_title: Name change?

message: I am going to go through and do a bit of surgery on this article. I hope this will meet with folks' approval - the problem as I see it is that there is far too much detail and advocacy in the article. While I'm a big fan of Cocoa and use it daily in my work, I feel this article is not in the right vein. It needs to convey what Cocoa is, without getting carried away with trying to evangelise it. I'll be making the changes over the next day or two - give me chance OK? Graham 00:04, 19 May 2005 (UTC)
thread_title: Copyediting

message: I've been working on a wikibook which a beginners guide to programming with Cocoa. As I write this it's still just a very early first draft, with many typos and other inconsistencies. Hopefully some others will be interested enough to help out! Here's the link: . Graham 23:22, 29 January 2006 (UTC)
thread_title: Wikibook

message: :Image:Cocoa dev screenshot.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is  other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page.  Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot (talk) 21:14, 13 February 2008 (UTC)
thread_title: Fair use rationale for Image:Cocoa dev screenshot.png

message: Is there any official word on the pronunciation, and should the phonetic version be added to the first line? I've always assumed it was pronounced "ko-ko", like hot chocolate, but I've heard "ko-ko-uh" or "ko-ko-ah" as well. — John 19:23, 27 February 2008 (UTC)
replies: text: it's ko-ko, listen to any keynote or demo  —Preceding unsigned comment added by Petchboo (talk • contribs) 15:57, 5 March 2008 (UTC)
thread_title:  Pronunciation 

message: Add it, pronto!  —Preceding unsigned comment added by 129.120.94.106 (talk) 18:24, 6 March 2008 (UTC)
replies: text: why dont you add it?  —Preceding unsigned comment added by Petchboo (talk • contribs) 14:35, 10 March 2008 (UTC)

text: It's November 2008 and still nothing? There is a little bit of info in the Cocoa Touch article, which has a merge proposal but no discussion. I suggest a section on Cocoa Touch with a link to the main article, or a section on differences – there are many differences, although I am not familiar with them. —[semicolons]— 21:36, 20 November 2008 (UTC)
thread_title: Cocoa Touch

message: "Using only the built-in features, one can write a text editor application in as few as 0 lines of code. With new controller objects, this may fall to zero."
Also, maybe an example of how you would write a text editor in zero lines of code might be .. illustrative.
:You can pretty much drop a text field on a window, and then it does pretty much all the basic things a real editor can do (fonts, colors, sizes, ruler, etc), except maybe saving. But I don't know that we need to put that in the article. --Thekmc (talk) 19:21, 5 March 2011 (UTC)
thread_title:  Typos in Rich objects section 

message: Could someone write a very detailed explanation of the difference between Cocoa and Carbon, and how they compare and contrast? I don't know much in that field. I think it would benefit people reading this article, especially if they are choosing one. Maybe make a "Differences between Cocoa and Carbon" page sometime?  —Preceding unsigned comment added by Geek 2.0 (talk • contribs) 01:23, 29 October 2008 (UTC)
replies: text: Good idea, but Thanks, it is too easily googled.
http://www.osnews.com/story/661/What_is_the_Difference_Between_Carbon_and_Cocoa  — Preceding unsigned comment added by 2001:558:6045:56:A494:E24D:2C11:BD29 (talk) 23:03, 27 July 2018 (UTC)
thread_title: Cocoa Vs. Carbon

message: The following sentence needs an update reflecting AppleScript changes in Snow Leopard: "AppleScript Studio, part of Apple's Xcode Tools makes it possible to write (less complex) Cocoa applications using AppleScript."(91.46.121.29 (talk) 15:12, 12 September 2009 (UTC)
replies: text: --Thekmc (talk) 14:47, 5 March 2011 (UTC)
thread_title: AppleScript Studio and Snow Leopard

message: The first sentence says that "Cocoa is one of Apple Inc.'s native object-oriented application program languages" but it is not a programming language, instead, it is a framework. Khatchad (talk) 05:22, 13 August 2010 (UTC)
thread_title:  Programing language? 

message: This remark seems like an opinion or original research: "For end-users, Cocoa applications are considered to be those written using the Cocoa programming environment. Such applications usually have a distinctive feel, since the Cocoa programming environment automates many aspects of an application to comply with Apple's human interface guidelines."
It's entirely possible for a Carbon app to behave exactly like a Cocoa app, or for a Cocoa app to be poorly written and exhibit inconsistent behavior. Mike Richardson (talk) 20:20, 6 November 2012 (UTC)
thread_title: Cocoa apps aren't necessarily better

message: Maybe Swift should get a mention. The first I heard of cocoa was in researching Swift for a project. According to at least one source http://arstechnica.com/apple/2014/06/a-fast-look-at-swift-apples-new-programming-language/ Cocoa works with Swift so perhaps Swift should be mentioned along with the other languages being mentioned in the article. 184.75.159.160 (talk) 00:04, 6 June 2014 (UTC)
thread_title:  Swift? 

message: Since Yellow Box does not have a dedicated webpage, I'm writing here.
Yellow Box for Windows could be found in WebObjects for Windows, Yellow Box Developer Preview, OPENSTEP Enterprise for Windows, Rhapsody DR2 for Windows and it's not obvious what is the order between them. One man has shown screenshots of "Project Builder" about Window on different Yellow Boxes.
OPENSTEP Enterprise 4.2 (1996?) v300.2
Rhapsody DR2 (1998) v332.2
WebObjects 4.5.1 (2001) contain Yellow Box 1.0, v365
YellowBox 5.1 DR2 (?), v?
OCTAGRAM (talk) 22:45, 22 November 2014 (UTC)
replies: text: Yellow Box might not be significant enough to have its own Wikipedia page.  However, OpenStep does have its own Wikipedia page. Guy Harris (talk) 23:14, 22 November 2014 (UTC)
thread_title:  Yellow Box history 

message: Recently there has been work on an open source Cocoa binding in C called Silicon. 
Maybe it could be added to the list of other Cocoa bindings? ColleagueRiley (talk) 20:17, 9 April 2023 (UTC)
thread_title:  Cocoa Binding in C