Anyway, it does note make sense, as upgrading the view without
rewriting all the logic using Cocoa paradigms is probably not a good
idea.
Unlike Carbon nib, Cocoa nib are not just a set of interface object
with some property and flags, they also contains lots of information
about action,
It would be a nightmare to recreate them by hand... , especially for the big
project which needs to move to Cocoa..
No better method?
On Mon, Jun 30, 2008 at 3:37 AM, Christopher Pavicich [EMAIL PROTECTED] wrote:
Hi:
There is no way to automatically convert a Carbon Interface Builder
This question was asked recently on the carbon-dev list and the
answer was that there is no way to automate the process, nor even a
method to get you part-way. Unfortunately this is likely to be one of
those painful transitions for you...
On Jul 2, 2008, at 8:31 PM, Fosse wrote:
It would
My Carbon nib contains a lot of dialogs. I want to make it be used by
another cocoa application and don't want to create all those dialogs and
econstruct the entire control hierarchy manually in the Interface Builder. I
don't care about connections, I'll wire them up myself. I'm just hoping to
Hi:
There is no way to automatically convert a Carbon Interface
Builder Document into a Cocoa Interface Builder Document.
You are going to need to recreate all of your Carbon dialogues in
Cocoa. By hand.
--Chris
On Jun 29, 2008, at 1:59 AM, Fosse wrote:
My Carbon nib contains a
