Igor Delovski Board

[delovski]

Where Is __va_start Declared?

"I am in the process of porting all my CW code over to XCode (yeah,
yeah, I know I am a few years late) and have just finished getting all my
libraries to build properly."

[delovski]

comp.sys.mac.programmer.codewarrior - carbonization...

Miro Jurisic: "If you want your software to run properly on Mac OS X, the
only way to debug it is under Mac OS X. At that point, you might as well
develop it under Mac OS X as well."

Warren J. Dew: "Is your software PowerPC or 68k? If the latter, it's
convenient to have an older version of CodeWarrior (one that supports 68k
code) available while converting the software to native PowerPC, a necessary
prerequisite to carbonization."

[Ike]

Extract fuul file name from OpenDialog

"You should use the newer Nav Serv APIs. Avoid any API that uses FSSpecs."

[delovski]

Get a picture from a resource file and draw it

"I think the current recommended mechanism for procedural code uses
QuickTime and discrete image files."

[Ike]

Apple: Introduction to Carbon Porting Guide

"What Is Carbon?
What Are the Benefits of Carbon?
What Is in Carbon Today?
What’s Not in Carbon?
How Does Carbon Work?
Carbon and the Mac OS Application Model
Additional Information and Feedback"

Apple: Carbon Development Tips & Tricks

"If you are running animation, or other high frequency timer driven events
from your WaitNextEvent based application you may get better performance
by increasing your sleep time passed into WaitNextEvent. Yes, increasing
your sleep time. Passing in a small sleep time such as 0 or 1 may cause a
barrage of null events to be sent to your application. Event Loop Timers
only fire while waiting on the Event Queue, i.e. while blocked in WaitNextEvent.

So, passing in a larger sleep time may cause your high frequency timers
to actually fire more often and your CPU usage to drop significantly."

[delovski]

ADC: Technical Note TN2003 - Moving Your Code to Mac OS X

"This Technical Note describes how to move existing applications to Mac OS X
and where equivalent functionality found in existing applications and other
software can be implemented in Mac OS X."

[delovski]

MacTECH: Carbon: Getting Ready for Mac OS X, by Dan Parks Sydow

Becoming familiar with the Carbon API to ready your code for Mac OS X

"Each operating system has its own API, so to make it quickly evident which
API a programmer is referring to, each API has a name. As you know from
reading Getting Started, the API Macintosh programmers use is referred to
as the Macintosh Toolbox (or the Mac Toolbox, or simply the Toolbox). The
Macintosh Toolbox, like any API, is nothing more than a set (albeit a very
large set) of routines. When you learn how to make use of these routines,
you know how to write programs.

... Carbon is nothing more than a cleaned-up, enhanced, Macintosh Toolbox.
If you're familiar with the Macintosh Toolbox, you're familiar with Carbon.
The more you already know about the Macintosh Toolbox, the more you
will know about Carbon."

[delovski]

Apple: Carbon User Experience Guides

"Accessibility Programming Guidelines for Carbon, Apple Human Interface
Guidelines, Dock Tile Programming Guide, Software Delivery Guide, Search
Kit Programming Guide, HIArchive Programming Guide, Handling Carbon
Windows and Controls, HIToolbar Programming Guide, HIView Programming
Guide ,Setting Up Your Carbon Application to Use the Services Menu, Desktop
Icons, Programming with the Appearance Manager, etc."

[delovski]

Macromedia: Avoiding Pitfalls when Porting to Mac OS X [PDF]

A case study of the Macromedia Authorware 7 conversion to Mac OS X from
Mac OS 9, by François Breton

"In order to make the rest of this reading as easy as possible, I have broken
it down into six key issues developers should address to avoid major pitfalls
when porting to Mac OS X."

[delovski]

ADC: DialogsToHIViews

"This sample code illustrates the conversion process from a resource-based
dialog as would have been written for System 6 or 7, to an appearance-savvy
dialog as would have been written for Mac OS X 8 or 9, to a modern nib-based
window with custom HIViews as should be written for Mac OS X 10.2 on."

Includes sample application: DialogsToHIViews.zip

[Ike]

ADC: Core Foundation - Introduction to Design Concepts

"Core Foundation supports the transition from earlier Mac OS to Mac OS X
systems. The evolution of the Mac OS into Mac OS X requires the participation
of application developers. By slightly modifying your current code to use new
programming interfaces and techniques, your applications can run smoothly
on a radically different operating system, one with features such as protected
memory and preemptive multitasking."

[Ike]

MacTech: Carbonization 101 - Easier than you might think and so rewarding
by Éric Simenel

"Another whole section of the traditional Macintosh Toolbox, the Scrap Manager,
has also been revised in Carbon. Most applications use the Scrap Manager
routines in a fairly straightforward way and the amount of modifications you
may have to apply may not be much more complicated than the following."

See: Scrap Manager Reference

"The InfoScrap function is not supported in Carbon. You should use the function
GetCurrentScrap instead. Your application can determine if the scrap contents
have changed by storing the scrap reference returned by GetCurrentScrap and
comparing it against the scrap reference returned by GetCurrentScrap at a later
time. If the two scrap references are different, the scrap has changed."

[delovski]

ADC: Introduction to Porting CodeWarrior Projects to Xcode

"Although this document generally describes how to convert CodeWarrior
projects that build applications, much of the information can be applied to
projects that build plug-ins, bundles, frameworks, and other kinds of software."

ADC: Xcode From a CodeWarrior Perspective

"Though there are many minor differences between Xcode and CodeWarrior,
you’ll find that Xcode supports most of the features CodeWarrior users are
familiar with. Xcode also provides a great deal of flexibility in organizing the
environment for the way you like to work, as described in “Customizing the
Environment”."

ADC: Switching from CodeWarrior to Xcode

"This article is intended for developers who currently use CodeWarrior. It
provides a brief overview of Xcode’s major components, describes the benefits
of moving to Xcode from CodeWarrior, and tells you how to get started."