Re: [Pyobjc-dev] Suggested Documentation change

[Ronald O. <ous...@ci...>]

On Wednesday, 13 August, 2003, at 19:49, Pierce T. Wetter III wrote:

> Currently:
>
>
> The basics
>
> The code for loading a framework and exporting its classes is pretty  
> simple:
>
[...]

>
> Change to:
>
> The basics
>
[ improved version ]

Thanks for the feedback.

> Don't forget to import the frameworks that are used by your framework  
> before calling objc.loadBundle. This is necessary to arrange for the  
> helper code for these modules (if there is any) to be loaded.
>
> Pierce
>
> P.S.
>
>   I'm not sure about the: "Don't forget to import the frameworks that  
> are used by your framework before calling objc.loadBundle." line. I  
> did a quick test and found out that the framework loading mechanism  
> seemed to be able to figure it out even if I didn't load all the  
> required frameworks. It used to be true under Rhapsody, but X seems to  
> have fixed this.

I'll try to clarify this in the documentation. There is a PyObjC  
problem w.r.t. fixing the method signatures for a number of methods.  
The wrappers for AppKit and Foundation update the method signatures for  
a number of methods with input/output pass-by-reference arguments.  
Those updates don't work if the method list for a class has already  
been scanned. Importing the PyObjC modules in the right order solves  
this problem, and I have correctly fixing this problem on my todo list.


Ronald
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct; 
> at.aspnet_072303_01/01
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>