pyobjc-dev — CVS commit notices go here

[Pyobjc-dev] Call for help

[Nico W. <nic...@gm...>]

Hi,

I want to load a font from a ttf file and then draw some text using  
this font, and I want to do that in Python using the PyObjC bridge. My  
program already does some drawing; it uses NSBitmapImageReps and  
NSGraphicsContext for that. The font I'm trying to load is http://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-released 
  .

If someone has an idea how I could get this to work, please speak up.

Here's what I tried so far:


1.) Activate the font through ATS, then load it through NSFont through  
its postscript name.

This is what most programs written in ObjC do – they call  
ATSFontActivateFromFileReference to load a ttf file and then can use  
NSFont to load the font given its postscript name. The problem is that  
there seems to be no built-in python binding for ATS. This fails:

     import ATS

Now, ATS.framework is a subframework in the ApplicationServices  
framework, but this fails as well:

     import ApplicationServices

Fair enough. The pyobjc documentation shows how to write your own  
wrapper:

     import objc
     b =  objc.loadBundle("ApplicationServices", globals(),
     bundle_path=objc.pathForFramework(u'/System/Library/Frameworks/ 
ApplicationServices.framework/'))

For reasons I don't quite understand, this doesn't load the ATS  
subframework methods, though (might be related that there is no  
ATS.bridgesupport in /System/Library/Frameworks/ 
ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/ 
Versions/A/Resources/BridgeSupport). I tried to create the  
bridgesupport file on my own, using

     gen_bridge_metadata -f /System/Library/Frameworks/ 
ApplicationServices.framework/Frameworks/ATS.framework -o  
ATS.bridgesupport

This gave some linking errors, and didn't work. `man  
gen_bridge_metadata` even says that there might be problems if you  
want to create bridgesupport files for subframeworks of umbrella  
frameworks, but doesn't really say how to work around them. I tried  
explicitly setting special compiler flags with

     gen_bridge_metadata -f /System/Library/Frameworks/ 
ApplicationServices.framework/Frameworks/ATS.framework -o  
ATS.bridgesupport -c ' -F /System/Library/Frameworks/ 
ApplicationServices.framework/Frameworks/ATS.framework -framework  
ApplicationServices'

, but in vain.

Now, pyobjc has a `loadBundleFunctions` function that can be used to  
load functions from a bundle. One of the examples in /Developer/ 
Examples/Python/PyObjC/Cocoa/AppKit/PyObjCLauncher/LaunchServices.py  
does use this function to load a specific function from a bundle. So I  
tried loading ATSFontActivateFromFileReference thusly (in its own file  
`myfile.py`):

     import objc

     __bundle__ = objc.loadBundle("ApplicationServices", globals(),
         bundle_path=objc.pathForFramework(u'/System/Library/ 
Frameworks/ApplicationServices.framework/'))
     functions = [( u'ATSFontActivateFromFileReference',  
's^{FSRef=[80C]}II^vIo^I' )]
     objc.loadBundleFunctions(__bundle__, globals(), functions)

(See http://developer.apple.com/documentation/Cocoa/Conceptual/ObjCRuntimeGuide/Articles/chapter_7_section_1.html 
  for how the type encodings work; you can use `NSLog(@"FSRef*: %s",  
@encode(FSRef*));` to let gcc show you the type encoding for a given  
type).

To some extent, this even worked. After `import myfile`, I can call  
ATSFontActivateFromFileReference on the `myfile` module. Cool. Now I  
need an FSRef of my font to pass it to the function. I tried:

     from Cocoa import *
     from CoreFoundation import *
     import myfile

     url = NSURL.fileURLWithPath_(u'Envy Code R Bold.ttf')
     status, fsref = CFURLGetFSRef(url, None)

     kATSFontContextLocal = 2
     kATSFontFormatUnspecified = 0
     kATSOptionFlagsDefault = 0
     print myfile.ATSFontActivateFromFileReference(fsref,
        kATSFontContextLocal, kATSFontFormatUnspecified, None,
        kATSOptionFlagsDefault, None)

However, this fails with the error message "# ValueError:  
depythonifying 'pointer', got 'Carbon.File.FSRef'". The problem is  
that I claimed that ATSFontActivate... takes a  
'^{FSRef=[80C]}' ("pointer to a struct FSRef which is 80 bytes"), but  
CFURLGetFSRef returns a Carbon.File.FSRef object instead (which, as  
far as I understand, is something from the days before pyobjc). Now,  
this object has a `.data()` function that returns the raw 80 bytes  
that make up the FSRef as a str, but there seems to be no way to pass  
raw data to a function that was loaded through loadBundleFunctions –  
so I have a reference to the function and all data I need to call it,  
but I can't get my data through the bridge.

Looks like a dead end (and http://osdir.com/ml/python.pyobjc.devel/2006-12/msg00024.html 
  seems to agree. Then again, that is a pre-Leopard post).


2.) Load the font through CoreGraphics, then convert it to a CoreText  
CTFont, which is toll-free bridged to NSFont, and use that for drawing.

CoreGraphics provides a function to load a font from a file, which I  
can then convert to a CTFont, which is toll-free bridged to an NSFont.  
So I should be able to load a font this way and then use Cocoa's  
normal drawInRect_withAttributes_ function to draw it. I tried:

     from CoreGraphics import *
     from CoreText import *

     fontDataProvider = CGDataProviderCreateWithFilename('Envy Code  
R.ttf')
     customFont = CGFontCreateWithDataProvider(fontDataProvider)
     print customFont  # looks good so far!

     ctFont = CTFontCreateWithGraphicsFont(customFont, 12.0, None, None)
     print CTFontCopyPostScriptName(ctFont)  # looks still good
     print ctFont

However, printing the ctFont or using it as an NSFont gives the error  
message "<Error>: can't find font object for font id 13828539." – and  
after that, even printing the postscript name returns "(null)". This  
does also happen when I call the same functions in an Objective-C  
program, so this is a limitation of the Cocoa runtime. Another dead end.


3.) Load the font through CoreGraphics, and also draw the text through  
CoreGraphics

It's possible to get a CoreGraphics context from an NSGraphicsContext.  
Then I can set the current font of the cg context to the font I loaded  
from the ttf file. The first few steps even work:

     from CoreGraphics import *
     from CoreText import *  # contains CGContextSetFont for some reason

     fontDataProvider = CGDataProviderCreateWithFilename('Envy Code  
R.ttf')
     customFont = CGFontCreateWithDataProvider(fontDataProvider)

     cgContext = NSGraphicsContext.currentContext().graphicsPort()
     CGContextSetFont(cgContext, customFont)

Now, CG has a function CGContextShowTextAtPoint that draws a given  
string (char*) at a given position into a cg context. Sounds great,  
but as it turns out this function doesn't work for fonts loaded from a  
file – it only works for activated system fonts loaded through  
CGContextSelectFont (source: http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_text/chapter_18_section_4.html 
  ). There is a function CGContextShowGlyphsAtPoint that works, but it  
takes a list of glyphs (indices into the font's glyph table – which  
glyph corresponds to which character is font-dependent!). There is no  
official function that converts a string to a list of glyphs for a  
given font, however. But there is an undocumented function:  
CGFontGetGlyphsForUnichars. As this function is undocumented, we have  
to load it ourselves again:

     # CoreGraphics is part of the ApplicationServices umbrella  
framework
     functions = [
        # bool CGFontGetGlyphsForUnichars(CGFontRef, unichar[],  
CGGlyph[], size_t);
        ( u'CGFontGetGlyphsForUnichars', 'B^{CGFont=}^So^SI'),
     ]

     # This gives a bus error btw:
     #import CoreGraphics
     #objc.loadBundleFunctions(CoreGraphics, globals(), functions)

     AppServices = objc.loadBundle("ApplicationServices", globals(),
         bundle_path=objc.pathForFramework(u'/System/Library/ 
Frameworks/ApplicationServices.framework/'))
     objc.loadBundleFunctions(AppServices, globals(), functions)

Now, let's try to call it:

     print CGFontGetGlyphsForUnichars(customFont, 'py', None, 2)

This gives "ValueError: depythonifying 'pointer', got 'str'" as error.  
I couldn't figure out how to pass python text to a function that takes  
`unichar*`. This is probably possible somehow, but since this needs  
undocumented functions anyways, I'm not too happy with this approach  
anyway.


4.) Give up, write a small C-based module that calls  
ATSFontActivateFromFileReference given an string, call that from  
Python, and call it a day

That's what I ended up doing. It works, but it is strange that this  
seems necessary for such mundane a task.


Thanks,
Nico

Re: [Pyobjc-dev] pyObjC programmers wanted for paid museum project

[Darran E. <da...@ed...>]

Re our search for python developers for the Australian museum project ...

Just a clarification that people definitely don't need to be located in 
Australia to work on this project.  Our lead developer is actually in 
the Czech Republic, and we have others working in the UK, Singapore, US 
and elsewhere.  Please don't let the distance dissuade you from making 
contact.

Cheers,
Darran

[Pyobjc-dev] defining class methods, and, is this insane?

[Matthew A. <man...@gm...>]

Hi --

After much hunting with google and through the content on the pyobjc
website, I was unable to find documentation on how one creates a class
method.  I was, in particular, wanting to add a class method to an
existing Foundation class (for use only on the Python side of the
bridge, though I can imagine wanting to have access from the
Objective-C runtime as well).  Is there an official, approved of way
of doing this?

After some experimentation and poking at source code, I did get this to work:

>>> def foo(arg, *args):
...   print arg, args
...
>>> foo = objc.selector(foo)
>>> NSObject.__class__.foo = foo
>>> NSObject.foo()
<objective-c class NSObject at 0xa06bdcc0> ()
>>> NSObject.foo(1, 2, 3)
<objective-c class NSObject at 0xa06bdcc0> (1, 2, 3)

I'm unsure if setting attributes of a class's __class__ attribute is
frowned upon for some reason, or if there were a better way.  Note, I
haven't tried to access any such function from Objective-C code.  If
someone knows, after doing the above, would it work?

The hunt to figure this out came out of a desire to have an alternate
'syntax' to call objective-C methods from python code.  Instead of:

>>> d = NSMutableDictionary.alloc().init()
>>> d.setObject_forKey_(5, "foo")

I wanted the option of saying something more like:

>>> d = NSMutableDictionary.alloc().init()
>>> d.call( "setObject:", 5,
            "forKey:", "foo")

Mostly for aesthetic/readibility (and sane line wrapping in the editor) reasons.

I was able to write such a function "call", and with modest testing,
it seems to work just fine.  I'm wondering a few things:
* is there some facility that I missed that already allows for
something like this?
* is this a bad and/or insane idea?  if so, why?  what sort of gotchas
are lurking out there if I were to add a "call" function to NSObject
(both instance and class method) and then use it in my code?
* if this is not an insane idea, and there is no facility like this
already in place, should there / could there be something like this
available in pyobjc?

My little proof of concept code is below.

Thanks,
Matt Anderson

======================================================================
#!/usr/bin/env python

from Foundation import *
import objc

def call(self, *arg):
    if len(arg) == 0:
        return None
    elif len(arg) == 1:
        sel = arg[0]
        return getattr(self,sel)()
    elif len(arg) % 2 == 0:
        sel = "".join(arg[::2]).replace(":","_")
        callargs = arg[1::2]
        return getattr(self,sel)(*callargs)
    else:
        raise Exception("selector plus arguments must be even in number!")

call = objc.selector(call)
NSObject.call = call
NSObject.__class__.call = call


d = NSMutableDictionary.alloc().init()
d.call( "setObject:", 5,
        "forKey:", "foo")
print d
# prints {
#    foo = 5;
#}
print d.call("valueForKey:", "foo")
# prints 5
print d.call("className")
# prints NSCFDictionary
print NSUserDefaults.call('standardUserDefaults')
# prints <NSUserDefaults: 0x355870>

o = NSObject.alloc().init()
print NSObject.call("description")
# prints NSObject
print o.call("description")
# prints <NSObject: 0x361810>

[Pyobjc-dev] pyObjC programmers wanted for paid museum project

[Darran E. <da...@ed...>]

Hi All,

We are working on a large museum project in Australia and need some good 
python programmers to help us realise the outcome.  On the digital side, 
the 10,000 square foot gallery features
   - a 14-screen touch "table" interactive
   - a wraparound wall of community voices/faces
   - touch interactives that solicit visiter opinions on museum content
   - RFID-enabled passes that, among other things, provide content for
     non-English speakers and accessibility to vision impaired visitors.
   - roughly 45 short films spread over 20 different viewing areas

If this sounds interesting and you,
   - are a savvy python programmer with pyObjC experience
   - can work as part of globally-distributed team (museum is set up
     with network cameras for remote access)
   - are committed to unit testing (ideally test-driven-development)
   - are available to work between half and full-time from Feb-April/May.

then please contact me directly at da...@ed....  Please provide 
an indication of your experience, your availability, and your 
saught-after hourly rate.

Cheers,
Darran

P.S. Apologies if the above "job posting" isn't welcome on the list; I 
looked but couldn't find any restrictions in this regard.

[Pyobjc-dev] catching NSUnknownKeyException?

[Daniel A. <an...@cc...>]

How can I catch NSUnknownKeyException? It's thrown by
valueForUndefinedKey_, but appears to be somehow dynamically defined in
the pyobjc code...?

Thanks,


dan

Re: [Pyobjc-dev] Decorators with descriptors

[Barron S. <li...@ba...>]

On Jan 20, 2009, at 3:16 PM, Diez B. Roggisch wrote:

> Barron Snyder schrieb:
>> Hello,
>> Can decorators with descriptors be used with pyobjc?
>> I'm getting the error:
>> *  File "/Users/barron/Projects/Python/Relations/build/Debug/ 
>> Relations.app/Contents/Resources/Person.py", line 22, in Person*
>> *    @givenNames.setter*
>> *AttributeError: 'property' object has no attribute 'setter'*
>> *2009-01-17 09:45:26.140 Relations[1476:10b] *** Terminating app  
>> due to uncaught exception *
>> Here's my class:
>> class Person(NSObject):
>>        def __init__(self, givenNames, surname):
>>        self.givenNames = givenNames
>>        self.surname = surname
>>        @property
>>    def givenNames(self):
>>        return self.givenNames
>>            @givenNames.setter
>>    def givenNames(self, givenNames):
>>        self.givenNames = givenNames
>>            @property
>>    def surname(self):
>>        return self.surname
>>            @surname.setter
>>    def surname(self, surname):
>>        self.surname = surname
>> Does pyobjc require a different way to do getters/setters than the  
>> Guido recommended way?:
>> http://mail.python.org/pipermail/python-dev/2007-November/075182.html
>
> AFAIK that's python2.6-property-descriptor. You sure you are using  
> 2.6?
>
> Diez

(sheepish grin) Well no, I'm using 2.5.1. Sorry, I'm new to all this  
and didn't know it was a new feature. Thanks for enlightening me.

- Barron

Re: [Pyobjc-dev] py2app -A equivalent in pyobjc2.0?

[Will L. <le...@gm...>]

Diez,

I realize this is a very incomplete answer, but you can build XCode  
projects from the command line using 'xcodebuild', as described here http://developer.apple.com/documentation/Darwin/Reference/Manpages/man1/xcodebuild.1.html 
  .

(You could, if you like unnecessarily complex systems, also create an  
Automator workflow using the 'Build Xcode Project' action, and then  
run that workflow using /usr/bin/automator . :)

Best,
Will

On Jan 20, 2009, at 3:31 PM, Diez B. Roggisch wrote:

> Hi,
>
> after developing quite a few nice apps in pyobjc 1.4 under
> Panther/Tiger, I finally started wetting my feet using 2.0
>
> To be brutally honest: it hasn't been a smooth ride, to say the least.
>
> Will Larson's tutorial helped to explain quite a few things. Thanks  
> for
> that, the donation is under way.
>
> But I can't stop noticing that *a lot* of things have become more
> cumbersome. That begins with the need to decorate methods and to
> explicit declare outlets.
>
> It continues with the existence of *.m-files that require a C- 
> compiler.
> Granted, I have that, but nontheless...
>
> And Will mentions in part two that methods with underscores in them
> confuse the system. Have to experience that myself, as I'd rather not
> use CamelCase...
>
> But what seems to me a rather big issue is that one does not work with
> setup.py/py2app anymore. The reason that bugs me is that I'm a heavy
> PDB-user, and my coding is done using Emacs.
>
> So I used the py2app -A functionality to create an aliased project  
> that
> I could modify the source in place, and potentially debug in the  
> console.
>
> Now I need to run build from XCode?!? Is there *any* way around  
> that? I
> know one can invoke xcode from the commandline somehow, so far I never
> did that...
>
> Or is there any chance I could continue to use 1.4? Or that the old
> py2app-powers somehow return?
>
> Please don't take this as an insult to a truly great system.
>
> Hoping for the best,
>
>
> Diez
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] py2app -A equivalent in pyobjc2.0?

[Diez B. R. <de...@we...>]

Hi,

after developing quite a few nice apps in pyobjc 1.4 under 
Panther/Tiger, I finally started wetting my feet using 2.0

To be brutally honest: it hasn't been a smooth ride, to say the least.

Will Larson's tutorial helped to explain quite a few things. Thanks for 
that, the donation is under way.

But I can't stop noticing that *a lot* of things have become more 
cumbersome. That begins with the need to decorate methods and to 
explicit declare outlets.

It continues with the existence of *.m-files that require a C-compiler. 
Granted, I have that, but nontheless...

And Will mentions in part two that methods with underscores in them 
confuse the system. Have to experience that myself, as I'd rather not 
use CamelCase...

But what seems to me a rather big issue is that one does not work with 
setup.py/py2app anymore. The reason that bugs me is that I'm a heavy 
PDB-user, and my coding is done using Emacs.

So I used the py2app -A functionality to create an aliased project that 
I could modify the source in place, and potentially debug in the console.

Now I need to run build from XCode?!? Is there *any* way around that? I 
know one can invoke xcode from the commandline somehow, so far I never 
did that...

Or is there any chance I could continue to use 1.4? Or that the old 
py2app-powers somehow return?

Please don't take this as an insult to a truly great system.

Hoping for the best,


Diez

[Pyobjc-dev] Decorators with descriptors

[Barron S. <li...@ba...>]

Hello,

Can decorators with descriptors be used with pyobjc?

I'm getting the error:

   File "/Users/barron/Projects/Python/Relations/build/Debug/ 
Relations.app/Contents/Resources/Person.py", line 22, in Person
     @givenNames.setter
AttributeError: 'property' object has no attribute 'setter'
2009-01-17 09:45:26.140 Relations[1476:10b] *** Terminating app due to  
uncaught exception

Here's my class:

class Person(NSObject):

     def __init__(self, givenNames, surname):
         self.givenNames = givenNames
         self.surname = surname

     @property
     def givenNames(self):
         return self.givenNames

     @givenNames.setter
     def givenNames(self, givenNames):
         self.givenNames = givenNames

     @property
     def surname(self):
         return self.surname

     @surname.setter
     def surname(self, surname):
         self.surname = surname

Does pyobjc require a different way to do getters/setters than the  
Guido recommended way?:
http://mail.python.org/pipermail/python-dev/2007-November/075182.html

Thanks,
Barron

[Pyobjc-dev] Get file MIME and suggested apps

[p. m. <rik...@gm...>]

Hi
I need to get some info about a file - it's MIME type, and list of
applications (or default application) that can open given file. I've
checked fileAttributes of NSFileWrapper but it doesn't help me. Can it
be done in PyObjc?

[Pyobjc-dev] Passing NSError** from Obj-C to Python

[Ian B. <ia...@on...>]

Hey folks,

I'm running into trouble with a feature/limitation of the PyObjC  
bridge and could use help figuring out how to work around it.  I am  
currently implementing a Cocoa plugin in pure Python using PyObjC,  
py2app, and the default Leopard Python frameworks.  The application  
I'm plugging into expects to be able to send this message to any  
classes that I create:

- (BOOL)performActionWithContext:(id)context error:(NSError **)outError

Because NSError pointers don't translate directly to Python, I've  
coded my class method as follows:

def performActionWithContext_error_(self, context):

Objective-C sends the message just fine, and the Python code executes  
correctly (the application's document reflects the changes after I  
activate the plugin).  However, when I run it I get an uncaught  
exception error ("Uncaught system exception: signal 11") and the  
program crashes.  Best I can tell, this is because of the NSError**  
stuff.  All the examples I can find about using NSError** talk about  
calling functions that use it from Python, and handling the tuple  
return with Python.  I haven't been able to find any resources about  
sending a message with NSError** from Objective-C to Python.  Is there  
something specific I need to do to get this working?  Any suggestions  
for how to debug the problem?

If I've got things set up the way they should be, please let me know  
that, too.  It's possible that this error is located in the  
application itself, which is currently in early beta.

I've tried setting up various signatures for the method, accepting an  
argument as a placeholder for the pointer, and so forth, but nothing  
changes the uncaught system exception.  For example:

@objc.signature('B@:@:^^@')
def performActionWithContext_error_(self, context, outError):

Works identically to the version lacking the outError argument, as  
does this:

@objc.signature('B@:@@')
def performActionWithContext_error_(self, context, outError):

Thanks for any pointers you can give me! (Sorry, couldn't resist the  
pun.)

Ian

[Pyobjc-dev] Confused on opaque pointers

[Andy M. <nzm...@gm...>]

I'm using the OpenGl library (successfully) with an __init__ that looks
like:
import objc as _objc
import sys
__bundle__ = _objc.initFrameworkWrapper("CGL",
      frameworkIdentifier="com.apple.opengl",
      frameworkPath=_objc.pathForFramework(
       "/System/Library/Frameworks/OpenGL.framework"),
     globals=globals())

However there is a function that takes an opaque pointer that I'm struggling
to wrap.

The opaque pointer is CGLPixelFormatObj and it's defined as
  typedef struct _CGLPixelFormatObject  *CGLPicelFormatObj;

The function I need to use is CGLChoosePixelFormat defined as
  CGLError CGLChoosePixelFormat ( const CGLPixelFormatAttribute *attribs,
CGLPixelFormatObj *pix, GLint *npix )

The ChoosePixelFormat function uses the Attributes (which I can create OK)
to modify the PixelFormatObj pointer to point to a newly created Object as
well as modifying npix to represent the number of screens..

First problem is that I am unable to create a CGLPixelFormatObj - get a
TypeError: Cannot create CGLPixelFormatObj objects.  I've tried using
createOpaquePointerType without any success..  How do I get this pointer
creates - -and then once I do that I presume I'll need to tweak the calling
signature of ChoosePixelFormat  to return the modified 'pix' and 'npix' ?

Thanks
Andy

[Pyobjc-dev] PyObjC & Pyglet ...

[Mic P. <mic...@gm...>]

Hi,

I'm looking at the possiblity of using Pyglet in a PyObjC application,
but I think I may have come across an issue when reading up about
PyObjC on the internet and I'm looking for a little clarification.

Pyglet uses methods like the following to allow you to override and
handle different window events ...

@window.event
def on_draw():

or

@window.event
def on_key_press(symbol, modifiers):

But as I understand it, you cannot name your standard Python methods
in this way (using the underscore) or PyObjC will cause an error?

Is this the case ?

Can I use Pyglet from a PyObjC applications (or any other Python
library for that matter) ? If so, how ?

Thanks

-Mic

[Pyobjc-dev] How to return an NSRect without crashing the bridge.

[Ian B. <ian...@ya...>]

I'm doing some exploratory coding with subclassing NSOutlineView.

I want to override a method from NSView so I tried the code:

from Foundation import *
from AppKit import *

from PyObjCTools import NibClassBuilder

class CrimsonOutlineView(NibClassBuilder.AutoBaseClass):
# NSView
    def adjustScroll_(self, proposedRect):
        returnVal = super(CrimsonOutlineView, self).adjustScroll_(proposedRect)
        print str(self)+" proposedRect_("+str(proposedRect) +") returns "+str(returnVal)
        return returnVal

Pretty simple it just passes everything and prints the results to the console. But this causes a hard crash.

I know this has to do with NSRect being a basic struct and not an NSObject but I have no idea how to make it work.

Many thanks in advance and warm regards,
IBloom

Re: [Pyobjc-dev] Question about animation proxy objects

[Mani G. <ma...@tu...>]

Hi all,

I have continued to tinker with this, and have the following to report:

I can invoke "setAlphaValue:" by using the performSelector: message, i.e.

---
anim = window.animator()
anim.performSelector_('setAlphaValue:')
---

This will make the window go fully transparent, since I can't pass in
any values and I guess it's just assuming nil or 0. But at least it
does so smoothly. :)

(Yes, I know about performSelector_withObject_ but the parameter for
setAlphaValue: is not an NSObject so it doesn't work).

This still doesn't answer the original question, but hopefully it
sheds some light. I'm sure this has to do with KVC stuff, which I am
admittedly quite unfamiliar with. Is my only option to start digging
into NSInvocation and figure out a different way to invoke the
setAlphaValue method?

Thanks in advance.

Regards,
Mani

On Wed, Dec 3, 2008 at 10:29 AM, Mani Ghasemlou <ma...@tu...> wrote:
> Hi all,
>
> Attempting to use proxy animations
> (http://developer.apple.com/DOCUMENTATION/Cocoa/Reference/NSAnimatablePropertyContainer_protocol/Introduction/Introduction.html)
> on an NSWindow object causes a segmentation fault in my application.
> I've read the documentation over and over, and I must still be missing
> something!
>
> Here's how I'm trying to do it (this is a code snippet of my app
> delegate's instance method):
>
> [CODE]
> def fadeOut(self, window):
>  window.animator().setAlphaValue_(0.0)
>  window.orderOut_(self)
> [/CODE]
>
> calling fadeOut with an NSWindow instance as input, causes the
> application to crash. I tried the same code, without the animation
> proxy:
>
> [CODE]
> def fadeOut(self, window):
>  window.setAlphaValue_(0.0)
>  window.orderOut_(self)
> [/CODE]
>
> ... and it works just fine.
>
> Any ideas what I might be doing wrong here? (Fingers crossed that it's
> not something embarrassingly obvious...)
>
> Kind regards,
> Mani
>

[Pyobjc-dev] Question about animation proxy objects

[Mani G. <ma...@tu...>]

Hi all,

Attempting to use proxy animations
(http://developer.apple.com/DOCUMENTATION/Cocoa/Reference/NSAnimatablePropertyContainer_protocol/Introduction/Introduction.html)
on an NSWindow object causes a segmentation fault in my application.
I've read the documentation over and over, and I must still be missing
something!

Here's how I'm trying to do it (this is a code snippet of my app
delegate's instance method):

[CODE]
def fadeOut(self, window):
  window.animator().setAlphaValue_(0.0)
  window.orderOut_(self)
[/CODE]

calling fadeOut with an NSWindow instance as input, causes the
application to crash. I tried the same code, without the animation
proxy:

[CODE]
def fadeOut(self, window):
  window.setAlphaValue_(0.0)
  window.orderOut_(self)
[/CODE]

... and it works just fine.

Any ideas what I might be doing wrong here? (Fingers crossed that it's
not something embarrassingly obvious...)

Kind regards,
Mani

Re: [Pyobjc-dev] Noob problem: My First PyObjC app

[Frederik De B. <fre...@pa...>]

After some more digging, I found out that XCode munges the original  
file hierarchy of your libraries. If you look inside Twite.app/ 
Contents/Resources, you'll see that scanner.py is in the root folder,  
although it should be inside of the simplejson folder.

Here's the solution:

1. Download a new simplejson version from http://pypi.python.org/pypi/simplejson 
  , and replace the old copy. Also, make sure there are no  
simplejson.py files in the root of your project.

2. Delete the folder reference to simplejson in your XCode project,  
and do a Resources > Right click > add existing files... > [ your new  
simplejson folder] > Create folder references. This last step is very  
important, and makes sure the package hierarchy is maintained.

3. Somewhere in your project was a reference to Scanner, with a  
capital 'S'. Replace that with a lowercase 's'.

3. Do a clean build of your project, so no extraneous simplejson.py  
files clutter up the system.

Here's a version that includes the above changes:

http://www.megaupload.com/?d=FOPDBQVI

Kind regards,

Frederik

[Pyobjc-dev] Noob problem: My First PyObjC app

[Alejandro N. <ale...@gm...>]

Hello List!
I´m a spanish python lover who wanted to develop for his loving aluminium
Mac.

My application tries to make a bridge between Tumblr and Twitter, making my
last Tumblr post to appear in my Twitter timeline. I´m a user of both
systems and this makes my life easier.

I made a gui with with 3 textform, one for Tumblr feed and two for Twitter
data.

If a build this on my machine all works great, but if my source is built in
other machine (same XCode 3.0 and Leopard version 10.5.2, and Mac of course)
a import error appear.

And I´m unable to build using py2app :/

A friendly hand will be welcome,

You can download source from http://www.megaupload.com/es/?d=NTIO0580

Best Regards,

Alex

Re: [Pyobjc-dev] Compiling PyObjC 2.0 trunk on 10.4

[Ronald O. <ron...@ma...>]

On 18 Nov, 2008, at 22:15, Luc Heinrich wrote:

> On 12 nov. 08, at 21:17, Luc Heinrich wrote:
>
>> So I try to regenerate the ExceptionHandling framework bridgesupport
>> file using gen_bridge_metadata but I'm not sure what to do with the
>> result.
>
> So, I've made some progress on my own.
>
> Manually generating the metadata for the ExceptionHandling framework  
> (for example) in a PyObjC.bridgesupport file which I put in pyobjc- 
> framework-ExceptionHandling/Lib/ExceptionHandling allows the tests  
> to pass. Installing this and then using it works fine but ONLY with  
> alias builds (py2app -A). Using a bundled build fails with the same  
> error than without the bridgesupport file.
>
> So now what ? :)

Have you checked if py2app copies the bridgesupport files into the  
application bundle?

I'm currently (very) slowly adding unittest for the pyobjc-framework-*  
projects, after having ran into some issues with some API's that used  
to work but stopped doing so when I wasn't paying atttention to them.  
When that's finished I'll have some time to work on py2app and  
actually doing a release again.

Porting PyObjC to OSX 10.4 has very low priority at the moment, I  
don't need that support myself and basicly won't have time to work on  
that in the forseeable future.

Ronald

Re: [Pyobjc-dev] Compiling PyObjC 2.0 trunk on 10.4

[Luc H. <lu...@ho...>]

On 12 nov. 08, at 21:17, Luc Heinrich wrote:

> So I try to regenerate the ExceptionHandling framework bridgesupport
> file using gen_bridge_metadata but I'm not sure what to do with the
> result.

So, I've made some progress on my own.

Manually generating the metadata for the ExceptionHandling framework  
(for example) in a PyObjC.bridgesupport file which I put in pyobjc- 
framework-ExceptionHandling/Lib/ExceptionHandling allows the tests to  
pass. Installing this and then using it works fine but ONLY with alias  
builds (py2app -A). Using a bundled build fails with the same error  
than without the bridgesupport file.

So now what ? :)

-- 
Luc Heinrich - lu...@ho...

[Pyobjc-dev] Compiling PyObjC 2.0 trunk on 10.4

[Luc H. <lu...@ho...>]

Greetings,

The PyObjC application I'm working on has to run on 10.4 and 10.5,  
which currently forces me to use PyObjC 1.4 on 10.4 to build the app,  
which recently started to cause some very weird performance issues so  
I would *really* like to use PyObjC 2 now.

I'm trying to build the latest sources from trunk on 10.4 and I get  
errors with pyobjc-framework-Cocoa because:
- NSUInteger does not exist on 10.4.
- _CoreFoundation_CFBinaryHeap.m defines an NSObject category with no  
name, which gcc does not seem to like.

Locally fixing these problems allows me to build pyobjc-framework- 
Cocoa, all the other pyobjc-framework that I want to use building just  
fine.

But then I'm having the incomplete bridgesupport files problem. For  
example, this wouldn't work:

from ExceptionHandling import NSLogAndHandleEveryExceptionMask

So I try to regenerate the ExceptionHandling framework bridgesupport  
file using gen_bridge_metadata but I'm not sure what to do with the  
result.

What should I do to be able to have a compilable and running PyObC 2  
on 10.4 at this point?

-- 
Luc Heinrich - lu...@ho...

Re: [Pyobjc-dev] proxy for a number behaving strangely

[Paul T. <spo...@ma...>]

Apologies, I found the problem in a different object in the same  
dictionary that wasn't ObjC derived

On 25 Oct 2008, at 21:57, Paul Thomas wrote:
>

[Pyobjc-dev] proxy for a number behaving strangely

[Paul T. <spo...@ma...>]

I'm sending a dictionary from Python to an ObjC method and one of the  
values is a number. Trouble is, I keep getting this error:

ValueError: NSInvalidArgumentException - Class OC_PythonObject: no  
such selector: isNSString__

The following are trimmed down from the real code and I can't get  
simple examples to fail the way my code does. This implies that it's a  
problem in my code of course, but I'm hoping against hope that someone  
has seen just this error before or can at least tell me what the  
problem might be.

The really strange thing (strange to me with my level of  
understanding) is that I found one case where it does work - and that  
is passing the index value returned by enumerate(<seq>).

assume 'v' comes from enumerate():

myobj.sendDictionary_(dict(version=v))  # works
x=v
myobj.sendDictionary_(dict(version=x))  # works

#all these fail...

myobj.sendDictionary_(dict(version=v))
myobj.sendDictionary_(dict(version=v+1))
x=v+1
myobj.sendDictionary_(dict(version=x))
myobj.sendDictionary_(dict(version=int(v+1))
myobj.sendDictionary_(dict(version=NSNumber.numberWithInt_(v+1)))

I mean, what could the difference be between the proxy objects created  
in the different cases?

Paul.

[Pyobjc-dev] NSProgressIndicator ignores incrementBy when called using performSelectorOnMainThread_withObject_waitUntilDone_

[Johannes S. <lgo...@go...>]

I am trying to advance an NSProgressIndicator from a thread, therefor  
i am using performSelectorOnMainThread_withObject_waitUntilDone_
to have the incrementBy call done from the main thread.

However while just calling progress_indicator.incrementBy_(some_value)  
works just as expected,
progress_indicator.  
performSelectorOnMainThread_withObject_waitUntilDone_("incrementBy:",  
some_value, True)
just does not seem to do anything. See the code below for an simple  
example.


from Foundation import *
import objc

class controller(NSObject):
     progress_indicator = objc.IBOutlet()

     @objc.IBAction
     def go_(self, sender):
         # WORKS
          
self.performSelectorOnMainThread_withObject_waitUntilDone_("test:",  
25, True)

         # DOES NOT SEEM TO WORK
         
self 
.progress_indicator 
.performSelectorOnMainThread_withObject_waitUntilDone_("incrementBy:",  
25.0, True)

     def test_(self, x):
         print 'yaye', x


What am I doing wrong?

Regards,

Johannes

[Pyobjc-dev] PyObjC on Leopard

[Dav C. <da...@al...>]

Hi there,

I spent quite a bit of time scouring the internet for answers, and  
there don't seem to be any... so now I put these to you:

1) The pyobjc website says Leopard users should install from svn  
trunk.  Why?  What (bad) happens if I use pyobjc 1.4 + python 2.5.2  
(Framework, non-System) + Leopard (OSX 10.5.x)?

2) Is there anything that's simply an amazing improvement in 2.0 (for  
existing code that already works with 1.4)?

3) How the heck to I build 2.x PyObjC from the trunk.  I've found  
threads where other's asked about this, but they never ended in an  
answer...

FWIW - I'm interested in getting pyobjc into the Enthought Python  
Distribution - which requires compatibility with 10.4.  So another  
angle on the above would be

4) Could I build pyobjc (mpkg or egg or what have you) that would work  
on both 10.4 and 10.5?

Thanks!
Dav