OOFILE | Downloads | Purchasing | Press | Services | Company Information | Soapbox | References | F.A.Q. | HOME


PP2MFC and AM/MFC Getting Started

An OOFILE Product


This document summarises the processes and tools used to develop using our cross-platform PP2MFC toolkit with the AppMaker MFC code generator.

One set of instructions is included here because it's assumed that most people will be using AppMaker to generate their cross-platform code, or starting with code that has been generated for them.

The Process

  1. Draw your application windows in AppMaker, or import an existing application.
  2. Specify Commands linked to the menu items and controls in AppMaker.
  3. Specify DataDefs to describe any data types you want to have edited and possibly persistent to disk.
  4. Generate MFC code using an appropriate generator, eg: for the windowing model you desire.
  5. Compile the generated code using the stationery included for CodeWarrior or Visual C++.
  6. Include your business logic, written to the PowerPlant interface.

Quick Tips

A very important point is that you do NOT need to rush out and buy a Windows compiler - the standard Mac CodeWarrior IDE includes x86 compilers and cross-platform debugging via TCP/IP or a serial cable.

Even better, cross-platform debugging means you don't need a very grunty PC on which to test your application - even an old 486 will do for simple apps.

PP2MFC is also tested with Visual C++ but anyone doing Visual C++ development is assumed to be a savvy Windows programmer with loads of other documentation on how to run their projects :-)

Windows Resource Editing

The Pro4 resource editor ships with CW Pro5 in the Thrill Seekers folder. It has been tested and confirmed to work with code generated from AppMaker. Full documentation is included in the Resource Editor.zip archive. It was dropped from later versions of CodeWarrior as being too unreliable and too expensive to fix.

There are no Windows resource editors included with the Mac CodeWarrior CD. You can tweak resource text files by hand if you desire, or keep changing them in AppMaker and regenerate.

A good guide to free editors is http://www.thefreecountry.com/programming/resourceeditors.shtml

Using CodeWarrior to debug Windows apps

Start by building a standard CW Example like the MFC chkbook and make sure you can debug that before you try your generated code. This proves your debugging environment is doing the right thing transferring and controlling the Windows application.

You need to run the MWRemote.exe program on your PC - it can be found in the Win32-x86 folder on your CW Pro Tools CD. The default TCP/IP settings and port will usually work and all you need to know is the IP Address of the PC - look that up in:

This IP number is entered into your Mac CodeWarrior IDE Preferences (NOT the project settings) under:

Once this is done you can run your project on the Mac. You can only run Debug targets and you must Enable Debugging (Project menu) before they can be run.

This is a little disconcerting - we're used to being able to run Debug targets on the Mac without enabling debugging so you might sit and stare at the project for a few minutes wondering why the Run button is disabled (I did!).

Other Docs

Temperature Walkthrough walks you through the specific AppMaker Temperature example

PP2MFC Prog Notes is a collection of detailed notes on how the PP2MFC framework maps PowerPlant to MFC.

AM MFC CodeGen Details describes low level details of how the MFC code generator generates code compared to the PP generator.

Recommended MFC and Windows Programming Books the books that I use to "understand" MFC.