
	Where results make sense

Topic: Carbon (API)

Related Topics

Magnesium

NeXT

	Carbon (API) - Wikipedia, the free encyclopedia
		Carbon is often seen as a transitional or legacy technology, but in fact it is unlikely that large legacy codebases (e.g., Adobe Photoshop, etc.) ever will be completely rewritten for Mac OS X, and so it will necessarily remain a core part of the OS X operating system indefinitely.
		Carbon is often confused and/or compared with Cocoa, but the two are complementary and are solving different problems.
		Carbon descends from the Toolbox, and as such, is composed of "Managers".
	en.wikipedia.org /wiki/Carbon_(API) (1599 words)

	Carbon development language list
		Carbon applications are closely related to applications traditionally written for the Mac OS.
		Carbon is based on the programming tools available for MacOS 9 and earlier, and allows a smooth path for bringing applications to OS X. Apple is providing strong support for this programming environment, and the libraries provided have been maturing for over 15 years.
		A growing developer community has brought a large number of Carbon apps to the platform, and the developer tools and libraries are abundant.
	osx.hyperjeff.net /Reference/carbon.php (449 words)

	DVD Recorders and Players: Carbon Programming - $36.49
		The programming samples (several run over 50 pages) not only show off еvеrу API at work, but each is preceded bу a listing of all available API methods аnd constants used in each demo, making this a reference as well as a programming tutorial.
		Carbon Programming is a comprehensive guide that is logically organized, compatible with the current system software, and includes ready-to-run dеmоnstrаtiоn programs within each chapter.
		Carbon Programming is a comprehensive guide that is logically organized, compatible with the current sуstеm software, and includes ready-to-run demonstration programs within еасh chapter.
	www.dvdplayers-store.info /good30363732333232363736.html (1230 words)

	Red Sweater Blog - The Cocoa-Carbon Advantage
		Carbon is not the same kind of application framework that Cocoa is. That’s why the Mac has had a long history of good C++ frameworks, from Think Class Library, MacApp, and PowerPlant to modern ones that wrap up all of HIToolbox and Carbon Events.
		Another area where Carbon is deliberately hindered vs. Cocoa is in the “grow thumb” in Carbon windows, which appears as a solid-white background square instead of transparent as in Cocoa-derived windows.
		Carbon can make the grow thumb appear identical to Cocoa windows, it is simply not the default appearance for no technical reason whatsoever (just political ones, methinks, but what do I know).
	www.red-sweater.com /blog/181/the-cocoa-carbon-advantage (5922 words)

	Call Me Fishmeal.: Pimp My Code, Part 12: Frozen in Carbonite. (Site not responding. Last check: 2007-11-03)
		Carbon is descended from the original Mac Toolbox written in the early 1980s, and still shows signs of its Pascal and machine-language origins, even though it is now primarily accessed through and written in the C language.
		Carbon is wordy, in part because it is based on C, and in part because it still uses metaphors and programming conventions that were in vogue twenty to thirty years ago.
		Carbon memory management is a mish-mash of new and old metaphors, so you might easily find yourself using, in addition to CoreFoundation objects that can be retained and released, "Handles" or "Atoms", which are obtuse and easy to screw up.
	wilshipley.com /blog/2006/10/pimp-my-code-part-12-frozen-in.html (10605 words)

	Interview with Cosmoe's Bill Hayden - OSNews.com
		Carbon was just coming out, and it looked like the future of MacOS programming, so I used it as the basis of the port.
		The Carbon API is implemented using the BeOS API.
		The native Cosmoe API is a significantly reworked derivative of the Atheos API, which is done in C++.
	www.osnews.com /story.php?news_id=1075 (1117 words)

	MacKiDo/Opinion/CarbonFutures
		Since Carbon and YellowBox are going to likely be merged into one mega-API in the future (with YellowBox being the high-level API, on top of Carbon which is the low-level API), I sometimes refer both "Carbon and YellowBox" as just "Carbon" -- as I believe they will be the same thing.
		So while Carbon on Windows is a great plan, Mac OS X on Intel is not exactly a bad plan either.
		Carbon on Windows, or MacOS X on Intel, would be the exact opposite.
	www.mackido.com /Opinion/Carbon.html (2738 words)

	Activated Carbon Filter Manufacturer - TIGG Corporation
		TIGG Corporation is a pioneer manufacturer of modular activated carbon treatment systems for various process and environmental remediation and control applications.
		Founded in 1978, TIGG has manufactured activated carbon adsorption vessels in a variety of sizes, designs and materials of construction such as lined carbon steel, stainless steel, and thermoplastics.
		Carbon and stainless steel tank and vessel capability ranges to 12 foot diameter and 10 foot sidewalls.
	www.tigg.com /company_info/api_tank.html (251 words)

	Learning Carbon: Chapter 6: Carbon Events
		Carbon supports two event-handling models, although only one is recommended.
		Carbon events happen, at a general level, in a window or in a menu.
		Carbon provides a default event handler for each type of event target (window, menu, control, and application).
	www.oreilly.com /catalog/learncarbon/chapter/ch06.html (4652 words)

	PalmSource \| Conduit Development Basics
		The Sync Manager API is the programmatic interface for communicating with the handheld.
		Carbon is a subset of the classic Mac OS API that is available for both Mac OS 9 and Mac OS X applications.
		The first step to updating ("Carbonizing") an existing conduit to work under both Mac OS 9 and Mac OS X is to download and use Apple's Carbon Dater utility, which will examine your existing conduit and create a report indicating what changes are needed in order to make it Carbon-compliant.
	www.palmos.com /dev/support/docs/conduits/mac403/MCComp_Overview.html (1761 words)

	creativepro.com - The Difference Between Cocoa and Carbon Apps
		Carbon is a way for developers to transform their "Classic" applications quickly and with relative ease.
		According to Apple, developers using the Carbon API's are able to make an application Carbon by changing only 10 to 30 percent of the existing code.
		"A developer who is Carbonizing their application can do an absolute minimalist job, in which case they will get all of the baseline capabilities of Mac OS X in terms of being a modern process with a basic Aqua user interface," Bereskin said.
	www.creativepro.com /printerfriendly/story/9236.html (461 words)

	Ars Technica: Mac OS X DP2: A Preview - Page 3 - (12/99) (Site not responding. Last check: 2007-11-03)
		Carbon is a revision of the classic Mac OS API that eliminates or changes any functions that do not lend themselves to implementation in a modern, memory-protected, preemptive multitasking environment.
		Hence, Carbon is the transitional API for Mac OS developers on both sides of the fence: OS 9.x and OS X. Making the next major revision of your application Carbon- compliant allows you to sell it to both Mac OS 9.x users and Mac OS X users.
		Previously known as the "Yellow Box", and as the OpenStep APIs before that, Cocoa is the most modern API in Mac OS X. The name change from Yellow Box to Cocoa is yet another horrible computer industry pun centered around the Java programming language.
	arstechnica.com /reviews/4q99/macos-x-dp2/m-macos-x-dp2-3.html (678 words)

	Intro To Mac Porting - OpenOffice.org Wiki
		You just need to first be comfortable with the concepts of Carbon and how to manipulate the different elements of the API and then it will be very easy to implement functions.
		The Windows API is actually very close to the Carbon API and the Windows implementation can always give you an idea about how to structure your function.
		The first thing to do is look in the Carbon API how to get the current display's size, how to resize a window and how to save the current state of a window.
	wiki.services.openoffice.org /wiki/Intro_To_Mac_Porting (2122 words)

	MacKiDo/Opinion/RhapsodyDead
		They are going to eliminate a few thousand of the "bad" API calls, and replace them with better ones.
		That those lower level API's change from Display Postscript and Unix to MacOS to Windows to Solaris is irrelevant.
		Carbon is just Apples way to bring Mac Apps into the future as well.
	www.mackido.com /Opinion/RhapsodyDead.html (2173 words)

	Mac OS X's Finder: Cocoa rewrite not the answer \| The Register
		Certainly Carbon seems to be getting all the bad press, while Cocoa is being held up as some sort of shining beacon lighting the way to 'true' Mac OS X native apps.
		Carbon was only developed because some of the biggest Mac software developers balked at being forced to rewrite their code from scratch.
		Carbon can work with both of these 'event models', but to get the most from it code needs to be written with the OS X event model in mind.
	www.theregister.co.uk /2001/06/21/mac_os_xs_finder_cocoa (1328 words)

	Ed Craig's WeldReality.com
		API 1104 is Standard for welding pipe lines.
		Note the API code does not spell out the MIG gas mix that must be used with the short circuit process on pipe welds.
		Carbon, manganese and low alloy steels made at the mill with inadequate deoxidization are sensitive to lamellar tearing.
	www.weldreality.com /ASTM_API.htm (1996 words)

	Amazon.com: Carbon Programming: Books: Kevin Bricknell (Site not responding. Last check: 2007-11-03)
		The programming samples (several run over 50 pages) not only show off every API at work, but each is preceded by a listing of all available API methods and constants used in each demo, making this a reference as well as a programming tutorial.
		The author provides a great tour of every imaginable area of the Carbon API (which allows developers to target both the Mac X OS and older versions of the Mac OS).
		Carbon Programming is a comprehensive guide that is logically organized, compatible with the current system software, and includes ready-to-run demonstration programs within each chapter.
	www.amazon.com /Carbon-Programming-Kevin-Bricknell/dp/0672322676 (1769 words)

	Above the Kernel
		Carbon has traditionally been a very critical Mac OS API family, and is so in Mac OS X as well.
		LangAnalysis: an API to the Language Analysis Manager, allows for analyzing morphemes (a morpheme is a meaningful linguistic unit, that is, a distinctive collocation of phonemes, having no smaller meaningful parts) in text.
		Carbon: This is a set of procedural C-based APIs for Mac OS X that are based on the "old" Mac OS 9 APIs.
	www.kernelthread.com /mac/osx/arch_sys.html (1123 words)

	Chibineko.org - Mac OS X tips, tricks and articles
		This is a set of procedural C-based APIs for Mac OS X that are based on the old Mac OS 9 API, although it actually goes back to MacOS 8.1.
		Carbon was originally designed to provide an easy development migration path from Mac OS 9 to Mac OS X. The Carbon APIs are all-encompassing (they include legacy interfaces), covering most things that you are likely to do on Mac OS X. Carbon specific code is not portable to other platforms.
		This is an object-oriented based API that's the preferred way of doing things in Mac OS X (if what you want to do can be done through Cocoa), particularly because of how well it's supported by Apple's Rapid Development tools.
	www.chibineko.org /article5.shtml (2662 words)

	Mac OS X Porting - Native Printing - OpenOffice.org Wiki
		Then, we will also need to implement low-level printing using OS API because, without that the user might not be able to use every setting available in the native dialog.
		To achieve this, we want to know the functionality of this class, and let carbon manage the functionality maybe at this level or maybe in a other lever (higher or lower).
		The strategy is to first use the Carbon API to get Print Information and to provide an Aqua User Inerface for printing.
	wiki.services.openoffice.org /wiki/Mac_OS_X_Porting_-_Native_Printing (1495 words)

	It strange nobody mentioned it but carbon is the way to go for cross platform (Site not responding. Last check: 2007-11-03)
		Since Carbon and Win32 are very close, conceptually, it is much easier to write such applications with Carbon.
		I think Carbon Events, which Cocoa seems to be built on top of, will survive, and some other key features, but a large portion of Carbon will slowly fade out as OS 9 disappears.
		Apple have used Carbon to implement some of the Mac OS X Cocoa methods, but it isn't used from the ground up as your comment implies.
	tim.oreilly.com /cs/user/view/cs_msg/3272 (709 words)

	The Carbon Component Framework - Carbon Library Usage
		This document details the 3rd party libraries used by Carbon, why they are used, and the license agreements involved with each.
		Xalan is use as the XSLT processor during the build process of Carbon.
		Carbon uses JDOM as its API for the manipulation of XML files in the XML-based configuration system.
	carbon.sourceforge.net /Libraries.html (341 words)

	Unsanity.org: Cocoa vs Carbon
		This is often true (bug-wise) due to the fact Cocoa implements lot of high-level sht Carbon* developers have to much with themselves, which cuts the number of bugs in UI code significantly.
		However, with all that said, my experience with OS X has very much been that Carbon apps are typically inconsistent in their UI, often more buggy / less stable, and generally much more annoying to use than the various Cocoa applications I have run into.
		Carbon & Cocoa are different today, this is true, and will likely remain true for a bit longer.
	www.unsanity.org /archives/000024.php (3407 words)

	Technical Note TN2058: The Font Panel for Carbon API
		Describes the API used to display and interact with the Font Panel from a Carbon application on Mac OS X. Introduction
		This dialog is implemented by the NSFontPanel class using Objective C and Cocoa and is not directly accessible from Carbon applications.
		Modifying your Carbon application to use the Font Panel API is not difficult, and enhances the Mac OS X experience by giving your users an interface for font selection that is consistent with Cocoa applications and is easier and often more convenient than a Fonts menu.
	developer.apple.com /technotes/tn2002/tn2058.html (2305 words)

	TechNetCast 1998-06-26 - Mac OS X
		The first is that the Carbon APIs themselves, the subset that is moving forward, will be implemented natively on top of the new mach-based core Mac OS X. No emulation.
		But we do so in a Web and e-mail based architecture, such that as the carbon implementation and specification is taking final form, we can update the information and developers can just retest their application again through the Internet and get the latest information on an ongoing basis.
		You take your application binary, drop it on top of the carbon dating tool, and what it does is it performs an analysis of all of the toolbox in ports required by that application.
	technetcast.ddj.com /hz-show-980626.html (4090 words)

Try your search on: Qwika (all wikis)