🚀 go-pugleaf

I am working on a Carbonized app on OS X 10.0.3 with the WWDC Dev Tools
installed on a PB G4.  I have just updated to CW Pro 7EA after getting
frustrated with CW Pro 6.2.

Here are some notes regarding my experience.


First, the good news:

1. The editor works much faster now (it's now usable).

2. I no longer have to wiggle the mouse to get the debugger to appear.

3. Debug > Kill works without having to quit MetroNubX and restart the IDE.

4. Debug > Restart works now.

5. For Pro 6.2, I had made the suggested links as follows:

      cd /System/Library/Frameworks
      ln -s Carbon.framework CarbonCore.framework
      ln -s Carbon Carbon.framework/Versions/A/CarbonCore

   which eliminated the need to manually launch DebugNub Controller and
hit "Start".  This workaround is no longer needed for 7EA.


Now, the bad news, in order of annoyance factor:

1. The debugger still takes about 30 seconds to launch.  This is due to
gdb, according to ProcessViewer.

2. Each step in the debugger takes approximately two seconds.

3. The "Step over == Step into" bug is still there.

4. Debugging now no longer works under CW Pro 6.2.  The app to be tested
gets launched but the stack window never appears.  Maybe the gdb update
caused this?  So there's no turning back.
   

I'm looking forward to the 7EA update Ron mentioned.  Ron, what kind of
performance improvement can we expect?

- Mark