Jim,
I am still using a beige G3 Mac as well as running CW on Virtual PC. I can only
use PILRC in VPC and I find it is like trying to eat gravy with a fork compared
to the solid structure of Constructor.
The strange thing I discovered is that a Constructor file comes up with
different resources inside Windows to what it does on the Mac. I thought I could
simply transfer these files from one system to the other but not so. This
explains why so many Constructor examples made with windoze come up looking
empty on the Mac.
This usually happens when the data and resource forks aren't properly integrated -- for example, if you move over the Windows resource fork file and don't properly reconstruct it on the Mac, it will all appear empty. The same thing can happen going back to windows with a network client that doesn't separate the forks.
One of the reasons to avoid Constructor on Windows is the nasty management of two files (one which should always be 0 bytes) to hold resources. It works better on the Mac.
As for PilRC -- it's easy to build a Mac OS X native version of it, since it's a command line utility. If you mean "PilRC Designer", that's a separate program, and the PilRC language shouldn't be judged based on that editor's capabilities.
-- Ben Combee, DTS technical lead, PalmSource, Inc. Read "Combee on Palm OS" at http://palmos.combee.net/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
