IB Palettes no longer supported in Leopard - what to do?
-
I'm using a third-party framework in my application development that includes an Interface Builder palette. After installing the Leopard upgrade, I found out that these are no longer supported. In fact, the NIB becomes inaccessible whenever such a palette has been used.
Why isn't it still supported? I assumed everything to be backward compatible. And, is there some workaround, conversion tool or something? I would like to take advantage of the new development tools, rather than stick with the old ones just because of this single issue.
Best regards,
Arthur C. -
Install Xcode 2.5 and use the old IB until your palette is updated for
Leopard.
Dave
On Nov 2, 2007, at 10:33 AM, Arthur C. wrote:
> I'm using a third-party framework in my application development that
> includes an Interface Builder palette. After installing the Leopard
> upgrade, I found out that these are no longer supported. In fact,
> the NIB becomes inaccessible whenever such a palette has been used.
>
> Why isn't it still supported? I assumed everything to be backward
> compatible. And, is there some workaround, conversion tool or
> something? I would like to take advantage of the new development
> tools, rather than stick with the old ones just because of this
> single issue.
>
> Best regards,
>
> Arthur C.
>
-
On 11/2/07, Arthur C. <arthur_cw...> wrote:
The release do talk about this... always good to read those before upgrading.
> Why isn't it still supported?
IB 3.0 has a much improved method of writing palettes that isn't
compatible with the older style. In fact, as I understand it, all
Apple provides palettes you see in IB 3.0 now are implemented using
this same method (Apple is eating its own dog food so to speak).
> And, is there some workaround, conversion tool or something?
Use the version of IB that comes with Xcode 2.5 until you can get
updated palettes that work with IB 3.0.
-Shawn -
Hey Arthur -
On Nov 2, 2007, at 10:33 AM, Arthur C. wrote:
> I'm using a third-party framework in my application development that
> includes an Interface Builder palette. After installing the Leopard
> upgrade, I found out that these are no longer supported. In fact,
> the NIB becomes inaccessible whenever such a palette has been used.
>
> Why isn't it still supported? I assumed everything to be backward
> compatible. And, is there some workaround, conversion tool or
> something? I would like to take advantage of the new development
> tools, rather than stick with the old ones just because of this
> single issue.
Beginning with Xcode 2.5, and 3.0, you can have two versions of the
developer tools installed side by side. This setup gives you a
convenient way out of this problem. You can use Interface Builder 2.5
to edit this document until the 3rd part palette is updated. If the
3rd party palette isn't ever going to be updated, you can use
Interface Builder 2.5 to remove the objects that depend on the palette
and either replace them with code, or with NSCustomView and then begin
using Interface Builder 3.0.
Good Luck -
Jon Hess
>
>
> Best regards,
>
> Arthur C.
