Re: "backporting" nibs question / Rhapsody license anyone?
Re: "backporting" nibs question / Rhapsody license anyone?
- Subject: Re: "backporting" nibs question / Rhapsody license anyone?
- From: Jonathan Hess <email@hidden>
- Date: Mon, 4 Aug 2008 15:15:43 -0700
I read the original question to mean that Lars was trying to get the
NIB's from Rhapsody to run on Open Step. If so, I don't know of anyway
to do this. It's largely the reason we use NSKeyedArchiver on Mac OS X
instead of NSArchiver. Generally, we're pretty good about reading old
binary formatted archives with newer code.
Jon Hess
On Aug 4, 2008, at 2:55 PM, Bill Bumgarner wrote:
On Aug 4, 2008, at 2:46 PM, Lars Sonchocky-Helldorf wrote:
- So does anyone on this list know of a way to "backport" nibs to
an earlier version (besides recreating all the nibs from scratch)?
Your problem statement doesn't make sense. The NIBs don't need to
be backported. The problem is that the NIBs contain constructs that
no longer unarchive correctly -- most likely because the code used
to unarchive the ancient version of the NIBs compatibility has been
removed.
Given that the NIB does actually open, your choices are two fold.
The shortest, but most manual labor way, would be to open the NIBs
in IB, fix up the broken connections, then save it. That should
result in a working NIB, with a bit of debugging.
The second way is slightly more indirect.
You'll need to find a copy of Rhapsody DR1 or DR2, Mac OS X Public
Beta, and -- most likely -- Mac OS X 10.1 or so. You can then open
the NIB file in each version, save it in that version, and then move
on to the next OS Release. Rinse. Repeat. This generally results
in a working NIB on the modern system.
Unless, of course, the code involves custom IB palettes. If it
does, you are going to need to either port those across the systems,
making the palette available on each interim system, or figure out a
way to eliminate the palettes altogether on the most ancient OS you
can work with.
And you might have to write a palette of your own to adjust the NIB
along the way. Fortunately, IB has long had a powerful API for
adjusting the NIB's object graph as it is loaded. I used it to fix
a number of issues along a similar path when moving a codebase from
NS 3.3 to Mac OS X 10.2 (Jaguar).
Oh -- one other thing -- with a bit of cajoling, I found it possible
to run all the various flavors of Mac OS X and OpenStep under
Virtual PC. Maybe the same thing will be possible with the modern
"emulators".
Have fun,
b.bum_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden