Re: Version Nib Loading?
Re: Version Nib Loading?
- Subject: Re: Version Nib Loading?
- From: Stephane <email@hidden>
- Date: Wed, 20 Jun 2007 19:37:41 +0200
On Jun 20, 2007, at 6:37 PM, Jeff Alexander wrote:
AFAIK, it would be equivalent to the code loading mechanism I
described (I would rather use a prefix on the nib name with the OS
version) since you would need to load it manually with code.
Yes, that would be exactly the same; in the one case you are using an
obscure language/region to stand in for a not-yet-released OS, so it
makes a nice work around. But note the rest of my post and a reply on
the list regarding NDA. Obscurity might not defend you against an NDA
violation.
I'm not sure it would go against NDA in most cases:
1. I would tend to believe that a nib built on a non released OS
including new objects specific to this release can't be opened by a
shipping IB. Of course, you could have a look at the nib using a hex
or a text editor.
2. In the case of a new NSButton type, the back-from-the-future nib
would contain only an integer with the new type. And nobody can see
this new button look without the non released OS.
3. I tend to believe it's safer to release a specific nib for a
specific OS version after the GM is made available so you can test it
against the GM before releasing it. So this solution would be used to
avoid shipping 2 different releases or dumping compatibility with an
older release of a product.
My $0.02
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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