wxWindows 2 for Mac FAQ

X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/2edb0bdef6238c8c246b6978bc14828b7033d931..e1366cdb2a2c3fdbce35d6ef3207d01c288c8bfa:/docs/html/faqmac.htm?ds=inline diff --git a/docs/html/faqmac.htm b/docs/html/faqmac.htm index 7b4663fb96..3e7f255569 100644 --- a/docs/html/faqmac.htm +++ b/docs/html/faqmac.htm @@ -2,7 +2,7 @@ -wxWindows 2 for Mac FAQ +wxWidgets 2 for Mac FAQ @@ -13,7 +13,7 @@ -wxWindows 2 for Mac FAQ +wxWidgets 2 for Mac FAQ @@ -30,13 +30,15 @@ See also top-level FAQ page.

How is the Mac OS X port different from the Classic Mac OS port?

How are improvements to the Classic Mac OS port integrated into the Mac OS X port?

What compilers are supported?

How does CVS handle file types/creators under Mac OS 8.x/9.x?

How does CVS handle file types/creators under Mac OS X?

What steps are required to build wxMac using CodeWarrior Pro 5.3?

How does CVS handle file types/creators under Mac OS 8.x /9.x?

How does CVS handle file types/creators under Mac OS X?

What steps are required to build wxMac using CodeWarrior P ro 5.3?

What steps are required to build wxMac under Mac OS X?

What important settings are required in the CodeWarrior Project Preferences?

What are the smart preprocessing errors with the Apple Developer Tools?

How does wxMac support the standard Apple About menu item and Help menu?

How do I add an icon to my application?

How can I easily switch between different versions of wxWidgets in CodeWarrior?

@@ -52,15 +54,15 @@ The author of this port is Stefan Cs

Which Mac platforms are supported?

-wxWindows 2 can be used to develop and deliver applications on Classic Mac OS (e.g. Mac OS 8.x/9.x) both as Carbon and non-Carbon applications. +wxWidgets 2 can be used to develop and deliver applications on Classic Mac OS (e.g. Mac OS 8.x/9.x) both as Carbon and non-Carbon applications.

-A Mac OS X port is in progress in order to be able to build wxWindows applications using the Apple Developer Tools that are delivered with every copy of Mac OS X. +A Mac OS X port is in progress in order to be able to build wxWidgets applications using the Apple Developer Tools that are delivered with every copy of Mac OS X. The Mac OS X port is based on and, for the most part, merged with the Carbon code for Classic Mac OS.

How is the Mac OS X port different from the Classic Mac OS port?

-wxMac for Mac OS X shares code both with wxMac for Mac OS and common Unix code in wxWindows. The aim is to use the same Mac OS Carbon code both for Classic Mac OS and for Mac OS X while leveraging the fact that Mac OS X is a BSD Unix. +wxMac for Mac OS X shares code both with wxMac for Mac OS and common Unix code in wxWidgets. The aim is to use the same Mac OS Carbon code both for Classic Mac OS and for Mac OS X while leveraging the fact that Mac OS X is a BSD Unix.

This hybrid approach was suggested by Apple to the Fizzilla team working on Mozilla for Mac OS X.

@@ -85,7 +87,7 @@ Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior P

How does CVS handle file types/creators under Mac OS 8.x/9.x?

-Before checking out the wxWindows code using a CVS client under Mac OS 8.x/9.x, be sure your computer is set up to treat xpm and xbm images correctly: +Before checking out the wxWidgets code using a CVS client under Mac OS 8.x/9.x, be sure your computer is set up to treat xpm and xbm images correctly:

bring up the Internet control panel, select the Advanced Options tab, click on the File Mapping icon from the list at the left and see if there are is an entry for ".xpm" files and another for ".xbm".
if an entry exists, click Change... and make sure File Type is TEXT (just those four capital letters); correct it if necessary. If there is no entry, make one with type set to TEXT and creator set to anything you like; reasonable choices include GKON (Graphic Converter) or CWIE (CodeWarrior). @@ -99,8 +101,8 @@ The Mac OS X CVS client does not handle file types and creators at all (just lik
All files checked out under Mac OS X will be untyped and CodeWarrior will not recognize them correctly. To correct this, use the autotyper provided in the CVS sources:
- decode and decompress the file wxWindows/docs/mac/TypeAsMetrowerksText.sea.hqx -
- drag the wxWindows CVS sandbox directory onto the autotyper and most of the files will be typed according to the file extension +
- decode and decompress the file wxWidgets/docs/mac/TypeAsMetrowerksText.sea.hqx +
- drag the wxWidgets CVS sandbox directory onto the autotyper and most of the files will be typed according to the file extension
@@ -123,11 +125,11 @@ This is also necessary even if you don'want to build the Carbon targets.
Build the projects (makemac6.mcp for CodeWarrior Pro 6; makemac.mpc for CodeWarrior Pro 5) in the following five directories:
- wxWindows:src: -
- wxWindows:src:jpeg: -
- wxWindows:src:png: -
- wxWindows:src:tiff: -
- wxWindows:src:zlib: +
- wxWidgets:src: +
- wxWidgets:src:jpeg: +
- wxWidgets:src:png: +
- wxWidgets:src:tiff: +
- wxWidgets:src:zlib:
@@ -137,8 +139,8 @@ You need to have the Apple Developer Tools installed. The Developer Tools CD is
Building wxMac completely without configure is not supported.
-Building wxWindows directly in the CVS sandbox is not recommended. Instead, wxWindows should be built in a directory configured relatively to the CVS sandbox. -For instance, to build wxMac with configure, start in the base wxWindows directory and type: +Building wxWidgets directly in the CVS sandbox is not recommended. Instead, wxWidgets should be built in a directory configured relatively to the CVS sandbox. +For instance, to build wxMac with configure, start in the base wxWidgets directory and type:
- mkdir macbuild
- cd macbuild @@ -195,15 +197,40 @@ This error can sometimes be corrected or avoided by modifying the source code. H
  How does wxMac support the standard Apple About menu item and Help menu?
  -Because wxWindows does not have a specific API for the About menu item or the Help menu, the Mac OS port uses some static variables to help the engine make the right decisions: +Because wxWidgets does not have a specific API for the About menu item or the Help menu, the Mac OS port uses some static variables to help the engine make the right decisions:
  - It assumes that the About menu item is part of a Help menu.
  - The title of the Help menu is stored in wxApp::s_macHelpMenuTitleName, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
  - The item Id of the About menu is stored in wxApp::s_macAboutMenuItemID, it defaults to wxID_ABOUT, but can be changed as well to suit your needs. -
  - The other items of the wxWindows help menu are appended to the Mac OS Help menu and the translation of Ids is handled transparently for your application. +
  - The other items of the wxWidgets help menu are appended to the Mac OS Help menu and the translation of Ids is handled transparently for your application.
  +
  How do I add an icon to my application?
  + +If you have Mac OS X, you have the icns editor somewhere in the +Utilities folder. Create an icon using this tool and DeRez it, so that you have a .r +file with a 'icns' resource with id (-16455). Include this .r file in +your project and in the CodeWarrior Settings add a check mark under Linker:Output +Flags/Finder Flags/Has Custom Icon. +
  + +
  How can I easily switch between different versions of wxWidgets in CodeWarrior?
  + +Sometimes you want to test your application against different versions +of wxWidgets, for example a stable version of wxWidgets versus a development version. +The easiest way to do this is to create a symbolic path.
  + +Under Edit-Preferences in General:Source Trees, type a name (for example WXWIN) +and choose a path for it. Now reselect your include and lib paths for a last +time, in the settings for each configuration, but make them relative to the symbolic name. +
  + +From now on you can just change the path associated with the symbolic name. + +
  + +