🚀 go-pugleaf

in article mwron-5078AC.10455103092003@enews.newsguy.com, MW Ron at
mwron@metrowerks.com wrote on 9/3/03 7:45 AM:

> In article <BB7A87FD.B61E%kkb@breathsense.com>,
> Kurt Bigler <kkb@breathsense.com> wrote:
> 
>> in article mwron-4158FF.11431902092003@enews.newsguy.com, MW Ron at
>> mwron@metrowerks.com wrote on 9/2/03 8:43 AM:
>> 
>>> We will include a version of CW 8 IDE that can be used as a standalone
>>> debugger for Classic Debugging or debugging on OS 9.
>> 
>> This is something I haven't tried likely, thought it didn't work at one
>> point, but it will become important soon.  Are you saying that I can debug
>> classic apps while running OS X?  Is this done by running the IDE in classic
>> mode?
> 
> Yes just launch the 8.3 version as classic.  There was a bug iwth the
> 5.0 IDE if you debugged on the boot volume but that was fixed with the
> 5.1 IDE with Cw 8.3
>> 
>> Or when you say "as a standalong debugger" do you mean I get to run the IDE
>> (for editing) in native (Carbon/Cocoa) mode and only the debugger (and the
>> app) run in classic.
> 
> CW 9 will use the IDE stripped down to debugging items only and it will
> run in OS 9 for debugging  and read the CW 9 symbolics.

I have to ask my question again.  Maybe you answered it but I couldn't
understand it.  I'm trying hard to be clear here, so I hope you can read
through it carefully...

Can I be editing in the *normal* CW 9 IDE, running as a native
(Carbon/Cocoa) app, and invoke the Debug command from within that native IDE
and as a result cause the stripped-down-debugger-only classic IDE to run,
giving me a debugger window?

If this basically works, are there any weaknesses in this arrangement, ways
that the two IDE's don't play well together?

If not, can the native IDE and the classic debugger still peacfully coexist,
requiring perhaps just an extra step to invoke the debugger (like dropping
the sym file on the classic-debugger-only IDE)?

Thanks,
Kurt

> 
> Ron